The U.S. aircraft register, updated daily
Accidents · NTSB OPS18IA003 · Final report

Bombardier INC CL600 2D24 incident near Medford, Oregon, December 25, 2017

On December 25, 2017 at about 2:08 am local time, a 2008 Bombardier INC CL600 2D24, registered N162PQ, was involved in an incident during approach (IFR initial approach) near Medford, Oregon (Rogue Valley International airport). It was flown under scheduled airline rules (Part 121). The NTSB record does not give the injuries. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 12, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 25, 2017 · about 2:08 am local time · cases in 2017
Place
Medford, Oregon · Rogue Valley International · cases near this airport · map
Type
Incident
Injuries
The NTSB record does not give the injuries.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Bombardier INC CL600 2D24 900, built 2008
Registration
N162PQ · registry record · serial 15162
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Terrain avoidance alert during approach
  2. Air traffic event during approach
  3. Navigation error during approach (IFR initial approach) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › ATC personnel

The aircraft

  • Airframe total time: 24,912.5 hours
  • Last inspection: continuous airworthiness programme, December 22, 2017
  • Seats: 80
  • Landing gear: retractable
  • Engine 1: Ge CF34-8B5 (turbojet); 26,388 hours total
  • Engine 2: Ge CF34/8C5 (turbojet); 25,913 hours total
  • Operator: Skywest Airlines INC

The flight

  • Departed from: SLC Salt Lake City UT
  • Destination: MFR Medford OR
  • Flight plan: IFR
  • Runway 32, 8,800 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: dusk
  • Visibility: 10 statute miles
  • Sky: overcast at 7,000 ft; not recorded
  • Temperature: 43°F (6°C), dew point 37°F (3°C)
  • Altimeter: 30.17 inHg
  • Observation at 1:53 am from KMFR, 27 miles away

Documents from the investigation the NTSB's docket: the evidence folder behind the report

19 documents, released by the NTSB on March 31, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Air Traffic Control Factual Report PDF, 16 pages View Download
2 Air Traffic Control Attachment 1 Controller Summaries PDF, 13 pages View Download
3 Air Traffic Control Factual Report Attachment 2 Mor PDF, 4 pages View Download
4 Air Traffic Control Factual Attachemnt 3 Ssr PDF, 6 pages View Download
5 Air Traffic Control radar File zip file Download
6 Air Traffic Control Communications zip file Download
7 Operational Factors Group Chairman Factual Report PDF, 46 pages View Download
8 Operational Factors Attachment 1 - Flight Crew Interview Summaries PDF, 18 pages View Download
9 Operational Factors Attachment 2- NTSB 6120.1 Form PDF, 11 pages View Download
10 Operational Factors Attachment 3 - Flight Crew Schedule - Previous 90 Days PDF, 11 pages View Download
11 Operational Factors Attachment 4 - Flight Crew Training Records [excerpts] PDF, 4 pages View Download
12 Operational Factors Attachment 5 - Incident Flight Dispatch Release PDF, 43 pages View Download
13 Operational Factors Attachment 6 - Medford Weather PDF, 2 pages View Download
14 Operational Factors Attachment 7 - Skywest Airlines Standard Operating Procedures Manual [excerpts] PDF, 14 pages View Download
15 Operational Factors Attachment 8 - Skywest Airlines Approach Briefing PDF, 7 pages View Download
16 Operational Factors Attachment 10 - Skywest 10-7 Page and VOR Dme-c Chart PDF, 4 pages View Download
17 Operational Factors Attachment 11 - Honeywell Mark V and Vii EGPWS Pilots Guide [excerpts] PDF, 9 pages View Download
18 Operational Factors Attachment 12 - Honeywell Terrain Warning Alert at Medford PDF, 6 pages View Download
19 Operational Factors Attachment 13 - Group Party Forms PDF, 16 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/OPS18IA003.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.