Aviation Crash Map

Bombardier CL600 2D24 N162PQ

25 December 2017 · Medford, Oregon, United States · Unknown

Summary

On 25 December 2017 at about 02:08 local time, a Bombardier CL600 2D24 registered N162PQ, operated by Skywest Airlines Inc, was involved in an incident near Medford, Oregon, United States. The number of people on board was not recorded. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 02:08
Classification
Incident
Location
Medford, Oregon, United States
Nearest airport
Rogue Valley International (MFR)
Coordinates
42.0472, -122.7436
Aircraft
Bombardier CL600 2D24
Registration
N162PQ
Category
Airplane
Year built
2008
Engines
2
Operating rule
Part 121: Air Carrier
Phase of flight
Not recorded
Route
Salt Lake City → Medford
Aircraft damage
Not recorded
Weather
IMC
Light
Dusk
NTSB number
OPS18IA003

People

Injuries not recorded.

On board Died Serious Minor Uninjured
Not recorded 0 0 0 0

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.

Other Bombardier CL600 accidents

Date Aircraft Location Operator Outcome Died
27 Jan 2016 Bombardier CL600 2D24
N316PQ
Detroit, Michigan, United States Endeavor Air Unknown -
17 Apr 2016 Bombardier CL600 2C10
JA06RJ
Fukuoka, Japan
no coordinates
- Unknown -
1 May 2018 Bombardier CL600 2D24
N606LR
Queens, New York, United States Endeavor Air No injuries -
11 Mar 2018 Bombardier CL600 2B16
TC-TRB
Shahr-e Kurd, Iran
no coordinates
- Fatal 11
16 May 2018 Bombardier CL600 2B19
ZS-NMI
Geuteng, South Africa, South Africa
no coordinates
- Unknown -
8 Jan 2016 Bombardier CL600 2B19
SE-DUX
Kiruna, Sweden
no coordinates
West Atlantic Sweden Fatal 2

All 55 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
20 Jun 2017 Van's RV-12
N234VA
Eugene, Oregon, United States Lane Community College No injuries -
14 Jun 2017 Cessna A188
N4877Q
Salem, Oregon, United States Industrial Aviation Services Inc No injuries -
24 Jun 2017 Piper PA 22
N2473P
Pendleton, Oregon, United States - No injuries -
17 Sep 2017 Rudberg Todd W VANS ACFT RV8
N232TB
Manzanita, Oregon, United States - No injuries -
25 Jun 2017 Cessna 172
N79938
Roseburg, Oregon, United States - No injuries -
12 Mar 2017 Cessna 172
N5440H
Hillsboro, Oregon, United States Twin Oaks Airpark Inc No injuries -

All 170,864 records in United States