|
Instructions on How to Use SquawkBox (SB) and FS2002 To Fly with Real-Time, Live sim-ATC By
Daniel M. Hill Introduction –
My appreciation to those of you who have been waiting patiently for this tutorial. First
of all let me make this perfectly clear – there may be numerous errors,
redundancies and format inconsistencies within the following text.
Due to a necessary rearrangement of steps in which tasks are carried out
in the SB-FS2002 interaction (as opposed to the arrangement in the SB-FS2000
interaction) there is no doubt room for error. Please contact
me if you find an error below or if you have a suggested change to this
text. Some
may think that the new interface for SB with FS2002 is clumsy, difficult to work
with and limiting. Perhaps, but
remember this is only a temporary
patch which was feverishly worked out by those at The Developers Group at our
request for a method by which we could get FS2002 to run with SquawkBox as soon
as possible. The Developers Group
continues work on new server software and a new revision for SB that they hope
will be as seamless – perhaps even smoother – than that used in SB 2.3.4 for
FS2000). Advisories –
·
If you
are using FS2000, see my original tutorial entitled “Instructions
on How to Use SquawkBox and FS2000 To Fly with Real-Time, Live sim-ATC”. ·
SB 2.3.4
will not function with FS2002 (unless you’re using FSWide, I am told) ·
SB 2.3.5
will not function with FS2000. ·
When
exporting Flight Plans written with third-party software (e.g., FSNavigator 4.5)
to SB, make sure you are exporting to the proper SB directory.
You may have an SB directory for the FS2000 application and a separate SB
directory for the FS2002 application. ·
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 ·
Microsoft
Flight Simulator 2002
(required). Both the Standard
Edition and the Professional Edition are compatible.
As before -- yes, you need to purchase this program ·
Register
with VATSIM
(required) - Do it at VATSIM's website.
Registration is instantaneous. Free! ·
Roger
Wilco
(suggested) - If you own a microphone and speakers (or headset) you can interact
via voice with ATC if you download and install Roger Wilco at Resounding.com.
The Roger Wilco program will automatically execute during SquawkBox startup if
you so desire. Free! ·
SquawkBox
(required) - Download from the PC/SB site
and install. Make sure you download version 2.3.5 for FS2002.
Free! ·
Whazzup!
(suggested) -- Want to know what controllers are online so that you can plan a
flight in an area where there is live ATC at the moment? Download Whazzup
at Schiratti.com and install
and run it while online, before (or during) MSFS startup. It will show you a map
of the world and show you what controllers (and pilots) are online. You can zoom
in/out, move the map, filter the map (to show only certain flights, etc.). Free!
·
ServInfo
(suggested) – Here’s a neat little non-graphical program that will list and
sort all ATC, pilots, servers, etc. for you in whatever fashion you desire. A
beautiful interface makes it simple. At a glance you can tell where
ATC is in the USA, or the UK, or wherever. Try it – you’ll like it. You can
find it at http://avsim.com/hangar/utils/servinfo/home.htm
·
FSNavigator
or similar
flight planner (suggested) - FSNavigator can be found here.
If you choose another flight planner, it should be able to export flight plans
in SquawkBox format. Most flight planners charge a fee between $20 and $30. Good
news is that most offer free "trial" downloads. In the case of
FSNavigator, the trial version will work for twenty (20) FS sessions and then
refuse to work unless you pay. Payware. ·
FSUIPC.dll
(required) -- This file is available at no charge from Schiratti.com,
and should be placed into your FS2002/modules directory.
You must have the most recent version of FSUIPC.dll for SB to work with
FS2002. 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
moving a copy of the fsuipc.dll file to the FS2002/modules directory and
starting FS2002 for the first time, you should chose MODULES from your FS2002
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 only this one time (and
each time after you install an upgraded version of fsuipc.dll. 1.0
Establish
your Internet connection. 2.0
Run
FS2002 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). 2.6.
Alternatively
you can use FS2002's postioning where you can choose parking positions on aprons
instead of runways. 3.0
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.] 3.1.
Peter
Dowson's "AutoSave" utility is also helpful.
It will automatically save your flight at regular intervals so that if
you lock up on final approach, you can recover your flight from a few minutes
before without having to start all over again (http://www.schiratti.com/dowson).
4.0
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 katlklga.sbp. If you do not have a flight-sim planning add-on,
continue and note Step 7.4.2 below. 4.1.
Many
flight planner packages allow you to export into the FS2002 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 FS2002 do not export to SquawkBox format, nor does SquawkBox
read FS2002 flight plans. 5.0
Go
to the FS2002 menu bar (if you cannot see the FS2002 menu bar – you are
probably in full-screen mode -- 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 16 (that’s maximum for FS2002) 5.3.5.1.
Click OK.
A "chat box" will pop up. Close it -- you don't need it. 6.0
Return to the PC Desktop (you may need to task switch to reach the SquawkBox
program -- use ALT-TAB to task-switch). 6.1.
Run the
SB Host as follows 6.1.1.
Click
START, 6.1.2.
Click
PROGRAMS, 6.1.3.
Click
SQUAWKBOX FOR FS2002, 6.1.4.
Click SB
HOST FOR 2002. 6.1.5.
An
empty application box will appear on your desktop. Leave it there. 6.2.
Run the
SB Main program as follows 6.2.1.
Click
START, 6.2.2.
Click
PROGRAMS, 6.2.3.
Click
SQUAWKBOX FOR FS2002, 6.2.4.
Click SB
MAIN PROGRAM. 6.3.
A dialog
box pops up asking you for a session name. 6.3.1.
Enter
your name or anything else you like. 6.3.2.
Make sure
TCP/IP is selected and click OK. 6.4.
Another
dialog screen pops up (the "join session" box). 6.4.1.
Click on
START 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.5.1.
The
program should show you the name of the session you created in Step 5.3.4. [If
not, return to Step 6.5 and enter 127.0.0.1 in the IP box and click OK.] 6.6.
Highlight
your session and click on JOIN (SESSION). 6.7.
The
dialog boxes disappear. 7.0
The
SquawkBox title screen appears. 7.1.
Click the
gray bar at the bottom of the title screen to initiate SquawkBox. 7.2.
You
should now observe the old, familiar SquawkBox Access Panel appear within
the empty application window that opened up in Step 6.1.5.
[If not, shut everything down and find your SquawkBox.ini
file on your hard drive and delete it, then restart the entire process.] 7.3.
Right-click
the SB Access Panel in the gray-area. 7.3.1.
Click ATC
FUNCTIONS 7.3.2.
Click
CHANGE CALLSIGN 7.3.3.
Enter
your aircraft’s callsign and click OK. 7.4.
Right-click
the SB Access Panel 7.4.1.
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 flight plan dialog box will pop up. Go to step 7.4.3. 7.4.1.1.
It is
imperative that the SB Flight Plans you use are located in the main SB Folder.
Otherwise SB will look for some necessary files later on in the folder that the
FPs are in and it will pop up warnings that they are not found. 7.4.2.
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 [Note – You don’t have to
build a Flight Plan using the FMS – you can simply fill out the flight plan as
detailed below BUT you will not be able to use the FMS as an autopilot if you do
this. What goes into the flight
plan dialog box is for the controller’s use.] 7.4.3.
Confirm
and/or enter the following information where required 7.4.3.1.
Your
callsign should match what you entered in Step 7.3.3. [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 7.4.1.] 7.4.3.2.
Choose
the aircraft type from the drop-down menu within the dialog box. 7.4.3.2.1.
Use
prefix T (means your aircraft is equipped with TCAS) 7.4.3.2.2.
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, 767, A340, A380, MD-11,
etc.). 7.4.3.3.
If
you’ve loaded the flight plan, confirm your flight plan waypoints match the
the ones in the flight plan you set up. You can edit your flight plan waypoints
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. 7.4.3.4.
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. 7.4.3.5.
Enter any
remarks you may have for ATC (e.g., "I'm a new pilot" or "No
charts available" or "Live pets on board" or “Able to fly DPs/STARs”,
etc.). 7.4.3.6.
Enter the
number of passengers and crew you're carrying, if you like. 7.4.3.7.
You can
specify an alternate airport in case of unsuitable landing conditions at your
prime airport. 7.4.3.8.
Click on
OK -- your flight plan is tentatively filed in the system. 7.4.4.
You can
choose FMS FUNCTIONS and the SAVE FMS FLIGHT PLAN if you wish to save your
flight plan for future use. Then
next time you can simply “load” it. 7.4.5.
Access
the drop-down menu and click on CONNECT 7.4.5.1.
A dialog
box will appear. 7.4.5.2.
You need
to enter your VATSIM ID and password. [Note
– Old SATCO IDs and passwords will not work!] 7.4.5.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.
[Note – You can also find out which server is responding faster to your
connection by using ServInfo's PING
function. You can also extract the ipaddr.txt from ServInfo into SB for name reference to the servers as well. 7.4.5.4.
Indicate
if you will be using Roger-Wilco by checking the appropriate box, if applicable.
[Note - Make sure your Roger Wilco is configured to require "press key to talk" and not
"voice activated." Never
use the SPACEBAR key as the microphone activation key.
I use the SCROLL LOCK key.] 7.4.5.5.
Click OK. 7.4.6.
Right-click
the SB Access Panel 7.4.6.1.
Click on
ATC DIRECTORY 7.4.6.2.
Find out
what controller, if any, you need to contact for clearance to your destination. 7.4.6.2.1.
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. 7.4.6.2.2.
Always
look for a controller at your airport
or, in the case of the APP or DEP and/or CTR controller, in your region
-- and always in that order -- DEL, GND, TWR, DEP, APP, CTR.
For example, if you’re sitting at KDFW you would need to look for
DFW_DEL, DFW_GND, DFW_TWR, REG_APP (Regional Approach), or DFW_CTR. If you’re not sure what the callsign is of your TRACON or
CTR see if an APP or DEP or CTR is online, switch to them, contact them and ask.
They’ll be happy to point you in the right direction!] 7.4.6.2.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. 7.4.6.2.4.
If the
controller has a _V_ in the middle of the callsign (e.g., ATL_V_CTR), it means
that they are also available for voice ops (using Roger Wilco). 7.4.6.2.5.
Other
callsign modifications in the middle position can include _VS_ (a voice student),
VM ( a voice mentor – someone who trains others on voice ops), _CF_ (usually
the Chief of the ARTCC), _AC_ (usually the Assistant Chief of the ARTCC and _CI_
(the Chief Instructor of an ARTCC). 7.4.6.2.6.
As
long as the callsign ends in _DEL, _GND,
_TWR, _DEP, _APP, _CTR or _FSS
(this last one is rare, for oceanic positions mostly) it is a valid controlling
position. _OBS stands for observer
and are just watching. 7.4.6.3.
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_ or otherwise) your Roger Wilco
program will automatically be set to the voice channel. 7.4.6.3.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.
7.4.6.4.
Get
current weather information and phonetic code by requesting the current ATIS in
one of two ways – 7.4.6.4.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., .ATIS ATL_TWR, .ATIS ATL_APP, .ATIS ATL_V_CTR, etc.).
Usually TWR keeps a current ATIS, but if TWR isn't available try any of the
other area controllers per 7.4.6.2.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. 7.4.6.4.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
you finish reading the AUTOATIS message!] 7.4.7.
Right-click
the SB Access Panel 7.4.7.1.
Choose
RESEND FLIGHT PLAN 8.0
8.
Return to your FS2002 Program (maximize your FS2002 application) 8.1.
The
SquawkBox access panel will not
appear within your FS2002 screen (this differs from FS2000/SB). 8.2.
You will
see text scrolling across the screen in a green ticker-tape format and/or an FS
Chat Window. If an FS Chat
Window is not open, simply press ENTER. The
text therein should be something about using your real name, etc.
This is your signal that you are actually connected to the VATSIM system.
The FS Chat Window becomes your
ATC-Interaction window. 8.2.1.
You can
enter any and all text (ATC chatter) and dot-commands
that are valid for SB and they will be transmitted to the SB Access Panel
automatically (and invisibly) and on to ATC. 8.2.2.
To tune a
new ATC from within FS2002 you need only enter .ATIS ATC_CALLSIGN (the period [.] is necessary), where
ATC_CALLASIGN is replaced by the exact
title of the new ATC controller. For
example, .ATIS ATL_V_CTR or .ATIS JFK_TWR, or .ATIS LAX_V_APP, etc.
It is very important you know the exact callsign.
This will switch your radios to the right frequency and
set your Roger-Wilco frequency if you are using Roger-Wilco. 8.2.3.
There
should be little need to task-switch back out to the SB Access Panel unless you
need to perform a function that cannot be executed by dot-commands or normal ATC chatter (text). 8.2.4.
Return to
the PC Desktop. 8.2.4.1.
Using
START/FIND or the EXPLORER application, find the program named FSChatScroll14AutoShow.exe
in your SB directory (you may wish to create a Desktop Shortcut to this program
for future reference). 8.2.4.2.
Run the
program (double-click the program filename or the shortcut you create for it). 8.2.4.3.
This
opens a small application window. 8.2.4.3.1.
Minimize
it and return to FS2002. 8.2.4.3.2.
This
program will fix a bug in the FS Chat Window.
Now, whenever any text is sent
by you, ATC or another pilot on your frequency, the FS Chat Window will open
automatically and display the text while positioning the text so that you can
see the most recent transmission. 8.2.4.3.3.
You can close the FS Chat Window by pressing ENTER at any time and it
will reappear when new text is added. The
ENTER key, you might realize by now, closes an open FS Chat Window and opens a
closed FS Chat Window. 8.2.4.4.
Without
this program, the Chat Window will only open when you press ENTER.
You will not see ATC transmissions unless the window is open (sometimes
important) and when the window does open, you’ll have to manually scroll down
to the bottom to see the latest transmission.
That would be quite troublesome. 9.0
I
suggest using SquawkBox's TCAS (Traffic Collision Avoidance System) display. You
can access it via the “E” button in the SquawkBox Access Panel (you’ll
have to switch back out to the Desktop to reach it). 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 be resized into a
comfortable space in your panel (you can’t drag it – you reposition/resize
it by dragging each corner one at a
time). 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.0
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. 10.1.
In the FS
Chat Window (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.] Instead of using
ALPHA, use the phonetic code of the ATIS report you have received. The
controller will see that you are aware of the current weather situation and
airport advisories/conditions. The code changes once about every hour, so if you
are on the ground for an extended period, recheck ATIS often. 10.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." 10.3.
Copy this
all down, because you'll need to read it back to the controller. 10.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. 10.5.
You will
know when a text message is for you -- you will hear the two-bell chime
(ding-dong) instead of the mike-static (psssssst...) sound. 10.6.
If the
controller indicates any additional route information, make notes because you'll
need to edit your FMS Flight Plan and resend it (edit it by right-clicking the
SB Access Panel and choosing ATC FUNCTIONS, then FILE FLIGHT PLAN – you can
edit the flight plan, click OK and the FP will automatically be resent to the
controller). 10.7.
He may
indicate that he is routing you to a specific intersection, navaid or NDB on
departure before you start following 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.] 10.8.
Read back
the clearance so the controller knows you read it properly. Abbreviations are
acceptable and preferred in many cases. Type (or say) "...clrd
KLGA as filed c/m 10000 exp FL290 10 min after, dep frq 126.90 sq 0231,
USA1207." 10.9.
At this
point the controller should state something like "Read back is correct,
pushback and engine start approved, advise when ready to taxi..." 11.0
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." 11.1.
Type .ATIS
ATL_GND into the FS Chat Window and, “Voila!” The COMM channel is automatically reset (so will the Roger
Wilco voice address if you are on voice and the controller is, too). 11.2.
Note
- Do not
simply change your COMM frequency on your FS2002 radio. This will not complete
the frequency change! 12.0
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. 13.0
Go
ahead and push your plane back from the gate (slewing is permitted for this, but slowly, please) and start your engines.
FS2002 also has a pushback function (P, then 1 or P, then 2). 14.0
Contact
the appropriate controller when ready to taxi. "USA1207, ready to taxi..." 14.1.
Wait for
approval to taxi. "USA1207,
taxi to 8R..." 14.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). 14.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." 14.4.
A
controller might indicate that you must hold short of any or all other
runways that you encounter during your taxi "USA1207, runway 8R taxi
approved, hold short runway 15..." In this case you must stop
before crossing runway 15 and contact the controller for permission to cross. 14.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. 14.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 FS Chat
Window (.ATIS ATC_CALLSIGN) to contact the new controller. 15.0
Contact
the new controller and advise him of your situation "USA1207 h/s 8R for dep..." 15.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. 15.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" This means that
after takeoff you would turn to heading 070 at the middle marker (which is
generally a half-mile from the end of the runway). He may say "…fly
heading 070 at ATL 4 DME…" which means you'd tune ATL VOR on your
NAV1 and execute the turn to heading 070 when your Distance Measuring Equipment
(DME) reads 4.0 miles. 15.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. 15.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…”). 16.0
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. 17.0
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.] 17.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 (sorry, need to go back to the SB Access panel for this)
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. This will inform you to switch
frequencies and make contact. 17.2.
If you
wish to send a private message to a controller or another aircraft, you must use
the .msg function – e.g., .msg
ATL_CTR can I got to 2x simulation speed?
[Note that the period is necessary.]
Only ATL_CTR will receive your transmission – other pilots cannot see
it. You’ll know a private message coming in for you because it
is preceded with a [PRIVATE] tag at the beginning of a line.
If you wish to communicate with a neighboring aircraft (say, USA1245),
you’d type .msg USA1245 hi there. 17.2.1.
Be
careful. Never put anything in a
private message that you would embarrass you if everyone saw it.
There are more instances than I can count where a pilot messed up the .msg
command and the whole flight-sim world saw their message. 18.0
When
climbing through FL180 (18,000 ft MSL) you reset your altimeter to 29.92. 19.0
Now
in the cruise phase of your flight it's time to check destination weather (via
SB’s ACARS function or by asking present Controller) and start planning for
your approach (charts, procedures review etc...). 20.0
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
while on the AUTOATIS frequency or .ATIS ATC_CALLSIGN). 21.0
Anytime
you switch frequencies away from a controller you are already in contact with,
request a frequency change first. [Example -- "NY_CTR, USA1207 requesting frequency change for AUTOATIS, will
advise upon return this frequency…."] 22.0
If
you need to step away from the computer cockpit for a few seconds, request
it first. Nothing frustrates a
controller more than trying to contact you with important information (e.g., a
handoff to another controller or an imminent collision) while getting no
response. When you return to the PC
cockpit, let him/her know. 23.0
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). 23.1.
Sometimes
a CTR controller (or even an APP controller) will issue (or ask you if you can
accept) a crossing restriction, e.g., USA1207, descend at pilot’s
discretion, cross LENDY at 11,000 and 250 knots, KLGA altimeter 30.12. 23.2.
What he
means is, “Can you descend on your own and cross a certain nav-point (he’ll
name it) at a certain altitude (again, specified to you) and/or speed
(specified, if necessary).” The
trick is knowing how early to start your descent.
Soft rule – for every 1000
feet you need to descend, plan on four (miles) 4 miles.
So if you find yourself at FL330 and need to descend to 11,000, you’d
better plan on starting a descent when you’re 88 miles from LENDY.
If you don’t know where LENDY is (and therefore have no idea how far
you are from it) you should inform the controller that you are “…unable
to accept a crossing restrictionIn that case, CTR will tell you when to
begin a descent. .”
[You could use your FMS’s DIR.TO
function to tell you how far from you are from any navaid.] 24.0
Once
you start receiving vectors off your planned course (e.g., USA1207 turn right heading 090,
vectors for the approach), you will change altitude and
heading only at the request of ATC (unless they tell you to resume own
navigation again). Sometime ATC will even indicate that you need to adjust
indicated airspeed (e.g., USA1207, maintain 180 knots to the
outer marker….” 25.0
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. 26.0
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! 27.0
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 FS2002, or load/create a new flight plan, refuel, SQUAWK NORMAL and
continue your adventure. 28.0
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. I have not
met a controller yet who wouldn't stop to help a pilot with a question. We were
all there once, and every time I fly I learn something new. Please e-mail
me with any corrections or questions pertaining to this file. 29.0
Just
a note – MSFS2002 has some excellent Flying Lessons contained within the
program itself. They can be
invaluable to the pilot, both novice and experienced. Enjoy
your flight! |
VATSIM Home · User
Agreement · Privacy
Statement
© 2008 VATSIM. All Rights Reserved