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

Amateur-built BREESE accident near Whitewater, California, May 13, 2012

On May 13, 2012 at about 2:15 am local time, a 2007 amateur-built BREESE, registered N51336, was substantially damaged in an accident during enroute (cruise) near Whitewater, California. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s decision to fly at low altitude in mountainous terrain in the presence of strong wind and turbulence, which resulted in an aerodynamic upset at too low an altitude for recovery.

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

What the record shows

Date
May 13, 2012 · about 2:15 am local time
Place
Whitewater, California · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built BREESE DS, built 2007
Registration
N51336 · registry record · serial 29652
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The day before to the accident, the pilot flew from his home to a private airstrip about 60 miles away in order to attend a desert gathering of his ultralight association. The ultralight-like aircraft consisted of an aluminum tube framework with a single seat, an open fuselage, and fabric-covered aerodynamic surfaces, and was powered by a 60-horsepower engine and was equipped with a rocket-powered parachute. The next day, the pilot flew about 15 miles to another private airstrip and flew back to the gathering a few hours later. Although the gathering was scheduled to continue one more day, in the late afternoon, the pilot decided to depart for his home airport. Before his departure, he had a brief discussion about the headwind with another association member. When the aircraft was about halfway to its destination, in a region of mountainous terrain, two witnesses observed it flying about 400 feet above the ground. They believed the aircraft to be in trouble because the wings were rocking. The aircraft made a 270-degree turn, pitched up and over to the inverted position, and began a steep, nose-down descent. The pilot deployed the rocket-powered aircraft parachute, but the parachute did not arrest the descent. The aircraft struck the ground in a steep trajectory in a steep nose-down attitude. Examination of the aircraft did not reveal any preimpact mechanical failures or deficiencies that would have prevented continued flight or the deployment and functioning of the parachute system. Although all but one of the parachute system's shroud lines were cut, their as-found location and appearance indicated that they were cut after the accident—most likely to prevent the canopy from inflating and disturbing the wreckage. About the time of the accident, a meteorological station 2 miles from the accident site recorded 31 mph wind , with gusts to 47 mph. Witnesses also reported that it was very windy, and one ultralight pilot familiar with the area reported that the area was notorious for strong winds and rotors. Although the pilot was not the owner, he was considered to be highly experienced and quite familiar with the aircraft. Although the specific reasons for the failure of the parachute to arrest the descent could not be determined, the high wind, turbulence, initial descent attitude and trajectory, and low deployment altitude likely all contributed to that failure. Additionally, the pilot regularly left the safety pin for the parachute activation handle in during flight, which may have delayed his activation of the system.

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. Turbulence encounter during enroute (cruise)
  2. Inflight upset during enroute (cruise) defining event
  3. Turbulence encounter during uncontrolled descent
  4. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Expectation/assumption › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Aircraft capability › (general) › Capability exceeded
  • Aircraft › Aircraft systems › Equipment/furnishings › Parachute › Capability exceeded
  • Environmental issues › Conditions/weather/phenomena › Wind › High wind › Contributed to outcome

Pilot

  • Certificate: sport pilot
  • Ratings: single-engine land
  • Medical certificate: Sport Pilot
  • Seat: sngl
  • Injury: fatal

The aircraft

  • Airframe total time: 210 hours
  • Last inspection: condition inspection, July 9, 2011
  • Maximum gross weight: 650 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Hks 700E (piston); 210 hours total

The flight

  • Departed from: CA51 Lucerne Valley CA at 1:30 am
  • Destination: Perris CA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 300° at 27 knots, gusting 40
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 46°F (8°C)
  • Observation at 2:50 am from WWAC, 2 miles away

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.