FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SkyWest Airlines Flight 3567

24 Dec 2017 · Medford, OR, United States

Bombardier Inc CL600 2D24 900 · Incident: navigation error on approach

From Salt Lake City International Airport (SLC) to Rogue Valley International-Medford Airport (MFR)

Report a problem

Event

NTSB case
OPS18IA003
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
Instrument Meteorological Cond

Bombardier Inc CL600 2D24 900

Aircraft type
Bombardier CL600
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
N162PQ
Onboard fatalities
Unknown
Route
From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Rogue Valley International-Medford Airport (MFR), Medford, OR
Aircraft age
About 9 years (built 2008)
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
Navigation error
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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

After initial contact with the flight, the air traffic controller issued the pilots a clearance to cross the initial approach fix CEGAN at or above 7,800 feet and cleared the flight for the published instrument procedure. The published altitude for the instrument procedure was at or above 10,000 feet from CEGAN until BRKET while established on the arc. The flight crew accepted the ATC clearance, and descended from 12,000 feet to 7,800 feet while established on the arc. The minimum vectoring altitude (MVA) for the airspace containing the arc was 7,800 feet, however, just prior to BRKET the floor of the MVA raised to 8,700 feet. The MVA altitudes as depicted on the radar display are for air traffic control and are not available to flight crews. Interviews with the controller indicated there was an expectation that the pilot would not descend below the 10,000 feet as published despite being assigned the "at or above 7,800 feet" crossing restriction. The controller introduced risk by assigning the lowest altitude in the MVA area containing the fix CEGAN (7,800 feet) and expecting the crew to stop their descent at the higher published altitude of 10,000 feet. There was no operational or procedural advantage gained by assigning the flight crew 7,800 feet when the controller expected the crew to stop at 10,000 feet. Had the controller issued the published altitude of 10,000 feet and issued the approach clearance, the incident likely would not have occurred because the crew could have descended to 10,000 feet and then descended according to the published procedure and not below the MVA for that segment. In the incident sequence, the controller instructed the flight crew to cross the initial approach fix (IAF) CEGAN at 7,800 feet, and, the flight did not become established on the published procedure until after CEGAN when established on the arc. The controller was required to assign an altitude to maintain until being established on the procedure, in this case at or above 10,000 feet as published. When the flight crew received the approach clearance that included a descent below the published altitude, they did not query the controller or stop the descent at the published altitude as required in accordance with 14 Code of Federal Regulations (CFR) Part 121. As a result of the incident, the FAA initiated an education program with briefings and information graphics to the air traffic control workforce to emphasize MVA and MSAW conditions. The topics included the use of MVA maps, assignment of appropriate altitudes, ensuring correct altitudes are maintained, and a reminder to know approach procedures and appropriate altitudes. During the incident investigation, it was determined that an antenna adjacent to the IAF BRKET was not depicted on the Jeppesen produced approach chart for the VOR DME C current on the day the incident. Jeppesen changed the approach chart to reflect the antennae and a new obstacle height of 7,614 feet. Additionally, Jeppesen conducted a review of the terrain surrounding the MFR airport to support produced navigation products.

Probable cause

The incident was caused by the air traffic controller assigning an altitude below the published procedure altitude for the approach segment to be flown prior to the aircraft being established on a published portion of the approach. Contributing to the incident was the flight crew's failure to identify the appropriate altitude for the segment of the approach being flown and query the controller before subsequent decent below the published minimum altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS18IA003
Event ID
20180102X34923
Case number
OPS18IA003
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, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-12-25.
  • API snapshot SHA-256: 34c3522079923f6ac218e5754ec06025dd232ed4e768b52847805aedab9c7814; retrieved 2026-09-16T06:15:17.096Z.