ATL89LA001 · Grumman AA-5A
Grumman AA-5A · Accident: airframe, component or system failure while taxiing
From an unrecorded airport to Southwest Georgia Regional Airport (ABY)
Event
- NTSB case
- ATL89LA001
- 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
- 0
- 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
Grumman AA-5A
- Aircraft type
- Grumman AA-5
- 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
- N26827
- Operator
- Ceronnie Robinson
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Southwest Georgia Regional Airport (ABY), Albany, 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 · to runway
- 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
- Landing gear, normal brake system › Chafed
- Landing gear, normal brake system › Corroded
- Landing gear, normal brake system › Leak
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT THE LEFT BRAKE FAILED TO FUNCTION DURING TAXI WHEN HE ATTEMPTED TO REDUCE SPEED AND TURN 180 DEG INTO T/O POSITION. THE AIRPLANE BEGAN TO TRACK TO THE RIGHT. HE RELEASED BRAKE PRESSURE ON BOTH PEDALS THINKING THAT HE MIGHT HAVE BEEN APPLYING PRESSURE TO THE RUDDER PEDAL INSTEAD OF THE BRAKE PEDAL. HE THEN REAPPLIED PRESSURE AND EXPERIENCED THE SAME RESULTS. AT THAT POINT, HE REDUCED THE POWER TO IDLE. THE AIRPLANE RAN OFF THE SIDE OF THE RWY. TRAVELED DOWN AN EMBANKMENT, AND FLIPPED OVER. EXAM OF THE ACFT REVEALED A HOLE IN THE LEFT BRAKE-SYSTEM PRESSURE LINE BEHIND THE CO-PLT BRAKE PEDALS. THE HOLE HAD RESULTED FROM CHAFING BETWEEN A MOUNTING CLAMP & THE LINE. THE LINE & CLAMP WERE PROPERLY INSTALLED. THE HOLE WAS NOT VISIBLE UNTIL THE CLAMP WAS REMOVED. CORROSION WAS ALSO NOTED ON THE LINE IN THE AREA OF THE HOLE. A SEARCH OF FAA SDR'S REVEALED NO REPORTS OF SIMILAR FAILURES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL89LA001
- Event ID
- 20001213X26977
- Case number
- ATL89LA001
- 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. 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: 040a091fae104b9c339711a896f5ae2298e62b8388d41504c39c882d3c6d9a23; retrieved 2026-09-22T00:23:21.961Z.