RSickenberg · April 7, 2025 10:53
diff --git a/062_07.txt b/062_07.txt
 01.01 PBN Principles
 01 List the factors used to define area navigation (RNAV) or required navigation performance (RNP) system performance requirements (accuracy, integrity and continuity).
 02 State that these RNAV and RNP systems are necessary to optimise the utilisation of available airspace.
 03 State that it is necessary for flight crew and air traffic controllers to be aware of the on-board RNAV or RNP system capabilities in order to determine whether the performance of the RNAV or RNP system is appropriate for the specific airspace requirements.
 04 Define accuracy as the conformance of the true position and the required position.
 05 Define continuity as the capability of the system to perform its function without unscheduled interruptions during the intended operation.
 06 Define integrity as a measure of the trust that can be placed in the correctness of the information supplied by the total system. Integrity includes the ability of a system to provide timely and valid alerts to the user.
 07 State that, unlike conventional navigation, PBN is not sensor-specific.
 08 Explain the difference between raw data and computed data.
 09 Define availability as the percentage of time (annually) during which the system is available for use.

 01.02 PBN Components
 01 List the components of PBN as navigational aid (NAVAID) infrastructure, navigation specification and navigation application.

 01.03 PBN Scope
 01 State that in oceanic/remote, en-route and terminal phases of flight, PBN is limited to operations with linear lateral performance requirements and time constraints.
 02 State that in the approach phases of flight, PBN accommodates both linear and angular laterally guided operations, and explain the difference between the two.

 02.01 Area Navigation (RNAV) and Required Navigation Performance (RNP)
 01 State the difference between RNAV and RNP in terms of the requirement for on-board performance monitoring and alerting.

 02.02 Navigation Functional Requirements
 01 List the basic functional requirements of the RNAV and RNP specifications (continuous indication of lateral deviation, distance/bearing to active waypoint, GS or time to active waypoint, navigation data storage and failure indication).

 02.03 Designation of RNP and RNAV Specifications
 01 Interpret X in RNAV X or RNP X as the lateral navigation (LNAV) accuracy (total system error) in nautical miles, which is expected to be achieved at least 95 % of the flight time by the population of aircraft operating within the given airspace, route or procedure.
 02 State that aircraft approved to the more stringent accuracy requirements may not necessarily meet some of the functional requirements of the navigation specification that has a less stringent accuracy requirement.
 03 State that RNAV 10 and RNP 4 are used in the oceanic/remote phase of flight.
 04 State that RNAV 5 is used in the en-route and arrival phases of flight.
 05 State that RNAV 2 and RNP 2 are also used as navigation specifications.
 06 State that RNP2 is used in the en-route and oceanic/remote phases of flight.
 07 State that RNAV2 might be used in the en-route continental, arrival and departure phases of flight.
 08 State that RNAV 1 and RNP 1 are used in the arrival and departure phases of flight.
 09 State that required navigation performance approach (RNP APCH) is used in the approach phase of flight.
 10 State that required navigation performance authorisation required approach (RNP AR APCH) is used in the approach phase of flight.
 11 State that RNP 0.3 navigation specification is used in all phases of flight except for oceanic/remote and final approach, primarily for helicopters.
 12 State that RNAV 1, RNP 1 and RNP 0.3 may also be used in en-route phases of low-level instrument flight rule (IFR) helicopter flights.

 03.03 Specific RNAV and RNP System Functions
 01 Recognise the definition of radius to fix (RF) leg.
 02 Recognise the definition of a fixed radius transition (FRT).
 03 State the importance of respecting the flight director guidance and the speed constraints associated with an RF procedure.
 04 Explain the difference between a fly-by-turn and a fly - over.
 05 State that the Aeronautical Radio, Incorporated (ARINC) 424 path terminators set the standards for coding the SIDs, STARs and instrument approach procedures (IAPs) from the official published government source documentation into the ARINC navigation database format.
 06 State that the path terminators define a specific type of termination of the previous flight path.
 07 Define the term ‘offset flight path’.

 04.01 Performance-Based Navigation (PBN) Principles
 01 Define ‘path definition error’ (PDE).
 02 Define ‘flight technical error’ (FTE) and state that the FTE is the error in following the prescribed path, either by the auto-flight system or by the pilot.
 03 Define ‘navigation system error’ (NSE) and state that the accuracy of a navigation system may be referred to as NSE.
 04 Define ‘total system error’ (TSE) and state that the geometric sum of the PDE, FTE and NSE equals the TSE.
 05 State that navigation accuracy depends on the TSE.

 04.02 On-Board Performance Monitoring and Alerting
 01 State that on-board performance monitoring and alerting of flight technical errors is managed by on-board systems or flight crew procedures.
 02 State that on-board performance monitoring and alerting of navigation system errors is a requirement of on-board equipment for RNP.
 03 State that, dependent on the navigation sensor, the estimated position error (EPE) is compared with the required navigation specification.
 04 Explain how a navigation system assesses the EPE.
 05 Give an example of how the loss of the ability to operate in RNP airspace may be indicated by the navigation system.
 06 State that on-board performance monitoring and alerting of path definition error is managed by gross reasonableness checks of navigation data.

 04.03 Abnormal Situations
 01 State that abnormal and contingency procedures are to be used in case of loss of the PBN capability.

 04.04 Database Management
 01 State that, unless otherwise specified in the operations documentation or acceptable means of compliance (AMCs), the navigational database must be valid for the current aeronautical information regulation and control (AIRAC) cycle.

 05.01 RNAV 10
 01 State that RNAV 10 requires that aircraft operating in oceanic and remote areas be equipped with at least two independent and serviceable long-range navigation systems (LRNSs) comprising an INS, an inertial reference system (IRS)/flight management system (FMS) or a GNSS.
 02 State that operators may extend their RNAV10 navigation capability time by updating

 05.02 RNAV 5
 01 State that manual data entry is acceptable for RNAV 5.

 05.03 RNAV 1/RNAV 2/RNP 1/RNP 2
 01 State that pilots must not fly an RNAV 1, RNAV 2, RNP 1 or RNP 2 standard instrument departure (SID) or standard instrument arrival (STAR) unless it is retrievable by route name from the on-board navigation database and conforms to the charted route.
 02 State that the route may subsequently be modified through the insertion (from the database) or deletion of specific waypoints in response to ATC clearances.
 03 State that the manual entry, or creation of new waypoints by manual entry, of either latitude and longitude or place/bearing/distance values is not permitted.

 05.05 Required Navigation Performance Approach (RNP APCH)
 01 State that pilots must not fly an RNP APCH unless it is retrievable by procedure name from the on-board navigation database and conforms to the charted procedure.
 02 State that an RNP APCH to LNAV minima is a non- precision IAP designed for two-dimensional approach operations.
 03 State that an RNP APCH to lateral navigation (LNAV)/vertical navigation (VNAV) minima has lateral guidance based on GNSS and vertical guidance based on either SBAS or barometric vertical navigation (Baro- VNAV).
 04 State that an RNP APCH to LNAV/VNAV minima may only be conducted with vertical guidance certified for the purpose.
 05 Explain why an RNP APCH to LNAV/VNAV minima based on Baro-VNAV may only be conducted when the aerodrome temperature is within a promulgated range if the barometric input is not automatically temperature- compensated.
 06 State that the correct altimeter setting is critical for the safe conduct of an RNP APCH using Baro-VNAV.
 07 State that an RNP APCH to LNAV/VNAV minima is a three-dimensional operation.
 08 State that an RNP APCH to localiser performance with vertical guidance (LPV) minima is a three-dimensional operation.
 09 State that RNP APCH to LPV minima requires a final approach segment (FAS) data block.
 10 State that RNP approaches to LPV minima require SBAS.
 11 State that the FAS data block is a standard data format to describe the final approach path.

 05.06 Required Navigation Performance Authorisation Required Approach (RNP AR APCH)
 01 State that RNP AR APCH requires authorisation.

 05.07 Advanced Required Navigation Performance (A-RNP)
 01 State that A-RNP incorporates the navigation specifications RNAV 5, RNAV 2, RNAV 1, RNP 2, RNP 1 and RNP APCH.
	01.01 PBN Principles
	01 List the factors used to define area navigation (RNAV) or required navigation performance (RNP) system performance requirements (accuracy, integrity and continuity).
	02 State that these RNAV and RNP systems are necessary to optimise the utilisation of available airspace.
	03 State that it is necessary for flight crew and air traffic controllers to be aware of the on-board RNAV or RNP system capabilities in order to determine whether the performance of the RNAV or RNP system is appropriate for the specific airspace requirements.
	04 Define accuracy as the conformance of the true position and the required position.
	05 Define continuity as the capability of the system to perform its function without unscheduled interruptions during the intended operation.
	06 Define integrity as a measure of the trust that can be placed in the correctness of the information supplied by the total system. Integrity includes the ability of a system to provide timely and valid alerts to the user.
	07 State that, unlike conventional navigation, PBN is not sensor-specific.
	08 Explain the difference between raw data and computed data.
	09 Define availability as the percentage of time (annually) during which the system is available for use.

	01.02 PBN Components
	01 List the components of PBN as navigational aid (NAVAID) infrastructure, navigation specification and navigation application.

	01.03 PBN Scope
	01 State that in oceanic/remote, en-route and terminal phases of flight, PBN is limited to operations with linear lateral performance requirements and time constraints.
	02 State that in the approach phases of flight, PBN accommodates both linear and angular laterally guided operations, and explain the difference between the two.

	02.01 Area Navigation (RNAV) and Required Navigation Performance (RNP)
	01 State the difference between RNAV and RNP in terms of the requirement for on-board performance monitoring and alerting.

	02.02 Navigation Functional Requirements
	01 List the basic functional requirements of the RNAV and RNP specifications (continuous indication of lateral deviation, distance/bearing to active waypoint, GS or time to active waypoint, navigation data storage and failure indication).

	02.03 Designation of RNP and RNAV Specifications
	01 Interpret X in RNAV X or RNP X as the lateral navigation (LNAV) accuracy (total system error) in nautical miles, which is expected to be achieved at least 95 % of the flight time by the population of aircraft operating within the given airspace, route or procedure.
	02 State that aircraft approved to the more stringent accuracy requirements may not necessarily meet some of the functional requirements of the navigation specification that has a less stringent accuracy requirement.
	03 State that RNAV 10 and RNP 4 are used in the oceanic/remote phase of flight.
	04 State that RNAV 5 is used in the en-route and arrival phases of flight.
	05 State that RNAV 2 and RNP 2 are also used as navigation specifications.
	06 State that RNP2 is used in the en-route and oceanic/remote phases of flight.
	07 State that RNAV2 might be used in the en-route continental, arrival and departure phases of flight.
	08 State that RNAV 1 and RNP 1 are used in the arrival and departure phases of flight.
	09 State that required navigation performance approach (RNP APCH) is used in the approach phase of flight.
	10 State that required navigation performance authorisation required approach (RNP AR APCH) is used in the approach phase of flight.
	11 State that RNP 0.3 navigation specification is used in all phases of flight except for oceanic/remote and final approach, primarily for helicopters.
	12 State that RNAV 1, RNP 1 and RNP 0.3 may also be used in en-route phases of low-level instrument flight rule (IFR) helicopter flights.

	03.03 Specific RNAV and RNP System Functions
	01 Recognise the definition of radius to fix (RF) leg.
	02 Recognise the definition of a fixed radius transition (FRT).
	03 State the importance of respecting the flight director guidance and the speed constraints associated with an RF procedure.
	04 Explain the difference between a fly-by-turn and a fly - over.
	05 State that the Aeronautical Radio, Incorporated (ARINC) 424 path terminators set the standards for coding the SIDs, STARs and instrument approach procedures (IAPs) from the official published government source documentation into the ARINC navigation database format.
	06 State that the path terminators define a specific type of termination of the previous flight path.
	07 Define the term ‘offset flight path’.

	04.01 Performance-Based Navigation (PBN) Principles
	01 Define ‘path definition error’ (PDE).
	02 Define ‘flight technical error’ (FTE) and state that the FTE is the error in following the prescribed path, either by the auto-flight system or by the pilot.
	03 Define ‘navigation system error’ (NSE) and state that the accuracy of a navigation system may be referred to as NSE.
	04 Define ‘total system error’ (TSE) and state that the geometric sum of the PDE, FTE and NSE equals the TSE.
	05 State that navigation accuracy depends on the TSE.

	04.02 On-Board Performance Monitoring and Alerting
	01 State that on-board performance monitoring and alerting of flight technical errors is managed by on-board systems or flight crew procedures.
	02 State that on-board performance monitoring and alerting of navigation system errors is a requirement of on-board equipment for RNP.
	03 State that, dependent on the navigation sensor, the estimated position error (EPE) is compared with the required navigation specification.
	04 Explain how a navigation system assesses the EPE.
	05 Give an example of how the loss of the ability to operate in RNP airspace may be indicated by the navigation system.
	06 State that on-board performance monitoring and alerting of path definition error is managed by gross reasonableness checks of navigation data.

	04.03 Abnormal Situations
	01 State that abnormal and contingency procedures are to be used in case of loss of the PBN capability.

	04.04 Database Management
	01 State that, unless otherwise specified in the operations documentation or acceptable means of compliance (AMCs), the navigational database must be valid for the current aeronautical information regulation and control (AIRAC) cycle.

	05.01 RNAV 10
	01 State that RNAV 10 requires that aircraft operating in oceanic and remote areas be equipped with at least two independent and serviceable long-range navigation systems (LRNSs) comprising an INS, an inertial reference system (IRS)/flight management system (FMS) or a GNSS.
	02 State that operators may extend their RNAV10 navigation capability time by updating

	05.02 RNAV 5
	01 State that manual data entry is acceptable for RNAV 5.

	05.03 RNAV 1/RNAV 2/RNP 1/RNP 2
	01 State that pilots must not fly an RNAV 1, RNAV 2, RNP 1 or RNP 2 standard instrument departure (SID) or standard instrument arrival (STAR) unless it is retrievable by route name from the on-board navigation database and conforms to the charted route.
	02 State that the route may subsequently be modified through the insertion (from the database) or deletion of specific waypoints in response to ATC clearances.
	03 State that the manual entry, or creation of new waypoints by manual entry, of either latitude and longitude or place/bearing/distance values is not permitted.

	05.05 Required Navigation Performance Approach (RNP APCH)
	01 State that pilots must not fly an RNP APCH unless it is retrievable by procedure name from the on-board navigation database and conforms to the charted procedure.
	02 State that an RNP APCH to LNAV minima is a non- precision IAP designed for two-dimensional approach operations.
	03 State that an RNP APCH to lateral navigation (LNAV)/vertical navigation (VNAV) minima has lateral guidance based on GNSS and vertical guidance based on either SBAS or barometric vertical navigation (Baro- VNAV).
	04 State that an RNP APCH to LNAV/VNAV minima may only be conducted with vertical guidance certified for the purpose.
	05 Explain why an RNP APCH to LNAV/VNAV minima based on Baro-VNAV may only be conducted when the aerodrome temperature is within a promulgated range if the barometric input is not automatically temperature- compensated.
	06 State that the correct altimeter setting is critical for the safe conduct of an RNP APCH using Baro-VNAV.
	07 State that an RNP APCH to LNAV/VNAV minima is a three-dimensional operation.
	08 State that an RNP APCH to localiser performance with vertical guidance (LPV) minima is a three-dimensional operation.
	09 State that RNP APCH to LPV minima requires a final approach segment (FAS) data block.
	10 State that RNP approaches to LPV minima require SBAS.
	11 State that the FAS data block is a standard data format to describe the final approach path.

	05.06 Required Navigation Performance Authorisation Required Approach (RNP AR APCH)
	01 State that RNP AR APCH requires authorisation.

	05.07 Advanced Required Navigation Performance (A-RNP)
	01 State that A-RNP incorporates the navigation specifications RNAV 5, RNAV 2, RNAV 1, RNP 2, RNP 1 and RNP APCH.