Hello all
We have now, for some time, been studying Vectors to Copenhagen very thoroughly, identifying key threats, looking at what goes well, when event goes well, what goes wrong when even goes wrong, and so on and so forth.
I think the time is mature for us to come together, and discuss some of these factors, to all have our say in how to shape the future of this event, which has gone on to become one of the most popular events on VATSIM.
I invite everybody, regardless of rating (No OBS please) to come with input on their experiences, their thoughts and their aspirations. No comment is stupid, and we want as much data as possible.
Here are a few topics I would like to open to the floor.
Controller level
This has no intention of putting out any individual controller. The facts are clear though. The experience and skill of the person occupying especially the FINAL sector is more often than not dictating the success of the event. If FINAL becomes a mess, APP becomes a mess, CTR becomes a mess. We therefore need to evaluate if we need requirement to certain positions, especially FINAL. Talks have been of three possible scenarios
Event Rating
First idea is an event rating, which all students must go through after passing their S3 checkout. It requires observing for VTC, theoretical training and a practical training session during Mondays. This would require extra TD recourses, but would then be required before being allowed to sit on FINAL and potentially other positions in the TMA on VTC.
VTC Recency
An idea where in order to be allowed to sit on especially FINAL you must be VTC recent. This would be for example a requirement to have had a minimum of two slings of APP within the previous month before being allowed to occupy FINAL on either early or late shift.
Given that issues are mainly arising when controllers who are not normally controlling during VTC takes FINAL, there may be some reasoning in a requirement to be current within the event before occupying FINAL. This could be done in conjunction with a full or abbreviated event rating, or just as a stand along.
No limitations
A third idea is to have no limitations, and fix whatever issues are arising by use of more holdings. This is not to be discarded as a messy final can be given time to be fixed by use of holdings, which would increase availability of controllers each Monday, but at the expense of ACC controllers.
Time of Closure
This is another topic which has brought some controversy due to differing opinions, all valid. When do we close? Do we wait until last man, do we have a time, what do we do? Here are a few options, but feel free to mix and match, or come up with a complete fourth idea.
Zurich model
What they do in Zurich is they have a specific time where EVERYBODY logs off. Whatever chaos is left is left. Now while this hardly is something we should go for in EKCH, there are some interesting sides to in, because it will affect how late pilots tend to fly in. While it would show a drop in traffic numbers, it could also lead to being earlier finished, simply by letting pilots know that we are not staying up until midnight.
Last man standing
This is kind of the unofficial model already. Some positions have a freedom to close at certain times, but everybody generally stays until last man is down, in good weeks at 22.30 in bad weeks 23.45. This model provides very happy pilots, but unhappy controllers, and is in its current form, in my opinion unsustainable.
Last flight identified
A model where a controller (EKDK_B) for example, identifies an airplane scheduled to arrive at 2215, and notes the flight with LAST FLIGHT. After that flight has landed, everybody is either free to log off, or everybody is forced to log off, depending on which model we want to adopt. Either way, holdings should be somewhat empty before we can start closing on ACC, but this model would work for APP and FINAL.
Event times
Do we stick with a weekly event, or is the only solution making it bi-weekly? Norway and Sweden are doing this already
Weekly VTC
Stick with the current setup, which works, but requires work from the entire community in getting signed up. I would love to hear your opinion about how often you sign up, and why staying away. Is it fear of chaos, or is it tiredness of potentially a long night? What would make it different?
Bi-weekly
A model where every second week is EKCH every second week is regional. This is what Sweden and Norway are doing, but it is worth noting that it may work for them, specifically because they have EKCH every Monday to attract traffic to them. Additionally we would need to staff EKCH up as well for any bi-weekly event to regionals, because about 40-50% of traffic still comes to EKCH regardless of the event being posted on VATSIM or not.
Statistical based controlling
Most of you will have noticed that we have moved more and more to a statistical approach in how we are controlling. It may feel a bit much for some, so I would like to open the discussion to opinions. Do we need more, do we need less, do we need to ease complexity, or do we need even more complexity?
While the model is not perfect, the results the last 6 months, especially between ACC and APP has been amazing. Everything is coming in a much more orderly fashion, and flow breakdown are often more due to FINAL, GAs or understaffing than actual uncontrolled chaos.
That’s all. Short stories, long stories, brutally honest opinions in regards to these topics and ideas are most welcome
- Controller limitations
- Event time policy
- Statistical controller procedures
Feel free to come with your own interpretation of ideas as well, that can be open for a larger discussion, so everybody has a chance to set their mark on VTC in the future.
