Maule M5-235C accident near Zellwood, Florida, April 18, 2010
On April 18, 2010 at about 11:15 pm local time, a Maule M5-235C, registered N9196E, was substantially damaged in an accident during maneuvering near Zellwood, Florida (Orlando North Airpark airport). It was a positioning flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain airspeed while maneuvering after takeoff, which resulted in an aerodynamic stall, loss of aircraft control, and collision with trees.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 18, 2010 · about 11:15 pm local time
- Place
- Zellwood, Florida · Orlando North Airpark · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Maule M5-235C · all M5-235Cs on the register
- Registration
- N9196E · no longer on the register · serial 7130C
- Damage
- Substantial damage
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
After an engine runup, the pilot taxied onto the runway and commenced his takeoff roll. The airplane lifted off approximately 1/3 of the length down the runway. After liftoff, one witness thought she heard popping and the airplane immediately turned approximately 40 degrees to the right in the approximate direction of the pilot's destination airport, which one witness stated was the pilot's usual practice. What appeared to be a thin trail of dark gray smoke or black smoke was observed trailing from the airplane. The airplane then reached a height of approximately 60 feet above ground level, leveled off, and the smoke stopped. Upon approaching a tree line that ran perpendicular to the right side of the runway, the airplane was observed to climb. The airplane cleared the trees by approximately 50 feet, stalled, entered a spin, and impacted the ground. A post crash fire then ensued. The airplane had been in a previous accident and it was reported to the NTSB that it may have had a preexisting engine problem. A postaccident examination of the airplane and engine revealed no evidence of any preimpact failure or malfunction of the airplane or engine. During the takeoff, light rain was falling. This may have resulted in the formation of visible vapor during power application which could have appeared to the witnesses as smoke. It is also possible that the smoke may have been residual oil being burned off from a replacement of the oil cooler, which occurred 16 days prior to the accident, recent engine oil servicing, seepage of oil past the seals or rings while the airplane was parked, or a richer than normal mixture due to the atmospheric conditions that existed at the time. The popping that may have been heard could also have been caused by a richer than normal mixture. Had the pilot flown a normal departure which continues straight ahead along the extended runway centerline and continues until reaching a point at least 1/2 mile beyond the departure end of the runway and within 300 feet of the traffic pattern altitude. Following Federal Aviation Administration guidance for departing traffic patterns would have kept the airplane clear of the treeline.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Unknown or undetermined during initial climb
- Aerodynamic stall/spin during maneuvering defining event
- Loss of control in flight during maneuvering
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- factor Aircraft › Aircraft power plant › Power plant › (general) › Not specified
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 673 hours in all; 610 as pilot in command
- Last flight review: April 11, 2009
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 2,838 hours
- Last inspection: 100-hour inspection, March 23, 2010
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-540-J1A5D (piston); 0 hours total
- Fire on the ground
- Operator: Airsign Inc.
The flight
- Departed from: FA83 Zellwood FL at 11:15 pm
- Destination: X35 Dunellon FL
- Flight plan: VFR
- Runway 27, 2,577 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 160° at 5 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 7,000 ft
- Temperature: 66°F (19°C), dew point 61°F (16°C)
- Altimeter: 29.90 inHg
- Observation at 10:53 pm from LEE, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
