CEN09CA244 · Mooney M20J
Mooney M20J · Accident: collision with terrain/object (non-CFIT) during landing
From Salem Municipal Airport (I83) to Salem Municipal Airport (I83)
Event
- NTSB case
- CEN09CA244
- 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 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
- N115MS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salem Municipal Airport (I83), Salem, INTo Salem Municipal Airport (I83), Salem, IN
- 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 · 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
- Collision with terrain/object (non-CFIT)
- 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 systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was practicing takeoff and landings when he extended the landing gear and heard the landing gear motor start while the airplane was on the downwind leg to the runway. The pilot noticed that the landing gear was not down during the landing flare. The airplane touched down on the runway with the landing gear retracted, and the airplane skidded about 500 feet before coming to a stop. The airplane received substantial damage when the airplane's firewall and underside skin were damaged. During the airplane's recovery, the landing gear control handle was placed into the down position and the landing gear extended when the master switch was placed into the on position. Postaccident inspection of the airplane revealed no anomalies.
Probable cause
The pilot's failure to follow the landing checklist and extended the landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA244
- Event ID
- 20090413X02042
- Case number
- CEN09CA244
- 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: 8979ec821003bb975dd21ba5e736b0a474e74391ab983b7dc1e6cc9e45f1e338; retrieved 2026-09-15T10:55:21.668Z.