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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

AIRPROX REPORT No Date/Time: 18 Aug Z

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: 11 Mar Z

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

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

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

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

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

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

AIRPROX REPORT No

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

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

Paraglider (not radar derived) Reported CPA 0836:58

AIRPROX REPORT No Date/Time: 17 Jul Z. (5nm NE Silverstone) Airspace: Lon FIR (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 Date/Time: 10 Oct Z. (North Weald Base Leg RW02 LH - elev 321ft) Airspace: Lon FIR (Class: G)

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

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

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

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

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

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

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

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

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

EMB :40 A43 A38 A35 A34 43:28 A29

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

AIRPROX REPORT No Date/Time: 20 Dec Z

CPA2 1256: ft V/2.8nm H

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

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

SAFETYSENSE LEAFLET AIR TRAFFIC SERVICES OUTSIDE CONTROLLED AIRSPACE

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

C :34 A62 14:14 A50 LTMA

GENERAL INFORMATION Aircraft #1 Aircraft #2

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

AIRPROX REPORT No Date/Time: 7 Sep Z. of Culdrose - Helford River) Airspace: CMATZ (Class: G)

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

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

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)

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

Contents. Subpart A General 91.1 Purpose... 7

Collision Avoidance UPL Safety Seminar 2012

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

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

AIRPROX REPORT No

Radar derived Levels show

AIR LAW AND ATC PROCEDURES

USE OF RADAR IN THE APPROACH CONTROL SERVICE

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

Assessment Summary Sheet for UKAB Meeting on 22 nd Jul 2015

helicopter? Fixed wing 4p58 HINDSIGHT SITUATIONAL EXAMPLE

LETTER OF AGREEMENT. Between. and RELATING TO

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

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

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

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

AVIATION INVESTIGATION REPORT A00Q0116 RISK OF COLLISION

AIRSPACE CO-ORDINATION NOTICE Safety and Airspace Regulation Group ACN Reference: Version: Date: Date of Original

CAR Section II Series I Part VIII is proposed to be amended. The proposed amendments are shown in subsequent affect paragraphs.

PASCO (Pacific Soaring Council) ADVISORY TO GLIDER PILOTS

129 th RQW/SE P.O. Box 103, MS#1 Moffett Federal Airfield, CA

SECTION 4 - APPROACH CONTROL PROCEDURES

Safety Brief. 21st March Operations in Somali Airspace

VISITING LASHAM BY AIR

ATC PRACTICE. 20 miles South inbound landing Lincoln 22 miles SW inbound for the Denton. airport

Virtual Royal Air Force 45 (R) Sqn Syllabus

ENR 1.14 AIR TRAFFIC INCIDENTS

Assessment Summary Sheet for UKAB Meeting on 9 th October 2013

Virtual Royal Air Force 208 (R) Sqn Syllabus

Final Report of the Aircraft Accident Investigation Bureau

SECTION 6 - SEPARATION STANDARDS

Fresno Area Mid-Air Collision Avoidance Program (MACA)

AIRSPACE INFRINGEMENTS

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

Transcription:

AIRPROX REPORT No 2018212 Date: 14 Aug 2018 Time: 1443Z Position: 5225N 00040E Location: Lakenheath PART A: SUMMARY OF INFORMATION REPORTED TO UKAB Recorded Aircraft 1 Aircraft 2 Aircraft F15 Duo Discus glider Operator Foreign Mil Civ Gld Airspace London FIR London FIR Class G G Rules VFR VFR Service ACS Basic Provider Lakenheath Lakenheath Zone 1 Altitude/FL 3100ft NK Transponder A, C, S Not fitted Reported Colours Grey White Lighting Anti-cols, Nil Position lights Conditions VMC VMC Visibility 10km 10nm Altitude/FL 3200ft 2500ft Altimeter RPS QFE Heading 270 Circling Speed 330kt 52kt ACAS/TAS Not fitted FLARM Alert None Separation Reported 100ft V/100m H 0ft V/250m H Recorded NK V/<0.1nm H THE F15 PILOT reports that he was in a flight of 2 F15s, on a visual recovery to Lakenheath at FL190. At 25nm, they were advised of multiple gliders to the east, north-east and north of the field, including in the vicinity of the initial point. 2 The weather was scattered at 4000-6000ft. They conducted a descent with the intention of reporting high-initial due to the clouds and glider traffic, and found a significant break in the clouds just east of Thetford, which is immediately south of the approach corridor to initial- RW24. Lakenheath App then handed the F15s over to Lakenheath Twr, who did not pass updates on the glider traffic. On the 072 radial inbound to the Lakenheath TACAN at 7DME and 3500ft MSL, they spotted a glider passing down the right-hand-side of the formation at about 0.5nm from the formation, but not a collision risk. About 15 sec later at 3200ft at 5.2DME, they saw a glider in a sharp right-turn at 10 o clock, 100m away and about 100ft below. The lead pilot directed the formation to level off and, 5sec later, they were clear of the glider. He assessed the risk of collision as High. THE DUO DISCUS PILOT reports that he was participating in a gliding competition, in Class G airspace and receiving a Basic Service from Lakenheath Zone for safety (he recalled). At the time of the Airprox he was beginning to thermal to gain height. He recalled being given Traffic Information on the inbound formation and then saw two fast-jets a mile away. He decided to continue to circle for conspicuity and saw them fly safely past, he felt that there was adequate separation. He assessed the risk of collision as Low. 1 As recalled by the pilot 2 The military Initial Point is a point that fast-jet aircraft flow through at circuit height as they join the airfield for a run-andbreak, normally 3nm just deadside on the extended centreline. 1

THE LAKENHEATH APP CONTROLLER reports that the F15s were at FL190 when they called for a Traffic Service. They were given a direct initial approach to RW24 and descent to 2500ft. He then issued a blanket Traffic Information call about multiple gliders north and east of Lakenheath. The pilot acknowledged the call and asked for confirmation of the location of the gliders, which was given, along with information on further traffic on the RW24 centreline. The pilot requested a high tactical initial at FL80, but the controller could not accommodate this request because of the cloud-base being reported as 4900ft at Lakenheath. The pilot then asked to fly through at FL60 to re-enter at point D (a point 5nm east of the runway), this request was approved, and he was told to switch to Tower frequency. THE LAKENHEATH TOWER CONTROLLER reports that it was a clear day and he was given a call from radar to tell him that a glider pilot had called to inform them that there were multiple gliders to the north/northwest of RAF Lakenheath, routing to the southwest; a few gliders could be seen on the radar screen. They were informed that the F15s were coming through initial, this was updated to say that due to the glider activity they would recover from the south at a higher altitude. They approached from the south-east and, once on frequency, reported that they had passed over a glider by 300ft. The glider was not visible on the radar, and the Tower controller was not visual with it. THE LAKENHEATH VCR SUPERVISOR reports that it was a clear day and glider activity was known to be present in the area. They were given an advisory from the Radar App controller that there was a heavy concentration of gliders to the north of the Lakenheath ATZ. There were several primary contacts on the Tower Display Workstation (TDW), however, the glider targets are usually intermittent and not transponder equipped, so no height information is displayed. The Wing aircraft were beginning their arrival phase and the radar controller was issuing Traffic Information as needed, prior to switching the aircraft to Tower. When necessary, Tower also issued Traffic Information to arriving aircraft on any primary contacts seen. The F15 flight were inbound for initial RW24 and reported that they had just passed a glider by about 300ft. There were no observed primary targets on the TDW in the vicinity of the F15, so Traffic Information could not be given, and generic Traffic Information had already been passed to them. To their knowledge, all the gliders were clear of the ATZ and in Class G airspace, so operating completely legally. THE LAKENHEATH RADAR SUPERVISOR reports that the F15s were handed over by Swanwick(Mil)to the App controller and had requested initial for their recovery. There was known glider activity in the vicinity of Lakenheath and he observed the App Controller issue multiple traffic calls and updates to the affected recovering aircraft. The F15 pilot changed his request to a high-tactical-initial recovery once he was informed of the glider activity, which would have taken him above all of the glider activity. However, the weather was not what was needed to allow the formation to recover this way. The App controller descended the aircraft to FL50 and sent them to Tower frequency to allow them to descend directly over the field and entre the Tower pattern via Delta, (a point 5nm east of the runway). All information was passed to both the Tower controller and the pilots, and the F15s were sent to the frequency 10nm east of the field. The App controller was not in contact with the glider and there were reports of many more gliders than they could see on the radar. Other aircraft recovering at the same time recovered via direct initial without any issues. Factual Background The weather at Lakenheath was recorded as follows: METAR EGUL 141356Z AUTO 26007KT 9999 FEW039 BKN049 22/13 A2998 RMK AO2 SLP155 T02220127 METAR EGUL 141456Z AUTO 28011KT 9999 FEW044 SCT055 24/13 A2997 RMK AO2 SLP152 T02410127 58001 2

At Figure 1 is a guide to arrivals at RAF Lakenheath: Analysis and Investigation UKAB Secretariat Figure 1 Screenshots taken from the NATS radar (which is not the radar seen by the Lakenheath controllers) show an intermittent primary only contact, thought to be the glider, appear on the radar for two sweeps before fading. 3

Primary return Primary return fades F15s Figure 2: 1443:20 Figure 3 (CPA): 1443:35 F15 0434 Squawk The F15 and glider pilots shared an equal responsibility for collision avoidance and not to operate in such proximity to other aircraft as to create a danger of collision 3. If the incident geometry is considered as head-on or nearly so then both pilots were required to turn to the right 4. If the incident geometry is considered as converging then the F15 pilot was required to give way to the glider 5. Comments USAFE Notwithstanding that the glider pilot was in Class G airspace, just above the CMATZ, and apparently in receipt of a Basic Service from Lakenheath, the wisdom of operating just to the south of the extended centreline of the main instrument runway of one of the busiest fighter bases in the UK must be questioned. Further, one pilot s view of adequate separation is not necessarily another s. BGA It s good to see that glider pilots are making more use of UK FIS than historically has been the case, which led to improved situational awareness for all involved. If not identified on radar, it would be worth giving position reports when operating near the centreline of an active runway because that area is likely to have a higher concentration of traffic. Summary An Airprox was reported when an F15 and a Duo Discus glider flew into proximity near Lakenheath at 1443hrs on Tuesday 14 th August 2018. Both pilots were operating under VFR in VMC, the F15 pilot in receipt of a ACS from Lakenheath Tower. Although the glider pilot reported receiving a Basic Service from Lakenheath Zone, Lakenheath could not find evidence of this on their RT recordings. PART B: SUMMARY OF THE BOARD S DISCUSSIONS Information available consisted of reports from both pilots, transcripts of the relevant R/T frequencies, radar photographs/video recordings, reports from the air traffic controllers involved and reports from the appropriate ATC and operating authorities. 3 MAA RA 2307 paragraph 1 and 2, Avoidance of collisions and SERA.3205 Proximity 4 MAA RA 2307 paragraph 13, Approaching Head-On and SERA.3210 Right-of-way (c)(1) Approaching head-on. 5 MAA RA 2307 paragraph 12, Converging and SERA.3210 Right-of-way (c)(2) Converging. 4

The Board first looked at the actions of the F15 pilots, they had been told about the gliders by ATC, but the cloud-base had constrained the type of approach that they could do. Although they wanted to remain high and overfly initial, they had to descend to get beneath the cloud at some point. Consequently, having found a gap in the clouds as they positioned to join the visual circuit, they ended up flying through the initial point at a similar height to the gliders. One member with military fast-jet experience wondered whether military fast-jet aircrew in general had become fixated on recovering to military airfields via a run-and-break through initials. He opined that if the cloud base was below 3000ft, subject to cloud and operating constraints, it may have been possible to join through Point C and join the circuit downwind, thus avoiding the gliders known to be in the vicinity of initials. As it was, the F15 pilots were fortunate to have become visual with two of gliders and were able to level-off in time to avoid the Airprox glider. The Board were informed by the glider member that the gliders were operating from a local gliding site and were involved in a local gliding competition. Because this competition only concerned local pilots, all of whom were familiar with the local airspace, the competition had not been NOTAM d. As a result of this Airprox, the BGA had reviewed how such local gliding competitions should be promulgated and had subsequently provided new guidance to gliding clubs about when a NOTAM should be issued. In future, irrespective of whether the competition was local or not, when more than 20 gliders are involved a NOTAM will be issued. There followed considerable discussion about this, with some members pointing out that more than even just a few gliders in the vicinity of an aerodrome could still be a problem. The gliding members acknowledged this and recognised the difficulty in setting specific numbers for the issue of a NOTAM. In some mitigation, they informed the Board that the BGA was also encouraging members to talk directly to local ATC units to notify them of competitions or events in their vicinity. They also noted that, in this case, the gliding club had said that they did not have a contact for Lakenheath ATC at the time of the Airprox, and that that was why they had not contacted them. The club had since attended a Regional Airspace User Working Group, and this had now been rectified. The Board were heartened to hear this, although they noted that planning documents such as Pooleys provide a telephone number for ATC or Ops for all units covered, which included all RAF airfields and the majority of civilian ones, and that this could provide a good starting point for notifying any activity to affect. Turning to the glider pilot, although he reported that he had called Lakenheath, they could find no evidence of the call on their frequencies. Nevertheless, the glider pilot reported being aware that the F15s were recovering and so the Board concluded that he was at least listening out on the Zone frequency. He reported seeing the F15s from a mile away, and elected to continue to circle to provide the best visual conspicuity. The Board agreed that his changing aspect probably allowed the F15 pilots to become visual with him. The glider pilot was content with the separation, perhaps because he had the benefit of seeing the F15s from a distance, rather than the likely startle-factor that the F15 pilots had of suddenly seeing the glider in close proximity. That he assessed the risk of collision as low caused some members to wonder whether he had a particularly robust approach to the risks of fastjets flying so close by. Finally, the Board looked at the role of ATC in the incident. Although they could find no evidence of a call on the radar frequencies, it was clear that ATC were at least generically aware of the gliders, and the Tower controller reported that radar had warned them about the gliders operating at initial (albeit without any knowledge of their height). The gliders intermittently showed on the radar, enabling the controllers to provide generic Traffic Information to the recovering aircraft. The USAFE advisor told the Board that, unlike some RAF ATC units, Lakenheath ATC did not possess a FLARM receiver and so had no information on the gliders other than reports from other pilots and the brief intermittent primary radar traces; given their location in an area of intensive gliding activity, the Board commended the purchase of a FLARM receiver to Lakenheath as a means of gaining significantly improved situational awareness of gliders in future. Nevertheless, the Board were clear that the controllers had done their best to provide as much information as possible to the F15 pilots as they recovered to the airfield. In determining the cause of the Airprox the Board quickly agreed that this had been a conflict in Class G, resolved by the F15 pilot. They then discussed the risk and noted that the F15 pilot had reported that he had only seen the glider at the last moment and that the separation had been only 100ft and 5

100m as they flew past. Notwithstanding, the F15 pilot had been able to level off, and the Board assessed that this emergency avoiding action had materially affected the achieved separation. As such, the Board agreed that safety had been much reduced below the norm and therefore the risk was assessed as Category B. PART C: ASSESSMENT OF CAUSE AND RISK Cause: A Conflict in Class G resolved by the F15 pilots. Degree of Risk: B. Safety Barrier Assessment 6 In assessing the effectiveness of the safety barriers associated with this incident, the Board concluded that the key factors had been that: Flight Crew: Situational Awareness and Action were assessed as partially effective because although the F15s knew that there were gliders in the area, the information was only generic. Warning System Operation and Compliance were assessed as ineffective because the FLARM on the glider could not detect the F15s, and the F15s had no collision warning systems installed. See and Avoid were assessed as partially effective because the F15s were able to see the glider, albeit late, and level off. Airprox Barrier Assessment: 2018212 Outside Controlled Airspace ANSP Flight Crew Barrier Regulations, Processes, Procedures & Compliance Manning & Equipment Situational Awareness & Action Warning System Operation & Compliance Regulations, Processes, Procedures, Instructions & Compliance Tactical Planning Situational Awareness & Action Warning System Operation & Compliance See & Avoid Key: Availability Functionality Effectiveness Availability Functionality Effectiveness Barrier Weighting 0% 5% 10% 15% 20% Fully Available Partially Available Not Available Not Present Fully Functional Partially Functional Non Functional Present but Not Used, or N/A Effective Partially Effective Ineffective Not present Not Used 6 The UK Airprox Board scheme for assessing the Availability, Functionality and Effectiveness of safety barriers can be found on the UKAB Website. 6