CSC DUATS Quick Path(tm)
User's Guide

  
DUATS Quick Path (tm)
---------------------
     
Quick Path is a means to avoid the use of DUATS menus.
Quick Path is designed for the expert user and is a convenient 
means of getting to DUATS services that are frequently used.  
Off-line automated briefings (OLAB) is also available using Quick Path
commands.  See section 6.0 for details.
  
1.0  Format
   
Quick Path can be activated entering the "#" symbol followed 
by the Quick Path name at any menu prompt.
  
The format of the Quick Path name is:
   
   QQQ[S\p1\p2\...\pn]  where
  
       QQQ           is the 3 character Quick Path identifier
       S             option which sets continuous scrolling
       \p1\p2...\pn  optional user responses to prompts
  
The 'S' option allows the data to be sent continuously.  This 
is helpful if you are simultaneously printing or capturing the 
data to a file.  Setting this option does not modify your lines 
per page default parameter.
  
Each user response must be separated by a '\'.  Don't specify
a response for any prompt in which you want to accept the 
default or in some cases left blank.  For example, to accept 
the default Aircraft Tail Number in an Encode, use #ENC\\ALBANY 
instead of #ENC\N1234\ALBANY.  Don't specify a response to any
prompt in which you would enter only a carriage return (CR).
  
1.1  Quick Path Pause
  
Normally a Quick Path entry is a response to a prompt.  
Quick Path Pause gives you the option of pausing in the middle
of your Quick Path string and be prompted for a response.
  
If you use a '#' as an entry in your Quick Path string:
   - all entries prior to '#' are Quick Pathed,
   - the prompt for the field '#' is displayed,
   - after entering a correct value, Quick Path continues until
     the end of the Quick Path string or until an error occurs.
   
For example, #WAB\\sa no\gtf\#\+45\0100\q\ - pauses in request for
abbreviated weather requesting sa and notam data for location gtf
to prompt for 'altitude: (hundreds of feet)' then continues, setting
departure time to current time plus 45 minutes, and an estimated time
enroute of 1 hour".
    
    
2.0  Partial Quick Path Names and Errors
    
The user has the option of specifying a complete Quick Path name
with a response for every service prompt or a partial list.
If a partial list is specified, the next prompt will be displayed.
  
If a Quick Path user response is in error, an error message is 
displayed and the user must correct that entry and the remaining
entries in the Quick Path string.  This is done manually.
  
  
3.0  Quick Path Identifiers
  
Each Quick Path Identifier is a 3 character string.  Flight 
plan services begin with the letter 'F', weather services begin 
with 'W' and all plain language weather services begin with 'P'.
  
3.1  Exit DUATS
  
BYE - Exit DUATS
   
3.2  Encode/Decode 
  
DEC - Decode
ENC - Encode
EXT - Extended Decode
FWC - FAA/Weather Contractions
   
3.3  Flight Plan 
  
CLO - Close VFR Flight Plan
FFI - File ICAO Flight Plan 
FPF - Be Prompted for Domestic Flight Plan 
FPD - Use Default Flight Plan 
FPA - Amend Flight Plan 
FPC - Cancel Flight Plan 
FFV - View Flight Plan
LOG - Flight Planner  
    
3.4  Weather Briefings
  
WLO - Low Alt Weather Brief
WHI - High Alt Weather Brief
WAR - Weather Area Radius
WOR - Weather Outlook Route
WOA - Weather Outlook Area
WAB - Abbreviated Weather 
WSC - State/Collective Weather
WRA - Abbreviated Route Weather
WBR - Abbreviated Defined Radius Weather
   
3.5  Plain Language Weather 
  
PLO - Plain Low Alt Weather Brief
PHI - Plain High Alt Weather Brief
PAR - Plain Area Radius
POR - Plain Outlook Route
POA - Plain Outlook Area
PAB - Plain Abbreviated Weather 
PSC - Plain State/Collective Weather
PRA - Plain Abbreviated Route Weather
PBR - Plain Abbreviated Defined Radius Weather
   
4.0  Prompts and Examples
  
Most responses can be specified as part of the Quick Path name.
This section lists all applicable prompts for each DUATS service.
Examples are provided.
  
Due to the nature of several of the services, the user interface
will remain interactive.  An example of this is Amending and 
Canceling flight plans where the user must examine the flight plan
before deciding whether to cancel or amend the file.  
  
Another interactive example is when a preferred route is identified.
In this case, the preferred routes must be examined before 
continuing.
  
Plain language weather has two additional prompts.  The first
is FAA/NWS weather should be displayed before the plain language
weather.  THe default is no.  The second is specifying the time zone.
The user has the option of entering the first letter of the
time zone or the number of the menu selection which corresponds
to the time zone.  For example, the user can enter P or 4 for
Pacific time zone prior to entering the appropriate briefing
information.
  
4.1  BYE (Exit DUATS)
   
Please confirm exit (Y/N), or
  enter S to start new session:
  
Example:  #BYE\S - This will terminate current DUATS session
                   and restart another.
    
4.2  DEC (Decode)
  
Enter aircraft tail number: 
Enter ident(s):              
   
Examples:   #DEC\N1234\IAD - Decode IAD for tail number N1234.
            #dec\\iad dca bwi pit - Decode multiple identifiers.
  
4.3  ENC (Encode)
  
Enter aircraft tail number:  
Enter name:                 
  
Examples:   #ENCS\\PITTSBURGH - Encode "PITTSBURGH" using default tail 
                                number with continuous scrolling.
            #enc\n1234\sharon - Encode sharon for tail number n1234.
  
4.4  EXT (Extended Decode)
  
Enter aircraft tail number: 
Enter ident(s):              
   
Example:   #EXT\N1234\IAD - Extended Decode IAD for tail number N1234.
   
4.5  FWC (FAA/NWS Contractions)
  
Enter contraction(s):              
   
Example:   #FWC\XCP ADIZ - Expands contractions XCP and ADIZ
   
4.6  CLO   (Close VFR Flight Plan Plan)
  
Aircraft tail number:   
Acft type/special equip: 
Departure point:          
Filed Destination:               
Actual Destination:               
Remarks:                   
Enter 'C' to close or 'Q' to quit:
  
Examples:  
  
#CLO\N1234TZ\C172\ACY\IAD\DCA\DULLES FOGGED IN\C
  
The above example is a closure of a filed flight from Atlantic City N.J.
to Dulles International outside Washington D.C.  The aircraft actually landed
at Washington National.
  
4.7  FFI   (File ICAO Flight Plan)
   
Note: Adverse weather prompt will be displayed if a weather briefing has
not been requested during the current transaction. The prompt will be 
displayed prior to the filing prompt. Therefore, an additional entry will
be required if weather briefings have not been requested.
 
Aircraft tail number:         
Flight rules:(IFR,VFR,Y,or,Z)
Type of flight:(S,N,G,M,or,X) 
Aircraft type:              
COM/NAV/Approach equip:   
Departure point:          
Departure time: UTC (hhmm)   
Cruising speed: (knots)      
Level: (hundreds of ft)      
Destination:                 
Enter route:  
Est time enroute: (hhmm)    
Alternate destination(s):       
Other Information:              
Endurance: (hhmm)         
Persons on board:        
Emergency Radio:        
Survival Equipment:    
Jackets:              
Number Of Dinghies:  
Total Capacity Of Dinghies:    
Are The Dinghies Covered (Y/N) 
Color of Dinghies:            
Color of aircraft:           
Remarks about safety equip:     
Pilot in command:           
  Address:                   
  Phone no. (nnn nnn nnnn):  
Adverse WX (Y/N)          * only applies when NO weather briefing has been
                            requested prior to selection of the flight
                            plan menu items.
 
Enter field number(s) to correct, 'F' to file,'S' to save,
'FS' to file and save, 'R' for route wx briefing, or 'Q' to quit: 
 
Before the flight plan is filed, multiple fields can optionally
be modified. In order to modify the field, put the field number
in a quickpath entry and follow it with the data:
  
Field 7 is aircraft tail number
Field 8 is type of flt plan
Field 9 is acft type
Field 10 is navigational and communication equipment
Field 13 is departure point and time
Field 15 is true airspeed, cruising level, and route of flight
Field 16 is destination, est time enroute and alternate airports
Field 18 is remarks
Field 19 is endurance, persons on board, emergency radio, survival equipment, 
jackets,  number of dinghies, total capacity of dinghies, if the dinghies are
covered, color of dinghies, color of aircraft,  remarks about safety equipment,
and the pilot in commands name, address and phone number
  
Example:
  
 Note: This example can only be used when weather briefings have been 
 requested prior to the selection of flight plan items.
 
#FFI\N1234\IFR\S\DC10/H\I/A\ACY\1941\130\171\CYUL\MIV VCN YQL\0300\\\0500\2\V\P\
        V\1\6\Y\R\R\NO ELBA\\\\F\
  
This is an example of an ICAO flight plan filed from ACY to CYUL with
departure time of 19:41 GMT.  It is a scheduled IFR flight with a DC10
aircraft type with heavy weight class.  The comm equipment used is
inertial navigation with a transponder.  The flight speed is 130 knots.
17,100 feet is the altitude level.  The estimated time in route is 3 hours
with 5 hours of fuel.  Two people are on board.  On board is:  VHF emergency
radio, polar survival equipment, VHF jackets, and 1 dinghy with a capacity
of 6 people.  The dinghie is red, and it is covered.  
  
Example:
 
 Note: This example can only be used when weather briefings have NOT been 
 requested prior to the selection of flight plan items.
 
#FFI\N1234\IFR\S\DC10/H\I/A\ACY\1941\130\171\CYUL\MIV VCN YQL\0300\\\0500\2\V\P\
        V\1\6\Y\R\R\NO ELBA\\\\Y\F\
  
This is an example of an ICAO flight plan filed from ACY to CYUL with
departure time of 19:41 GMT.  It is a scheduled IFR flight with a DC10
aircraft type with heavy weight class.  The comm equipment used is
inertial navigation with a transponder.  The flight speed is 130 knots.
17,100 feet is the altitude level.  The estimated time in route is 3 hours
with 5 hours of fuel.  Two people are on board.  On board is:  VHF emergency
radio, polar survival equipment, VHF jackets, and 1 dinghy with a capacity
of 6 people.  The dinghie is red, and it is covered.  The adverse weather 
will be displayed before the flight plan is filed.
 
4.8  FPF (Be Prompted for Domestic Flight Plan)
  
Note: Adverse weather prompt will be displayed if a weather briefing has
not been requested during the current transaction. The prompt will be 
displayed prior to the filing prompt. Therefore, an additional entry will
be required if weather briefings have not been requested.
 
Type of flt plan: (IFR/VFR)
Aircraft tail number:   
Acft type/special equip: 
True airspeed: (knots)   
Departure point:          
Destination:               
Departure time: UTC (hhmm)  
Altitude: (hundreds of ft)   
Route:
Est time enroute: (hhmm)  
Remarks:                   
Fuel on board: (hhmm)       
Alternate destination(s):    
Pilot's name:            
Address:                  
Phone no. (nnn nnn nnnn):  
Aircraft home base:    
Number aboard:          
Color of aircraft:       
Dest contact name:        
Phone no. (nnn nnn nnnn):  
Adverse WX (Y/N)          * only applies when NO weather briefing has been
                            requested prior to selection of the flight
                            plan menu items.
Enter field number(s) to correct, 'F' to file,'S' to save,
'FS' to file and save, 'R' for route wx briefing, or 'Q' to quit: 
  
Before the flight plan is filed, multiple fields can optionally
be modified. In order to modify the field, put the field number
in a quickpath entry and follow it with the data:
  
Field 1 is type of flt plan
Field 2 is aircraft tail number
Field 3 is acft type
Field 4 is true airspeed
Field 5 is departure point
Field 6 is destination
Field 7 is departure time
Field 8 is altitude
Field 9 is route
Field 10 is est time enroute
Field 11 is remarks
Field 12 is fuel
Field 13 is alternate destinations
Field 14 is pilot name, address, phone, and acft home base
Field 15 is number aboard
Field 16 is color of aircraft
Field 17 is destination contact name and phone
  
Examples:  
 
 Note: This example can only be used when weather briefings have been 
 requested prior to the selection of flight plan items.
 
#FPF\I\\\100\PIT\BWI\1230\110\DIRECT\0300\\0500\\\\\\2\\\\F\
  
This is an example of filing an IFR flight plan from PIT to BWI at 
12:30 GMT with 2 aboard, taking a DIRECT route at 100 knots 
with 0500 hours of fuel aboard with estimate 3 hours enroute.  
Default values or values from the pilot record are used for 
the blanked fields.   The filed flight plan will be displayed.  
  
 Note: This example can only be used when weather briefings have NOT been 
 requested prior to the selection of flight plan items.
 
#FPF\I\\\100\PIT\BWI\+90\110\DIRECT\0300\\0500\\\\\\2\\\\Y\FS\
  
This is an example of an IFR flight plan from PIT to BWI with 
a departure time of current time plus 90 minutes with 2 aboard, 
taking a DIRECT route at 100 knots with 0500 hours of fuel 
aboard with estimate 3 hours enroute.  Default values or values 
from the pilot record are used for the blanked fields.  The adverse 
weather will be displayed. This flight plan is displayed, saved and filed.
  
 Note: This example can be used whether or not weather briefings
 have been requested prior to the selection of flight plan items.
 Adverse weather will NOT be displayed. 
   
#FPF\I\\\100\PIT\BWI\+90\110\DIRECT\0300\\0500\\\\\\2\\\\\FS\
  
This is an example of an IFR flight plan from PIT to BWI with 
a departure time of current time plus 90 minutes with 2 aboard, 
taking a DIRECT route at 100 knots with 0500 hours of fuel 
aboard with estimate 3 hours enroute.  Default values or values 
from the pilot record are used for the blanked fields.  This flight 
plan is displayed, saved and filed.
  
NOTE: FPF files DOMESTIC flight plans.
   
4.9  FPD (Use Default Flight Plan)
  
Note: Adverse weather prompt will be displayed if a weather briefing has
not been requested during the current transaction. The prompt will be 
displayed prior to the filing prompt. Therefore, an additional entry will
be required if weather briefings have not been requested.
 
Enter default flight plan number,
'L' for list, or 'Q' to quit:
  
Adverse WX (Y/N)          * only applies when NO weather briefing has been
                            requested prior to selection of the flight
                            plan menu items.
Enter field number(s) to correct, 'F' to file,'S' to save,
'FS' to file and save, 'R' for route wx briefing, or 'Q' to quit: 
  
Enter default flight plan number,
'A' to add, 'D' to delete, or 'Q' to quit:
  
Enter default flight plan number to delete:
  
Before the flight plan is filed, multiple fields can optionally
be modified. In order to modify the field, put the field number
in a quickpath entry and follow it with the data:
  
If the default flight plan is domestic, the fields are:
  
Field 1 is type of flt plan
Field 2 is aircraft tail number
Field 3 is acft type
Field 4 is true airspeed
Field 5 is departure point
Field 6 is destination
Field 7 is departure time
Field 8 is altitude
Field 9 is route
Field 10 is est time enroute
Field 11 is remarks
Field 12 is fuel
Field 13 is alternate destinations
Field 14 is pilot name, address, phone, and acft home base
Field 15 is number aboard
Field 16 is color of aircraft
Field 17 is destination contact name and phone
  
If the default plan is ICAO, the fields are:
  
Field 7 is aircraft tail number
Field 8 is type of flt plan
Field 9 is acft type
Field 10 is navigational and communication equipment
Field 13 is departure point and time
Field 15 is true airspeed, cruising level, and route of flight
Field 16 is destination, est time enroute and alternate airports
Field 18 is remarks
Field 19 is endurance, persons on board, emergency radio, survival equipment, 
jackets,  number of dinghies, total capacity of dinghies, if the dinghies are
covered, color of dinghies, color of aircraft,  remarks about safety equipment,
and the pilot in commands name, address and phone number
  
Examples:
  
#FPD\1 or #FPD\L\1
  
This displays the first default flight plan stored by the pilot.
  
#FPD\1\F or #FPD\L\1\F
  
This displays and files the first default flight plan stored by the pilot.
  
#FPD\L
  
This lists the pilot's default flight plans, 
identified by the departure and destination points.
  
#FPD\L\D\5
  
This displays the fifth default flight 
plan stored, and gives the pilot the option of deleting the plan.
  
4.10  FPA (Amend Flight Plan)
   
Note: Adverse weather prompt will be displayed if a weather briefing has
not been requested during the current transaction. The prompt will be 
displayed prior to the filing prompt. Therefore, an additional entry will
be required if weather briefings have not been requested.
 
Enter aircraft tail number: 
For OLAB, there are two additional fields within the quickpath
sequence after the tail number:
  
Departure point:
Departure time: UTC (hhmm)
  
These fields along with the pilot's access code and the tail number,
ensure that the flight plan the OLAB user is attempting to amend is
unique.
  
Before the flight plan is filed, multiple fields can optionally
be modified. In order to modify the field, put the field number
in a quickpath entry and follow it with the data:
  
If the default flight plan is domestic, the fields are:
  
Field 1 is type of flt plan
Field 2 is aircraft tail number
Field 3 is acft type
Field 4 is true airspeed
Field 5 is departure point
Field 6 is destination
Field 7 is departure time
Field 8 is altitude
Field 9 is route
Field 10 is est time enroute
Field 11 is remarks
Field 12 is fuel
Field 13 is alternate destinations
Field 14 is pilot name, address, phone, and acft home base
Field 15 is number aboard
Field 16 is color of aircraft
Field 17 is destination contact name and phone
  
Adverse WX (Y/N)          * only applies when NO weather briefing has been
                            requested prior to selection of the flight
                            plan menu items.
 
If the default plan is ICAO, the fields are:
  
Field 7 is aircraft tail number
Field 8 is type of flt plan
Field 9 is acft type
Field 10 is navigational and communication equipment
Field 13 is departure point and time
Field 15 is true airspeed, cruising level, and route of flight
Field 16 is destination, est time enroute and alternate airports
Field 18 is remarks
Field 19 is endurance, persons on board, emergency radio, survival equipment, 
jackets,  number of dinghies, total capacity of dinghies, if the dinghies are
covered, color of dinghies, color of aircraft,  remarks about safety equipment,
and the pilot in commands name, address and phone number
  
Adverse WX (Y/N)          * only applies when NO weather briefing has been
                            requested prior to selection of the flight
                            plan menu items.
 
Example:
  
#FPA\N1234
  
This displays the flight plan filed for N1234 and give the user the option
of modifying any field. 
  
  
4.11  FPC (Cancel Flight Plan)
  
Enter aircraft tail number:  
   
For OLAB, there are three additional fields within the quickpath
sequence after the tail number:
  
Departure point:
Departure time: UTC (hhmm)
Destination (optional):
  
These fields along with the pilot's access code and the tail number,
ensure that the flight plan the OLAB user is attempting to cancel is
unique.
 
Examples:
#FPC\N1234
  
This displays the flight plan files for N1234 and give the user the option of
canceling.
#FPC\N1111L\IAD\2300\DAL
This cancels the flight plan for N1111L with Departure Point (IAD), 
Departure Time (2300), and Destination Point (DAL).
 
 
4.12 FFV (View Flight Plan)
 
Enter aircraft tail number:
 
For OLAB, there are two additional fields within the quickpath
sequence after the tail number:
  
Departure point:
Departure time: UTC (hhmm)
  
These fields along with the pilot's access code and the tail number,
ensure that the flight plan the OLAB user is attempting to cancel is
unique.
  
Enter 'R' for route wx briefing or 'Q' to Quit
 
Example:
 
#FFV\N1234
  
This displays the flight plan file for N1234 and gives the user the option
of getting the route weather briefing.
 
4.13 LOG (Flight Planner)
   
The Quick Path option for the flight planner differs slightly
from the Quick Path entry for other parts of DUATS.  Only users
that have stored performance data are eligible to use Flight
Planner Quick Path.  Since the flight planner is highly interactive, 
and different input options will result in different prompts, the 
Quick Path option for the planner has been set up to always accept
a single form of input:
  
    #LOG\from\to\time\routing\tail\type\altitude
    
For example:
  
    #LOG\rhv\trk\0200\*a\n6506c\\115
  
would request a plan from Reid-Hillview (RHV) to Truckee (TRK)
departing at 0200 UTC, routed via shortest-path airways (*A), in
aircraft N6506C, using stored parameters for that aircraft,
cruising at 11,500 feet.  That same request could also be
entered as:
  
    #LOG\rhv\trk\0200\1\n6506c\n6506c\11500
  
Note that "*a" is replaced by "1", which is the menu choice
number for automatic routing via low-altitude airways.  "*a"
will work even if the routing menu is revised at some future
time; "1" may refer to a different option in the future.
  
A more complex user-specified route request can also be given:
  
    #LOG\rhv\smo\1700\*g gmn *a\n2901t\warrior\7500
  
would request a plan from Reid-Hillview (RHV) to Santa Monica
(SMO) departing at 1700 UTC, routed via LORAN direct (*G) to
Gorman (GMN) and then via shortest-path airways (*A) to Santa
Monica, in aircraft N2901T, using stored parameters for a
Warrior, cruising at 7,500 feet.
  
    #LOG\\\\*a\\\
  
would request a plan via low-altitude airways using previously-
entered data for all other inputs:  departure airport,
destination airport, departure time, N-number, and cruise
altitude.  The N-number also specifies the aircraft type, and
performance data must have been stored for this N-number.
  
Routing may either be specified by a menu choice number or may
be a user-selected routing string (e.g., *a); valid menu choices
are:
  
    1.  automatically selected shortest path, via low altitude
        airways
    3.  automatically selected shortest path, via a combination
	of low altitude airways and VOR-direct segments
    4.  great-circle routing for LORAN
    5.  great-circle routing for RNAV (fix/radial/distance)
	equipment
  
Automatic routing via jet routes cannot be specified using menu
choice 2 -- instead, it may be specified by stating the
departure procedure or fix, *J, and the arrival procedure or
fix.  Explicit routing options are described in detail in
section 4.3.  As an example, from San Jose to Chicago, the
routing "loupe8.sac *j dbq.jvl1" could be used:
  
    #LOG\sjc\ord\1400\loupe8.sac *j dbq.jvl1\n302ua\b737\330
  
The aircraft type may be:
(1) null ("\\"), in which case the current tail number will be
    used 
(2) a string, in which case the stored aircraft profiles will
    be searched for aircraft performance data with this name
(3) a menu item number from the "Select Aircraft Performance
    Data" menu, in which case that selection will be used
  
As with all other input to the flight planning system,
input is case-insensitive (upper or lower case will be accepted).
  
No interactive confirmation will be performed.  If any problems
are detected with the Quick Path string, the entire command will
be rejected and you will be returned to the DUATS main menu.
  
  
4.14  WLO, WHI (Standard Low and High Route Weather Briefing)
  
Enter aircraft tail number:  
Departure time: UTC (hhmm)
Departure point:            
Destination:               
Alternate Destination:               
Altitude: (hundreds of ft)
Enter Route:
Est time enroute: (hhmm)   
Route Corridor Width:
Winds Aloft Corridor Width:
View ATC delay and flow control advisories (Y/N): 
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated NOTAMs are available.
Do you request them? (Y/N)
 
Examples:  
 
#WLOS\N3421\1230\SFO\MIA\\110\DIRECT\0900\\\N\N\N
  
Note, continuous scrolling has been specified and the user has not specified an
alternate destination, has selected to use the default route and winds
aloft corridor widths, has selected to decline the Tropical Depression
data and the ATC delay data, and FDC NOTAMs that are not associated with 
an affected facility. 
  
#WHI\N3421\0900\BOS\IAD\BWI\220\\0300\\\Y\N\N
  
Note, this user has selected BWI as an alternate, an altitude of 22000 feet,
the default corridor widths, accepts the ATC delay advisories, declines the 
WH data, and declines FDC NOTAMs along the route.  
 
#WHI\\+120\bna\boi\\220B250\\0300\40\\N\Y\N
  
Note, the time of departure is current time plus 120 minutes, the user
has selected a block of altitude levels, has selected route corridor width
of 40 nautical miles, and will receive Tropical depression data,  but not
the ATC data, or the FDC NOTAMs along the route.  
  
4.15  WAR (Standard Area Radius Weather Briefing)
  
Enter aircraft tail number:  
Departure Time: UTC (hhmm)
Departure Point:
Radius: nm
View ATC delay and flow control advisories (Y/N): 
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.
Do you request them? (Y/N)             
  
Example:
  
#WAR\\+120\gtf\100\n\n\n
  
Note, this user has requested weather for 100
nautical miles from Great Falls, the departure time is current time
plus 120 minutes, and has declined to receive the Tropical depression 
data, the ATC delay data, and the FDC NOTAM data.
  
4.16  WOR, WOA (Outlook Route, and Area Weather Briefing)
 
           Outlook Route Weather Briefing
  
Enter aircraft tail number:   
Departure Time: UTC (hhmm)  
Departure Point:          
Destination:               
Alternate Destination:
Altitude(s): (hundreds of feet)
Enter Route:
Est time enroute: (hhmm)
Route Corridor Width:
METAR,UA,SD,FD,NO/FDC,ATC are not
included in this briefing unless
you enter the type(s) needed below.
Enter Desired type(s):
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.  * only applies when FDC is 
                                            specified as a weather type.
  
Example:
 
#WOR\\+420\gtf\boi\\100\direct\0100\\\n
 
Note, this user has requested outlook route weather from Great Falls to
Boise with no alternate, the departure time is current time plus 420
minutes (7 hours), the altitude is 10000 feet, the default route corridor
width is 100 and the  user has declined to display any of the excluded data 
types and also has declined to receive the Tropical depression data, and FDC 
NOTAMS.
  
           Outlook Area Weather Briefing
  
Enter Aircraft tail number:
Departure Time: UTC (hhmm)
Departure Point:
Radius: (nm)
METAR,UA,SD,FD,NO/FDC,ATC are not
included in this briefing unless
you enter the type(s) needed below.
Enter Desired type(s):
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.  * only applies when FDC is 
                                            specified as a weather type.
  
Example:
 
#WOA\\+420\gtf\100\\n
  
Note, this user has requested outlook area weather for 100 nautical miles from 
Great Falls, the departure time is current time plus 420 minutes (7 hours), and 
has declined to display any of the excluded data types, and has declined to
the Tropical Depression data, and FDC NOTAMS.
  
4.17  WAB (Abbreviated Location Weather Briefing)
  
Enter aircraft tail number:
Weather types:
Locations:                
Altitude:
Departure time: UTC (hhmm)  
Est time enroute:
Adverse WX: (Y/N)                  
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.  * only applies when FDC is 
                                            specified as a weather type.
   
Example: 
  
#WABS\\taf metar\dca\120\0900\0130\n\n
  
This user has selected the smooth scroll option for the TAF and METAR
reports to be received from DCA.  The user has declined the adverse weather
and the tropical Depression data.  
  
#WABS\\sd ua\dca\120\+90\0130\n\n
  
This user has selected smooth scroll, SD and UA reports, a departure
time of +90 minutes, and has declined the adverse weather and the WH data.
   
4.18  WSC (State/Collective Weather Briefing)
  
Enter aircraft tail number:
Weather types:
Enter State/Collective Id(s):
Collective(s) Exist:                * only applies if Collectives
                                      exist for specified State id
Altitude:
Departure time: UTC (hhmm)  
Est time enroute: (hhmm)
Non-associated FDC NOTAMS are available.  * only applies when FDC is
Do you request them? (Y/N)                  specified as a weather type.
  
Example:  
#WSC\\taf metar\wa va\120\0900\0100
  
Note, this user has requested the weather for the states of Washington
and Virginia, the file types TAF and METAR.  The input altitude is 12,000 feet. 
  
Example:  
#WSC\\metar ua no\ca\nocal cntcal\120\0900\0100\ 
  
Note, this user has requested the weather for the state of California, the  
collectives displaying weather for Northern and Central California, the file  
types, METAR, UA and NO.  The selected altitude is 12,000 feet.
  
Example:  
#WSC\\metar\wtx\120\+90\0100\ 
  
Note, this user has requested the weather for the Western Texas,
the departure time is current time plus 90 minutes, the file type METAR. 
The selected altitude is 12,000 feet.
  
4.19  WRA  (Abbreviated Route Weather Briefing)
 
Enter aircraft tail number:
Weather types:
Departure time: UTC (hhmm)
Departure point:
Destination:
Alternate Destination:
Altitude: (hundreds of ft)
Enter Route:
Est time enroute: (hhmm)                  * only applies when FD is specified
                                            as a weather type
Route Corridor Width:
Winds Aloft Corridor Width:               * only applies when FD is specified
                                            as a weather type
Adverse WX: (Y/N)
Tropical Depression/Hurricane Advisories (Y/N):
Non-associated FDC NOTAMS are available.  * only applies when FDC is
                                            specified as a weather type.
 
Example:#WRA\\taf metar fd\+45\iad\acy\\120\\0100\\\n\n
 
Note, this user has requested only the weather types metar, taf and fd along
the route from IAD to ACY using the default route corridor width and
default winds aloft corridor width. The user is prompted for estimated time
enroute and the winds aloft corridor width since he selected FDs. The user
has declined the adverse weather and tropical depression advisories.
 
Example:#WRAS\\taf metar\+45\iad\acy\\120\\\n\n
 
Note, this user has requested only the weather types metar, and taf along
the route from IAD to acy using the default route corridor width. The user
has declined the adverse weather and tropical depression advisories.
 
4.20 WBR (Abbreviated Defined Radius Weather Briefing) 
 
Enter aircraft tail number:
Weather Types:
Departure time: UTC (hhmm)
Location(s):
Radius:
Altitude: (hundreds of ft)      * only applies when FD is specified as
                                  a weather type
Est time enroute: (hhmm)        * only applies when FD is specified as
                                  a weather type
Adverse WX: (Y/N)
Tropical Depression/Hurricane Advisories (Y/N):
Non-associated NOTAMs are available. * only applies when FDC is specified 
Do you request them? (Y/N)             as a weather type
 
Example:  #WBRS\N1234\metar taf\+45\dfw\200\n\n
 
Note:  This user wants to view all metars and tafs in the 200 nm radius
around DFW. The user has declined the adverse weather and the tropical
depression advisories.
 
Example:  #WBRS\N1234\metar taf fd\+45\dfw sea\150\100\0030\n\n
 
Note:  This user wants to view all metars, tafs and FDs in the 150 nm radius
around DFW and SEA. The Altitude and ETE are specified as the user requested
the FD data type. The user has declined the adverse weather and the tropical
depression advisories.
 
Example:  #WBRS\N1234\fd\+45\3851/7702\200\100\0030\n\n
 
Note:  This user wants to view the FDs in the 200 nm radius around the 
lat/long 3851/7702 (DCA). The Altitude and ETE are specified as the user 
requested the FD data type. The user has declined the adverse weather and the 
tropical depression advisories.
 
4.21 PLO, PHI (Plain Language Standard Low and High Route Weather Briefing)
 
Display official FAA weather: (Y/N)  
Timezone:
Enter aircraft tail number:  
Departure time: UTC (hhmm)
Departure point:            
Destination:               
Alternate Destination:               
Altitude: (hundreds of ft)
Enter Route:
Est time enroute: (hhmm)   
Route Corridor Width:
Winds Aloft Corridor Width:
View ATC delay and flow control advisories (Y/N): 
Tropical Depression/Hurricane Advisories (Y/N
Non-associated NOTAMs are available. * only applies when FDC is specified 
Do you request them? (Y/N)             as a weather type
  
Examples:  
#PLOS\N\E\N3421\1230\SFO\MIA\\110\DIRECT\0900\\\N\N\N
  
Note, continuous scrolling has been specified and the user has not specified an
alternate destination, has selected to use the default route and winds
aloft corridor widths, has selected to decline the Tropical Depression
data and the ATC delay data, and FDC NOTAMs that are not associated with 
an affected facility. No FAA formatted weather will be displayed. 
  
#PHI\n\p\n3421\0900\BOS\IAD\BWI\220\\0300\\\Y\N\N\
  
Note, this user has selected plain language weather only, and accepted
BWI as an alternate, an altitude of 22000 feet, the default corridor
widths, accepts the ATC delay advisories, declines the WH data, and
FDC NOTAMs along the route.
  
4.22  PAR (Plain Standard Area Weather Briefing)
    
Display official FAA weather: (Y/N)  
Timezone: 
Enter aircraft tail number:   
Departure Time: UTC (hhmm)  
Departure Point:          
Radius: nm
View ATC delay and flow control advisories (Y/N):   
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.  * only applies when FDC is
Do you request them? (Y/N)                  specified as a weather type.
  
Example: 
#PAR\n\e\\+120\gtf\100\n\n\n\
  
Note, this user has requested plain language weather only, has requested
weather for 100 nautical miles from Great Falls, the departure time is
current time plus 120 minutes, and has declined to receive the ATC delay 
data, Tropical Depression data, and FDC NOTAMs.
  
4.23  POR, POA (Plain Standard Outlook and Area Weather Briefing)
  
      Outlook Route Weather Briefing
  
Display official FAA weather (Y/N):
Timezone:
Enter Aircraft tail number:
Departure Time: UTC (hhmm)
Departure Point:
Destination:
Alternate Destination:
Altitudes: (hundreds of ft)
Enter route:
Est time en route: (hhmm)
Route corridor width:
METAR,UA,SD,FD,NO/FDC,ATC are not
included in this briefing unless
you enter the type(s) needed below.
Enter Desired type(s):
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.  * only applies when FDC is
Do you request them? (Y/N)                  specified as a weather type.
  
Example:  
#POR\N\E\N5434\+420\MIA\ALB\\170\\0400\\\Y
  
This example selects plain language weather only, and selects Eastern
time zone, departure time is current time plus 420 minutes
(7 hours), altitude is 17000 feet, the Tropical depression data will be
displayed, FDC data will not be displayed.  
  
      Outlook Area Weather Briefing
  
Display official FAA weather (Y/N):
Timezone:
Enter aircraft tail number:
Departure time:  UTC (hhmm)
Departure point:
Radius: (nm)
METAR,UA,SD,FD,NO/FDC,ATC are not
included in this briefing unless
you enter the type(s) needed below.
Enter Desired type(s):
  
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available.  * only applies when FDC is
Do you request them? (Y/N)                  specified as a weather type.
  
Example:  
#poa\y\e\\+420\sea\100\\y
  
This example selects FAA weather as well as plain language, 
and selects Eastern time zone.  The WH will be displayed.
The FDC NOTAMs will not be displayed.
    
4.24  PAB (Plain Abbreviated Location Weather Briefing)
  
Display official FAA weather: (Y/N)  
Timezone:
Enter Aircraft tail number:
Weather Types:
Locations:
Altitude:
Departure Time: UTC (hhmm)
Est time en route:
Adverse WX: (Y/N)                  
Tropical Depression/Hurricane Advisories (Y/N):   
Non-associated FDC NOTAMS are available * only applies when FDC is specified
Do you request them (Y/N)?                as a weather type
  
Example:
#PABS\N\C\\taf metar\dca\130\0900\0130\n\n
  
The user has selected plain language weather only and has selected
Central Time zone.  Weather types TAF and METAR are selected.  WH
data and adverse weather have been declined.  
  
4.25  PSC (Plain State/Collective Weather Briefing)
  
Display official FAA weather: (Y/N)  
Timezone:
Enter aircraft tail number:
Weather Types:
Enter State/Collective Id(s):
Collectives Exist:                * only applies when Collectives 
                                    exist for specified State id
Altitude:
Departure time: UTC (hhmm)  
Est time enroute: (hhmm)
Non-associated FDC NOTAMs are available     * only applies when FDC is
Do you request them (Y/N)?:                   specified as a weather type
  
Examples:  
#PSC\N\P\\taf metar\wa\\130\0900\0100
  
Note, this user has requested plain language weather only, and has
requested Pacific time zone for the state of Washington, the file
types TAF and METAR.  The selected altitude is 13000 feet.
  
#PSC\N\P\\taf metar\wa va\130\+60\0100
  
Note, this user has requested plain language weather only, and has
requested Pacific time zone for Washington and Virginia, the file
types TAF and METAR.  The departure time is current time plus 60
minutes, the selected altitude is 13000 feet.
 
4.26  PRA (Plain Abbreviated Route Weather Briefing)
 
Display official FAA weather: (Y/N)
Timezone:
Enter aircraft tail number:
Weather types:
Departure time: UTC (hhmm)
Departure point:
Destination:
Alternate Destination:
Altitude: (hundreds of ft)
Enter Route:
Est time enroute: (hhmm)                  * only applies when FD is specified
                                            as a weather type
Route Corridor Width:
Winds Aloft Corridor Width:               * only applies when FD is specified
                                            as a weather type
Adverse WX: (Y/N)
Tropical Depression/Hurricane Advisories (Y/N):
Non-associated FDC NOTAMS are available.  * only applies when FDC is
                                            specified as a weather type.
 
Example:
#PRAS\N\E\\taf metar fd\+45\iad\acy\\120\\0100\\\n\n
 
Note,  this is the same request as above except the user only wants to
see the plain language translation for the Eastern timezone.
 
Example:
#PRA\N\e\\taf metar\+45\iad\acy\\120\\\n\n
 
Note,  this is the same request as above except the user only wants to
see the plain language translation for the Eastern timezone. The user has
not selected the FD data type.
 
4.27 PBR (Plain Abbreviated Defined Radius Weather Briefing)
 
Display official FAA weather (Y/N):
Timezone:
Enter aircraft tail number:
Weather Types:
Departure time: UTC (hhmm)
Location(s):
Radius:
Altitude: (hundreds of ft)                * only applies when FD is specified
                                            as a weather type
Est time enroute: (hhmm)                  * only applies when FD is specified
                                            as a weather type
Adverse WX: (Y/N)
Tropical Depression/Hurricane Advisories (Y/N):
Non-associated NOTAMs are available. * only applies when FDC is specified 
Do you request them? (Y/N)             as a weather type
 
Example:  #PBRS\N\C\N1234\metar taf\+45\dfw\100\n\n
 
Note:  This users selects the same request as above except wants to only
see the Plain Language translation for the Central timezone.
   
  
5.0  Off-line Automated Briefing (OLAB)
  
OLAB is a fully non-interactive session that can be used to access DUATS
using scripts.
  
OLAB Logon
----------
  
An OLAB script is identified by inserting a "#" symbol in front of the
access code in a script file. It is valid to place the OLAB identifier
in between a TERMINAL ID and access code.  If you are using DUAT front-end
software provided by GTE (CIRRUS for GTE DUATS) or an approved third-party 
vendor, you do not have to be concerned about inserting the '#' symbol or 
the terminal ID before the access code.  It is done automatically by the 
front end software.  However, if you are writing your own scripts using a 
general commercial off-the-shelf terminal communications package, you will 
need to insert a '#' before your access code when your script or software
package replies to the access code prompt.  For example, when the
system prompts:
  
Enter DUAT access code -or- last name:
  
your program or script should reply with:
  
#nnnnnnnn 
  
where "nnnnnnnn" is your 8-character GTE assigned access code or
your 9-character or 10-character personal selected access code.
  
The Windows Software "Cirrus" for GTE DUATS can be downloaded from the GTE
DUATS Aviation Home Page (http://www.gtefsd.com/aviation/GTEaviation.html)
or can be obtained by calling the GTE DUATS 24 Hour Help Line: 1-800-345-3828
  
OLAB Commands
-------------
  
Once an OLAB session is identified, then the only commands that are accepted
are valid quickpath commands. Please see the "Prompts and Examples" section 
for a list of valid quickpath commands. In general, all weather graphics,
weather functions and flight planning functions are available through 
quickpath.
  
Weather Graphics
----------------
  
Weather Graphics will be available with the "MAP" command. These will
be distributed in the NAPLPS format.  Weather graphics will only be 
available to users with 14400 bps modem connections or better. The 
Weather Graphic commands available are:
  
OLAB Command 		Description 			Update cycle
------------		-----------------------------	------------
#MAP\USRADAR\           US Radar                        Every 60 minutes
#MAP\USWXDPCT\          Weather Depiction               Every 60 minutes 
#MAP\USSFC\             Surface Analysis                Every 6 hours
#MAP\MOISTURE\          Comp Moist Stability Chart      Every 12 hours
#MAP\USHI00Z\           US High Level Weather 00Z       Every 12 hours
#MAP\USHI12Z\           US High Level Weather 12Z       Every 12 hours
#MAP\USLO00Z\           US Low Level Weather 00Z        Every 12 hours 
#MAP\USLO12Z\           US Low Level Weather 12Z        Every 12 hours 
#MAP\USPRG12\           12 Hour Surface Forecast        Every 12 hours
#MAP\USPRG24\           24 Hour Surface Forecast        Every 12 hours 
#MAP\USPRG36\           36 Hour Surface Forecast        Every 12 hours
#MAP\USPRG48\           48 Hour Surface Forecast        Every 13 hours
#MAP\SEVERE24\          Severe Weather Outlook - Day 1  Every 24 hours
#MAP\SEVERE48\          Severe Weather Outlook - Day 2  Every 24 hours
  
OLAB Session
------------
  
The OLAB session will run each quickpath command in a smooth scroll mode.
No user intervention is allowed, so quickpaths that terminate abnormally
will be aborted, and the next quickpath command processed. A reason for
the abnormal termination will be available.
  
OLAB Limitation
---------------
  
Since the OLAB session is completely non-interactive, notifications to the
user will be given to the user that may be tended to later in an interactive
session. These cases include: personal and FAA messages, personal profile
updates, preferred routes, and SOCALS. In the case of preferred routes and
SOCALS the route chosen by the user will be processed but the notification
given.
  
Any informational messages will be shown to the user. These include the login
banner, OLAB error messages, an OLAB prompt (OLAB:), and no weather available
messages (if, applicable).
  
The user is required to terminate the OLAB session with the #BYE command.


Copyright © 1991-99 Computer Sciences Corporation $Id: duats_quick_path.html,v 1.6 2003/03/30 05:00:18 geoff Exp $