FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA063 · Mooney M20E

16 Dec 2025 · Gonzales, LA, United States

Mooney M20E · Accident: hard landing

From Baton Rouge Metropolitan Airport (BTR) to an unrecorded destination

Report a problem

Event

NTSB case
CEN26LA063
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

Mooney M20E

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
N9081V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo not recorded
Aircraft age
About 57 years (built 1968)
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 › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot and his safety pilot were conducting a proficiency flight for insurance purposes. According to the pilot, he began the landing flare too high and the airplane bounced when the main wheels touched down. The safety pilot reported that he monitored the pilot’s remedial action to the bounced landing. According to the safety pilot, the pilot increased airplane pitch but did not increase engine power which resulted in a second bounced landing. The safety pilot then took over the flight controls and advanced the throttle to maximum rpm. The safety pilot stated that he was unable to regain directional control and the airplane touched down a third time, veered left, passed through a fence, and impacted trees. The airplane sustained substantial damage to both wings, the fuselage, and the horizontal stabilizer. Both pilots reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. Additionally, the safety pilot stated that the accident might have been prevented had he taken over controls and/or called for an aborted landing sooner.

Probable cause

The pilot’s improper pitch control that resulted in a hard landing, and his improper recovery from multiple bounced landings. Contributing to the accident was the safety pilot’s delayed response to the initial bounced landing which led to the runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA063
Event ID
20251216202172
Case number
CEN26LA063
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: c38d8c0b299c0fe271e8436bd344adb1d4edc7c72e7bd20f3677d6980b889095; retrieved 2026-09-16T20:36:46.252Z.