Aircraft strikes temporary taxiway light during night taxi at Adelaide Airport

No fatalities • Adelaide Airport, South Australia

An aircraft collided with a temporary unserviceability light at Adelaide Airport after being cleared through a closed taxiway area.

What happened

During a night operation at Adelaide Airport, an aircraft was cleared to taxi through a section of the taxiway that was temporarily closed for maintenance. Although the pilot was aware of the active closures via ATIS and NOTAMs, the controller issued a standard taxi clearance that inadvertently directed the aircraft into the unserviceable zone.

As the aircraft entered the closed area, the pilot failed to notice the red unserviceability lights and the aircraft struck one of the temporary lights. Following the impact, the pilot became aware of the error and waited while the lights were removed. Despite hearing radio transmissions regarding the removal of debris from a broken light, the pilot assessed that no impact had occurred and proceeded with the departure without requesting a formal inspection of the aircraft.

The investigation

The investigation examined the controller's actions, the visibility of the closure markers, and the airport's maintenance protocols. It was found that the controller, while alert, provided a routine clearance that failed to account for the temporary closures. While a custom text box had been created on the controller's display to note the closures, it lacked an automated alerting system to prevent clearances into closed areas.

Regarding the physical markers, the investigation found that the three red lights used to denote the 35m wide closed section were difficult to identify against the background airport lighting. Furthermore, the required physical markers were not positioned at the site. The investigation also noted that the airport's method of working plan did not specify the exact number of lights or markers required, leading to a lack of prominence for the closed area.

Findings

  • The controller issued a clearance that directed the aircraft through a temporarily closed movement area.
  • The pilot did not challenge the clearance, incorrectly assuming the works had concluded.
  • The pilot failed to observe the existing unserviceability lights and the aircraft struck a temporary taxiway light.
  • The lighting provided was insufficient to alert the pilot to the closed area, and necessary cone markers were absent.
  • The airport's working plan lacked specific requirements for the quantity of markers or lights, contributing to reduced visibility of the closed area.
  • The pilot continued the flight without an inspection despite indications that a light had been damaged.

Probable cause

The incident was caused by a combination of a controller issuing a clearance through a closed area and the pilot failing to question that clearance, compounded by insufficient lighting and a lack of physical markers to clearly identify the unserviceable taxiway section.

Frequently asked questions

What happened in the 2024-11-04 Pilatus Aircraft Ltd PC-12/47E accident near Adelaide Airport, South Australia?

An aircraft collided with a temporary unserviceability light at Adelaide Airport after being cleared through a closed taxiway area.

Were there any fatalities in the 2024-11-04 Pilatus Aircraft Ltd PC-12/47E accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 2024-11-04 involved a Pilatus Aircraft Ltd PC-12/47E, registration VH-FXJ, operated by Royal Flying Doctor Service of Australia Central Operations, at Adelaide Airport, South Australia.

What was the probable cause of the accident?

The incident was caused by a combination of a controller issuing a clearance through a closed area and the pilot failing to question that clearance, compounded by insufficient lighting and a lack of physical markers to clearly identify the unserviceable taxiway section.

Loading the flight search…