Runway Incursion at Amsterdam Schiphol Involving Boeing 757 and Boeing 737

Casualties unknown • Runway incursion, Boeing 757-2Q8, Boeing 737-306, Amsterdam Schiphol Airport, 29 January 2004, NL

A Boeing 757 mistakenly entered an active runway during taxiing at Amsterdam Schiphol, forcing an approaching Boeing 737 to perform an emergency go-around.

What happened

On 29 January 2004, a Boeing 757-2Q8, registration D4-CBG, was taxiing for departure at Amsterdam Schiphol Airport. After receiving clearance to taxi via the south toward runway 36C, the flight crew inadvertently turned onto the active landing runway, 36R, via taxiway entrance E4. At the same time, a Boeing 7.37-306, registration PH-BDC, was on final approach to the same runway. An apron controller noticed the unauthorized runway entry and alerted the ground controller via intercom. Consequently, the landing crew of the Boeing 737 was ordered to execute a go-around to avoid a collision. The Boeing 757 was subsequently instructed to vacate the runway, and no injuries or aircraft damage were reported.

The investigation

The investigation examined the taxi routing, air traffic control (ATC) communications, and airport infrastructure. Investigators found that the flight crew had turned left at taxiway Alpha instead of right, and despite subsequent corrective instructions from the ground controller, the crew eventually entered runway 36R. The investigation also looked into the visibility conditions, noting that snow-clearing activities were underway and the runway surface was reflective due to water and sun. The role of the tower supervisor and the effectiveness of the runway lighting and stop bars were also scrutinized.

Findings

Several contributing factors led to the runway incursion:

  • The flight crew experienced a loss of situational awareness, failing to recognize they had entered the active runway.
  • The taxi instructions provided by the ground controller were potentially ambiguous, leading to incorrect turns.
  • The intersection at entrance E4 was designed in a way that made it easy for aircraft taxiing on taxiway Bravo to enter the runway with a slight turn.
  • The runway controller's view of the E4 entrance was partially obstructed by a window frame.
  • The stop bar at E4 was not illuminated because low visibility procedures were not in effect at the time.
  • The landing crew of the Boeint 737 could not observe the Boeing 757 until the go-around was already underway due to the reflective runway surface and the aircraft's color.

Safety action

Following the incident, the airline implemented updated pilot training and procedures to better manage taxi clearances and prevent runway incursions. Additionally, the airport infrastructure was later modified; the junction at E4 was redesigned with a bend to provide pilots with a better view of the runway and to clearly signal when they are no longer on the taxiway.

Probable cause

The runway incursion was caused by the flight crew's failure to follow taxi instructions, leading to a loss of situational awareness, compounded by ambiguous taxi clearances and an airport intersection design that facilitated easy entry onto the active runway.

Frequently asked questions

What happened in the 2004-01-29 aircraft accident near Runway incursion, Boeing 757-2Q8, Boeing 737-306, Amsterdam Schiphol Airport, 29 January 2004, NL?

A Boeing 757 mistakenly entered an active runway during taxiing at Amsterdam Schiphol, forcing an approaching Boeing 737 to perform an emergency go-around.

What aircraft was involved and where did it happen?

The accident on 2004-01-29 involved a aircraft, at Runway incursion, Boeing 757-2Q8, Boeing 737-306, Amsterdam Schiphol Airport, 29 January 2004, NL.

What was the probable cause of the accident?

The runway incursion was caused by the flight crew's failure to follow taxi instructions, leading to a loss of situational awareness, compounded by ambiguous taxi clearances and an airport intersection design that facilitated easy entry onto the active runway.

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.