FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Mesa Airlines Bombardier CL-600-2B19 incident

13 Jun 2003 · Phoenix, AZ, United States

Bombardier CL-600-2B19 · Incident: airframe, component or system failure en route

From Phoenix Sky Harbor International Airport (PHX) to Boise Air Terminal/Gowen Field (BOI)

Report a problem

Event

NTSB case
LAX03IA199
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
Incident
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
Airline
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

Bombardier CL-600-2B19

Aircraft type
Bombardier CL-600
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
N97325
Onboard fatalities
Unknown
Route
From Phoenix Sky Harbor International Airport (PHX), Phoenix, AZTo Boise Air Terminal/Gowen Field (BOI), Boise, ID
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 121: Air Carrier
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 · climb to cruise
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
None

Cause areas

  • Reason for occurrence undetermined

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

NTSB narrative

The airplane was climbing through 23,000 feet for flight level 290 (29,000 feet) when the stab trim/mach trim caution illuminated on the instrument panel indicating both channels 1 and 2 were inoperative, and subsequently the pitch trim system could not be moved. The captain maintained the airplane's airspeed below 215 knots, and initiated a return to the departure airport. The flight crew took turns at the controls. To maintain the airplane in the proper attitude, the first officer had to maintain about 30 pounds of backpressure on the yolk to counteract the trim forces. The captain landed the airplane uneventfully. Maintenance crews believed the failure was in the captain's stab trim disconnect switch, which they suspected was stuck in the cutout position. The switch was replaced with another unit. A second stab trim failure event occurred 32 days later in the same airplane. The captain reported that during a descent from flight level 290, both channels of stab trim and mach trim failed with a corresponding "AP Pitch Trim" message. After about 2 minutes, the captain was able to reset both stab trim channels and then the mach trim. The airplane landed uneventfully. The maintenance crew removed and replaced the Horizontal Stabilizer Trim Control Unit (HSTCU) to correct the discrepancy. The airplane's flight data recorders (FDR's) were removed, and the data downloaded. The data revealed that 17 minutes into the flight on the first occurrence the stabilizer trim discrete changed from 'on' to 'off.' The data for the second occurrence revealed that 96 minutes into the flight the stabilizer trim discrete changed from 'on' to 'off' for about 2 minutes, and then back to 'on.' The stab trim disconnect switch and the HSTCU were tested, and both functioned within the manufacturer's specifications. Under physical examination it was noted that the HSTCU's access panel door cam-type fastener's shoulder guide was missing from one of the two door latching fittings. The shoulder half was located loose inside the HSTCU circuitry area of the unit. Engineers described the electrical circuit boards as having a heavy coat of protective/sealing varnish that would protect the circuits from shorts caused by debris. Additionally, each trim channel is on a separate circuit board in the HSTCU. The simultaneous failure of both trim channels due to a single piece of debris is unlikely. A search of the Federal Aviation Administration Service Difficulty Report (SDR) database for Stab Control System anomalies in the CL-600 from 1995 to July 10, 2003, identified 67 dual channel stab trim failures. Twenty-seven percent of the dual trim failures were identified as cockpit trim disconnect switch issues; 52 percent were identified as HSTCU/HSTA/MCU issues; and 21percent were not resolved or could not be duplicated on the ground. The airplane in question, serial number 7325, was not listed in the results as having any reported flight control discrepancies in the database.

Probable cause

the simultaneous failure of both horizontal stabilizer trim channels on two separate occasions for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03IA199
Event ID
20030624X00941
Case number
LAX03IA199
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-06-14.
  • API snapshot SHA-256: 5259a898dd69b0d5f56f92f2bd94d7ed45fc2e4e6fc5c4b5804a8b88e87ddca4; retrieved 2026-09-18T15:46:28.534Z.
  • The NTSB's operator name is blank for N97325; the operator shown is the name the NTSB records it doing business as.