GAA19CA297 · Quicksilver 2S SPORT
Quicksilver 2S SPORT · Accident: loss of engine power (total) while maneuvering
From Waverly, MN (private airstrip) to Waverly, MN (private airstrip)
Event
- NTSB case
- GAA19CA297
- 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
- 0 · 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
Quicksilver 2S SPORT
- Aircraft type
- Quicksilver 2
- Category
- Airplane
- 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
- UNREG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waverly, MN (private airstrip)To Waverly, MN (private airstrip)
- Aircraft age
- About 18 years (built 2001)
- 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
- Maneuvering
- 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 engine power (total)
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the unregistered airplane reported that he departed with 3 gallons of fuel and that he was flight testing the airplane by flying it low up and down a private, grass airstrip. He added that, about 1 hour 15 minutes hours into the flight, he "neglected to carefully check the fuel remaining" before taking off to conduct a teardrop maneuver. Once airborne, about 50 to 75 ft, he performed a climbing left turn and noticed the "engine was no longer producing power." He leveled the wings and pushed forward on the control stick. He began the landing flare for a forced landing in a field, and the airplane landed hard and nosed over.
The airplane sustained substantial damage to the fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The pilot recommended as a safety recommendation to "fill the fuel tank!"
Probable cause
The pilot's improper preflight fuel planning, which resulted in a total loss of engine power due to fuel exhaustion and a subsequent forced, hard landing in a field.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA297
- Event ID
- 20190531X70328
- Case number
- GAA19CA297
- 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 2019-05-31.
- API snapshot SHA-256: 4b55abbe4c8b003a32007ca279d73f98b0818509efa20c2f196e4efdc83ca68d; retrieved 2026-09-16T09:06:50.555Z.