Bombardier CL-600-2B19 N97325
14 June 2003 · Phoenix, Arizona, United States · No injuries
Summary
On 14 June 2003 at about 00:30 local time, a Bombardier CL-600-2B19 registered N97325 was involved in an incident near Phoenix, Arizona, United States. 52 people were on board and nobody was injured. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 00:30
- Classification
- Incident
- Location
- Phoenix, Arizona, United States
- Nearest airport
- Phoenix Sky Harbor Intl (KPHX)
- Coordinates
- 33.4342, -112.0081
- Aircraft
- Bombardier CL-600-2B19
- Registration
- N97325
- Category
- Airplane
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 121: Air Carrier
- Phase of flight
- Not recorded
- Route
- Phoenix → Boise
- Aircraft damage
- Not recorded
- Weather
- VMC
- Light
- Day
- NTSB number
- LAX03IA199
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 52 | 0 | 0 | 0 | 52 |
Probable cause
the simultaneous failure of both horizontal stabilizer trim channels on two separate occasions for undetermined reasons.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Bombardier CL-600 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 7 May 2003 | Bombardier CL-600-2B19 | Boston, Massachusetts, United States | - | No injuries | - |
| 8 May 2003 | Bombardier CL-600-2B19 | Chattanooga, Tennessee, United States | Atlantic Southeast Airlines, Inc. | No injuries | - |
| 2 Dec 2003 | Bombardier CL-600-2B19 | Jamaica, New York, United States | Comair Inc | No injuries | - |
| 15 Dec 2003 | Bombardier CL-600-2B19 | Miami, Florida, United States | - | No injuries | - |
| 16 Dec 2003 | Bombardier CL-600 | Teterboro, New Jersey, United States | PrivatAir | No injuries | - |
| 21 Jul 2004 | Bombardier CL-600 | Snow Hill, Virginia, United States | - | Serious injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 8 Jan 2003 | Piper PA-23-250 | Flagstaff, Arizona, United States | - | Fatal | 4 |
| 12 Jul 2003 | Cessna 172S | Chandler, Arizona, United States | Angel Air | No injuries | - |
| 25 Apr 2003 | Piper PA-28-181 | Bullhead City, Arizona, United States | - | No injuries | - |
| 22 Aug 2003 | Ercoupe 415-C | Saint Johns, Arizona, United States | Robert Greenwade | No injuries | - |
| 15 Mar 2003 | Piper PA24 | Mesa, Arizona, United States | - | No injuries | - |
| 22 Aug 2003 | Cessna 150C | Tucson, Arizona, United States | - | No injuries | - |