Runway Incursion Risk at Schiphol Due to Complex Intersection Starts

Casualties unknown • Quarterly Aviation Report 1st quarter 2020, NL

A potential collision occurred at Amsterdam Airport Schiphol when two aircraft were simultaneously cleared for takeoff on the same runway, highlighting risks associated with intersection operations.

What happened

On July 27, 2018, a high-risk situation developed at Amsterdam Airport Schiple involving an Embraer ERJ 190-100 STD, registered PH-EXV, and a Boeing 737-800, registered PH-BXI. The Embraer was stationary at the start of runway 18C when it was cleared for takeoff. Simultaneously, the Boeing 737 was granted clearance to line up for an intersection takeoff using high-speed exit W4 on the same runway.

Upon hearing the clearance, the Boeing 737 crew stopped past the hold-short line and notified the tower they were on the runway. Despite this, the runway controller issued the takeoff clearance to the Boeing 737. The Embraer crew began its takeoff roll but aborted the maneuver after realizing the Boeing 737 had also been cleared to depart. The aircraft passed within approximately 19 meters of each other at a speed of roughly 85 knots. The Runway Incursion Alerting System (RIASS) only triggered an alarm after the Embraer had already begun to decelerate.

The investigation

The investigation examined the operational complexities of runway 18C, which features non-standard exits and names. It looked into the controller's workload, noting that the controller was managing three different runways simultaneously. The investigation also reviewed recent incidents involving the same controller, including two separate occurrences earlier in the same shift that may have impacted mental resilience.

Findings

  • The use of intersection starts, particularly via non-right-angled high-speed exits, increases the risk of incursions because crews have difficulty seeing approaching traffic from the runway start.
  • The controller increased operational complexity by authorizing an intersection start rather than instructing the Boeing 737 to line up behind the Embraer.
  • The RIASS failed to act as an effective safety barrier, as the alarm only sounded after the potential collision was already in progress.
  • The controller's workload was high due to managing multiple runways and recent stressful incidents involving other aircraft.

Probable cause

The potential collision was caused by the simultaneous clearance of two aircraft for the same runway section, exacerbated by the inherent visibility challenges of intersection takeoffs and increased controller workload.

Frequently asked questions

What happened in the null aircraft accident near Quarterly Aviation Report 1st quarter 2020, NL?

A potential collision occurred at Amsterdam Airport Schiphol when two aircraft were simultaneously cleared for takeoff on the same runway, highlighting risks associated with intersection operations.

What aircraft was involved and where did it happen?

The accident on null involved a aircraft, at Quarterly Aviation Report 1st quarter 2020, NL.

What was the probable cause of the accident?

The potential collision was caused by the simultaneous clearance of two aircraft for the same runway section, exacerbated by the inherent visibility challenges of intersection takeoffs and increased controller workload.

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.