Monthly Meeting 22 April 2026

2026011

08 Feb 26

1521

B787

(CAT)

Drone

5129N 00023W

2.3NM E LHR RW27R

~875ft

London CTR

(D)

The B787 pilot reports they were short final at LHR when a drone was sighted directly in front of the aircraft.
The aircraft was stable with the landing checklist completed and autopilot was engaged throughout the encounter. At approximately 2.3NM DME and 750ft QNH [they remembered] a drone was sighted within the flight path of the aircraft at a range of around 100m. The drone was moving left-to-right in a northerly direction. The drone passed down the righthand side of the aircraft within the wingspan of the aircraft, around 30m, and marginally above the wing.

Reported Separation: ‘above the wing’/30m H

Reported Risk of Collision: NR

The London (Air North) Arrivals controller, for RW27R LHR,  reports that the [B787 pilot] reported a drone to the east of them. The pilot subsequently filed an Airprox.

Conclusion,

Watch log [entry] - [B787 CS] reported a drone at around 1000ft [they thought] on final approach to RW27R. [The drone was] yellow and black in colour and to the north of the aircraft. The police were advised and ATIS updated.

HAL were asked if the Drone Detection Unit was activated, who confirmed nothing was reported.

In the Board’s opinion the reported altitude and/or description of the object were sufficient to indicate that it could have been a drone.

Applicable Contributory Factors: 1, 2, 3, 4, 7

Risk: The Board considered that providence had played a major part in the incident and/or a definite risk of collision had existed.

A

2026012

18 Feb 26

1015

Voyager

(HQ Air (Ops))

Unk Obj

5325N 00144E

32NM NNE Cromer

FL160

London FIR

(G)

The Voyager pilot was conducting Air-to-Air refueling with a Typhoon at FL160 in good VMC. They were the non-handling pilot in the Captain's seat. As they progressed east bound in the towline, they caught [sight of] something directly in front of the aircraft and gained visual as it went past, but only for a matter of seconds. The object was black and circular in nature passing approximately 100-150ft directly above the Voyager. The proximity was such that it made them instinctively duck and it was notified to ATC as a drone. The Swanwick [controller] took the details and confirmed they had nothing on their radar.

No-one else on the flight deck saw the object, but one of the Typhoon pilots also saw it and agreed with the description, direction and clearance. Upon reflection and discussion, it is impossible to positively identify it was a drone and could have been a balloon or something similar but they could put no confidence in confirming it as a specific object. The sortie was continued with other aircraft notified and no further incidents.

Reported Separation: 100ft V/0m H

Reported Risk of Collision: Medium

The Swanwick Military controller reports that [the pilot of the Voyager] was maintaining FL160 with one receiver in tow, in the block FL140-170. They reported on frequency that they saw what was believed to be a drone flying approx 100-150ft above them, fast moving, tracking to the west and they asked if it could be seen on radar. Nothing was seen on radar so they noted the co-ordinates, which the Planner passed to D&D immediately, and they warned the [pilots of the] other joining formation of the potential drone. [The controller] asked for any further sightings, [and the pilot of the Voyager] stated that their receiver had also seen the object flying overhead, however, no further sightings were reported.

2 Gp BM Analysis: The controller acted accordingly in this situation and displayed a good duty of care by passing the information [to other pilots] operating in the area for situational awareness.

In the Board’s opinion the reported altitude and/or description of the object were such that they were unable to determine the nature of the unknown object.

Applicable Contributory Factors: 4, 6

Risk: The Board considered that safety had been much reduced below the norm to the extent that safety had not been assured.

B

2026014

23 Feb 26

1521

Typhoon

(HQ Air Ops)

Unk Obj

5446N 00020E

D323A

12,000ft

Danger Area 323

(G)

The Typhoon pilot reports that they were operating in D323A/B with [another aircraft], manoeurving. Whilst setting up for the next event, straight and level at 300kt and 12,000ft, they observed a circular black object (similar in size to a car tyre) pass directly above them. It was assessed to be approximately 300ft above them, tracking east in straight and level flight. They seperated away from the location that it was sighted and reported an Airprox to Swanwick East a few minutes after the event.

Reported Separation: 300ft V/NK H

Reported Risk of Collision: High

The Swanwick Mil controller reports that they were  the controller on East Tac Right, working several tracks. At circa 1530Z, the Typhoon pilot called complete ivo D323A, having been working in D323A/B with [another aircraft]. They identified the Typhoon, the pilot  was looking to RTB. In one of the initial comms exchanges, the pilot reported an Airprox during autonomous ops in D323; the controller asked for details, when ready. Details passed from the pilot were as follows: ivo D323A circa 1520Z Drone 200ft above the Typhoon, tracking east the Typhoon was at 12,500ft.

No other details were passed and the RTB continued as standard.

In the Board’s opinion the reported altitude and/or description of the object were such that they were unable to determine the nature of the unknown object.

Applicable Contributory Factors: 4, 5

Risk: The Board considered that although safety had been reduced, there had been no risk of collision.

C

2026027

16 Mar 26

0842

A321

(CAT)

Drone

5128N 00011W

Fulham

3200ft

London TMA

(A)

The A321 pilot reports that they had been on a normal flight with an ILS approach planned onto RW27R. On first contact with LHR DCTR on 121.400MHz, a general broadcast was made for a drone sighting on the final approach path of the ILS for RW27L at approximately 6NM. They therefore briefed the possibility of drones and to keep a good lookout, even though they were expecting to land on

RW27R. They established on the ILS for RW27R glideslope. FO was P1 at that point and was manually flying the approach so was very much focused on flying the aircraft (heads in at that point).

The reporting pilot was heads out a bit more and suddenly at 9NM noticed out of the corner of their eye an object approaching their 1 to 2 o’clock position at the same altitude. Before they had a chance to really have a good look, it flew by them within maybe 200m at the same altitude. All they were able to see was that it had lights and they believe it was therefore a drone. Size unknown, colour white. They advised ATC of the sighting and their approach was continued to an uneventful landing thereafter.

Reported Separation: 0ft V/200m H

Reported Risk of Collision: NR

The Heathrow controller reports that At 0831:15 the Heathrow Tower controller informed the LL FIN controller that a previous inbound aircraft had reported a drone to them when on a 6NM final for

RW27L, 20ft above the aircraft. The LL FIN controller reported this information to all subsequent

arrivals. The LL FIN controller made a broadcast to all aircraft on their frequency, at 0837:03, warning them of the drone sighting. [A321 c/s] was on the frequency at the time this message was transmitted.

Analysis of the radar by Safety Investigations indicated that there were no associated primary or secondary contacts associated with the drone report, visible on radar at the approximate time of the

event.

In the Board’s opinion the reported altitude and/or description of the object were sufficient to indicate that it could have been a drone.

Applicable Contributory Factors: 1, 2, 3, 4, 5

The Board considered that although safety had been reduced, there had been no risk of collision.

C