CEN17LA307 · Pegasus QUANTUM Q-2
Pegasus QUANTUM Q-2 · Accident: loss of control in flight on approach
From Fort Atkinson Municipal Airport (61C) to Fort Atkinson Municipal Airport (61C)
Event
- NTSB case
- CEN17LA307
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Pegasus QUANTUM Q-2
- Aircraft type
- Pegasus QUANTUM
- Category
- Weight-Shift
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N56092
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Atkinson Municipal Airport (61C), Fort Atkinson, WITo Fort Atkinson Municipal Airport (61C), Fort Atkinson, WI
- Aircraft age
- About 10 years (built 2007)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR go-around
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The sport pilot (who was not an instructor) and the student-pilot-rated passenger were making a local personal flight in the weight-shift-control (WSC) aircraft. The pilot was seated in the front seat, and the passenger was seated in the rear seat. A flight instructor observed the WSC aircraft make several stable visual approaches to a grass runway. The last approach was unstable, which the flight instructor attributed to the passenger attempting to fly the approach. A go-around was initiated, which transitioned to a diving left turn that continued to impact with a river.
Postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The aircraft's two "training bars," which were designed for use by a flight instructor flying from the rear seat, were each deformed to the left, consistent with the passenger gripping them as the aircraft impacted the river.
The passenger had recently accomplished a solo flight in a fixed-wing airplane, which has reverse control inputs from a WSC aircraft. The passenger likely made incorrect control inputs during the go-around, due to negative transfer of learning from his fixed-wing airplane training. Because of the position of the training bars, the front-seat pilot would have been unable to see the inputs being made by the person in the rear seat.
Although toxicological testing indicated that the pilot had used diphenhydramine at some point before the accident, the blood levels of this drug can change postmortem, and the pilot's blood levels at the time of the accident may have been significantly lower than the therapeutic range. Based on the accident scenario and available information, the pilot's use of diphenhydramine most likely did not contribute to the accident.
Probable cause
The student pilot's failure to maintain aircraft control during a go-around, which resulted in impact with water. Contributing to the accident was the non-instructor sport pilot's decision to allow the student pilot to fly the aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA307
- Event ID
- 20170809X40008
- Case number
- CEN17LA307
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-08-09.
- API snapshot SHA-256: 9e0be0449c815f7cf3d199e66aa1dba418b915ff7afbb1bb8fe46fb95f61b396; retrieved 2026-09-15T06:12:30.042Z.