Assessment Summary Sheet
Contributory factor assessment for each assessed Airprox can be downloaded
| Total | Risk A | Risk B | Risk C | Risk D | Risk E |
|---|---|---|---|---|---|
| 18 | 2 | 3 | 10 | 0 | 3 |
|
Airprox |
Aircraft 1 (Type) |
Aircraft 2 (Type) |
Airspace (Class) |
ICAO Risk |
|
Kestrel (Civ Gld) |
BE200 (Civ Comm) |
London FIR(G) |
B |
|
|
Pioneer (Civ FW) |
Wilga (Civ FW) |
London FIR (G) |
C |
|
|
Eurofox/ASK21(Civ FW/Gld) |
Cessna 182 (Civ FW) |
London FIR (G) |
C |
|
|
T67 (Civ FW) |
C152 (Civ FW) |
London FIR (G) |
C |
|
|
PA28 (Civ FW) |
C182 (Civ FW) |
London FIR (G) |
E |
|
|
Ventus (Civ Gld) |
C182 (Civ FW) |
London FIR (G) |
C |
|
|
Recommendation: That Sherburn Aero Club remove the expired AIC Y 083/2023 from their website and ensure the RNP Instrument Approach Procedures ‘Pilot Brief’ and ‘RNP Pilot Crib Sheet’ are consistent. |
||||
|
Viking (HQ Air (Trg) |
TB20 (Civ FW) |
London FIR (G) |
C |
|
|
C172 (Civ FW) |
PA28 (Civ FW) |
Kemble ATZ (G) |
C |
|
|
P68 (Civ Comm) |
Spitfire (Civ FW) |
London FIR (G) |
C |
|
|
BE200 (Coast Guard) |
Calidus (Civ Helo) |
London FIR (G) |
E |
|
|
C42 (Civ FW) |
RV4 (Civ FW) |
Southampton CTR (D) |
A |
|
|
Silvaire (Civ FW) |
C172 (Civ FW) |
London FIR (G) |
A |
|
|
Cessna T206 (Civ FW) |
ASH31 (Civ Gld) |
Argyll CTA (E) |
C |
|
|
EMB190 (CAT) |
PA28 (Civ FW) |
London TMA (A) |
E |
|
|
DA42 (Civ FW) |
Hang-glider (Civ Hang) |
London FIR (G) |
B |
|
|
AW139 (Civ Comm) |
EC155 (Civ Comm) |
RA(T) (G) |
C |
|
|
DA42 (Civ FW) |
Gazelle (Civ Helo) |
Cranfield ATZ |
C |
|
|
PA28 (Civ FW) |
BE24 (Civ FW) |
Tatenhill ATZ |
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 | 2 | 0 | 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 |
|
2025204 |
3 Sep 25 1436
|
B787 (CAT) |
Drone |
5120N 00000E BIG Hold FL110 |
London TMA (A) |
The B787 pilot reports that they were in the hold for approach to LHR, when a large drone passed very closely down the left-hand side of the aircraft, in very close proximity.
Reported Separation: 100ft V/100ft H Reported Risk of Collision: High
The Swanwick controller reports that the B787 pilot was on the outbound leg of the BIG Hold when they reported seeing a drone off the left-hand-side. The controller asked for a description of the drone and the distance, to which the pilot reported silver and “pretty close”.
A general broadcast was made and another pilot in confirmed that they were also visual with the drone. Subsequent aircraft were vectored towards the OCK Hold and Heathrow police were informed.
A NATS Investigation reports that the B787 pilot reported that the drone passed down their left-hand side at the same level which was “pretty close”. The INT S controller issued an all-stations broadcast with position and level of the reported drone, the pilot of [another aircraft] then reported that they were “visual with it right now” at 1437:20 and stated that it was at a similar level to the B787. Due to the presence of the drone, one aircraft in the BIG Hold and following aircraft inbound to the BIG Hold were vectored to hold at OCK. Safety Investigations reviewed the radar at the time the pilot reported the sighting, however, no radar contacts associated with the drone were visible. |
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. |
B |
|
2025211 |
24 Sep 25 0857 |
A320 (CAT) |
Unk Obj |
5133N 00256W 3NM SE Newport FL050 |
Bristol CTA (D) |
The A320 pilot reports that a black object passed under their aircraft [when at] around 5000ft under radar vectors. The object was approximately 50-100ft below. The object was half a metre long and possibly travelling south-to-north.
Reported Separation: 50ft V/NR H Reported Risk of Collision: NR
The Bristol controller reports that [the pilot of the A320] reported something passing below their aircraft but provided no further information and could not identify it. |
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. |
B |
|
2025217 |
01 Oct 25 1154 |
A320 (CAT) |
Drone |
5130N 00003E IVO Greenwich 6200ft |
London TMA (A) |
The A320 pilot reports that on base leg to LHR, 6000ft approximately 18NM from threshold they spotted a large drone in their 1 o’clock position, heading toward them at extremely close range, they thought they were certain to hit it. It was a large drone, black and white, and unlit. This drone was the biggest drone they had seen, it would have caused significant damage if they were to hit it. They reported it immediately to ATC. Any drone sighting they have had before have been small drones but this was unlike anything they had seen before and it had scared them!
Reported Separation: NR Reported Risk of Collision: “just missed it”.
The Heathrow Final Director (LL FIN) reports that the pilot of [the A320] submitted an Airprox report in response to the sighting of a drone whilst approximately 1.6NM west of London City Airport. It has been estimated that the UAS was at 6000ft. Safety Investigations reviewed the radar at the time the pilot of [the A320] reported the sighting, however, no radar contacts associated with the drone were visible. The [A320] was 1.6NM bearing 258° from London City Airport (approximate coordinates 513021N 0000317E) when the sighting was reported, within the confines of the London TMA (Class A). The reporting aircraft was an Airbus A320 inbound to RW27L at Heathrow The time of the encounter was 1154:17 UTC. At the time of the report [the A320 was indicating 6200ft on the London QNH of 1028hPa. The pilot reported to the controller that the drone had passed beneath them. 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, 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.