Assessment Summary Sheet
Contributory factor assessment for each assessed Airprox can be downloaded
| Total | Risk A | Risk B | Risk C | Risk D | Risk E |
|---|---|---|---|---|---|
| 15 | 2 | 3 | 6 | 0 | 4 |
|
Airprox |
Aircraft 1 (Type) |
Aircraft 2 (Type) |
Airspace (Class) |
ICAO Risk |
|
KC135 (Foreign Mil) |
JS1 (Civ Gld) |
London FIR (G) |
C |
|
|
Paramotor (Civ Hang) |
C177 (Civ FW) |
London FIR (G) |
A |
|
|
Eurofox (Civ FW) |
EC145 (Civ Comm) |
London FIR (G) |
C |
|
|
Recommendation: In the CAA review of CAP413, consideration be given to the wording at paragraph 4.165 to permit a response to transmissions on unattended aerodrome frequencies. |
||||
|
Perkoz (Civ Gld) |
Nimbus (Civ Gld) |
London FIR (G) |
C |
|
|
PA32 (Civ Comm) |
PA28 (Civ FW) |
London FIR (G) |
E |
|
|
Rallye (Civ FW) |
Baron (Civ Comm) |
Boscombe CMATZ (G) |
C |
|
|
Eurofox (Civ FW) |
PA34 (Civ FW) |
Shobdon ATZ (G) |
E |
|
|
U2 (Foreign Mil) |
ASG29 (Civ Gld) |
London FIR (G) |
E |
|
|
Mavic 2 Pro (Civ UAS) |
Phenom (HQ Air (Trg)) |
Scottish FIR (G) |
E |
|
|
RV7 (Civ FW) |
DA42 (Civ FW) |
London FIR (G) |
B |
|
|
ASW20 (Civ Gld) |
C172 (Civ FW) |
London FIR (G) |
A |
|
|
EC145 (HEMS) |
TB20 (Civ FW) |
London FIR (G) |
C |
|
|
A319 (CAT) |
A321 (CAT) |
London TMA (A) |
C |
|
|
C152 (Civ FW) |
RV6 (Civ FW) |
London FIR (G) |
B |
|
|
LAK-17 (Civ Gld) |
Nimbus (Civ Gld) |
London FIR (G) |
B |
|
Consolidated Drone/Balloon/Model/Unknown Object Summary Sheet
Contributory factor assessment for each Drone/Balloon/Model/Unknown Object Airprox can be downloaded
| Total | Risk A | Risk B | Risk C | Risk D | Risk E |
|---|---|---|---|---|---|
| 3 | 1 | 0 | 2 | 0 |
0 |
|
Airprox Number |
Date Time (UTC) |
Aircraft (Operator) |
Object |
Location[1] Description Altitude |
Airspace (Class) |
Pilot/Controller Report Reported Separation Reported Risk |
Comments/Risk Statement |
ICAO Risk |
|
2025227 |
22 Oct 25 1219 |
B787 (CAT) |
Drone |
5131N 00000E IVO Plaistow 6000ft |
London TMA (A) |
The B787 pilot reports that on initial approach into LHR, passing through 6000ft turning base, a drone passed down the aircraft’s right-hand side. It was approximately 100m to 200m away from the aircraft. The event was reported to ATC and the police met the aircraft on arrival on stand at Heathrow for a statement. It was just north of the RW27R centreline.
Reported Separation: 0ft V/100m-200m H Reported Risk of Collision: N/R
The Swanwick TC Radar controller reports that [the B787] pilot reported a drone to the northwest of London City Airfield, while on a base leg from the north to RW27R for Heathrow. The pilot estimated the drone had been at 5500ft. The controller passed information to following aircraft about the drone for approximately 12min, they then received an update that a drone was around the final approach track RW27R, approximately 13NM to touchdown, estimated to be at 3500ft and orange in colour. The controller continued to pass information on the latest sighting for another 5min before being relieved by an oncoming controller. The Airport GS reported the 2 sightings to the police.
The NATS Safety Investigations reports that 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
Risk: The Board considered that although safety had been reduced, there had been no risk of collision. |
C |
|
2025230 |
04 Nov 25 1504 |
Prefect (HQ Air (Trg) |
Drone |
5244N 00022W 2NM SSW Bourne 6000ft |
London FIR (G) |
The Prefect pilot reports that, during a teach ‘Straight & Level’ exercise at 6000ft (Barnsley QNH) on radial 030°/7NM from Wittering, and located west of Bourne, the QFI spotted a large (3-5ft) black drone with steady green light. It was seen to be hovering approximately 100ft laterally and slightly below the aircraft. Once a safe MSD was achieved an orbit was initiatied while reporting to Cranwell Bank TATCC on frequency. Surprisingly, the drone started to follow the smooth turn rate with impressive speed, and was judged to be First Person View type.
Reported Separation: 300ft V/ 100ft H Reported Risk of Collision: Medium
The Cranwell controller reports that at 1504 a Prefect pilot reported a drone at 6000ft in their vicinity, approximately 8NM NNE of RAF Wittering. The Prefect tracked away and gave an updated drone position report. As Wittering had numerous aircraft in the area, the drone information was passed onto the Wittering Approach controller and reported to the shift ATCO IC. The drone did not show on radar at any point. The police were informed. |
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, 4, 5
Risk: The Board considered that although safety had been reduced, there had been no risk of collision. |
C |
|
2025238 |
16 Nov 25 1348 |
A321 (CAT) |
Drone |
5132N 00014W S of Kensal Green 5000ft |
London TMA (A) |
The A321 pilot reports that they had a near miss with a large black drone at about 5000ft, just after intercepting the LON 070° radial on an ULTIB1J SID. The drone was above the clouds and it was overcast. It passed over the right wing. The pilot reported the drone to ATC, and the flight continued normally.
Reported Separation: ‘passed over the wing’ Reported Risk of Collision: NR
The London Terminal controller reports that [A321 C/S] departed Heathrow on an ULTIB departure. On passing 5000ft the crew reported that a drone had passed very close to them. They described it as being large and black in colour. They advised the GS who informed Heathrow Tower and they also informed their colleague on NE Departures.
UKAB Secretariat An analysis of the NATS radar replay was undertaken and there were no primary tracks detected in the vicinity of the reported Airprox |
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 |
[1] Latitude and Longitude are usually only estimates that are based on the reported time of occurrence mapped against any available radar data for the aircraft’s position at that time. Because such reported times may be inaccurate, the associated latitudes and longitudes should therefore not be relied upon as precise locations of the event.