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

Cessna 152 accident near Hayward, California, July 14, 2020

On July 14, 2020 at about 1:00 am local time, a 1977 Cessna 152, registered N530CA, was substantially damaged in an accident during landing (flare/touchdown) near Hayward, California (Hayward Executive airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 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 airplane control during landing in gusting wind conditions, and the flight instructor's delayed remedial action, which resulted in the left wing striking the runway.

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

What the record shows

Date
July 14, 2020 · about 1:00 am local time · cases in 2020
Place
Hayward, California · Hayward Executive · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 152, built 1977 · all 152s on the register
Registration
N530CA · registry record · serial 152-79757
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The flight instructor reported that the private pilot, who had not flown for a long time, was receiving instruction to become current. After accomplishing flight maneuver training, they returned to the airport for the pilot to practice landings. During the flare for the third landing, with the private pilot on the controls, the left wing was pushed downward and struck the ground when the airplane encountered a wind gust. The pilot subsequently landed and taxied off the runway. The airplane sustained substantial damage to the left wing rear spar. The flight instructor added that, if he had positioned his hands on or very near the controls during the landing, the accident could have been prevented. The flight instructor reported that there were no mechanical anomalies with the airplane or engine 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. Loss of control on ground during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Action/decision › Action › Delayed action › Instructor/check pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation

Flight instructor

  • Certificate: flight instructor
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 935 hours in all; 120 in this make and model; 85 in the last 90 days; 78 in the last 30 days; 840 as pilot in command; 660 on instruments
  • Last flight review: January 20, 2019
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 70 hours in all; 2.5 in this make and model; 2.5 in the last 90 days; 2.5 in the last 30 days; 14 as pilot in command
  • Last flight review: June 1, 1995
  • Medical certificate: Unknown
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: 100-hour inspection, April 6, 2020
  • Maximum gross weight: 1,670 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-L2C (piston); 107 hours total

The flight

  • Departed from: SQL San Carlos CA at 10:15 pm
  • Destination: SQL San Carlos CA
  • Flight plan: none
  • Runway 28L, 5,694 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 290° at 13 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 1,500 ft
  • Temperature: 61°F (16°C), dew point 52°F (11°C)
  • Altimeter: 29.87 inHg
  • Observation at 2:54 am from KHWD

Injuries

FatalSeriousMinorNone
Flight crew2

Photographs from the investigation 1 picture from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

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

2 documents, released by the NTSB on October 9, 2020. 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.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
2 Photo PDF, 1 page · our copy View Download

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/WPR20CA222.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.