MIA84FA053 · Cessna 210M
Cessna 210M · Accident: in flight collision with terrain/water on approach
From Charleston International Airport (CHS) to an unrecorded destination
Event
- NTSB case
- MIA84FA053
- 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
- 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 210M
- Aircraft type
- Cessna 210
- 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
- N761HZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charleston International Airport (CHS), Charleston, SCTo not recorded
- 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
- Destroyed
Cause areas
- Pilot in command › IFR procedure, not followed
- Pilot in command › Minimum descent altitude, below
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT 1926 THE PLT WAS CLEARED FOR THE LOC BC ARCH FOR RWY 27R. AT 1927 THE ACFT ACKNOWLEDGED A CLEARANCE TO LAND. 10 SECS LATER THE RADAR TARGET DISAPPEARED. THE PLT WAS RESCUED AT 2050 FROM THE WATERS OF THE ATLANTIC OCEAN ABOUT 1 MIOFF THE BEACH AT WEST PALM BEACH. THE ACFT WAS NOT RECOVERED & THE 3 PAX ARE ARE MISSING. THE PLT STATED THAT HE CROSSEDTHE FAF (KEACH INTERSECTION) AT 900 FT. MINIMUM ALTITUDE AT THE FAF IS 1,600 FT. THIS WAS THE LAST TIME THE PLT RECALLS LOOKING AT THE ALTIMETER. HE REMEMBERS LOOKING OUTSIDE & BELOW THE ACFT & SEEING A CLOUD LAYER. HE ALSO REMEMBERS THINKING THA THE ATIS WX WAS REPORTED AT 500 FT OVERCAST & THAT BY DESCENDING BELOW THIS LAYER HE SHOULD BREAK OUT OF THE CLOUDS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA84FA053
- Event ID
- 20001214X45362
- Case number
- MIA84FA053
- 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. 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: a6bfbbff608c9e2b65c847b4cfa25000dc25431c9fb709943bb439dc478fb566; retrieved 2026-09-21T05:42:42.326Z.