1 / 58

ATCoach  Tactical Edition PAR Simulator (APARS) DATA MANAGEMENT: ATCOACH FILES PART TWO

ATCoach  Tactical Edition PAR Simulator (APARS) DATA MANAGEMENT: ATCOACH FILES PART TWO Site File CLS2004.A.0-004.2. Site File Intro. Site Data File. (*.st). (UM Section 4.2.2 & Chapter 6).

mura
Download Presentation

ATCoach  Tactical Edition PAR Simulator (APARS) DATA MANAGEMENT: ATCOACH FILES PART TWO

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATCoach Tactical Edition PAR Simulator • (APARS) • DATA MANAGEMENT: • ATCOACH FILES • PART TWO • Site File • CLS2004.A.0-004.2

  2. Site File Intro • Site Data File. (*.st) (UM Section 4.2.2 & Chapter 6) • The Site File defines the airspace used in an exercise including; arrival and departure routes, flight profiles, and fixes that are not graphically depicted. • The site file also defines the runway, antenna, glidepath and safety cursor data. • The site file may contain data for video mapping, but this capability is not applicable to a PAR only system.

  3. The site file is displayed. Site File • Site Data File. (*.st) Note: (UM Section 6.3) Many of the following Site Files entries rely on latitude/longitude coordinates, especially when plotting fixes and other points. ATCoach provides several utilities to assist the developer in site development. The following commands were designed exclusively for this purpose: CSCAN0 & CSCAN4 COO & COC (UM Section 4.2.2 & Chapter 6) • To open the Sites editor: • Click on the Sites option on the Workspace menu. • The File Manager opens to the top level directory for sites: /space/atcoach/sites. • Double click with the left mouse button on the desired .st file.

  4. Site File • Site Data File. Requirements, formats, and explanation of terms. • The following presentation includes all site file formats and entries (in no particular order). • Site file names can contain a maximum of twenty-nine alphanumeric characters, including the extension. • Site file items can be entered in any sequence and there is no limit to the number of site file items that can be entered. • There are four items that are mandatory for a Site file: • Site Name (NS), • Major Airport (MA), • Antenna (AN). • Runway (RW). • All other items are optional. Note: To provide maximum compatibility with existing and future simulated radar systems, some entries, although still required to be entered in the site file, are actually overridden by the data file created for that particular radar model (for example: gpn22.dat). For those instances that this occurs, it will be so noted • Data Format Symbols: • Mandatory data (< >). • Optional data ([ ]). • Space is required (_).

  5. Site FileNS • Site Name (NS) - (UM Section 6.5) • The site name entry depicts the site name by a three-letter or four-letter identifier that is usually the major airport for which the site is created. • The NS entry is a mandatory entry in the site file. • Format NS_<name> • <name> Is a 3 or 4 character identifier for the site. • EXAMPLES NS GSB Seymour-Johnson site.

  6. Site File HM • Hemisphere (HM) - (UM Section 6.6) • The hemisphere entry defines the hemisphere that the airspace is situated in. ATCoach defaults to the Northwest hemisphere. If a different hemisphere is desired, the choices are Northwest, Northeast, Southeast, and Southwest. • Format HM_<hemisphere> • <hemisphere> Is NW, NE, SW, or SE. • EXAMPLES HM NW ATCoach default hemisphere. Note: Hemisphere coordinate entries cannot be mixed. For example, within a site file, you could not have Northeast and Northwest entries.

  7. Site File AN • Antenna (AN) - (UM Section 6.7) • The antenna (AN) entry defines the center reference point of the airspace and the characteristics of the azimuth and elevation antennas. • The AN entry is mandatory in the site file. • The following assumptions are made regarding the radar antenna. • There are no equipment siting limits for display resolution, system accuracy, and mechanical limits except for elevation’s and azimuth’s fields of view. • There are no obstructions to the line of sight except for non-radar areas. • The radar set can only service the approach end of the runway, not in both directions. • The radar set can service up to four runways per site. • There can only be one radar set per site file. • The corresponding calm wind runway name must be defined in the site file via the RW entry. • Format AN_<radar type>_<airport name>_<runway name >_<magnetic variation>_<azimuth antenna scan rate>_<elevation antenna scan rate>_ <overscan>_ <elevation scan mode>_<offset distance>_ <distance to touch down position>_ <elevation ground angle>_<tilt angle>_<servo angle>_<scan angle offset>_<distance to RPL target reflector>_<bracket reflector offset distance_<cone of silence>_<antenna orientation> • <distance to touch down position> Distance along the runway centerline from the touch down position to the radar set. • <runway name > Name (number) of runway configured for ASR and PAR approaches. • <magnetic variation> Magnetic variation for the site. A minus symbol (-) is required for easterly variations whereas the plus symbol is assumed for westerly variations. • <azimuth antenna scan rate> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than 0. • <elevation antenna scan rate> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than 0. • <overscan> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than or equal to 0. • <scan mode> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be one of the following six options; BI-DIRECTIONAL, LOOK- GOING-UP, LOOK-GOING-DOWN, BI-DIRECTIONAL- LOCK, LOOK-GOING-UP-LOCK, LOOK-GOING- DOWN-LOCK. • EXAMPLE AN ANGPN-22 GSB 26 00 01 01 00 LOOK-GOING-UP 400 4550 107 5 0 0 4550 75 4.8 R • <servo angle> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than or equal to 0. • <scan angle offset> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than or equal to 0. • <distance to RPL target reflector> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than or equal to 0. • <bracketing reflector offset distance> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than or equal to 75. • <cone of silence> Specifies inclination angle and the cone of silence on the azimuth antenna in degrees. (1 to 90 deg). • <threshold elevation> Elevation at the runway threshold in MSL. • <orientation> Left or Right of runway orientation of the radar antenna based upon pilot’s perspective. (L or R) • <offset distance> Perpendicular distance from the radar set to the runway centerline. • <tilt angle> The gpn-22.dat file overrides this setting. The entry is still required, & the value must be greater than or equal to 0. • <airport name > Three or four letter identifier for the airport. • <radar type > Nomenclature of the radar in use at the airport.

  8. Site File DR • Drop Range (DR) - (UM Section 6.8) • The drop range designates the distance from the antenna where ATCoach no longer updates an aircraft and drops it from the radar display and Instructor position. • Format DR_<range> • <range> Is the distance from the antenna (AN) in nautical miles. • EXAMPLE DR 80

  9. Site File DR • Clutter (CLUTTER) - (UM Section 6.9) • The clutter (CLUTTER) entry defines permanent echoes from ground clutter. Clutter is defined by a lat/lon location, and the elevation and diameter of the object. • NOTE: Clutter is displayed as raw radar video; subsequently it is not visible on the supervisor display. • Format CLUTTER <latlon>_<top elevation> <diameter> • <latlon> Latitude and longitude location of clutter’s center mass. • < top elevation> Height of clutter in thousands of feet. • <diameter> Diameter of object in hundreds of feet. • EXAMPLE CLUTTER 35 21 09 77 52 47 1000 400 • The example above defines a 1000ft tall object (silo) that's 400 feet across.

  10. Site File NR • Non-radar areas (NR) - (UM Section 6.10) • Non-radar areas are three-dimensional blocks of airspace that do not have radar coverage. • Format NR_<base altitude>_<ceiling altitude>_<azimuth 1>_<azimuth 2>_<range 1>_<range 2> • <base altitude> Lower (base) altitude in hundreds of feet. • <ceiling altitude> Upper (ceiling) altitude in hundreds of feet. • <azimuth 1> First boundary radial from the antenna. • <azimuth 2> Second boundary radial from the antenna. • <range 1> Inner boundary distance from the antenna in nautical miles. • <range 2> Outer boundary distance from the antenna in nautical miles. • EXAMPLE NR 000 100 200 300 10 20 • The example above defines a non-radar area from surface to 10,000 ft. between the 200 and 300-degree radials from 10 to 20 miles from the antenna location.

  11. Site File BN • NAVAIDS & Fixes (UM Section 6.11.1) • NDBs (BN) • Non-Directional Beacons are used for navigational purposes and in conjunction with other navigational aids to specify a route. • Format BN_<name>_<latlon> • <name> Up to Five letter name for the NDB. • <latlon> Latitude and longitude location of the NDB. BN ETP 31 20 11 85 57 39 • EXAMPLE

  12. Site File VR • NAVAIDS & Fixes (UM Section 6.11.2) • NAVAIDS - VORs (VR) • Very High Frequency Omni-Range or VORs. • Format VR_<name>_<latlon>_<dmequip> • <name> Three letter identifier of the VOR. • <latlon> Latitude and longitude location of the VOR. • <dmequip> The number 1 or 2 to indicate DME. A 1 indicates DME, and a 2 indicates no DME. • EXAMPLE VR DHN 31 17 52 85 24 41 1 (DME equipped).

  13. Site File PT • NAVAIDS & Fixes (UM Section 6.11.3) • Points In Space (PT) • Points in space are imaginary points that may be navigated by aircraft. • Format PT_<name>_<latlon> • <name> Three to nine character name of the point. • <latlon> Latitude and longitude location of the point. • EXAMPLE PT TP1 31 29 06 85 41 55 First point for traffic pattern.

  14. Site File VP • NAVAIDS & Fixes (UM Section 6.11.4) • Visual Reporting Points (VP) • Visual reporting points are specified locations in relation to which the position of an aircraft can be reported. • Format VP_<name>_<latlon> • <name> Five character name for the point. • <latlon> Latitude and longitude location of the point. • EXAMPLE VP ETP 31 20 11 85 57 39

  15. Site File MA • NAVAIDS & Fixes (UM Section 6.11.5) • Major Airport (MA) • Major Airport is the host facility. • Format MA_<name>_<latlon> • <name> Three character identifier of the airport. • <latlon> Latitude and longitude location of the airport. • EXAMPLES MA GSB 35 20 19 77 57 19

  16. Site File RW • PAR Runway Definition (RW) - (UM Section 6.12.1) • The PAR Runway Definition (RW) defines a runway that can be used for instrument approaches and departures. • The RW entry is mandatory in the site file. • An optional entry allows for the runway extended centerline to be drawn. If this option is desired, the starting point of the extended centerline distance and the end point of the extended centerline distance must also be defined. • Format RW_<runway name>_<airport name>_<elevation>_<threshold latlon>_ <touchdown point >_<takeoff offset point>_<runway direction>_<runway length>_<runway width>_<glidepath angle>_ <decision height>_ <safety limits offset>_<asr dec dist>_<asr alt>_<alt var>_<width var>_<range limits>_<centerline Y | N> • <runway name> Name (number) of the runway as defined. • <airport name> Three letter identifier of the airport the runway serves. • <elevation> Runway elevation at the touchdown position in MSL. • <threshold latlon> Latitude and longitude location of the runway threshold. • <touchdown point> Distance in feet from the runway threshold. • <takeoff offset point> Distance from the runway threshold that an aircraft will begin the takeoff procedure in feet. • <runway direction> Approach direction to the runway in degrees. • <runway length> Runway length in feet. • EXAMPLE • <runway width> Runway width in feet. • <glidepath angle> Specifies the glide path angle for the elevation cursor measured in degrees. (1 to 7 degrees). • <alt var> The variation in feet +/- (plus or minus) from the <asr alt> and <par alt> that is defined. • <decision height> Altitude in feet MSL. • <safety limit offset> Negative decimal value relative to the PAR glide path. Sets the angle of the lower safety cursor. • <width variation> The lateral distance in feet from the edge of the runway that define the width an aircraft must be within to complete an approach. • NOTE: If the altitude or width variations are exceeded at the decision points for the ASR or PAR, the aircraft will execute a missed approach. • <range limits> The plus or minus (+/-) distances used in reference to the ASR/PAR decision points, entered in feet • <centerline Y | N> This is not viewable on the on a PAR display. Entry is still required, but N is the only supported entry. • <asr dec dist> Distance in feet from runway threshold where the decision is made to complete the approach or execute a missed approach. • <asr alt> The MDA for the ASR approach in feet. RW 26 GSB 107 35 20 25 77 56 13 940 11700 260 11758 300 3.0 210 -0.5 6080 680 500 500 3040 N RW 08 GSB 072 35 20 05 77 58 46 1010 11700 080 11758 300 3.0 174 -0.5 6080 680 500 500 3040 N

  17. Site File DP • Departure Profile (DP) - (UM Section 6.12.2) • The Departure Profile is the initial heading and altitude that aircraft are assigned for departure. This is normally the runway heading as defined in the RW entry. • If there is a restricted or prohibited area off the departure end of runway that would preclude the use of the RW heading, a force (F) procedure may be used to specify a heading other than the runway heading. • A separate DP entry is required for each runway. • Format DP_<airport/rwy name>_<climbing alt for props>_<climbing alt for jets>_< heading for props [F]>_<heading for jets [F]>_<speed for props>_<speed for jets> • <airport/rwy name> Airport/runway name previously defined in the RW entry. • <climbing alt for props> Initial altitude prop type aircraft will climb to in thousands of feet. (i.e. 4 digits for 2200 not 022) • <climbing alt for jets> Initial altitude jet type aircraft will climb to in thousands of feet. (i.e. 4 digits for 2000 not 020) • <heading for props> Initial or forced heading for props on departure in three digits. • <heading for jets> Initial or forced heading for jets on departure three digits. • <speed for props> Indicated airspeed prop aircraft will accelerate to in knots. • <speed for jets> Indicated airspeed jet aircraft will accelerate to in knots. • EXAMPLE DP GSB/08 2000 2000 080 080 170 220 DP GSB/26 2000 2000 260 260 170 220

  18. Site File PA • Climb Out Instructions (PA)- (UM Section 6.12.3) • The Climb Out Instructions entry specifies the climb out procedures for aircraft conducting a Low Approach or Touch and Go. • Format PA <pattern altitude> <heading> <distance> • <pattern altitude> Altitude aircraft will climb to after completing the Low Approach or Touch and Go in hundreds off feet. • <heading> Initial heading aircraft will fly to enter the radar traffic pattern entered in three digits. • <distance> Distance from the approach end of the runway in feet where the aircraft will initiate the climb and turn to the pattern altitude and heading specified in the format. • EXAMPLE PA 020 080 4500 • In the example above the aircraft climbs to 2000 and then turns to heading 080 at a point 4500 feet from the approach end of runway (If the runway length is 4500 feet, this procedure will occur approximately right at the departure end of runway).

  19. Site File RT • Routes (RT)- (UM Section 6.13) • The Route entry specifies a flight path to be navigated within a site. • The RT may be plotted by using fixes defined in the site file or by using the fix symbol and heading fix formats. • This allows the user to create procedures such as instrument approaches, visual approaches, Non-ILS approaches (AI), IFR routes, VFR routes, Standard Terminal Arrival Routes (STARs), and Standard Instrument Departures (SIDs). • Format RT_<name>_<[route]>_[drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • <[route]> Itinerary to be flown on the route. The route format options may consist of simply the names of the fixes (NAVAIDS) that are defined in the site file, or the fixed symbol and heading fix formats may be used. • NOTE: Because there are so many options to this entry field’s format, it will be explained in subsequent slides. • [drop | again] Optional entry that defines the aircraft’s action after it reaches the last fix in the route. If drop is specified, the aircraft is eliminated from the scenario. If again is specified, the aircraft will repeat the route over again. If no option is specified, the aircraft will continue on its last assigned heading after reaching the fix until directed otherwise. • EXAMPLE RT TRAFFICONE TP33 DHN TP4 TP3 TP2 TP30 TP15 ETP DROP • In the example above the route is made up from various NAVAIDS defined in the site file. The aircraft starts at a point in space (TP33) and proceeds direct Dothan (DHN), then proceeds direct to 5 more points in space. Upon reaching the last point, Enterprise (ETP), the aircraft is dropped from the scenario.

  20. RT TRAFFICONE TP33 DHN TP4 TP3 TP2 TP30 TP15 ETP DROP Note: For PAR only systems, the CSCAN0 utility is limited to display only the surveillance area offset for the active runway. Route - TRAFFICONE

  21. Site File RT - FS • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • A route defined by the fix symbol format may be any fix by itself or one of five fix/maneuver combinations. • The fix symbol format contains fixes (NAVAIDS) previously defined by lat/lon coordinates elsewhere in the site file. • The format may also contain fix symbols, which combine the fixes with aircraft flight maneuvers pertaining to altitude and speed changes. • Altitude (/aaa) or speed (sss) assignment changes may precede any fix symbol and will override previous altitude or speed assignments. • When the individual fix symbol condition is met, the aircraft will proceed to the next fix or fix symbol. • Format RT_<name>_[/aaa | sss]_<[route]>_[drop | again]

  22. Format RT_<name>_<[route]>_[drop | again] Site File • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • For clarification, the entry field in the format below will be changed from <[route]> to the various fix symbol format entries that may be used. RT_<name >_[/aaa | sss]_<[fix | fix\aaa> | fix\aaa< | fix/dd.d< | fix/dd.d> | fix/dd.d/rrr]>_ [drop | again] • Note that the < and > symbols within the brackets [ ] have command functions. (Not indicating a mandatory entry). • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix A fix entry indicates the name of the fix only. Instructs an aircraft to proceed to a specified location; NAVAID, intersection or waypoint previously defined in the site file. (This is the same format used for the example back on Slide 28). • EXAMPLE RT TRAFFICTWO TP33 DHN ETP • The example above instructs an aircraft to start at TP33 and proceed direct DHN, then proceed direct ETP. Since the optional drop | again entry was not used, upon reaching ETP the aircraft will circle ETP once, then continue on its last heading until it reaches the defined drop range (DR).

  23. RT TRAFFICTWO TP33 DHN ETP Route - TRAFFICTWO

  24. Site File • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • Format RT_<name >_[/aaa | sss]_<[fix | fix\aaa> | fix\aaa< | fix/dd.d< | fix/dd.d> | fix/dd.d/rrr]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix\aaa> The fix\aaa> entry indicates the name of the fix combined with a climbing altitude change. Instructs an aircraft to proceed toward the named fix until reaching an altitude above, then proceed to the next fix symbol in the flight plan. • EXAMPLE RT APE TBR /050 ETP\030> DHN • The example above instructs an aircraft to climb to 5,000 (/050) en route to ETP; leaving 3,000, continue climb to 5,000 and proceed direct DHN.

  25. RT APE TBR /050 ETP\030> DHN Route - APE Aircraft Reaches 3,000 • Note: All of Route APE is not represented. Using the last part of the route for this example.

  26. Site File • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • Format RT_<name >_[/aaa | sss]_<[fix | fix\aaa> | fix\aaa< | fix/dd.d< | fix/dd.d> | fix/dd.d/rrr]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix\aaa< The fix\aaa< entry indicates the name of the fix combined with a descending altitude change. Instructs an aircraft to proceed toward the named fix until passing an altitude below, then proceed to the next fix symbol in the flight plan. • EXAMPLE RT BEAR TP33 /015 OZR\025< ETP • The example instructs an aircraft to descend to 1,500 en route to OZR; leaving 2,500, continue descent to 1,500 and proceed direct ETP.

  27. RT BEAR TP33 /015 OZR\025< ETP Route - BEAR Aircraft Reaches 2,500 • Note: All of Route Bear is not represented. Using the last part of the route for this example.

  28. Site File • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • Format RT_<name >_[/aaa | sss]_<[fix | fix\aaa> | fix\aaa< | fix/dd.d< | fix/dd.d> | fix/dd.d/rrr]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix/dd.d< The fix/dd.d< entry indicates the name of the fix combined with a specified distance prior to the fix. Instructs an aircraft to proceed to a point within or before the distance (in nautical miles) of the fix, then proceed to the next fix symbol. • EXAMPLE RT CAT TP31 /040 ETP/12.0< /020 DHN • The example above has an aircraft maintain 4,000 en route to ETP. When the aircraft is 12 NM before ETP, the aircraft will then begin a descent to 2,000 en route to DHN.

  29. 12 Miles RT CAT TP31 /040 ETP/12.0< /020 DHN Route - CAT Aircraft Begins Descent to 2,000 • Note: All of Route Cat is not represented. Using the last part of the route for this example.

  30. Site File • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • Format RT_<name >_[/aaa | sss]_<[fix | fix\aaa> | fix\aaa< | fix/dd.d< | fix/dd.d> | fix/dd.d/rrr]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix/dd.d> The fix/dd.d> entry indicates the name of the fix combined with a specified distance after the fix. Instructs an aircraft to proceed to a point beyond or past the distance (in NM) of the fix, then proceed to the next fix symbol. • EXAMPLE EAGLE / TP12 /050 OZR OZR/05.5> /120 ETP • The example above instructs an aircraft to maintain 5,000 until 5.5 NM past or beyond OZR then begin a climb to 12,000 and proceed to ETP.

  31. 5.5 Miles RT EAGLE TP12 /050 OZR OZR/05.5> /120 ETP Route - EAGLE • Note: All of Route Eagle is not represented. Using the last part of the route for this example. • Note 2: If OZR did not precede OZR/5.5, the exit condition would be met at TP12 and the aircraft would immediately proceed to ETP.

  32. Site File • Routes (RT) - Route <[route]> Fix symbol formats - (UM Section 6.13.1.1) • Format RT_<name >_[/aaa | sss]_<[fix | fix\aaa> | fix\aaa< | fix/dd.d< | fix/dd.d> | fix/dd.d/rrr]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix/dd.d/rrr Instructs an aircraft to fly along a DME arc (dd.d) to a radial (rrr) of the specified fix. The aircraft proceeds to the distance from the fix, then proceeds via the DME arc to the specified radial. When the aircraft reaches the radial, it will proceed to the next fix symbol in the flight plan. • fix/dd.d/rrr The fix/dd.d/rrr entry indicates the name of the fix combined with a DME arc distance and radial. RT FINCH TP39 OZR/12.5/030 ETP • EXAMPLE • The example above instructs an aircraft to fly towards or away from OZR to a distance of 12.5 NM. Then the aircraft would fly a 12.5 NM arc, left or right, whichever is closer, to the OZR 030 radial. Upon reaching the OZR 030 radial, the aircraft will proceed direct to ETP.

  33. 030 Radial 12.5 Miles RT FINCH TP39 OZR/12.5/030 ETP Route - FINCH • Note: All of Route Finch is not represented. Using the last part of the route for this example.

  34. Site File RT - HF • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • The RT structure includes heading fix functionality. • This feature allows an aircraft to fly a given heading until an exit condition is met and when that exit condition is met, the aircraft will proceed to the next fix on its flight plan. • All heading fix formats use a ‘^’ (carat) as an identifier to ATCoach. • Format RT_<name>_[/aaa | sss]_<[route]>_[drop | again]

  35. Format RT_<name>_<[route]>_[drop | again] Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • For clarification, the entry field in the format below will be changed from <[route]> to the various heading fix format entries that may be used. RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • Note that all heading fix formats must be preceded by the ^ (carat) symbol, and the < and > symbols within the brackets [ ] have command functions. • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • fix Once again, a fix entry indicates the name of the fix only. Instructs an aircraft to proceed to a specified location; NAVAID, intersection or waypoint previously defined in the site file.

  36. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • EXAMPLE RT GOAT /015 DHN ^180\020< HRT • ^hhh\aaa< The ^hhh\aaa< entry indicates a heading and an altitude below exit condition. Instructs an aircraft to proceed on a specific heading until below an altitude. The (hhh) specifies the heading to be flown and (aaa) the altitude. The heading and altitude are separated by a backslash (\), combined with the less than (<) character that specifies the exit condition occurs below the altitude. Once the exit condition is met, the aircraft proceeds to the next fix in its flight plan. • The example above instructs an aircraft to descend and maintain 1,500 enroute to DHN. Upon reaching DHN, continue descent and fly heading 180 until below 2,000, then proceed on flight plan to HRT.

  37. RT GOAT /015 DHN ^180\020< HRT Route - GOAT Aircraft now below 2,000 • Note: All of Route Goat is not represented. Using the last part of the route for this example.

  38. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • ^hhh\aaa> The ^hhh\aaa> entry indicates a heading and an altitude above exit condition. Instructs an aircraft to proceed on a specific heading until above (>) an altitude. • EXAMPLE RT HOG /060 TBR ^090\035> ETP • The example above instructs an aircraft to climb and maintain 6,000 enroute to TBR. Upon reaching TBR, continue climb and fly heading 090 until above 3,500, then proceed on flight plan to ETP.

  39. RT HOG /060 TBR ^090\035> ETP Route - HOG Aircraft now above 3,500 • Note: All of Route Hog is not represented. Using the last part of the route for this example.

  40. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • EXAMPLE RT IBIS TP39 DHN ^270/ETP/07.0< HRT • ^hhh/fix/dd.d< The ^hhh/fix/dd.d< entry indicates a heading for an aircraft to fly until it is within (before) a DME distance. The (hhh) specifies a heading the aircraft will follow and fix is a location defined in the site file. The dd.d< is a distance within the identified fix. A forward slash (/) separates the heading from the fix and the fix from the distance. Once the exit condition is met, the aircraft proceeds to the next fix in its flight plan. • The example above instructs an aircraft to proceed from TP39 direct to DHN, then fly heading 270 until within or before 7 miles of ETP, then proceed on flight plan to HRT.

  41. 7 Miles RT IBIS TP39 DHN ^270/ETP/07.0< HRT Route - IBIS • Note: All of Route Ibis is not represented. Using the last part of the route for this example.

  42. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • ^hhh/fix/dd.d> The ^hhh/fix/dd.d> entry indicates a heading for an aircraft to fly until it is away (beyond) from a DME distance. • EXAMPLE RT JUNCO OZR TP13 ^285/ETP/06.0> TBR DROP • The example above instructs an aircraft to start at OZR and proceed to TP13, then fly heading 285 until 6 miles beyond or past ETP, then proceed on flight plan to TBR and drop from the scenario.

  43. 6 Miles RT JUNCO OZR TP13 ^285/ETP/06.0> TBR DROP Route - JUNCO • Note: All of Route Junco is not represented. Using the last part of the route for this example. • Note 2: If TP13 did not precede ^285/ETP/06.0, the exit condition would be met at OZR and the aircraft would proceed direct to TBR.

  44. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • ^hhh/fix/rrr The ^hhh/fix/rrr entry indicates a heading for an aircraft to fly until crossing a radial of a fix. The (hhh) specifies the heading an aircraft will follow and fix is a location defined in the site file. The (rrr) is a radial from the fix that an aircraft is expected to cross. A forward slash (/) separates the fields. Once the exit condition is met, the aircraft proceeds to the next fix in its flight plan. • EXAMPLE RT KANGAROO HRT ^310/OZR/270 DHN • The example above instructs an aircraft to start at HRT and fly heading 310 until crossing the 270 radial of the OZR VORTAC, then proceed on flight plan to DHN.

  45. Crosses 270 Radial RT KANGAROO HRT ^310/OZR/270 DHN Route - KANGAROO • Note: All of Route Kangaroo is not represented. Using the last part of the route for this example.

  46. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • ^fix/dd.d/rrr The ^fix/dd.d/rrr entry specifies a distance for an aircraft to fly to then proceed on an arc to a specified radial. The aircraft will stay on its current heading until reaching the specified distance, then arc to the inbound radial. Depending on the aircraft’s position, the distance may be before or beyond the fix. The ^fix behaves differently in that the aircraft will not proceed directly to the fix but will maintain its last heading until the specified distance which may be before or beyond the fix. • EXAMPLE RT LEOPARD DHN HEY ^HEY/10.0/290 OZR • The example above instructs an aircraft to start at DHN and proceed direct HEY, then fly present heading until 10 miles from HEY, then arc to the 290 radial. Upon reaching the 290 radial the aircraft will proceed inbound to OZR.

  47. 10 Miles Crosses 290 Radial RT LEOPARD DHN HEY ^HEY/10.0/290 OZR Route - LEOPARD • Note: All of Route Leopard is not represented. Using the last part of the route for this example.

  48. Site File • Routes (RT) - Route <[route]> Heading fix formats - (UM Section 6.13.1.2) • Format RT_<name>_[/aaa | sss]_<[fix | ^hhh\aaa< | ^hhh\aaa> | ^hhh/fix/dd.d< | ^hhh/fix/dd.d> | ^hhh/fix/rrr | ^fix/dd.d/rrr |  <pilot command>]>_ [drop | again] • <name> Up to 14 characters (a period ‘ . ’ is also allowed) name of route. • pilot command The  pilot command entry indicates a transition to pseudo-pilot commands. This entry follows the last fix in a flight plan, and instructs the aircraft to perform the pseudo-pilot commands that follow the  symbols. • Note: The  is made by pressing the dash/minus key followed by the greater than arrow. • EXAMPLE RT MOLE TP30 /030 DHN ^200\040< HRT TBR ETP H030 A020 • The example above instructs an aircraft to start at TP30, descend and maintain 3,000 enroute to DHN. Upon reaching DHN, continue descent and fly heading 200 until below 4,000, then proceed on flight plan direct HRT direct TBR direct ETP. After the last ETP, the aircraft will fly heading 030 and maintain 2,000 until reaching the defined drop range (DR).

  49. RT MOLE TP30 /030 DHN ^200\040< HRT TBR ETP H030 A020 Route - MOLE Aircraft Begins Descent to 3,000 Heading 030 At 2000 Aircraft Now Below 4000

  50. Site File HP • Holding Patterns (HP)- (UM Section 6.13.2) • Holding Patterns are racetrack patterns associated with NAVAIDS that are used to keep an aircraft within a specified airspace while awaiting further clearance from air traffic control. • Format HP_<pattern name>_<fix or latlon>_<inbound track>_<length>_<turn direction> • <pattern name> The name of the holding pattern. • <fix or latlon> NAVAID or latitude and longitude location of waypoint. • <inbound track> The heading toward the fix. • <length> Defined in minutes (a decimal point is optional). • <direction L | R> The letter L or R to specify left or right turns. • EXAMPLES HP OZHD 31 13 36 85 48 01 060 1.0 RSE of lat/lon 31 13 36 85 48 01 on the 240 radial, 1 min. legs, right turns.

More Related