FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL07CA058 · Cessna 172K

22 Mar 2007 · Cornelia, GA, United States

Cessna 172K · Accident: airframe, component or system failure while taxiing

From Habersham County Airport (KAJR) to Habersham County Airport (KAJR)

Report a problem

Event

NTSB case
ATL07CA058
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 172K

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
N46567
Operator
Unknown
Onboard fatalities
Unknown
Route
From Habersham County Airport (KAJR), Cornelia, GATo Habersham County Airport (KAJR), Cornelia, GA
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
Taxi
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
Airframe, component or system failure
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

  • Company/operator management › Maintenance, service of aircraft/equipment, 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 airplane veered off a taxiway and collided with trees after landing. The certified flight instructor (CFI) stated he was conducting a training flight with a new student. A preflight inspection was completed and no anomalies were noted except for a low nose wheel tire which was corrected. They departed the airport and flew north of the airport and completed some air work before returning back to the airport to do some landings. The student pilot made a normal landing to runway 24. The CFI felt the student pilot apply some brakes and informed the student pilot to maintain directional control with the rudder only. The student pilot complied with his instructions, taxied the airplane to the end of runway 24, and turned left onto the taxiway. Another airplane was on the parallel to the runway 24 taxiway. The CFI instructed the student pilot to stop the airplane after clearing the runway. The airplane went further than the CFI wanted it to go and the CFI instructed the student pilot to apply brakes. The CFI applied brakes and the airplane would not stop. The CFI applied the emergency brake and the airplane would not stop. The CFI pulled the mixture to the cut off position and attempted to stop the airplane on the lip of the edge of the taxiway. The airplane did not stop and went down an embankment and collided with some trees. The registered owner and operator of the airplane informed the FAA that the brake system had been serviced a week before the accident by adding brake fluid to the brake system. Review of the airframe logbook revealed no entry had been entered into the logbook pertaining to the servicing of the brake system. A functional test of the brake system was performed by the FAA inspectors who tried to push the airplane with the parking brake engaged. In addition, one FAA inspector got in the airplane's left front seat and applied brakes and then in the right front seat and applied brakes as the other FAA pushed the airplane, and the airplane continued to move in each test. The brake pads and rotors were visually inspected and no anomalies were noted. Visual inspection of the master cylinder found that brake fluid was leaking onto the exterior of the master cylinder components, as evidenced by the staining of dried hydraulic fluid. The carpet near the pilot's (left front seat) rudder pedals were saturated with brake fluid and there were indications of some recently spilled brake fluid which had a reddish color. In addition, brake fluid stains that were brownish in color were observed.

Probable cause

The failure of the owner/operator to repair or replace a known leaking brake system components resulting in a total loss of brakes while taxing and an on-ground collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL07CA058
Event ID
20070522X00605
Case number
ATL07CA058
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: 6f2ba702b0675f7c02674fa70948561b154037346a0324942cb5bfe7bba0b0e3; retrieved 2026-09-22T03:57:56.626Z.