FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA329 · JMB Aircraft S R O VL-3LSA-912

18 Aug 2025 · Erie, CO, United States

N593TT Rental JMB Aircraft S R O VL-3LSA-912 · Accident: abnormal runway contact during landing

From Northern Colorado Regional Airport (FNL) to an unrecorded destination

Report a problem

Event

NTSB case
CEN25LA329
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

JMB Aircraft S R O VL-3LSA-912

Aircraft type
JMB VL-3
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N593TT
Onboard fatalities
Unknown
Route
From Northern Colorado Regional Airport (FNL), Fort Collins, COTo not recorded
Aircraft age
About 2 years (built 2023)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Abnormal runway contact
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA329
Event ID
20250820200828
Case number
CEN25LA329
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: e7b9fde45c9a946ab15951a146a2c1b77d776043b8b4e51d54c90c61eae1fe3a; retrieved 2026-09-16T20:14:28.772Z.