FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA164 · Lancair LEGACY FG

22 Apr 2024 · Spicewood, TX, United States

Lancair LEGACY FG · Accident: loss of control in flight during initial climb

From Garner Field (UVA) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24FA164
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
1 · all aircraft and ground
Ground fatalities
0
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 LEGACY FG

Aircraft type
Lancair LEGACY FG
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
N550NL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Garner Field (UVA), Uvalde, TXTo not recorded
Aircraft age
About 19 years (built 2005)
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
Initial climb
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
  • Aircraft › Aircraft systems
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Witnesses reported that, during the pilot’s initial approach for landing on runway 17, the experimental airplane was fast, encountered a wind gust, and ballooned, prompting the pilot to initiate a go-around. During the subsequent approach, one witness observed the nose landing gear nearly contact the runway. The pilot again initiated a go-around, during which the airplane entered a steep, left-turning climb before descending nose-down into terrain. A postimpact fire consumed most of the airplane. The recorded wind conditions at a nearby airport about 10 minutes after the accident were from 170° at 6 knots (kts) with gusts to 15 kts. An observation recorded about 10 minutes before the accident included wind from 180°, variable between 140° and 220°, at 6 kts with gusts to 14 kts. Postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions that would have precluded normal operation. The engine displayed internal continuity and signs of producing power at impact, and propeller damage was also consistent with power being produced at the time of impact. The flap actuator position corresponded to full flap extension (40°); however, the airplane’s go-around procedure specified reducing the flap extension to 20° after applying power and establishing the climb. Toxicology testing detected the over-the-counter antihistamine cetirizine at levels unlikely to have caused significant impairment. Autopsy findings identified significant coronary artery disease that put the pilot at an increased risk of a sudden impairing or incapacitating cardiac event, including angina, arrhythmia, or heart attack. There is no autopsy evidence that such an event occurred; however, such an event does not leave reliable autopsy evidence if it occurs immediately before death. No evidence of an acute medical event was identified. Given the position of the flap actuator as found at the accident site, it is likely that the pilot failed to retract the flaps during the go-around as prescribed by the pilot’s operating handbook, which likely significantly reduced the climb performance of the airplane. It is also likely that the pilot subsequently exceeded the airplane’s critical angle of attack during the attempted go-around with the flaps fully extended, which resulted in an aerodynamic stall and loss of airplane control at an altitude that was too low for recovery.

Probable cause

The pilot’s failure to properly configure the airplane during a go-around in gusting wind conditions, and his subsequent exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall at an altitude too low for recovery.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA164
Event ID
20240423194133
Case number
CEN24FA164
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, 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: 9ac1796b2d8a8963a20a451b77a932761454fbd6f4d83839c3e43c4360c3c20e; retrieved 2026-09-15T08:12:57.072Z.