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

Cessna 177 accident near Corona, California, December 12, 2010

On December 12, 2010 at about 2:30 am local time, a Cessna 177, registered N2262Y, was substantially damaged in an accident during landing (flare/touchdown) near Corona, California (Corona Municipal airport). It was a personal 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 improper flare, which 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
December 12, 2010 · about 2:30 am local time
Place
Corona, California · Corona Municipal · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 177 · all 177s on the register
Registration
N2262Y · registry record · serial 17700062
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that during the first approach for landing the wind affected his alignment to the runway, and he performed a go-around. On the second attempt, the approach seemed normal until the pilot flared the airplane excessively, resulting in a stall and subsequent hard landing. Examination of the airplane revealed substantial damage to the firewall and wing.

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. 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 › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 119 hours in all; 49 in this make and model; 22 in the last 90 days; 7 in the last 30 days; 74 as pilot in command
  • Last flight review: February 20, 2010
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,298 hours
  • Last inspection: annual inspection, November 19, 2010
  • Maximum gross weight: 2,350 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360 (piston); 0 hours total

The flight

  • Departed from: HII Lake Havasu AZ
  • Destination: AJO Corona CA
  • Flight plan: none
  • Runway 07, 3,200 ft by 60 ft

Weather at the time

  • Light: night
  • Wind: from 150° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 73°F (23°C), dew point 39°F (4°C)
  • Altimeter: 30.07 inHg
  • Observation at 1:56 am from KAJO

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.