SEA08LA110 · Cessna 180
Cessna 180 · Accident: aircraft structural failure during landing
From Eagle City, UT to Blanding Municipal Airport (KBDG)
Event
- NTSB case
- SEA08LA110
- 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 180
- Aircraft type
- Cessna 180
- 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
- N180XP
- Operator
- Berge Christian F
- Onboard fatalities
- Unknown
- Route
- From Eagle City, UTTo Blanding Municipal Airport (KBDG), Blanding, UT
- 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
- Defining eventThe 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
- Aircraft structural 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
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the landing roll, the pilot began to apply right rudder and right brake in order to compensate for the airplane turning to the left. During that sequence, the right main landing gear leg separated from the airframe at the point where it protrudes from the fuselage. The airplane then slid off the runway onto the surrounding soft terrain. An inspection of the gear leg by the NTSB Materials Laboratory determined that the metallurgical features discovered on the right main landing gear leg were consistent with separation due to a fatigue fracture that had initiated in a corrosion pit under a gear leg clamping mechanism. In addition to the fatigue region at the origin area, three smaller fatigue regions were detected within the shear lip of the fracture.
Probable cause
The fatigue failure of the right main landing gear leg during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08LA110
- Event ID
- 20080428X00560
- Case number
- SEA08LA110
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: a97df391d18227cf1363837bf65002346b8850ea7ea04e809e998237dc97c099; retrieved 2026-09-15T09:35:02.789Z.