FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA086 · Quad City CHALLENGER II

7 Jan 2023 · Kent, WA, United States

Quad City CHALLENGER II · Accident: loss of control in flight during initial climb

From Auburn Municipal Airport (S50) to Harvey Field (S43)

Report a problem

Event

NTSB case
WPR23LA086
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

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
N528J
Onboard fatalities
Unknown
Route
From Auburn Municipal Airport (S50), Auburn, WATo Harvey Field (S43), Snohomish, WA
Aircraft age
About 6 years (built 2017)
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
Initial climb
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 › Action/decision
  • Personnel issues › Experience/knowledge

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot-rated passenger had just purchased the light sport airplane and hired the pilot to relocate airplane to his home airport. The passenger/owner reported that the pilot stated he had no experience in the airplane make and model, but that he ferried airplanes for a living and was confident with no hesitations. After conducting a preflight inspection, the pilot and passenger boarded the airplane and the passenger briefed the pilot on the use of the airplane’s flaperons. The passenger reported that the airplane “swerved right” about 20 ft above ground level after takeoff, and that the pilot continued the climb while adjusting the flaperons. The pilot reported that, shortly after takeoff, the airplane became “unresponsive” to left stick inputs and entered an uncontrolled turn to the right. The pilot was unable to recover, and the airplane descended and impacted the roof of a storage facility, resulting in substantial damage to the fuselage and both wings. The forward control stick aileron cables separated at the left aileron turnbuckle and right aileron cable near the forward pulley. The forward control stick aileron cable sections, including turnbuckles and forward pulleys, were removed for further examination. The flaperons were near the full-down position. Postaccident examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The right aileron control cable and the turnbuckle barrel for the left aileron control cable both exhibited ductile overstress fractures from abnormal loading, likely associated with impact. Even if either of the fractures occurred before impact, the ailerons could have been controlled by cables attached to the aft control stick. The left pulley and support brackets showed multiple contact marks and scratches consistent with cable contact outside the normal pulley groove contact area, but no similar contact marks were observed on the right pulley. If the abnormal cable marks on the left pulley were the result of slack in the system before the fracture, similar marks would also be expected on the right pulley. The absence of abnormal cable contact marks on the right pulley suggests the marks on the left pulley assembly likely occurred due to impact rather than due to preexisting slack in the system. Information from the airplane manufacturer stated that pilots should not attempt to fly without a proper type checkout. Information on the use of the flaperon system indicated that, under certain flight conditions with the flaperons extended, control stick pressures would become “heavy,” and in some cases, “an increasingly steep dive will result.” The pilot reported no experience in the accident airplane make and model. It is likely that the pilot’s lack of familiarity with the airplane’s flight characteristics resulted in his loss of airplane control during flight.

Probable cause

The pilot’s inflight loss of airplane control. Contributing to the accident was the pilot’s decision to fly the airplane without receiving training in its operation and flight characteristics.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA086
Event ID
20230110106561
Case number
WPR23LA086
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, coordinates, cause areas. 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: 3e59891d3a7588caa95779f6c0299373d97e2acbcaf0113999a8f1e88ffeee95; retrieved 2026-09-16T17:14:33.175Z.