TCAS Resolution Advisory Avoids Mid-Air Collision Between Two Commercial Airliners

Casualties unknown • A 50 NM del VOR de Castejón (Zaragoza), ES

A near-miss between a Ukraine International Airlines Boeing 737-300 and a Lufthansa Airbus 321 occurred due to delayed air traffic control instructions and unacknowledged descent rate commands.

What happened

On October 29, 2005, a Ukraine International Airlines Boeing 737-300 (registration UR-GAL) and a Lufthansa German Airlines Airbus 321 (registration D-AIRL) experienced a loss of separation while descending toward Madrid. Both aircraft were following the same track during their descent phase.

At approximately 10:12 UTC, the Madrid Area Control Centre (LECM) instructed the Boeing 737-300 to increase its rate of descent to 2,000 ft/min or more to reach flight level 210. While the crew read back the new flight level, they did not acknowledge the specific instruction regarding the descent rate, and the air traffic controller (ATCO) did not request a formal acknowledgment of that specific parameter. Simultaneously, the Airbus 321 was instructed to maintain flight level 260.

Shortly thereafter, the Airbus 321 crew received a TCAS Traffic Advisory (TA), followed by a TCAS Resolution Advisory (RA) instructing them to climb. The crew complied, climbing to flight level 265. The Boeing 737-300 crew also performed a TCAS RA maneuver, descending to maintain separation. Radar data indicated that the minimum vertical separation between the two aircraft dropped to approximately 700 feet during the event. No injuries or aircraft damage were reported.

The investigation

The investigation examined radar data, flight data recorder (DFDR) information from the Boeing 73 and-300, and air traffic control communications. The investigation established that the Airbus 321 was descending at a rate of 2,200 ft/min, significantly faster than the Boeing 737-300, which was descending at 1,200 ft/min.

Investigators found that the Boeing 737-300 crew likely did not realize the severity of the event or report the RA maneuver because they were in the process of switching radio frequencies to Madrid Approach at the time the conflict occurred. Furthermore, the investigation noted that the ATCO provided an instruction regarding the aircraft's position without including a call sign, which went unacknowledged.

Findings

  • The primary cause of the separation infringement was that air traffic control instructions were issued too late to allow for a timely reaction by both aircraft.
  • The Airbus 321 crew did not reduce their high rate of descent despite observing the conflicting traffic below them.
  • The ATCO failed to request a specific readback for the required descent rate for the Boeing 737-300 and failed to use a call sign during a critical traffic update.
  • Neither the controller nor the supervisory personnel reacted promptly to the automated conflict alert warnings (CPA/CVA) generated by the radar system.
  • The Boeing 737-300 crew did not follow standard reporting procedures for a TCAS RA, mistakenly treating the event as a nuisance warning.

Probable cause

The separation violation and subsequent evasive maneuvers were caused by air traffic control instructions being issued too late to permit timely corrective action by the flight crews.

Frequently asked questions

What happened in the 2005-10-29 Airbus Industries A-321 accident near A 50 NM del VOR de Castejón (Zaragoza), ES?

A near-miss between a Ukraine International Airlines Boeing 737-300 and a Lufthansa Airbus 321 occurred due to delayed air traffic control instructions and unacknowledged descent rate commands.

What aircraft was involved and where did it happen?

The accident on 2005-10-29 involved a Airbus Industries A-321, registration D-AIRL, at A 50 NM del VOR de Castejón (Zaragoza), ES.

What was the probable cause of the accident?

The separation violation and subsequent evasive maneuvers were caused by air traffic control instructions being issued too late to permit timely corrective action by the flight crews.

Investigation report by the Spanish Civil Aviation Accident and Incident Investigation Commission (CIAIAC). Original record: https://www.transportes.gob.es/recursos_mfom/2005_069_in_eng_0.pdf. This page is a structured re-presentation; facts and quotes are in the Comision de Investigacion de Accidentes e Incidentes de Aviacion Civil (CIAIAC), Spain - Ministerio de Transportes y Movilidad Sostenible.

Loading the flight search…