ATL89LA032 · Beech 35-A33
Beech 35-A33 · Accident: airframe, component or system failure while standing
From 8A4 · Marietta, GA to 6A0 · Cartersville, GA
Event
- NTSB case
- ATL89LA032
- 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
Beech 35-A33
- Aircraft type
- Beechcraft 35
- 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
- N431T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 8A4 · Marietta, GATo 6A0 · Cartersville, 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
- Standing · engine(s) operating
- 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, line › Ruptured
- Landing gear, normal brake system › Failure, partial
- Pilot in command › Brakes(normal), improper use of
- Pilot in command › Throttle/power control, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING PREFLT 'RUN-UP' AT THE END OF THE ACTIVE RWY, THE RIGHT BRAKE FAILED AND THE AIRPLANE PIVOTED LEFT WHILE THE ENGINE WAS AT A HIGH POWER SETTING. THE PLT RPTED THAT THINGS HAPPENED SO FAST THAT HE MAY HAVE ADDED POWER WHILE ATTEMPTING TO REDUCE POWER. HE ALSO STATED THAT HE CONTINUED TO PRESS ON THE BRAKE PEDALS CAUSING THE ACFT TO TURN TO THE LEFT TOWARDS A STEEP BANK. THE ACFT ROLLED APPROX 200 FT AND OVERTURNED ON THE SIDE OF AN EMBANKMENT. INVESTIGATION REVEALED THAT THE RIGHT BRAKE HOSE HAD RUPTURED AT THE CALIPER WHICH CAUSED THE LOSS OF RIGHT BRAKE FLUID/PRESSURE. THE BRAKE HOSE WAS ORIGINAL EQUIPMENT, 28 YEARS OLD. AN ANNUAL INSPECTION WAS PERFORMED 5 MONTHS PRIOR TO THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL89LA032
- Event ID
- 20001213X27196
- Case number
- ATL89LA032
- 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: d2e6f405e7806eae22bcb2596ae9c1eaf54c35784f5e302564a37857e8b8f5b0; retrieved 2026-09-22T00:20:48.259Z.