You are on page 1of 4

1 NAVBLUE ACADEMY – TRAINING MANUAL

1 Introduction

20-5 Enhancements
N-FP 20-5 Enhancements
We estimate that this will take 2 minutes to complete.
AIRAC Data
The 20-5 release does not include code that changes navigation data records.
Release Deployment Window Information
N-Flight Planning relies on an interdependency of systems which use common data
formats and network communication. In all but the most exceptional cases, a
common release version must be installed on all N-Flight Planning systems.The most
prevalent constraint placed on system upgrades are AIRAC data processing
boundaries.

Failure to update an N-Flight Planning client system within the same AIRAC
processing cycle as the centrally managed systems carries with it the likelihood that
navigation data and/or other distributed content will no longer be replicated and
current.

The consequence of failing to deploy a release within the window is that the client
system is exposed to potential navigation data inconsistencies that are not present
on the centrally managed systems. N-Flight Planning management may notify a
customer that their navigation data cannot be certified or guaranteed if the client
system is not upgraded during the normal deployment window.
2 NAVBLUE ACADEMY – TRAINING MANUAL

2 Detailed Explanation

NFP-476 – Include Required Additional in Min Landing


When determining whether to include additional fuel in their minimum landing fuel,
you can exclude additional fuels flagged as Optional in the Plan Screen. The option
is found in the Airline Code Parameters (FOMS 170) menu, under the Minimum
Landing Fuel section.
3 NAVBLUE ACADEMY – TRAINING MANUAL
4 NAVBLUE ACADEMY – TRAINING MANUAL

NFP-1357 – Airport Approach Minima – Optional Suffix and Transition


Waypoint
When adding or editing the entries in the Airport Approach Minima menu, the fields
for approach suffix and transition waypoint are no longer required. Entries without
data in the optional fields apply to all matching approaches.
NFP-3153 – Flight Papers Archive (FOMS 375) – Archive Messages Received
from ATC in “ATC Message” Instead of “Messages”
As part of the changes required to implement the new feature ATC Transmissions
in InfoView, the location in which received ATC messages (ACK/REJ) are
archived is changed from “Messages” to “ATC Message.”

Furthermore, some message types which were not archived before, such as SAM,
SRM, and GRL messages are not part of the records.

You might also like