Display Taxi Fuel: Display taxi fuel instead of time. Options are Y (yes), N (no) or F (only for Fixed Taxi aircraft). This impacts the taxi fuel default shown in the plan screen. When set to Y, taxi fuel will show in lbs/kgs instead of time. When set to N, taxi fuel will show as a time value in minutes for aircraft configured with taxi fuel as an hourly rate in aircraft characteristics. When set to F, default taxi fuel will show in lbs/kgs only for aircraft configured with taxi fuel as a fixed rate in aircraft characteristics.
Orig Taxi Time: Enter the default origin taxi time in minutes; this value overrides airport taxi time.
Dest Taxi Time: Enter the default destination taxi time in minutes; this value overrides airport taxi time.
Orig Circuit Time: Enter the default origin circuit time in minutes. Circuit time added does not apply to alternates.
Dest Circuit Time: Enter the default destination circuit time in minutes. Circuit time added does not apply to alternates.
Orig Circuit Method: Options are Calculated or Burn (burn bias) for origin circuit time. If set to Calculated, NFP moves the TOC point closer to the origin and adjusts burns accordingly. If set to Burn, only the burns are adjusted based on circuit time.
Dest Circuit Method: Options are Calculated or Burn (burn bias) for destination circuit time. If set to Calculated, NFP moves the TOD point closer to the destination and adjust burns accordingly. If set to Burn, only the burns are adjusted based on circuit time.
Unsuitable Airport Error: Treat unsuitable airports flagged from the menu as a compute error. Options are Yes or No.
Use WGS84 Model: Options are Yes and No. If set to Yes, NFP observes the WGS84 model for carbon emissions. If set to No, NFP observes the sphere model. Both options do not affect displayed distances.
Constant Mach: Options are Yes or No. If set to Yes, NFP ensures a constant Mach speed is flown through designated FIRs as specified in FOMS 570. If set to No, NFP does consider flying constant Mach speeds through designated FIRs. If blank, the same behavior as Yes occurs.
Note: NAT tracks are always designated as constant Mach.
Airport DCT Distance: When a distance value in NM is entered, NFP creates pseudo waypoints at the appropriate distance/interval that appear in the nav log for segments origin –TOC and TOD – destination. This provides the aircrew with valuable climb and descent information between pseudo waypoints that would normally not be available.
These pseudo waypoints appear in the route log as pure waypoints (11 character lat/longs). If the field is blank the feature is not enabled.
Burn Flight Levels
Stepclimb Distance: If this field is blank the default is 300NM. Any other distance value entered forces NFP to omit stepclimbs within this set distance from destination.
NAT Stepclimb: Options are Yes or No. If Yes is entered, NFP allows stepclimbs for routes planned while on the North Atlantic track structure. If No is selected, no step climbs are allowed. If field is blank the default is the same as No and stepclimb on the NAT tracks does not occur.
Avoid NAT Flight Levels: Options are Yes or No. If set to Yes, NFP does not allow a route to fly at the same flight level as a NAT track if crossing it. FOMS 330 shows available flight levels for the NATS. If set to No, NFP does allow a route to cross a NAT track at the same flight level. If blank, the same behavior as No occurs.
Respect Airway Min: Options are Yes, No, or Error. If set to Yes, NFP provides flight levels above the minimum flight levels for the airways as per FOMS 341. If set to No, NFP does not respect the minimum flight levels. If set to Error, NFP generates an error if a route is planned below airway minimum flight levels.
Respect Airway Max: Options are Yes, No, or Error. If set to Yes, NFP ensures that airway maximum flight levels are not exceeded as per FOMS 341. If set to No, NFP does not respect airway maximum flight levels. If set to Error, NFP generates an error if a route is planned above airway maximum flight levels.
Respect USA Jet Awy Max: Options are Yes or No. If set to Yes, NFP respects the maximum flight levels for US jet airways. If set to No, NFP allows computes above US jet airway maximum flight levels.
Note: When turned on, this parameter ensures that airway minimum and maximum flight levels are respected based on FOMS 341. Keep in mind that setting these flags to N may have flight safety repercussions.
Check RAIM Automatically: If checked, NFP automatically validates the route post compute. If unchecked, you must click on the RAIM Validate button manually.
Check ADSB Automatically: If checked, NFP automatically validates the route post compute.
Check ADSB on main route only: If checked, ADSB validation is performed on the main route only. Unchecked also validates alternate route.
12555 Exemption: If the check box is selected, it specifies that the operator holds Exemption 12555.
Note: The interval offset and angle information will be used for ADSB check as well as RAIM check.
Interval: Enter a value in minutes. If blank, default = 1 minute. If interval = 3 and flight time is 39 minutes between two waypoints, the RAIM service performs a check every 3 minutes of flight time between waypoints. Service = DWI GRPS on-demand.
Route Offset Time (en route): – Enter a value in minutes. If 15 is entered, a RAIM check is performed at ETD–15 mins, ETD, and ETD+15 mins (once per Offset count – default count is 0 = for ETD only)
Route Offset Count: Enter a numerical value to choose the number of time slots a RAIM check is performed as shown in the example below. Default is 0.
So for OffsetCount = 3 and OffsetTime 15 mins would mean 7 slot times….
Point Offset Minutes (terminal area - arrival end): Enter a value in minutes. If blank, default is 30 minutes. This is the size of the RAIM calculation window for the arrival station.
If set to 60 minutes as shown above, a RAIM calculation is performed for a window that consists of ETA-60 minutes to ETA+60 minutes (120 minutes window) based on destination station.
Mask Angle: A line of sight angle between aircraft position/flight level and available satellite(s). Default is 10 degrees if field left blank. This is designed to filter out low angle satellites. Keep in mind that a lower mask angle may impact validation especially when departing from or arriving into a station surrounded by high terrain since mountains may obscure line of sight with available satellites. Entry range is -20.0 to 25.0 degrees.
Check Curfew: Options are Yes or No. If Y is entered, the curfew warning module is activated.
NFP provides a warning if a curfew is broken at origin or destination. Curfew times are stored in the FOMS 105 menu (Airports) or the FOMS 366 menu (Curfew times) databases. Curfew times entered in FOMS 366 overide the ones in FOMS 105.
If No is entered, the system will not alert you if curfews times have not been met. All curfew times entered in FOMS 105 or FOMS 366 are in local time.
If field is blank, curfew times will not be considered or warned against.
Affects OptCI: Options are Yes and No. This option allows NFP to increase CI cruise profile or slow it down when OPT CI is used to avoid breaking a curfew. Yes changes the OPT CI speed selection to meet the curfew times - a warning is displayed indicating that the best profile was used so that the curfew was not violated. No does not change OPT CI - a warning is displayed on the computed flight to indicate that arrival time breaks the curfew of the destination airport.
Start/End Buffer: These fields allow you to enter a start and end buffer time around the curfew set in FOMS 336, a warning message is displayed to indicate that curfew has been violated, the curfew and buffer times are shown.
The buffer time on curfews set here are be applied to the SID and STAR Approach Validity Times, and Navigation Data as well as the start and end time of the curfew.
Restriction errors: Options are Yes or No. If set to Yes, NFP generates an error if an MEL restriction has been broken based on the penalties for that MEL. If set to No, NFP generates a warning instead and allows a successful compute. If blank, the same behavior as Yes occurs.
Check Expiry: Options are Warning, Error, or No Check. Based on selection, NFP verifies if an MEL is expired. If it is, NFP generates either a warning, abort compute, or ignores the expired MEL.
Check Method: Options are Departure or Arrival. If set to Departure, NFP performs an MEL expiry check based on the flight’s ETD. If set to Arrival, NFP performs an MEL expiry check based on the flight’s ETA.
ETD/ETA Offset: Entry is in hours. Enter the number of hours you would like NFP to do an MEL expiry check after ETD or ETA based on the settings in the third field (Departure/Arrival + X hours). This buffer allows NFP to verify whether an MEL expires within this buffer period.