ZMP and ZKC ARTCCs Present... The Great Plains Tetralogy!

Join us on Saturday, March 4th from 5pm to 10pm CT as we staff up Lincoln, Omaha, Kansas City and St Louis for a four-way crossfire event. Whether you prefer to fly heavy metal or light GA, this event has an airfield for every preference. Five hours of solid staffing in the Heart of the Great Plains allows you time to experience all!

ZMP's Annual Last Minute Shopping event featuring MSP and FCM. 2359z-0400z

ZMP knows you waited until the last minute. Don't worry, we won't tell!

Lucky for you, the world famous Mall of America is right across the street from Minneapolis/St. Paul International Airport!

ZMP will be providing full ATC service to KMSP as well as to Flying Cloud Airport (KFCM) in Eden Prairie, MN, home of the Eden Prairie shopping center.

More than enough time for you to fly in, hit the malls, and fly out...before anyone else knows how long you waited!

Honestly, wouldn't this have made more sense to give out four copies to four different people (why would one person need two keys? Plus, from a marketing standpoint, it would have been better to target more pilots)? Secondly, it would have been really easy to log into the VATSIM statistics database, filter the event times when people were flying into MEM (didn't think flying out counted based on how this initially read, hence the reason a number of us flew in rather than out), and then randomly select 4 people from that list. This would have made far more sense and should have happened after the event was over and then results posted on the forum so people weren't left in the dark.

Just some food for thought... for future reference.

Initial article written for/posted at ZMP, but have received requests to have it more publicly available for interested parties.



Since we're reaching the time of year where severe weather can significantly impact ZMP, I figured now would be a good time to include information on the dissemination of weather information to aircraft on frequency.


What Information Needs to be Provided?
How do we know what types of weather information need to be disseminated to pilots? Chapter 2, Section 6 of the 7110 explains this:

Controllers must advise pilots of hazardous weather that may impact operations within 150 NM of their sector or area of jurisdiction. Hazardous weather information contained in HIWAS broadcasts includes Airmen's Meteorological Information (AIRMET), Significant Meteorological Information (SIGMET), Convective SIGMET (WST), Urgent Pilot Weather Reports (UUA), and Center Weather Advisories (CWA). Facilities must review alert messages to determine the geographical area and operational impact for hazardous weather information broadcasts. The broadcast is not required if aircraft on your frequency(s) will not be affected.

Another note to keep in mind for those of you providing terminal approach control services or ATCT services:

c. Terminal facilities have the option to limit hazardous weather information broadcasts as follows: Tower cab and approach control facilities may opt to broadcast hazardous weather information alerts only when any part of the area described is within 50 NM of the airspace under their jurisdiction.

What is this Information?
Now that we know the types of weather information we need to be on the look-out for as controllers, What exactly does this information mean?

- AIRMETs (AIRman's METeorological Information) include information about widespread (3000 square miles or larger areas) weather phenomenon associated with IFR conditions, turbulence, and icing conditions that primarily may affect VFR aircraft and sometimes larger operators. They are broken down into three sub-categories listed below:
   
         • AIRMET Sierra (IFR):
              Ceilings less than 1000 feet and/or visibility less than 3 miles affecting over 50% of the area at one time.
              Extensive mountain obscuration

         • AIRMET Tango (Turbulence):
              Moderate turbulence
              Sustained surface winds of 30 knots or more at the surface

         • AIRMET Zulu (Icing):
              Moderate icing
              Freezing levels

- SIGMETs (SIGnificant METeorological information) advise of weather potentially hazadous to all aircraft other than convective activity. In the conterminous U.S., items covered are:

         • Severe icing severe icing below 8,000 feet • Severe or extreme turbulence severe turbulence between FL100 and FL240
         • Duststorms lowering visibilities to less than three (3) sm
         • Volcanic Ash

- WST - Convective SIGMETs (SIGnificant METeorological information) are issued in the conterminous U.S. for any of the following:

         • Severe thunderstorm due to:
            Surface winds greater than or equal to 50 knots
            Hail at the surface greater than or equal to 3/4 inches in diameter
            Tornadoes

         • Embedded thunderstorms
            Line of thunderstorms
            Thunderstorms greater than or equal to VIP level 4 affecting 40% or more of an area at least 3000 square miles

- UUA - Urgent PIREPs (Urgent PIlot weather REPorts) include information reported directly from the pilot concerning turbulence and icing information.

- CWAs (Center Weather Advisories) are an aviation weather warning for thunderstorms, icing, turbulence, and low cloud ceilings and visibilities.


So now that we know the types of weather information we need to be on the look out for as controllers, where do we find this information?


AIRMETs/SIGMETs
AIRMET and SIGMET information can be found from sources such as ADDS (Aviation Digital Data Services) found at this link http://aviationweather.gov/adds/airmets/. On this page, you'll note a section labeled "Text AIRMETs/SIGMETs: Check at least one in each column:" followed by a series of check-boxes beneath that allow you to specify the types of weather information you are seeking and specific areas/area for that information with a map below that indicating which states fall within the given areas. See the below image for a visual:

[img]http://dl.dropbox.com/u/16162462/HWI/1.jpg\\\" border=\\\"0\\\" class=\\\"linked-image\\\" /]

You'll note that the ZMP falls within the Chicago area according to the map, so we'll want to specify that area when seeking hazardous weather information. Although AIRMETs (IFR, turbulence, icing information, primarily) are certainly important to pay attention to, they are generally not read as often on frequency as SIGMET/Convective SIGMET information/UUAs/CWAs. To pull up the SIGMET/CONVECTIVE SIGMET information, you'll want to check the following boxes for our area and then click the "Retrieve" button. See the below image for a visual:

[img]http://dl.dropbox.com/u/16162462/HWI/2.jpg\\\" border=\\\"0\\\" class=\\\"linked-image\\\" /]

Now a textual list of all current SIGMET information will display in a new window. See the below image for a visual:

[img]http://dl.dropbox.com/u/16162462/HWI/3.jpg\\\" border=\\\"0\\\" class=\\\"linked-image\\\" /]

Now that we have the textual list, we need to understand how to decode the information and read it on frequency to inform the pilots.

Convective SIGMETs are issues for the Western (W), Eastern (E) and Central © parts of the United States.  Each SIGMET report will begin with the place of issuance followed by the date and ZULU time in the very first line. They are generally issued at 55 minutes past each hour but can be issued at any time in between. The second line will show SIGW, SIGC or SIGE depending on the region it is for. The third line will read "CONVECTIVE SIGMET XXW/C/E" with the "XX" being a number (1 through 99) and the W/C/E following to indicate the affected region of the United States. The fourth line will indicate the time the SIGMET is valid till (2 hours from the time of issuance). The fifth line will indicate the affected States/areas. The sixth line will indicate the VORs, DME distances and directions for the affected geographic area (which makes it relatively easier for pilots/controllers to plot). The last line (which sometimes may be the seventh or eighth depending on the size of the previous section) then indicates the type of thunderstorms, size of the system, direction/speed of movement and cloud tops of the storms. Following the initial SIGMET report will be OUTLOOK information in which we should probably expect to see further SIGMETs issued for those specific geographic areas.

Something to keep in mind - I've noticed that the list will occasionally display SIGMET information for areas outside of the region we initially selected (you'll note this from the very first SIGMET in this list as it is an Eastern SIGMET for North Carolina, South Carolina and Coastal Waters). You'll have to browse down through the list to find the specific SIGMETs that concern the ZMP area (keeping in mind that it should be within 150nm of our sector). Pay attention to the affected States/water bodies as some of them will be for the South-Central U.S. outside of our coverage area.

[img]http://dl.dropbox.com/u/16162462/HWI/4.jpg\\\" border=\\\"0\\\" class=\\\"linked-image\\\" /]

Now that we understand how to decode the SIGMETs, we need to know how to read these on frequency. Below is the phraseology from the 7110 for reading the SIGMETs on frequency:

a. Controllers within commissioned HIWAS areas must broadcast a HIWAS alert on all frequencies, except emergency frequency, upon receipt of hazardous weather information. Controllers are required to disseminate data based on the operational impact on the sector or area of control jurisdiction.

NOTE-
The inclusion of the type and number of weather advisory responsible for the HIWAS advisory is optional.

PHRASEOLOGY-
ATTENTION ALL AIRCRAFT. HAZARDOUS WEATHER INFORMATION (SIGMET, Convective SIGMET, AIRMET, Urgent Pilot Weather Report (UUA), or Center Weather Advisory (CWA), Number or Numbers) FOR (geographical area) AVAILABLE ON HIWAS, FLIGHT WATCH, OR FLIGHT SERVICE FREQUENCIES.

So we'll take the example from our above textual list which indicates a SIGMET is out affecting the state of Iowa. Using the above phraseology, we would read that SIGMET on frequency as follows:

"Attention all aircraft, hazardous weather information, CONVECTIVE SIGMET Three-One Central out valid until two-one-five-five zulu for Iowa available on HIWAS, Flight Watch, or Flight Service Frequencies."

Since we are on VATSIM and those frequencies (HIWAS, Flight Watch, Flight Service Frequencies) are not readily available for use by most pilots not using some sort of addon weather programs, we are adding to the "realistic experience" we can provide to pilots on the network by stating this. To assist with this issue, I also like to add and additional phrase after the HIWAS, FlightWatch, Flight Service Frequencies line that would read on frequency as follows:

"Attention all aircraft, hazardous weather information, CONVECTIVE SIGMET Three-One Central is out valid until two-one-five-five zulu for Iowa available on HIWAS, Flight Watch, Flight Service Frequencies, or from air traffic control upon pilot request" which then indicates to the pilot that they can obtain a detailed reading of the SIGMET from us on frequency upon request. In this case, you would simply read the SIGMET in full detail (keeping in mind that you should work your traffic first and provide this information as second priority to that).

A full reading of the example report we are using would read as follows:

"CONVECTIVE SIGMET Three-One Central, out valid until two-one-five-five zulu, affecting Iowa, From 5-0 North-Northeast of Des Moines to 2-0 North-Northwest of Iowa City to 1-0 West-Northwest of Iowa City to 1-0 Southeast of Des Moines to 5-0 North-Northeast of Des Moines, an area of embedded thunderstorms moving from 2-3-0 at 3-0 knots. Tops to Flight Level 3-5-0."

There are, of course, other shortened words that you may see in the reports that need to be decoded but most are relatively simple to unlock using common sense as most of the vowels are simply removed to shorten the length of the report.

Keep in mind that there may be multiple SIGMETs out for our area, especially with the sheer size of ZMP's coverage area. You can read those off using the following phraseology:

"Attention all aircraft, hazardous weather information, CONVECTIVE SIGMETs Three-One Central, three-two central, and three-three central out valid until two-one-five-five zulu for Iowa, Nebraska, Kansas, North Dakota, South Dakota and Minnesota, available on HIWAS, Flight Watch, Flight Service Frequencies, or from Air Traffic Control upon pilot request."


UUAs
Urgent PIREPs can be obtained from multiple online sources, but have no real applicability on VATSIM unless actually reported by a pilot flying on the network. Our IDS system will help you to keep track of that information and deliver this information to other pilots on frequency when/where applicable.

Some important information and phraseology from the 7110 should be noted for PIREPs:

Significant PIREP information includes reports of strong frontal activity, squall lines, thunderstorms, light to severe icing, wind shear and turbulence (including clear air turbulence) of moderate or greater intensity, volcanic eruptions and volcanic ash clouds, and other conditions pertinent to flight safety.

REFERENCE-
FAAO JO 7110.65, Para 3-1-8, Low Level Wind Shear/Microburst Advisories.
FAAO JO 7210.3, Para 6-3-1, Handling of SIGMETs, CWAs, and PIREPs.
AIM, Para 7-5-9, Flight Operations in Volcanic Ash.
FAAO JO 7210.3, Para 10-3-1, SIGMET and PIREP Handling.

a. Solicit PIREPs when requested or when one of the following conditions exists or is forecast for your area of jurisdiction:

1. Ceilings at or below 5,000 feet. These PIREPs must include cloud base/top reports when feasible.

TERMINAL. Ensure that at least one descent/climb-out PIREP, including cloud base/s, top/s, and other related phenomena, is obtained each hour.

EN ROUTE. When providing approach control services, the requirements stated in TERMINAL above apply.

2. Visibility (surface or aloft) at or less than 5 miles.

3. Thunderstorms and related phenomena.

4. Turbulence of moderate degree or greater.

5. Icing of light degree or greater.

6. Wind shear.

7. Volcanic ash clouds.

NOTE-
Pilots may forward PIREPs regarding volcanic activity using the format described in the Volcanic Activity Reporting Form (VAR) as depicted in the AIM, Appendix 2.

8. TERMINAL. Braking Action Advisories are in effect.

REFERENCE-
FAAO JO 7110.65, Para 3-3-5, Braking Action Advisories.
P/CG Term- Braking Action Advisories.

b. Record with the PIREPs:

1. Time.

2. Aircraft position.

3. Type aircraft.

4. Altitude.

5. When the PIREP involves icing include:

(a) Icing type and intensity.

( b ) Air temperature in which icing is occurring.

c. Obtain PIREPs directly from the pilot, or if the PIREP has been requested by another facility, you may instruct the pilot to deliver it directly to that facility.

PHRASEOLOGY-
REQUEST/SAY FLIGHT CONDITIONS.

Or if appropriate,

REQUEST/SAY (specific conditions; i.e., ride, cloud, visibility, etc.) CONDITIONS.

If necessary,

OVER (fix),

or

ALONG PRESENT ROUTE,

or

BETWEEN (fix) AND (fix).

d. Handle PIREPs as follows:

1. Relay pertinent PIREP information to concerned aircraft in a timely manner.

2. EN ROUTE. Relay all operationally significant PIREPs to the facility weather coordinator.

3. TERMINAL. Relay all operationally significant PIREPs to:

(a) The appropriate intrafacility positions.

( b ) The FSS serving the area in which the report was obtained.

NOTE-
The FSS is responsible for long line dissemination.

© Other concerned terminal or en route ATC facilities, including non-FAA facilities.

(d) Use the word gain and/or loss when describing to pilots the effects of wind shear on airspeed.

EXAMPLE-
“Delta Seven Twenty-one, a Boeing Seven Twenty-seven, previously reported wind shear, loss of Two Five knots at Four Hundred feet.”

“U.S. Air Seventy-six, a D-C Niner, previously reported wind shear, gain of Twenty-Five knots between Niner Hundred and Six Hundred feet, followed by a loss of Five Zero knots between Five Hundred feet and the surface.”

REFERENCE-
AIM, Para 7-1-24, Wind Shear PIREPs.

Much of this information that we, as controllers, need to obtain from pilots is provided to you in the PIREP form via IDS. All you will need to do is fill in the blanks and submit the PIREP to the system. Use the above prescribed phraseology when disseminating the PIREPs to other pilots on frequency when necessary.


CWAs
CWAs are read on frequency in a very similar fashion as the SIGMETs. What exactly is a CWA?

CWAs are unscheduled in-flight, flow control, air traffic, and aircrew advisory. By nature of its
short lead-time, the CWA is not a flight-planning product. It is generally a nowcast for conditions
beginning within the next two hours. CWAs will be issued:

        • As supplement to an existing SIGMET, Convective SIGMET, AIRMET, or FA.

        • When an In-flight Advisory has not been issued, but observed or expected weather
           conditions meet SIGMET/AIRMET criteria based on current PIREPs and reinforced by other
           sources of information about existing meteorological conditions.

        • When observed or developing weather conditions do not meet SIGMET, Convective
           SIGMET, or AIRMET criteria; e.g., in terms of intensity or area of coverage, but current Pilot
           Weather Reports or other weather information sources indicate existing or anticipated
           meteorological phenomena will adversely affect the safe flow of air traffic within the Air Route
           Control Center (ARTCC) area of responsibility.

Where can CWAs be found? Click the following link: http://aviationweather.gov/products/cwsu/. This will bring you to a page with a map showing all of the ARTCC boundaries within the U.S. Mouse over the ZMP area (which should highlight in a reddish color) and click. A new, smaller window should open that should then display the current CWA and MIS (Meteorological Impact Statement) information. MIS are for ATC planning purposes only and NOT read over the frequency to pilots.

Here is an example of a CWA:

[img]http://dl.dropbox.com/u/16162462/HWI/5.jpg\\\" border=\\\"0\\\" class=\\\"linked-image\\\" /]

The above example is a CWA issued from the Kansas City, Missouri ARTCC. The "3" after ZKC indicates this CWA has been issued for the third weather phenomenon to occur for the day. The "301" in the second line denotes the phenomenon number again (3) and the issuance number, "01," for this phenomenon. The CWA was issued at 2140Z and is valid until 2340Z.

This would be read on frequency as:

"Attention all aircraft, hazardous weather information, Center Weather Advisory Three-Zero-One out valid until two-three-four-zero concerning an isolated thunderstorm over the KCOU airport available on HIWAS, Flight Watch, Flight Service Frequencies, or from Air Traffic Control upon pilot request"


Weather Deviations
Something else to keep in mind on this topic is pilot deviations for weather. I've heard many controllers throughout VATUSA get completely tripped up and turn to mush when a pilot makes a request such as, "Hey Center, N123AB, we need to turn about 30 left for build-up..."

Handling weather deviations is actually quite simple (phraseology-wise). The phraseology for this is as followed:

2. When a deviation cannot be approved as requested and the situation permits, suggest an alternative course of action.

PHRASEOLOGY-
UNABLE DEVIATION (state possible alternate course of action).

FLY HEADING (heading),

or

PROCEED DIRECT (name of NAVAID).

b. In areas of significant weather, plan ahead and be prepared to suggest, upon pilot request, the use of alternative routes/altitudes.

PHRASEOLOGY-
DEVIATION APPROVED, (restrictions if necessary), ADVISE WHEN ABLE TO:

RETURN TO COURSE,
or
RESUME OWN NAVIGATION,
or
FLY HEADING (heading),
or
PROCEED DIRECT (name of NAVAID).

It may not always be possible to approve a weather deviation due to traffic or other factors. Keep in mind, the pilot has ultimate authority in making these deviations, however. It's more or less a "weather emergency" in this case as flying directly through the convective weather could present a massive risk to the safety of the flight. As a controller, you'll need to find a way to work around these situations.

Another way that I regularly seem to hear deviations for weather approved by ATC:

"Deviations left of course/right of course approved, when able proceed direct [VOR/FIX/AIRPORT]."



This about covers the dissemination of hazardous weather information to pilots on frequency and should help many of you to provide a more professional and realistic service to pilots operating within our sector.

Further information on weather information can be found in Chapter 2, Section 6 of the 7110: http://www.faa.gov/air_traffic/publication...#atc0206.html.1.



Additions from other ZMP controllers:

MT: Good stuff AJ. I personally also add aviationweather.gov in my broadcasts. ie. "hazardous weather info ....... Available on HIWAS, flight service, aviationweather.gov or controller time permitting."


JM: I'll also add in the terminal setting, the hazardous weather information is usually disseminated on the ATIS as well.  The short broadcast, "Attention all aircraft, Hazardous weather information Convective Sigmet 22 Central for Wisconsin and Lake Michigan available on HIWAS, Flight Watch, and Flight Service frequencies" is usually sufficient.  If a pilot has a question about weather not in my area of jurisdiction, I will generally refer them to flight watch/flight service, but of course that is not possible on VATSIM.

Wouldn't it be cool if there was a Flight Service position that we could staff during certain times?


DK: For the sake of not confusing network pilots any more than some stuff already does, I usually drop the "HIWAS/FlighWatch/AFSS" bit and just say:

"Hazardous weather, Convective SIGMET XXC valid until XX55z for MN/IA/ND/SD, etc. available from Air Traffic Controller on request."

For you terminal guys, when you're recording the KMSP voice ATIS and a convective SIGMET or CWA coverage area falls within 50nm of KMSP, add the following into the voice ATIS immediately after approaches/runways in use:

"ATTN ALL ACFT: HAZARDOUS WX INFO FOR KMSP AREA AVAIL FROM ATC ON REQ" (Read as: "Attention all aircraft: Hazardous weather information for Minneapolis-St. Paul Airport Area available from Air Traffic Control on request.").

To each his/her own, though. I strongly encourage all the enroute guys to disseminate these advisories, workload permitting!



Other comments, contributions welcome! Hope this provides a bit of insight and assistance to the rest of VATUSA...

Hey there... Just recently put in an order for work through Albany Distributors (USB PTT Adapter)... I can send the personal contact info of one of the leads there who can put an order in.

www.albanyheadsets.com/plantronics is the website.

They've got some of the cheapest prices I've seen out there for the headsets and all sorts of accessories (eartips, extension cables, etc.).

They offer both the H31 Starset and the H81 TriStar for good rates there. They're webpage is still under development, but we got in touch with the main company customer service, Albany Distributors, and they sorted our orders out very quickly (again, I'll send the contact info for this guy should anyone be interested).

Just a reminder to everyone, we are three days away from this years Northern Migration!

On a personal note, this year's Migration will be a first for me to attend with this facility but I have thoroughly enjoyed my time working with these guys. I stand by my comments that ZMP is the most professional, organized and realistic crew I have had the opportunity to work with within VATUSA to date... The momentum the facility has built up over the past couple of years is really something special to have witnessed and I'm proud to be a part of this team! We try hard to provide a "real feel" to flying in the United States...



Below are some notes that us, as controllers, would like pilots to be aware of during your participation in this event to help maintain high situational awareness and improve your experience when navigating and communicating with ATC both for yourselves and for others.

During this event, 20 controllers or so will be working Live, side-by-side from the same location in Minneapolis, MN. As the flights available are pulled directly from the current real world flight schedules, this is truly a LIVE!, Real OPS event for both controllers and pilots alike.

For those of you who wish to fly Regional airline flights such as SkyWest (SKW), Comair (COM), Compass (CPZ), ASA, Mesaba (MES), Pinnacle (Flagship - FLG), etc. using CRJs or ERJs, you can find your flights located next to the appropriate Major airline regional logo (mostly Delta Connection flights). The carrier and aircraft type are provided in the pop-up Dash Board by clicking on a specific flight.

We do ask however that if you book one of the regional flights originating from MSP, please book the return flight back to MSP. These "out and back" flights generally retain the same flight number and callsign. So if you book Mesaba flight 2484 from MSP to Mason City, check to see if there is a return flight using the same number. This will help prevent another pilot from not only booking your return trip, but will prevent the headache of you, or another pilot, from not being able to log onto the network with the correct callsign, in the example above, MES2484.

If however you do experience this problem, we encourage you to log-in by dropping the first digit, and add an alpha character at the end of the flight number. So, using the above example, you would log-in as MES484A.

One other thing we ask, and we highly encourage, is please fly the type of aircraft that is listed for the flight. If unable to do so, and if you wish to substitute one type of aircraft for another, please do so using a comparable aircraft.

An example of this would be flying an A320 instead of a B737. However, we ask that pilots to the greatest extent possible, refrain from substituting a B747/B767/B777 for a smaller aircraft, especially if your flight is operated by a regional jet or prop.

B737s and A320 series would be okay substitutes for CRJs or ERJs. However, when we get 60 B777s and B747s back to back, our spacing requirements go through the roof, and our airport arrival rate decreases dramatically due to the increased spacing requirements. So we respectfully ask that pilots fly the aircraft listed on the booking system to the greatest extent practical, or follow the replacement schedule below:

Regional Jet/Prop = No bigger than A320 / B737 / MD80/90 Series (No B757/B747/B767/B777/MD11/DC10, Basically no Heavies!)

A320 / B737 / MD80/90 Series = May substitute like size aircraft, but no bigger than B757 and no heavies!

B757= No replacement unless smaller.

B747/B767/B777/MD11/DC10 or any other HEAVY = May substitute for another Heavy, or smaller aircraft.

Again, this is a respectful request from all of the controllers who are participating in this event. I think everyone, including the pilots, would really enjoy this event if we run as a real ops, flying the actual type of aircraft and callsign (ie: using SKW rather than DAL on a regional flight, using the actual operator) on their respective routes.

[size=](Regional Flights are HIGHLY encouraged for a special reason... More information will follow in the next day or two regarding why this is!)[/size]

[size=]On that note, we ask, and highly encourage, all pilots to read the Pilot Briefing.[/size] There is tons of information to found, such as where scenery can be located, how runways are assigned, the importance of making the downwind turn as depicted on the STAR charts, terminal parking locations and much much more. We have been very diligent in our preparations for this event and ask that pilot participants do the same. Please come prepared! When or if all else fails, please be sure to know how to fly a heading, altitude and maintain airspeed in accordance with ATC instructions. As we expect a high turnout during this event, please execute and comply with ATC instructions as quickly as possible. Remember, "Aviate, Navigate, Communicate." Do things in that order and all should be well!

[size=]And please, please, please, remember to obtain the ATIS and advise the approach controllers you have the appropriate code on initial contact from the communications transfer from the center! The same goes for calling for a clearance on the ground.[/size] Check in with the ATIS! PLEASE! We train our controllers to pay close attention to this tool as it's been available for a long time on VATSIM and serves a purpose to reduce controller workload on reading weather, runway, NOTAM information to each and every pilot that checks in on the frequency. You do us a huge favor by checking in with it as you'll be able to pre-plan which runway to expect (or at the very least, have a general idea) and maybe even make a request with us for a certain runway on frequency to reduce your taxi time on the ground (if we can accommodate).

[size=]The pilot briefing may be located here:[/size]
http://www.minniecenter.org/node/migration/brief.php

[size=]Finally, the booking system may be located here:[/size]
http://www.minniecenter.org/node/migration/reservation.php

Again, our facility will be staffed for a full 24 hours during the following times:

Friday, 7/29, 19:00 CDT
until
Saturday, 7/30, 19:00 CDT (and quite possibly later into the evening on Saturday night should the traffic levels warrant the coverage and the controllers have not suffered traumatic brain damage by then... )

(19:00= 7:00PM Central Daylight Saving Time)


We look forward to everyone's participation!
See everyone there!

<disregard, accidental double post>