FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SkyWest Airlines Flight 5086

14 Dec 2016 · San Francisco, CA, United States

Bombardier Inc CL 600 2B19 100 and United Air Lines Boeing 737 924ER · Incident: runway incursion (vehicle, aircraft or person) while taxiing

Report a problem

Event

NTSB case
OPS17IA008
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
Event fatalities
Unknown
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

Aircraft 1 · Bombardier Inc CL 600 2B19 100

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
N986SW
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo Ontario International Airport (ONT), Ontario, CA
Aircraft age
About 12 years (built 2004)
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
Taxi · to runway
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
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Aircraft 2 · Boeing 737 924ER

Aircraft type
Boeing 737
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
UNK
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo not recorded
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
Takeoff
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
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Personnel issues › Action/decision

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

NTSB narrative

The runway incursion occurred when a CRJ inadvertently turned onto a highspeed exit taxiway and entered a runway after a Boeing 737 was cleared for takeoff on the same runway. Air traffic control ground controller issued the pilots of the CRJ taxi instructions to runway 28L from their ramp exit point. The instructions included clearance to cross runway 1 left and runway 1 right. Subsequently, the ground controller issued revised taxi instructions requiring the pilots to taxi on the taxiway closest to but parallel to runway 28L, then make a slight right turn to another taxiway to taxi to the approach end of runway 28L. During the taxi, the captain made a left turn onto a runway 28L highspeed exit and began to cross the runway hold short line, instead of making the slight right turn required to follow their taxi clearance. The captain reported that "something did not feel right" and stopped the airplane as the ground controller commanded the CRJ to stop. Although the captain of the CRJ had taxied at San Francisco International Airport (SFO) "many times" and was familiar with a hotspot in the area he made the mistaken turn, he had no explanation as to why he turned left at that point in the taxi. Recorded data indicated that the B737 passed in front of the CRJ within 188 feet laterally. The pilots of the B737 did not observe the CRJ during the takeoff roll. A review of air traffic control procedures and equipment showed that appropriate procedures were followed and there were no irregularities noted with the equipment. Federal Aviation Administration guidance on taxiway design indicated that complex intersections increase the possibility of pilot error. It offered the "three-node concept" which means that a pilot is presented with no more than three choices at an intersection. The intersection where the incursion began contained five choices: a left turn, a slight left turn, straight, slight right turn, and a right turn. After this incident, SFO placed temporary barricades at this intersection preventing its use before permanently closing the taxiway. Following this event, SkyWest Airlines developed and disseminated, on January 19, 2017, a "Flight Operations Message" to all pilots titled "Surface Movement Safety – Preventing Incursions" discussing the events surrounding this event and what crews should do to be vigilant.

Although the area in which this incident occurred may have contributed to the captain’s mistaken turn, it was designated as a hot spot location that required enhanced crew vigilance during wayfinding through this area. Further, there were multiple cues at the intersection before the turn was made that could be used by the pilots to support the wayfinding task. Finally, the taxiway in which the captain mistakenly turned had signs, marking, and lighting to indicate both the identification of the taxiway and the identification of and presence of a runway and the fact it was active. These cues were not heeded by either pilot before the airplane entered the runway.

Probable cause

The captain’s inadvertent turn onto the incorrect taxiway and subsequent entry onto an active runway without a clearance, which resulted in the runway incursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS17IA008
Event ID
20161219X82155
Case number
OPS17IA008
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, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-12-15.
  • API snapshot SHA-256: 03827409865045a72c102475061dab9c8baf81825307453da174075d9cbaeac7; retrieved 2026-09-13T18:26:15.254Z.