ANC24LA040 · Cessna 180H
Cessna 180H · Accident: collision during takeoff/landing
From an unrecorded airport to ALH · Anchorage, AK
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
- ANC24LA040
- 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 180H
- 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
- N91224
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From not recordedTo ALH · Anchorage, AK
- Aircraft age
- About 55 years (built 1969)
- 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
- 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
- Collision during takeoff/landing
- 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
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while on takeoff roll from a gravel airstrip, the airplane’s left main wheel struck a pile of gravel, resulting in a nose over. The airplane sustained substantial damage to the wings, horizontal stabilizer, and rudder. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operations. The pilot added that flat light conditions, coupled with the gray silt ladened gravel, contributed to him not seeing the obstacle on the airstrip.
Probable cause
The pilot’s failure to recognize and avoid an obstacle on the runway environment during takeoff roll. Contributing was flat light conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC24LA040
- Event ID
- 20240603194374
- Case number
- ANC24LA040
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-06-01.
- API snapshot SHA-256: 49709cc40923b8b4c6d546d6abb5115a3320321d927a399c724dd3eb09b0b9cc; retrieved 2026-09-16T18:50:19.997Z.