MIA08FA115 · Cessna T206H
Cessna T206H · Accident: controlled flight into terrain/object (CFIT) on approach
From George T Lewis Airport (CDK) to George T Lewis Airport (CDK)
Event
- NTSB case
- MIA08FA115
- 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
- 3 · 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 T206H
- 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
- N206GG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From George T Lewis Airport (CDK), Cedar Key, FLTo George T Lewis Airport (CDK)
- 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 downwind
- 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
- Controlled flight into terrain/object (CFIT)
- 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 › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident occurred less than 4 minutes after takeoff in dark night conditions and over open water, as the airplane was maneuvering near the airport. The flight departed about 15 minutes after midnight and the moon was below the horizon. Radar captured the airplane on the upwind, crosswind, and downwind legs for runway 5, reaching an altitude of 900 feet mean sea level (msl). The airplane’s last radar contact indicated a turn to base leg at 600 feet msl, while the airplane was flying toward the ocean. Witnesses at the departure airport observed the airplane on the downwind leg and then lost sight of it as the airplane turned southwest. Shortly after, a bright flash of light was observed in the water just west from their location. Wreckage examination concluded that the airplane was in a 30- to 40-degree left bank and a 5- to 10-degree nose-below-horizon attitude at the time of water impact. There was no evidence of preimpact failure or malfunction with the airplane and its systems.
Probable cause
The pilot’s failure to maintain clearance from the water during a dark night approach to a coastal airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08FA115
- Event ID
- 20080627X00926
- Case number
- MIA08FA115
- 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, 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: 3fa5fd71f51d415f1c8ab21efa341bebb9b57e60afa63b4c50abcd303e3808ea; retrieved 2026-09-13T19:09:48.572Z.