Serious incident Boeing 737-290C (Adv) N740AS,
ASN logo
ASN Wikibase Occurrence # 370274
 
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:Monday 30 October 2006
Time:09:40 LT
Type:Silhouette image of generic B732 model; specific model in this crash may look slightly different    
Boeing 737-290C (Adv)
Owner/operator:Alaska Airlines
Registration: N740AS
MSN: 22578/767
Year of manufacture:1981
Engine model:Pratt & Whitney JT8D-17
Fatalities:Fatalities: 0 / Occupants: 76
Aircraft damage: None
Category:Serious incident
Location:Seattle, WA -   United States of America
Phase: Take off
Nature:Passenger - Scheduled
Departure airport:Seattle/Tacoma International Airport, WA (SEA/KSEA)
Destination airport:Juneau International Airport, AK (JNU/PAJN)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The captain of the Boeing 737 stated that there was a short delay at the gate because of a "cargo issue." The automatic terminal information service broadcast indicated that departures were using runway 34R, either with the full length or from the intersection at taxiway Q. The ground controller cleared the flight to taxi to runway 34R at taxiway Q. During the taxi, the first officer was busy talking with dispatch and completing the flight paperwork while the captain taxied the airplane and handled the ATC communications. The flight crew received the amended flight release as the airplane approached taxiway Q. The captain then switched to the local control frequency and heard the local controller (LC) issue the flight clearance to taxi into position and hold on runway 34C. The captain read back the clearance, including "runway 34 center." As the FO was completing the preflight activities, the LC cleared the flight for takeoff from runway 34C and indicated that there was traffic on short final. The captain again repeated the clearance for takeoff on runway "34 center." However, the captain lined up the airplane on the 34R centerline and transferred control to the FO. The airplane departed uneventfully. The LC noticed the airplane departing on runway 34C and did not order an abort because there were no potential traffic conflicts.


Probable Cause: the flight crew's failure to cross-check and verify that the airplane was on the correct runway before takeoff. Contributing to the incident was the flight crew's self-induced pressure to heed the takeoff clearance during a period of increased workload.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: DCA07IA008
Status: Investigation completed
Duration: 1 year and 7 months
Download report: Final report

Sources:

NTSB DCA07IA008

Location

Revision history:

Date/timeContributorUpdates
25-Mar-2024 08:56 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