曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
IMPORTANT NOTE - Ctrl-Shift-M calls for your co-pilot to take over the controls. This command will not work prior to Departure airspace. You are welcome to take advantage of this feature now, or at anytime throughout the flight, all the way to “cleared to land”. Your co-pilot will not make speed/gear/flap adjustments, nor other-than-default FS VAS inputs. If the co-pilot is flying, attempts to change heading or altitude settings, will be reset to the assigned heading and altitude by the co-pilot.
Chicago Center
Eventually Departure will have you contact Chicago Center, who tells you to “resume own navigation”. You see CID is well within reception range. Use VOR1 and/or your FS GPS to proceed direct.
Remember, RC‟s checkpoint heading information on the Menu Display is no wind. The indicated heading will not necessarily be that which you need to fly. Make course corrections per wind as necessary. Notice also, checkpoint #2, DBQ (view VOR2) is within reception range. Though you have the ability to request direct DBQ (Press 9, 1, 1), we will stay on course for now. Center issues assigned altitudes upon initial contact. The altitude may be to the upper limits of this controller‟s stratum (LOW) or an interim altitude if you have crossing traffic. Having filed FL290 for cruise altitude, you will eventually be switched to the HIGH Center controller who takes you to FL290. While below the PCA (FL180), press “B” periodically to ensure your altimeter setting is current. Climbing through FL180, be sure to reset the altimeter to standard pressure (29.92). Your co-pilot calls “altimeter check” passing through FL180 as a reminder.
Radar Contact Tutorials
Version 4 December 2, 2007
Copyright JDT LLC 2005 Page 146
During this flight you will be switched to a new Chicago center controller, because you have crossed a sector boundary. You make the switch to the new controller, he will acknowledge you. No new altitudes will be assigned. Moments later you will be told to contact another Chicago center controller. When you make this switch, this is a stratum switch, and you will be assigned your cruise altitude of FL290.
Approaching CID remember, the enroute checkpoint tolerance window is 5 miles in RC. You must pass within 5 miles of CID for credit. Having left the Chkpt Ding checkbox at default on the General Options Tab, you will know you have gotten credit as the wav file plays. You should be level at FL290 within 20 miles either side of CID.
Also, notice that the checkpoint after your next checkpoint is being automatically displayed once you are within 15 miles of the next checkpoint.
As you pass over CID, use Ctrl-Shift-L to auto-set your Nav radio(s) again. Notice, the DBQ frequency is set in Nav 1, but Nav 2 hasn‟t changed. This indicates the checkpoint after DBQ is a waypoint or fix (a checkpoint without a frequency). Press Ctrl-Shift-P at this time. Sure enough, BRIBE (an intersection) follows DBQ.
You have several options. Fly via your Nav 1 only. If you wish, locate the next frequency to be used on your flight plan display and enter that frequency manually in Nav 2. In this case it‟s JVL‟s frequency of 114.30. Or, you could set and leave your destination‟s VOR frequency in Nav 2. This helps in determining when to expect descents and crossing restrictions. You have every option here. IMPORTANT NOTE - Use the Menu Display for general no-wind heading information and the FS GPS for precise navigation to checkpoints without frequencies. Your co-pilot does all this for you if he/she is at the controls. At 45 miles from DBQ, let‟s see if the controller is sleeping. If the co-pilot is flying, take the plane back by pressing Ctrl-Shift-M. Climb to FL294. The controller has a word with you, does he not? Return to FL290. With DBQ bearing approximately 055°, turn left to 025°. Again, the controller has something to say about this. Turn direct DBQ, pause the sim and let‟s talk about this for a moment.
Make RC as tolerant as you like by adjusting the Deviations settings under Heading, Altitude, and Speed on the General Options Tab. The higher the value, the more forgiving your RC controller will become. Enter 100 in Altitude for instance (300 default), and you would have been scolded sooner. Enter 25 in Heading (15 default), and the controller will not be so quick to call your hand at straying off course. In time and after several flights, you will know what numbers suit your needs.
Radar Contact Tutorials
Version 4 December 2, 2007
Copyright JDT LLC 2005 Page 147
There will be times when deviating from a flight path is necessary (thunderstorms), or due to chop/turbulence you cannot hold your assigned altitude. Pressing 9 displays menu page 2, where you will find “Dev for Wx” and ”Dev for Turbulence”. When necessary, select these options to state your needs.
IMPORTANT NOTE - The RC controller will always deny wx deviation requests when within 25 miles of a checkpoint. If you are close to a checkpoint and must deviate, request direct the following checkpoint before making the deviation request. Also, if deviation has been approved, once you come within 35 miles of your next checkpoint, the RC controller required you to return to on course. Again, if this is not possible, request direct the following checkpoint, then request to deviate again.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
Radar Contact(51)
