CEN18CA291 · Quad City CHALLENGER II
Quad City CHALLENGER II · Accident: loss of control in flight on approach
From Wautoma Municipal Airport (Y50) to Wittman Regional Airport (OSH)
Event
- NTSB case
- CEN18CA291
- 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
Quad City CHALLENGER II
- Aircraft type
- Quad City CHALLENGER
- 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
- N1666R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wautoma Municipal Airport (Y50), Wautoma, WITo Wittman Regional Airport (OSH), Oshkosh, WI
- Aircraft age
- About 10 years (built 2008)
- 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 pattern final
- 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 airplane was landing on the ultralight field when the accident occurred. The pilot stated that she made a wide base to final turn because she was unsure about the placement of the runway. Although the pilot added power, the airplane entered a left descending turn until the left wing contacted the ground near the beginning of the runway's displaced threshold. The airplane then spun left and slid rearward on the ground until it contacted a chain-link fence.
The pilot reported that there were no mechanical anomalies with the airplane that would have precluded normal operation. The pilot's statement, along with a ground-based video of the accident, revealed that the pilot failed to maintain adequate airspeed and exceeded the airplane's critical angle of attack during the base to final turn, which resulted in an aerodynamic stall.
Probable cause
The pilot’s failure to maintain adequate airspeed during the base to final turn and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18CA291
- Event ID
- 20180723X24509
- Case number
- CEN18CA291
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 003d53f54649aa4f87de2653d9f4db15fc38e6c3ff95088b9c949fff7c1e3f7c; retrieved 2026-09-16T07:56:59.938Z.