FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL05FA066 · Cessna T206H

26 Mar 2005 · Johns Island, SC, United States

Cessna T206H · Accident: in flight collision with terrain/water on approach

From ISZ · Blue Ash, OH to Charleston Executive Airport (JZI)

Report a problem

Event

NTSB case
ATL05FA066
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
2 · all aircraft and ground
Ground fatalities
0
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
Instrument 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
N222YT
Operator
Unknown
Onboard fatalities
Unknown
Route
From ISZ · Blue Ash, OHTo Charleston Executive Airport (JZI), Johns Island, SC
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 · IFR final approach
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
In flight collision with terrain/water
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

  • Pilot in command › Altitude, not maintained
  • Pilot in command › IFR procedure, not followed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Upon arrival at the destination airport, the flight was cleared for an ILS Approach to runway 09. The flight was inbound from the final approach fix when it descended below published minimums, collided with the ground, and burst into flames approximately 866 feet left and 597 feet short of the runway. The last radar return reported the airplane inbound from the final approach fix, 0.19 nautical miles from the runway, 200 feet above the ground, and traveling at 70 knots. Post-accident examination of the airplane revealed fire damage. Post-accident examination revealed no evidence of mechanical malfunction with the airframe or engine. The ILS approach to runway 09 was test flown on March, 29, 2005 by an FAA Flight Inspector and was found satisfactory. At 2114 eastern standard time, the Charleston Executive Airport weather reporting facility, reported winds from 090 degrees, magnetic, at nine knots, visibility of 0.25 statute miles, overcast 100 feet, temperature 14 degrees, Celsius, and dew-point 14 degrees, Celsius, and an altimeter setting of 30.00 inches of mercury. Published weather minimums for the ILS runway 9 (S-ILS ) are 267 feet with 0.75 mile visibility.

Probable cause

The pilot's failure to follow instrument flight procedures and descent below the published minimum descent altitude, which resulted in an in-flight collision with terrain during an instrument approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL05FA066
Event ID
20050331X00385
Case number
ATL05FA066
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-03-27.
  • API snapshot SHA-256: eb18948c460ee72a9ddbdf8fd8c4f7f11e81ba2f811dd2f06f5a756891051ef8; retrieved 2026-09-20T18:05:43.071Z.