Skip to content

DCA16IA036

2015-12-19 · Seattle, Washington, United States · None · 1 aircraft · Status: Completed

Airport SEA

Current FAA registration · N477AS

Make / Model
BOEING 737-990ER
Year of manufacture
2015 · 0 years old at event
Engine
CFM INTL CFM56-7B27E
Seats / Engines
222 seats · 2 engines
Last airworthiness date
20150613
ADS-B equipped
Yes — Mode-S A5DB2C

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

the flight crew's misidentification of the taxiway as the landing runway.

Factual narrative

On December 19, 2015, about 0831 pacific standard time, Alaska Airlines flight 27, a Boeing 737 airplane, N477AS, landed on taxiway T instead of the intended runway 16C at the Seattle-Tacoma International Airport (SEA), Seattle, Washington. There were no injuries to the 153 passengers and crew onboard and the airplane was not damaged. The flight was conducted under the provisions of 14 Code of Federal Regulations Part 121 as a regularly scheduled passenger flight from Chicago O'Hare International Airport (ORD), Chicago, Illinois, to SEA. Visual meteorological conditions prevailed at the time of the incident. The captain reported that the descent and approach were normal. They had been cleared for the instrument landing system (ILS) approach to runway 16R. Just inside of 5 miles, the tower controller offered runway 16C that had recently opened. The captain lined up the airplane to land on what he believed was 16C. He noted that runways 16C and 16R and taxiway T were wet and reflected the morning sun, whereas 16L and the terminal were in a shadowed area and not readily visible. He further noted that the distance from 16L to 16C is less than the distance between 16C and 16R so it may appear that 16C is the left runway with taxiway T being the middle runway. The captain suggested that runway lead-in lights should remain on to prevent future similar events. The first officer reported that both pilots were focused on landing what they thought was runway 16C, but was taxiway T. Although the first officer had retuned the captain's ILS for 16C, he was puzzled that the flightpath indicator showed on-glideslope while the localizer showed off course. Although he casually mentioned the discrepancy, since they were visually aligned with the runway, he did not give it further attention. The first officer noted that he had been focused too much on secondary tasks and neglected the big picture of ensuring the airplane was lined up on the proper runway. The flight crew inadvertently landed on a taxiway that ran parallel to the intended landing runway. About 5 miles from the runway and having been cleared to land on runway 16R, the tower controller asked if the flight would like to sidestep to runway 16C which had recently opened. The flight crew accepted and visually lined up with taxiway T, instead of the intended landing runway 16C. Although visual meteorological conditions were present, the sun was reflecting off taxiway T resulting in the flight crew visually focusing on it during landing. The flight crew and controller did not recognize the error until after landing. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

FAA avdata. C = Cause, F = Factor.

  • — Environmental issues-Conditions/weather/phenomena-Light condition-Glare-Effect on personnel
  • C Personnel issues-Action/decision-Info processing/decision-Identification/recognition-Flight crew - C

Verbatim from NTSB's published report. Source file NTSB_2015_DCA16IA036.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type. All research papers