ANC25LA009 · Cessna 180
Cessna 180 · Accident: system/component malfunction/failure (non-power) during landing
From King Salmon, AK (private airstrip) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ANC25LA009
- 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
- Event fatalities
- Unknown
- 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
- N9140R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From King Salmon, AK (private airstrip)To not recorded
- Aircraft age
- About 71 years (built 1953)
- 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
- System/component malfunction/failure (non-power)
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that, during the landing roll on a remote, gravel-covered beach, the right main landing gear leg broke just above the wheel axle. The remaining gear leg dug into the frozen gravel and folded under the fuselage, and the airplane veered right, resulting in substantial damage to the fuselage and the right wing. A postaccident examination by the pilot revealed that the right main landing gear leg fractured a few inches above the axle. The fractured landing gear leg was ground into the gravel-covered surface before the main landing gear leg folded aft, which obliterated the fracture surface. The separated right wheel assembly traveled into the lake and was not recovered; therefore, the failure mode of the landing gear leg could not be determined. The pilot stated that the main landing gear legs were last inspected for cracks about 15 years before the accident.
Probable cause
A failure of the right main landing gear leg for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC25LA009
- Event ID
- 20241203195574
- Case number
- ANC25LA009
- 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, coordinates, cause areas. 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: 6ff3774d62393d63f4c81e093afc49a809661e42b68110684204e8008d44c866; retrieved 2026-09-16T19:31:03.351Z.