Delta A333 at Amsterdam on Apr 18th 2012, runway incursion
Last Update: February 13, 2014 / 19:36:44 GMT/Zulu time
Incident Facts
Date of incident
Apr 18, 2012
Cause
Runway incursion
Airline
Delta Airlines
Aircraft Registration
N815NW
Aircraft Type
Airbus A330-300
ICAO Type Designator
A333
The crew missed the relevant hotspot on the airport chart. The term “cross†in the taxi instruction “cross at Z2†gave the captain the impression that he had a clearance to cross the runway. He no longer followed the instructed route to Z2 but instead turned left, crossing the runway at the end and thus causing a runway incursion at W11. The stop bar at that intersection was not illuminated. There was no risk of a collision.
The DSB analysed that the aircraft had landed on runway 18R, the ground controller at Tower West subsequently instructed the aircraft to taxi to their gate via taxiway Z. About 4 minutes later the aircraft was handed off to ground controller north, the aircraft was approaching the intersection taxiway Z and W11 at that time. The intersection is identified as a hot spot on the charts released by AIP Netherlands and the charts used by the crew. The first officer checked in with ground control north reporting the aircraft was on taxiway Z and received the clearance "cross at Z2, taxi Alpha North to gate E17".
The first officer looked to identify the taxiway Alpha North, the second first officer in the observer seat looked over his shoulder to assist in finding Alpha North. The captain made a left turn, the stop bars were not illuminated and continued across the runway. The second first officer in the observer seat noticed that Z2 was south of and well clear of the runway and made the captain aware, however the aircraft had already crossed most of the runway at that point. The captain saw the W11 sign and realized he had taken the wrong taxiway and had just caused a runway incursion, he observed an aircraft on an about 3nm final to runway 18C and expedited the crossing just about at the same time when the ground controller instructed the aircraft to expedite crossing. The aircraft vacated the runway and continued to the gate without further incident.
The DSB analysed: "At the moment the Airbus A330 crossed the end of runway 18C at W11, a passenger aircraft was on final for runway 18C from the north for a full stop landing. The approaching aircraft was approximately 3 NM (5,5 km) before the beginning of runway 18C. Including the length of runway 18C, the total distance between the approaching and the crossing aircraft was about 5 NM (9 km). There was no risk of collision."
The DSB further analysed: "In the instruction of the ground controller the term “cross†was used. The captain interpreted the instruction as a clearance to cross runway 18C. The Captain made a left turn and crossed 18C at the end. The captain by then had observed the W11 sign and realised that he had taken the incorrect intersection." The DSB added, that the two first officers had also understood they were cleared to cross the runway, and later provided testimony that the term "cross" was misleading as Z2 did not cross the runway but only the extended runway center line.
The DSB concluded analysis: "The initial taxi instruction given to the crew by the Ground Controller West reads: “taxi via Z to E17â€. In the instruction the word “via†is. Later on, Ground Controller North instructs the crew to “cross at Z2. Taxi Alpha North to gate E17â€. This instruction did not state the words “via Z†which, in combination with the position of the aircraft when the clearance was given, namely at the end of runway 18C, may have contributed to the confusion on the flight deck."
As result of this and other occurrences, where aircraft turned left onto W11 instead of continuing to Z2, taxiways W11 and W12 were temporarily closed and barriers established until the intersections had been redesigned to prevent turning left to southbound aircraft while permitting turning right to northbound aircraft on taxiway Z.
Aircraft Registration Data
Incident Facts
Date of incident
Apr 18, 2012
Cause
Runway incursion
Airline
Delta Airlines
Aircraft Registration
N815NW
Aircraft Type
Airbus A330-300
ICAO Type Designator
A333
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Related articles
Fleet type match
Delta A333 over Scotland on Aug 15th 2023, hydraulic failure
A Delta Airlines Airbus A330-300, registration N815NW performing flight DL-179 from Amsterdam (Netherlands) to Portland,OR (USA), was enroute at…
Fleet type match
Delta A333 over Atlantic on Dec 16th 2019, smoke and sparks from galley floor
A Delta Airlines Airbus A330-300, registration N815NW performing flight DL-162 (dep Dec 15th) from Minneapolis,MN (USA) to Amsterdam (Netherlands)…
Fleet type match
Delta A333 near Rome on Apr 27th 2016, hydraulic problem
A Delta Airlines Airbus A330-300, registration N815NW performing flight DL-444 from New York JFK,NY (USA) to Rome Fiumicino (Italy), was descending…
Fleet type match
Delta A321 at Atlanta on Apr 9th 2024, lightning strike
A Delta Airlines Airbus A321-200, registration N394DX performing flight DL-1192 from New York La Guardia,NY to Atlanta,GA (USA), was on approach to…
Fleet type match
Delta B739 enroute on Mar 30th 2024, cracked windshield
A Delta Airlines Boeing 737-900, registration N888DU performing flight DL-1736 from Denver,CO to Minneapolis,MN (USA), was enroute at FL350 about…
Fleet type match
Delta B764 over Atlantic on Mar 23rd 2024, unreliable airspeed
A Delta Airlines Boeing 767-400, registration N845MH performing flight DL-1 from New York JFK,NY (USA) to London Heathrow,EN (UK) with 225 people on…
Fleet type match
Delta A21N at Lihue on Mar 25th 2024, bird strike
A Delta Airlines Airbus A321-200N, registration N550DN performing flight DL-344 from Seattle,WA to Lihue,HI (USA) with 185 people on board, landed on…
Fleet type match
Delta A339 at Salt Lake City on Mar 24th 2024, dropped engine panel on departure
A Delta Airlines Airbus A330-900, registration N405DX performing flight DL-56 from Salt Lake City,UT (USA) to Amsterdam (Netherlands), departed Salt…
Newest articles
Fleet type match
Easyjet A320 near Hanover on Apr 17th 2024, smoke in cockpit
An Easyjet Airbus A320-200, registration G-EZOU performing flight U2-6621 from Birmingham,EN (UK) to Berlin (Germany), was enroute at FL370 about…
Fleet type match
United B753 enroute on Apr 10th 2024, Rockies' coach in captain's seat
A United Boeing 757-300, registration N73860 performing charter flight UA-3779 from Denver,CO (USA) to Toronto,ON (Canada) with the Colorado Rockies…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
A new way to document and demonstrate airworthiness compliance and aircraft value. Find out more.
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
Your regulation partner, specialists in aviation safety and compliance; providing training, auditing, and consultancy services. Find out more.
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways