Air Canada Jazz de Havilland DHC-8 incident
de Havilland DHC-8 · Incident during landing
From Vancouver International Airport (CYVR) to Seattle–Tacoma International Airport (KSEA)
Event
- NTSB case
- SEA04IA035
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- Visual Meteorological Cond
de Havilland DHC-8
- Aircraft type
- de Havilland DHC-8
- 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
- C-GTAQ
- Operator
- Air Canada Jazz
- Onboard fatalities
- Unknown
- Route
- From Vancouver International Airport (CYVR), Vancouver, BCTo Seattle–Tacoma International Airport (KSEA), Seattle, WA
- Aircraft age
- Not recorded
- 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
- Non-U.S., Commercial
- 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
- Landing
- First occurrenceThe 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
- Miscellaneous/other
- 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
- Flightcrew › Wrong runway, inadvertent use
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight crew was cleared by Seattle Center for a visual approach to Runway 16 Right. They contacted Seattle-Tacoma Tower when they were near Elliot Bay, and were cleared to land on Runway 16 Right, number two behind a 737 that was then touching down. Because of the distance between their position and the preceding 737, neither flight crew member saw the aircraft they were sequenced behind. The Captain, who was flying at the time, therefore aligned the aircraft with what he felt sure was Runway 16 Right. He then continued on the approach, and completed what to him seemed to be an uneventful landing. Soon after the aircraft touched down, the tower advised the flight crew that they had landed on Taxiway Tango. The Captain said that when they lined up on final approach, there was an overcast over the approach end of the runway (which was dry), bright sunshine to the south of the airport, and a glare on the runway surface. According to him, this caused the area around the approach end of the runway to appear as one dark color (shadow), making it hard to differentiate between Runway 16 Right and Taxiway Tango. He further stated that he had been into Seattle-Tacoma Airport many times before, and was aware of the large "X" just off the north end of Taxiway Tango. But, according to the Captain, because of the contrast between the runway glare and the dark area around the approach end, he did not notice that he had flown over the "X" just prior to touching down on the taxiway.
Probable cause
The flight crew's misidentification of the parallel taxiway as the active runway, resulting in the flight crew executing a landing on the taxiway. Factors include sun glare and shadows around the runway/taxiway environment, and visual illusions created by the airport surface environment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04IA035
- Event ID
- 20040128X00118
- Case number
- SEA04IA035
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1cfba0dcace3bfea62787ed4b589a6f4fa3dfd6b0f191fcc88162e276d9efddc; retrieved 2026-09-18T15:31:16.305Z.