CEN24LA037 · Charles L. Hayes Lancair IVP Turbine
Charles L. Hayes Lancair IVP Turbine · Accident: landing area overshoot
From Midland Airpark (MDD) to an unrecorded destination
Event
- NTSB case
- CEN24LA037
- 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
Charles L. Hayes Lancair IVP Turbine
- Aircraft type
- Charles L Hayes LANCAIR IVP TURBINE
- 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
- N751HP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Midland Airpark (MDD), Midland, TXTo not recorded
- Aircraft age
- About 21 years (built 2002)
- 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
- 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
- Landing area overshoot
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that while in cruise at flight level (FL) 250, the airplane sustained a sudden loss of pressurization. He descended the airplane to 10,000 ft mean sea level (msl) and continued to his planned destination. He had not previously landed at the destination airport, so he performed a touch and go landing “to see the field,” and then flew a standard traffic pattern for landing. On the downwind leg the ball on the top of the power lever unscrewed and the pilot continued the approach. The pilot reported the airplane touched down in the first 500 ft of the runway without a float or a bounce in ground effect. He immediately “hit [the] brakes gently” and maintained the runway centerline. For about 5 to 10 seconds, the pilot unsuccessfully attempted to move the power lever into beta-reverse and applied maximum braking; however, the brakes faded, and the stopping power decreased. The airplane subsequently exited the end of the runway, went through an airport perimeter fence, and struck a moving vehicle on a roadway. The airplane sustained substantial damage to the fuselage and right wing.
A review of a cellular telephone camera video provided to the National Transportation Safety Board showed that the airplane touched down near the midpoint of the 3,002 ft runway, bounced and touched down again. Tire skid marks were observed about 200 ft beyond the runway’s midpoint and continued for about 1,300 ft until the airplane exited the runway surface. Automatic dependent surveillance-broadcast (ADS-B) and avionics data showed the airplane’s groundspeed was between 96 and 99 knots and the flaps were extended to 40° during the final approach.
Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded a normal landing. Although the power lever ball top unscrewed, the power lever functioned normally between full power and reverse settings.
Probable cause
The pilot’s failure to attain the proper touchdown point during landing, which resulted in a runway excursion and collision with terrain and a vehicle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA037
- Event ID
- 20231113193375
- Case number
- CEN24LA037
- 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: d31c89b05874dea54c31182990c975b3ddba049b32a1135d0176664af18a8a6c; retrieved 2026-09-16T18:17:26.173Z.