FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SkyWest Airlines Flight 6467

23 May 2010 · Ontario, CA, United States

Bombardier Inc CL-600-2B19 · Incident: system/component malfunction/failure (non-power) during landing

From San Francisco International Airport (SFO) to Ontario International Airport (ONT)

Report a problem

Event

NTSB case
WPR10IA256
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 Inc 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
N925SW
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo Ontario International Airport (ONT), Ontario, 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
Landing
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 systems
  • Not determined › Not determined

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

NTSB narrative

After the pilots extended the airplane’s landing gear in preparation for landing, they observed an unsafe nose landing gear indication and performed a go-around to try to correct the situation. The pilots followed the emergency procedures in the operator’s Quick Reference Handbook but were unable to lower the nose landing gear. The pilots then performed a low-level flyby so air traffic control tower (ATCT) and ground personnel could evaluate the condition of the nose landing gear. When ATCT and ground personnel confirmed that the landing gear doors were open and the nose landing gear remained retracted, the pilots decided to make an emergency landing with the nose landing gear retracted. After the main landing gear touched down, the captain held the nose off the ground as long as possible, in accordance with company procedures. The airplane slid about 2,000 feet after the nose settled to the runway before coming to a stop. During the recovery process, the nose landing gear was extended. Postaccident examination revealed no abnormalities that would have precluded normal operation of the nose landing gear system.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10IA256
Event ID
20100523X62317
Case number
WPR10IA256
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: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: bb2333ac112465d1f5c82944b2ebcb59d6e834223f1ada7428c0b0e3039cfa82; retrieved 2026-09-15T14:11:30.792Z.