FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Boeing 737-3H4 incident

30 Jan 2005 · Seattle, WA, United States

Boeing 737-3H4 · Incident on approach

From Albuquerque International Sunport (KABQ) to Seattle–Tacoma International Airport (KSEA)

Report a problem

Event

NTSB case
SEA05IA040
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

Boeing 737-3H4

Aircraft type
Boeing 737
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
N350SW
Onboard fatalities
Unknown
Route
From Albuquerque International Sunport (KABQ), Albuquerque, NMTo 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
Part 121: Air Carrier
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
Approach · VFR pattern final
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 › Visual lookout, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The First Officer, who was the flying flight crew member during the approach, inadvertently aligned the aircraft with the paved surface of the parallel taxiway as he rolled out on final for a visual approach. He then continued the approach until he noticed the large yellow "X" just off the north end of the taxiway. At that point he realized that the surface that he intended to land on was not an operational runway, so he decided to initiate a go-around. After completing a successful go-around, the flight crew received vectors to a second visual approach final, whereupon they completed an uneventful full-stop landing. Although the FAA Control Tower had the Runway End Identifier Lights (REIL's) for both parallel runways on, the flight crew did not see them during this approach. When they came around for the second approach, the tower had turned on the sequencing approach flashers (rabbit), and it was at that time that they first saw the REIL's for either runway. Both flight crew members said that although the paved surfaces where wet and a little shiny (from an earlier shower), they felt it was the shape, size, and color of the taxiway surface that most directly contributed to the misidentification of the taxiway as a runway. This incident was the eighth in a series of known events wherein flight crews inadvertently aligned their aircraft with the subject taxiway with the intent to land on its surface. During three of these events the aircrews completed their landings on the taxiway surface. Although the airport operations personnel and the local FAA Airports Inspector are aware of this series of events, no markings or visual cues have been placed directly on the taxiway surface to assist crews in more easily identifying Taxiway Tango as a taxiway and not a runway.

Probable cause

The flight crew's failure to maintain an adequate visual lookout while on final for a visual approach. Factors include the failure of both airport operations personnel and the local FAA Airports Inspector to insure that some form of identification marking was placed directly on the taxiway surface after the first seven misalignment events.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA05IA040
Event ID
20050209X00169
Case number
SEA05IA040
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: 7668934c077bd54594d2a7c690e349facece28d18466327d31c1d95f7b71cfa3; retrieved 2026-09-18T15:07:27.105Z.
  • The NTSB's operator name is blank for N350SW; the operator shown is the name the NTSB's other records give its FAA operator code, SWAA.