SEA04LA117 · Cessna 185F
Cessna 185F · Accident: airframe, component or system failure during landing
From an unrecorded airport to Bozeman Yellowstone International Airport (BZN)
Event
- NTSB case
- SEA04LA117
- 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 185F
- Aircraft type
- Cessna 185
- 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
- N4585F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Bozeman Yellowstone International Airport (BZN), Bozeman, MT
- 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
- Landing · landing roll
- 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 › Fractured
- Landing gear, normal brake system › Inoperative
- Pilot in command › Directional control, not possible
- Pilot in command › Ground loop/swerve, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the landing roll, the pilot was applying heavy braking in order to turn off the runway at taxiway Echo, when the aircraft suddenly and rapidly ground-looped to the left. An initial post-accident inspection of the aircraft revealed that the right main gear brake rotor assembly had torn lose from the wheel itself, rendering the right wheel brake totally inoperative. The wheel hub and brake disk assembly were shipped to the NTSB Materials Laboratory, where it was determined that the brake disk attachment flange failed in fatigue in the bend around the attachment flange. The brake disk showed a substantial amount of general corrosion, and although the attachment flange met the minimum thickness requirements, most of its surface was covered by corrosion and corrosion pitting. The fatigue crack propagation that eventually lead to the failure had originated in one of these corrosion pits.
Probable cause
The failure of the right main gear brake disk attach flange during the landing roll, due to fatigue cracks emanating from numerous corrosion pits present on the surface of the disk, leading to the right brake becoming totally inoperative, and resulting in a rapid inadvertent ground-loop. Factors include hard braking applied by the pilot in order to turn off the active runway at an early taxiway, and considerable corrosion on the surface of the brake disk flange.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04LA117
- Event ID
- 20040702X00902
- Case number
- SEA04LA117
- 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: 51c632528d8c4e4b32b2babd4959b09e6fd2097f19cc1829181bea8d61f66dcc; retrieved 2026-09-22T07:15:28.811Z.