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

Cessna 152 accident near Merced, California, August 31, 2009

On August 31, 2009 at about 10:00 pm local time, a Cessna 152, registered N5155B, was substantially damaged in an accident during landing (flare/touchdown) near Merced, California (Merced/Castle airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improper flare which resulted in a hard landing and subsequent collapse of the nose landing gear strut.

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

What the record shows

Date
August 31, 2009 · about 10:00 pm local time · cases in 2009
Place
Merced, California · Merced/Castle · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 152 · all 152s on the register
Registration
N5155B · no longer on the register · serial 15283779
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

During the landing flare for a full-stop landing, the airplane touched down hard, and bounced into the air. The student pilot attempted to arrest the descent, but the airplane's nose wheel hit the runway surface with sufficient force to collapse the nose gear strut and to damage the firewall.

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. Abnormal runway contact during landing (flare/touchdown) defining event
  2. Landing gear collapse during landing (flare/touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot

Dual student

  • Certificate: student
  • Flight time: 50 hours in all; 50 in this make and model
  • Medical certificate: Class 2 (without waivers/limitations)
  • Injury: no injuries

The aircraft

  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235 SERIES (piston); 0 hours total

The flight

  • Departed from: MER Merced CA
  • Destination: MER Merced CA
  • Flight plan: not recorded
  • Runway 31, 7,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 7 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 9,000 ft; a few clouds at 4,000 ft
  • Temperature: 99°F (37°C), dew point 0°F (-18°C)
  • Altimeter: 29.81 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

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

1 document, released by the NTSB on September 25, 2009. 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/WPR09CA430.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.