If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user


A332/B738, vicinity Amsterdam Netherlands, 2012

From SKYbrary Wiki

On 13 November 2012, a Garuda Airbus A330 and a KLM Boeing 737 lost separation against each other whilst correctly following radar vectors to parallel approaches at Amsterdam but there was no actual risk of collision as each aircraft had the other in sight and no TCAS RA occurred. The Investigation found that one of the controllers involved had used permitted discretion to override normal procedures during a short period of quiet traffic but had failed to restore normal procedures when it became necessary to do so, thus creating the conflict and the ANSP was recommended to review their procedures.
Event Details
When November 2012
Actual or Potential
Event Type
Day/Night Day
Flight Conditions VMC
Flight Details
Aircraft AIRBUS A-330-200
Operator Garuda Indonesia
Domicile Indonesia
Type of Flight Public Transport (Passenger)
Origin Dubai International Airport
Intended Destination EHAM
Take off Commenced Yes
Flight Airborne Yes
Flight Completed Yes
Flight Phase Descent
Flight Details
Aircraft BOEING 737-800
Operator KLM
Domicile Netherlands
Type of Flight Public Transport (Passenger)
Origin Manchester International Airport
Intended Destination EHAM
Take off Commenced Yes
Flight Airborne Yes
Flight Completed Yes
Flight Phase Descent
Location - Airport
Airport vicinity EHAM
Tag(s) ATC clearance error,
ATC Unit Co-ordination,
Ineffective Monitoring,
Procedural non compliance
Tag(s) Required Separation not maintained,
ATC Error
Damage or injury No
Causal Factor Group(s)
Group(s) Air Traffic Management
Safety Recommendation(s)
Group(s) None Made
Investigation Type
Type Independent


On 13 November an Airbus A330-200 being operated by Garuda on a scheduled passenger flight from Dubai to Amsterdam and a Boeing 737-800 being operated by KLM on a scheduled passenger flight from Manchester to Amsterdam were being radar vectored to ILS approaches to runways 18C and 18R respectively in day VMC when the prescribed traffic separation was lost. ATC gave corrective headings and the two aircraft then continued their ILS approaches as planned. There were no abrupt manoeuvres and no TCAS RAs during deconfliction.


An Investigation was carried out by the Dutch TSB using radar and R/T recordings. It was noted that the former had a refresh interval or time lag of 5 seconds.

It was established that both aircraft had been under radar control service to join the localiser of their landing runway - 18R for the Boeing 737 and 18C for the Airbus 330. This service was, as required by ATC procedures, being provided by controllers with individual responsibility for each approach. Recorded data showed that all instructions to both aircraft had been followed correctly but that the normal procedures for the dependent parallel approaches flown on these runways when traffic demand was high enough had been suspended by the controller responsible for runway 18C during a gap in traffic joining from the west for runway 18R. Such a suspension of the normal procedures was found to be permitted but this discretion was not accompanied with any guidance on ensuring that such a suspension ceased once the gap in other runway arrivals ceased.

It was noted that the required separation during positioning to and when on the dependent parallel ILS approaches to runways 18R and 18C, which have exactly the same alignment and only 2060 metres between their centrelines, was effectively a minimum of 1000 feet vertically, since the airspace alternative to this was 3nm horizontally and not achievable if two aircraft were to be vectored on to the two approaches at the same time. When using these two runways, this standard separation was normally achieved by bringing aircraft in from the west to runway 18R at 2000 feet on a base leg at least 11nm north of the runway threshold and aircraft from the east to runway 18C at 3000 feet on a base leg at least 13nm north of the runway threshold which with the displacement of the 18C landing threshold by 1.8nm to the south of that for runway 18R effectively provides separation of 1000 feet vertically as opposing aircraft close with respective ILS FATs.

In the investigated incident, the controller who had suspended the normal procedure of vectoring from the east to the 18C ILS due to a gap in traffic from the west was descending his traffic to 2000 feet instead of 3000 feet - although the Investigation noted that since the base leg track was unchanged, this deviation was not delivering any operational benefit. The Airbus 330 was the fourth aircraft he had done this with but by this time, a Boeing 737 was being vectored from the west for the runway 18R ILS and the two aircraft were closing on opposite headings at the same cleared altitude. The two controllers noticed the developing conflict with the aircraft 5.7nm apart and at similar speeds and the Boeing, having just been given a right turn to an intercept heading of 160° was, four seconds later, given a left turn onto 360°. Then, a few seconds later, with the Airbus having been turned on to a heading of 210°, the Boeing was instructed to turn right again onto a heading of 160° when the controller realised that the effect of the instructed left turn was going to produce less separation than the right turn to close the ILS. Within just under 20 seconds, each of the aircraft had reported visual acquisition of the other. As both aircraft continued their headings, the Airbus without the usual instruction to establish on the ILS Localiser from the heading given because the controller had forgotten to give that instruction, both received two successive TCAS TAs. The minimum separation of 0.6nm at the same altitude was reached just as the Boeing began to turn left to establish on the 18R localiser and soon afterwards, the Airbus was given a heading to close the 18C localiser from the right having gone slightly through it. The remainder of both approaches was uneventful.

Tracks of the two aircraft showing the positions at which each one received TCAS TAs(reproduced from the Official Report)

The Investigation concluded that the cause of the conflict was the failure of the controller vectoring to runway 18C to resume the normal operational procedure of vectoring traffic to the 18C localiser at 3000 feet when the gap in traffic from the west finished. Although it was clear that “no immediate chance of a collision was present” it was considered that the loss of prescribed minimum separation represented “a possible breach of flight safety”. It was noted that whilst it was necessary for controllers to be afforded a degree of operational flexibility in handling traffic, such discretion should be “conducted…within written boundaries”. Accordingly, the Investigation recommended that LVNL (the ANSP) should “give extra attention to the circumstances under which ATC controllers are allowed to deviate from procedures in their safety program”. It was also observed that “controllers must be aware that they cannot operate individually, but are dependent on each other, especially when deviating from procedures” and appreciate that “strict co-ordination and communication are needed to maintain separation during parallel approaches”.

The Final Report of the Investigation was released in May 2013. No formal Safety Recommendations were issued.

Editor’s Note: It is unclear whether the recommendation made as a consequence of this Investigation and quoted above verbatim from the Final Report has the status of a formal Safety Recommendation.

Further Reading