WorldFlight in the USA

It's that time of the year again!  Prepare yourself for one the larger events on the VATSIM calendar and you are invited to join in the fun!

WorldFlight 2016

This year, WorldFlight will be celebrating its 16th year of operations.  WorldFlight will start in Sydney (YSSY) on 06 November and will finish 6 days later on 12 November.

WorldFlight is a virtual round the world flight that raises money for selected charities around the world. There will be a number of fixed based simulators participating in the event. Full ATC coverage from both local and international controllers will be provided throughout the event as it makes its way around the world.

Join the WorldFlight this year by participating in the event as it makes its way through your region, by flying one of the 45 designated flights or by controlling. Pilots are welcome to start your journey anywhere along the event, expect congested airspace and challenging approaches into a number of locations around the world.

As always, we are looking for all ARTCCs that will be seeing WF arrivals, departures and/or overflights to staff up appropriately for an event of this size, even -- as best you can -- even during the school/work day and in the middle of the night.  Overflight Centers should plan on 1-2 CTR controllers.  Arrival/Departure  airports should plan on needing 1-2 CTR, 2-3 APP, 1 DEP, and a full cab, including TWR, GND and DEL!

For more information, including route details, flight plans, suggested scenery links and updates throughout the event, please visit: www.worldflight.com.au go to the OPERATIONS|DOWNLOADS to get the files.


VATUSA Schedule Highlights (Note:  All dates/times are in Zulu time)

Flight From To Sched Departure Sched Arrival
WF1604 Apia Kailua Kona 11/06/2016 10:50 11/06/2016 16:20
WF1605 Kailua Kona Seattle 11/06/2016 17:10 11/06/2016 22:55
WF1606 Seattle Juneau 11/06/2016 23:45 11/07/2016 02:05
WF1607 Juneau Cold Lake 11/07/2016 02:55 11/07/2016 05:35
WF1608 Cold Lake Duluth 11/07/2016 07:05 11/07/2016 09:30
WF1609 Duluth Toronto Pearson 11/07/2016 10:20 11/07/2016 13:35
WF1610 Toronto Pearson New York La Guardia 11/07/2016 14:25 11/07/2016 15:50
WF1611 New York La Guardia Charleston 11/07/2016 16:40 11/07/2016 19:30
WF1612 Charleston Sarasota 11/07/2016 20:20 11/07/2016 22:00
WF1613 Sarasota Miami 11/07/2016 22:50 11/07/2016 23:45
WF1614 Miami Santo Domingo 11/08/2016 00:35 11/08/2016 02:45
Full schedule here:  http://www.worldflight.com.au/operations/schedule

________________________________________________________

Controlling WorldFlight, and cooperating with WorldFlight Controllers
Reminder that WorldFlight controllers are authorized to control any USA airspace where VATUSA controllers are not present, or not present in sufficient volume to ensure an efficient, effective turnaround/event.  Most will defer if a VATUSA controller comes online, but are not required to.  WF controllers can and will also come on and assist in cases where the home facility does not bring enough controllers to make it an effective, efficient process for the WF flights.  Best bet for good relations is if a WF controller is online and you'd like to staff, come on as an OBS, identify yourself as a home ARTCC controller, and offer to either relieve the WF controller if they wish, or ask where you can be most useful.  Or if you're controlling and a WF controller offers to help, take them up on the help -- they are probably asking politely because they already see an efficiency/effectiveness problem, or see one coming!  The idea here is to stay friendly, keep up good relations, and make it a great experience for everyone.  Whatever you do, DO NOT argue with a WF controller.  Yes, they put their pants on just like the rest of us, but are highly trained and experienced to provide a good ATC service for WF across the globe, and may just see something brewing that you do not.

All affected ARTCCs should treat this as an event, and should solicit and staff appropriately.  If unable to staff per the guidelines above, seek ACE team help.  If there still isn't enough staffing, do the best you can to staff the best you can, but let your controllers know that WF controllers are there to help and they should be accepted into the event with all the warmth/friendliness/cooperation that another home controller would receive.

Everyone should note/remember that WF is a significant VATSIM event, and is a great workout for our affected ARTCCs.  Each leg generally has 40-80 aircraft all shooting for the same arrival and departure times, so the best strategy is to staff up for a 2-4 hour event ensuring at a minimum CTR, TRACON, TWR and GND (and DEL if possible) are staffed as outlined above.  Like CTP, PDCs should be in use at fields/facilities where PDCs are normally used (and I don't mind you using them just for the event at fields where they are normally not used) -- it makes a HUGE difference in terms of efficiency!  I don’t think most ARTCCs have always understood the level of traffic, commitment and staffing needed to run a good, if not flawless, WF event.  And some of it is during the school/workday, some of it is in the middle of the night, so it’s really important that the ARTCCs, if they do it right (which I want them to), take it seriously, advertise, guarantee staffing, get help when needed, etc.  It’s truly a wonderful opportunity, particularly for facilities that don't normally see as much large volume, global traffic like we see during the other major VATSIM global event, Cross The Pond.  And this is even better/crazier, as we're slamming a huge number of arrivals AND departures into the same airport!

Please remember that, in addition to the fun of flying and controlling with WorldFlight, these are great charities to donate to.  For more information on the USA WorldFlight team and the USA team's chosen charity, All Children's Hospital, go to http://www.worldflightusa.com

WorldFlight in the USA is getting closer and closer!  Is everyone fully staffed?  Ready to go?  If you're short a controller or two, have you reached out to your visitors, adjacent ARTCCs, Ace Team, etc. for help?  Let's do this!

A note/reminder from the Worldflight team (cross-posted):

We are looking forward to a bumper number of participants this year. The interest has been phenomenal. The list of controllers who have applied to support the event throughout the week has grown exponentially. In particular we expect the last few legs in Australia to be close to unmanageable which leads me to remind everyone about the spirit of WorldFlight.

WorldFlight is unique in many ways but probably the one thing that stands out is the way controllers and pilots come together to handle the very unrealistic objective of getting a large volume of traffic in and out of an airfield more or less at the same time. Then we do it again and again some 40+ times. It is entirely intentional that there are no flight booking slots and the vast majority of feedback that we receive each year from VATSIM divisions around the globe centers around the enjoyment they get from "blurring" their usual airspace procedures to accommodate what has affectionately become known as  "The WorldFlight Swarm".

Have some fun during this one folks, the official sim teams certainly do, and remember...."it is not always realistic to be realistic during WorldFlight". Reported virtual fatalities over the years from operating with "reduced separation" have been at acceptable levels

On behalf of the entire WorldFlight Team, we look forward to seeing you for all or part of WorldFlight 2016 for a week of fun raising important funds for some very worthy charitable causes around the world.

Cheers,
Tracy
WorldFlight Australia

All arrival/departure facilities:

In the spirit of moving tin as quickly and efficiently with as little burden on your folks as you possibly can, you may want to use a lessons learned from CTP and set up CPDLC/PDC use for this event, even if the airport does not use CPDLC/PDC in the RW.  When you have 40-80 aircraft calling for clearance essentially at the same time, it makes a huge difference to have the average clearance given in 6-10 seconds, vs. 1-2 minutes. 

For those that have not used CPDLC/PDC aliases in the past, I offer this as a suggestion:

==========

//PDCs
.pdc .p1 .p2
.pdcu .p1 .p2u
.route

.p1 .msg $aircraft - CLEARANCE START - | CALL SIGN: $aircraft | TRANSPONDER CODE: $squawk | ALTITUDE: $cruise | DEPT: $dep | ARR: $arr | EQUIPMENT: $type($aircraft) | APPROVED ROUTE: $route | ALTITUDE RESTRICTIONS: CLIMB VIA SID. -

.p2 ADDITIONAL INFORMATION: DEPARTURE FREQUENCY $freq($1) | THIS MESSAGE SERVES AS YOUR DEPARTURE CLEARANCE. YOU DO NOT NEED TO REPLY TO THIS MESSAGE. CONTACT $uc($radioname()) ON $com1 WITH LOCATION ON THE AIRPORT, ASSIGNED SID, AND CURRENT ATIS WHEN READY TO PUSH OR IF YOU HAVE QUESTIONS REGARDING THIS CLEARANCE. - CLEARANCE END -

.p2u ADDITIONAL INFORMATION: DEPARTURE CURRENTLY OFFLINE, EXPECT TO MONITOR UNICOM 122.800. | THIS MESSAGE SERVES AS YOUR DEPARTURE CLEARANCE. YOU DO NOT NEED TO REPLY TO THIS MESSAGE. CONTACT $uc($radioname()) ON $com1 WITH LOCATION ON THE AIRPORT, ASSIGNED SID, AND CURRENT ATIS WHEN READY TO PUSH OR IF YOU HAVE QUESTIONS REGARDING THIS CLEARANCE. - CLEARANCE END -

.pdcv .msg $aircraft - CLEARANCE START | CALLSIGN: $aircraft | TRANSPONDER CODE: $squawk | ALTITUDE: $cruise | DEPT: $dep | ARR: $arr | EQUIPMENT: $type($aircraft) | APPROVED ROUTE: RADAR VECTORS $uc($1) THEN AS FILED | ALTITUDE RESTRICTIONS: MAINTAIN $2. EXPECT $cruise 10 MINUTES AFTER DEPARTURE | DEPARTURE FREQUENCY $freq($3) | THIS MESSAGE SERVES AS YOUR DEPARTURE CLEARANCE. YOU DO NOT NEED TO REPLY TO THIS MESSAGE. CONTACT $uc($radioname()) ON $com1 WITH LOCATION ON THE AIRPORT AND CURRENT ATIS WHEN READY TO PUSH OR IF YOU HAVE QUESTIONS REGARDING THIS CLEARANCE. - CLEARANCE END -

.pdcx .msg $aircraft - CLEARANCE START- | CALL SIGN: $aircraft | TRANSPONDER CODE: $squawk | ALTITUDE: $cruise | DEPT: $dep | ARR: $arr | EQUIPMENT: $type($aircraft) | APPROVED ROUTE: $route | ALTITUDE RESTRICTIONS: CLIMB VIA SID EXCEPT MAINTAIN $1 | DEPARTURE FREQUENCY $freq($2) | THIS MESSAGE SERVES AS YOUR DEPARTURE CLEARANCE. YOU DO NOT NEED TO REPLY TO THIS MESSAGE. CONTACT $uc($radioname()) ON $com1 WITH LOCATION ON THE AIRPORT AND CURRENT ATIS WHEN READY TO PUSH OR IF YOU HAVE QUESTIONS REGARDING THIS CLEARANCE. - CLEARANCE END -

.nopdc .msg $aircraft PRE-DEPARTURE CLEARANCE UNAVAILABLE. CONTACT $freq($1) FOR CLEARANCE.

.route .msg $aircraft ATC HAS ISSUED AN AMENDMENT TO YOUR ROUTE OF FLIGHT TO BETTER FACILITATE AIR TRAFFIC MOVEMENTS. IF YOU ARE ABLE TO ACCEPT THE AMENDMENT, PLEASE REPLY TO THIS MESSAGE AND EXPECT TO RECEIVE CLEARANCE VIA CPDLC. IF YOU ARE NOT ABLE TO ACCEPT THE AMENDMENT, HAVE ANY QUESTIONS, OR WOULD PREFER A DIFFERENT ROUTE, PLEASE CONTACT $uc($radioname()) ON $com1. THE PROPOSED AMENDED ROUTE FOR YOUR FLIGHT IS: $uc($1) $uc($2) $uc($3) $uc($4) $uc($5) $uc($6) $uc($7) $uc($8) $uc($9)

==========

Note that for WF, I would *NOT* expect anyone to use .route but am just including it in case facilities can use it.....

I offer this as a suggestion:

You're welcome  Also, FYI, you don't need the "$uc($1) $uc($2) etc." at the end of the .route alias. Considering it's what comes last, it'll simply appear after the alias text.

Just like if I typed ".tl 150 Hi!!!"
It would result in: "Turn left heading 150 Hi!!!"

With .route, if I type ".route SSOXS4 SSOXS BUZRD SEY PARCH1"
It would result in: ". . . THE PROPOSED AMENDED ROUTE FOR YOUR FLIGHT IS: SSOXS4 SSOXS BUZRD SEY PARCH1" (Even without the $uc($1) variables).

True, they would just appear lower case for lazy SOBs like me that might type in the route lower case....

Quote from: Don Desfosse on November 03, 2016, 04:08:23 AM

I offer this as a suggestion:

You're welcome 

Wow, what an expertly-written set of aliases for PDC/CPDLC. I really like that ".route" alias. I wonder where you got it from...must have been a facility with a great FE.

Must have   Thank you, ZBW, for helping to raise the overall VATUSA water level and better prepare for WF!

My sincere thanks to everyone who participated in WF this year.  I really appreciate all of your efforts.  Your efforts helped the WF team raise $75,130 in support of the various charities that are supported by the organization!  Great job!

My sincere thanks to everyone who participated in WF this year.  I really appreciate all of your efforts.  Your efforts helped the WF team raise $75,130 in support of the various charities that are supported by the organization!  Great job!

As a follow up to what Don has already reported, let me take it a step further and tell you that the $75,130 is what was donated in US Dollars.  The actual total raised was significantly higher, and breaks down as follows:

AUD = 102,370
EUR =   70,860
USD =   75,130
GBP =   60,800

If anyone is interested in doing the math feel free. Suffice it to say that none of this happens without all of you, regardless of where you control, fly, or reside.

Ah, I interpreted that as that was the amount donated, shown in various currencies.  If you're correct, then that's truly phenomenal (and coincidental that each currency got roughly $75,130...)

It would be interesting to know what charities

Don't worry, the money isn't being donated to "Bob's Vacation Fund"  LOL

I believe most of the money goes to the Australian Royal Flying Doctor Service, but don't quote me.

Each of the WF teams' websites have information on which charities they are supporting.  You can find the links to the teams here: http://www.worldflight.com.au

I would be interested in hearing how they raised $75k this year.  According to the web site the goal was to raise 5k, which would be almost twice what was raised last year.  So how do you go from 3k to 75k ?   Now I'm not saying it isn't possible.  But it does make you curious.

Anyway, the charity of choice was a children's hospital in Florida.  I don't think anyone should have a problem with that.