ATL04LA059 · SOCATA TB21
SOCATA TB21 · Accident: hard landing
From M33 · Gallatin, TN to Avery County Morrison Field (7A8)
Event
- NTSB case
- ATL04LA059
- 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
- 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
SOCATA TB21
- Aircraft type
- Socata TB21
- 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
- N1879S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From M33 · Gallatin, TNTo Avery County Morrison Field (7A8), Spruce Pine, 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
- Landing
- 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
- Substantial
Cause areas
- Pilot in command › Directional control, not maintained
- Pilot in command › Flare, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated he entered left traffic for runway 34, and he noticed a reduction in airspeed as the airplane crossed over a hill. He increased power and the airplane developed an excessive sink rate. The pilot added power; the airplane touched down on the runway, and bounced back into the air. The airplane touched down again and went off the left side of the runway, down an embankment, and the left wing collided with a tree. Witnesses located on the airport who observed the accident stated the winds were one to three knots. Another witness located adjacent to the airport stated the winds were calm. The pilot stated he did not encounter any mechanical problems.
Probable cause
The pilot's inadequate flare, and his failure to maintain directional control. The pilot's improper recovery from a bounced landing, and trees are a contributing factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA059
- Event ID
- 20040105X00006
- Case number
- ATL04LA059
- 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, coordinates. 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: d1ae5abfbb839667bbcda9ab816871f554b9e92c9e35341878b34bbe0095a075; retrieved 2026-09-22T08:03:09.044Z.