{//% unless portal.user.is_agent %} Tickets
Welcome
Login Submit a Ticket News {//% endunless %}

FOMS Menu 170 (Flight Plan Calculation Settings - Page 2)

The following will provide details for each parameter currently residing in the FOMS 170 database. Details include descriptions, available options, defaults, and system behavior once the parameter change has been saved.

RNP Check: Check required RNP values for flight legs? (Y/N). Always check airport procedure RNP values when building routes? (Y/N).

Zero RcPad Inft: When flight plan is set to “In Flight,” set reclear pad to zero? (Y/N)

CoNtm Checks: Two fields:

Produce a compute warning if a Company NOTAM is modified within the number of hours entered.

Produce a compute warning if a Company NOTAM is due to expire within the number of hours entered.

Mel Checks: This parameter consists of 4 fields:

First field options are Y (yes) or N (no). If set to Y, NFP generates an error if an MEL restriction has been broken based on the penalties for that MEL. If set to N, NFP generates a warning instead and allows a successful compute.  If blank, the same behavior as occurs.

Second field options are W (Warning), E (Error), or N (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.

Third field options are D (Departure) or A (Arrival). If set to D, NFP performs an MEL expiry check based on the flight’s ETD. If set to A, NFP performs an MEL expiry check based on the flight’s ETA.

Fourth field 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.

Auto Reclr Fuel: Options are Y (yes) or N (no). If set to Y, NFP automatically adds extra fuel for reclear requirements without forcing the you to do so. If set to N, NFP generates an error, forcing you to manually add fuel to meet  the reclear requirements. If blank, the same behavior as occurs.

Auto Arrv Fuel: Options are R (required) or T (tanker). If set to R, additional fuel added to meet a fixed arrival fuel value is included as required fuel within the fuel block. If set to T, additional fuel added to meet a fixed arrival fuel value is included as extra/tanker fuel.  There is no need for a format change if the flight plan format accommodates both the required and extra fuel values.

Auto Dept Fuel: Fuel automatically added to meet departure fuel is treated as Required or Tanker?

Ground APU Time
 Leg Max

Default EnrWx: Options are Y (yes), or N (no). If set to Y, NFP automatically provides weather and NOTAM information for stations meeting suitability criteria for the aircraft. This additional information is included in the flight package. Enroute stations are selected based on the interval (distance between points on route), and the radius (maximum distance from points on route)

Text

Description automatically generated

In this example, NFP finds a point on the route of flight every 200NM and then search within 100NM of those points for stations meeting the suitability criteria. The weather and NOTAMS for those suitable stations are added to the flight package.

If set to N, NFP does not provide any Enroute weather or NOTAMS. If blank, the same behavior as occurs.

RoundUp Fuel: When this option is selected, the system will automatically round up both ground fuel (i.e. taxi) and the total ramp fuel to even hundreds of pounds/kilograms. Options are Yes, No, and Blank. Blank is no.

TakeOff Alt Warn: Options are E (error), W (warning), and L (error except MLW). If set to E, NFP generates an error if there is a problem with the selected takeoff alternate. If set to W, NFP allows the compute to occur but generates a warning. If set to L, NFP generates an error unless the problem is due to exceeding the MLW value at the takeoff alternate.

A picture containing graphical user interface

Description automatically generated

Text

Description automatically generated with medium confidence

AIRAC Offset: Enter + or -, followed by a time value in minutes, to establish an offset from 00Z where the next AIRAC cycle becomes effective.

Island Hold Pol (reserve policy): Policy options are currently 01, 02, 03, 04, 05, 06 based on availability. If the Island Hold checkbox is selected in the NFP plan screen, NFP calculates alternate and HOLD fuels based on the default policy entered in this field. Contact NAVBLUE Support for more details.

Graphical user interface, application, Teams

Description automatically generated

Ballast in Zfw: Options are Y (yes)or N (no). If set to Y, NFP includes ballast fuel as part of the zero fuel weight. If set to N, NFP does not.  If blank, the same behavior as occurs.

Rules Enabled: Options are Y (Warn), R (RAD only), N (Ignore), orE (Error). You can manually change these options, but this parameter determines what the default setting is. If set to Y, NFP provides a warning if a rule(s) impacts the route. If set to R, NFP only considers the RAD document(s) when generating a route. If set to N, the rules are ignored and no warning/error is generated. If set to E, NFP generates an error if a rule(s) impacts the route.  If blank, the same behavior as occurs.

Graphical user interface, text, application

Description automatically generated

The Apply Rules options are located in the Options Group on the Route Screen.

Constant Mach: Options are Y (yes) or N (no). If set to Y, NFP ensures a constant Mach speed is flown through designated FIRs as specified in FOMS 570. If set to N, NFP does consider flying constant Mach speeds through designated FIRs.  If blank, the same behavior as occurs.

Note: NAT tracks are always designated as constant Mach.

Graphical user interface, text

Description automatically generated

 

Default Max Pyld: Options are Y (yes) or N (no). If set to Y,  the Payload field in NFP defaults to Maximum. If set to N, payload field remain blanks (fixed payload). If blank, the same behavior as occurs.

Max Pay Cmp: select Y (yes) or N (no) to enable max payload compare. Use the next field to select the Opt method for payload compare, Least <F>uel, <C>ost or <T>ime. The next field is used to select a performance profile to use for max payload compare. Max Payload Compare is used to instruct N-Flight Planning to always calculate max payload even if a payload has been specified.  This is an information-only value that yields a maximum-allowable zero-fuel weight that may be of use on the flight plan or certain load planning integrations.  It can also be used for alerting purposes using the Weight Check field. This increases compute times and should only be used if it is known to be required.

Max PayTolerance(maximum payload or tanker): This parameter setting impacts the payload and tankerage fuel calculations when maximum is used for both features.

The default value if blank = 200 (LBS or KGS – you choose LBS or KGS in the Aircraft Characteristics Screens).

A screenshot of a computer

Description automatically generated

How is the tolerance factor calculated?

Based on the input in this field, the tolerance impacts the number of iterations NFP takes to determine the maximum amount of payload and/or tanker fuel an aircraft can carry based on structural limits, aircraft performance, environmental factors (winds, temperature), and restrictions (FL forcing or caps, MELs, navigation equipment).

If the tolerance factor is 50, NFP tries to get a maximum payload or tanker amount as close to 50 LBS/KGS from structural limits.

Note: Keep in mind that decreasing the tolerance factor increases compute times since the engine requires more iterations to get a result. The tolerance factor can be between 1 and 200.

Default Tankerage: Options are O (Optimal), T (Table), L (Next Ramp), M (Opt Multi-Leg), or N (Fixed).

If set to O, tanker default is Optimal

If set to T, tanker default is Table

If set to L, tanker default is Next Ramp

If set to M, tanker default is Optimal Multi-Leg tanker

If set to N, tanker field remains blank - if blank Use NextRamp if advantageous to do so or use 0 Fixed Tanker if not advantageous to do so or if there is no fuel price information.

Use TOD for Hold: options are Yes or No, when Yes is selected the hold calculation uses Top Of Descent fuel flow instead of hold performance when necessary for the primary hold.

WGS84 Fuel Burns: Options are Y (yes) and N (no). If set to Y, NFP observes the WGS84 model for carbon emissions. If set to N, NFP observes the sphere model. Both options do not affect displayed distances.

Default RwyInt Wx (Aerodata integration): Options are Y (yes) or N(no). If set to Y or left blank, the RWA box displays weather data from NFP when the RWA window is opened. If set to N, all RWA fields are blank and can be filled in manually. You can leave the fields empty and send a runway request to Aerodata. Aerodata will populate the fields with their data when a runway request is sent. If set to N and you select the Default Wx button in the Runway Analysis dialog, the weather data source is from Aerodata.

Graphical user interface

Description automatically generated

RwyInt Pres. Unit choose which runway integration pressure unit to display. Options are M for millibar or I for inches of Mercury. If the field is blank the NFP system uses the same unit of measurement used in the original TAF/METAR.

Default Runways: Options are L (Longest procedure), M (Max headwind), B (Best route) or N (None). NFP Departure and Arrival Runway fields default to whichever is set in this field.

Text

Description automatically generated

This parameter must be set to M or B to enable the automatic runway selection based on valid TAFS. If the flag is set to N, functionality is disabled.

If blank, the same behavior as occurs.

This feature allows for automatic selection of runway(s) based on valid METAR and TAF information for the origin and destination based on ETD and ETA. Runways are considered based on the best SID and STAR available and weather criteria (wind speed and direction, approach minima).

NFP also chooses the best runway based on whether the runway is suitable, based on suitability checks (ACN/PCN, runway surface, minimum length), and the magnetic bearing of the runway that yields the greatest headwind component.

Note: Route optimization also has an impact on runway selection.

UI Default Rwy: Options are Y (yes) orN (no). This parameter works in conjunction with the Default Runways parameter. If set to Y, NFP shows the default as set in the Default Runways field. If set to N, you are forced to select a specific runway for both departure and arrival stations. If blank, the same behavior as occurs.

Diagram

Description automatically generated with medium confidence

Min Rwy Length: Field entry is in feet. NFP generates a warning if you select a station with a runway length lesser than the value entered in this field.

Text

Description automatically generated with low confidence

Avoid NAT track FLs: Options are Y or N. If set to Y, 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 N, NFP does allow a route to cross a NAT track at the same flight level. If blank, the same behavior as occurs.

A picture containing calendar

Description automatically generated

Domestic Data Ccs: The country code entered in this field is the is the domestic-only navigation data that an ALC is allowed to use.

MLF Override (minimum landing fuel): Options are Y (yes),N (no),or I (in-flight). If set to Y, you can lower an MLF value that overrides the default weight entered in FOMS 220 for both standard and in-flight plans. If set to N, NFP does not allow an override. If set to I, the can only override the MLF value on an in-flight plan. If blank, the same behavior as occurs.

Diagram

Description automatically generated with low confidence

MLF Addl: Add2: Blst: This parameter consists of 3 fields:

First field(Addl1) options are Y (yes) or N (no). If set to Y, NFP includes additional fuel as part of the min landing fuel requirement. If set to N, NFP does not include it.

Second field (Add2) options are Y(yes) or N (no). If set to Y, NFP adds additional HOLD as part of the min landing fuel requirement. If set to N, NFP does not include it.

Third field (Blst) options are Y (yes) or N (no). If set to Y, NFP includes ballast fuel as part of min landing fuel requirement. If set to N, NFP does not include it.

Note: If blank, the same behavior as occurs.

Respect AwyMin and Max: This parameter consists of three fields:

First field options are Y (yes), N (no), or E (error). If set to Y, NFP provides flight levels above the minimum flight levels for the airways as per FOMS 341. If set to N, NFP does not respect the minimum flight levels. If set to E, NFP generates an error if a route is planned below airway minimum flight levels.

Second field options are Y (yes), N (no), or E (error). If set to Y, NFP ensures that airway maximum flight levels are not exceeded as per FOMS 341. If set to N, NFP does not respect airway maximum flight levels. If set to E, NFP generates an error if a route is planned above airway maximum flight levels.

Third field options are Y (yes) or N (no). If set to Y, NFP respects the maximum flight levels for US jet airways. If set to N, 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.

Text, chat or text message

Description automatically generated

Apt DCT Split Dist: 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.

Org/Dst Taxi: Enter a default origin and destination taxi time in minutes. This overrides the airport taxi time.

Org/Dst Circuit: Enter a default origin and destination circuit time in minutes.

Circuit Method Org: This parameter consists of two fields:

First field options are C (calculated) or B (burn bias) for origin circuit time. If set to C, NFP moves the TOC point closer to the origin and adjusts burns accordingly. If set to B, only the burns are adjusted based on circuit time.

Second field options are C (calculated) or B (burn bias) for destination circuit time. If set to C, NFP moves the TOD point closer to the destination and adjust burns accordingly. If set to B, only the burns are adjusted based on circuit time.

Warn DCT Below Mora: Check for DCT cruise legs below MORA. Options are (Y)es, (N)o, and (E)rror.

Alt: Check for DCT cruise legs below MORA in the route to alternate. Options are (Y)es, (N)o, and (E)rror.

Mora Dft Dwn: This parameter consists of four fields:

First field options are O (off), W (weight reduction), E (escape routes), and A (auto). If set to O, NFP does not provide any escape routes. If set to W, NFP penalizes aircraft weight to meet MORA requirements (Method 1). If set to E, NFP generates escape routes (O2 or drift down – Method 2) if MORA value is higher than 10,000 feet along the route of flight. If set to A, NFP generates escape routes and if unable to do so safely, reduces aircraft weight as per Method 1.

Second field options are Y (yes) or N (no). If set to Y, NFP checks MORA for all routes including alternates and reclear but not takeoff alternate. If set to N, NFP only checks MORA for the main route.

Third field options are Y (yes) or N (no). If set to Y, NFP aborts a compute if a MORA check fails. If set to N, NFP only provides a warning.

Fourth field options are 1 (one engine out), O (off), H (half engines). If set to 1, NFP generates drift down escape routes based on one engine out performance. If set to O, NFP does not generate any drift down escape routes. If set to H, NFP generates drift down escape routes based on the number of engines divided by 2. For 3 engine aircraft, H = 2 engines out. If blank, the same behavior as occurs.

Driftdown Rule: Options are Standard and FAA.

The Standard terrain clearance option, whether using Weight Reduction or Escape Routes for driftdown, ensures a terrain clearance of 1000ft when MORA is below 5000ft, and 2000ft when MORA is at or above 5000ft.

The FAA terrain clearance option ensures terrain clearance of 1000ft for Weight Reduction and 2000ft for Escape Routes, regardless of MORA.

Talt Drift Down: Options are Y (yes), N (no), and E (error). If set to Y, NFP provides MORA checking for the takeoff alternate route and warns if the route goes below MORA. If set to N, NFP does not provide this check. If set to E, NFP aborts a compute if the takeoff alternate route goes below MORA. Keep in mind that alternate routes are computed using 1EO performance.

Text

Description automatically generated

Escape Use Awy Min: Options are Y (yes) or N (no). If set to Y, NFP ensures that the escape routes generated for oxygen and drift down respect airway minimum flight levels as per FOMS 341. If set to N, NFP generates escape routes which respect MORA values instead of airway minimum flight levels. If blank, the same behavior as occurs.

O2 Escape All Rtes: Options are Y (yes) or N (no). If set to Y, NFP verifies whether oxygen escape routes should be generated for all routes including alternate route(s), reclear route, and takeoff alternate route. If set to N, NFP does not verify whether escape routes are required. If field is blank, NFP only checks the main route (origin – destination).

DCT Escape Routes: Allow the system to use DCT legs when generating escape routes. Options are Y/N/Blank. Blank renders the same result as N.

 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.