FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13CA086 · Cessna 172P

13 Dec 2012 · Murfreesboro, TN, United States

Cessna 172P · Accident: abrupt maneuver during takeoff

From City of Murfreesboro Airport (MBT) to City of Murfreesboro Airport (MBT)

Report a problem

Event

NTSB case
ERA13CA086
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 172P

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
N54500
Operator
James K. Gardner · private individual
Onboard fatalities
Unknown
Route
From City of Murfreesboro Airport (MBT), Murfreesboro, TNTo City of Murfreesboro Airport (MBT), Murfreesboro, 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
Takeoff
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
Abrupt maneuver
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
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot stated that during the practice soft field takeoff, he pulled the yoke back and applied full power. The airplane veered left and skidded off the runway where the propeller struck a concrete culvert. The skid continued across the grass and the airplane came to rest in a drainage area. Postaccident examination revealed substantial damage to the wings, firewall, and fuselage. The student pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The student pilot’s failure to maintain directional control during takeoff, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13CA086
Event ID
20121214X94004
Case number
ERA13CA086
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. 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: 55977a7506eaf781d7f6e1dffaac9b462f3682bf8d2ff065ff08f80dae326f09; retrieved 2026-09-15T20:35:43.473Z.