The CIX VFR Club The Stapleford Gang
Club Events - Over the Sea to Rotterdam
Tulips to...?
Home > Operations > Events > Event History 2005 > Rotterdam
The CIX VFR Club
Club Events - Over the sea to Rotterdam
Tulips to...?
 Briefing Wednesday 2nd February 2005 
A trip abroad to celebrate the Club's 1st Anniversary
Start Time 19:00 to 20:00 zulu
Start Location The Main Apron at Biggin Hill
Briefing Aim to be be at Rotterdam as soon as possible around 21:30 zulu (22:30 local). En route flight time is approximately 1:50 in still air at 100 knots.
Route (Visual references)

Biggin Hill - Dover - Calais - Ostende - Knokke-Heist - Middelburg - VRP Hotel (N51° 58', E004° 08') - Whiskey (N51° 58', E004° 13') - Rotterdam (EHRD) : FSNavigator Flightplan

Route (Radio Navaid References) EGKB - DVR(114.95) - Calais - KOK(114.50) - COA(110.05) - HSD(114.15) - VRP Hotel (N51° 58', E004° 08') - Whiskey (N51° 58', E004° 13') - EHRD : FSNavigator Flightplan
Procedures EHRD VFR Entry/Exit procedures
Charts Coastline map :Netherlands VFR chart : Rotterdam VFR Approach Chart : Rotterdam VFR Circuits
Class C Airspace There is no Class C airspace in the UK, but Rotterdam CTR is Class C. The rules, so far as VFR traffic is concerned, are the same as for Class D, except that IFR traffic and VFR traffic are procedurally separated, i.e. cannot be closer than 5nm horizontally and 1000 feet vertically. The effect of this might be that we, as VFR traffic, have to orbit at one of the holding points (Sierra or Tango) to keep clear of IFR traffic. There is no procedural separation requirement VFR to VFR. In Class D airspace, IFR is procedurally separated from IFR traffic, but there is no procedural separation IFR to VFR, or VFR to VFR.
Special Notes Be aware that the base of the Rotterdam TMA commences at 2500 feet at the south bank of the Westerschelde, some 2nm south of Middelburg. VFR aircraft should be below 2500 feet altitude at this point. Position to enter the CTA at VRP Whiskey (Wisky in the FSNav Flightplan), not above 1500 feet.

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". In our case 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 evryyone to be quiet on Teamspeak until ATC call again (which they will).
Acknowledgements Our Thanks to Dutch VACC for help in compiling these notes.
  Valid XHTML 1.0 Strict Valid CSS! Version 1.3 - 12:00 ZULU 09/12/09