#

RNP/PBN Procedures Design using FPDAM

The RNP (Required Navigation Performance) / PBN (Performance Based Navigation) tools have been a part of FPDAM since the release of version 7.0 in 2001.
The applications have been developed in compliance with ICAO (Docs 8168 and 9368) regulations as well as FAA's TERPS criteria, which covers more cases than the ICAO Docs.


Procedures Design using RNP Criteria

FPDAM has specific tools for the design of RNP procedures in the following phases of flight:


  • En-route
  • Standard Arrival (STAR)
  • Holding
  • Initial, Intermediate, Final, Missed Approach phases
  • Departures

The protection areas for all phases of flight are automatically drawn using the RNP value loaded from the WP. All the constructors of protection areas have been developed with a high level of flexibility in order to be able to design procedures with different RNP values. The worst parameters have been set as default, however the user can customize the construction of the protection areas.

The user can change the RNP value for each one of the WP, the 1/2 area width and the type of the turn. Available turns are:


  • Fly-over with path code TF
  • Fly-over with path code DF
  • Fixed Radius
  • Fly-by

In case of a turn on the Missed Approach Point, the system can manage the ASAP turn (even if not foreseen by ICAO regulations).
The designer is guided in the definition of the turns, for instance the system will suggest to use a fly-over in case of turn on a Missed Approach Point instead of fly-by. However, the last choice is always the designer's.
The WP are placed in a 3D environment, thus several checks can be conducted during the design of the tracks (gradient, angle between segments etc).


Obstacle Evaluation

FPDAM can evaluate the minima for all phases of flight using Digital Terrain Models (DTM), Obstacles (the system can import features from CRM format, ASCII files, from the active working file, from the DVOF format etc). Connection to an external database as also possible.
The terrain data can be imported from ASCII file, from the NIMA DTED files, from scanned paper and other "standard" formats.
The MOC value is automatically loaded according to the procedure type and the phase of flight. OCA/OCH and DA/DHY are automatically computed and stored in the database.


SSA Data

During the construction of the procedure the SSA (SID/STAR/Approach) data are automatically saved in the FPDAM database. The data storage has been developed in accordance with the ARINC format.
The user can add attributes to each feature of the working file. The Path and Termination codes can be added during the procedure elements tagging. The SSA data can be exported/imported from the FPDAM system to the IDS AeroDB via XML/AIXM format.