CEN25LA329

NTSB accident investigation · JMB Aircraft S R O VL-3LSA-912 · Erie, CO · August 18, 2025

Accident · No injuriesClass 4 · LimitedFinal report
Date
August 18, 2025, 15:20 local (21:20 UTC)
Place
Erie, CO
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N593TTJMB Aircraft S R O VL-3LSA-912
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report January 9, 2026
Report
Approved by Office Director
Investigation class
Class 4 - Basic report with no Prelim publish
NTSB office
Central Region
Parties
FAA FSDO
FAA report
20250818011219A
Case key
200828

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The flight instructors inadequate supervision of the flight and delayed remedial action and the pilot’s improper landing flare during which resulted in a hard landing.

Findings · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Not attained/maintainedJMB Aircraft S R O VL-3LSA-912: 1 caseAll aircraft: 1,285 casesProbable cause
Action: delayed actionPersonnel issues › Action/decision · Instructor/check pilotJMB Aircraft S R O VL-3LSA-912: 1 caseAll aircraft: 894 casesProbable cause
Attention/monitoring: monitoring other personPersonnel issues › Psychological · Instructor/check pilotJMB Aircraft S R O VL-3LSA-912: 1 caseAll aircraft: 200 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot receiving instruction reported that the flight was a cross-country instructional flight in preparation for a commercial pilot certificate. The flight progressed uneventfully to several airports and returned to the original departure airport. The pilot and flight instructor discussed the approach to the airport and decided on a straight-in approach. When they descended to about 1,000 ft above ground level (agl), the turbulence intensified. The pilot flew the approach manually, at 60 to 65 kts., and maintained a stable glidepath using the precision approach path indicator (PAPI) to aid guidance. At 400 ft agl a rapid sink rate started and the pilot added power to regain the glideslope. When the airplane crossed the runway threshold, the pilot reduced engine power to idle and initiated a flare. A gust of wind caused momentary instability, and she called “go-around” and added power to initiate a go-around. Just as she did this, the flight instructor pulled aft on the control stick, but no positive transfer of control occurred. The airplane’s nose pitched up abruptly which resulted in a tail strike, aerodynamic stall, and right-wing drop. In an earlier telephone interview with the pilot, she said that during the landing approach, the autopilot was disengaged about 1,000 ft agl. Just as they were about to touch down, a gust of wind caused the approach to become unstable, and she applied power to go-around when the CFI took control of the airplane. She noted that she did not hear a “my airplane” command or similar. The CFI pulled back on the controls and she thinks the airplane stalled and it also struck the ground tail first. When asked if there were any mechanical problems with the airplane, she said there were not any. During a telephone interview with the flight instructor, he stated that the approach to the runway was a little “rocky” due to winds, and just as they were about to touch down, a gust of wind caused the airplane to balloon up. He said the pilot did not recover and he did not react quickly enough, and the airplane struck the runway. When asked if there were mechanical issues with the airplane, he said there were none. The flight instructor did not submit a written report of the accident. The airplane sustained substantial damage to the fuselage.

Aircraft

Registration
N593TT
Reported as
JMB Aircraft S R O VL-3LSA-912
Category
Airplane
Serial number
VL-3-520
Built
2023
Engine
Rotax 912ULS, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
N593tt Rental LLC
Registered owner
N593tt Rental LLC
Airworthiness certificate
Special, Special light-sport (Special)
Departed
FNL · Fort Collins, CO
Destination
Same as departure
Airport
EIK · Erie Muni, runway 16/34, 4,700 × 60 ft, concrete
Equipment
ADS-B, Airframe parachute, Stall warning system, Onboard weather, Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, Auto-pilot, Angle of attack indicator

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
47
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
July 24, 2025
Seat
Left
Restraint
4-point
Flight hours
350 total · 8 in this make and model · 108 as pilot in command · 100 in the last 90 days · 62 in the last 30 days · 6 in the last 24 hours
Role
Flight instructor
Age
24
Injuries
None
Certificates
Flight instructor, Commercial
Airplane ratings
Single-engine land, Single-engine sea, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, With waivers/limitations
Last flight review
December 1, 2024
Seat
Right
Restraint
4-point
Flight hours
670 total · 80 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
280° at 7 knots
Visibility
7 statute miles
Lowest ceiling
None
Temperature
91 °F, dew point 52 °F
Altimeter
30.12 inHg
Observed at
KEIK
METAR
METAR KEIK 182115Z AUTO 28007KT 7SM CLR 33/11 A3012 RMK AO2 LTG DSNT N AND E AND SE T03280108=

Docket · 4

The files NTSB released with the investigation on January 9, 2026, on NTSB’s docket system: statements, records, photos and specialists’ reports. 7.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.