Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
CS ACNS.C.PBN.640 RNP AR departures - Functional Requirements
Available versions for ERULES-1963177438-16516
ED Decision 2019/011/R
found in: GM Remote Aerodrome Air Traffic Services (ED 2019/004/R) Issue 2 (Jul 2020)
Version
GM Remote Aerodrom... (Jul 2020)
Section
Share
Version
Show details
Hide details
Version
CS ACNS.C.PBN.640 RNP AR departures – Functional Requirements ED Decision 2019/011/R (See [AMC1 ACNS.C.PBN.640](#_DxCrossRefBm573002610) and [GM1 ACNS.C.PBN.640](#_DxCrossRefBm573002609)) The RNP system provides the following capabilities to support RNP AR departure procedures: (a) The RNP system allows loading and execution of a flight plan where the initial fix of the RNP AR DP defined path is placed at or just beyond the approach end of the take-off runway. (b) The RNP system provides lateral path guidance not later than when reaching 50 feet above the departure runway. (c) The RNP system is capable of executing an RF leg where the first fix defining the RF leg begins at the departure end of the runway. (d) The RNP system provides a means for the flight crew to confirm availability of GNSS for aircraft positioning immediately prior to take-off. (e) The INS position is automatically updated upon pressing the take-off/go-around (TOGA) button or provide the ability to manually initiate a position update during ground operations immediately prior to take-off. [Issue: CS-ACNS/2]