FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA277 · Lancair ES

22 Jul 2024 · Oshkosh, WI, United States

Lancair ES · Accident: loss of control in flight on approach

From Hartford Municipal Airport (HXF) to Wittman Regional Airport (OSH)

Report a problem

Event

NTSB case
CEN24FA277
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
API-reported fatalities
2 · all aircraft and ground
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

Lancair ES

Aircraft type
Lancair ES
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
N18BG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hartford Municipal Airport (HXF), Hartford, WITo Wittman Regional Airport (OSH), Oshkosh, WI
Aircraft age
About 23 years (built 2001)
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
Approach · VFR pattern base
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • 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 was flying the airplane on an arrival route when the air traffic controller instructed the pilot to widen the turn to allow for two warbird airplanes to land in front of him. The pilot acknowledged the transmission and stated that he had the two airplanes in sight. Wind was recorded as variable at 4 kts. According to ADS-B data, the airplane turned south, consistent with a modified downwind, then back to the east, and then toward the north, consistent with a base-to-final turn. The airplane was about 975 ft mean sea level (msl) and 84 kts ground speed when it started a turn to the north toward the airport. The last data point recorded from the airplane was about 975 ft msl and 70 kts ground speed, 1.5 miles from the approach end of the runway. According to the airframe pilot operating handbook, the stall speed varies from 59 to 74 kts indicated airspeed at zero degrees of bank. The airplane impacted a soybean field upright and was destroyed by a postimpact fire. An examination of the airplane, engine, and flight control system revealed no mechanical anomalies or failures that would have precluded normal operations. Further review of the ADS-B data from the warbird flight showed that the landing Aero L-39 airplane passed well to the east and above the flight path of the accident airplane. A review of the wake vortices generated by the L-39 revealed that the accident airplane would not have encountered the wake of the L-39 before impact. It is most likely that the pilot did not maintain adequate airspeed while maneuvering to ensure spacing from the L-39 that landed ahead while completing his turn toward final. This resulted in an inadvertent stall and subsequent impact with terrain.

Probable cause

The pilot’s failure to maintain adequate airspeed which resulted in an exceedance of the airplane’s critical angle of attack and an aerodynamic stall while maneuvering for traffic spacing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA277
Event ID
20240722194740
Case number
CEN24FA277
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: 416d02db65aba293f47dc42f21bdd2b9c1f186d97a07c281341415ae455ab5a4; retrieved 2026-09-15T08:25:00.173Z.