Link to eLearning


1       Introduction 

Route Screen Overview 

This topic gives you an overview of the Route screen. You should begin with this topic if you have no experience with the Route screen. 

We estimate that this will take 5 minutes to complete.

2       Detailed Explanation 

Route Screen - Prerequisites

Before you begin this topic you should be familiar with the Map and Info functionality. 

Route Screen Overview

This training is designed to provide an overview of the Route Interface.

 

Training will include:

        Reviewing and sorting the route analysis

        Editing a route

        Building a new route

        Utilizing Route Builder option

Interaction 1 Click the Flight 0100 list item.

Interaction 1

Interaction 1 Click the Route tab.

Once you have selected the flight, the route is displayed on the map. You may have to move and adjust the map to see the full route. 

Once you have selected the flight, the Info panel displays information on the flight. 

Interaction 1 Click the top route (Route 1) list item.

Saved routes are displayed here. If mulitple routes exist you can sort them by Fuel, Dist, Time, FuelCost, DOC, OFC or Cost. Click on one of the headers to sort.

It is important to note that the information displayed here are estimates only. Routes may change during a compute.  

The New button, along with the ones to the right, are used when editing or creating a new route. They will be explained in later topics. 

Interaction 1 Click the New button.

Route Information for the selected route is displayed in the Info panel.

Route Legs

The Route is displayed in individual legs. Each leg shows where it originated (From), the airway used (Airway), and where it terminates (To). Flight Level and Orbit Time (above) are also part of each leg.

Flight Level

Each leg of the generated flight includes a provision for a flight level to be entered for it. The Flight Level fields are located to the right of the corresponding leg. Clicking in the field enables it for data entry. The flight level that you enter corresponds to the waypoint listed to the left of it in the To column.

To illustrate, in the example below, the flight level for the leg from waypoint HEMIS to waypoint FNT is entered as 380. This means that at waypoint HEMIS, the pilot begins to ascend from flight level 320 (the flight level entered for the previous leg) so that the aircraft is at flight level 380 by the time waypoint FNT is reached.

 

Orbit Time

These fields allow you specify an orbit time (i.e., time in a holding pattern) for any waypoint in the route, in minutes. This can be any positive number up to three digits.

If a value is entered for one of these fields, the flight level must also be specified for the associated waypoint.

Profile

The Profile list displays all available cruise profiles for the selected aircraft.

Interaction 1

Interaction 1 Click the Departure Runway dropdown button.

Departure Runway

If the Default Runways field in FOMS Menu 170 (Airline Parameter File) is set to Y, then the Departure Runway drop-down list will default to Max Headwind, but you can select any of the following options:

None: Generic SIDs/STARs are used

Use specific runway: A specific runway can be selected from a drop-down list under the ORIG and/or DEST headings. The drop-down list of runways comes from FOMS Menu 107 (Runways Program).

Best Route: This option picks an optimized route result based on time, and the optimizer used (LC,LT,LF). Procedures are weighted so that ones tied to runways with higher headwinds are chosen over runway-specific procedures; however, the NFP system can choose a runway specific procedure that isn't the highest headwind if it is the most optimal route. You can set Best Route as your default in the FOMS 170 menu by setting the Default Runway field to.

Max Headwind: This option prioritizes procedures tied to the departure/arrival runway with the maximum headwind component. This is a strict component when choosing procedures as the best route will not be chosen over a route with maximum headwind.

Longest Procedure: The runway causing the longest distance is selected from the available runways. Once the route generator has chosen a SID/STAR, then for all the runways that the SID/STAR can use, the runway giving the longest procedure distance is chosen (as long as it is suitable). A similar ranking system would occur where the longest distance gives a better ranking, but unsuitability gives a lower ranking.

Max Tail Wind: Entering a value in the Max Rwy Tail Wind in the FOMS 170 sets a maximum tail wind for runway selection. This ensures the NFP system does not use a procedure with forecasted tail winds greater than this value. This setting primarily affects the Best Route and Longest Procedure options. 

Interaction 1

Interaction 1 Click the Best Route list item.

Interaction 1

Interaction 1 Click the Use a specific SID checkbox.

When you select a specific SID from the drop-down list the procedure is automatically displayed on the map screen. The procedure is available immediately, you do not need to select the Generate button. 

Use a specific SID

When you click on the checkbox allows a drop-down list of SIDs that apply to the selected runway from FOMS Menu 320 (SID Routes Program) is made available for you to choose from.

Do not use SIDs

Clicking the on Do not use SIDs checkbox instructs NFP to not use SIDS when the generating the route. NFP generates a route to fly direct to the most efficient enroute waypoint.

Use a preferred departure

Clicking the Use Preferred Departure checkbox allows you to make use of a preferred departure in your route. A drop-down list of preferred departures from FOMS Menu 316 (Preferred Departures Program) appears for you to choose from.

Interaction 1

Interaction 1 Click the Use Tracks checkbox.

Use Tracks

Clicking the Use Tracks checkbox allows you to make use of tracks in your route. A drop-down list of tracks (NAT, PAC, AUS, or NOR) appears for you to choose from. 

Use a preferred arrival

Clicking the Use a preferred arrival checkbox allows you to make use of a preferred arrival in your route. A drop-down list of preferred arrivals from FOMS Menu 317 (Preferred Arrivals Program) appears for you to choose from.

Interaction 1

Interaction 1 Click the Use a specific STAR checkbox.

When you select a specific STAR from the drop-down list the procedure is automatically displayed on the map screen. The procedure is available immediately, you do not need to select the Generate button.

Use a specific STAR

Clicking the Use a specific STAR checkbox allows you to make use of STAR in your route. A drop-down list of STARs that apply to the selected runway from FOMS Menu 325 (STARs Routes Program) is made available for you to choose from.

Arrival Runway

If the Arrival Runways field in FOMS Menu 170 (Airline Parameter File) is set to Y, then the Arrival Runway drop-down list will default to Max Headwind, but you can select any of the following options:

None: Generic SIDs/STARs are used

Use specific runway: A specific runway can be selected from a drop-down list under the ORIG and/or DEST headings. The drop-down list of runways comes from FOMS Menu 107 (Runways Program).

Max Headwind: The best runway based on wind is selected from the available runways. For Max Headwind, the route generator ranks all the runways for that airport based on suitability and METAR/TAF wind.

Longest Procedure: The runway causing the longest distance is selected from the available runways. Once the route generator has chosen a SID/STAR, then for all the runways that the SID/STAR can use, the runway giving the longest procedure distance is chosen (as long as it is suitable). A similar ranking system would occur where the longest distance gives a better ranking, but unsuitability gives a lower ranking.

 

Route String Window

The Route String window allows you to enter a specific route using MTTA (Minimum Time Track Airway), DCT (Direct), and/or specific airways.

See MTTA Expansion Options on the Route String Parser page for information on MTTA options.

When selected, the informational context arrow opens a text box displaying FAA preferred routes. Selecting a route string updates the Route String window with the selected route string. If you are building a new route with another route previously stored, the route string window automatically populates with the previously stored route instead of defaulting to MTTA. This makes for easier route editing.

The Route String window can be resized by dragging the bottom right corner. 

Interaction 1

Interaction 1 Click the Comments input field.

Interaction 1

Interaction 1 Click the Apply Rules dropdown button.

You can get more information on a field or drop-down menu when you click to use it. 

Comments

Enter any comments that are applicable to the route. If the route exists as a city-pair on FOMS Menu 305 (City-Pair Routes Program), the comments entered here are added to the FOMS file.

The Comments window can be resized by dragging the bottom right corner. 

The Back, Generate, and Reset buttons are used when creating or editing a route. They will be covered in later topics.

Interaction 1

Interaction 1 Click the Apply Rules dropdown button.

Apply Rules:

Ignore: If the flight does not comply with the rules a warning or error won't be received. NOTE: This is not recommended for planning in IFPS airspace.

RAD only: When used, a country's preferred route rules are not applied to the MTTA, only RAD and NOTAMS are applied. A warning is displayed if route generation fails or if a rule is broken. NOTE: This option gives the NFP system a better chance of successfully generating a route over complex airspace.

Warn: If the flight doesn't comply with the rules a warning will be displayed in the notification box and the flight will still compute.

All: All rules are applied even if you have set rules to ignore using the Ignore Rules Configuration screen.

Error: If the flight doesn't comply with the rules the flight will not compute and will display an error.

NOTE: To configure the rules drop-down default see FOMS Menu 170.

Changing the value in the Options group also changes the Apply Rules drop-down list on the Route Group section on the Plan screen.

Interaction 1

Interaction 1 Click the Avoid Restricted dropdown button.

Interaction 1

Interaction 1 Click the Error list item.

Avoid Restricted:

The Avoid Restrict Drop-down box has the following options:  

Ignore: no warning or error is received for restricted areas.

Apply: will apply restricted area avoidance if MTTA is used to find a route, but no warning will be given if a fixed  route through a restricted area is used.

Warn: warnings are displayed if a restricted area cannot be avoided.

Error: error messages are displayed if a restricted area cannot be avoided and the route is not built and the compute  fails.

 

Interaction 1

Interaction 1 Click the Avoid UDA dropdown button.

Interaction 1

Interaction 1 Click the Ignore list item.

Avoid  UDA:

The Avoid UDA Drop-down box has the following options:

Ignore: If the flight does not avoid UDAs a warning or error won't be received. 

Warn: If  the flight does not avoid UDAs a warning will be displayed in the notification box and the flight will still compute.

Error: If  the flight does not avoid UDAs the flight will not compute and will  display an error.

Avoid NATs:

Avoid NAT Tracks - Click Avoid NATs checkbox to generate a route that avoids the North Atlantic Tracks. 

Avoid turbulence:

Use this checkbox to generate a route that avoids turbulence  using the value set in the Avoid Turb Edr field in the FOMS 170 menu. Select Y on the FOMS 170 menu in the field beside Avoid Turb Edr to make this checkbox selected by default.

Avoid icing (if flying  low):

Use this checkbox to generate a route that avoids icing  using the value set in the Avoid Icing PPI field in the FOMS 170 menu. Select Y on the FOMS 170 menu in  the field beside Avoid Icing PPI  to make this checkbox selected by default.

Avoid thunder storms:

Use this checkbox to generate a route that avoids storms using the value set in the Avoid ThunderStorm  field in the FOMS 170 menu. Select Y on the FOMS 170 menu in the field  beside Avoid ThunderStorm to make  this checkbox selected by default.

Check Permits:

If deselected, there are no warnings for missing permits when generating a flight plan or route. If selected, warnings are generated.

By default the checkbox is selected. It will be deselected if the Permit Check button is deselected in the Route group on the Plan screen.

Optimize:

Route Gener­ation Optimi­zation Method

This drop-down list allows you to select the least cost, least time or least fuel optimization method when gen­erating the route.

MFL (Maximum Flight Level):

This field allows you to enter the maximum flight level for the flight.

MTTA Factor 

This field allows you to enter a value for the MTTA factor. By default, the system loads a maximum MTTA value based on the great circle distance from the origin to the destination.

The MTTA factor determines the width of an imaginary corridor  between waypoints by which the route is constrained. The value of the factor relates the width of the corridor to the distance between waypoints. For example, an MTTA factor of 1.1 tells the system to use a corridor width that is 10% of the distance between the two waypoints at halfway between the two waypoints (as pictured here).

MTTA Factor 

This is often necessary when avoiding certain airspace using the "Must Not Use" feature.

For example:

A flight using the route string keyword MTTA from KMIA to SKBO will overfly Cuba.If you must avoid Cuban airspace, enter in the "Must Not Use" box and change the MTTA Factor to 2.

If you must avoid Cuban airspace, enter <FIR MUFH> in the Must Not Use box and change the MTTA Factor to 2.

MTTA Factor 

Your new MTTA route will avoid the Cuban FIR. You may notice a slight increase in the compute time as more airways are being searched by the MTTA routine.

If you were to leave the route factor at 1.1 the system would build a route which overflies Cuba and you would get the following warning: RG:311:Failed to comply with the rules/restrictions.