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

Quicksilver Sport II accident near Manchester, Iowa, June 5, 2012

On June 5, 2012, a Quicksilver Sport II, registered N4396H, was substantially damaged in an accident during maneuvering (low-alt flying) near Manchester, Iowa (Manchester Municipal Airport). 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

An inadvertent aerodynamic stall while maneuvering at a low altitude.

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

What the record shows

Date
June 5, 2012 · cases in 2012
Place
Manchester, Iowa · Manchester Municipal Airport · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Quicksilver Sport II · all Sport IIs on the register
Registration
N4396H · no longer on the register · serial 0934
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airplane entered a sharp left bank turn over the airport at a low altitude before impacting the ground with the engine operating. The airplane wreckage was resting in a nose-down, left-wing-low orientation that was consistent with a stall. Examination of the wreckage revealed 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. Aerodynamic stall/spin during maneuvering (low-alt flying) defining event
  2. Loss of control in flight during maneuvering
  3. 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 › Angle of attack › Capability exceeded
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: sport pilot
  • Flight time: 177 hours in all; 4 in the last 90 days; 1 in the last 30 days
  • Last flight review: June 4, 2011
  • Medical certificate: None
  • Injury: fatal

The aircraft

  • Maximum gross weight: 720 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582DCDI (piston); 0 hours total

The flight

  • Departed from: PVT Ryan MN
  • Destination: C27 Manchester IA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 77°F (25°C), dew point 55°F (13°C)
  • Altimeter: 29.90 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

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

9 documents, released by the NTSB on May 30, 2013. 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/CEN12LA340.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.