WPR12CA268 · Cessna 182P
Cessna 182P · Accident: abnormal runway contact during landing
From Franklin Field (F72) to Watts Woodland Airport (O41)
Event
- NTSB case
- WPR12CA268
- 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 182P
- 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
- N7437Q
- Operator
- Brent Noble
- Onboard fatalities
- Unknown
- Route
- From Franklin Field (F72), Franklin, CATo Watts Woodland Airport (O41), Woodland, 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 · flare/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
- Abnormal runway contact
- 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was returning from a local area flight. After determining that the wind was calm, the pilot elected to conduct a straight-in approach. During the descent to the runway, the pilot realized that the airplane was higher than appropriate and extended the flaps to 40 degrees. He continued the approach and, when the airplane touched down hard on the runway, it bounced about 5 feet back into the air. The pilot decided to abort the landing rather than continue bouncing down the runway. The pilot added full power and retracted the flaps to 0 degrees. The airplane’s right wing rose and the left wing impacted the surface. According to the Cessna pilot’s operating handbook, during a balked landing, the flaps should be retracted to 20 degrees after full power is applied, and then retracted slowly after the airplane reaches 80 miles per hour. Postaccident examination revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilot's failure to maintain a proper descent path during the approach to land, which resulted in a hard, bounced landing, and his improper retraction of the flaps during the subsequent attempted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12CA268
- Event ID
- 20120618X91331
- Case number
- WPR12CA268
- 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: 8f05b03a7bb19186ec1f0c788d8092d50b430bb8a9c85c26d0848ebe5fb24ec4; retrieved 2026-09-15T18:33:34.991Z.