Boeing 737-700 and Airbus Industrie A330-200 incident near Seattle, Washington, July 3, 2008
On July 3, 2008 at about 5:36 am local time, 2 aircraft, Boeing 737-700 (N339AT) and Airbus Industrie A330-200 (N857NW), were involved in the same incident near Seattle, Washington (Seattle-Tacoma Intl airport). No one was hurt; 314 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The flight crew's diverted attention during taxi. Contributing to the incident was the air traffic control clearance was not followed.
The diverted attention during taxi of the flight crew in the other aircraft. Contributing to the incident was the air traffic control clearance was not followed by the flight crew of the other aircraft.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 3, 2008 · about 5:36 am local time
- Place
- Seattle, Washington · Seattle-Tacoma Intl · map
- Type
- Incident
- Injuries
- No one was hurt; 314 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Boeing 737-700 · all 737-700s on the register
- Registration
- N339AT · no longer on the register
- Damage
- Not recorded
- Flight
- Flight · scheduled airline rules (Part 121)
- Aircraft 2
- Airbus Industrie A330-200 · all A330-200s on the register
- Registration
- N857NW · registry record
- Damage
- Not recorded
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative for the Boeing 737-700 final · quoted from the NTSB record
After the Boeing 737 landed on runway 34C, the airplane exited the runway via high-speed taxiway F, rolled passed the illuminated hold short line for runway 34R and finally stopped on runway 34R as an Airbus A330 few almost directly overhead. The Boeing 737 flight crew had acknowledged two hold short clearances from the tower controller, but never saw the hold short line. After making the landing using idle reverse power, the first officer steered the airplane onto the taxiway, gave control to the captain, ran the "After Landing" checklist, and shut down the right engine. During this time, the captain was consulting his airport diagram while taxiing. Elapsed time from weight-on-wheels to right engine shutdown was 40 seconds. The Airbus A330 flight crew did not see the other airplane and was not aware of the conflict. After the over flight, the Boeing 737 continued across runway 34R and taxied to the gate. During the Boeing 737 approach in visual conditions, runway 34R would have been visible and the tower controllers takeoff clearance to the flight crew of the Airbus A330 was audible, but the crew of the Boeing 737 disregarded this information. The hold short markings, in-pavement lights and elevated guard lights were visible and illuminated but the flight crew of the Boeing 737 did not notice them. It is the policy of the operator of the Boeing 737 to minimize fuel burn by conducting idle reverse landings and by taxiing on one engine when possible.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Airbus Industrie A330-200 final · quoted from the NTSB record
After the Boeing 737 landed on runway 34C, the airplane exited the runway via high-speed taxiway F, rolled passed the illuminated hold short line for runway 34R and finally stopped on runway 34R as an Airbus A330 few almost directly overhead. The Boeing 737 flight crew had acknowledged two hold short clearances from the tower controller, but never saw the hold short line. After making the landing using idle reverse power, the first officer steered the airplane onto the taxiway, gave control to the captain, ran the "After Landing" checklist, and shut down the right engine. During this time, the captain was consulting his airport diagram while taxiing. Elapsed time from weight-on-wheels to right engine shutdown was 40 seconds. The Airbus A330 flight crew did not see the other airplane and was not aware of the conflict. After the over flight, the Boeing 737 continued across runway 34R and taxied to the gate. During the Boeing 737 approach in visual conditions, runway 34R would have been visible and the tower controllers takeoff clearance to the flight crew of the Airbus A330 was audible, but the crew of the Boeing 737 disregarded this information. The hold short markings, in-pavement lights and elevated guard lights were visible and illuminated but the flight crew of the Boeing 737 did not notice them. It is the policy of the operator of the Boeing 737 to minimize fuel burn by conducting idle reverse landings and by taxiing on one engine when possible.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Boeing 737-700 from the NTSB's investigation tables, in plain English
What happened, in order
- Airport occurrence during taxi (from runway) defining event
The NTSB's findings
- factor Personnel issues › Task performance › Communication (personnel) › Following instructions › Flight crew
- cause Personnel issues › Psychological › Attention/monitoring › Attention › Flight crew
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land
- Flight time: 17,500 hours in all; 7,000 in this make and model; 12,000 as pilot in command
- Seat: left
- Injury: no injuries
Crew member
- Certificate: airline transport pilot, commercial pilot
- Seat: rgt
- Injury: no injuries
The aircraft
- Landing gear: fixed
- Engine:; 0 hours total
The flight
- Departed from: BWI Baltimore MD at 11:59 pm
- Destination: SEA Seattle WA
- Flight plan: IFR
- Runway 34C, 9,426 ft by 150 ft
Weather at the time
- Light: night
- Wind: from 200° at 4 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 20,000 ft; a few clouds at 12,000 ft
- Temperature: 73°F (23°C), dew point 61°F (16°C)
- Altimeter: 29.87 inHg
- Observation at 4:53 am from SEA
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 3 | |||
| Flight crew | 2 | |||
| Passengers | 120 |
The factual record for the Airbus Industrie A330-200 from the NTSB's investigation tables, in plain English
What happened, in order
- Airport occurrence during takeoff defining event
The NTSB's findings
- cause Personnel issues › Psychological › Attention/monitoring › Attention › Pilot of other aircraft
- factor Personnel issues › Task performance › Communication (personnel) › Following instructions › Pilot of other aircraft
Pilot
- Certificate: airline transport pilot, commercial pilot
- Seat: left
- Injury: no injuries
Co-pilot
- Seat: rgt
- Injury: no injuries
The aircraft
- Landing gear: fixed
- Engine:; 0 hours total
The flight
- Departed from: KSEA Seattle WA
- Destination: EGLL London Lhr
- Flight plan: IFR
- Runway 34R, 11,901 ft by 150 ft
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 9 | |||
| Flight crew | 3 | |||
| Passengers | 177 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.