The U.S. aircraft register, updated daily
Accidents · NTSB WPR10CA267 · Final report

Piper PA-28-181 accident near Palo Alto, California, May 29, 2010

On May 29, 2010, a Piper PA-28-181, registered N2865M, was substantially damaged in an accident during approach (VFR pattern final) near Palo Alto, California (Palo Alto Airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power on final approach due to fuel starvation as a result of the pilot's inadequate fuel management.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 29, 2010 · cases in 2010
Place
Palo Alto, California · Palo Alto Airport · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-181 · all PA-28-181s on the register
Registration
N2865M · no longer on the register · serial 28-7890274
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot stated that prior to departing on a cross-country flight the "airplane was topped [off with fuel] prior to the flight." Before the return trip the pilot visually checked the fuel level in the tanks and estimated that the right tank had 10 gallons and the left had 12 gallons of fuel. The pilot reported that while on final approach to the destination airport the "engine began to sputter" and lost power. He attempted to perform an engine restart, including switching the fuel selector to another tank, but was unsuccessful. The airplane subsequently impacted terrain short of the runway resulting in substantial damage to the right wing and firewall. In a verbal statement the pilot said that he "suspected a fuel management issue." An FAA inspector examined the airplane and found that the right fuel tank was empty and the left tank had approximately 3.5 gallons of fuel. According to the FAA inspector the fuel tanks were still intact and there was no evidence of a fuel leak.

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

  1. Fuel starvation during approach (VFR pattern final) defining event
  2. Loss of engine power (total) during approach (VFR pattern final)
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level other cases naming the fuel system
  • cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 105 hours in all; 10 in this make and model; 35 in the last 90 days; 6 in the last 30 days; 28 as pilot in command
  • Last flight review: March 26, 2010
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 8,020 hours
  • Last inspection: 100-hour inspection, January 15, 2010
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4M (piston); 0 hours total

The flight

  • Departed from: KRDD Redding CA at 10:45 pm
  • Destination: KPAO Palo Alto CA
  • Flight plan: none
  • Runway 31, 2,443 ft by 70 ft

Weather at the time

  • Light: daylight
  • Wind: from 310° at 12 knots
  • Visibility: 30 statute miles
  • Sky: scat at 4,000 ft
  • Temperature: 68°F (20°C), dew point 0°F (-18°C)
  • Altimeter: 30.17 inHg
  • Observation at 11:50 pm from KPAO

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on July 14, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR10CA267.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.