ASN Wikibase Occurrence # 370338
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Sunday 30 January 2005 |
| Time: | 12:35 LT |
| Type: |  Boeing 737-3H4 |
| Owner/operator: | Southwest Airlines |
| Registration: | N350SW |
| MSN: | 24409/1748 |
| Year of manufacture: | 1989 |
| Total airframe hrs: | 51686 hours |
| Engine model: | General Electric CFM-56 |
| Fatalities: | Fatalities: 0 / Occupants: 46 |
| Aircraft damage: | None |
| Category: | Serious incident |
| Location: | Seattle, WA -
 United States of America
|
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Albuquerque International Airport, NM (ABQ/KABQ) |
| Seattle/Tacoma International Airport, WA (SEA/KSEA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB SEA05IA040
History of this aircraft
Other occurrences involving this aircraft
| 8 September 1993 | N350SW | Southwest Airlines | 0 | St. Louis, MO | |
min |
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 25-Mar-2024 09:36 | ASN Update Bot | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation