FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Mesa Airlines Bombardier CL-600-2C10 incident

15 Dec 2008 · Chicago, IL, United States

Bombardier CL-600-2C10 · Incident: system/component malfunction/failure (non-power) on approach

From Chicago O'Hare International Airport (ORD) to Chicago O'Hare International Airport (ORD)

Report a problem

Event

NTSB case
CEN09FA094
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-2C10

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
N511MJ
Onboard fatalities
Unknown
Route
From Chicago O'Hare International Airport (ORD), Chicago, ILTo Chicago O'Hare International Airport (ORD), Chicago, IL
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
Approach · IFR initial approach
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
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft structures
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the landing approach, the landing gear "Gear Disagree" warning message appeared. The flight crew performed the appropriate emergency checklists without success. An emergency landing was conducted with a fully extended nose and right main landing gear, but the left main landing gear was not extended. The pilot reported that he was able to keep the left wing up for only a few seconds before it contacted the runway. The airplane skidded to a stop with the left wing supported by the wing flaps and the outboard leading edge slats. The inspection of the airplane revealed that the landing gear belly fairing was fractured. The inspection further indicated that the left main landing gear door had intruded over the belly fairing and weather seal at the fracture area, and had become "hung up" and was not able to extend to the down position. The clearance between the left landing gear door and the belly fairing was measured while the landing gear was in the stowed position. The investigation revealed that the manufacturer’s Aircraft Maintenance Manual (AMM) did not specify the clearance measurement for zone “E”, which was the zone that corresponded to the fractured belly fairing. A review of the airplane’s maintenance records indicated that the left main landing gear door had been replaced at the manufacturer's heavy maintenance facility in September 2007. A maintenance review revealed that the door was rigged and checked with the use of the aircraft hydraulic pumps instead of the external hydraulic power unit as required by the AMM.

As a result of the investigation findings, the following safety actions were taken:

1. On December 23, 2008, Bombardier issued Service Letter CRJ700/900-SL-32-039, “Body Fairing Seal Inspection Common to MLG Inboard Door” to provide operators with guidelines for inspecting the body fairing seal common to the main landing gear inboard doors at the next convenient maintenance opportunity (i.e., 72 hour or 100 flight hours).

2. On December 24, 2008, Bombardier issued Reference Instruction Letter (RIL) No. 1583, "Clarification of clearance for MLG door installation." It stated that it was permissable to use the clearances shown in AMM 32-12-01-220-801-A02 Fig 502 during utilization of AMM 32-12-01-220-801-A01 Figure 501.

3. On January 28, 2009, the Federal Aviation Administration (FAA) issued a Special Airworthiness Information Bulletin (SAIB) No. NM-09-06. The SAIB stated that the FAA “strongly recommends that the affected operators comply with Bombardier Service Letter CRJ700/900-SL-32-039 at the earliest opportunity.”

4. Mesa Airlines conducted a fleetwide inspection of their aircraft and found no other door seal anomalies. Bombardier plans to issue a revised AMM procedure to indicate the proper clearances for zone E. The FAA plans to issue an AD once Bombardier makes the revision to the AMM.

Probable cause

The failure of the left landing gear to extend due to improper maintenance when the landing gear door was replaced. Contributing to the incident was the manufacturer's inadequate maintenance manual instructions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09FA094
Event ID
20081217X83220
Case number
CEN09FA094
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2008-12-16.
  • API snapshot SHA-256: ecf2be17adce1da030269768804e9702655dbacea3ec98dac959736c4d1b0715; retrieved 2026-09-15T10:36:38.283Z.