GAA16CA323 · Mooney M20 J
Mooney M20 J · Accident: runway excursion during landing
From Lake Elmo Airport (21D) to Reedsburg Municipal Airport (C35)
Event
- NTSB case
- GAA16CA323
- 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
- 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
Mooney M20 J
- 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
- N9139U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Elmo Airport (21D), ST PAUL, MNTo Reedsburg Municipal Airport (C35), Reedsburg, WI
- Aircraft age
- About 25 years (built 1991)
- 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 · aborted after 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
- Runway excursion
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
In a telephone interview with the NTSB Investigator-in-charge (IIC), the pilot stated that the airplane touched down midfield, and he knew he was going to overrun the runway. He attempted to abort the landing, however the airplane over ran the runway and impacted the airport perimeter fence.
A postaccident examination revealed substantial damage to the fuselage.
According to the pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
After multiple requests, the pilot did not return the National Transportation Safety Board Form 6120.1 Pilot/Operator Aircraft Accident/Incident Report as requested.
Probable cause
The pilot's long landing and failure to stop the airplane on the runway, resulting in an overrun, impact with a fence, and substantial damage to the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA323
- Event ID
- 20160622X93331
- Case number
- GAA16CA323
- 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. 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: d8ca6f62513516f5023c9e8407189184445aabefc2cf7691290eb45b63c81c09; retrieved 2026-09-16T03:32:32.428Z.