Briefing | 1st November 2017 |
Overview | The November Event will be a microlight event (flexiwing or 3-axis) and will also be an exercise in map-reading / navigation by using “Ground Features”. (Plan-G may be used to plan your route, but its use for navigation should be eschewed!). You simply have to keep out of danger. |
Start Time and Place | The event may be flown on any day in November. To maximise the chances of flying with other club members use the forum to arrange convenient dates/times to meet up and fly the event. We will be flying from White Waltham (EGLM) to Rochester Airport (EGTO), on the west of the town, with its two grass runways. |
Airmanship | With minimal instrumentation microlights are not permitted "Zone Transits", so no flying straight to Rochester through Heathrow's Control Zone! In any case Heathrow CTR is Class A Airspace, and VFR flights are not permitted within that area anyway. So you will need to plan to fly a southerly loop outside the CTR. Keep out of Biggin Hill's ATZ too, as Microlights are not permitted at Biggin. Microlights also must not overfly built-up areas! If this is impossible to avoid you should plan to be able to "glide clear" of such areas. Remember that microlights tend to have the glide angle of a house-brick in the event of an engine failure! As if all that weren't enough, very careful navigation will be required to avoid and to fly between the Pirbright Danger Area (D132 & D133A) and the Ash Ranges Danger Area (D132). |
Weather | Before starting we will check the weather. If it is unsuitable for our trip as planned, then we will fix it. Something we can do in the simulator - wouldn't it be nice if we could do it in real life! |
What Aircraft can I fly | Any microlight aircraft can be flown in this event – either flexiwing or 3-Axis. |
Flight Planning | Your flight plan should show:
|
Plan-G | There is no pre-prepared Plan-G file of the route, - do your own! BUT please avoid using Plan-G to navigate – part of the “fun” will be to navigate by identifying ground features. (N.b. if flying in company don't blindly follow your companion – you might infringe a danger zone or controlled airspace by doing that!). |
ATC | At the time of publishing this event plan, ATC has not been confirmed. |
Radio Discipline | Take care not to let our Teamspeak chat cut across ATC. Stop any conversation immediately the R/T comes alive, then continue if "he wasn't talking to us". This is difficult because when transmitting on Teamspeak you can't hear the R/T. So be brief on Teamspeak, and be aware that ATC might be trying to get through. If anyone hears an R/T message which seems to be being ignored, just say "ATC is calling G-CIXN" if you have identified the callsign, or "ATC is calling us" which is a cue for everyone to be quiet on Teamspeak until ATC call again (which they will). Remember too that if asked to "Stand By" by ATC, you do not reply - not even "Roger", but simply wait until you are called again. Remember also that there are several different ATC frequencies in use, and you may not be able to hear when communications are taking place. Make sure you have set and know how to use a Teamspeak mute switch. |
Acknowledgements | Event concept: Peter Dodds Briefing: Max Symons. |