WPR11CA259 · Cessna 172P
Cessna 172P · Accident: runway excursion during landing
From Madera Municipal Airport (KMAE) to Palo Alto Airport (KPAO)
Event
- NTSB case
- WPR11CA259
- 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 172P
- Aircraft type
- Cessna 172
- 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
- N9849L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Madera Municipal Airport (KMAE), Madera, CATo Palo Alto Airport (KPAO), Palo Alto, 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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported that during his descent to land, he observed the windsock and made a mental note to maintain aileron correction for the crosswind. As the airplane reached about 35-40 feet above the runway, the pilot reduced power to idle and at an altitude of 2 feet he initiated the landing flare. The stall warning horn sounded and the nose of the airplane started to veer to the left. After the airplane touched down, the pilot applied right rudder and the airplane started to veer off to the right. The airplane exited the right side of the runway and struck a pipe that was protruding from the ground, substantially damaging the nose gear and firewall. The pilot reported no mechanical failures or malfunctions with the airframe or engine that would have precluded normal flight.
Probable cause
The pilot's failure to maintain directional control during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11CA259
- Event ID
- 20110613X24238
- Case number
- WPR11CA259
- 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: 02590630c83b8722b1dac61135cd6bbe22398866ddcce39b094875fd8d7a8856; retrieved 2026-09-15T16:16:46.457Z.