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

Cessna 320D accident near Green River, Wyoming, April 12, 2012

On April 12, 2012 at about 11:30 pm local time, a Cessna 320D, registered N32EG, was destroyed in an accident during maneuvering near Green River, Wyoming. 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 failure to maintain airplane control while maneuvering in marginal weather conditions, which resulted in an exceedence of the design stress limits of the airplane and a subsequent in-flight structural failure.

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

What the record shows

Date
April 12, 2012 · about 11:30 pm local time · cases in 2012
Place
Green River, Wyoming · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 320D · all 320Ds on the register
Registration
N32EG · no longer on the register · serial 320D0009
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The non-instrument rated pilot departed in the high-performance multiengine airplane on a cross-country flight over mountainous terrain. Mixed rain and snow showers were reported in the area, and lightning flash data and surface observations indicate vigorous snow shower activity around the time and location of the accident. Recorded radar returns believed to be associated with the accident airplane showed a radar track on a westerly heading at cruise altitudes between 10,000 and 12,000 feet mean sea level. The radar track then depicted a descending 720-degree turn over the course of several miles. Following the turn, the radar track showed multiple heading and altitude changes over the course of about 2 minutes. The last observed radar return was about 0.4 mile from the accident location. The wreckage debris was scattered over an area about 0.4 mile in length. Pieces of the cockpit and a section of the right elevator were located at the southeast perimeter of the debris field; the fuselage and both engines located at the opposite, northwest, end of the debris field. Sections of the wings, flight control surfaces and horizontal stabilizer were also scattered between the beginning of the debris field and the main wreckage. Examination of the wing and horizontal stabilizer spars fracture surfaces showed features consistent with overstress separation in-flight and no evidence of fatigue was noted. Given the radar track, the length of the wreckage debris field, and the marginal weather conditions, it is likely that the break-up sequence was inadvertently induced as the pilot attempted to maneuver the airplane out of marginal weather conditions, which ultimately led to an exceedence of the design stress limits of the airplane.

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. Other weather encounter during enroute (cruise)
  2. Abrupt maneuver during maneuvering
  3. Aircraft structural failure during maneuvering defining event
  4. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Dynamic load › Capability exceeded
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Snow › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land
  • Flight time: 1,600 hours in all; 150 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,627 hours
  • Last inspection: annual inspection, November 1, 2011
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: Cont Motor TSIO-520-B (piston); 0 hours total
  • Engine 2: Cont Motor TSI0-520-B (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: KSNY Sidney NE at 9:30 pm
  • Destination: KWMC Winnemucca NV
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 280° at 8 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,500 ft; a few clouds at 200 ft
  • Temperature: 34°F (1°C), dew point 32°F (0°C)
  • Altimeter: 29.79 inHg
  • Observation at 11:07 pm from KRKS, 37 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

12 documents, released by the NTSB on September 22, 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/WPR12FA164.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.