Collective Purpose
The Planning Team is the collective group of decision makers who have final authority and responsibility for the execution of Cross the Pond events. The Planning Team is supported by the Event Team.
Coordinators - Kieran Hardern, Erik Quinn
The Coordinator of the Planning Team oversees the totality of the event planners, and strives to support the relevant planners with whatever they may need to fulfill their duties. This involves collection, organization, and dissemination of necessary planning and logistical tasks, as well as oversight in terms of quality control and ensuring on-time completion of time-critical tasks. To be used only when truly necessary, the Coordinator possesses the authority to overrule members of the Planning Team in decisions which may be subsequently reversed by a Planning Team majority vote. Adds and removes people from the Planning Team with input from the rest of the Planning Team.
Communications Lead - Nick Marinov
The Communications Lead is the primary handler of all relevant Discord, forum, and social media communications, as well as coordinating and disseminating necessary information with the various parties participating in the event.
EMEA Routes Lead - Raul Ferraz
The EMEA Routes Lead coordinates with all participating ATC facilities within the Europe, Middle East, and Africa Region of VATSIM, to develop a route structure representing the highest possible level of accommodation to all participants collectively. This occasionally means declining routing requests of some participants when an operational need necessitates a different approach. The EMEA Routes Lead coordinates with the EMEA Routes Team (a part of the Event Team) to spread out the work as needed to achieve the optimal degree of responsiveness to participants and quality of the final route plan. Coordinates with the AMAS Routes Lead as needed, and operates in strict compliance with timelines set by the Planning Team Coordinator. They also acknowledge the notion that the arrival side shall be given moderately higher priority in their desires for the overall route structure, though only for requests made within the established timelines.
AMAS Routes Lead - Cameron Peterson
The AMAS Routes Lead coordinates with all participating ATC facilities within the United States, Canada, Caribbean, and Central and South America, to develop a route structure representing the highest possible level of accommodation to all participants collectively. This occasionally means declining routing requests of some participants when an operational need necessitates a different approach. The AMAS Routes Lead coordinates with the AMAS Routes Team (a part of the Event Team) to spread out the work as needed to achieve the optimal degree of responsiveness to participants and quality of the final route plan. Coordinates with the EMEA Routes Lead as needed, and operates in strict compliance with timelines set by the Planning Team Coordinator. They also acknowledge the notion that the arrival side shall be given moderately higher priority in their desires for the overall route structure, though only for requests made within the established timelines.
Data & Logistics Lead - Sebastian Gruenewald
The Data & Logistics Lead's primary responsibility is to establish terminal and en route ATC service capacities, and establish appropriate traffic throughput constraints. This includes assessment of the capacity of all potential event airports and enroute sectors, in order to ensure participating ATC facilities experience an appropriate and enjoyable workload during the event. As part of this process, the Data & Logistics Lead conducts analysis on and provides recommendations for slot allocations (in total, and per airport), appropriate city pairs (with specific facility progressions). They also gather pilots’ slot misuse data, manage the slot lottery system, build the full set of bookable slots, and distribute that data to the appropriate parties. The Data & Logistics Lead should remain in close collaboration with the Coordinator and both Routes Leads, and should continuously monitor all planning to ensure the overall event plan (of routes and otherwise) conform to the established throughput constraints.
Oceanic Lead - Joshua Micallef
The Oceanic Lead is the primary handler of oceanic logistics, including controller recruitment, scheduling, sectorization and corresponding AFV configuration, generation of relevant controller reference materials, as well as configuration and dissemination of EuroScope packages used by Shanwick and Gander FIRs. In some cases, some of this work is handled by the OCAs themselves, and the Oceanic Lead need only ensure the work is done, and verify the configurations are indeed correct.
Technology Lead - William McKinnerney
The Technology Lead coordinates with the VATSIM HQ’s Tech Team as needed for website and NatTrak development, deployment, maintenance, resource scaling, and contingency planning to ensure reliable uptime for all services CTP relies on during event day.