WPR20CA041 · Cessna 182 P
Cessna 182 P · Accident: collision during takeoff/landing
From Pearson Field (VUO) to Grove Field (1W1)
Event
- NTSB case
- WPR20CA041
- 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 P
- 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
- N52458
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pearson Field (VUO), Vancouver, WATo Grove Field (1W1), Camas, WA
- Aircraft age
- About 46 years (built 1973)
- 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 · aborted after touchdown
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, with the student pilot on the controls for the landing, the airplane floated and eventually touched down about "the first third of the runway." The airplane bounced, and the instructor announced that he was assuming control of the airplane. The instructor simultaneously attempted to apply full throttle by pushing the student's hand, which was still on the throttle and prevented him from achieving full power as he attempted to gain altitude without stalling the airplane. The airplane subsequently struck a fence near the departure end of the runway, so the instructor reduced power and executed a forced landing to an open field. The airplane sustained substantial damage to the left horizontal stabilizer. The instructor reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that he should have assumed control of the airplane sooner.
Probable cause
The student pilot's improper landing flare, which resulted in a bounced landing, and the flight instructor’s delayed remedial action and the student’s failure to relinquish control, which resulted in a runway overrun and impact with a fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20CA041
- Event ID
- 20191206X45310
- Case number
- WPR20CA041
- 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: 62708875190558ece53816ac285bf091afab6bf760d0ed862d73d51a715f1bbf; retrieved 2026-09-16T10:44:21.327Z.