We use necessary cookies to make our website work. We'd also like to use optional cookies to understand how you use it, and to help us improve it.

For more information, please read our cookie policy.



Assessment Summary Sheet

Contributory factor assessment for each assessed Airprox can be downloaded 

Number of Airprox reports assessed, and their ICAO Risk rating
Total Risk A Risk B Risk C Risk D Risk E
17 1 6 5 1 4
Assessed Airprox reports

Airprox

Aircraft 1 (Type)

Aircraft 2 (Type)

Airspace (Class)

ICAO

Risk

2021235

EC145 (NPAS)

AW109 (Civ Helo)

London FIR (G)

C

2021236

Paraglider (Civ Hang)

Unk light-aircraft (unknown)

London FIR (G)

D

2021237

Typhoon (HQ Air Ops)

Typhoon Form’n (HQ Air Ops)

Coningsby ATZ (G)

B

2021241

TB10 (Civ FW)

PA28 (Civ FW)

Coventry ATZ (G)

B

2021242

RJ70 (MoD ATEC)

Hawk formation (RN)

Boscombe ARA (G)

E

2021244

ATR42 (CAT)

PA28 (Civ FW)

Dundee ATZ (G)

C

2021245

C404 (Civ Comm)

E-3 (HQ Air Ops)

London FIR (G)

E

2021246

C152 (Civ FW)

PS-28 (Civ FW)

Perth ATZ (G)

B

2021248

R44 (Civ Comm)

AS355 (Civ Comm)

London FIR (G)

C

Recommendation: The CAA reviews whether the Centralised Aviation Data Service (CADS) procedures, (Ref: UK IAIP ENR 1.10) generate the publication of sufficiently detailed information about operations below 500ft to enable other airspace users to accurately determine where the activity is taking place.

2021251

C152 (Civ FW)

DA42 (Civ FW)

London FIR (G)

B

2021255

A320 (CAT)

PA34 (Civ FW)

Gatwick CTR (D)

C

2022001

C172 (Civ FW)

Typhoon (HQ Air Ops)

Scottish FIR (G)

C

2022002

PA24 (Civ FW)

EC135 (Civ Helo)

Gloucestershire ATZ (G)

B

2022003

Hawk T1 (HQ Air Ops)

BASE Canopy (Civ Para)

London FIR (G)

E

2022004

Juno (HQ Air Ops)

WT9 Dynamic (Civ FW)

Shawbury MATZ (G)

A

2022005

AW169 (Civ Comm)

PA28 (Civ FW)

Blackpool ATZ (G)

E

2022008

PA28 (Civ FW)

F406 (Civ Comm)

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 

Number of Drone/Balloon/Model/Unknown Object reports, and their ICAO Risk rating
Total Risk A Risk B Risk C Risk D Risk E
8 3 1 4 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

2022041

25 Mar 22

1732

A320

(CAT)

Drone

5124N 00011W

8.5NM NW BIG

5500ft

London TMA

(A)

The A320 pilot reports that on passing 5500ft on the DET1J departure, the first officer observed a large drone passing down the right-hand side of the aircraft, approximately 150-200ft below and at about 200m lateral separation. It was a large drone, not a standard sub-250g, with 4 propellers and a large pale coloured central body, similar to a DJI Inspire.

 

Reported Separation: 150-200ft V / 200m H

 

The BIG Radar controller reports that the A320 departed Heathrow on a DET SID. At approximately 5500ft the pilot reported having had a drone pass down their right-hand side by about 100m as they passed 5000ft. The drone was described as being white, oval-rectangular shaped and of a decent size.

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 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

2022043

2 Apr 22

1634

PA28

(Civ FW)

Unk Obj

5115N 00248W

2NM S Cheddar VRP

1900

London FIR

(G)

The PA28 pilot reports that they saw the object very briefly off the port side. It appeared to have a two-tiered structure, which made them immediately think of a drone rather than a bird.

 

Reported Separation: 50ft V/100m H

Reported Risk of Collision: Medium

 

The Bristol Radar controller reports that [the PA28 pilot] was returning to Bristol VFR via Cheddar. While still outside controlled airspace, they recall the pilot reported that they "may have just passed a drone", or similar. There was no confirmation it was a drone, nor any indication that reporting action was going to be taken. The radar controller advised ADC in case the pilot mentioned any further details, which they did not. They cannot recall any other radar returns in the vicinity at the time. No other traffic was in the area.

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

2022046

9 Apr 22

1345

B737

(CAT)

Drone

5327N 00158W

Glossop

4000ft

 

Manchester TMA

(A)

The B737 pilot reports under radar control vectors in the descent on left base for an approach to RW23L at Manchester when they saw a blue drone pass slightly below and to the left. No avoiding action was taken because it was assessed that their vector would take them clear. The incident was reported to ATC and an Air Safety Report filed.

 

Reported Separation: 100ft V/30m H

Reported Risk of Collision: Medium

 

The Manchester controller reports that the B737 pilot, descending through altitude 4000ft, reported a large drone passing them nose to tail approximately 200ft below. The crew believed the drone to be blue in colour but stated that could be due to the sunlight.

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 safety had been much reduced below the norm to the extent that safety had not been assured.

B

2022054

8 Apr 22

1725

 

ATR72

(CAT)

Unk Obj

5325N 00254W

2NM N Liverpool

3500ft

Manchester TMA

(A)

The ATR72 pilot reports that on descending into Liverpool under radar vectors right downwind for RW27, the First Officer, who was the monitoring pilot, observed a small silver coloured object at the 2 o’clock position at same altitude passing by the right wing, within about 10m. No collision risk existed at the point that the object was sighted. As the object was only visible for 3 seconds it was not enough time to determine whether it was a balloon or a drone, but it appeared metallic at first, consequently it was reported to ATC as a possible drone sighting as a precaution.

 

Reported Separation: 0ft V/ 10m H

Reported Risk of Collision: Low

 

The Liverpool controller reports that the ATR72 pilot reported a small silver coloured drone passing down their right wing at the same altitude, which was 3700ft. They could not say if it was hovering or moving in a direction.

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

2022061

25 Apr 22

1326

 

A319

(CAT)

Drone

5103N 00028W

ivo Five Oaks

3700ft

London TMA

(A)

The A319 pilot reports they had started the turn onto right base for RW08R at Gatwick when the FO saw a white disc shaped drone, about a meter across, pass about 20m from the wing tip and at the same level. The incident was reported to Gatwick Approach and Tower.

 

Reported Separation: 0ft V/20m H

Reported Risk of Collision: NR

 

The Gatwick controller reports the A319 pilot reported on frequency at about 7NM out and was told to continue due to other traffic. Before the landing clearance was issued, the pilot reported details of a white drone seen on their right side at the same level whilst turning on to base leg. They stated it was 'quite close' with no actual distance given. The radar controller was immediately informed so they could alert other traffic. The supervisor was also informed. No subsequent reports were received from radar or from other 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, 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

2022066

30 Apr 22

0959

EMB190

(CAT)

Drone

5126N 00003W

3NM SW Greenwich

2000ft

London/City CTR

(D)

The EMB190 pilot reports that they were conducting an ODLEG arrival to London City for RW09. At 2NM inbound to TODBI, both flight crew spotted a large drone in very close proximity (vivid blue in colour) passing eastbound at high speed below the right-hand wingtip. The aircraft was at 2000ft, and they estimated the drone to be at 1800ft. No avoiding action was taken. They continued their arrival and immediately reported the drone to ATC. The police took details from the Captain and FO on the ground.

 

Reported Separation: 200ft V/30m H

Reported Risk of Collision: High

 

The Thames Radar controller reports that [the EMB190 pilot] reported a drone passing down the left-hand side of the aircraft [they recall], just below. The pilot deemed the proximity close enough to report an Airprox. On landing the pilot reported it as bright blue and big.

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 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

2022067

30 Apr 22

1457

PA25

(Civ FW)

Drone

5414N 00113W

Sutton Bank

180ft agl

London FIR

(G)

The PA25 pilot reports that just after take-off, whilst towing a glider, they glimpsed an object which they thought was a bird, initially dead ahead and close. It went directly overhead with no time to avoid. They noted it to be a 4-rotor drone as it passed. Size of drone was difficult to assess, but small, maybe 1/2 metre. [The gliding instructor’s recount was] virtually identical except that the drone passed over their right wing, which suggested it was travelling north.

 

Reported Separation: 15ft V / 0m 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, 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

2022068

30 Apr 22

1115

B787

(CAT)

Drone

5133N 00013W

6NM NE Heathrow

2800ft

London CTR

(D)

The B787 pilot reports that a small black drone passed approximately 500ft below down the right-hand side of the aircraft (FO side) while departing [departure airfield] at approximately D10 LON climbing through about 3000ft. No avoiding action was taken. They reported it to London ATC.

 

Reported Separation: 500ft V / NR H

Reported Risk of Collision: NR

 

NATS safety investigations found that the B787 pilot submitted an Airprox report in response to the sighting of drone whilst approximately 6NM NE of London Heathrow. It has been estimated that the UAS was at between 2500ft and 2800ft. Safety Investigations reviewed the radar at the time the pilot reported the sighting, however, no radar contacts 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, 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

 

[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.

 

 

Latest from UK Airprox Board

  1. July reports are now available
  2. June UKAB Insight newsletter
  3. Airprox Digest 2024