Home | Company Info | Products | News | Documentation | FAQ | Contact

KPIE-KPIE Tutorials



Your fifth flight demonstrates fully controlled fields, all controllers available.  We’ll look at:

  • Fully controlled fields
  • Entering Alternate Airport(s)
  • Specifying D&A runways
  • The Round Robin
  • Flex DP
  • The co-pilot on radios and aircraft controls
  • Save/Load
  • Requesting higher/lower altitudes
  • Request direct filed waypoint/fix
  • Pause at Distance
  • PD clearances/crossing restrictions

The Plan

  • 324 miles, tprop (FS King Air), 130


  • Alternate Airport 1 - KRSW

Launch FS and position your aircraft at KPIE.  Start RC. Click the FS200x (*.pln) button, and choose the V4 5 KPIE-KPIE.pln.

Controller Info

Type KRSW under Alternate 1 and click Find.  Set rwy 09 for the KPIE departure rwy.  Do not specify a KPIE arrival rwy.  Enter 130 for cruise altitude.  Choose Dep Procedure / Alt Restrictions box. 

Click OK.

General Options

Use King Air 72rc for this flight’s call sign, and select Turbo Prop for type aircraft.  Leave the three Deviations settings at default.  Along the right column we want Display Text and Pilot Autoreply unchecked.  Set Interact with AI, Play Pilot Wavs, Chkpt Ding, and Tune on Contact checked.  Also, check Pause at Distance entering 120 in it’s box.  Enter 3 Souls on Board. Let’s make sure we aren’t held on this flight, so select OFF in the Holding box.

Click OK. On RC’s main Page click Start RC.

Maximize FS and Preflight

Load the V4 5 KPIE-KPIE.pln into your FS GPS.  Flights/Flight Planner/Load, choose V4 5 KPIE-KPIE.pln, click OK, and again OK. Place the FS GPS in the desired location on your panel.

Round Robin

A round robin simply means, you depart from and return to the same airport.  You saw a (somewhat complicated) way of doing this in tutorial #4.  You can also “plan” such a flight, as we did here.  Set checkpoints along any route you wish to fly.  A Round Robin in RC is not VFR.  You need to fly the filed route and get credit for every filed checkpoint.

Yet another way of “fooling” RC into a Round Robin flight is of course, making use of the Change of Destination feature.  This is available nearly all the time while on a Center frequency.

Finally, you can “plan” a sort of broken Round Robin.  Such is displayed in tutorials 6, 7 and 8 where you’ll depart from an airport, and end up back at that airport with intermediate stops.

Pre-Planning and Departure Procedure

Our first filed checkpoint is OCF VOR (113.70) as seen on the AdvDisp.  We could allow the Departure controller to vector us towards OCF, but prefer to join a radial outbound until receiving.  That’s why we enabled Departure Procedures with Altitude restrictions.

We’ll depart on Rwy 09, and turn to join the PIE (116.40) 019° outbound.  Had there not been a VOR on the KPIE airport grounds, we could takeoff then turn to a heading to join an outbound radial from a nearby VOR.  It all works using Flex DP.

Set PIE VOR (116.40) in Nav1 and dial 019° in the OBS.  Set 113.70 in Nav2.

Having enabled Departure Procedure with Altitude Restrictions:

  • Tower will not assign specific takeoff instructions
  • Departure will not assign headings
  • The co-pilot will accept the aircraft controls in a DP, but will turn direct your 1st filed checkpoint.  This may not be what you’d like to see. 
  • Your flight path will not be critiqued until beginning at 30 miles from KTPA

IMPORTANT NOTE - Joining a radial outbound is an alternate benefit of Departure Procedure.  Its intended purpose is to serve those flight plans, where a published DP has several transitions depending on what runway is in use.  Those transitions all meet at a common checkpoint that’s outside 30 miles of the departure airport.  Since the Departure controller won’t assign headings, you’re able to takeoff any assigned runway and follow the route of the DP pertinent to specific runways, to the common checkpoint.  You file the common checkpoint as your first checkpoint.

St. Petersburg ATIS

We’re in a King Air and don’t need Push/Start.  Give the radios to the co-pilot.  The co-pilot tunes ATIS




St. Petersburg Clearance Delivery

The co-pilot calls Delivery for the Round Robin clearance (setting the altitude/transponder code for you)




St. Petersburg Ground

The co-pilot then requests taxi to Rwy 09 from Ground.

We specified Rwy 09 on the Controller Tab, but could have achieved the same results by requesting Rwy 09 when we talk to the Ground controller at KPIE.  The use of Rwy 09 in this tutorial is for illustration purposes only.

While taxiing to the runway, prep the aircraft for takeoff (flaps, trim, AP preset speeds & heading selections, etc).  Be well into those checklists by now. 




St. Petersburg Tower

When near the end, Ground will tell you to contact Tower.  The co-pilot switches frequencies and contacts tower.


After contacting tower, he will acknowledge you, and you should continue to taxi to the end of the runway.


When you are close to the hold short line, you will be told one of two things, depending on what the AI are doing.

  • Taxi into position and Hold – no AI taking off on your runway, no AI landing on your runway, and no AI in front of you
  • Hold Short – Either and AI is taking off on your runway, or an AI is on short final on your runway.

If you’re told to hold short, keep monitoring tower until it’s your turn. When it is time, you will be told to taxi into position and hold.

Once you are lined up on the runway, Tower will clear you for takeoff.

This is a Departure Procedure with Altitude Restrictions flight.  Your takeoff clearance will not include “fly rwy heading” or “fly heading”, just “…cleared for takeoff”.  Airborne, retract the gear, accelerate, and clean up the aircraft. 

St. Petersburg Departure

The co-pilot calls the Departure controller when told to do so. 

Though we can at anytime turn to join the PIE 019°, fly heading 090° (runway heading) for 5 miles.  Reference your Nav1 dme for distance information.  After a bit of sightseeing over the bay, fly heading 350° and join the outbound radial.


You can give the radios to the co-pilot as early as before listening to ATIS, but you must be on Departure’s frequency before he/she will accept the aircraft controls.  Remember though, the co-pilot will turn towards OCF.  Do not give the aircraft to the co-pilot.

Notice, Nav2 isn’t displaying OCF reception yet.  The benefit of joining an outbound radial should be obvious.  Departure Procedures allows for that.  Fly wind-corrected headings as necessary to remain established on the PIE 019°.

At 20 miles PIE, OCF lights up Nav2; straight ahead at 58 miles.  Press Ctrl-Shift-L now to reset your Nav radios.  You see OMN (checkpoint #2, Ormond Beach FL) is within reception range, bearing 050° at 100 miles.  Let’s plan to request direct OMN and a higher altitude as soon as we contact Center.



IMPORTANT NOTE -  At anytime during any flight, use Ctrl-Shift-P to view your flight plan. Press 0 (Home) returns you to the AdvDisp main screen, page 1.

Jacksonville Center

At Departure’s boundary, you’re switched to Jacksonville Center.  Press 4 – Req Higher




Have the co-pilot first request FL210 by pressing 9 to get to the second page, and then 3 - 21000.  You may be climbed to an intermediate altitude of 15000.  Approaching 15000, you will receive further clearance to FL 180 or FL210.


Press 9 to go to page 2, where Dir Ckpt menu item is.





Press 1 to request Direct Checkpoint. 




Then request direct <OMN>70m/11260 by pressing 1.  The display shows that OMN is 70 miles away, and has a frequency of 112.60.  If the controller doesn’t approve the request, wait a few minutes and make the request again.  You can set up the next couple of Navaids by pressing Ctrl-Shift-L.  Give the aircraft controls to the co-pilot (optional).  Sit back and enjoy Florida!


About 19 miles from OMN, you will be switched to a different Jacksonville center controller




At 50 miles north MLB, pause the sim.  Save Flight, and enter “tut5 1 50 miles MLB FL210” (no quotes).  Use this file at to experiment with the various RC options.  Look at Change of Destination, Emergencies, Dev for Wx/Turb, etc. anything you’re not clear on, or would like to see from an angle not covered in the tutorials.  As always, our forum is at www.avsim.com for individual help.


Unpause the sim and continue the tutorial.

Miami Center

About 17 miles from MLB, you will be switched to Miami Center.





About 10 miles before MLB, Flight Simulator, pauses.  Remember, we’ve enabled Pause at Distance on the General Options Tab.  You’re 120 flying miles from KPIE.  Consider this feature in your flight planning, especially those long cross countries or over-the-ocean flights where staying with the sim the entire way might be impractical.  To continue simply unpause.


Time to Start Down

About 48 miles from LAL, Center issues the “PD/expect” clearance.  The “expect” altitude was 8000 (or 9000 if it is a farside runway), not 11000 or 12000 as we’ve seen so far.  This is because your type aircraft is a Turbo Prop.  Props would “expect” 5000 or 6000 (if it is a farside runway). 


You’re at FL210 with PD (altitude) knowing you’ll have to be at 8000 or 9000 at or before you’re 40 miles from PIE.  If you have the aircraft controls, make the “time to descend” decision.  If the co-pilot is driving, you have the VAS.  If the co-pilot is talking, you’re going to buy the restriction.

About 30 miles from LAL, you will receive the crossing restriction, “King Air 72rc, cross four zero miles from PIE at 8000.  Altimeter xxxx”.


You will have another Miami center switch to a new controller about 26 miles from LAL.


IMPORTANT NOTE - You don’t have to wait for a crossing restriction to descend below your PD altitude.  Req Lower will always be available in this phase of RC flights.

St. Petersburg Approach

At 4 miles from LAL, and 40 miles KPIE, you will be asked to contact Approach, who will welcome you and advise which approach to expect.  Pause the sim, Save Flight and enter “tut5 2 KPIE Approach (early)” (no quotes) and click OK.  Return to this file at a convenient time, practicing the various options: Short Final, Alternate Rwys, post-Missed Approach issues, etc.


Unpause.  Give the aircraft to the co-pilot and allow him/her to fly us onto final.  You handle the radios in Approach airspace.  Otto will not execute the controller’s clearances, until you’ve acknowledged that clearance.  Remember, you have the IAS, VAS, flaps and gear to watch after.

St. Petersburg Tower

On short final and with “…cleared to land…”, you’ll take the aircraft controls. 




St. Petersburg Ground

After touchdown, slow and contact Ground.  Taxi to your gate.  All post flight and shutdown checklist completed, set your parking brakes and choose between Flight Critique for a flight synopsis, or End RC to close the program.



Questions or comments?  Your RC staff and veteran users are ready to help.  The RC forum is at RC Support Forum.  There are always several RC users there, eager to assist.  Thank you for using RC!



JDT LLC © 2005 | All Rights Reserved | Contact

Template by
Round the Bend Wizards