Loss of Separation Between Two Finnair Aircraft Near Helsinki

Casualties unknown • FI

An Airbus 321 and an MD-11 experienced a loss of separation near Helsinki-Vantaa due to inadequate air traffic control planning and supervision.

What happened

On April 28, 2003, at 03:48 UTC, a loss of separation occurred approximately 20 nautical miles northeast of Helsinki-Vantaa airport involving two Finnair passenger flights. The first aircraft, an Airbus 321 (registration OH-LZB), was on a scheduled flight from Oulu, while the second, an MD-11 (registration OH-LGC), was arriving from Bangkok.

The two aircraft passed each other with a vertical separation of only 700 feet and a horizontal distance of 1.9 nautical miles, failing to meet the required separation standards of 1,000 feet vertically or 5 nautical miles horizontally.

The incident began when the approach controller, a trainee on only their tenth operational shift, attempted to manage the arrival sequence. To maintain separation from a preceding ATR72, the controller ordered the Airbus 321 to turn left. During the maneuver, the aircraft's altitude settings were changed from QNH 1003 to standard pressure 1013, causing the aircraft to momentarily climb to 6,300 feet before descending back to the cleared flight level 60. Simultaneously, the MD-11 was cruising at 5,000 feet. The proximity was detected by the TCAS systems of both aircraft, issuing Traffic Advisories (TA).

The investigation

The investigation examined the actions of the approach radar controller, the supervising instructor, and the coordination between arrival and departure radar positions. The investigation reviewed radar recordings, radio communications, and the training status of the personnel involved. It also analyzed the altitude setting procedures used by the flight crews of both aircraft.

Findings

  • The primary cause of the loss of separation was inadequate planning and control of approaching traffic combined with the passive working method of the instructor supervising the trainee.
  • The trainee controller was managing a relatively heavy volume of arrival traffic, which was high relative to their limited experience.
  • The instructor failed to intervene with precise instructions until after both vertical and horizontal separation had already been lost.
  • The instructor provided imprecise directional instructions, specifically assuming a turn would occur to the right when it was actually to the left.
  • There was a lack of effective coordination between the approach (APP) position and the arrival (ARR) and departure (DEP) radar positions; specifically, the APP controller did not react to warnings from other controllers regarding the loss of separation.
  • The flight crews of both the Airbus 321 and the MD-11 operated the aircraft in accordance with the instructions provided by air traffic control.

Probable cause

The loss of separation was caused by poor traffic management and inadequate supervision of a trainee controller by a passive instructor, exacerbated by high traffic volume for the trainee's experience level.

Frequently asked questions

What happened in the 2003-04-28 aircraft accident near FI?

An Airbus 321 and an MD-11 experienced a loss of separation near Helsinki-Vantaa due to inadequate air traffic control planning and supervision.

What aircraft was involved and where did it happen?

The accident on 2003-04-28 involved a aircraft, registration OH-LZB, at FI.

What was the probable cause of the accident?

The loss of separation was caused by poor traffic management and inadequate supervision of a trainee controller by a passive instructor, exacerbated by high traffic volume for the trainee's experience level.

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.