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

Cessna 182K accident near Chemehuevi Valley, California, September 11, 2009

On September 11, 2009 at about 7:20 pm local time, a Cessna 182K, registered N2819R, was substantially damaged in an accident during landing (flare/touchdown) near Chemehuevi Valley, California (Havasu Palms airport). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improper flare while landing with a tailwind, resulting in a bounced landing.

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

What the record shows

Date
September 11, 2009 · about 7:20 pm local time
Place
Chemehuevi Valley, California · Havasu Palms · map
Type
Accident
Injuries
3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna 182K · all 182Ks on the register
Registration
N2819R · no longer on the register · serial 18258419
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 he conducted an approach to landing over the lake, landing to the west, and that as he reduced power to flare the airplane was caught in a downdraft. The airplane subsequently landed hard and bounced down the runway. On the third oscillation the nose landing gear sheared off before the airplane slid off of the runway and came to rest inverted. The nearest weather reporting system, located about 17 miles to the northwest of the airport, reported wind from 040 degrees at 5 knots. The pilot also reported landing with a slight tailwind.

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 Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
  • Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Not specified

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,005 hours in all; 152 in this make and model
  • Last flight review: September 9, 2009
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection, September 9, 2009
  • Seats: 4
  • Landing gear: fixed
  • Engine: Teledyne Continental Motors O-470 (piston); 0 hours total

The flight

  • Departed from: Unknown
  • Destination: N/A Chemehuevi Valley CA
  • Flight plan: none
  • Runway 27, 3,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 040° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 102°F (39°C), dew point 45°F (7°C)
  • Altimeter: 29.87 inHg
  • Observation at 6:56 pm from EED, 17 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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.