UK Airprox Board UK Airprox Board
  • Assessment Summary Sheet for UKAB Meeting on 21st February 2018

     

    Total Risk A Risk B Risk C Risk D Risk E
    19 0 8 10 0 1

     

    Airprox

    Aircraft 1

    (Type)

    Aircraft 2

    (Type)

    Airspace

    (Class)

    Cause ICAO Risk
    2017231

    C152

    (Civ Trg)

    C172

    (Civ Trg)

    Cumbernauld ATZ

    (G)

    The C172 pilot did not integrate with the C152 in the visual circuit pattern.

    Contributory: 1. Effective communication was not established.

    2. R/T congestion was such that the C152 pilot was not able to make a downwind call.

    C
    2017234

    A319

    (CAT)

    SR22

    (Civ Pte)

    Leeds/Bradford CTR

    (D)

    Lees/Bradford ATC did not integrate the SR22 with the A319.

    Contributory: 1. The Leeds/Bradford controllers did not agree a plan for the SR22 join.

    2. ATC did not pass sufficient Traffic Information on the A319 to the SR22 pilot.

    C
    2017235

    A320(A)

    (CAT)

    A320(B)

    (CAT)

    London TMA

    (A)

    The A320(B) pilot mistook another pilot’s R/T transmission as an ATC clearance and climbed into conflict with A320(A).

    Contributory: The A320(B) pilot’s verbose response delayed the controller’s endeavour to maintain separation minima.

    C
    2017237

    C152

    (Civ Trg)

    Glasair

    (Civ Pte)

    London FIR

    (G)

    A late sighting by the C152 pilot and a non-sighting by the Glasair pilot. B
    2017238

     Hawk

    (HQ Air Ops)

     C172

    (Civ Pte)

    London FIR

    (G) 

    Effectively a non-sighting by the Hawk pilot.  C
    2017241

     Puma

    (MoD ATEC)

    Apache

    (HQ AAC) 

    London FIR

    (G) 

     The Puma pilot was concerned by the proximity of the Apache formation.  C
    2017242

    AW139

    (Civ Comm)

    Light Aircraft

    (Unknown)

    London FIR

    (G)

    A conflict in Class G resolved by the AW139 pilot. B
    2017244

    EC135

    (Civ Comm)

    C152

    (Civ Club)

    London FIR

    (G)

    A conflict in Class G resolved by the EC135 pilot. E
    2017245

    S92

    (HEMS)

    Light Aircraft

    (Unknown)

    London FIR

    (G)

    A late sighting by the S92 pilot and probably a non-sighting by the light aircraft pilot. B
    2017246

    Murphy Renegade

    (Civ Pte)

    AW109

    (HEMS)

    London FIR

    (G)

    The AW109 pilot flew into conflict with the Murphy Renegade.

    Contributory: The AW109 was directly into sun to the Murphy Renegade pilot.

    C
    2017247

    B787

    (CAT)

    ATR72

    (CAT)

    Airway M605

    (A)

    The oncoming controller cleared the B787 into conflict with the ATR72.

    Contributory: The oncoming controller took control of the sector without fully assimilating the traffic situation.

    C
    2017250

    Squirrel

    (HQ JHC)

    Light Aircraft

    (Unknown)

    London FIR

    (G)

    A conflict in Class G resolved by the Squirrel pilot.

    Contributory: The low cloud base and high terrain caused the aircraft to be funneled together into the same valley feature.

    B
    2017251

    AW169

    (Civ Comm)

    AW109

    (Civ Comm)

    London FIR

    (G)

    The AW109 pilot descended into conflict with the AW169. B
    2017252

    Tutor

    (HQ Air Trg)

    Hawk

    (HQ Air Ops)

    Topcliffe MATZ/London FIR

    (G)

    Leeming ATC released the Hawk formation into conflict with the Tutor.

    Contributory: 1. The Approach controller’s workload was such that he did not assimilate that the Tutor was in the vicinity of the Hawks’ departure track.

    2. The call for release was not adequately communicated between the Supervisor and the Approach controller.

    3. The Hawk pilot did not act on Traffic Information, passed under a Traffic Service.

    C
    2017253

    DHC8

    (CAT)

    ASK13

    (Civ Club)

    Aberdeen CTA

    (D)

    The ASK13 pilot probably entered CAS and flew into conflict with the DHC8.

    Contributory: The ASK13 pilot was unsure of his location.

    C
    2017256

    Centrair Pegase

    (Civ Club)

    C172

    (Civ Trg)

    London FIR

    (G)

    A late sighting by the Pegase pilot and a probable non-sighting by the C172 pilot. B
    2017257

    Wildcat

    (Civ Comm)

    Paramotor

    (Unknown)

    London FIR

    (G)

    A conflict in Class G resolved by the Wildcat pilot. B
    2017260

    Wildcat

    (HQ JHC)

    Ximango Motor Glider

    (Civ Club)

    London FIR

    (G)

    The Wildcat pilot flew into conflict with the Ximango, despite being passed Traffic Information. B
    2017261

    DHC8

    (CAT)

    C42

    (Civ Pte)

    Solent CTR/CTA

    (D)

    The C42 pilot flew into CAS without clearance from ATC and into conflict with the DHC8.  C

     

  • Consolidated Drone/Balloon/Model/Unknown Object Report Sheet for UKAB Meeting on 21st February 2018

    Download below sheet as PDF

     

    Total Risk A Risk B Risk C Risk D Risk E
    2 1 0 1 0 0

     

    Airprox

    Number

    Date

    Time (UTC)

    Aircraft

    (Operator)

    Object

    Location

    Description

    Altitude

    Airspace

    (Class)

    Pilot/Controller Report

    Reported Separation

    Reported Risk

    Cause/Risk Statement

    ICAO

    Risk

    2018003

    7 Jan 18

    1133

    A319

    (CAT)

    Drone

    5131N 00019W

    Perivale, London

    4800ft

    London TMA

    (A)

    The A319 pilot reports that on climb-out from Heathrow, passing 4800ft a medium-sized, white drone passed directly overhead, with an estimated separation of 20ft. There was no time for the flight path to be altered.  It was reported to ATC and to the police and written up in the tech log for a precautionary inspection.

     

    Reported Separation: 20ft V/0m H

    Reported Risk of Collision: High

    Cause: The drone was being flown above the practical VLOS limit such that it was endangering other aircraft at that altitude and position. The Board agreed that the incident was therefore best described as the drone was flown into conflict with the A319.

     

    Risk: The Board considered that the pilot’s estimate of separation, allied to his overall account of the incident and his inability to avoid the drone portrayed a situation where providence had played a major part in the incident and/or a definite risk of collision had existed.

    A
    2018009

    16 Jan 18

    1230

     

    A320

    (CAT)

    Drone

    5128N 00011E

    8nm NE Biggin Hill

    2500ft

     

    London CTA

    (D)

    The A320 pilot reports that they were just establishing on the ILS LOC at Biggin Hill for RW21 and at approx. 2500ft.  Both crew members saw an object in the 11 o’clock position flying around.  They tracked it for a couple of seconds, before identifying it as a drone as it passed to the left-hand-side, about 0.5nm from the aircraft.  They reported it to ATC.

     

    Reported Separation: 0.5nm H

    Reported Risk of Collision: High

     

    The Thames Controller reports that they were providing a service to the A320 inbound to Biggin Hill.  Whilst on base leg for the ILS RW21, the pilot reported a drone to the left-hand-side being flown at a distance of 0.5nm from the aircraft.  There was no radar return, but the pilot was happy to continue with the approach.  At that position and level, the drone was well inside CAS.

    Cause: The drone was being flown above the practical VLOS limit such that it was endangering other aircraft at that altitude. The Board agreed that the incident was therefore best described as the drone was flown into conflict with the A320.

     

    Risk: The Board considered that the pilot’s estimate of separation, allied to his overall account of the incident portrayed a situation where although safety had been reduced, there had been no risk of collision.

    C