Turbulence Severity Range
There are three fields that allow you to set a turbulence range and these values are displayed on the flight plan. The fields are:
Light Turbulence TDR: Enter a light turbulence value - between 0.15 and 0.25. This value cannot be higher than the Moderate Turbulence value.
Moderate Turbulence TDR: Enter a moderate turbulence value - between 0.25 and 0.45. This value cannot be lower than the light value or higher than the severe turbulence value.
Severe Turbulence TDR: Enter a severe turbulence value - greater or equal to .55. This value cannot be lower than the light value or the moderate turbulence value.
This criteria impacts station colors displayed on the map as well as weather criteria for NFP features requiring suitability checks ( escape routes, auto-ETOPS selection, enroute alternates, etc…..)
Ceiling values are to be entered in 100’s of feet and visibility values are to be entered in meters.
Station Colors on NFP Map
These entries control the color of stations that are displayed on the NFP map. Once the user has entered the required minimum ceiling, warning, and visibility values in FOMS 170, stations appear on the NFP map in the appropriate color, based on the valid METARS/TAFS for the flight’s ETD/ETA.
Blue - FOMS 170 has not been configured for color coding – no entries
Green – METAR/TAF weather limits are above warning values entered
Yellow – METAR/TAF weather limits are below warning values but above minimum
Red – METAR/TAF weather limits are below minimum values entered.
The system will use the “worse” of the ceiling and visibility values taken from the METARS and TAFS when color coding stations. Example: If the ceiling is above the warning and minimum value entered (green) but the visibility is below the warning value but above the minimum value entered, the station is displayed as yellow.
Ceiling Buffer and Visibility Buffer: values entered for ceiling and visibility are added to the default weather minima and/or approach minima values for stations with runways greater than 7000 feet in length when certain conditions are met (see Criteria).
Criteria (Airport use)
While checking for weather suitability, the N-Flight Planning system looks at the planned airports (including the number of alternates) and references the criteria below to determine whether minima values need to be added. Next, N-Flight Planning determines whether “Normal” or “Alternate” scenarios are to be used based on the Airport Usage, number of alternates specified for that flight, and the number of engines on the aircraft.
Note: Keep in mind that only stations with runways longer than 7000 feet will be considered.
If the N-Flight Planning system determines that the flight meets the “Alternate” criteria, next it looks at the number of runways for the airport(s) where the flight could potentially land. N-Flight Planning also needs to know how many separate runways are available at these airports so that the correct minima is applied if required.
The Airports database supplies this information, see below.
If the system determines that it should use the Alternate scenario, then it looks at the number of Runways for the Airport. Whether an airport has separate runways will be determined based on number of available runways at ETA. A new field, called Separate, has been added to the FOMS 105 menu. This field lists the number of separate runways.
Default Stations: If set to checked, 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)
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 unchecked, NFP does not provide any Enroute weather or NOTAMS.
If set, these fields will auto-populate the historical wind fields in the Plan screen.
You can define horizontal and vertical tolerances around your route of flight for NOTAM inclusion in flight packages. With this feature, you can define an airport radius for inclusion of any relevant FIR NOTAMs to your flight package. Any NOTAMs outside of the tolerances should not be included in the flight package. The Vertical Tolerance field is in FL (e.g. Tolerance of FL50 and a cruise FL350 creates a vertical tunnel between FL300 and FL400). The Horizontal Tolerance field is in NM from centreline. The Airport Radius field is in NM.
Note: With this feature, when flying close to an FIR border the system may pick up NOTAMs from FIRs that are not flown because the NOTAM is within the tolerances of the tunnel.