23 May 2010: BOMBARDIER INC CL-600-2B19 — SKYWEST AIRLINES INC

23 May 2010: BOMBARDIER INC CL-600-2B19 (N925SW) — SKYWEST AIRLINES INC

No fatalities • Ontario, CA, United States

Probable cause

Failure of the airplane’s nose landing gear to extend for undetermined reasons.

— NTSB Determination

Accident narrative

On May 23, 2010, about 1020 Pacific daylight time (PDT), Skywest Airlines flight 6467, a Bombardier CRJ, CL-600-2B19, N925SW, made an emergency landing with the nose gear in the retracted position at Ontario International Airport (ONT), Ontario, California. Skywest Airlines, Inc., was operating the airplane as a scheduled domestic passenger flight under the provisions of 14 Code of Federal Regulations (CFR) Part 121. The certificated airline transport pilot captain, commercial pilot first officer, flight attendant, and 24 passengers were not injured. The flight departed San Francisco International Airport (SFO), San Francisco, California, about 0815 as a non-stop to Ontario. Visual meteorological (VMC) conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed.

The crew reported that the flight was uneventful until they were on final approach for landing at ONT. The landing gear selector was moved to the down position. The main landing gear extended and locked into place; however, the nose landing gear remained retracted. The crew observed an unsafe nose landing gear indication.

The crew aborted the landing approach, and advised air traffic control (ATC) of the emergency. The crew attempted to correct the landing gear malfunction by following the emergency procedures utilizing the Quick Reference Handbook (QRH), but was unsuccessful. The crew conducted a low-level flyby to have tower and ground personnel evaluate the condition of the nose landing gear. The landing gear doors were open, but the nose landing gear was still retracted in the landing gear compartment.

Due to the unsuccessful attempt to lower the nose landing gear, the crew decided to make an emergency landing. After the main landing gear touched down, the captain held the nose off the ground as long as possible. The nose landing gear doors touched down on the runway centerline, and the airplane slid about 2,000 feet. The passengers and crew exited the airplane using the main cabin door.

The airplane's Cockpit Voice Recorder (CVR), and the Flight Data Recorder (FDR) were removed and shipped to the NTSB CVR/FDR lab in Washington, DC, for download and read out. A factual report for the CVR and the FDR are attached to the docket.

After the airplane was jacked up using airbags and the nose gear extended, an examination of the damage to the belly of the airplane was determined to be minor.

The airplane was towed to a fixed base operator-(FBO) to prepare the airplane for a ferry flight to one of the operator’s maintenance facilities.

On May 26, 2010, the airplane was flown from ONT to Fresno, California, on a ferry permit.

On May 27 and 28, 2010, investigators examined the airplane's landing gear systems. The nose landing gear was removed from the airframe and shipped to the manufacturer for further examination. A copy of the inspection with the observations and findings are attached to the docket.

Investigators convened at the Messier-Dowty, the manufacturer of the nose landing gear on August 1, 2010. An examination of the landing gear was accomplished and a copy of the report is attached to the docket.

Hydraulic samples were taken from the (3) nose gear landing servos and submitted for analysis. All results appeared normal, except for the sample from the Uplock Actuator servo, which revealed “PARTICLES APPEAR ABNORMAL AT NAS CLASS 12, NAS CLASS 9 OR BETTER IS RECOMMENDED” All other tests appear normal. After all examinations, the investigation found no abnormalities that would have precluded normal operations of the landing gear system.

Contributing factors

  • cause Malfunction

Conditions

Weather
VMC, wind 250/09kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.