Boeing 737 descends below clearance altitude near Helsinki

Casualties unknown • FI

A Ukraine International Airlines Boeing 737 descended significantly below its assigned altitude, narrowly avoiding a telecommunications mast in the Helsinki terminal area.

What happened

On March 26, 2008, at 14:39 UTC, a Ukraine International Airlines Boeing 737-300, registration UR-GAQ, was being radar vectored toward Helsinki-Vantaa airport. The aircraft had been cleared to descend to 2,300 feet. However, the aircraft descended to a minimum altitude of approximately 1,400 feet, breaching the required terrain clearance for a telecommunications mast located near its flight path. The air traffic controller observed the deviation and immediately ordered the crew to climb back to 2,300 feet.

The investigation

The investigation by the Finnish Safety Investigation Authority (OTKES) established that the aircraft's altimeters were displaying an erroneous altitude of more than 1,000 feet. This error was caused by an incorrect barometric pressure setting. The investigation found that the flight crew had deviated from Standard Operating Procedures (SOP) and had failed to transition from QNH to QNE pressure settings at the appropriate phase of flight. Additionally, the crew had not reviewed the descent-approach checklist prior to the incident.

Detecting the hazard was delayed by two technical factors: the aircraft's Enhanced Ground Proximity Warning System (EGPWS) did not provide a warning for the specific telecommunications mast, and the Minimum Safe Altitude Warning (MSAW) feature in the Helsinki air traffic control radar system was not being utilized for alerting altitude infringements. Furthermore, the investigation revealed that the pilots did not report the incident to the airline or aviation authorities, contrary to company regulations.

Findings

  • The direct cause of the altitude infringement was an incorrect altimeter pressure setting.
  • Contributing factors included failures in Crew Resource Management (CRM) and the crew's deviation from Standard Operating Procedures.
  • The incident was classified as a serious incident, though the air traffic controller initially reported it simply as an incident.
  • The lack of active MSAW functionality and the failure of the EGPWS to warn of the mast hindered timely detection of the risk.

Probable cause

The primary cause was an erroneous altimeter pressure setting resulting from the flight crew's deviation from standard operating procedures, compounded by inadequate crew resource management and the non-utilization of radar warning systems.

Frequently asked questions

What happened in the 2008-03-26 aircraft accident near FI?

A Ukraine International Airlines Boeing 737 descended significantly below its assigned altitude, narrowly avoiding a telecommunications mast in the Helsinki terminal area.

What aircraft was involved and where did it happen?

The accident on 2008-03-26 involved a aircraft, at FI.

What was the probable cause of the accident?

The primary cause was an erroneous altimeter pressure setting resulting from the flight crew's deviation from standard operating procedures, compounded by inadequate crew resource management and the non-utilization of radar warning systems.

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.