FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA266 · Cessna 210 A

8 Sept 2019 · Marathon, FL, United States

Cessna 210 A · Accident: collision with terrain/object (non-CFIT) during initial climb

From Florida Keys Marathon International Airport (MTH) to Savannah Hilton Head International Airport (SAV)

Report a problem

Event

NTSB case
ERA19FA266
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
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 210 A

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
N9436X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Savannah Hilton Head International Airport (SAV), Savannah, GA
Aircraft age
About 58 years (built 1961)
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
Initial climb
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
Collision with terrain/object (non-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

  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot had planned a cross country instrument flight rules (IFR) flight but had not contacted air traffic control to receive an IFR clearance before departing. He was departing from a coastal airport during dark morning hours, prior to sunrise, and after takeoff made a right climbing turn. The airplane reached an altitude about 400 feet above the ground, about 90° through the turn, before descending in the turn and impacting the water. The airplane’s groundspeed continued to increase, from about 70 knots at liftoff, to 100 knots at the height of the right climbing turn, to 146 knots at the end of the data. Review of airport surveillance video depicted the airplane’s takeoff, initial climb, and turn toward an area of dark open water underneath a scattered cloud layer. Based on the dark night conditions and the lack of visual reference at the time of the accident, it is likely that the pilot became spatially disoriented, which led to the subsequent descent into water. Examination of the wreckage revealed a right-wing-low attitude at the time of the impact, which was consistent with the pilot maintaining the right turn seen in the surveillance video recordings. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or abnormalities that would have precluded normal operation. The pilot held an instrument rating, but no logbook information was available from which to determine his level of instrument currency or proficiency. According to medical certification files, the pilot had several eye disorders including chronic macular edema in his right eye and bilateral glaucoma; both conditions restrict visual fields. A year prior to the accident, the pilot had successfully completed a medical flight test and had been granted a statement of demonstration ability (SODA) by the Federal Aviation Administration for his right visual field defect. The medical flight test included, among other abilities, demonstrating the ability to judge distances and to recognize landmarks and the ability to read instrument panels quickly and correctly. The medical flight test is administered during daytime hours; in this accident, the pilot departed the airport under night visual conditions and then flew over the ocean which would have few visual cues. It is therefore unknown how well this pilot could respond under dark conditions. The challenge with a constricted visual field is not generally the speed to execute the visual scan, but the time to process the visual information. Given the lack of information from no nighttime vision testing as part of his SODA and insufficient information on the pilot’s instrument flight capabilities, the investigation was unable to determine what role, if any, the pilot’s vision restrictions contributed to this accident.

Probable cause

The pilot's failure to maintain a positive climb rate after takeoff due to spatial disorientation, which resulted in the airplane’s descent into water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA266
Event ID
20190908X05518
Case number
ERA19FA266
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, cause areas. 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: 749566402066a4e4f8b92604985fc61e75658bb681860abf42ffb79c162e6be1; retrieved 2026-09-15T07:05:04.445Z.