MIA07CA070 · Cessna 206G
Cessna 206G · Accident: total loss of engine power (non-mechanical) on approach
From Gainesville Regional Airport (GNV) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- MIA07CA070
- 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 206G
- Aircraft type
- Cessna 206
- 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
- N828EW
- Operator
- Eric Wiborg
- Onboard fatalities
- Unknown
- Route
- From Gainesville Regional Airport (GNV), Gainesville, FLTo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, 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
- Approach · VFR pattern final
- 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel management, improper
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 he was 15 miles north of the destination airport when he was cleared for a left downwind landing. He said he switched from the right fuel tank to the left fuel tank, and noted the right fuel tank was indicating 20 gallons. When he selected flaps, they would not work. On short final, he attempted to apply power, and noticed the engine was not producing power. He switched to the right fuel tank, with no response from the engine. He elected to land in a field, and made a hard landing in the grass, where the airplane nosed over. Postaccident examination of the airplane by an FAA inspector revealed that the left fuel tank had ample fuel, but the right fuel tank was empty. The inspector stated that the accident airplane was out of annual inspection, and the pilot's biennial flight review was past due.
Probable cause
The pilot's improper fuel management during the landing approach, resulting in a loss of engine power due to fuel starvation, and a forced off-airport landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07CA070
- Event ID
- 20070731X01063
- Case number
- MIA07CA070
- 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: c2c4046d2ed91c35d3f42d374c24fa6ae54fd1b21f9b59484d35b58773f73d12; retrieved 2026-09-21T18:33:14.528Z.