Cessna 172 accident near Yucca Valley, California, November 21, 2009
On November 21, 2009 at about 5:30 pm local time, a Cessna 172, registered N8504B, was substantially damaged in an accident during landing (flare/touchdown) near Yucca Valley, California (Valley Vista Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's inadequate compensation for the crosswind gusts and failure to maintain directional control of the airplane.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 21, 2009 · about 5:30 pm local time
- Place
- Yucca Valley, California · Valley Vista Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 · all 172s on the register
- Registration
- N8504B · no longer on the register · serial 36204
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was landing in a crosswind when a gust of wind coming between hangars caused the airplane to veer away from the wind and off the runway. The pilot applied full power in an attempt to execute a go-around, but subsequently impacted terrain and nosed over. The pilot said there were no preimpact mechanical malfunctions or failures.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control on ground during landing (flare/touchdown) defining event
- Nose over/nose down during landing (flare/touchdown)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Response/compensation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 115 hours in all; 115 in this make and model; 3 in the last 90 days; 2 in the last 30 days
- Last flight review: December 4, 2008
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,552 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor O-300 SER (piston); 0 hours total
The flight
- Departed from: KTNP Twentynine Palm CA at 5:00 pm
- Destination: 6CA5 Yucca Valley CA
- Flight plan: none
- Runway 18, 3,000 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 240° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 48°F (9°C), dew point 18°F (-8°C)
- Altimeter: 29.98 inHg
- Observation at 6:09 pm from KL35
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.