ATL96LA077 · Cessna 210M
Cessna 210M · Accident: overrun during landing
From Fort Lauderdale Executive Airport (FXE) to Everglades Airpark (X01)
Event
- NTSB case
- ATL96LA077
- 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
- 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
- Visual 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
- N700RP
- Operator
- John E. Toale · private individual
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Executive Airport (FXE), FT. LAUDERDALE, FLTo Everglades Airpark (X01)
- 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
- Landing · landing roll
- 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
- Overrun
- 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 › Distance/speed, misjudged
Approximate · Estimated position: the centre of Everglades City, FL, the place the record names. Not the accident site.
NTSB narrative
According to the pilot, the airplane touched down 1000 feet down the 2400-foot long runway. The airplane rolled off the end of the runway into the grass, and came to rest in the water. During the examination of the runway, there was a 472-foot black skid mark observed leading to the left main landing gear on the runway; there was not a skid mark leading to the right main landing gear. It was observed that the left main tire was flat with a hole, indicating it had been worn from braking. The right tire was fully inflated and showed no signs of excessive wear. There were indications of hydraulic fluid leakage on the right main gear leg at the pivot joint which allows movement of the gear leg during retraction. The pilot reported that recent brake maintenance had been performed on the airplane.
Probable cause
the pilot's excessive airspeed and misjudgment of the landing distance. A factor was the right brake not working due to a hydraulic leak.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL96LA077
- Event ID
- 20001208X05514
- Case number
- ATL96LA077
- 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: db4d0c2140e62c081b1c63507cc8daf4c873068da6900daf6ba59071502ad71a; retrieved 2026-09-22T22:39:53.162Z.