AMC3 NCC.OP.116 Performance-based navigation

Navigate / EASA

Ask question Discover more Add to collection

AMC3 NCC.OP.116 Performance-based navigation – aeroplanes and helicopters

ED Decision 2016/017/R

MANAGAMENT OF THE NAVIGATION DATABASE

(a) For RNAV 1, RNAV 2, RNP 1, RNP 2, and RNP APCH, the flight crew should neither insert nor modify waypoints by manual entry into a procedure (departure, arrival or approach) that has been retrieved from the database. User-defined data may be entered and used for waypoint altitude/speed constraints on a procedure where said constraints are not included in the navigation database coding.

(b) For RNP 4 operations, the flight crew should not modify waypoints that have been retrieved from the database. User-defined data (e.g. for flex-track routes) may be entered and used.

(c) The lateral and vertical definition of the flight path between the FAF and the missed approach point (MAPt) retrieved from the database should not be revised by the flight crew.

Details

Source-Title: AMC3 NCC.OP.116 Performance-based navigation - aeroplanes and helicopters View latest amendments

Erulesid: ERULES-1963177438-13218 Compare versions

Domain: Air operations

Applicabilitydate: 3 August, 2016

Entryintoforcedate: 3 August, 2016

Regulatorysource: ED Decision 2016/017/R Navigate

Regulatorysubject: Part-NCC

Typeofcontent: AMC to IR (Acceptable means of compliance to implementing rule)

Parentir: NCC.OP.116 Performance-based navigation - aeroplanes and helicopters

Origin: EASA

Category: EAR