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

Cessna 172 - S accident near Hawthorne, California, October 23, 2014

On October 23, 2014 at about 8:00 pm local time, a 2005 Cessna 172 - S, registered N564AT, was substantially damaged in an accident during landing (flare/touchdown) near Hawthorne, California (Hawthorne Municipal 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 loss of aircraft control and subsequent hard landing.

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

What the record shows

Date
October 23, 2014 · about 8:00 pm local time · cases in 2014
Place
Hawthorne, California · Hawthorne Municipal Airport · 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 172 - S S, built 2005 · all 172 - Ss on the register
Registration
N564AT · registry record · serial 172S10020
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The pilot reported that during landing he flared too high, which resulted in the airplane bouncing hard three times. A postaccident examination of the airplane revealed that the firewall had sustained substantial damage. The pilot reported no 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) defining event

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

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

The aircraft

  • Airframe total time: 3,674 hours
  • Last inspection: 100-hour inspection, September 17, 2014; 42 hours since
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 3,715 hours total
  • Operator: Pacific Air Flight School

The flight

  • Departed from: HHR Hawthorne CA at 8:00 pm
  • Destination: HHR Hawthorne CA
  • Flight plan: none
  • Runway 25, 4,956 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 61°F (16°C)
  • Altimeter: 29.98 inHg
  • Observation at 7:57 pm from HHR

Injuries

FatalSeriousMinorNone
Flight crew1

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

3 documents, released by the NTSB on December 19, 2014. 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/WPR15CA028.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.