CEN10FA164 · Maule M-5-235C
Maule M-5-235C · Accident: landing gear not configured
From Addison Airport (ADS) to Lake Lewisville, TX
Event
- NTSB case
- CEN10FA164
- 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
- 1 · 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
Maule M-5-235C
- Aircraft type
- Maule M-5
- 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
- N56489
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Addison Airport (ADS), Dallas, TXTo Lake Lewisville, TX
- 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
- Landing gear not configured
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Following a short cross-country flight, the pilot performed a water landing with the amphibious float-equipped airplane. During touchdown, the airplane nosed over and came to rest inverted, partially submerged in water. A postaccident examination of the wreckage revealed that the pilot had landed with the landing gear in the extended position. The examination also revealed that the floats were equipped with four visual landing gear position indicators, all of which indicated that the landing gear was in the extended position. According to a “Before Landing On Water” checklist for the amphibious floats, the landing gear position (retracted) was to be confirmed visually before landing. No preimpact anomalies were identified during the examination that would have precluded the airplane from operating normally.
Probable cause
The pilot did not retract the landing gear before a water landing. Contributing to the accident was the pilot did not use a checklist.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10FA164
- Event ID
- 20100318X30659
- Case number
- CEN10FA164
- 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, 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: 5be485173dbe98667682c54848eb0bcc5c785f938d895e9237b240fac0e25b92; retrieved 2026-09-13T20:43:27.019Z.