RNAV 1 Approval Process

Transcription

1 RNAV 1 Approval Process

2 JAA Temporary Guidance Material TGL 10 Published November 2000 P-RNAV meets all PBN requirements for RNAV 1 Operations using DME/DME or GNSS EASA transposing JAA guidance into AMC (AMC 20-16) Updating criteria, bringing more into line with the PBN Manual date of issue to be confirmed P-RNAV = RNAV 2 where the environment does not support 1 NM accuracy P-RNAV = RNAV 1 = RNP 1 where the sensor used is GNSS or the aircraft is RNP qualified

3 Aim of Presentation TGL 10 is guidance material not a rule Other ways can be used if you can demonstrate you meet the requirements of RNAV 1 TGL 10 provides a framework that could be used by the regulator of IR of Iran to prepare material as basis for approval of local operators Presentation highlights the points to be addressed in any local guidance material

4 Airworthiness Certification Objectives 1 Accuracy lateral track keeping accuracy equal to or better than +/- 1 NM for 95% of the flight time. For obstacle clearance FTE assumed: ± 0.5NM for the departure 1NM for the initial and intermediate segments, 2NM for en-route. The objective is to enable RNAV systems based on DME/DME, to be used in terminal airspace on RNAV Terminal procedures without further evaluation of system accuracy.

5 Airworthiness Certification Objectives 2 Accuracy continued Where design of procedures and navigation infrastructure have been assessed and validated as meeting P-RNAV (RNAV- 1) requirements. and RNAV systems declared to be compliant with the 2D navigation accuracy criteria of FAA AC 90-45A, AC (), FAA TSO-C115(), or JAA JTSO-2C115(), then no further accuracy demonstration is required. However, such a Flight Manual statement, by itself, does not constitute an airworthiness approval for P-RNAV and compliance with all other criteria of this leaflet will need to be shown. Note FAA AC 90-45A issued 1975 withdrawn 2014

6 Airworthiness Certification Objectives 3 Integrity With respect to the airborne system, the probability of displaying hazardously misleading navigational or positional information simultaneously to both pilots shall be Remote. Hazardously misleading is information without a timely warning and which, in the absence of other cues, is unlikely to be detected by the flight crew. A safety objective of Extremely Remote will continue to be applicable to a precision approach on the final segment i.e. from the FAWP down to the runway note the safety objective of Remote is an alleviation made possible by the design criteria for RNAV1 (PRNAV) procedures.

7 Airworthiness Certification Objectives 4 Continuity of function With respect to the airborne systems, it shall be shown that: a. The probability of loss of all navigation information is Remote. b. The probability of non-restorable loss of all navigation and communication functions is Extremely Improbable. (i) Improbable (Remote) Failure Conditions are those having a probability order of 1 x 10-5 or less but greater than of the order of 1 x (ii) Improbable (Extremely Remote) Failure Conditions are those having a probability of the order of 1 x 10 7 or less, but greater than of the order of 1 x 10 9.

8 Airworthiness Certification Objectives 5 RNAV Equipment at least one area navigation system is required. Where the minimum flight crew is two pilots, means needs to be provided for the pilot not flying to verify the desired path and the aircraft position relative to the path.

9 Functionality 1 Fly by waypoint (WP). Fly over WP. Execute following 424 leg types IF, TF, CF, FA, DF Direct to function. Indication of the RNAV system failure, including the associated sensors, in the pilot s primary field of view Entire procedures loadable from aircraft database Automatic tuning of DME For multi-sensor systems, automatic reversion to an alternate RNAV sensor if the primary RNAV sensor fails.

10 Functionality 2 Database that can be updated in accordance with the AIRAC cycle. Display active WP. Display validity period of database. Continuous display of computed RNAV desired path. Display of active sensors. Database protection against flight crew modification. Distance/bearing to WP. Automatic leg sequencing. Means to retrieve and display data, e.g. Master Control and Display Unit (MCDU).

11 Recommended Functions 1 Offset Left/Right of track. Offset should not be propagated through route discontinuities, unreasonable path geometry, or beyond the IAF Execute following 424 leg types HM, HA, HF, RF. Coupling to the flight director and/or automatic pilot from the RNAV system with unambiguous mode indication.

12 Recommended Functions 2 Capability for vertical navigation based upon barometric inputs. For an RNAV system using DME/DME updating, supported by IRS: means for automatic runway position update at the start of the takeoff run means to enter a distance offset for situations where the published threshold and the actual start of the take of run differ (i.e. take-off shift). Display of the navigation mode in the pilot s primary field of view.

13 Data Quality control Database obtained from a supplier holding a type 1 and type 2 Letter Of Acceptance (LOA). This demonstrates compliance with EUROCAE/RTCA document ED-76/DO200A. See later for TGL 10 workaround in LOA approval not possible SID/STAR plate supplier - Show how you check your supplier to establish the effectiveness of your supplier's quality system.

14 Error Reporting and Follow up Outline your process for error reporting/ withdrawal of operational use of procedures. Note: significant errors (i.e. those that would affect the flight path of the aircraft) must be reported to the database supplier immediately, and the affected procedures withdrawn from company operations by company instruction without delay. Any database or chart anomaly identified during RNAV operations must be reported to the CAO. Question: Do you have a Mandatory Occurrence Reporting Scheme

15 Database Loading Process to ensure that there is no possible corruption in the content of the database on the RNAV/GNSS system.

16 Standard Operating Procedures 1 (SOPs) MEL handling: Items required for P-RNAV operations. Required equipment list. Statement that autopilot/flight director should be used whenever possible. SOPs for which pages should be displayed on the FMC for P-RNAV (PF and PNF). Database Validity Check.

17 Standard Operating Procedures 2 (SOPs) Monitoring of system navigation accuracy. SID/STAR Validity Check including confirmation of procedure track and distance. Navigation System Downgrade Procedure. Contingency procedures if unable RNAV 1(P- RNAV). Statement that crew should not manually insert WPs into the procedure.

18 Operations Manual Part A RNAV concepts. Navigation accuracy assessment at dispatch/destination and alternates. RTF phraseology. MEL handling. SOPs. Crew Authorisation required/validation. Part B Technical information and MEL. Part C Training programme (Modular) in accordance with RNAV 1 (P-RNAV) operations.

19 Pre-Dispatch Confirm meet MEL. Confirm Crew qualified. Confirm Database valid. Check that RAIM available for flight Confirm NOTAMs for Navigation infrastructure allow DME operation Note: ANSP needs to: establish means to confirm GNSS availability and a means of checking for route. Ensure means to alert air crew of any failure of functioning of DME

20 Training Syllabus 1 To Include: Basic Area Navigation Concepts: RNAV/RNP Definitions. Theory of RNAV including differences between RNAV 5, RNAV 1, RNP 1. RNAV/RNP Definitions. The meaning of RNP/ANP. Limitations of RNAV. Limitations of Baro-VNAV. GPS concepts and limitations (if applicable). Charting, database and avionics issues including: 1. WP naming and depiction concepts. 2. Fly-by and fly-over WPs 3. Terminal Area leg types

21 Training Syllabus 2 Use of RNAV equipment including: 1. Verification and sensor management. 2. Tactically modifying the flight plan and its impact the route flown and on vertical constraints. 3. Managing route discontinuities 4. Entering associated data such as: i) Wind. ii) Altitude/speed constraints. iii) Vertical profile/vertical speed. RTF phraseology for RNAV/RNP. Implications on RNAV operation where systems malfunctions are not RNAV related (e.g. hydraulic or engine failure). NOTE: Credit may be given/taken for previous RNAV 5 Area Navigation concept training when Qualifying for RNAV 1

22 Summary The presentation has VERY briefly summarised the main points of TGL 10. TGL 10 is aimed at P-RNAV but, with one exception in terms of recommended functions, RNAV 1 and P-RNAV requirements are identical. Both P-RNAV and RNAV 1 have optional functionality. ADS-CY Ltd. experience has been that optional functionality cannot be used in designing airspace procedures and as a result the ADS airspace and procedure design will only make use of the required functionality of P-RNAV.

23 Data Integrity TGL 10 identifies an approach to data integrity in absence of LOA 1 or 2 approved supplier prior to the effective date of the navigation database, the operator must implement navigation database integrity checks using appropriate software tools or approved manual procedures to verify data relating to waypoints below the applicable minimum obstacle clearance altitude. The integrity checks need to identify any discrepancies between the navigation database and the published charts/procedures. Integrity checks may be performed by an approved third party.

24 Data Integrity Check Tool Enables independent checks on a navigation database to ensure data integrity. The tool should include the following functionality: Allow a user to specify the data areas to be checked and the critical data items to be monitored. Detect any changes in monitored data items. Generate reports listing all identified changes. Provide a full data history to support configuration control. Maintain non editable log-files of all online actions. Provide analyses of database quality and changes in quality levels by tracking of rates of discovered errors. Provide a flexible data input interface to enable database integrity checks for a variety of database providers These checks can be delegated to a service organization. The software does not have to be qualified in accordance with EUROCAE ED-12B/ RTCA DO-178B.

25 Questions