ERA21LA214 · Cessna 172
Cessna 172 · Accident: landing area overshoot
From Greeneville Municipal Airport (GCY) to an unrecorded destination
Event
- NTSB case
- ERA21LA214
- 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
- Event fatalities
- Unknown
- 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
Cessna 172
- Aircraft type
- Cessna 172
- 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
- N6344E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greeneville Municipal Airport (GCY), Greeneville, TNTo not recorded
- Aircraft age
- About 62 years (built 1959)
- 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
- Defining eventThe 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
- Landing area overshoot
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot was returning to his home airport from a cross-country solo flight. The winds were favoring the opposite direction runway, and he touched down “a little fast” with 20º of flaps extended about 1,000 feet down the 3,000-foot-long runway. He applied the brakes and the airplane veered to the right (he thought the left brake had failed). He then shut off the carburetor heat, retracted the flaps, and added power to abort the landing with about 300 feet of pavement remaining. He was able to get airborne before the end of the runway but was in ground effect. The airplane flew over a road, impacted a tree with the right wing while airborne, hit a truck, and the corner of a detached garage. The airplane then rolled a short distance, nosed over, and came to rest. The airplane’s fuselage, wings, and empennage were substantially damaged during the accident sequence. Postaccident testing revealed that both the left and right wheel brakes were functional.
Probable cause
The student pilot’s excessive airspeed during the landing approach and his delayed remedial action, which resulted in the airplane striking obstacles during an aborted landing. Contributing was the pilot’s decision to land with a tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA214
- Event ID
- 20210513103078
- Case number
- ERA21LA214
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: defb0dca9f711ad6ee8a12906d711bb4abcbb2c48263a6a54c8f2e0e7f6cd9c6; retrieved 2026-09-16T14:02:29.777Z.