曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

Radar Contact Radar Contact User Interface
Version 4 December 2, 2007
Copyright JDT LLC 2005 Page 107
MSA
This box will be filled in with the approximate MSA for the airport. There if you know the MSA at this airport is higher than what is provided, you can change it. This field determines the lowest possible altitude you will be assigned during departure and approach.
Departure Procedures
By definition, Departure Procedures (DPs) are published routes, with or without altitude restrictions, flown after takeoff. DP lengths vary depending on your departure airport. They might end at a point from 30 miles away, they might end at a point 100 miles away. This essentially is the first part of your flight plan, which guides you away from the airport. The purpose(s) of DPs include noise abatement, routing around restricted or prohibited areas, moving heavy volumes of departing traffic away from populated areas, transitions to common fixes for enroute, etc. Beyond filing a realistic route with appropriate procedures, there is a further purpose to filing a DP in RC. You wish to takeoff, but rather than be vectored towards your first checkpoint, you prefer to join an outbound radial from a VOR (in other words, pick up an airway). DPs allow for this. First, determine whether you want to fly a Departure Procedure. In effect, this means that RC‟s controllers will not vector you in the first 30 nautical miles of your flight plan, which leaves you free to fly a DP route. Departure Procedures are implemented in RC in several ways.
Filing a DP
RC sees filing your first checkpoint within 30 miles of the departure airport, as a DP. This form of DP will default to “Alt Restrictions” being checked (you have the option to change this, discussed below). You will notice, “No Dep Proc” is grayed out in the Dep Procedures column on the Controller Info. Leave default “Alt Restrictions”, or change to “No Altitude Restr” as needed.
Forcing a DP
If your first checkpoint is further than 30 miles from your departure field, RC defaults to “No Dep Proc” being checked in the Dep Procedures column on the Controller Info.
Radar Contact Radar Contact User Interface
Version 4 December 2, 2007
Copyright JDT LLC 2005 Page 108
Here you choose whether to check either “No Altitude Restr” or “Alt Restrictions”.
or This option allows you to file your first checkpoint outside 30 miles, but enables you to fly a necessary routing as long as you are within a 30 nm radius from the airport. That is perfect for those filing DPs, and intending to join an outbound radial. IMPORTANT NOTE – The “No Altitude Restr” and “Alt Restriction” buttons are available, regardless of distance of first checkpoint. Both constitute a DP, and RC will handle accordingly.
No Altitude Restr
Clearance Delivery will assign an initial altitude, and Departure will keep you climbing. However, some published DPs include altitude restrictions. They may be AOA (at or above), AT, or AOB (at or below) altitude instructions. If you see your DP might cause you to remain level at an altitude for some period or until a certain DME, this is the DP feature to use. Use this checkbox if you do not want the RC controller pestering you for not maintaining a continuous rate of climb to your assigned altitude. There will be no lateral “watch-dogging”, there will be no vertical “watch-dogging” from RC until you are at or beyond 30 miles from the departure field.
Alt Restrictions
By far, most DPs are of published routes without any altitude restraints. If your DP contains lateral routes but no altitude instructions, or if you simply wish to join an airway outbound, this is the way to go. Again, Clearance Delivery will assign an initial altitude, and Departure will keep you climbing but in this case, you need adhere to those altitude clearances. Keep it climbing to assigned, do not level off. Some Creative Thoughts
 Very often DPs are runway dependent. Problem: Logic says you do not know which DP to file prior to learning what runway Ground will put you on.
No problem! So long as what DPs available to you have a common fix (the routes to that common fix are different), and you have filed that common fix, no problem at all. In such cases, file your flight plan(s) to include the common fix only. Do not file
Radar Contact Radar Contact User Interface
Version 4 December 2, 2007
Copyright JDT LLC 2005 Page 109
intersections or fixes between the departure airport and the common fix. RC will look for you to be headed towards the common fix no later than 30 miles out, regardless of which runway you used for takeoff.
 You have filed your flight plan prior to a line of thunderstorms passing over. Your initial filing had a dep runway with no associated departure procedure. However, once you actually fired up FS and get "in the cockpit", the winds changed and the runway assigned does in fact have a dep procedure.
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：Radar Contact(39)