What is the minimum validation an operator should perform on every RNP AR APCH procedure before using it in IMC?

The operator should validate every RNP AR APCH procedure before using it in IMC to ensure compatibility with their aircraft and to ensure the resulting path matches the published procedure. As a minimum, the operator should: (1) compare the navigation data for the procedure(s) to be loaded into the FMS with the published procedure; (2) validate the loaded navigation data for the procedure, either in an FSTD or in the actual aircraft in VMC, flying the entire procedure to ensure the path is flyable, does not have any apparent lateral or vertical path disconnects, and is consistent with the published procedure; (3) once validated, retain a copy of the validated navigation data for comparison with subsequent data updates; and (4) for published procedures where FOSA demonstrated the procedure is not in a challenging operational environment, the flight or FSTD validation may be credited from already validated equivalent RNP AR APCH procedures.

How should an operator validate the loaded navigation data for an RNP AR APCH procedure?

The operator should validate the loaded navigation data for the procedure either in an FSTD or in the actual aircraft in VMC. The depicted procedure on the map display should be compared to the published procedure, and the entire procedure should be flown to ensure the path is flyable, does not have any apparent lateral or vertical path disconnects, and is consistent with the published procedure.

AMC3 SPA.PBN.105(d) PBN operational approval

Q: What should an operator do if an aircraft system required for RNP AR APCH operations is modified?

The operator should assess the need for a validation of the RNP AR APCH procedures with the navigation database and the modified system. This may be accomplished without any direct evaluation if the manufacturer verifies that the modification has no effect on the navigation database or path computation. If no such assurance from the manufacturer is available, the operator should conduct initial data validation with the modified system.

Navigate / EASA

Ask question Discover more Add to collection

AMC3 SPA.PBN.105(d) PBN operational approval

ED Decision 2016/020/R

NAVIGATION DATABASE MANAGEMENT

(a) The operator should validate every RNP AR APCH procedure before using the procedure in instrument meteorological conditions (IMC) to ensure compatibility with their aircraft and to ensure the resulting path matches the published procedure. As a minimum, the operator should:

(1) compare the navigation data for the procedure(s) to be loaded into the FMS with the published procedure.

(2) validate the loaded navigation data for the procedure, either in an FSTD or in the actual aircraft in VMC. The depicted procedure on the map display should be compared to the published procedure. The entire procedure should be flown to ensure the path is flyable, does not have any apparent lateral or vertical path disconnects and is consistent with the published procedure.

(3) Once the procedure is validated, a copy of the validated navigation data should be retained for comparison with subsequent data updates.

(4) For published procedures, where FOSA demonstrated that the procedure is not in a challenging operational environment, the flight or FSTD validation may be credited from already validated equivalent RNP AR APCH procedures.

(b) If an aircraft system required for RNP AR APCH operations is modified, the operator should assess the need for a validation of the RNP AR APCH procedures with the navigation database and the modified system. This may be accomplished without any direct evaluation if the manufacturer verifies that the modification has no effect on the navigation database or path computation. If no such assurance from the manufacturer is available, the operator should conduct initial data validation with the modified system.

(c) The operator should implement procedures that ensure timely distribution and insertion of current and unaltered electronic navigation data to all aircraft that require it.

Details

Source-Title: AMC3 SPA.PBN.105(d) PBN operational approval View latest amendments

Erulesid: ERULES-1963177438-13035 Compare versions

Domain: Air operations

Applicabilitydate: 3 August, 2016

Entryintoforcedate: 3 August, 2016

Regulatorysource: ED Decision 2016/020/R Navigate

Regulatorysubject: Part-SPA

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

Parentir: SPA.PBN.105 PBN operational approval

Origin: EASA

Category: EAR