ERA10CA406 · Cessna 172 P
Hixson Aviation Cessna 172 P · Accident: collision with terrain/object (non-CFIT) during landing
From 1A0 · Chattanooga, TN to 1A0 · Chattanooga, TN
Event
- NTSB case
- ERA10CA406
- 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
Cessna 172 P
- 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
- N51745
- Operator
- Hixson Aviation
- Onboard fatalities
- Unknown
- Route
- From 1A0 · Chattanooga, TNTo 1A0 · Chattanooga, TN
- 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
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot stated that he and a passenger departed on a local flight to a tower-controlled airport, where he conducted five touch-and-go practice takeoff and landings and one full-stop landing. He then departed back to his home airport, where he conducted another touch-and-go landing. The student pilot stated that the approach for the second landing was fine but during the landing flare, he believed that he was approaching the end of the runway too fast. The student pilot decided to execute a go-around by increasing engine power and retracting the wing flaps. He stated that the airplane settled onto the runway and he attempted to apply brakes. The airplane veered off the left side of the runway and impacted a pole and a building, resulting in substantial damage to the engine firewall. The student pilot stated that there were no mechanical malfunctions or anomalies with the airplane.
Probable cause
The student pilot's improper execution of the go-around procedure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA406
- Event ID
- 20100808X42452
- Case number
- ERA10CA406
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-08-08.
- API snapshot SHA-256: 111a8bf3fd029d4bb74d43a2b7259b25bddd5e7af0a156b612135a1b7e147404; retrieved 2026-09-15T14:48:34.047Z.