WPR20CA269 · Cessna 182 N
Cessna 182 N · Accident: landing area overshoot
From Johnson Creek Airport (3U2) to Sulphur Creek Ranch Airport (ID74)
Event
- NTSB case
- WPR20CA269
- 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 182 N
- 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
- N92403
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Johnson Creek Airport (3U2), Johnson Creek, IDTo Sulphur Creek Ranch Airport (ID74), Cascade, ID
- Aircraft age
- About 51 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
- Landing
- 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
- Personnel issues › Action/decision
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 reported that while on final approach to the runway, the airplane was too high. He initiated a slip to lose altitude, but the airplane was still too fast and high. After landing, the airplane collided with trees at the end of the ruwnay. The pilot further reported that the accident could have been prevented by initiating a go around sooner.
Two witnesses reported that the airplane landed hard more than halfway down the runway and began to porpoise. With about 800 ft of runway remaining, they heard the pilot apply full engine power. The airplane subsequently departed the runway surface and impacted trees. A post impact fire ensured which substantially damaged the airplane.
The pilot reported that there were no mechanical failures or malfunctions with the airplane or engine that would have precluded normal operation.
Probable cause
The pilot's decision to continue the unstable approach which resulted in an inadequate flare, bounced landing and collision with trees following a delayed go around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA269
- Event ID
- 20200813X63110
- Case number
- WPR20CA269
- 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: eae4208fcda6504cc27e8568e55fc6408f2c33812919894a672e3489eadfd495; retrieved 2026-09-16T12:33:22.469Z.