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

Cessna 152 accident near Santa Rosa, California, September 1, 2014

On September 1, 2014 at about 9:00 pm local time, a 1978 Cessna 152, registered N67367, was substantially damaged in an accident during landing (flare/touchdown) near Santa Rosa, California (Santa Rosa 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 student pilot's inadequate flare resulted in a hard landing.

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

What the record shows

Date
September 1, 2014 · about 9:00 pm local time
Place
Santa Rosa, California · Santa Rosa · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 152, built 1978 · all 152s on the register
Registration
N67367 · no longer on the register · serial 15281784
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The student pilot completed three takeoffs and landing with the certified flight instructor (CFI) on board, then took off for his first solo flight in the pattern. During the first landing, the airplane bounced twice and on the third touchdown, the nose gear collapsed and the airplane slid to a stop.  The student pilot was not injured, but the airplane sustained substantial damage to the firewall. There were no reports of preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

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)
  2. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Student/instructed pilot

Dual student

  • Certificate: student
  • Flight time: 30 hours in all; 30 in this make and model; 11 in the last 90 days
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 15,952 hours
  • Last inspection: 100-hour inspection, July 23, 2014; 53 hours since
  • Maximum gross weight: 1,676 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-L2C (piston); 0 hours total
  • Operator: North Coast Air INC

The flight

  • Departed from: STS Santa Rosa CA
  • Destination: STS Santa Rosa CA
  • Flight plan: none
  • Runway 20, 4,831 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 160° at 9 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 93°F (34°C), dew point 50°F (10°C)
  • Altimeter: 29.78 inHg
  • Observation at 9:18 pm from KSTS

Injuries

FatalSeriousMinorNone
Flight crew1

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.