FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA06FA146 · Spectrum Aeronautical LLC 33

25 Jul 2006 · Spanish Fork, UT, United States

Spectrum Aeronautical LLC 33 · Accident: airframe, component or system failure before flight

From U77 · Spanish Fork, UT to U77

Report a problem

Event

NTSB case
SEA06FA146
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
2 · 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

Spectrum Aeronautical LLC 33

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
N322LA
Operator
Unknown
Onboard fatalities
Unknown
Route
From U77 · Spanish Fork, UTTo U77
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
Prior to flight
First occurrenceThe 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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Company maintenance personnel › Maintenance, installation, incorrect
  • Flt control syst, aileron control › Reversed

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

NTSB narrative

The proto-type experimental light jet airplane was departing on a local maintenance test flight. Witnesses reported that the airplane entered a right roll almost immediately after liftoff. The roll continued to about 90 degrees right wing down at which point the right wingtip impacted the ground. During examination of the wreckage, the aileron control system was found connected such that the airplane rolled in the opposite direction to that commanded in the cockpit. The maintenance performed on the airplane before the accident flight included removal of the main landing gear (MLG) in order to stiffen the MLG struts. Interviews with the mechanics who performed the maintenance revealed that during re-installation and system testing of the MLG, it was discovered that the changes to the MLG struts impacted the V-bracket holding the aileron control system's upper torque tube. The V-bracket was removed and a redesigned V-bracket was installed in its place. This work required the disconnection of a portion of the aileron control system, including the removal of the aft upper torque tube bell crank from the torque tube. The mechanic who reinstalled the aft upper torque tube bell crank was under the incorrect assumption that there was only one way to install the bell crank on the torque tube. However, there are actually two positions in which the bell crank could be installed. The incorrect installation is accomplished by rotating the bell crank 180° about the axis of the torque tube and flipping it front to back, and this is the way the bell crank was found installed. With the bell crank installed incorrectly and the rest of the system installed as designed, there is binding in the system. This binding was noticed on the accident airplane during the inspection after initial installation. However, the mechanic did not recognize that the bell crank was improperly installed on the torque tube. Instead of fixing the problem by removing and correctly reinstalling the bell crank, he fixed the problem by disconnecting the necessary tie rods and rotating the upper torque tube so that the arm of the bell crank pointed up and to the left. This action reversed the movement of the ailerons. According to all of the personnel interviewed, there was no maintenance documentation to instruct mechanics how to perform the work since this was a proof-of-concept airplane. None of the mechanics who performed the work could recall if the position of the ailerons in relation to the position of the control stick was checked. Such a position check, if it had been performed by either the mechanics after the maintenance or by the flight crew during the preflight checks, would assuredly have indicated that the system was installed incorrectly.

Probable cause

Incorrect installation by company maintenance personnel of the aft upper torque tube bell crank resulting in roll control that was opposite to that commanded in the cockpit. Contributing factors were the lack of maintenance documentation detailing the installation of the bell crank, the installing mechanic's incorrect assumption that the bell crank could only be installed in one position, and the failure of maintenance personnel and the flight crew to check the position of the control stick relative to the ailerons after the maintenance and during the preflight checks.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA06FA146
Event ID
20060731X01059
Case number
SEA06FA146
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: cd297003072defb84157d5c6f1aa17f202374605b00c3aaa5b5ede28ff0f5aa5; retrieved 2026-09-20T17:07:50.844Z.