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

Piper PA-28-235 accident near San Carlos, California, March 28, 2009

On March 28, 2009 at about 5:50 pm local time, a Piper PA-28-235, registered N9249W, was substantially damaged in an accident during initial climb near San Carlos, California (San Carlos airport). It was a personal flight under general aviation rules (Part 91). 4 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power during the initial climb for undetermined reasons.

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

What the record shows

Date
March 28, 2009 · about 5:50 pm local time
Place
San Carlos, California · San Carlos · map
Type
Accident
Injuries
4 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-235 · all PA-28-235s on the register
Registration
N9249W · no longer on the register · serial 28-10920
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot had just departed on a local visual flight rules (VFR) flight when the airplane's engine suddenly lost all power as it was about 100 to 150 feet above ground level. Because of the airplane's low altitude, once the pilot checked the position of the magnetos, fuel selector, and fuel pump, he focused his attention on finding a landing spot in the nearby rough swampy terrain. During the landing, the airplane's wings and fuselage sustained substantial damage. A post-accident teardown inspection of the airframe, fuel system, air induction system, and the engine did not find any evidence of pre-accident anomalies or malfunctions.

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. Loss of engine power (total) during initial climb defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • Environmental issues › Physical environment › Terrain › Rough terrain › Contributed to outcome
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 847 hours in all; 154 in this make and model; 7 in the last 90 days; 2 in the last 30 days; 789 as pilot in command
  • Last flight review: July 23, 2008
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 6,430 hours
  • Last inspection: annual inspection, July 1, 2008
  • Maximum gross weight: 2,900 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-540 SERIES (piston); 0 hours total

The flight

  • Departed from: KSQL San Carlos CA at 5:49 pm
  • Destination: KSQL San Carlos CA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 55°F (13°C)
  • Altimeter: 30.00 inHg

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

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.