CEN13CA083 · Mooney Airplane Co Inc M20TN
Mooney Airplane Co Inc M20TN · Accident: loss of control in flight on approach
From Animas Air Park (00C) to Animas Air Park (00C)
Event
- NTSB case
- CEN13CA083
- 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 Airplane Co Inc M20TN
- 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
- N562BG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Animas Air Park (00C), Durango, COTo Animas Air Park (00C), Durango, CO
- 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
- Approach · VFR go-around
- 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
- 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
The airplane bounced twice during landing. The pilot said that after the second bounce, he added full throttle for a go-around and that the airplane began to drift to the left side of the runway centerline. Just as the airplane began to climb, the pilot retracted the landing gear and flaps, and the nose of the airplane immediately pitched up. The right wingtip struck the runway surface, and the airplane veered sharply to the right and impacted terrain on the right side of the runway. The impact resulted in the collapse of the landing gear and substantial damage to the engine mount, firewall, fuselage, and horizontal stabilizer. The pilot reported that there was no mechanical malfunction or failure and that he just failed to maintain control of the airplane during the landing.
Probable cause
The pilot's improper recovery from a bounced landing, and his failure to maintain airplane control during the go-around maneuver.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA083
- Event ID
- 20121202X32601
- Case number
- CEN13CA083
- 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: 9c58f7ababf6c95f7f30d08f0834cdd3ccf2727f806286be3ad8ff5baf7bcbd2; retrieved 2026-09-15T20:30:21.096Z.