FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08LA160 · Quad City Ultralight Aircraft Challenger LSS

31 May 2008 · Moses Lake, WA, United States

Quad City Ultralight Aircraft Challenger LSS · Accident: flight control system malfunction/failure on approach

From Moses Lake Municipal Airport (W20) to Moses Lake Municipal Airport (W20)

Report a problem

Event

NTSB case
LAX08LA160
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
1 · 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 Ultralight Aircraft Challenger LSS

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
N95478
Operator
Unknown
Onboard fatalities
Unknown
Route
From Moses Lake Municipal Airport (W20), Moses Lake, WATo Moses Lake Municipal Airport (W20)
Aircraft age
Not recorded
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 downwind
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
Flight control system malfunction/failure
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
  • Aircraft › Aircraft structures
  • Personnel issues › Task performance

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 was completing a local flight and entered the downwind leg of the traffic pattern at the destination airport. As the airplane was on the downwind leg and almost abeam the runway identifier numbers, the engine power reduced and the nose pitched up about 15 degrees. The airplane made a tight turn onto the base leg and then overshot final approach. The airplane was high and appeared to be configured in a slip (right wing low) while approaching the runway. When reaching about 30 feet above ground level (agl), the airplane pitched nose high, as if the pilot was attempting to flare. The engine power slowly increased and the airplane turned about 45 degrees, barely clearing a hangar and power lines. The airplane made numerous erratic maneuvers while varying altitudes between 45 and 300 feet agl. It then pitched up about 65 degrees nose high and made a left bank. It subsequently stalled and continued in a spin about 360 degrees before impacting a field located adjacent to the runway. A postaccident examination revealed that the vertical fin had separated from the fuselage attach points and remained attached to the airplane only by the horizontal tail plane struts, the elevator control push rods, and the rudder cables. Examination revealed that the vertical fin attach tubes (forward and aft) had not been secured to the fuselage attach tubing. The bolts designed to secure the vertical fin to the fuselage were not attached; rather, the bolts were secured to the fuselage tubing and the undrilled vertical fin attach tubing was resting on top of the bolts. The build manual for the airplane states that during assembly, the builder must remove the bolts secured to the fuselage attach tubing and insert the vertical fin attach tubing. Following insertion the builder is instructed to drill the vertical fin tubing and secure the bolt through both pieces of tubing.

Probable cause

The pilot's inability to maintain control due to an in-flight separation of the vertical fin as a result of the failure of the airplane's builder to properly secure the vertical fin to the fuselage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08LA160
Event ID
20080605X00798
Case number
LAX08LA160
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. 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: 61b12f8d7358aa498f5ffb6a4b335f6bc670fc2297c1e568580b17bca54ee31d; retrieved 2026-09-13T19:06:12.677Z.