Runway Incursion at Kuopio Airport Averted by Maintenance Crew

Casualties unknown • FI

A Finnish Air Force light aircraft nearly collided with a maintenance vehicle on runway 33 at Kuopio Airport due to air traffic controller oversight.

What happened

On March 20, 1998, at approximately 15:30 local time, a runway incursion occurred at Kuopio Airport. A Finnish Air Force P28T light aircraft, operating under callsign H49, was performing a landing on runway 33. At the same time, a maintenance vehicle, a Saab 900, was performing an inspection on the same runway.

The aircraft had requested a change to its flight plan to approach from the Juankoski direction. During the approach, the air traffic controller was engaged in lengthy telephone calls to AFIS units in Mikkeli and Varkaa to coordinate a student pilot's navigation flight. While the controller was occupied with these calls, the maintenance crew requested permission to enter the runway. The controller granted the request and placed a magnetic symbol on the flight progress strip to indicate runway activity, but did not verify the vehicle's entry point or intended direction.

As the P28T approached for landing, the maintenance personnel, who were walking back to their vehicle, noticed the aircraft on short final. The crew quickly drove the vehicle off the runway via taxiway D. The pilot of the aircraft, attempting to extend the landing roll slightly, passed taxiway D while still airborne. A collision was avoided only because the maintenance crew spotted the aircraft and moved out of its path.

The investigation

The investigation was initiated by the Safety Investigation Authority after two similar incidents had occurred within a short period. Investigators examined radio communications, controller training records, and interviewed the air traffic controller and the maintenance personnel involved.

Findings

  • The air traffic controller failed to verify that the runway was clear before issuing landing clearance, neglecting both visual monitoring and radio confirmation.
  • The controller's attention was diverted by non-essential telephone calls to other aerodromes, which lasted longer than usual.
  • Radio communications between the controller, the aircraft, and the ground vehicle did not strictly adhere to standard phraseology.
  • The maintenance vehicle did not communicate its specific entry point or direction of travel on the runway, and the controller did not seek this information.
  • While the controller had properly marked the runway activity on the flight progress strip, the lack of active monitoring of the landing pattern was a critical failure.

Safety action

It is recommended that on-the-job training and monitoring procedures for air traffic controller trainees be improved. Specifically, tools should be developed to better assess whether trainees have fully internalized and are consistently applying fundamental air traffic control requirements during low-traffic periods.

Probable cause

The runway incursion was caused by the air traffic controller's failure to verify that the runway was clear before authorizing the landing, primarily due to being distracted by prolonged telephone communications with other aerodromes.

Frequently asked questions

What happened in the 1998-03-20 aircraft accident near FI?

A Finnish Air Force light aircraft nearly collided with a maintenance vehicle on runway 33 at Kuopio Airport due to air traffic controller oversight.

What aircraft was involved and where did it happen?

The accident on 1998-03-20 involved a aircraft, at FI.

What was the probable cause of the accident?

The runway incursion was caused by the air traffic controller's failure to verify that the runway was clear before authorizing the landing, primarily due to being distracted by prolonged telephone communications with other aerodromes.

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.