WPR14CA314 · Cessna 182Q Q
Cessna 182Q Q · Accident while taxiing
From Warren USFS Airport (3U1) to Dixie US Forest Service Airport (A05)
Event
- NTSB case
- WPR14CA314
- 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 182Q Q
- Aircraft type
- Cessna 182
- 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
- N624M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Warren USFS Airport (3U1), Warren, IDTo Dixie US Forest Service Airport (A05), Dixie, ID
- Aircraft age
- About 36 years (built 1978)
- 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
- Taxi · into takeoff position
- 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
- Miscellaneous/other
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot/owner planned to fly to at least two back country airports in a neighboring state. His first destination was an unpaved United States Forest Service strip. The runway, designated 11/29, was reported to be 2,765 feet long and 50 feet wide. It was located in a narrow valley, and situated about 30 feet southwest of the main road that transited the valley. An unpaved road exited the main road immediately southeast of the threshold of runway 29, and then turned northwest to initially merge with the runway. About 300 feet northwest of the threshold, the unpaved road diverged slightly southwest of the runway, before assuming a track separate from but parallel to the runway. The pilot landed uneventfully on runway 11, and since the wind was calm, planned to depart from runway 29. He taxied to the end, turned around, and idled for a few minutes while reviewing the next flight leg. He then began his takeoff roll on what he believed to be runway 29, and at some point the left main tire struck a hole. The airplane veered to the left, and the left wingtip struck trees. This resulted in the pilot's inability to maintain directional control. The airplane veered further left, struck additional trees, and came to rest oriented about 90 degrees from the runway heading. The wings and fuselage sustained substantial damage, but the pilot was uninjured. Subsequent to the accident, the pilot recognized that he had inadvertently tracked the unpaved road instead of the runway for the takeoff attempt. Review of photographs of the runway environment indicated that the conjoined runway and road was conducive to such confusion. Commercial and Federal Aviation Administration documents contained a notation that the road crossed the runway about 800 feet from the threshold of runway 11, but the documents did not contain any information regarding the conjoining of the road and runway at the threshold of runway 29, or any remarks regarding the potential for confusion of the two. Subsequent to the accident, the Idaho Transportation Department added a cautionary note regarding the road to its Airport Facility Directory.
Probable cause
The pilot's attempt to depart on an unpaved road, which he mistook for the unpaved runway. Contributing to the accident was the fact that the road and the runway were conjoined for the first few hundred feet of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA314
- Event ID
- 20140726X52235
- Case number
- WPR14CA314
- 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: 56f4c61da7ead47e1f12f41dbb1f7a6c7dc64171b89adba8c1a131b33253030a; retrieved 2026-09-16T00:59:55.014Z.