Cessna 172S accident near Branscomb, California, November 1, 2010
On November 1, 2010, a Cessna 172S, registered N3542V, was substantially damaged in an accident during landing (landing roll) near Branscomb, California (Private Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain clearance from trees during the landing roll on an unimproved airstrip.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 1, 2010
- Place
- Branscomb, California · Private Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S · all 172Ss on the register
- Registration
- N3542V · no longer on the register · serial 172S8906
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that during the landing roll on a sloped dirt airstrip, the airplane approached a slight incline. As he began slowing the airplane, the right wingtip stuck a tree adjacent to the runway and the airplane immediately yawed 90-degrees to the right. The airplane departed the runway surface area, traveled down a small embankment, and impacted a group of small trees, which resulted in structural damage to both wings and engine firewall. The pilot reported that there were no preimpact mechanical malfunctions with the airplane.
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
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll) defining event
- Loss of control on ground during landing (landing roll)
- Runway excursion during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Response/compensation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 75 hours in all; 69 in this make and model; 31 in the last 90 days; 10 in the last 30 days; 19 as pilot in command
- Last flight review: October 22, 2010
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,183 hours
- Last inspection: annual inspection, October 4, 2010
- Maximum gross weight: 2,500 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
The flight
- Departed from: UKI Ukiah CA
- Destination: PVT Branscomb CA
- Flight plan: none
- Runway 03, 3,000 ft by 50 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: overcast at 8,000 ft; ovct at 8,000 ft
- Temperature: 61°F (16°C), dew point 50°F (10°C)
- Altimeter: 30.20 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
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.