WPR12CA169 · Cessna 182G
Cessna 182G · Accident: runway excursion during landing
From KS2P · Santa Paula, CA to KE36 · Georgetown, CA
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
- WPR12CA169
- 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 182G
- 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
- N3272S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From KS2P · Santa Paula, CATo KE36 · Georgetown, CA
- 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
- Runway excursion
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he flew over the airport and observed the windsock favoring runway 16 with a 5- to 8-knot crosswind. He made the landing approach with the right wing down, and had good directional control. The airplane was in the flare when it encountered two wind gusts that lifted the airplane and caused it to land hard twice. Upon the second hard landing, the nose pitched down and the airplane veered to the left, off the runway, over a taxiway, and impacted a hangar nose first. The pilot expressed concerns that the pilot's seat may have slid back during the landing. The seat and seat rails were in compliance with applicable airworthiness directives and were properly functioning. The right wing and fuselage were substantially damaged.
Probable cause
The pilot’s failure to maintain control of the airplane while landing with a gusting wind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12CA169
- Event ID
- 20120417X02303
- Case number
- WPR12CA169
- 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: bf756c91a8d01ba6473180bfb8957d14e7e92c6a832c4ebc33136e1db872bfe5; retrieved 2026-09-15T17:47:22.981Z.