ATL95LA037 · Cessna P210R
Cessna P210R · Accident: in flight collision with object on approach
From 29J · Rock Hill, SC to Lumberton Regional Airport (LBT)
Event
- NTSB case
- ATL95LA037
- 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 P210R
- 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
- N5464A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 29J · Rock Hill, SCTo Lumberton Regional Airport (LBT)
- 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 · VFR pattern base
- 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 object
- 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
- Utility pole
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE 73-YEAR-OLD COMMERCIAL PILOT HAD REPORTED ON UNICOM THAT HE WAS LANDING ON RUNWAY 13. NO SUBSEQUENT COMMUNICATIONS WERE HEARD. THE AIRCRAFT WAS OBSERVED ON A LEFT BASE LEG FOR RUNWAY 13, BUT DID NOT TURN ONTO FINAL. THE AIRCRAFT CONTINUED DESCENDING, AND CONTACTED A UTILITY POLE, SOME BUILDINGS, AND SOME VEHICLES BEFORE COMING TO REST INVERTED. THE LANDING GEAR WERE FOUND EXTENDED; THE FLAPS WERE FOUND RETRACTED. THE PROPELLER BLADES SHOWED EVIDENCE OF POWER AT IMPACT. EXAMINATION OF THE AIRFRAME AND POWERPLANT DID NOT REVEAL EVIDENCE OF A MECHANICAL MALFUNCTION OR FAILURE. THE PILOT COULD NOT RECALL THE EVENTS SURROUNDING THE ACCIDENT.
Probable cause
THE FAILURE OF THE PILOT TO MAINTAIN AIRCRAFT CONTROL DURING THE APPROACH FOR LANDING, RESULTING IN A COLLISION WITH OBJECTS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL95LA037
- Event ID
- 20001207X02820
- Case number
- ATL95LA037
- 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: 3d1d6f5f408aff467e3c40e1deaebd8cecc683b208f70c9bcb1b0438a9b2b986; retrieved 2026-09-21T13:27:50.898Z.