Assessment Summary Sheet
Contributory factor assessment for each assessed Airprox can be downloaded
Total | Risk A | Risk B | Risk C | Risk D | Risk E |
---|---|---|---|---|---|
17 | 3 | 2 | 8 | 1 | 3 |
Airprox |
Aircraft 1 (Type) |
Aircraft 2 (Type) |
Airspace (Class) |
ICAO |
C152 (Civ FW) |
Socata TB20 (Civ FW) |
London FIR (G) |
C |
|
Prefect (HQ Air Trg) |
Hawk TMk1 (HQ Air Ops) |
LFA 17 (G) |
E |
|
EV97 (Civ FW) |
P68 (Civ Comm) |
London FIR (G) |
C |
|
PA28(1) (Civ FW) |
Robin R100 (Civ FW) |
Fairoaks ATZ (G) |
A |
|
Chinook (HQ JHC) |
Skyranger (Civ FW) |
London FIR (G) |
E |
|
Paraglider (Civ Hang) |
Unk light-aircraft (Unknown) |
London FIR (G) |
A |
|
PA28 (Civ FW) |
Extra 300 (Civ FW) |
London FIR (G) |
B |
|
C208 (Civ Para) |
Prefect (HQ Air Trg) |
London FIR (G) |
E |
|
Prefect (HQ Air Trg) |
Paramotor (Unknown) |
London FIR (G) |
B |
|
Cabri G2 (Civ Helo) |
Just Escapade (Civ FW) |
Leicester ATZ (G) |
C |
|
ASW19 (Civ Gld) |
PA28 (Civ FW) |
Halton ATZ (G) |
C |
|
C172 (Civ FW) |
PA32 (Civ FW) |
Southend CTR (D) |
C |
|
ASK21 (Civ Gld) |
C182 (Civ FW) |
Halton ATZ (G) |
C |
|
PA28 (Civ FW) |
C152 (Civ FW) |
London FIR (G) |
A |
|
Atlas (HQ Air Ops) |
PA28 (Civ FW) |
London FIR (G) |
C |
|
C152 (Civ FW) |
Diamond HK36 (Civ FW) |
London FIR (G) |
C |
|
C140 (Civ FW) |
Spitfire (Civ FW) |
London FIR (G) |
D |
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 |
---|---|---|---|---|---|
11 | 2 | 2 | 7 | 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 |
2021154 |
12 Aug 21 1617 |
C182 Civ FW |
Drone |
5141N 00027E 3NM SSW Chelmsford 2100ft |
London FIR (G) |
The C182 pilot reports that they were approximately halfway between the Chelmsford and Billericay VRPs. On first sighting the drone, their initial assumption was that it was a large bird of prey, hovering with wings fixed in the open position, and that it must be a large one. Then they reconsidered, due to the colour being completely black or dark grey, and with zero movement. As they got closer, its position remained unchanged, but it appeared to be rotating around its vertical axis, as if a camera was following them. They are not certain, but it may have had a red light on it.
Reported Separation: 0ft V/25m H Reported Risk of Collision: Medium
The NATS Safety Investigation reports that the C182 pilot submitted an Airprox report in response to the sighting of drone whilst approximately 2NM north of Billericay. There were no associated primary or secondary contacts 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, 4, 7
Risk: The Board considered that the pilot’s overall account of the incident portrayed a situation where safety had been much reduced below the norm to the extent that safety had not been assured. |
B |
2021155 |
20 Aug 21 1500 |
A320 (CAT) |
Unk Obj |
5150N 00003W Hertford FL105 |
London TMA (A) |
The A320 pilot reports that a large black-coloured drone was spotted passing directly under the aircraft’s nose. The First Officer saw what appeared to be a 4-legged shape. The separation was assessed as between 100-200ft vertically. Reported Separation: 100-200ft V/0m H Reported Risk of Collision: Medium The NATS Safety Investigation reports that a review of the RTF frequencies with which the aircraft was in contact inbound to Luton could not locate any pilot report. This was confirmed by the Airline Safety Report received from the operator which stated that ATC was not advised. A review of the radar at the time the aircraft passed the reported Flight Level of the encounter revealed there were no other primary or secondary returns visible in the vicinity. |
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 the pilot’s overall account of the incident portrayed a situation where although safety had been reduced, there had been no risk of collision. |
C |
2021158 |
21 Aug 21 1639 |
A320 (CAT) |
Drone |
5133N 00007W LHR 4500ft
|
London TMA (A) |
The A320 pilot reports that they were on base leg of the approach into LHR RW27L, a drone was suddenly spotted in close proximity to the aircraft. The drone was flying at approximately 4500ft and had a yellow coloured body with black propellors and was similar in type to a SIMEX X300C. It appeared above a cloud layer and was visible from the left-hand side of the flight deck at the high 1 o’clock position. It was displaced approximately 50ft to the right and 50ft above the aircraft. It was observed for approximately 5sec and no avoiding action was possible. The sighting was immediately reported to ATC and the approach was continued and the aircraft landed safely without further incident. A subsequent report was made to the police.
Reported Separation: 50ft V/50ft H Reported Risk of Collision: High |
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 the pilot’s overall account of the incident portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2021162 |
28 Aug 21 1345 |
B737 (CAT) |
Drone |
5350N 00138W Leeds Bradford 300ft |
LBA CTR (D) |
The B737 pilot reports that the aircraft was fully configured and ready to land. At approximately 300-500ft agl a four bladed drone in the shape of a blue cross with four black rotors passed extremely close to the flight deck window. It happened so fast a better description could not be given. It appeared to be in the area of the Old Ball Pub at Horsforth. The Captain was the pilot flying and as a result of the startle factor ducked and moved their head away from the flight deck window as they thought it was coming through the window. As a result of becoming unstable a standard a go around was initiated. ATC were informed that they were going straight ahead to 4000ft. Once level, Approach were informed of the reason for the go around. ATC vectored them for a second attempt to land which was successful. Engineers met aircraft on the stand and it was believed that no evidence of damage to aircraft was found.
Reported Separation: 10ftV/10ft H Reported Risk of Collision: High |
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 the pilot’s overall account of the incident portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2021168 |
28 Aug 21 1323 |
B737 (CAT) |
Balloons |
5452N 00135W Chester-le-Street 7000ft |
Borders CTA (D) |
The B737 pilot reports passing about 7000ft in the descent into Newcastle RW25 when approximately 5 large purple balloons tied together passed just under the right wing. It was reported to ATC and the remainder of the approach was normal.
Reported Separation: NK Reported Risk of Collision: NK
The Newcastle controller reports that the B737 was being vectored for an ILS Approach to RW25. As the aircraft was descending through FL064, 3NM west of the Nissan factory, the pilot transmitted "just a report of a near miss with about 5 or 6 balloons, they just nearly hit us (chuckling)". The report was acknowledged and as no other aircraft were in the vicinity no further action was taken. |
In the Board’s opinion the reported description of the object was sufficient to indicate that it was a group of balloons.
Applicable Contributory Factors: 4, 6
Risk: The Board considered that the pilot’s overall account of the incident portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2021171 |
5 Sep 21 1242 |
B737 (CAT)
|
Drone |
5503N 00139W Newcastle 450ft agl |
Newcastle CTR (D) |
The B737 pilot reports that a white quadcopter drone of the DJI Phantom type was sighted on short final to RW25. It was to the right of aircraft track at approximately 1.5NM on final approach. The drone was at same level and appeared to be hovering and passed as close as 20m from the right wingtip. ATC were informed.
Reported Separation: 0ft V/ 20m H Reported Risk of Collision: High
The Newcastle controller reports that at 1245z the B738 landed and reported a possible drone at 1.5NM on the approach to RW25. The drone was reported as being white and stationary, no height was given but from pilot report it was at the same level as the aircraft. The aircraft had landed before reporting but from the position given an estimation of height was between 400-600ft. The information was passed to Radar ASAP as they had landing traffic at 12 miles. The following traffic decided to continue approach and on landing reported nothing seen. The Airport 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, 3, 4, 7
Risk: The Board considered that the pilot’s overall account of the incident portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2021176 |
13 Aug 21 1628 |
A319 (CAT) |
Balloon |
5320N 00216W Manchester 350ft |
Manchester CTR (D) |
The A319 pilot reports that they were on short finals, the first officer (FO), who was the pilot flying (PF), questioned “what’s that?” pointing to below the nose. They discussed and both initially thought a drone. The pilot in charge (PIC) monitored while the PF flew. As it got closer (rose steadily) the PIC realised it was a helium balloon, but not just a small child’s one. It appeared to be in two parts; a large circular shape and rectangular part below with a very long substantial tether. Their concern was that if they had initiated a go around there was a potential of damage to the engine. The safest option was to land, which they did with no issues.
Reported Separation: 6-9ft V/1NM H Reported Risk of Collision: Medium
The Manchester controller reports that the A319 landed on RW23R and, as it was vacating the RW, reported a balloon at 400ft on short final. There was nothing observed from the tower. The controller was subsequently advised by the watch manager that the A319 pilot would be filing an Airprox.
The NATS Investigation found that the object reported was a child’s helium balloon released, or escaped, from a member of the public. |
In the Board’s opinion the reported altitude or description of the object were sufficient to indicate that it was probably a balloon.
Applicable Contributory Factors: 4, 6
Risk: The Board considered that the pilot’s overall account of the incident portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2021179 |
9 Sep 21 1526 |
B737 (CAT) |
Unk Obj |
5148N 00017E Stansted 4000ft |
Stansted CTR (D) |
The B737 pilot reports that they were climbing out on a STN SID and had commenced the initial turn onto 086° when they saw a large black rectangular drone on the starboard side of the aircraft. There was a small amount of cloud cover and they noticed it emerge out of the cloud and then they went past it, at the same level as the aircraft. The pilot noted that they thought this was medium risk due to the SID having a speed limit of 210kts for the initial turn. Should the aircraft not have adhered to this and accelerated, the radius of turn would have been greater and therefore a closer proximity to drone. They believed the drone deliberately occupied this particular piece of airspace as it would see (and possibly record) aircraft flying towards the drone followed by a turn and 'fly-by'.
Reported Separation: 0ft V/ <1.0NM H Reported Risk of Collision: Medium |
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 the pilot’s overall account of the incident portrayed a situation where although safety had been reduced, there had been no risk of collision. |
C |
2021180 |
13 Sep 21 1723 |
B737 (CAT) |
Unk Obj |
5147N 00001E 3NM NW of Harlow 2700ft |
Stansted CTR (D) |
The B737 pilot reports that they were on base-leg for RW04 at Stansted when suddenly a white object believed to be a drone appeared and narrowly avoided hitting the aircraft to the left-hand side of the nose cone. It managed to pass without hitting the aircraft. The whole event happened too quickly for any avoiding action to be taken. Reported Separation: 0ft V/2m H Reported Risk of Collision: High The Stansted INT/FIN controller reports that, at approximately 1723 [the B737 pilot], who was on a left-base for RW04, reported a drone passing down the left side of their aircraft whilst they were descending through approximately 2800ft. When asked about colour or an estimate of proximity, the reply was “white in colour, and metres”, with the pilot commenting that they "did not know how it did not hit the aircraft"'. The incident was reported to Group Supervisor airports, who informed Stansted Tower. Information on the drone was passed over the RT to aircraft following in the approach sequence. There were no further sightings and the aircraft following all landed without 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 the pilot’s overall account of the incident portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed. |
A |
2021183 |
10 Sep 21 1532 |
C180 (Civ FW) |
Drone |
5324N 00053W 2NM northeast Retford 2300ft |
London FIR (G) |
The C180 pilot reports that having just passed northeast abeam Gamston on a heading of 355° at altitude 2,300ft and about ½ mile before entering Doncaster controlled airspace, a large drone passed below. It was difficult to assess whether it was stationary, but it was on an apparent converging track from the 1 o'clock position. The incident was reported to Doncaster Approach.
Reported Separation: 50ft V/0m H Reported Risk of Collision: NR
The Doncaster controller reports that the phrase ‘Airprox’ was not used on frequency and that they were not aware of such an 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, 4, 7
Risk: The Board considered that the pilot’s overall account of the incident portrayed a situation where 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.