# NTSB SEA05LA184: Airbus Industrie A330-223, N855NW, Portland, OR, August 29, 2005

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: August 29, 2005, 14:09 local (21:09 UTC)
- Place: Portland, OR
- Coordinates: 45.588611, -122.597503
- Nearby events: https://openairdocs.org/map.md?lat=45.5886&lon=-122.5975&mi=10
- Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 270 uninjured
- Status: Completed, report March 28, 2006
- Report: Approved by Office Director
- Parties: FAA FSDO
- NTSB case key (mKey): 62356
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA05LA184
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62356/pdf
- Page: https://openairdocs.org/ntsb/SEA05LA184

## Probable cause (aircraft 2)

The failure of the flightcrew of the other airplane to maintain clearance while taxiing.

## Probable cause (aircraft 1)

The failure of the flight crew to maintain adequate clearance while taxiing.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Collision between aircraft (other than midair), taxi - to takeoff
  - clearance - not maintained, flightcrew (cause)
- Collision between aircraft (other than midair), standing - engine(s) operating
  - clearance - not maintained, flightcrew of other aircraft (cause)

## Analysis (aircraft 2)

The Airbus was taxiing east via Taxiway B to runway 28L for departure.  The Bombardier had landed, taxied to the gate area, and was stopped on the ramp located north of Taxiway B waiting to be marshaled to its parking spot.  The Bombardier was sitting on a northerly heading, oriented perpendicular to Taxiway B with its tail towards the taxiway.  The captain and augmenting captain of the Airbus visually checked for clearance between their left wingtip and the tail of the Bombardier and decided that there was adequate clearance.  However, as the Airbus passed behind the Bombardier, the left wingtip of the Airbus struck the tail of the Bombardier.  The left winglet of the Airbus was scraped, bent and cracked.  The vertical stabilizer, horizontal stabilizer, both elevators, and the rudder of the Bombardier sustained structural damage.

## Analysis (aircraft 1)

The Airbus was taxiing east via Taxiway B to runway 28L for departure.  The Bombardier had landed, taxied to the gate area, and was stopped on the ramp located north of Taxiway B waiting to be marshaled to its parking spot.  The Bombardier was sitting on a northerly heading, oriented perpendicular to Taxiway B with its tail towards the taxiway.  The captain and augmenting captain of the Airbus visually checked for clearance between their left wingtip and the tail of the Bombardier and decided that there was adequate clearance.  However, as the Airbus passed behind the Bombardier, the left wingtip of the Airbus struck the tail of the Bombardier.  The left winglet of the Airbus was scraped, bent and cracked.  The vertical stabilizer, horizontal stabilizer, both elevators, and the rudder of the Bombardier sustained structural damage.

## Factual narrative (aircraft 2)

On August 29, 2005, approximately 1409 Pacific daylight time, an Airbus A330-223, N855NW, was taxiing for takeoff when it collided with a Bombardier DHC-8-202, N363PH, that was standing with engines operating waiting to be marshaled to its parking spot on the Portland International Airport, Portland, Oregon.  There were no injuries to the 3 flight crewmembers, 9 flight attendants, and 235 passengers aboard the Airbus or to the 2 flight crewmembers, 1 flight attendant, and 20 passengers aboard the Bombardier.  There was minor damage to the left winglet of the Airbus and substantial damage to the tail of the Bombardier.  The Airbus was operated by Northwest Airlines as flight number 5, a 14 CFR Part 121 scheduled international passenger flight from Portland to Narita Airport, Japan.  The Bombardier was operated by Horizon Air as flight number 2066, a 14 CFR Part 121 scheduled domestic passenger flight from Medford, Oregon to Portland.  Visual meteorological conditions prevailed, and instrument flight rules flight plans were filed for both flights.

According to information provided by FAA inspectors who responded to the scene of the accident, the Airbus was taxiing east via Taxiway B to runway 28L for departure.  The Bombardier had landed, taxied to the gate area, and was stopped on the ramp located north of Taxiway B waiting to be marshaled to its parking spot.  The Bombardier was sitting on a northerly heading, oriented perpendicular to Taxiway B with its tail towards the taxiway.  As the Airbus passed behind the Bombardier, the left wingtip of the Airbus struck the tail of the Bombardier.  The left winglet of the Airbus was scraped, bent and cracked.  The vertical stabilizer, horizontal stabilizer, both elevators, and the rudder on the Bombardier sustained structural damage.

Portland Air Traffic Control Tower prepared a chronological summary of the event and a transcript of the communications on the ground control frequency.  The chronology indicated that at 1403, the Bombardier contacted ground control stating they had exited the runway at Taxiway B-5 for spot 14, and the ground controller cleared them to taxi to spot 14.  At 1405, the Airbus advised they were ready to taxi, and the ground controller instructed them to taxi to runway 28L.  The transcript indicated that at 1406:40, the ground controller advised the Airbus to "use caution for a dash eight [Bombardier] pulled up ah on taxiway tango by bravo ahead and to your left should have wing tip clearance there."  The Airbus acknowledged the transmission.  At 1408:58, the unidentified transmission, "hey ah northwest are you (unintelligible)" was made.  At 1412:45, the Airbus advised the ground controller that they had hit the Bombardier.

During an interview conducted by FAA inspectors, the captain of the Bombardier reported that the flight's landing and taxi in were normal.  He further reported that the flight was instructed to park in spot 14, and he held on the ramp short of the spot awaiting a marshaler to direct him into the parking spot.  While waiting to be marshaled, the captain heard the ground controller direct the Airbus to taxi behind his airplane.  He then taxied his airplane "as far forward as possible but did not cross the access road due to the missing marshaler."  The captain reported that the Bombardier was stopped when the Airbus passed behind it.  Just prior to the impact, the captain attempted to contact the ground controller, but the impact pulled his hand away from the radio transmit switch.  Following the event, the flight crew shut down the engines, and the passengers exited the Bombardier and walked to the terminal.  There was no emergency evacuation.

According to a written statement submitted by the captain of the Airbus, the flight was cleared to taxi to the runway, and the ground controller commented that the flight should "not have a problem" getting past the Bombardier that was clear of the taxiway on the ramp.  The captain reported that the tail of the Bombardier "appeared to be 20-30 feet outside the taxi line" and that he was "not comfortable" with the Bombardier's position.  As the Airbus approached the Bombardier, the Bombardier "moved forward about another 20-30 feet perpendicularly away from the yellow taxiway edge line."  The captain asked the augmenting captain seated in the jump seat if it looked like they would clear the Bombardier, and the augmenting captain got out of his seat and looked out the left window.  The augmenting captain told the captain that it looked like he would have 10-20 feet of clearance.  The captain reported that he also looked at the left wingtip and thought there was adequate clearance.  According to the captain, the nose wheel of the Airbus was slightly right of the taxiway centerline when he passed behind the Bombardier.  The captain felt a "shudder" and stopped the airplane.  Following the event, the Airbus taxied back to the gate, and the passengers de-planed.  Written statements submitted by the first officer and the augmenting captain of the Airbus collaborated the captain's statement.

When FAA inspectors reached the scene, the Airbus was parked at the gate, and the Bombardier had not been moved since the collision.  FAA inspectors measured the distance between the Bombardier's nose wheel and the centerline of Taxiway B as approximately 150 feet.  According to information provided by Horizon Air, the distance from the nose wheel to the tip of the Bombardier's tail was approximately 67 feet.  This placed the tip of the Bombardier's tail approximately 83 feet from the centerline of Taxiway B.  According to information provided by Northwest Airlines, the wingspan of the Airbus was 197 feet 10 inches.  With the nose wheel of the Airbus on the centerline of the taxiway, the tip of the left wing would have been located 98 feet 10 inches left of the centerline.

## Factual narrative (aircraft 1)

On August 29, 2005, approximately 1409 Pacific daylight time, an Airbus A330-223, N855NW, was taxiing for takeoff when it collided with a Bombardier DHC-8-202, N363PH, that was standing with engines operating waiting to be marshaled to its parking spot on the Portland International Airport, Portland, Oregon.  There were no injuries to the 3 flight crewmembers, 9 flight attendants, and 235 passengers aboard the Airbus or to the 2 flight crewmembers, 1 flight attendant, and 20 passengers aboard the Bombardier.  There was minor damage to the left winglet of the Airbus and substantial damage to the tail of the Bombardier.  The Airbus was operated by Northwest Airlines as flight number 5, a 14 CFR Part 121 scheduled international passenger flight from Portland to Narita Airport, Japan.  The Bombardier was operated by Horizon Air as flight number 2066, a 14 CFR Part 121 scheduled domestic passenger flight from Medford, Oregon to Portland.  Visual meteorological conditions prevailed, and instrument flight rules flight plans were filed for both flights.

According to information provided by FAA inspectors who responded to the scene of the accident, the Airbus was taxiing east via Taxiway B to runway 28L for departure.  The Bombardier had landed, taxied to the gate area, and was stopped on the ramp located north of Taxiway B waiting to be marshaled to its parking spot.  The Bombardier was sitting on a northerly heading, oriented perpendicular to Taxiway B with its tail towards the taxiway.  As the Airbus passed behind the Bombardier, the left wingtip of the Airbus struck the tail of the Bombardier.  The left winglet of the Airbus was scraped, bent and cracked.  The vertical stabilizer, horizontal stabilizer, both elevators, and the rudder on the Bombardier sustained structural damage.

Portland Air Traffic Control Tower prepared a chronological summary of the event and a transcript of the communications on the ground control frequency.  The chronology indicated that at 1403, the Bombardier contacted ground control stating they had exited the runway at Taxiway B-5 for spot 14, and the ground controller cleared them to taxi to spot 14.  At 1405, the Airbus advised they were ready to taxi, and the ground controller instructed them to taxi to runway 28L.  The transcript indicated that at 1406:40, the ground controller advised the Airbus to "use caution for a dash eight [Bombardier] pulled up ah on taxiway tango by bravo ahead and to your left should have wing tip clearance there."  The Airbus acknowledged the transmission.  At 1408:58, the unidentified transmission, "hey ah northwest are you (unintelligible)" was made.  At 1412:45, the Airbus advised the ground controller that they had hit the Bombardier.

During an interview conducted by FAA inspectors, the captain of the Bombardier reported that the flight's landing and taxi in were normal.  He further reported that the flight was instructed to park in spot 14, and he held on the ramp short of the spot awaiting a marshaler to direct him into the parking spot.  While waiting to be marshaled, the captain heard the ground controller direct the Airbus to taxi behind his airplane.  He then taxied his airplane "as far forward as possible but did not cross the access road due to the missing marshaler."  The captain reported that the Bombardier was stopped when the Airbus passed behind it.  Just prior to the impact, the captain attempted to contact the ground controller, but the impact pulled his hand away from the radio transmit switch.  Following the event, the flight crew shut down the engines, and the passengers exited the Bombardier and walked to the terminal.  There was no emergency evacuation.

According to a written statement submitted by the captain of the Airbus, the flight was cleared to taxi to the runway, and the ground controller commented that the flight should "not have a problem" getting past the Bombardier that was clear of the taxiway on the ramp.  The captain reported that the tail of the Bombardier "appeared to be 20-30 feet outside the taxi line" and that he was "not comfortable" with the Bombardier's position.  As the Airbus approached the Bombardier, the Bombardier "moved forward about another 20-30 feet perpendicularly away from the yellow taxiway edge line."  The captain asked the augmenting captain seated in the jump seat if it looked like they would clear the Bombardier, and the augmenting captain got out of his seat and looked out the left window.  The augmenting captain told the captain that it looked like he would have 10-20 feet of clearance.  The captain reported that he also looked at the left wingtip and thought there was adequate clearance.  According to the captain, the nose wheel of the Airbus was slightly right of the taxiway centerline when he passed behind the Bombardier.  The captain felt a "shudder" and stopped the airplane.  Following the event, the Airbus taxied back to the gate, and the passengers de-planed.  Written statements submitted by the first officer and the augmenting captain of the Airbus collaborated the captain's statement.

When FAA inspectors reached the scene, the Airbus was parked at the gate, and the Bombardier had not been moved since the collision.  FAA inspectors measured the distance between the Bombardier's nose wheel and the centerline of Taxiway B as approximately 150 feet.  According to information provided by Horizon Air, the distance from the nose wheel to the tip of the Bombardier's tail was approximately 67 feet.  This placed the tip of the Bombardier's tail approximately 83 feet from the centerline of Taxiway B.  According to information provided by Northwest Airlines, the wingspan of the Airbus was 197 feet 10 inches.  With the nose wheel of the Airbus on the centerline of the taxiway, the tip of the left wing would have been located 98 feet 10 inches left of the centerline.

## Aircraft 1

- Registration: [N855NW](https://openairdocs.org/aircraft/N855NW), registered now, S/N 0621, built 2004 (OpenAirDocs)
- Reported make and model: Airbus Industrie A330-223
- Registry model: [Airbus A330-223](https://openairdocs.org/model/airbus-a330-223) (registry code 3940031) (OpenAirDocs)
- Registry engine: [Pratt & Whitney PW4000 series](https://openairdocs.org/engine/pratt-whitney-pw4000-series) (registry code 52119, turbo-fan) (OpenAirDocs)
- Category: Airplane
- Serial number: 0621
- Airframe hours: 4125
- Engines: Pratt & Whitney PW-4168A turbo fan; Pratt & Whitney PW-4168A turbo fan
- Damage: Minor damage
- Flight: Part 121
- Registered owner: Northwest Airlines
- Airworthiness certificate: Standard, Transport
- Last inspection: August 1, 2005, 0 hours before
- Departed: PDX, Portland, OR
- Destination: NRT, Narita
- Flight plan: IFR
- Airport: PDX, Portland International

## Aircraft 2

- Registration: [N363PH](https://openairdocs.org/aircraft/N363PH), registered now, S/N 520, built 1998 (OpenAirDocs)
- Reported make and model: Bombardier, Inc. DHC-8-202
- Registry model: [Bombardier DHC-8-202](https://openairdocs.org/model/bombardier-dhc-8-202) (registry code 1390007) (OpenAirDocs)
- Registry engine: [Pratt & Whitney Canada PW123](https://openairdocs.org/engine/pratt-whitney-canada-pw123) (registry code 52129, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 520
- Airframe hours: 16229
- Engines: Pratt & Whitney PW-1230 2150 horsepower turbo prop; Pratt & Whitney PW-1230 2150 horsepower turbo prop
- Damage: Substantial damage
- Flight: Part 121
- Operator: Horizon Air
- Registered owner: Wells Fargo Bank Northwest NA Trustee
- Airworthiness certificate: Standard, Transport
- Last inspection: Continuous airworthiness, August 1, 2005, 55 hours before
- Departed: MFR, Medford, OR
- Destination: PDX, Portland, OR
- Flight plan: IFR
- Airport: PDX, Portland International

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot, aircraft N855NW; age 52; injuries: none; flight engineer, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review June 1, 2005; seat: left; flight hours: 15,000 total, 50 in this make and model, 202 in the last 90 days, 72 in the last 30 days, 0 in the last 24 hours
- Co-pilot, aircraft N855NW; age 59; injuries: none; flight engineer, airline transport; airplane ratings: multi-engine land, single-engine sea; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review March 1, 2005; seat: right; flight hours: 20,000 total, 2,000 in this make and model, 198 in the last 90 days, 65 in the last 30 days, 0 in the last 24 hours
- Other flight crew, aircraft N855NW; age 54; injuries: none; flight instructor, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; seat: center
- Pilot, aircraft N363PH; age 30; injuries: none; airline transport, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review February 1, 2005; seat: left; flight hours: 6,000 total, 600 in this make and model, 156 in the last 90 days, 50 in the last 30 days, 5 in the last 24 hours
- Co-pilot, aircraft N363PH; age 33; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review November 1, 2004; seat: right; flight hours: 4,700 total, 600 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 30° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: 6,500 ft broken
- Temperature: 66 °F, dew point 55 °F
- Altimeter: 30.04 inHg
- Observed at: PDX

## FAA reports on this event (2)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20050829019959A](https://openairdocs.org/incident/20050829019959A), Aug 29, 2005: Airbus A330223, Portland, OR, Minor damage. (-23) While taxiing for takeoff NWA5 struck HORIZON66. The impact resulted in substantial damage to the horizon DHC-8 aircraft. Horizon 66 was holding short of…
- [Accident 20050829019919A](https://openairdocs.org/incident/20050829019919A), Aug 29, 2005: Dhav DHC8202, Portland, OR, Substantial damage. (-23) While taxiing for takeoff NWA5 struck HORIZON66. The impact resulted in substantial damage to the horizon DHC-8 aircraft. Horizon 66 was holding short of…

## Other investigations on N855NW (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ENG17IA003](https://openairdocs.org/ntsb/ENG17IA003), Oct 26, 2016: Airbus A330 223 (N855NW), Seattle, WA, incident, no damage. Probable cause: A No. 1 engine fire caused by a fuel manifold supply line high cycle fatigue crack which led to a fuel leak that subsequently ignited on hot engine case surfaces. The fatigue crack originated and…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
