LAX08CA245 · Cessna 180
Cessna 180 · Accident: landing area overshoot
From Garden Valley Airport (U88) to Graham US Forest Service Airport (U45)
Event
- NTSB case
- LAX08CA245
- 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
- N2294C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Garden Valley Airport (U88), Garden Valley, IDTo Graham US Forest Service Airport (U45), Atlanta, ID
- 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
- Landing area overshoot
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The plot landed on the last half of the 2,900-foot-long grass runway and was unable to bring the airplane to a stop before it ran off the end of the runway and into trees. Prior to going to the airport, the pilot had spoken with local area pilots who indicated that he should not use the first half of the runway because it was muddy and soft. The pilot indicated that the airplane and engine had no mechanical failures or malfunctions during the flight. The Federal Aviation Administration Airport/Facility Directory for the airport states in part, " that the lower 1/3 of the runway is soft and unusable during the early spring. " The performance section landing distance charts of the Cessna 180 Owners Manual listed a total landing distance of 1,842 over a 50-foot obstacle, with a 847-foot ground roll (chart correction factors applied for grass runway surface and no wind).
Probable cause
The pilot's misjudged speed and distance during the intentional touchdown in the last half of the runway, which resulted in a landing overrun. Contributing to the accident was the muddy runway condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA245
- Event ID
- 20080807X01177
- Case number
- LAX08CA245
- 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. 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: 6581a95b416eba6131ffb165e5658f5480f3f547f6928a3dfe65d2a723e5b4c4; retrieved 2026-09-15T10:00:18.649Z.