CEN23LA221 · Quad City CHALLENGER II
Quad City CHALLENGER II · Accident en route
From Neelyville, MO (private airstrip) to Neelyville, MO (private airstrip)
Event
- NTSB case
- CEN23LA221
- 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
- Event fatalities
- Unknown
- 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
- N265JW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Neelyville, MO (private airstrip)To Neelyville, MO (private airstrip)
- Aircraft age
- About 20 years (built 2003)
- 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
- En route
- 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
- Unknown or undetermined
- 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 power plant
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during the flight he attempted to increase engine power to climb over a densely wooded hillside; however, the engine did not respond. Unable to clear the hill, he decided to execute a forced landing to a pasture. During the landing rollout, the airplane struck a fence. The pilot noted that the engine did not stop running during the flight, but that he was unable to increase engine power. Postaccident engine examination of the engine did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation and the engine was started and ran at idle speed with no anomalies noted. The pilot speculated that some type of fuel flow restriction had resulted in the partial loss of engine power. Weather conditions were conducive to carburetor icing at glide power. However, the engine was equipped with a slide-type carburetor which, due to their design, are generally not susceptible to icing.
Probable cause
A partial loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA221
- Event ID
- 20230602192294
- Case number
- CEN23LA221
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2023-05-28.
- API snapshot SHA-256: ba5eea9f27a0dc87a377d2391383c8dc5aa3e24388d3139fcda6b8bb2c158ed4; retrieved 2026-09-16T17:40:58.229Z.