Assessment Summary Sheet
Contributory factor assessment for each assessed Airprox can be downloaded
Total | Risk A | Risk B | Risk C | Risk D | Risk E |
---|---|---|---|---|---|
22 | 2 | 8 | 10 | 0 | 2 |
Airprox |
Aircraft 1 (Type) |
Aircraft 2 (Type) |
Airspace (Class) |
ICAO Risk |
Ikarus C42 (Civ FW) |
PA28 (Civ FW) |
Gloucester ATZ (G) |
B |
|
Mini 3 Pro (Civ UAS) |
Tutor (RN) |
London FIR (G) |
E |
|
SR20 (Civ FW) |
TB10 (Civ FW) |
London FIR (G) |
C |
|
PA28 (Civ FW) |
Microlight CTSW (Civ FW) |
Shobdon ATZ (G) |
A |
|
Microlight CTSW (Civ FW) |
AS350 (Civ Helo) |
London FIR (G) |
C |
|
PA28 (Civ FW) |
C210 (Civ FW) |
London FIR (G) |
B |
|
Hawk (HQ Air Trg) |
Ikarus C42 (Civ FW) |
London FIR (G) |
B |
|
Juno(A) (HQ Air Trg) |
Juno(B) (HQ Air Trg) |
Shawbury ATZ (G) |
B |
|
SZD Junior (Civ Gld) |
PA28 (Civ FW) |
London FIR (G) |
B |
|
C172 (Civ FW) |
CAP10 (Civ FW) |
London FIR (G) |
C |
|
DA40 (Civ FW) |
DA42 (Civ FW) |
London FIR (G) |
E |
|
DA42 (Civ FW) |
TB9 (Civ FW) |
London FIR (G) |
C |
|
C172(A) (Civ FW) |
C172(B) (Civ FW) |
Scottish FIR (G) |
B |
|
DA42 (Civ FW) |
PA28 (Civ FW) |
London FIR (G) |
C |
|
PA28(A) (Civ FW) |
PA28(B) (Civ FW) |
London FIR (G) |
A |
|
Ikarus C42 (Civ FW) |
Unknown (Civ FW) |
London FIR (G) |
C |
|
Falcon 20 (Civ Comm) |
Paramotor (Civ Para) |
London FIR (G) |
C |
|
PA28 (Civ FW) |
HR200 (Civ FW) |
London FIR (G) |
B |
|
A321 (CAT) |
G280 (Civ Comm) |
Portsmouth CTA (A) |
C |
|
SZD-50 (Civ Gld) |
C152 (Civ FW) |
London FIR (G) |
C |
|
RV8 (Civ FW) |
Pitts S2A (Civ FW) |
London FIR (G) |
B |
|
R66 (Civ Comm) |
Typhoon (HQ Air Ops) |
RA(T) (G) |
C |
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 |
---|---|---|---|---|---|
6 | 2 | 2 | 1 | 1 |
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 |
2025059 |
24 Apr 25 1355 |
Ikarus (Civ FW) |
Drone |
5245N 00125E 2NM NE Coltishall 1000ft |
London FIR (G) |
The Ikarus pilot reports they were on a local flight, in good visibility, and had just passed Coltishall VRP by approximately 2NM when a drone appeared and quickly disappeared off their left wing approximately 50 to 100ft at level altitude of 1000ft on Norwich QNH 1023hPa. They further described the drone as a grey and red quadcopter.
Reported Separation: 0ft V/50ft H Reported Risk of Collision: High
The Norwich controller reported that at approximately 1350 [the Ikarus pilot] transiting from [point to point], reported an Airprox with a drone. They reported that it had happened about 60sec previously and was at a similar level (1000ft). They acknowledged the Airprox and asked the pilot to call once landed safely to pass any further details. They continued without any further incident. On landing, the pilot reported that the drone appeared to be a regular size, with red and grey colourings. It occurred approximately 2-3 miles after Coltishall, with [the Ikarus] on an easterly track.
|
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 |
2025061 |
20 Apr 25 1814 |
ATR72 (CAT) |
Drone |
5551N 00429W 1.5NM SW Glasgow 500ft |
Glasgow CTR (D) |
The ATR72 pilot reports that a white and black drone was spotted [when] at 1.5NM [DME] and 500ft during the ILS approach to RW05 at Glasgow. No evasive manoeuvre was required or executed. Glasgow Tower was informed and the local police were debriefed on arrival at the gate.
Reported Separation: NR Reported Risk of Collision: NR The Glasgow Tower controller reports that [the pilot of the ATR72] landed on RW05 and reported that a drone was sighted when they had been at 1.5DME.
Glasgow Unit Investigation: [The pilot of the ATR72] reported the drone to ADC as they vacated RW05. They reported the drone as black and white in colour, on their left hand side when on a 1.5NM final and at 500ft. They did not state an intention to file an Airprox [at that time] and the controller replied with “thanks for that”. The controller then took appropriate action and reported to the ATC Watch manager and the Airport and [the pilots of] subsequent aircraft were warned, but there were no further sightings.
The radar screens visible to the radar controller have been checked and there were no unknown returns in the area and ATC was not working anything in that vicinity. The primary radar recordings were reviewed but there was nothing shown in the area. The Tower controller did not observe anything visually from the VCR window and there was nothing visible on the ATM recording. As the intention to file an Airprox was not communicated to ATC, it was filed as an MOR Drone report.
|
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 there was insufficient information to make a sound judgement of risk. |
D |
2025066 |
26 Apr 25 1537 |
B787 (CAT) |
Drone |
5151N 00017W 3NM ESE Luton 8000ft |
London TMA (A) |
The B787 pilot reports that on climb for the ULTIB 1J SID, but on a heading under positive radar control, when passing 8000-8300ft and abeam Luton, a red/black object passed above and to the right of the aircraft, approximately 200ft above and 100ft to the right of the aircraft. The object was travelling at speed and, although they were climbing, it appeared to climb also. The object was approximately 1m in diameter and of mechanical structure with possible arms attached.
Reported Separation: 200ft V/ 100ft H Reported Risk of Collision: NR
The TC GS Midlands controller reports that at 1537 [B787 C/S] outbound from Heathrow reported sighting a drone approx 1M in size at FL80 as they passed Luton. |
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 safety had been much reduced below the norm to the extent that safety had not been assured. |
B |
2025068 |
29 Apr 25 1024 |
B777 (CAT) |
Drone |
5128N 00030W 1.2NM west of RW09L at LHR 350ft |
London CTR (D) |
The B777 pilot reports that at 1.2 ILS DME 09L LHR a small white 4 propeller drone passed to the right of them co-altitude and close proximity to their right wing tip.
Reported Separation: 0ft V/NR H Reported Risk of Collision: NR
The LHR VCR Supervisor reports that the B777 had been on finals for RW09L and the pilot reported a white toy drone on the right hand side of the aircraft at 1.2NM DME. No further reports were received by the following landing aircraft.
|
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, 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 |
2025070 |
2 May 25 1006 |
F15 (Foreign Mil) |
Unk Obj |
5306N 00015W ivo Coningsby FL120 |
London FIR (G) |
The F15 pilot reports leading a pair on RTB over Conningsby at FL120 in the process of a handoff between Swanwick and Approach. Behind them was a 3-ship formation along the same route. The pilot gained tally of what looked like a basketball-sized drone with a flashing blue light. They acquired the drone at the moment they flew past it, assessing a miss distance of approximately 50ft. There were no prior indications on radar. They advised their operating authority of the incident and requested notification to Swanwick. Additionally, they advised the 3-ship in trail. None of the trail formation crew observed anything on radar or visually as they passed.
Reported Separation: 0ft V/50ft H Reported Risk of Collision: High
The Swanwick controller reports an F15 formation was RTB, underneath Y70 at FL120 and under a Traffic Service. They allocated the Lakenheath squawk and proceeded to handover. On completion of the handover they instructed the formation to contact Lakenheath Approach but was answered with a 'stand by'. Shortly afterwards the pilot returned to frequency and then proceeded with Lakenheath. The controller was not informed about an Airprox or drone sighting. The watch log did not reflect a call at any point from Lakenheath regarding the incident.
|
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 providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2025072 |
27 Apr 25 1603 |
A220 (CAT) |
Unk Obj |
5053N 00003W 2NM NE of Brighton FL310 |
London UIR (C) |
The A220 pilot reports that during cruise at FL310 approximately 10NM before SFD VORDME on airway Y803, both pilots saw a white object with a rectangular shape that they believed to be a UAV. The Airprox was transmitted to London ACC and to Paris ACC. The encounter lasted for a maximum of 2sec.
Reported Separation: Very close, just in front of the aircraft and below. Reported Risk of Collision: Low
The Swanwick ACC controller reports 'at 1615 [the A220 pilot] reported seeing a drone slightly below them in the vicinity of SFD’. The aircraft was at FL310. Sussex police were informed.
|
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 |
[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.