Serious incident McDonnell Douglas MD-82 N298AA,
ASN logo
ASN Wikibase Occurrence # 370416
 
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:Friday 14 March 2003
Time:18:20 LT
Type:Silhouette image of generic MD82 model; specific model in this crash may look slightly different    
McDonnell Douglas MD-82
Owner/operator:American Airlines
Registration: N298AA
MSN: 49310
Total airframe hrs:51944 hours
Engine model:Pratt & Whitney JT8D-217C
Fatalities:Fatalities: 0 / Occupants: 111
Aircraft damage: None
Category:Serious incident
Location:Seattle, WA -   United States of America
Phase: Landing
Nature:Passenger - Scheduled
Departure airport:Dallas/Fort Worth International Airport, TX (DFW/KDFW)
Destination airport:Seattle/Tacoma International Airport, WA (SEA/KSEA)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
Initially the flight crew planned to execute the visual approach to Runway 16 Right backed up by the ILS, but because there was a ceiling over the final approach course, they were advised to expect the ILS. The flight was then vectored to a 15 mile final and cleared for the ILS approach. About four to five miles from the end of the runway, at about 3,500 feet above the ground (AGL), the flight crew passed through the cloud deck, made visual contact with the runway environment, and transitioned to visual navigation. According to the information collected from the flight data recorder, the aircraft started a constant-rate deviation to the right of the localizer approximately the same time as it broke out of the clouds. During this deviation the flight crew maintained a heading that was taking them directly to the "approach end" of Taxiway Charlie. Neither the Captain nor the First Officer were aware they were lined up on the taxiway, and they did not know they had landed on the taxiway until advised by the tower. A rain shower had recently moved through the area, and although there was an overcast over the center and north end of the airport, south of the field rays of sunlight were shining through holes in the clouds, resulting in a degradation of the visual clues that would normally help the flight crew differentiate between the runway and 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 sunglare from the wet paved surfaces, and a visual illusion created by the airport surface environment.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: SEA03IA046
Status: Investigation completed
Duration: 1 year 1 month
Download report: Final report

Sources:

NTSB SEA03IA046

Location

Revision history:

Date/timeContributorUpdates
25-Mar-2024 10:27 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org