FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11LA065 · Cessna 172

16 Nov 2010 · Hobe Sound, FL, United States

Cessna 172 · Accident: fuel contamination en route

From Tailwinds Airport (FD15) to Jacksonville Executive at Craig Airport (CRG)

Report a problem

Event

NTSB case
ERA11LA065
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

Cessna 172

Aircraft type
Cessna 172
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
N8306B
Operator
Ramon C Fenner · private individual
Onboard fatalities
Unknown
Route
From Tailwinds Airport (FD15), Jupiter, FLTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, 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
En route · cruise
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
Fuel contamination
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 › Fluids/miscellaneous hardware

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, about 20 minutes into the flight, the engine began to lose power. He was able to keep the engine running using the fuel primer knob; however he could not maintain the airplane's altitude. The pilot then performed a forced landing into an orange grove and the airplane nosed over in the soft terrain, resulting in substantial damage to the wings. Two inspectors from the Federal Aviation Administration examined the airplane and engine. The carburetor was disassembled and a thick, black and brown, slime-like substance was found in the carburetor bowl, blocking the fuel channel and drain plug. The origin of the contamination was not determined.

Probable cause

A partial loss of engine power due to fuel contamination in the carburetor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11LA065
Event ID
20101116X04443
Case number
ERA11LA065
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: 9543ca5e77879f51292076cad1a2fa8b80e7a27c60c5446be6ae61e34c481642; retrieved 2026-09-15T15:34:07.696Z.