ATL84FA005 · Cessna T210F
Cessna T210F · Accident: hard landing
Event
- NTSB case
- ATL84FA005
- 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 T210F
- 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
- N3006R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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 › Directional control, not maintained
- Pilot in command › Ground loop/swerve, not corrected
- Pilot in command › Lack of total experience in kind of aircraft
- Pilot in command › Procedures/directives, not followed
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT CRASHED DURING AN ATTEMPTED GO-AROUND AFTER A HARD LANDING ON A 1200 FT PRIVATE STRIP IN MOUNTAINOUS TERRAIN. THE TWO PILOTS HAD LANDED AT THIS ARPT IN LANDINGS DESCRIBED AS FAST. THEN TWO PASSENGERS WERE INVITED TO RIDE ALONG ONE MORE LANDING WAS COMPLETED ALTHOUGH ONE WITNESS SAID THEY ALMOST NOSED THE PROPELLER INTO THE GROUND DURING HARD BRAKING. ALL LANDINGS WERE FULL STOP SINCE TAKEOFF WAS IN THE OPPOSITE DIRECTION BECAUSE OF THE TERRAIN. THE PILOT ON THE LAST LANDING ATTEMPTED A GO-AROUND AFTER LANDING AND THE ACRT VEERED LEFT AND THE LEFT WING CONTACTED THE GROUND. THE ACFT CARTWHEELED AND WENT BACKWARDS INTO AN EMBANKMENT. BOTH WITNESSES REPORTED THAT THE ENGINE WAS RUNNING SMOOTHLYAFTER THE BOUNCED LANDING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL84FA005
- Event ID
- 20001214X44723
- Case number
- ATL84FA005
- 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: ce10a7574b9a1e56295c8d1cdfbe8c8a9812458821f4ceada74befe75beda9df; retrieved 2026-09-21T17:46:33.551Z.