Assessment Summary Sheet
Contributory factor assessment for each assessed Airprox can be downloaded
Total | Risk A | Risk B | Risk C | Risk D | Risk E |
---|---|---|---|---|---|
19 | 1 | 7 | 8 | 0 | 3 |
Airprox |
Aircraft 1 (Type) |
Aircraft 2 (Type) |
Airspace (Class) |
ICAO Risk |
PA28 (Civ FW) |
Skyranger (Civ FW) |
Kemble ATZ (G) |
C |
|
R44 (Civ Helo) |
Extra EA300 (Civ FW) |
London FIR (G) |
C |
|
C42 (Civ FW) |
Unk Light-aircraft (Civ FW) |
London FIR (G) |
B |
|
Mavic Pro (Civ UAS) |
Juno (HQ Air Trg) |
London FIR (G) |
E |
|
Cabri G2 (Civ Helo) |
C152 (Civ FW) |
London FIR (G) |
B |
|
Chinook (HQ JHC) |
Unk Light-aircraft (Civ FW) |
London FIR (G) |
E |
|
PA28 (Civ FW) |
DR400 (Civ FW) |
London FIR (G) |
B |
|
PA28 (Civ FW) |
Unk Light-aircraft (Civ FW) |
London FIR (G) |
A |
|
DA42 (Civ FW) |
Jonker JS3 (Civ Gld) |
London FIR (G) |
B |
|
P68 (Civ Comm) |
PA28 (Civ FW) |
London FIR (G) |
B |
|
DA42 (Civ FW) |
Unknown (Civ Gld) |
London FIR (G) |
C |
|
Recommendation 1: The Cranfield aerodrome operator considers a means by which controller SA of traffic utilising airspace surrounding the Cranfield ATZ can be improved. Recommendation 2: Cranfield-based training organisations review their risk assessments with respect to their local operations without a surveillance-based ATS. |
||||
B737(A) (CAT) |
B737(B) (CAT) |
Lincolnshire CTA1 (A) |
C |
|
DR1050 (Civ FW) |
C172 (Civ FW) |
London FIR (G) |
B |
|
ASK13 (Civ Gld) |
C130 (HQ Air Ops) |
London FIR (G) |
C |
|
DA40 (Civ FW) |
C208 (Civ FW) |
Oxford ATZ (G) |
C |
|
TB20 (Civ FW) |
AS355 (Civ Comm) |
London FIR (G) |
E |
|
Recommendation: Gloucestershire Airport considers applying for an SSR transponder conspicuity code. |
||||
PA28 (Civ FW) |
Extra (Civ FW) |
Halfpenny Green ATZ (G) |
B |
|
P68 (Civ Comm) |
DA42 (Civ FW) |
London FIR (G) |
C |
|
DA40 (Civ FW) |
EC155 (Civ Comm) |
London FIR (G) |
C |
* The same recommendations apply to the 3 indicated Airprox.
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 | 0 | 1 | 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 |
2023029 |
11 Mar 23 1410 |
HR200 (Civ FW) |
Drone |
5207N 00113E 5NM SE Crowfield 3000ft |
London FIR (G) |
The HR200 pilot reports that during a normal flight in very good flying conditions, they and their passenger suddenly spotted an unidentified object that they both believed to be a drone in their 2 o'clock position. It was described as black with green lighting. It passed their port wing at their altitude (3000ft) and at an estimated distance of 100-200m at a speed of approximately 40-50kts. It passed their port wing in just a few seconds and there was no time to take significant avoiding action. They immediately transmitted a radio message to Wattisham Traffic for other listening aircraft in the area.
Reported Separation: 0ft V / 100-200m H Reported Risk of Collision: Medium |
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 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 |
2023033 |
12 Mar 23 0713 |
A320 (CAT) |
Unk Obj |
5134N 00107E 15NM E Southend FL180 |
London TMA (A) |
The A320 pilot reports that on a Standard Arrival into Heathrow, a drone was seen ahead which passed below and under the right side of the aircraft. The drone appeared to be a large circular structure with twin upper and lower circles connected by a vertical rod/connection.
The NATS Ltd Safety Investigation reports that the [A320 pilot] reported on frequency at 0713:22 and, aware of controller workload, stated they had a report and requested a call back when available. This suggested the drone encounter occurred prior to this time. The pilot subsequently reported “a drone at 18000 feet at about ten miles from TANET … looked like it was reasonable size but hard to gauge exactly.” and described it as a “large circular structure with twin upper and lower circles connected by vertical rod/connection.”
Reported Separation: 500-1000ft V/800-1000ft H Reported Risk of Collision: NK |
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 |
2023039 |
3 Apr 23 1710
|
A350 (CAT) |
Drone |
5135N 00013W 1.5NM NE Brent Reservoir FL60 |
London TMA (A) |
The A350 pilot reports that whilst on departure, on radar heading 335° and at FL60, the aircraft commander saw an object passing below the left-hand side of the aircraft approximately 100ft below. The object appeared to be silver in colour and ‘X’ shaped. The object was only in view for a few seconds as passed quickly. Due to the short time it was visible, it was difficult to estimate the size of object and distance from aircraft but due to relative speed it is assumed to have been fairly close.
Reported Separation: 100ft V / NR H Reported Risk of Collision: High
The London Radar controller reported that the A350 pilot reported a drone sighting when they were level at 6000ft. On questioning, they stated that it had passed down their left-hand side approximately 200ft below and was silver in colour. The controller reported it to the Group Supervisor, told the Heathrow Intermediate controller and then vectored subsequent departures around whilst advising them of the sighting. |
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 |
[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.