Lukas Agerskov (1226374) Posted January 3 Report Share Posted January 3 Cross the Land is upon us, and Copenhagen is part of that. It is a privilege to be able to attend these big events, and the more successful we are, the more likely it is we get chosen for the next one, so we need a nice amount of staffing for this. As we are arrival airport we would need: EKCH_A_GND: Self-explanatory EKCH_A_TWR: Handling arrivals EKCH_C_TWR: Handling departures as well as funnelling arrivals to proper sites. EKCH_W_APP: The arrival routes will go via TIDVU and MONAK most likely, with MONAK route being re-routed to the other side of the airport for better flow management, hence EKCH_W_APP is also needed. EKCH_E_APP: Arrivals from TIDVU EKCH_F_APP: Merge them EKDK_B_CTR: Covering MONAK arrivals, as well as a departures. (EKDK_V_CTR) This position would not be included in the event to EKCH but is needed due to all the enroute traffic to ENBR which will go via EKDK, so if you prefer this position, say the word. Meaning, we need around 10 controllers as a minimum average, evenly distributed. Timeframe is not yet confirmed, but is expected to be between: around 15z-21z, based on the timeslots from previous years. If you are only available some of the event, still please sign up, as some may be available in the beginning, and some at the end. Briefings and Staffing will be produced! 1 Link to comment Share on other sites More sharing options...
Jeppe Seier (1602589) Posted January 3 Report Share Posted January 3 Able S2 Link to comment Share on other sites More sharing options...
Viktor Espenhain (1563351) Posted January 3 Report Share Posted January 3 (edited) Able S2 untill 2100z Edited January 28 by Viktor Espenhain (1563351) Link to comment Share on other sites More sharing options...
Gavin Peter Møller-Jensen (1546788) Posted January 3 Report Share Posted January 3 S2 available Link to comment Share on other sites More sharing options...
Soeren Juul (1327487) Posted January 3 Report Share Posted January 3 (edited) Able S3 Unavailable Edited February 8 by Soeren Juul (1327487) Link to comment Share on other sites More sharing options...
Markus Nielsen (1401513) Posted January 3 Report Share Posted January 3 Able S3 Link to comment Share on other sites More sharing options...
Torben Andersen (861112) Posted January 3 Report Share Posted January 3 (edited) Able C1 Unfortunately unable Edited February 10 by Torben Andersen (861112) http://pcflyer.net/indicators/pilotbadges/861112.png Link to comment Share on other sites More sharing options...
Esben Madsen (1447299) Posted January 3 Report Share Posted January 3 Able C1, hele eventet, gerne EKDK_V :-) Link to comment Share on other sites More sharing options...
Jakob Ek Jensen (1336291) Posted January 3 Report Share Posted January 3 Æjbel C1 Link to comment Share on other sites More sharing options...
Daniel Folsoe (1442076) Posted January 3 Report Share Posted January 3 Æble S3, From start to 1830z Link to comment Share on other sites More sharing options...
Martin Thorsteinsson (1338009) Posted January 5 Report Share Posted January 5 (edited) Able S2 until 20z edit: not able anymore sorry Edited February 9 by Martin Thorsteinsson (1338009) not able to control anymore Link to comment Share on other sites More sharing options...
Morten Jelle (1012739) Posted January 5 Report Share Posted January 5 (edited) Able C3, prefer not to be on APP. Edited January 5 by Morten Jelle (1012739) Morten Jelle VATSIM Network Supervisor - Team Lead Link to comment Share on other sites More sharing options...
Frederik Rosenberg (1401649) Posted January 10 Report Share Posted January 10 Able C1 Link to comment Share on other sites More sharing options...
Kenneth Hald (832365) Posted February 10 Report Share Posted February 10 able Link to comment Share on other sites More sharing options...
Mikkel Lindgren (1003540) Posted February 10 Report Share Posted February 10 (edited) Able C1 16.30-21z. However, I need a 30 minute break somewhere in that timeframe. Edited February 10 by Mikkel Lindgren (1003540) Best regards Mikkel Lindgren Link to comment Share on other sites More sharing options...
Lukas Agerskov (1226374) Posted February 10 Author Report Share Posted February 10 (edited) Briefing Pack, Cross the Land Westbound Staffing CTL 2023.pdf Saturday, Feb 11th, 15.30-21.00z Expected runway configuration: 22R for departure and 22L for arrival General We will run with split apron for the first time. Please provide feedback on how it works First inbound at 15:46 landing 16:07. Last arrival is already around 19z, but the expectation is that traffiic will continue relatively actively. Logging off before time is completely fine if traffic levels are not for the configuration All positions have been booked already. EKDK_B_CTR 3 out the 5 routes comes in via MONAK, meaning quite heavy traffic from there. IF you get overloaded, ask EKDK_V_CTR to go on EKDK_D_CTR instead and hence handle TUDLO/TESPI inbounds. Or alternatively ask EKDK_V to keep those arrivals All CTL inbounds comes to EKCH_E_APP so be ready to redirect some arrivals to TUDLO if needed. Use holdings effectively to ensure minimum 15nm on average separation into the TMA EKDK_V_CTR Transits to ENBR for CTL will go thru your airspace as well Be ready to help EKDK_B_CTR in case of heavy traffic over MONAK. Take initiative. EKCH_E_APP All CTL inbounds comes to you. 3 routes from MONAK, 2 from TIDVU. it will be IMPOSSIBLE to get them all in, so don't even try. If/when the TMA gets overloaded, be ready to reroute MONAK arrivals with a heading 360 and over EKCH_W_APP. Keep at FL80 crossing the centreline due to departures Maintain average minimum of 10nm on handover to final, or otherwise final WILL get overloaded Flights will come in via TIDVU and MONAK with 15nm separation on average EKCH_W_APP All CTL inbounds comes to EKCH_E_APP. 3 routes from MONAK, 2 from TIDVU. Be ready to help out. You will have the least traffic load If/when the TMA gets overloaded, be ready to accept MONAK arrivals with a heading 360 at FL80. Maintain average minimum of 10nm on handover to final, or otherwise final WILL get overloaded EKCH_A_TWR Due to split apron, take following procautions and STICK to them please. STICK to the standardd Taxi Routes. Everything above A17 and A4,6,8 needs to go via K3,K2. If they vacate B5, you MUST turn them at Runway 30 If you change the assigned stand do it WELL BEFORE runway 30, as apron will look for them to plan their coordination DO NOT change the stand, just because you wanna have an easier taxi route to give the pilot. It will ruin everything for the apron controllers EKCH_D_GND You Control Delivery. Coordinate with EKCH_A_GND! See the guidance on managing coordination. You are free to make your own arrangement if it suits you better. The GM is only a proposition EKCH_A_GND Coordinate with EKCH_D_GND! See the guidance on managing coordination. You are free to make your own arrangement if it suits you better. The GM is only a proposition General between EKCH_A_GND & EKCH_D_GND This below is a guidance to how to act without coordinating all the time. Agree on either these terms or other terms as desired. If in doubt, TALK! If there are several airplanes in lines at a hotspot then do 1+1. thee first controller gets one past, then the second, then the first. No one crosses two in a row without coordination. Three HOTSPOTS should be shown with extra considaration PUSHBACKS: EKCH_D_GND: Always make sure no arrivals is on the "Apron AOR" on their way to a stand your pushback would block for. Strongly recommend using vStrips, making it A LOT easier for EKCH_A_GND to spot which airplanes have pushbacks, and which have been told to wait (START ONLY) HS1 D_GND make sure noone is on their way in when giving pushback A_GND should hold short Z at K3 and wait for the departure to taxi out HS2 D_GND make sure noone is on their way in when giving pushback D_GND should taxi via P/Q to hold short Y and wait for any crossing arrivals. If arrivals are going into the same alley then continue the taxi to clear it Alternate the sequence of A_GND airplanes and D_GND airplanes HS3 D_GND make sure noone is on their way in when giving pushback A_GND should taxi inbound via B and R to C27-39 as well as D1-D4. If E20-E36 is used taxi via B, R, W and S and yield to any departures on W. D_GND should taxi outbounds from D1-D4 always via S hold short V. Then when clear of crossings then via V, Y and F to hold short 30 D_GND should only push to R1 facing north from D1-D4 D_GND should be careful with pushbacks from C27-C39. Consider non-standard facing north and taxi them around onto S if you loose oversight. A_GND consider taxi planes to F1-H106 via V and T This would be the suggestion Edited February 10 by Lukas Agerskov (1226374) Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now