ERA24LA317 · Mooney M20J
Mooney M20J · Accident: hard landing
From Danbury Municipal Airport (DXR) to an unrecorded destination
Event
- NTSB case
- ERA24LA317
- 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
- 0 · 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
Mooney M20J
- Aircraft type
- Mooney M20
- 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
- N8201R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo not recorded
- Aircraft age
- About 46 years (built 1978)
- 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
- Hard landing
- 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 › 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 reported that while on final approach to the runway, after passing over some high terrain, he encountered turbulence, and the airplane began to sink “very fast.” The pilot increased engine power to arrest the sink rate, however, the airplane was too low resulting in a hard landing on the runway. After the hard landing, the pilot reported the airplane first went to the right, followed by a left turn and runway excursion into bushes. The airplane sustained substantial damage to the fuselage and the right aileron. The pilot reported there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain an appropriate glide path during the landing approach in terrain induced turbulence, resulting in a hard landing and subsequent runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA317
- Event ID
- 20240722194743
- Case number
- ERA24LA317
- 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: fe56ec534b565bb5976eb5ab8961572d49695161db7ced5b04674d068b567efb; retrieved 2026-09-16T19:04:21.102Z.