Airprox Incident Tupolev Tu-154B-2 LZ-BTE, Saturday 6 February 1988
ASN logo
 

Date:Saturday 6 February 1988
Time:11:38
Type:Silhouette image of generic T154 model; specific model in this crash may look slightly different    
Tupolev Tu-154B-2
Owner/operator:Balkan Bulgarian Airlines
Registration: LZ-BTE
MSN: 74A074
Fatalities:Fatalities: 0 / Occupants:
Other fatalities:0
Aircraft damage: None
Location:18 NM South SW of Lydd, Kent -   United Kingdom
Phase: En route
Nature:Passenger - Scheduled
Departure airport:Sofia Airport (SOF/LBSF)
Destination airport:London-Gatwick Airport (LGW/EGKK)
Investigating agency: AAIB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
At 1135 hrs on 6 February 1988, the British Airways Tristar Flight BAW 305, en route from Paris to London Heathrow, was approaching a position some 12 nautical miles south-south-west of the Lydd radio navigation beacon. At the same time the Balkan Bulgarian Airlines Flight LAZ 967 was leaving the Lydd radio navigation beacon holding pattern having been cleared to descend for an approach to London Gatwick. There had previously been a significant build up of traffic due to a temporary, although pre-planned, closure of runway 26L at Gatwick - between 1056 and 1115 hrs - and an emergency closure of runway 27L at Heathrow at 1126 hrs. As a result there was a complex and unusual traffic situation, and inbound aircraft to Gatwick were being held at Eastwood and Lydd. As the Tristar was descending to Flight Level (FL) 180 on a radar heading towards Biggin Hill, an airmiss occurred with the Tupolev 154, which was also descending to FL 180 whilst turning onto a radar heading for positioning at Eastwood. The Tristar commander saw the Tupolev 154 aircraft and took violent evasive action to avoid a collision. The Tupolev 154 flight crew were unaware of the confliction as their aircraft, at the time, was in a right hand turn that made visual
sighting of the other aircraft virtually impossible. Both aircraft were under positive radar control and both aircraft were being flown in accordance with their flight clearances.

Cause
The primary cause of the airmiss was a lack of co-ordination between two experienced Air Traffic Control Officers who were controlling the two aircraft, in the same section of airspace, but on two different radio frequencies. Other causal factors were the lack of sufficient warning of impending traffic peaks, lack of dual monitoring requirements between Controllers, the lack of a conflict alert warning system, and the lack of formulated procedures to co-ordinate pre-planned runway closures with inbound traffic flow.

Accident investigation:
cover
  
Investigating agency: AAIB
Report number: AAR 1/89
Status: Investigation completed
Duration: 11 months
Download report: Final report

Sources:

https://assets.publishing.service.gov.uk/media/5422feb8ed915d1374000989/1-1989_G-BBAH_and_LZ-BTE.pdf

https://www.jetphotos.com/photo/10471642 (Photo)

Revision history:

Date/timeContributorUpdates
30-Mar-2025 09:57 Justanormalperson Added
30-Mar-2025 10:00 ASN Updated [Narrative, Accident report, ]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2025 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org