FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SkyWest Airlines Bombardier Aerospace, Inc. CL-600-2B19 accident

12 Jun 2005 · Los Angeles, CA, United States

Bombardier Aerospace, Inc. CL-600-2B19 · Accident: airframe, component or system failure on approach

From Los Angeles International Airport (LAX) to Santa Barbara Municipal Airport (SBA)

Report a problem

Event

NTSB case
LAX05FA202
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
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 Aerospace, Inc. CL-600-2B19

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
N960SW
Onboard fatalities
Unknown
Route
From Los Angeles International Airport (LAX), Los Angeles, CATo Santa Barbara Municipal Airport (SBA), Santa Barbara, CA
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
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
Substantial

Cause areas

  • Landing gear, emergency extension assembly › Malfunction
  • Landing gear, normal retraction/extension assembly › Malfunction
  • 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 damaged during a landing with the nose landing gear partially extended. As the airplane descended toward the destination airport, the crew moved the landing gear handle to the extend position. The pilots noted a "gear disagree" warning message displayed on the Engine Indicating and Crew Alerting System (EICAS) that showed the main landing gear were down and locked, and the nose gear was not fully extended. The pilots opted to land at an alternate airport and began to troubleshoot the gear indication with use of the airplane's Quick Reference Handbook (QRH). Despite their efforts, which included using the manual release handle, the nose gear failed to extend. The airplane touched down on the main landing gear and the nose lowered to the ground as the speed dissipated. Review of the CVR found that the flight crew followed each step of the Quick Reference Handbook checklist. The flight crew did not cycle the landing gear lever, nor was that action part of the QRH procedure at the time. The digital flight data recorder (DFDR) revealed that the main landing gear transitioned into the down and locked position but the nose gear remained partially extended between the uplocked and downlocked positions. A further review of the data disclosed the hydraulic pressure remained constant throughout the extension and did not show the pressure changes that should have occurred with normal system operation. The only pressure changes noted in the duration of the flight were consistent with the manual release system being activated. No increase of brake pressure was recorded during the gear extension attempt, indicating that there was no hydraulic backpressure on the retract side of the NLG actuator. The components of the nose landing gear (NLG) system were tested, revealing no anomalies or malfunctions that could have precluded normal operation. Several simulations were conducted exploring various potential problem scenarios; however, none of the simulations produced the hydraulic system and brake pressure readings on the accident flight's DFDR data. A review of several maintenance discrepancy databases for events where the NLG failed to extend into the downlock position found that the operator did not have a higher event rate of gear disagree messages than the rest of the worldwide fleet. Simulations and static analysis on the friction force of the uplock was performed, specifically detailing the interaction between the pin and the latch. As a result of the testing, areas of potential problems with the NLG extension systems (both normal and manual) under adverse conditions were found to include: friction within the system and the sequencing of the hydraulic pressure application. Bombardier subsequently modified the QRH procedure, adding another step to specifically recycle the gear selector handle.

Probable cause

failure of the nose landing gear to extend to the down and locked position for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA202
Event ID
20050617X00804
Case number
LAX05FA202
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-06-13.
  • API snapshot SHA-256: f90204ea846d312344364bdae0d663dc0c28e4d481486769c678f239cbc0e5d9; retrieved 2026-09-18T15:01:26.312Z.
  • The NTSB's operator name is blank for N960SW; the operator shown is the name the NTSB's other records give its FAA operator code, SWIA.