Cessna 152 accident near Cross City, Florida, April 16, 2009
On April 16, 2009 at about 2:15 pm local time, a Cessna 152, registered N64988, was substantially damaged in an accident during enroute (climb to cruise) near Cross City, Florida. It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 16, 2009 · about 2:15 pm local time · cases in 2009
- Place
- Cross City, Florida · map
- Type
- Accident
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 152 · all 152s on the register
- Registration
- N64988 · registry record · serial 15281515
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While climbing through 3,400 feet mean seal level (msl), the newly certificated private pilot noticed that the engine power decreased by approximately 300 rpm; however, the engine was running smoothly with no abnormal noise. The pilot verified that the engine controls were in the proper position and he then positioned the carburetor heat to "ON." The engine power continued a steady decay to 1,400 rpm as the airplane descended to 1,000 feet msl and the pilot elected to perform a forced landing to a field that he had been circling. During the landing, he overshot his intended touchdown point. The airplane subsequently struck two fence posts and came to rest inverted in the field. Review of fueling records revealed that the airplane had adequate fuel to complete the round trip cross-country flight. The engine crankshaft and carburetor were damaged during impact, which limited the field examination of those components. The cabin heat was noted in the "ON" position and the carburetor heat was in the "OFF" position; however, the carburetor box had been pulled from the airframe during impact. Examination of the wreckage could not identify the reason for the engine power loss. Review of a Federal Aviation Administration Carburetor Icing Chart revealed "Serious icing - glide power" for the reported temperature and dew point conditions.
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
- Loss of engine power (partial) during enroute (climb to cruise) defining event
- Landing area overshoot during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to carburetor icing › Not specified
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 136 hours in all; 136 in this make and model; 60 in the last 90 days; 35 in the last 30 days; 40 as pilot in command; 0 on instruments
- Last flight review: March 24, 2009
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 7,286 hours
- Last inspection: annual inspection, April 7, 2009; 21 hours since
- Maximum gross weight: 1,670 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-235 (piston); 0 hours total
- Operator: Sunrise Aviation
The flight
- Departed from: CTY Cross City FL at 2:00 pm
- Destination: OMN Ormond Beach FL
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 050° at 11 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 63°F (17°C), dew point 52°F (11°C)
- Altimeter: 30.00 inHg
- Observation at 1:53 pm from CTY
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Other NTSB records under N64988 the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N64988 on the register today · the tail number may have moved to another aircraft since
- Cessna 152 1,636 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Lycoming O-235 14 aircraft carry this series today · as the NTSB recorded it
- Cross City Airport · departed from
- Ormond Beach Municipal · bound for
- Accidents and incidents in Florida 6,111 since 1982 · 984 in the last ten years
- Florida 21,709 aircraft registered
- Other NTSB records under N64988 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA09LA247.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
