BFGC’s Incident Summary 2017-18

1. BFGC’s Incident Summary 2017-18 Richard Peake CSO

2. Incidents raised during 2017-18 Flying season These are recorded in the Club Safety Record for future lessons. Those that meet criteria are reported to the BGA either by phone, email or formally using the incident accident forms supplied for that purpose. The following slides contain reported incidents that occurred at BFGC and recorded for later use. Incident report 2017-18 version 1.0

3. K13 parked close to the threshold of RW30 and considered to be a risk. Conditions were field wet and boggy restricting flying operations to the track. The immediate risk was the overflight of aircraft during landing back on the track which is unacceptable This slows the launch process and causes more restrictive operations and demands more complex considerations from pilots and ground crews to maintain safety. Incident report 2017-18 version 1.0

4. Operating from the top end and on the track. Tractor left on threshold of RW 12, the operating track. Whilst K13 reported downwind. Noticed very late by ground crew and cleared as K13 turned final removing collision risk The tractor was returning from towing another aircraft to the non flying side of the track and a novice member (non flyer) had just stopped the tractor on the track not understanding the situation. The pilot had already called downwind and had probably scanned the landing site (track) The tractor suddenly appearing on the threshold had changed the picture of the landing area considerably. Possibly unnoticed by a busy pilot now turning from base leg. Incident report 2017-18 version 1.0

5. K13 lose battery cable snagging controls in JZE Identified during DI and rectified before releasing the ac to flying status. There have been several incidents of this nature this year and one was identified post DI at the launch point and a solo flight. Possible fatal incident if the controls had become entangled. Incident report 2017-18 version 1.0

6. Loss of power on winch during launch –K13 launch incident occurred twice during the first launches of the day and was then identified following a thorough DI by the operator Raised by CFI Winch driver allowed himself to be interrupted during DI and failed to fully open the gas taps causing a fuel starvation scenario when the winch was powered up. Incident report 2017-18 version 1.0

7. Ground loop accident G-CJLO R-Way 12 Categorised as a minor accident with no injuries. Pilot allowed himself to become compromised and overloaded having elected to return to the hill with little energy and height and not adjusting original landing plan. Aircraft landed on occupied runway and ground looped having contact the long grass on the left side of the runway whilst attempting to remain as far left as was possible to avoid collision. In this case the Pilot submitted a comprehensive report and admitted that lack of currency and tiredness were contributory factors in this incident. Incident report 2017-18 version 1.0

8. Single Seat Glider Landed Gear up RW 30 Glass Aircraft landed with gear retracted. Landed on the grass 30 runway sustaining no damage or personal injuries There has been two gear Up incidents this year with similar aircraft and very different levels of experience It is noteworthy that both Pilots provided a post flight report. Distracted during vital stages of the flight offered as a reason. Fatigue as a factor should not be ruled out in either of these incidents considering the experience of the crews. Incident report 2017-18 version 1.0

9. Aircraft ASK8 damaged in hanger unnoticed Noticed by Pilot when entering hanger to DI another aircraft. Flying operations were taking place at the time. The K21 elevator was found embedded in a K8 wing causing distortion to the wing fabric. Our inspectors completed a minor repair and no other damage was found. Incident report 2017-18 version 1.0

10. Air prox reported to club by CSO Pennine Soaring Club (PSC) A video was presented to the club showing a BFGC Aircraft passing close to a para glider on several occasions and presented as a near miss. The video evidence showed although close and appearing aggressive there was no actual danger of collision The incident occurred on the west face of Parlick Hill, in good visibility and weak soaring conditions where only parts of the hill were working. This naturally concentrates aircraft and other users increasing workloads and risks of collision. Incident report 2017-18 version 1.0

11. Open Cirrus destroyed during ridge soaring incident Pilot suffered minor injuries Incident occurred at other site. (Eden Soaring) The club and its pilots could benefit from a report of the incident. Incident report 2017-18 version 1.0

12. Visitor evening incident- considered a near miss. A cable was attached to K13 whilst visitors standing near and ahead of the unused cable and strop. Fortunately this was noticed by Flight logger and another pilot from the DP Van- The launch was stopped but only after a verbal prompt from the CSO. This allowed the removal of the spare cable from proximity of the other aircraft and visitors were move back before continuing with the launch. Incident report 2017-18 version 1.0

13. Launch cable failed to release from ASK13 during winch launch Aircraft landed with strop attached. On inspection links appeared deformed due to stretching or crushing. Instructor and Pilot attempted cable release during and after release. However unable to recreate incident on the ground. Incident report 2017-18 version 1.0

14. K13 landed long and almost collided with fence following simulated launch failure Pilot briefed the instructor that they would to go left during eventuality brief and attempted a land ahead late from what should have been a go around, resulting in Instructor take over and late landing. There were complications where the instructor suffered minor injury when the brake handle shot rearwards unexpectedly trapping their hand, delaying the takeover by a few vital seconds Incident report 2017-18 version 1.0

15. K13 Solo flight suffered potential launch failure after the cable caught on the edge of the track momentarily. Whilst operating from the top end on Runway 12 and on the track it was agreed that to speed up the launch process a K13 with a solo pilot was OK to launch from the right hand side on the grass. The Duty instructor briefed the pilot on what to expect as the lead of the cable was increased now that the cables had been pulled across from the track. The cables were checked visibly by the Pilot who actually walked a length of the wire to ensure it was clear however during the launch the rotation appeared to be delayed as the wire caught on the edge of the track much further down. The aircraft flew level for a few seconds and the cable cleared as it pulled straight and the launch continued with no further incidents to a useful height in excess of 1000 feet. Incident report 2017-18 version 1.0

16. How can you report an incident quickly On the day verbally to the Duty Instructor, Duty manager or a member of the Duty crew You can also complete the incident report form held in the DP Van or Main Office in the Club House You can also use the dedicated email address safety@bfgc.co.uk Incident report 2017-18 version 1.0

17. Ground Operations incidents These are not generally reported out side of the club and not to the BGA but are recorded and follow up actions encouraged to improve safety These can be reported in the same way although you wouldn't complete a BGA Incident report Incident report 2017-18 version 1.0

18. Any Questions Comments or feedback please Please discuss the implications of these incidents and ways we can reduce their occurrence with pilots and your instructors Forward your ideas to the safety@bfgc.co.uk mailbox Incident report 2017-18 version 1.0