Near-Miss at Shannon Airport: Aeroflot Ilyushin IL-62M Avoids Terrain

Casualties unknown • IE

An Aeroflot Ilyushin IL-62M narrowly avoided controlled flight into terrain during an unstable approach at Shannon Airport, prompting an investigation into crew procedures and air traffic control oversight.

What happened

On the morning of September 14, 1996, an Aeroflot Ilyushin IL-62M, registration No. 86512, was conducting a scheduled flight from Chicago O'Hare to Moscow via Shannon Airport. During the approach to Runway 24, the aircraft performed an unstable and highly irregular maneuver that brought it dangerously close to the ground near the Clenagh area.

While attempting an Instrument Landing System (ILS) approach, the aircraft failed to establish on the localizer. Instead of following standard procedures, the aircraft maintained excessive speeds and performed a series of turns that took it away from the runway centerline. At approximately 200 feet above ground level, the pilot initiated a go-around. The low-altitude flight over residential rooftops caused significant noise and vibration, leading local residents to fear an imminent crash. Following the go-around, the aircraft successfully completed a second approach and landed without further incident. There were no injuries to the 101 persons on board.

The investigation

The investigation was triggered by noise complaints filed by residents of Clenagh. Upon reviewing radar tapes, the Air Accident Investigation Unit (AAIU) determined that the incident constituted a serious incident, as controlled flight into terrain was only marginally avoided.

Investigators examined the aircraft's flight data, which revealed that the crew did not follow company protocols for landing preparations. The investigation also scrutinized the communication between the cockpit and the Approach Radar Controller. A notable complication was the three-way communication chain, where the Captain's instructions had to be relayed through a Radio Operator, potentially causing delays in response time.

Findings

Several critical factors contributed to the dangerous situation:

  • The flight crew failed to adhere to Aeroflot's established procedures, which require landing preparations—such as extending flaps and lowering gear—to be completed on the base leg.
  • The aircraft maintained excessive airspeeds during the approach, far exceeding the 150 knots required by company policy.
  • The pilot failed to comply with two specific instructions from the Approach Radar Controller to turn right and climb, instead continuing to fly parallel to the runway at a distance of 1 to 1.5 nautical miles from the centerline.
  • The Approach Radar Controller did not intervene or comment on the aircraft's high speeds or improper approach path, mistakenly assuming the pilot had visual contact with the runway.
  • The controller's initial reporting of the event was found to be understated and incomplete, which delayed the formal investigation.

Safety action

Following the investigation, the following safety recommendations were issued:

  • The operator was advised to consider providing Cockpit Resource Management (CRM) training to international flight crews.
  • The Irish Aviation Authority (IAA) was recommended to implement a structured annual continuation and emergency training program for State-employed air traffic controllers.

Probable cause

The incident was caused by the flight crew's failure to follow standard landing procedures and comply with air traffic control instructions, combined with the controller's failure to recognize and correct the aircraft's unstable and off-course approach.

Frequently asked questions

What happened in the null aircraft accident near IE?

An Aeroflot Ilyushin IL-62M narrowly avoided controlled flight into terrain during an unstable approach at Shannon Airport, prompting an investigation into crew procedures and air traffic control oversight.

What aircraft was involved and where did it happen?

The accident on null involved a aircraft, registration IL-62M, at IE.

What was the probable cause of the accident?

The incident was caused by the flight crew's failure to follow standard landing procedures and comply with air traffic control instructions, combined with the controller's failure to recognize and correct the aircraft's unstable and off-course approach.

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.