ATL90LA009 · Cessna 210
FMP Cessna 210 · Accident: in flight encounter with weather on approach
From Addison, TX to Piedmont Triad International Airport (GSO)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL90LA009
- 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
- Instrument Meteorological Cond
Cessna 210
- 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
- N1155M
- Operator
- FMP
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Addison, TXTo Piedmont Triad International Airport (GSO), Elkin, NC
- 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
- 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 encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel consumption calculations, improper
- Pilot in command › Fuel supply, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT HAD PLANNED A 5 HR FLT TO ELKIN, NC. HE ESTD THE ACFT HAD 6.5 HRS OF FUEL ON BOARD. AT ELKIN, HE ATTEMPTED TO LAND FROM AN NDB APCH, BUT MADE A MISSED APCH & DIVERTED TO GREENSBORO, NC. HE OBTAINED VECTORS FOR AN ILS 5 APCH AT GREENSBORO, BUT THE ENG BEGAN LOSING POWER FROM FUEL EXHAUSTION ABOUT 8 MI FROM THE ARPT. SUBSEQUENTLY, IT CRASHED INTO TREES DURING A FORCED LANDING AFTER ABOUT 5.5 HRS OF FLT.
Probable cause
IMPROPER FUEL CONSUMPTION CALCULATIONS BY THE PILOT, WHICH RESULTED IN FUEL EXHAUSTION FROM LACK OF FUEL. ADVERSE WEATHER CONDITIONS WERE RELATED TO THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90LA009
- Event ID
- 20001213X29531
- Case number
- ATL90LA009
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-10-19.
- API snapshot SHA-256: 5afe02c94fd9e8bb3fea3f42353b772e03c84b548070e55c4cceb155e8d674b6; retrieved 2026-09-23T07:03:16.106Z.