MIA07CA115 · Mooney M20R
Mooney M20R · Accident: overrun during landing
From Freeway Airport (W00) to an unrecorded destination
Event
- NTSB case
- MIA07CA115
- 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 M20R
- 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
- N321MD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Freeway Airport (W00), Mitchellville, MDTo not recorded
- Aircraft age
- Not recorded
- 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 · landing roll
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Go-around, not performed
- Pilot in command › Proper touchdown point, not attained
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 stated that the airplane was on the glide path and approach speed was approximately 85 knots. Several minutes prior, the manifold pressure gauge became erratic and was unable to be used as an accurate indication. He pushed the manifold control full forward for the remainder of the approach. The landing touchdown was 1/3 down the runway and seemed to be a "tad fast". Halfway down the runway, he realized the engine wasn't going completely to idle. At about 2/3 down the runway, knowing that the airplane was too fast, he looked at the option of going around and ruled it out because of the slow speed and the height needed to clear the tree line. He attempted to slow the airplane by applying full brakes; however, was unable to slow down before running off the runway. The pilot stated to the NTSB investigator that there were no mechanical issues with the airplane and he should have initiated a go-around. The published length of runway 18/36 at the Freeway Airport, Mitchellville, Maryland, is 2,420 feet by 40 feet.
Probable cause
The pilot's failure to attain the proper touchdown point for landing and his failure to initiate a go-around when he realized the airplane would touchdown past the intended point.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07CA115
- Event ID
- 20070829X01264
- Case number
- MIA07CA115
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: e842ed337fffbaa811a6ad53cf2c4d19af3038dfc6508af26ad128dcfaa44007; retrieved 2026-09-22T03:42:12.509Z.