MIA03CA091 · Maule M-5-235C
Maule M-5-235C · Accident: loss of control on ground/water during landing
From Bob Sikes Airport (KCEW) to HCA Florida Westside Hospital Heliport (FD82)
Event
- NTSB case
- MIA03CA091
- 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
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
- N366X
- Operator
- William O. DeWeese · private individual
- Onboard fatalities
- Unknown
- Route
- From Bob Sikes Airport (KCEW), Crestview, FLTo HCA Florida Westside Hospital Heliport (FD82), Jay, FL
- 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
- Loss of control on ground/water
- 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 › Recovery from bounced landing, not performed
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 after takeoff, the flight proceeded to the private airstrip where he performed two touch-and-go landings. The flight remained in the traffic pattern for another touch-and-go landing, and touched down with 2 notched of flaps extended within the first third of the 2,000-foot long runway designated 27. The airplane bounced and he maintained, "the tail down attitude and the plane settled down into the ground." He thought he could land and committed to the landing roll, but lost directional control towards the left side of the runway. He applied differential braking, and the airplane nosed over coming to rest about the middle of the runway near the departure end. He further reported that the accident could have been prevented if he had performed a go-around, and there was no mechanical failure or malfunction.
Probable cause
The failure of the pilot to perform a go-around after bouncing following touchdown, resulting in the airplane nosing over during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03CA091
- Event ID
- 20030407X00444
- Case number
- MIA03CA091
- 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: 8087aa7471ae8dc4f3d7cde61e3c021c16a00cb0cbc1f753d1e80d63658de903; retrieved 2026-09-22T09:28:12.434Z.