Date: 18 Jul 2016 Time: 1441Z Position: 5112N 00128W Location: Picket Piece, Hampshire

Similar documents
Date: 23 Jul 2016 Time: 1125Z Position: 5137N 00146W Location: IVO Swindon

Time: 1111Z Position: 5049N 00016W Location: 1nm SE Brighton City Airport

Date: 29 Apr 2017 Time: 1119Z Position: 5226N 00112W Location: 10nm ENE Coventry

Date: 01 Aug 2016 Time: 1344Z Position: 5441N 00241W

Date: 14 Jun 2017 Time: 1513Z Position: 5101N 00251W Location: Curry Rivel

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

THE GLIDER PILOTS: Despite extensive tracing action, none of the glider pilots could be identified.

Date: 14 Jun 2017 Time: 1600Z Position: 5121N 00102W Location: 7nm NW Blackbushe airport

Date: 9 Dec 2015 Time: 1503Z Position: 5417N 00039W Location: Vale of York AIAA

Date: 12 Apr 2017 Time: 1732Z Position: 5123N 00028W Location: Heli-route 3

AIRPROX REPORT No Date/Time: 7 Dec Z (Saturday)

Date: 01 Jun 2018 Time: 0959Z Position: 5121N 00048W Location: 6nm N Farnborough

Date: 07 Feb 2018 Time: 1547Z Position: 5317N 00043W Location: W Scampton

Paraglider (not radar derived) Reported CPA 0836:58

Date: 19 Jun 2016 Time: 1211Z Position: 5228N 00216W Location: IVO Wolverhampton

Date: 14 Aug 2018 Time: 1443Z Position: 5225N 00040E

Date: 4 Jun 2015 Time: 1009Z Position: 5155N 00209W Location: Gloucestershire

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRPROX REPORT No Date/Time: 9 Sep Z. (6nm N Linton on Ouse) Airspace: Vale of York AIAA (Class: G)

AIRPROX REPORT No Date: 05 Apr 2018 Time: 1451Z Position: 5128N 00058W Location: Reading PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

RV6 800ft aal 24:27 24:39 25:03 24:51

Date: 23 May 2017 Time: 1019Z Position: 5443N 00244W Location: 10nm south Carlisle Airport

Date: 29 Jun 2018 Time: 1502Z Position: 5325N 00312W Location: 5nm NW Liverpool Airport

Date: 9 Jul 2015 Time: 1417Z Position: 5311N 00031W Location: Cranwell visual circuit.

AIRPROX REPORT No Date: 17 Apr 2015 Time: 1345Z Position: 5243N 00253W Location: Nesscliff PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRPROX REPORT No Date/Time: 27 Aug Z. (5nm NE Coventry Airport) Airspace: London FIR (Class: G)

AIRPROX REPORT No Date/Time: 12 Jan Z. (White Waltham elev 133ft) Airspace: White Waltham ATZ (Class: G)

AIRPROX REPORT No Date/Time: 14 Jul Z (Sunday) (6.7nm SE of Brize Norton) Airspace: Brize Norton CTR (Class: D)

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRPROX REPORT No Date/Time: 18 Aug Z

AIRPROX REPORT No Date/Time: 31 May Z (Saturday)

Date: 09 Apr 2017 Time: 1305Z Position: 5357N 00245W Location: 2nm east of Cockerham

CPA 1711:56 R44 A15 EC135 A14 100ft V 0.2nm H. Wolverhampton Halfpenny Green

Date: 27 Jun 2018 Time: 0919Z Position: 5331N 00030W Location: ivo Hibaldstow parachuting site

Date: 21 May 2015 Time: 1951 (Twilight) Position: 5132N 00004W Location: Victoria Park London

AIRPROX REPORT No

Date: 23 Aug 2017 Time: 0753Z Position: 5111N 00033W Location: near Godalming

Date: 27 Jun 2018 Time: 1510Z Position: 5257N 00033W Location: Barkston Heath

AIRPROX REPORT No Date/Time: 17 Jul Z. (5nm NE Silverstone) Airspace: Lon FIR (Class: G)

AIRPROX REPORT No Date/Time: 20 Dec Z

AIRPROX REPORT No Date/Time: 26 Jul Z 5133N 00106W (3nm FIN APP RW01 Benson - elev 203ft) Airspace: MATZ/FIR (Class: G)

AIRPROX REPORT No Date/Time: 28 Jun Z (Saturday)

AIRPROX REPORT No Date/Time: 11 Mar Z

Date: 26 Jan 2018 Time: 1233Z Position: 5116N 00208W Location: Bratton Camp launch site 1

CPA2 1256: ft V/2.8nm H

Date: 08 Dec 2016 Time: 1628Z (Twilight) Position: 5114N 00049W Location: 3nm SW Farnborough

Date: 16 Jan 2018 Time: 1227Z Position: 5128N 00025W Location: Heathrow airport

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRPROX REPORT No Date/Time: 22 May Z. (2.5nm WNW Gloucester/Staverton) Airspace: Lon FIR (Class: G)

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

Date: 25 Apr 2016 Time: 1714Z Position: 5107N 00024W Location: 10nm W Gatwick airport

AIRPROX REPORT No Date/Time: 10 Oct Z. (North Weald Base Leg RW02 LH - elev 321ft) Airspace: Lon FIR (Class: G)

Radar derived Levels show Mode C 1013mb 27:52 PA :32 27:16 037

SAFETYSENSE LEAFLET AIR TRAFFIC SERVICES OUTSIDE CONTROLLED AIRSPACE

USE OF RADAR IN THE APPROACH CONTROL SERVICE

Primary. Contact 1. CPA 1535:31 100ft V/0.2nm H. Primary

Total Risk A Risk B Risk C Risk D Risk E Airspace (Class) Cranwell ATZ (G) London FIR (G) London FIR (G) London FIR (G) London FIR (G)

Radar derived Levels show

AIR LAW AND ATC PROCEDURES

B :50 A :50 A12 07:10 A12 A12 07:26 A13 A14

AIRPROX REPORT No Date/Time: 11 Jul Z. (9.4nm WSW RAF Linton-on-Ouse) Airspace: Vale of York AIAA (Class: G)

GENERAL INFORMATION Aircraft #1 Aircraft #2

EMB :40 A43 A38 A35 A34 43:28 A29

AIRPROX REPORT No Date/Time: 31 Oct Z. NNW of Wyton - elev 135ft) Airspace: London FIR/ATZ (Class: G)

Assessment Summary Sheet for UKAB Meeting on 22 nd Jul 2015

C :34 A62 14:14 A50 LTMA

VISITING LASHAM BY AIR

CPA 0833: ft V 0.4nm H F186 F189 F173 33:16 F175

AIRPROX REPORT No Date/Time: 16 Feb Z. Douglas Platform - elev 146ft) Airspace: Liverpool Bay HTZ (Class: G)

Radar derived Levels show Mode C 1013hPa M185 FL : : :10 F406

VFR PHRASEOLOGY. The word IMMEDIATELY should only be used when immediate action is required for safety reasons.

AIRPROX REPORT No Date/Time: 1 May Z. (9nm SW Southend) Airspace: Lon FIR (Class: G)

SPORT AVIATION CORP LTD

Collision Avoidance UPL Safety Seminar 2012

Investigation Report

AIRPROX REPORT No

AIRCRAFT INCIDENT REPORT

SECTION 4 - APPROACH CONTROL PROCEDURES

ENR 1.14 AIR TRAFFIC INCIDENTS

AVIATION INVESTIGATION REPORT A00Q0116 RISK OF COLLISION

C560X. Tutor(A) Tutor(B) AIRPROX REPORT No Date/Time: 1 Apr Z 5144N 00115W (15nm N CPT) Airspace: Oxford AIAA (Class: G)

Air Law. Iain Darby NAPC/PH-NSIL IAEA. International Atomic Energy Agency

CHAPTER 5 SEPARATION METHODS AND MINIMA

Number April 2016

helicopter? Fixed wing 4p58 HINDSIGHT SITUATIONAL EXAMPLE

Chapter 6. Airports Authority of India Manual of Air Traffic Services Part 1

AIRPROX REPORT No Date/Time: 24 Sep Z (Saturday) N of Shoreham Airport - elev 7ft) Airspace: London FIR (Class: G)

Contents. Subpart A General 91.1 Purpose... 7

COLLISION AVOIDANCE FOR RPAS

NETWORK MANAGER - SISG SAFETY STUDY

AERODROME OPERATIONS 1 INTRODUCTION

SAFETY BULLETIN. One Level of Safety Worldwide Safety Bulletin No. 05SAB004 5 July 2004

IFR SEPARATION USING RADAR

AIRPROX REPORT No Date/Time: 6 Mar Z. finals RW19 at Valley - elev 36ft) Airspace: Valley AIAA/FIR (Class: G)

Operating Safely. A Fundamental Guide to FAA RADAR Operations. Federal Aviation Administration Near Airports

21 November 2016, 18:06 UTC Coordinates --- Altitude Approximately 1700 ft above mean sea level Air traffic service

INTERNATIONAL VIRTUAL AVIATION ORGANISATION CANADIAN AIR TRAFFIC CONTROL PHRASEOLOGY ATC OPERATIONS DECEMBER 2016 BY: MATHIEU LAFLAMME

GENERAL AVIATION ALLIANCE Partnership in Aviation

Transcription:

AIRPROX REPORT No 2016140 Date: 18 Jul 2016 Time: 1441Z Position: 5112N 00128W Location: Picket Piece, Hampshire PART A: SUMMARY OF INFORMATION REPORTED TO UKAB Recorded Aircraft 1 Aircraft 2 Aircraft Paramotor A400 Operator Civ Club HQ Air (Ops) Airspace Lon FIR Lon FIR Class G G Rules VFR IFR Service None Traffic Provider Boscombe Down Altitude/FL 2200ft Transponder Nil A, C, S Reported Colours Grey Lighting Nil HISLs, Nav, Take-off light. Conditions VMC VMC Visibility Altitude/FL 2000ft Altimeter NK QFE (1007hPa) Heading 080 northerly Speed NK 220kt ACAS/TAS Not fitted TCAS II Alert N/A None Separation Reported 0ft V 600ft H 0ft V/100m H Recorded NK THE PARAMOTOR PILOT reports that they were attending the British Paramotor Team training weekend as a guest conducting their first thermalling experience in preparation for the World Championships to be held nearby later in the year. A NOTAM d zone had been established for their training and they briefed beforehand that they expected to stay within the zone and remain clear of the Middle Wallop MATZ. They were thermalling engine-off and well within the circumference of the NOTAM, although slightly above its notified ceiling. Whilst in a left-hand thermal and heading 080, they saw what they believed was a C130 coming from the south-east at the same altitude. It passed with an estimated 600ft separation and then altered course to the west. There was no indication that the other pilot took any avoiding action or saw the paramotors. On seeing the C130, the paramotor pilot turned abruptly to the right to fly 090 away from it and hoped to avoid any wake turbulence; she commented that she thought she was going to die. The other paramotor pilot also took avoiding action and thought that the C130 passed between them, although he didn t assess that he was in any danger. The weather was clear without any haze, and they were engaged in a notified activity that meant their position should have been predictable for any military flight planner they opined. She assessed the risk of collision as High. THE A400 PILOT reports that whilst vectoring for a PAR for RW23 at Boscombe Down, they were configuring the aircraft for the approach during the crosswind leg of the instrument pattern. As they rolled out of the turn onto a northerly heading, a single paramotor was seen approximately 300m away, co-altitude in the 1130 position. The paramotor appeared to be turning away from the aircraft as it passed. He didn t take any avoiding action because once sighted it was quickly apparent that it would pass down the left-hand-side of the aircraft and to turn right would have meant losing sight of it. They reported the presence of the paramotor to the Boscombe Director and continued the approach. He assessed the risk of collision as High. 1

THE BOSCOMBE DIRECTOR reports that the A400 was receiving a Traffic Service in the radar pattern for an instrument approach. When it was late downwind, she gave Traffic Information on an intermittent contact, which, although not displaying SSR, she could see on the PAR radar was indicating well below. The A400 pilot then reported that a paraglider had just flown down his lefthand-side. Nothing was immediately apparent on the radar, but a few moments later an intermittent contact displayed in the vicinity of the reported position of the paraglider. She tried to maintain track ident on it ready for the A400 s next approach because the danger area to the north of Boscombe, and Netheravon were active, precluding a right-hand pattern. However, on climb-out, the A400 pilot requested a northerly pattern and reported that there were numerous paragliders on the approach centreline. She therefore negotiated a turn back through the overhead for the following pattern. Once again, the A400 encountered a further paraglider on the nose and requested to deviate from her vectors. An Airprox was not reported on frequency at the time. She perceived the severity of the incident as Medium. THE BOSCOMBE SUPERVISOR reports that he did not witness the first radar controlled approach by the A400. But he was made aware of the conflicting traffic within the local airspace and so monitored the second approach, during which he witnessed the difficulty that the conflicting traffic was causing the Director. Most of the conflicting traffic was not IFF equipped, or in communication with Boscombe ATC. Factual Background The weather at Boscombe Down was recorded as follows: METAR EGDM 181350Z 23003KT 9999 FEW040 27/17 Q1021 BLU NOSIG= The NOTAM issued is reproduced below: Phone No. Deleted Relevant portions of the tape transcripts between Boscombe Director and BDN52 are below: From To Speech Transcription Time Dir A400 {A400 c/s} set Boscombe QFE 1-0-0-7. 14.38.57 A400 Dir Set Boscombe QFE 1-0-0-7, {A400 c/s}. 14.39.02 Dir A400 {A400 c/s} descend to height 2500ft. 14.39.07 Dir A400 {A400 c/s}, continue descent to height 2000ft, cockpit checks, report complete. 14.40.20 A400 Dir Descend to 2000, {A400 c/s} 14.40.25 A400 Dir {A400 c/s}, checks to come, happy for vectors. 14.40.43 Dir A400 {A400 c/s}. 14.40.48 Dir A400 {A400 c/s}, intermittent contact right 1 o clock, 5 miles, crossing right-left, no height information. 14.41.27 A400 Dir A400 c/s. 14.41.34 Dir A400 {A400 c/s}, that track is indicating well below on PAR. 14.41.37 A400 Dir And {A400 c/s}, just had a paraglider in this vicinity, just pass passed out left hand side. 14.41.40 Dir A400 {A400 c/s}, roger, the previous reported traffic is in your right 1 o clock, at 1 and a half miles, 14.41.49 now, um, crossing right-left, indicating well below on PAR. A400 Dir {A400 c/s}, yeah, looks like a few paragliders in this vicinity. 14.41.58 2

The A400 was cleared by Boscombe Director to descend from 5000ft to 2500ft QFE 1007 hpa initially, and then further cleared to 2000ft. However, at the time that he flew over the paramotor activity he was at 2200ft QFE, the equivalent of 2600ft amsl. The paramotor did not display on the radar replay. Analysis and Investigation Military ATM Figure 1 1441:40 A400 squawking 2605, paramotor not visible. The A400 pilot reported during vectoring for a PAR to RW23 that he saw a single paramotor pass approximately 100m down the left-hand side at the same altitude. The pilot reported that the paramotor appeared to be turning away. The controller reported that the A400 was under a Traffic Service and, when it was late downwind in the instrument pattern, called an intermittent contact to the aircraft. Using the PAR console, the controller ascertained that this contact was indicating well below and the tape transcript correlates this information. Shortly after, the A400 pilot reported the paramotor to the controller. The controller reported nothing showing immediately on radar but a short time afterwards an intermittent contact appeared. The prime barrier in this incident for the A400 pilot was see and avoid. A paramotor would be unlikely to show on radar due to its limited refractive area and material and its low speed, which may have been below the threshold for display. Without any form of conspicuity on the paramotor, the controller would have been unlikely to have seen any permanent contact, and in this case the contact could quite easily have not been present on the display. A NOTAM was active that day for paramotor activity at Picket Piece (close vicinity to the Airprox location), but no 3

consultation or discussion about the NOTAM is known to have occurred between any parties involved. Subsequent discussion with the unit indicated that the NOTAM was plotted (in the briefing room) on the day, and the controller would have been briefed about local active NOTAMs before taking position. On subsequently speaking with the paramotor operator, it transpired that they were conducting rehearsals for a competition with 2 paramotors in the air at the time. The location is not routinely used for multiple launches and the NOTAM was issued due to the type (competition practice) and increased paramotor activity. The operator indicated that they were unaware of the proximity of Picket Piece to the Boscombe Down radar training circuit, and would be open to future engagement with Boscombe Down ATC; this has since been facilitated via email. UKAB Secretariat The paramotor and A400 pilots shared an equal responsibility for collision avoidance and not to operate in such proximity to other aircraft as to create a collision hazard. If the incident geometry is considered as overtaking then the paramotor pilot had right of way and the A400 pilot was required to keep out of the way of the other aircraft by altering course to the right 1. A paramotor is defined as a glider under ANO 2009 Article 255 [the regulations in force at the time]; therefore, if the geometry is considered as converging then the A400 pilot was required to give way. Comments HQ Air Command The most positive thing to come from this event is that the paramotor operators and Boscombe Down have now established communication such that they can increase awareness of possible conflicting activities in the future. Good communication should help inform other airspace users that activity could extend beyond the area indicated on the NOTAM warning. However, on the day, both aircraft were in Class G airspace and since the paramotor does not carry any electronic conspicuity equipment and they only rarely paint on primary radar, the only barrier remaining was see-and-avoid. Summary An Airprox was reported when a Paramotor and an A400 flew into proximity at 1441 on Monday 18 th July 2016. Both pilots were operating under VFR in VMC, the A400 pilot in receipt of a Traffic Service from Boscombe. The Paramotor was not receiving an ATS. PART B: SUMMARY OF THE BOARD'S DISCUSSIONS Information available consisted of reports from the pilots of both aircraft, transcripts of the relevant RT frequencies, radar photographs/video recordings, reports from the air traffic controllers involved and reports from the appropriate ATC and operating authorities. The Board first commended the paramotor event organising authority for their pre-planning and issuing of a NOTAM. However, observing that the NOTAM was a warning of the activity only and not an avoidance area, members wondered whether they had thought that this might afford them greater protection than it in fact did. They also wondered why the NOTAM had not extended high enough to encompass all of the event s activities given that the paramotor involved in the Airprox was operating approximately 600ft above its level, and what amount of thought had gone into liaison with other airspace users in the area given that it appeared that the paramotors involved did not realise that their event was taking place underneath an active traffic pattern on the extended centreline of Boscombe Down. Some members thought it possible that the Paramotor pilots were not likely to be aware of how their activity would affect the Boscombe instrument pattern, but others thought that 1 SERA.3210 Right-of-way (c)(3) Overtaking. 4

most aviators should know that activity 10nms on the extended centreline of an airfield up to an altitude of nearly 2000ft would likely cause an issue for IFR traffic. Ultimately, see-and-avoid was the only remaining barrier available to the paramotor pilots, and the Board noted that although they did see the A400 in time to manoeuvre out of the way to some extent, the ability of a paramotor to effectively avoid was extremely limited due to its dynamics compared to a rapidly approaching aircraft. A member of the Board with paragliding experience also commented that there was a very real risk from wake turbulence causing an accident, as much as from collision itself. As such, the Paramotor pilot s concerns about the risk posed were justified, and the speed of the paramotor would have precluded getting out of the way any faster than it did. All of this pointed to the need for effective deconfliction of such activities from other aircraft rather than relying on dynamic avoidance, and the Board were heartened to hear that the paragliding organisers had now established an effective liaison link with the local airfields. Turning to the A400 pilot s actions, the Board opined that he should have been aware of the NOTAM as part of his pre-flight planning and briefing, and could therefore have probably anticipated that paramotors might be operating not only within but around its extremities. The Board noted that the NOTAM was active up to 1500ft agl, and although the A400 was above it whilst descending to 2000ft on the Boscombe Down QFE (approx. 2400ft amsl), members noted that the NOTAM was unusual in that it stated its top height as 1500ft agl in the main text. Although it also stated later that this equated to 1970ft amsl, they thought that this could easily have been overlooked such that the A400 pilot might have thought he was further above the NOTAM than he was whilst flying in the Boscombe Down radar pattern. Turning to the dynamics of the incident itself, and noting that the A400 pilot saw the paramotor as he rolled out onto a base leg heading, the Board thought that he had probably seen it as soon as he could reasonably be expected, particularly due to its likely small cross-section and effectively stationary crossing rate due to its low speed. Although he had had enough time to assess that it was going away, and that maintaining track was perceived to be the best action, the A400 pilot only had 2-3 secs between first sighting the paramotor and it passing his aircraft, and was therefore unlikely to have been able to materially change the separation anyway had he attempted to manoeuvre. The Board noted that although the A400 was fitted with TCAS, the paramotor did not have a CWS or a transponder and so prior warning from the electronic conspicuity barrier was not available to the A400 pilot. Furthermore, the paramotor did not present a solid radar contact (due either to lack of radar cross-section, or because of the radar display s speed filters). As a result, even though he was receiving a Traffic Service, ATC were not able to pass conclusive Traffic Information to him, rendering another barrier ineffective. Ultimately, members noted that it was for the A400 pilot to give way to the paramotor (the paramotor qualifies as a glider under ANO rules), but he could only do so once he had seen it or been informed specifically about its presence. Finally, the Board looked at the actions of the Air Traffic Controller. Members noted that the NOTAM was available to view in the air traffic briefing room, but the Board did not know whether it had been plotted on the radar screen, or whether the controller had fully assimilated the risk to the radar pattern. Some members wondered whether the radar pattern height or geometry could have been changed for the duration of the paramotor activity, but air traffic members quickly advised that this was not as easy as first seems, and can cause other unforeseen problems with extended or foreshortened patterns affecting different airfields and ground obstacles. Furthermore, noting the proximity of the danger areas to the north and south of Boscombe Down, they opined that ATC were already fairly restricted in options without adding further complications. Notwithstanding, the Board were left with the feeling that Boscombe Down ATC had not done all that they could have to mitigate the presence of the NOTAM and its impact on their radar pattern once they had become aware of its existence. In this respect, some members thought that had the controller assimilated the full details of the NOTAM he could have given the A400 pilot generic Traffic Information on the NOTAM and associated likely paramotor activity before the A400 turned base leg, albeit they also noted that the paramotors did not show on his radar (other than the fleeting contact on PAR) and therefore precise Traffic Information could not be given. However, with a contact number printed on the NOTAM, ultimately the Board thought it disappointing that no-one from Boscombe ATC had contacted the paramotor operators beforehand. That said, they were heartened to hear that contact had been made subsequent to this incident to ensure that future liaison should take place. 5

In determining the cause of the Airprox, the Board decided that, notwithstanding the seeming lack of foresight and liaison between the paramotor operators and Boscombe Down, because both aircraft were operating as they were entitled to do in Class G airspace, the incident was best described as a conflict in Class G airspace. However, contributory factors were then discussed at length. Some members opined that because the paramotor was operating above the NOTAM this should be considered a factor. However, the majority thought that the paramotors were entitled to do so and so this should not be a contributory factor. Notwithstanding, the Board did agree that a lack of liaison between Boscombe Down ATC and the paramotor operators was contributory; much more could have been done to deconflict their respective activities had they both had the foresight to understand the impact that the NOTAM might have on the Boscombe Down IFR pattern. Turning to the risk, the Board were clear that they were there to assess the risk of collision rather than risk due to wake turbulence. Even so, and notwithstanding that the paramotor pilot had attempted to turn out of the way, this was still a very close encounter in which providence had played a major part; they assessed the risk as Category A, separation had been reduced to the bare minimum. PART C: ASSESSMENT OF CAUSE AND RISK Cause: A conflict in Class G. Contributory Factor: Lack of liaison between the paramotor operators and Boscombe Down ATC. Degree of Risk: A. 6