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

Bombardier INC DHC 8 402 incident near Pullman, Washington, December 30, 2017

On December 30, 2017 at about 2:40 am local time, a 2002 Bombardier INC DHC 8 402, registered N412QX, was involved in an incident during landing (flare/touchdown) near Pullman, Washington (Pullman/Moscow Rgnl airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 46 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

the flight crew's misidentification of the taxiway as the landing runway due to the failure of the runway lighting that caused only the taxiway lights to be illuminated.

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

What the record shows

Date
December 30, 2017 · about 2:40 am local time
Place
Pullman, Washington · Pullman/Moscow Rgnl · map
Type
Incident
Injuries
No one was hurt; 46 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Bombardier INC DHC 8 402 402, built 2002
Registration
N412QX · no longer on the register · serial 4059
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)

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

This incident occurred when Horizon flight 2184 landed on a parallel taxiway to runway 6 at Pullman/Moscow Regional Airport (PUW), Pullman, Washington. Pullman/Moscow Airport was not served by an air traffic control tower (i.e. an uncontrolled airport). The runway lighting at KPUW was not operating at the time of the incident and there was no NOTAM regarding the inoperative lights.  However, at the time of landing, the taxiway lights on the parallel taxiway were operational. The lighting system had been tested about two hours prior to the incident landing but airport personnel did not notice the runway lights were not functioning until informed by the flight crew.  Following the incident landing, airport personnel found that the runway lighting wiring vaults were flooded, likely from recent heavy rains and snow from the previous day, and issued a NOTAM that the runway lights were inoperative.   As the flight proceeded inbound, the captain could not determine whether the lights were on bright or dim and indicated that he keyed the radio to increase the lighting, but was uncertain if the intensity had changed. The captain disengaged the autopilot soon after calling runway in sight when the airplane was about 4.5 miles from the runway 6 threshold after he thought he saw the actual runway.  The captain stated he then looked down to check that the gear was down and, as he looked back out, saw nothing but black in front of the airplane before identifying pavement that was lit up. He stated he then smoothly slid the airplane over a little to line up with the illuminated pavement.  He stated that he thought he had aligned with the runway. The flight crew noticed they were on a taxiway as they were in the flare and touching down on the pavement. During the taxi to the terminal, the flight crew again attempted to illuminate the runway lights via the CTAF with no success, only the taxiway lights changed illumination intensity. Although some cues, such as the taxiway light color and alignment of the PAPI relative to the intended landing surface, were available to the flight crew to distinguish the taxiway from the from nonilluminated runway, sufficient cues also existed, such as a single lighted paved surface similar in width to the runway, to confirm the crew's expectation that the airplane was aligned with the intended landing runway. As a result, once the airplane was aligned with what the flight crew thought was the correct landing surface, they were likely not strongly considering contradictory information.  Once the flight had exited the clouds, the flight crew had expected to see an illuminated runway.  The taxiway and runway were about 200 feet apart, and only a small correction while in flight would be required to align the aircraft with the taxiway.  The captain indicated that after the runway was in sight, he focused on the runway surface, and not the lighting until the airplane had landed on the taxiway. The NTSB concludes that the cues available to the flight crew to indicate that the airplane was aligned with a taxiway were not sufficient to overcome their belief, as a result of expectation bias, that the illuminated taxiway was the intended landing runway.

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. Wrong surface or wrong airport during landing (flare/touchdown) defining event

The NTSB's findings

  • factor Environmental issues › Operating environment › Airport facilities/design › Airport lighting › Contributed to outcome
  • cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Flight crew

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 13,528 hours in all; 5,997 in this make and model; 117 in the last 90 days; 67 in the last 30 days; 8,079 as pilot in command
  • Last flight review: November 28, 2017
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,582 hours in all; 95 in this make and model; 95 in the last 90 days; 42 in the last 30 days; 1,428 as pilot in command
  • Last flight review: December 24, 2017
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 38,496 hours
  • Last inspection: continuous airworthiness programme
  • Maximum gross weight: 64,501 lb
  • Seats: 76
  • Landing gear: retractable
  • Engine 1: P&W Canada PW150A (turboprop); 35,381 hours total
  • Engine 2: P&W Canada PW150A (turboprop); 20,400 hours total
  • Operator: Horizon Air Industries INC

The flight

  • Departed from: SEA Seattle WA at 1:48 am
  • Destination: PUW Pullman WA
  • Flight plan: IFR
  • Runway 06, 6,730 ft by 100 ft

Weather at the time

  • Light: night, dark
  • Wind: from 150° at 10 knots
  • Visibility: 5 statute miles
  • Sky: broken clouds at 3,000 ft; a few clouds at 2,400 ft
  • Temperature: 39°F (4°C), dew point 36°F (2°C)
  • Altimeter: 29.86 inHg
  • Observation at 2:53 am from KPUW

Injuries

FatalSeriousMinorNone
Cabi2
Flight crew2
Passengers42

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

24 documents, released by the NTSB on October 2, 2018. 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 Operations Group Chairman's Factual Report PDF, 35 pages View Download
2 Operations Attachment 1 – Interview Summaries PDF, 61 pages View Download
3 Operations Attachment 2 - Flight Release and Weather Packet PDF, 18 pages View Download
4 Operations Attachment 3 - N412QX Maintenance Logbook PDF, 8 pages View Download
5 Operations Attachment 4 - Captain Training History PDF, 10 pages View Download
6 Operations Attachment 5 - Fo Training History PDF, 3 pages View Download
7 Operations Attachment 6 - Captain Trip Pairing and Monthly Schedule PDF, 5 pages View Download
8 Operations Attachment 7 - Fo Trip Pairing and Monthly Schedule PDF, 2 pages View Download
9 Operations Attachment 8 - Horizon Air Q400 Descent Flow PDF, 2 pages View Download
10 Operations Attachment 9 - Horizon Air Q400 Normal Checklist PDF, 3 pages View Download
11 Operations Attachment 10 - Horizon Air Q400 RNAV Approach Guidance PDF, 10 pages View Download
12 Operations Attachment 11 - Horizon Air Q400 RNAV Approach Profile PDF, 8 pages View Download
13 Operations Attachment 12 - Horizon Air Q400 Sops for Landing PDF, 2 pages View Download
14 Operations Attachment 13 - Q400 Amplified Approach Checklist PDF, 2 pages View Download
15 Operations Attachment 14 - Puw Airport Information Chart PDF, 4 pages View Download
16 Operations Attachment 15 - Sea Simulator Observation PDF, 42 pages View Download
17 Operations Attachment 16 - Party Forms PDF, 5 pages View Download
18 Operations Attachment 17 - NTSB Safety Letter PDF, 3 pages View Download
19 Operations Attachment 18 - Horizon Air Response to NTSB Safety Letter PDF, 2 pages View Download
20 Operations Attachment 19 - Horizon Air CRM Policy PDF, 4 pages View Download
21 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
22 Flight Data Recorder Specialist's Factual Report PDF, 6 pages View Download
23 Flight Data Recorder - Attachment 1 data file Download
24 Cockpit Voice Recorder Factual Report PDF, 5 pages View Download

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

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.