ATL04LA065 · Aero Commander 500
Aero Commander 500 · Accident: airframe, component or system failure during takeoff
From 88J · Allendale, SC to 88J · Allendale, SC
Event
- NTSB case
- ATL04LA065
- 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
Aero Commander 500
- Aircraft type
- Aero Commander 500
- 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
- N800SL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 88J · Allendale, SCTo 88J · Allendale, SC
- 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 · roll/run
- 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
- Hydraulic system, accumulator › Failure
- Landing gear, normal brake system
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, while on takeoff roll the airplane began to "track right", differential braking input was applied to line up the airplane with the runway center line. When brakes were applied to stop the airplane, they failed and the airplane veered off the left side of the runway into a ditch. Examination of the wheel brakes revealed that the hydraulic pucks were leaking, and the brake disc and linings were worn. Examination of the accumulator revealed the diaphragm was ruptured and the system would not maintain pressure. No other flight control or mechanical problems were reported by the pilot.
Probable cause
The failure of the hydraulic brake system accumulator due to a ruptured diaphragm. A factor was the ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA065
- Event ID
- 20040112X00049
- Case number
- ATL04LA065
- 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: 152df3ef4a8cea53cd1fc89608063df579bfbd90d8e7ae7c27c7f555245ccf70; retrieved 2026-09-22T08:01:53.965Z.