|
Instructions on How to Use SquawkBox
and FS2000 ATL_ARTCC Controller Cardinal Airlines Pilot, CAL2131 Additional “Primers”
Written (or Being Written) by Daniel Hill ·
How to Fly a Departure Procedure (formerly
known as a SID) is currently under construction. ·
How to Fly a Standard Terminal Arrival is
currently under construction. ·
How to Fly an ILS Approach is
currently under construction. Advisories - ·
Do not slew once you are connected to VATSIM. Taxiing via slew mode is not
acceptable. · Once in the air do not pause; do not increase simulation speed to 2x or 4x or greater without approval from ATC.
Requirements and
Suggestions -
The
following session will demonstrate a flight plan from Atlanta (KATL) to New
York City (KLGA). NOTES: ·
Bold-face
type indicates what you type (say) to ATC. ·
Bold-face-italic
type indicates a typical response from ATC. ·
After
starting FS2000 for the first time after installing the fsuipc.dll file, you
should chose MODULES from your FS2000 menu bar, choose FSUIPC, choose the
TECHNICAL tab and enable the option that states “No Reposition on GPS Plan
Mode.” This prevents the flight
simulator from whisking you onto the runway when you load a flight plan. This need only be done once. 1.
Establish
your Internet connection. 2.
Run
FS2000 and position your aircraft at your airport of choice but not on a
runway or taxiway (slew over to the terminal area before you proceed -- nothing
dismays ATC more than seeing you pop onto his screen on runway 4 while he has a
747 on final approach to that runway). Slew Instructions - Make sure the
simulation is not paused. 2.1. Map mode
helps when slewing. Turn it on (and
off) by using CTRL-S. The minus (-) and
plus (+) keys zoom out and in. 2.2. Press Y
(activates slew mode) 2.3. Make sure
your NUMLOCK key is off. 2.4. Press
NUMPAD 2 (roll backward), or NUMPAD 8 (roll forward), or NUMPAD 4 (slide left),
or NUMPAD 6 (slide right), or NUMPAD 1 (yaw left), or NUMPAD 3 (yaw right)
until you have the aircraft where you want it, then press NUMPAD 5 to stop all
movement. [Note - The more you press a
key (or lean on it) the faster you will move, so be cautious.] 2.5. Press Y
(deactivates slew mode). 3.
Save your flight at this point (use FILE, SAVE FLIGHT). [Reason - Should you crash on takeoff, taxi
or during your flight you will be reset to this "gate" location
instead of to the runway where you started a few minutes ago.] 4.
At this time, if you have an add-on flight planning package
(FSNavigator, etc.) you will build your flight plan and export it (into
SquawkBox format) to the SquawkBox directory on your hard drive. Make sure you remember the name of the
file. I use the departure-destination
codes in the file name, so for this I'd use the filename katl_klga.sbp. If you do not have a flight-sim planning add-on,
continue and note 10.3 below. 4.1. Many
flight planner packages allow you to export into the FS2000 format so that you
can get a nice printout of your navaids, NDBs, intersections and load the plan
into your GPS. Unfortunately flight
plans built with the Flight Planner installed within FS2000 do not export to
SquawkBox format, nor does SquawkBox read FS2000 flight plans. 5. Go to the FS2000 menu bar (if you
cannot see the FS2000 menu bar, use the ALT-key to access the menu bar) 5.1.
Choose
FILE 5.2. Choose
MULTIPLAYER 5.3. Choose
CONNECT 5.3.1.
In the dialog box presented enter your aircraft callsign (e.g., USA1207
or TWA677) for the flight.
Realistic callsigns are appreciated by ATC. 5.3.2.
Choose the TCP/IP option 5.3.3.
Press the HOST button. 5.3.4.
On the next screen enter your SESSION NAME. It is easiest for all concerned to make the session
name your destination-departure airports -- in this case the session name would
be KATL-KLGA. 5.3.5.
Set the number of players to a value of about 50 (you can choose
more if you want -- handy for VATSIM fly-ins, where you may encounter a hundred
planes). 5.3.6.
Click OK. 5.3.7.
A "chat box" will pop up. Close it -- you don't need it. 6.
Now, run SquawkBox (you may need to task switch to reach the
SquawkBox program -- use ALT-TAB to task-switch). 6.1.
A dialog box pops up asking you for a player name. Enter your full name (first and last
--VATSIM requires users to use their real names -- if not they will deactivate
your account). 6.2.
Make sure TCP/IP is selected and click OK. 6.3. Another
dialog screen pops up (the "join session" box). 6.4. Press OK
or SEARCH. 6.5.
The next dialog box asks you for an IP address to search for. Leave this box blank (no entry required) and
press OK. 6.6.
The program should show you the name of the session you created in
Step 5.3.4. 6.7.
Click on OK or JOIN SESSION. 6.8.
The dialog boxes disappear. 7. The
SquawkBox title screen appears. 7.1. Click the
gray bar at the bottom of the title screen to initiate SquawkBox. 8. Return to your FS2000 Program
(task-switch?) 8.1.
The
SquawkBox interface box should appear within your FS2000 screen. 8.2.
To move
the box to a place where it will not be in your way during flight is a
trick. The box cannot be
"dragged" as a normal window can.
It must be "resized" into a new location on your FS2000
screen. 8.2.1.
Using the corners of the box (maneuver your mouse pointer to an
edge of the SquawkBox screen until it turns into a double-headed arrow), click
and drag the window. 8.2.2.
Using the technique above, expand and/or shrink the dimensions of
the box until it occupies a space comfortable for flight (does not obstruct
your view -- I use the upper left or very bottom of my FS2000 screen and reduce
the "depth/height" of the box so that one text line appears below the
white chat portion (you can scroll back to a limited number of previous
messages using the arrow keys you see in the SquawkBox window). 9. I suggest
using SquawkBox's TCAS (Traffic Collision Avoidance System) display. You can access it via the “E” button in the
SquawkBox window. This is your
collision avoidance system. It will
show traffic around you once you are connected. Blips turn yellow to indicate caution and red to indicate danger
of collision. 9.1. This
display must also be resized into a comfortable space in your panel. I usually place the TCAS gauge over the
clock or the backup EHSI or backup ADI.
Your choice. Right- and
left-clicking inside the gauge zooms it in and out. 10.
The SquawkBox (SB) menu is accessed by right-clicking
anywhere within the gray area of the box. 10.1.
Access the SB menu and click (and activate) the function called
SQUAWK STANDBY. This prevents your
plane from displaying all your information on the controller's screen right
away. 10.2.
If you already have an SB flight plan ready to load in, access
the drop-down menu and click on FMS FUNCTIONS, then on LOAD FMS FLIGHT
PLAN. A dialog box will pop up. Go to
step 10.4. 10.3.
If you do not have an SB flight plan ready to load in (i.e., if
you do not have a program that lets you plan a flight and export the flight
plan to SquawkBox format), you will not be able to LOAD FMS
FLIGHT PLAN -- you will have to create a flight plan using SquawkBox's built-in
FMS. See http://www.ivpa.com/manuals/sb/sec04-01.htm
for help. The “F” button on the
SquawkBox screen brings up the built-in FMS if you think you can figure it out
without help.] Once you build or load
your flight plan using FMS you would use access the drop-down menu, choose ATC
FUNCTIONS and choose FILE FLIGHT PLAN 10.4.
Confirm and/or enter the following information where required 10.4.1. Your callsign should match what you
entered in Step 5.3.1. [Note - If not,
press CANCEL, access the drop-down menu, choose ATC FUNCTIONS, then CHANGE
CALLSIGN, enter the proper callsign, click OK, then go back to Step 10.2.] 10.4.2. Choose the aircraft type from the
drop-down menu within the dialog box. 10.4.3. Use Prefix T (means your aircraft is
equipped with TCAS) or B (meaning TCAS-equipped heavy aircraft) if your
aircraft is classified as a HEAVY craft (747, etc.). 10.4.4. Use suffix F for starters, meaning
that you are FMS-equipped, or use suffix B (meaning TCAS-equipped heavy aircraft)
if your aircraft is classified as a HEAVY craft (747, etc.). 10.4.5. Confirm your flight plan matches the
one you setup. You can edit your flight
plan in this box (your FMS and your autopilot, if you are using one, will not
pick up the changes, so editing should be done for purposes of brevity and/or
clarity only). For example, if your
flight plan lists five or six intersection fixes along Jetway J40, you might
replace that long string of intersections with "J40" but this only
makes it easier for the ATC controller and you to read, nothing more. What is entered in this box is what ATC will
see for your flight plan. 10.4.6. Enter your "requested" en
route altitude (if you choose an invalid flight level, ATC will ask you to
correct and refile). Remember -- NEODD
and SWEVEN below FL290, then FL290 eastbound, FL310 westbound, FL330 eastbound,
etc. VFR uses the aforementioned rules
plus 500 feet. 10.4.7. Enter any remarks you may have for
ATC (e.g., "I'm a new pilot"
or "No charts available" or "Live pets on board"). 10.4.8. Enter the number of passengers and
crew you're carrying, if you like. 10.4.9. You can specify an alternate airport
in case of unsuitable landing conditions at your prime airport. 10.4.10.
Click on OK -- your flight plan is tentatively filed in the
system. 10.5.
You can choose FMS FUNCTIONS and the SAVE FMS FLIGHT PLAN if you
wish to save your flight plan for future use. 11. Access
the drop-down menu and click on CONNECT 11.1.
A dialog box will appear. 11.2.
You need to enter your VATSIM ID and password. 11.3.
Choose (or enter) a server IP address with which to connect. Choose the server closest to your real-world
geographic location for best results.
Server addresses are available on the VATSIM pages at http://www.vatsim.net/status/vatservers.htm 11.4.
Indicate if you will be using Roger-Wilco by checking the
appropriate box, if applicable. 11.5.
Click OK. 12.
Upon returning to the FS2000 screen there should be some blue text
appearing in the SquawkBox area (something about using your real name, etc.)
and it should be accompanied by a "ding-dong" chime. The controller can now see your plane but
will not act yet. If you are on a
runway or taxiway (shame on you), expect a polite "message" within
moments. 13. Now it’s
time to contact ATC and get going. 13.1.
Access the drop-down menu and click on RESEND FLIGHT PLAN. 13.2.
Access the drop-down menu and click on SQUAWK STANDBY (this will
clear the check-mark and take you OFF 'squawk standby.' Now the controller will be able to see your
flight information, including callsign on his scope. 13.3.
Find out what controller, if any, you need to contact for
clearance to your destination. 13.3.1. Access the drop-down menu and click
on ATC DIRECTORY. This will list any
and all ATC positions within range of your communications device. If you are at Atlanta's Hartsfield Airport
(KATL) you would look for ATL_DEL. If
not available, look for ATL_GND. Again,
if not available look for (in this order) ATL_TWR, ATL_DEP, ATL_APP, ATL_CTR. 13.3.2. Always look for a controller at
your airport or, in the case of the APP and/or CTR controller, in your region
-- and always in that order -- DEL, GND, TWR, DEP, APP, CTR.] 13.3.3. You may notice that the controller
has adjusted the first part of his callsign; e.g. ATL1_TWR instead of ATL_TWR
-- this is OK and equivalent. 13.3.4. If the controller has a _V_ in the middle of the callsign, it means
that they are also available for voice ops (using Roger Wilco). 13.4.
Double-click the controller of your choice, using the scheme above
and your radio will automatically be set to his frequency. If you indicated you are using Roger Wilco
and the controller is on voice ops (_V_) your Roger Wilco program will
automatically be set to the voice channel. 13.4.1. Even though the controller may be
voice ops capable, this does not mean that you must use voice to contact
him/her. Most controllers, though,
prefer that you choose one method (text or voice) and stay with that method
while in contact with them. 13.5.
Get current weather information and phonetic code by requesting
the current ATIS in one of two ways -- 13.5.1. In the white message area of
Squawkbox, type .ATIS ATC_CALLSIGN
(note the period -- it is necessary) and press ENTER on your
keyboard. You should see an ATIS report
(in blue text) appear in the gray area of the SquawkBox (you may need to use
the scroll arrows to scroll back through the lines to see it all). ATC_CALLSIGN is the callsign of the
controller whose ATIS you want (e.g., ATL_TWR, ATL_APP, ATL_V_CTR, etc.). Usually TWR keeps a current ATIS, but if TWR
isn't available try any of the other area controllers per 13.3.2. Note the phonetic code of the ATIS report
(ALPHA, BRAVO, CHARLIE, etc.). This
ATIS report should also tell you what your altimeter should be set at. 13.5.2. The
controller’s ATIS message might direct you to tune to a certain frequency and
request the AUTOATIS. AUTOATIS is a
computer-generated ATIS report that the servers produce. It makes the controller’s job easier in that
he/she need not continually update their ATIS reports. To use AUTOATIS (available only at some airports)
find out what frequency to tune (check the controller’s ATIS report , tune to
that frequency and type AUTOATIS AIRPORT_CODE where AIRPORT_CODE =
the ICAO code for the airport (Atlanta = KATL, Heathrow = EGLL, etc.) Don't forget to re-select your ATC
controller (right-click, ATC DIRECTORY, etc) after finished reading the
AUTOATIS message!] 14. Request
IFR clearance to your destination. For
the following example, we will assume we are in ATL airspace and that we are
USA1207, from KATL to KLGA. 14.1.
In the SquawkBox
white message area (or using the keyboard key to transmit via voice) type (or
say), "USA1207, requesting IFR clearance to KLGA (or you could say
LaGuardia) with information ALPHA".
[You better get a pencil and paper ready.] 14.2.
You should, within a few minutes receive a message along the
following lines -- "USA1207, cleared to KLGA as filed, climb and
maintain 10,000, expect FL290 10 minutes after departure, departure frequency
126.90, squawk 0231." 14.3.
Copy this all down, because you'll need it later and you have to
read it back to the controller. 14.4.
At any time you can contact the controller and say "USA1207,
say again please." However, it's
important that you try to keep repeats to a minimum. 14.5.
You will know when a text message is for you (as opposed to a
message for someone else) -- the text will be blue (instead of green) and you
will hear the two-bell chime (ding-dong) instead of the mike-static
(psssssst...) sound. 14.6.
If the controller indicates any additional route information, make
notes because you'll need to edit your FMS Flight Plan and resend it
afterwards. He may indicate that he is
routing you to a specific intersection, navaid or NDB on departure before you
start your flight plan. The controller
may say "USA1207, cleared to KLGA via ATLANTA FOUR departure NOONE
transition, then as filed, climb and maintain 10,000, expect FL290 10 minutes
after departure, departure frequency 126.90, squawk 0231." This means that upon departure, expect to be
routed to the NOONE intersection before picking up your flight plan. You are within your rights to request that
you be vectored to any intersection or navaid. If you are unfamiliar
with a navaid reference, simply tell the controller "USA1207, will require
vectors to NOONE." [During
flight you can also request vectors if you become confused, and then take the
time to figure out the problem while en route to the fix.] 14.7.
Read back the clearance so the controller knows you read it
properly. Abbreviations are acceptable
and preferred in many cases. You can
find a list of acceptable abbreviations within the VATSIM site. Type (or say) "...clrd KLGA as filed
c/m 10000 exp FL290 10 min after, dep frq 126.90 sq 0231, USA1207." 14.8.
At this point the controller should state something like "Read
back is correct, pushback and engine start approved, advise when ready to
taxi..." 15. You may
be handed off to another controller at this point, "USA1207, contact
ATL_GND on 121.90". If so,
acknowledge that you understand the handoff by saying, "...over to
121.90, good day, USA1207," and access the SquawkBox menu and choose
ATC DIRECTORY. Double-click the
controller who you are being handed off to.
Voila! The COMM channel is
automatically reset (so will the Roger Wilco voice address if you are on voice
and the controller is, too). 15.1.
Note - Do not simply change your COMM frequency
on your FS2000 radio. This will not
complete the frequency change! 16. By now
you may have noticed that sometimes your callsign goes first in what you are
typing or saying, sometimes it goes last.
Here's a soft rule -- when requesting or stating intention
state your callsign first, when reading back or responding to a request made
by ATC, state your callsign last. 17. Go ahead
and push your plane back from the gate (slewing is permitted for this,
but slowly, please) and start your engines. 18. Contact
the appropriate controller when ready to taxi.
"USA1207, ready to taxi..." 18.1.
Wait for approval to taxi.
"USA1207, taxi to 8R..." 18.2.
Approval to taxi to a specific runway automatically authorizes you
to cross all runways except the runway to which you have been assigned
(active runway). 18.3.
Approval to taxi to a runway automatically implies that you will not
enter upon the active (assigned) runway.
You must hold short of the active runway. Some controllers include the term "hold
short" in their instructions but it is not necessary. You must hold short of the active runway
unless told to "taxi into position and hold." 18.4.
A controller might indicate that you must hold short of any or all
other runways that you encounter during your taxi "USA1207, taxi to
runway 8R, hold short runway 15..." In this case you must stop before crossing runway 15 and contact
the controller for permission to cross. 18.5.
Read back that you copy "...taxiing to 8R, USA1207"
or "...taxiing to 8R, will hold short runway 15, USA1207" and
taxi to the runway (don't forget, hold short once at 8R). It is absolutely mandatory that you
read back any and all "hold short" instructions. 18.6.
Report in when holding short at your runway. "USA1207, holding short rwy
8R." At this point you may be
handed off again to another controller.
If so, read back that you understand and use the ATC directory to
double-click the new controller. 19. Contact
the new controller and advise him of your situation "USA1207 h/s 8R for
dep..." 19.1.
Note - When handed off to another controller it is up to you to
make first contact with that controller.
In busy times, a simple "ATL_TWR, with you…" will suffice. 19.2.
In a few minutes you will be cleared for takeoff. "USA1207, fly heading 070 at MM,
winds 090 at 05, runway 8R cleared for takeoff" 19.3.
Read back "...clrd for t/o and hdg 070 at MM (or
ATL 4 DME), USA1207" and go!
Once clearance for takeoff is given you must move quickly (there may be
a jet on final approach for your runway).
Any preflight adjustments should be made prior to taxi (setting
autopilot, NAV radios, etc.). Once you
are on the runway and cleared for takeoff you are expected to roll for takeoff.
19.4.
Upon departure you may again be handed off. Read back (without a voice op this is a
trick with one hand on the yoke, a lot of pilots let the autopilot have the ascent
for a few moments) and switch frequencies, contact the new controller (here's a
perfect time for "...with you, USA1207") and get ready to be
vectored for departure. Remember to
maintain runway heading (or the heading assigned to you in the takeoff clearance)
until told otherwise by ATC. Climb to
but do not exceed the initial altitude given in your IFR clearance (remember,
“…c/m 10,000…”). 20. ATC will
vector you to your departure track, perhaps clear you to higher altitude (or
even your filed en route altitude) and then clear you on your own
navigation. At this point you can start
flying your plane according to your flight plan. 21. You will
eventually, if not already, be handed off to the CTR controller who will guide
you through the en route phase of your flight.
Remember to read back instructions, switch frequencies and check in with
the new controller for each handoff. In
our example, we'd probably be handed off from ATL_CTR to DC_CTR and then to
NY_CTR as we move to LaGuardia airport.
[Note - If all stations were staffed, NY_CTR would hand us off to
NY_APP, who would hand us off to LGA_TWR, who would hand us off to LGA_GND.] 21.1.
Note - If you leave the airspace of the current
CTR controller and there is no one on duty in the next CTR he will inform you
of this, approve you to switch frequencies (122.80 for UNICOM is a good choice)
and say goodbye. You would then
frequently check the ATC DIRECTORY to see if anyone comes online in that area. If so, switch frequencies and contact
them. If the controller sees you first
he will send you a PRIVATE MESSAGE, which will sound the ding-dong chime and be
in blue. This will inform you to switch
frequencies and make contact. 22. When
climbing through FL180 (18,000 ft MSL) you reset your altimeter to 29.92. 23. When
descending through FL180 (18,000 ft MSL) make sure the controller gives you the
local (or destination airport) altimeter reading and reset your altimeter to
that setting. If he doesn't give it to
you, request it politely "USA1207, request altimeter setting for
KLGA..." Don't forget to
check AUTOATIS or request the ATIS of a controller at your destination airport
(AUTOATIS KLGA or .ATIS ATC_CALLSIGN). 24. Anytime
you switch frequencies away from a controller you are already in contact with, inform
them first and advise them when you switch back to their frequency. [Example --
"NY_CTR, USA1207 switching frequency for AUTOATIS, will advise upon
return this frequency…."] 25. When you
are told to descend you can prepare to be handed off in reverse order (and
dependent upon what controllers are available), from CTR to APP to TWR and then
upon landing to GND. If any of those
functions are not manned you will probably be held on to by the ATC next up on
the ladder (e.g., CTR can usually guide you into approach airspace, vector you
to the approach, clear you for landing and taxi you to the gate at the major
airports in his control, APP can do all that except guide you into approach
airspace, TWR can only handle you from when you "lock on" to the ILS
or 10 miles from the airport and GND can't do a thing for you until you are
landed). 26. Remember
that when you land, unless you are approved to taxi to the gate you are
required to exit the active runway immediately after slowing to taxi speed and
hold short of any other runways or taxiways (yes, even taxiways) you encounter
and ask permission to cross (or enter onto taxiways). [Example - "GND, USAir1207 clear of rwy 22, holding short
of taxiway…."] When in doubt, stop and ask. 27. If you
are approved taxi to the ramp (gate) it means you may cross all runways on your
way (it is assumed you will not have to cross the active you just exited
again). If you made a wrong exit from the active runway and need to re-cross
it, ask! If ATC gives you any
"hold short" instructions make sure you read them back! 28. Get
approval to taxi to your gate and taxi there.
Stop, shut down your engines, say "good day" to the ATC
and then SQUAWK STANDBY. Exit SquawkBox
before shutting down FS2000, or load/create a new flight plan, refuel, SQUAWK
NORMAL and continue your adventure. After
three of four flights you won't need this guide anymore. You'll find that the controllers are very,
very helpful as long as you ask and don't go rolling around the airports or
flying through the skies oblivious to their direction. If you're flying with VATSIM you're in it
for the interactivity, so play along and play well. If you're unfamiliar with how to maintain heading and altitude
and speed use your autopilot until you are familiar. There's nothing worse than a pilot in crowded airspace who cannot
control his plane. Collisions with
other planes can occur, ruining another pilot's flight as well as your own. Enjoy your flight! |
