Runway Incursion at Amsterdam Schiphol Involving Boeing 787 Towing Operation

Casualties unknown • Runway incursion with tug combination, 28 February 2016, Amsterdam Airport Schiphol, NL

A tug combination towing a Boeing 787 entered an active runway at Amsterdam Airport Schiphol after receiving incorrect clearance from an apron controller.

What happened

On 28 February 2016, at approximately 13:10 local time, a tug combination was moving an aircraft from Schiphol-East to Schiphol-Centre at Amsterdam Airport Schiphol. The convoy consisted of an aircraft tug, registration KO, and a Boeing 787, registration PH-BHD.

As the tug approached intersection E3 of runway 18L-36R, the driver requested permission to cross the runway from the north apron controller. The controller mistakenly granted the clearance, despite the runway being active and under the control of Air Traffic Control the Netherlands (LVNL) for landing aircraft. The tug driver and an instructor traveling in the aircraft proceeded onto the runway. An approaching Embraer 190 was subsequently ordered to perform a go-around to avoid a collision. No injuries or damage were reported.

The investigation

The Dutch Safety Board investigated the causes of the incorrect clearance and the failure of the crew to identify the active runway. The inquiry examined the technical setup of the air traffic control environment, the visibility of runway warning lights, and the communication protocols between towing crews and air traffic controllers. The investigation also reviewed the post-incident response by the Airside Operations Manager regarding the driver's credentials.

Findings

Several contributing factors led to the incursion:

  • Controller Error: The apron controller was distracted by administrative tasks and failed to verify the runway status on a separate panel, which was not integrated into the primary radar screen and sat outside the controller's direct line of sight.
  • Lack of Information: Towing crews were not proactively informed of runway usage, leading the driver to believe the runway was inactive upon receiving clearance from Apron Control.
  • Reduced Visibility of Signals: The tug was traveling at a coasting speed after a turn, leaving little time to observe warning lights. Additionally, the red stop bar lights may have been set to a low intensity, making them difficult to see against the bright daylight.
  • Operational Ambiguity: There was a lack of clarity regarding the specific roles and responsibilities of the crew members during training.

Safety action

Following the incident, the management of runway crossings was changed; since May 2016, all runway crossings at Schiphol have been handled by LVNL. The investigation also noted that the immediate revocation of the driver's Schiphol Pass by the Airside Operations Manager was inconsistent with the principles of a "just culture," which is essential for maintaining transparent safety reporting.

Probable cause

The runway incursion was caused by an incorrect clearance from an apron controller distracted by administrative duties, compounded by a lack of integrated runway status monitoring and inadequate communication regarding runway activity to towing crews.

Frequently asked questions

What happened in the 2016-02-28 aircraft accident near Runway incursion with tug combination, 28 February 2016, Amsterdam Airport Schiphol, NL?

A tug combination towing a Boeing 787 entered an active runway at Amsterdam Airport Schiphol after receiving incorrect clearance from an apron controller.

What aircraft was involved and where did it happen?

The accident on 2016-02-28 involved a aircraft, at Runway incursion with tug combination, 28 February 2016, Amsterdam Airport Schiphol, NL.

What was the probable cause of the accident?

The runway incursion was caused by an incorrect clearance from an apron controller distracted by administrative duties, compounded by a lack of integrated runway status monitoring and inadequate communication regarding runway activity to towing crews.

Loading the flight search…