intro to ifr vatsim flying - mountain air to ifr vatsim flying v1.0.pdf · intro to ifr vatsim...

Intro to IFR VATSIM FlyingIntro to IFR VATSIM FlyingVersion 1.0 – November 26, 2012

© 2012 Mountain Air Virtual Airlines

Introduction

It is assumed you are familiar with the material presented in the other MTN manuals entitled “Welcome to VATSIM, VFR & IFR” and “Intro to VFR VATSIM Flying” .

Always remember – You are the pilot in command and at all times have the ultimate responsibility for the safety of your aircraft and persons aboard. You are expected to take whatever action necessary whenever needed to insure this safety. Remember these words, “Aviate, Navigate, Communicate; in that order!” In other words, first and foremost fly your aircraft in a safe manner, then insure you are flying the heading and altitude needed, and last but no less important, communicate to ATC or other surrounding aircraft what you are doing.

of 14

A “Step-By-Step” online IFR flight with VATSIM

For this training IFR flight, you are going to use MTN's official flight # 4415, Boise, Idaho (KBOI – Class C airspace) to Seattle, Washington (KSEA – Class B airspace). You will fly this in a B737-800. The flight is 346 nm long and should take about 1.5 hours total. Your cruise altitude will be FL340*. The route is: BOI PDT CHINS7 . Since this is an official MTN flight, the route planning has been done for you and is posted on the MTN website (see MTN's “Pilot Manual” for how to find a flight).

*Note: Altitudes from 0 to 17,999 feet are written and spoken in regular number format. Altitudes of 18,000 feet and above are expressed in “Flight Levels”. For example, an altitude of 24,000 feet would be FL240, 29,000 feet would be FL290, and so on. FL290 would be spoken as, “Flight Level Two Niner Zero”. The number 9 is spoken “Niner” in aviation lingo; other numbers are spoken normally.

1) Round up the appropriate charts to begin planning your flight. You can use http://SkyVector.com to plan this flight. See Figs. 1, 2, 3, and 4 (these charts are also available via the MTN website chart system). You can see from the KBOI and KSEA airport pages on SkyVector, you will be departing from Class C airspace (KBOI) and arriving in Class B airspace (KSEA). You need the airport diagrams so you can follow taxi instructions. (Seattle is one of MTN's hubs and uses gates N1 thru N9 – North Terminal). You need the CHINS7 arrival chart so you can properly fly the approach into KSEA.

Check the weather so you can anticipate which runways you will be using. Assume calm winds for this presentation (you may use other runways, depending on real-time wind directions). Plan on using KBOI runway 28L for departure. Calm wind landing at KSEA is to the south using runway 16C. Have the 16C ILS chart handy in case you cannot do a visual landing. Since you will be flying east to west, your cruise altitude must be an even number, so use FL340.

For the B738 to fly this flight, use the payload assigned by FSX, but use FuelPlan2 ( http://fuel.aerotexas.com/ ) to determine how much fuel you should have on board (see Fig. 5) – 13,662 pounds. Also, a “quick” VATSIM fuel approximation method is: On Board Fuel = (amount of fuel it takes to fly from the departure airport to the destination airport) + (additional reserve fuel for another one hour of flight). You can also dig into real-world fuel planning, but be prepared for a life-time of reading... or you can “kick the tires, fill the tanks, light the engines, and fly the flight”.

of 14

http://skyvector.com/

http://fuel.aerotexas.com/

of 14

Fig. 1: Boise Airport Diagram (KBOI).

of 14

Fig. 2: Seattle Airport Diagram (KSEA).

of 14

Fig. 3: Standard Terminal Arrival Route (STAR) CHINS7 chart for KSEA.

of 14

Fig. 4: KSEA Runway 16C ILS Approach Plate.

of 14

Fig. 5: FuelPlan2 printout for KBOI to KSEA using a B738 aircraft.

2) Start your flight simulator software and your multi-player client software (FSInn or Squawkbox) but do not immediately connect to VATSIM. Make sure your aircraft is positioned at a gate or in a parking area at KBOI airport BEFORE connecting to VATSIM. You do not want to start on an active runway – someone might be landing at the very moment you join VATSIM! Now you are sure you are not parked on a runway or taxiway, connect to VATSIM.

3) Fill out your Flight Plan; see Fig. 6: “KBOI to KSEA Flight Plan (FSInn)” and submit it to VATSIM via FSInn (or Squawkbox). In FSInn, select the “Send to tower” button to send the file.

4) Before you begin to set your COM1 radio to UNICOM 122.80 (remember this is TEXT ONLY frequency) if there is no ATC available, or the appropriate VATSIM ATC frequency to request a Clearance if ATC is available, you are encouraged to read through the typical VATSIM radio communications beginning on page 10.

Who do you initially contact? This can be a little confusing on VATSIM because it depends on what controller positions are staffed and the controllers don't always know the rules (remember, it's a hobby for them too and some are experienced and some are students).

of 14

Fig. 6: KBOI to KSEA Flight Plan (FSInn).

Bring up the FSInn Chat window (or Squawkbox ATC Directory option) to see what ATC controllers are available. The first thing you need to do is request your IFR Clearance from Clearance Delivery at your airport, but the Clearance Delivery controller is rarely available, so you need to start working your way up the list of hierarchy shown in Table 1 below until you hopefully find an ATC controller online in your area. If there are no ATC controllers available, you need to announce your intentions on UNICOM 122.80 as if there were ATC available. Examples are, “KBOI traf. Taxing to 28L”, “KBOI traf. Holding short 28L”, KBOI traf. Departing 28L to the northwest”, “KBOI traf. Clear of 28L”, etc.

Note: Authorities of each position increase and include the previous position's authorities. For example, a Tower controller is authorized to perform their duties, plus perform the duties of a Clearance Delivery controller and Ground controller, but a Ground controller cannot perform the duties of a Tower controller.

Table 1: VATSIM Controller Authorities & ResponsibilitiesPosition Title Authorities & ResponsibilitiesCenter Provides en-route air traffic control on a

regional basis, and can perform all duties, of all positions.

Approach/Departure Controls airspace for departing/arriving aircraft, and can perform all the duties of the Tower, Ground, and Clearance Delivery.

Tower Controls air traffic in the immediate airspace surrounding the airport and runway activity, and can perform all the duties of Ground and Clearance Delivery.

Ground Controls ground movement & can provide clearances.

Clearance Delivery Provides clearances only.

Listen before you transmit. Wait about five seconds before talking to ensure someone else is not in the middle of talking. Be brief. Others are waiting to transmit. There is no need to read back every exacting detail to the controller; get on and get off. This helps avoid radio congestion.

The following is a typical exchange during a flight, but the best way to learn is to listen to other pilots and ATC controllers. Log onto VATSIM and sit at a busy airport like KJFK or KLAX (make sure you are parked at a gate or parking area) and listen to the different ATC controllers and pilots. At first you may become overloaded, but with a little practice you will soon realize that most of the communications are “standard” and you can anticipate what will be said before the words are ever spoken!

of 14

Typical communications with all ATC controller positions staffed:

Action Pilot Controller Comment

Obtain Clearance

"Ground, MTN2071 requesting IFR to Seattle as filed”

"MTN2071, clearance on request, standby"

Initial contact.

no response needed "MTN2071, you are cleared to Seattle vectors to BOI, then as filed. Climb and maintain 5,000, expect 10,000 ten minutes after departure, departure frequency is 118.10, squawk 0425."

He might first say "clearance is available, advise ready to copy." He wants to make sure you are ready to copy.

"Cleared to KSEA, vectors BOI, climb and maintain 5,000, 10,000 in ten, departure control 118.10, and squawk 0425, MTN2071"

"MTN2071, your read back is correct. Push back and start at your discretion is approved, call when ready for taxi."

Remember C-R-A-F-T

Clearance Route

AltitudeFrequency

Transponder

Taxi "Ground, MTN2071 ready for taxi"

"MTN2071, taxi to runway 28L via taxiway Alpha"

This implies you may cross runway 28R on the way to 28L via “A” taxi way, but you are not to enter 28L."Delta to 28L,

MTN2071"

Takeoff "Tower, MTN2071 holding short 28L, ready for departure"

"MTN2071, winds are calm, runway 28L, cleared for takeoff"

GND may hand you off to TWR on the way to 28L, or you might have to call GND first. Either way, don't leave a controller's frequency until he gives you a "contact tower on xxx.xx"

"Clear for takeoff, 28L, MTN2071"

Taxi onto the runway, and takeoff.

of 14

Departure "Tower, MTN2071 is passing 1,000 for 5,000"

"MTN2071, contact approach 124.65, good day"

Tower might hand you off without calling him if he's really on the ball.

"124.65, MTN2071, good day"

Find DEP (more likely APP) and switch to it. Look for the position with the 124.65 frequency.

"Departure, MTN2071 passing 2,000 for 5,000”

"MTN2071, fly direct BOI when able, climb and maintain 6,000”

When checking in, always give the controller your present altitude, and if climbing or descending, your target altitude.

"direct BOI, up to 6,000, MTN2071"

Cruise "MTN2071, contact Salt Lake Center on 132.60, good day"

Depending on the route of flight, distance and altitudes, you will be handed off to whatever controller is managing the airspace you are about to enter. Who that is, depends on what controllers are online.

"132.60, MTN2071, good day"

Now find Salt Lake Center with the 132.60 frequency.

"Salt Lake Center, good afternoon, MTN2071 with you at 6,000"

"MTN2071, Salt Lake Center. Radar contact. Continue as filed."

Descent and approach

"MTN2071, contact Seattle Approach on 125.4, good day"

"125.40, MTN2071, good day"

Switch to Seattle Approach.

"Approach, Good afternoon, MTN2071 with you 6,000"

"MTN2071, Seattle Approach. Turn left 300, vectors for the ILS 16C, descend and maintain 4,000."

Now you know you'll be flying the ILS for runway 16C.

of 14

"Left 300, down to 4,000, MTN2071"

"MTN2071, turn left 250, descend and maintain 2,000"

He's turning you to a base leg

"Left 250 and 2,000, MTN2071"

"MTN2071, you are 8 miles from KSEA, turn left 200 to join the localizer, maintain 2,000 until established, cleared ILS 16C approach"

You may descend below 2,000 per the approach once established on the final approach course (the localizer).

"Left 200, 2,000 until established, cleared for the approach, MTN2071"

"MTN2071, contact the tower 119.70, good day"

"119.70, MTN2071, Good day"

Landing "Tower, MTN2071, 5 miles out for runway 16C"

"MTN2071, Seattle Tower. Winds are calm, runway 16C, clear to land."

"Clear to land, MTN2071"

On the ground, Tower might tell you to "take next taxiway to the left, contact ground" or you might call him "clear of the active" once you are clear of the runway.

"MTN2071 is clear of runway 16C"

"MTN2071, taxi to parking" On the ground, Tower might tell you to "take next taxiway to the left, contact ground" or you might call him "clear of the active" once you are clear of the runway.

"To the ramp, MTN2071"

Once at the gate or parking, it's not necessary to call ground or tower, but some VATSIM controllers seem to like that.

of 14

"MTN2071 at the gate shutting down, thanks for the ATC, good day"

"MTN2071, flight plan closed, have a good day"

5) If there is no ATC online, set your Transponder to 2200 (this is the standard VATSIM IFR Transponder code) and leave it in the “Standby” mode. If you have received a Clearance from ATC, set your Transponder Code and Mode per ATC instructions.

6) Set your altimeter.

7) Complete your aircraft pre-flight checks and prepare the aircraft for engine start and taxi.

8) Check parking brake, turn on Beacon and NAV lights; start engine and prepare for taxi and takeoff.

9) Push back from the gate and contact Ground for taxi permission. If there is no ATC online, announce on UNICOM (text only) you are taxing to KBOI runway 28L.

10) Taxi to the runway and hold short of the runway.

Note: You may be given instructions to “Line up and wait”. This is giving you permission to pull onto the runway and line up with the center line, and then sit and wait for further take off clearance.

11) When given take off clearance, acknowledge the clearance, turn on Strobes, Landing Lights, Transponder, enter the runway, and take off! If there is no ATC, announce intentions on UNICOM.

12) Enjoy the flight and fly your approved flight plan route, following ATC instructions. Remember, if there is no ATC available, but other aircraft are in your area, fly the flight plan you filed and announce your intentions on UNICOM (text only) as if ATC were online.

Help-Tip: If there is no ATC online and you don't have any on board flight computer equipment to tell you when to begin your descent into your destination, you can use what is called the “Rule of 3s” as general guidance.

Example: You are cruising towards KSEA at FL340 and want to be at 16,000 when you cross the intersection called RADDY (per CHINS7 arrival chart). This is an altitude change of 18,000 feet; drop the last “3” digits of the amount of change, so you now have “18”; multiple the “18” by the number “3”, giving you “48”; this means you will want to begin your descent about 48 nm (nautical miles) or more before RADDY.

13) Once parked and shutdown at the gate, you can disconnect from VATSIM.

14) Just like VFR, your flight is not over until the paperwork is filed. To log your flight at MTN, you have two different methods available; manually or using the FSAcars system. It is recommended you manually file your PIREPS while first learning. See MTN's “Pilot Manual” on how to file your PIREP

of 14

manually (Pilot's Report). While you have completed this online IFR flight with VATSIM, there is much more a pilot can learn about IFR flying!

You are encouraged to read the training materials for IFR flying with VATSIM at:

http://www.vatsim.net/prc/prc-ifrspec/

Odds & Ends

Other MTN help: There are several ways to obtain help at MTN; visit the MTN website and visit the Training page; log into the Forum and post questions; join the Group Flights and get online-on-the-spot-help from other MTN pilots (this is the most fun way!!!), and/or contact MTN's Training Manager by emailing:

[email protected] .

VatSpy: This is a freeware program that allows you to look real-time at what is going on with VATSIM ATC and other online pilots. For example, you can see what VATSIM servers have the quickest ping time to your location, which ATC controllers are online, what airport arrival/departure flights are scheduled, details of individual pilots and their flights, radio frequencies of online ATC, etc. You can download this freeware from: http://www1.metacraft.com/VATSpy/ .

Vataware: This is an interesting website that provides statistics of VATSIM flight activity. After you have logged a few flights on VATSIM, go to this site and enter your own MTN callsign to see your own flight information. Explore the site and enjoy! The URL address is: http://www.vataware.com/ .

of 14

http://www.vataware.com/

http://www1.metacraft.com/VATSpy/

mailto:[email protected]

http://www.vatsim.net/prc/prc-ifrspec/

intro to ifr vatsim flying - mountain air to ifr vatsim flying v1.0.pdf · intro to ifr vatsim...

Documents