ICAO FLIGHT PLAN
ROUTE OF FLIGHT -
Example - DD: KDSM
RT: DCT.MCW.DCT.GRB.J101.SSM.HL548.YTS.DCT.YQL/N0471F370.
DCT.YVP.DCT.6401N03005W.6415N03000W.64N020W.63N010W.
65N005W.DCT.VALDI.UG3.KLD.DCT.GRC.DCT
AD: ENMG
........................ NOTE: For AFSS users - The software in Model1-FC is designed to automatically convert the format for a route to the "conventional" format used by ARTCC computers as well a convert the format as is used in AFTN Service B messages. For example, the software will delete "DCT" to ARTCC flight plan messages, when present in the route of flight, yielding "MCW..GRB" in the above example. Likewise, the two "periods" (MCW..GRB) are deleted from the Service-B AFTN message. Knowledge of this premis is essential for transmission and acceptance of FPL messages to ARTCC's for acceptance and processing.
.................................. NOTE: For AFSS users - The airspace information which is adapted into the Model1-FC data base only includes data for use in U.S. contiguous airspace, a part of Canadian and Mexican airpace, and a portion of Carribean airspace commonly used by Miami IAFSS. The only "oceanic" airspace adapted is generally to a named intersection or navaid, at or just beyond the initial FIR (foreign ARTCC) boundary. It is essentially for this reason, that it is necessary to "overide" the error message (GIS RO or RO ) on virtually every ICAO flight plan. Such practice should then be considered as "standard procedure"....and it generally will not affect the processing of data at the departure ARTCC.
If the departure airport is not located on or adapted to a segment of the initial filed airway, insert "DCT", followed by the first fix on the route of flight.
Use the contraction "DCT" for any segment of the route of flight which is not on a published airway, including that portion on filed "direct" segments of the route, between navaids, navaids and fixes/intersections, segments between named intersections and segments between navaid/intersections and fixes defined in the route by latidude and longitude. DO NOT USE "DCT" between individual latitude/longitude fixes.
The distance between filed "direct" fixes should not exceed 30 minutes flying time OR 200 NM (370KM) distant from each other. Additonal fixes to define the route may be required by the affected ARTCC/ATS facility. In addition, segments of EAST-WEST flights are additionally required to be defined in minimum intervals of 10 degrees of longitude.
Defining the route:
Insert the designator code for:
Any segment of the route on a defined airway: V20 - J186 - UB10 - R12 - BR52V
Named intersections and navaids: VALDI -- GRB -- LN -- MAY
Bearing & distance from a navaid: LEV183097 -- DUB180040
Degrees defined by Latitude and Longitude: - 2-figures defining latitude in degrees, or 4-figures defining latitude in degrees and minutes, followed by "N" or "S" as appropriate....and 3-figures defining longitude in degrees or 5 figures defining longitude in degrees and minutes, followed by an "E" or "W". - 6410N03000W -- 64N020W
..................................... NOTE: To AFSS users - DO NOT use a ( / ) to separate latitude and longitude in ICAO flight plans, as normally applied for use in domestic flight plans.
Got a comment? ..."Stale" link report" ...Suggestion for additional service?
waters@txucom.net