Application for RNP Approach (RNP APCH) - Irish Aviation Authority

Form No. FOD.F.223a 

Version No. 1 

Issue Date: 17/06/2011 

APPLICATION FOR RNP APPROACH 

(RNP APCH) BASED ON GLOBAL 

NAVIGATION SATELLITE SYSTEM 

(GNSS) OPERATIONAL APPROVAL 

APPLICATION FOR RNP APPROACH (RNP APCH) BASED ON GLOBAL 

NAVIGATION SATELLITE SYSTEM (GNSS) OPERATIONAL APPROVAL 

Please complete the form in BLOCK CAPITALS. 

Please read the ‘Notes for Completion’ (page 2). 

SECTION ONE: OPERATOR/AIRFRAME DETAILS 

1. Applicant Details - required for all Approval requests 

Note: For AOC holders - company name, AOC number and e-mail address will suffice. 

1 (a) Name of Business or Trading Name(s): ................................................................................................. 

1 (b) Name of Individual (if applicable): 

Title: …………..…Surname: ........................................................ Forename: ………………........................ 

1 (c) AOC Number (if applicable): ………………………………... 

1 (d) Address: 

......................................................................................................................................... 

……………………………………………………………………………………………………. 

Postcode: ..................................................... Country: .................................................... 

1 (e) Postal Address (if different from above): 

......................................................................................................................................... 

……………………………………………………………………………………………………. 

Postcode: ..................................................... Country: .................................................... 

1 (f) Contact details 

Phone No.: ................................................... Mobile No: .................................................................... 

Fax No: .........................................................E-mail address: ............................................................. 

2. Aircraft Details - required for all Approval requests 

Aeroplane type(s), series and registration mark(s). 

Aeroplane Type Aeroplane Series Registration 

Page 1 of 8


Version No. 1 

Issue Date: 17/06/2011 

APPLICATION FOR RNP APPROACH 

(RNP APCH) BASED ON GLOBAL 

NAVIGATION SATELLITE SYSTEM 

(GNSS) OPERATIONAL APPROVAL 

SECTION TWO: NOTES FOR COMPLETION 

1. Applicability 

RNP APCH operation without vertical guidance (Non Precision Approach operation) and with vertical 

guidance based on barometric vertical navigation (APV BARO-VNAV operation). This application form 

does not apply to RNP AR APCH (Authorisation Required) operations. 

The requirements for Operator Approval to carry out RNP-APCH operations are laid out in AMC 20-27 

(available via the Eurocontrol Website - see below). 

Additional Guidance can be found in: 

ICAO Doc 9613 Manual of Performance-Based Navigation 

AMC 20-27 

Other useful information is provided on the Eurocontrol Website: www.ecacnav.com/PBN. 

2. Operator's RNP APCH Submissions Matrix 

Section Four of this application form is the Operator's RNP APCH Submissions Matrix. All applicants 

should complete Column 3 of this matrix in full. If more than one type of aircraft/fleet is included in a single 

application a completed matrix should be included for each aircraft/fleet. 

3. Documents to be included with the application 

Copies of all documents referred to in the Operators RNP APCH Submissions Matrix should be included 

when returning the completed application form to the Irish Aviation Authority. Original documents should 

not be sent, photocopies are sufficient. Do not send complete manuals, only the relevant sections/pages 

will be required. 

4. Submissions and Enquiries 

Address for submissions: Contact details for enquiries: 

Irish Aviation Authority 

Flight Operations Department 

The Times Building 

11-12 D’Olier Street 

Dublin 2 

Ph: 00 353 1 6718655 

Fax: 00 353 1 6774460 

Email: fod@iaa.ie 

Note: Applications for non-AOC RNP APCH operations must be accompanied by the appropriate fee. 

Please contact the Flight Operations Department for details of the fee required. 

SECTION THREE: SIGNATURE BLOCK 

Signature: ................................................................Name: ............................................................................ 

Date: ........................................................................Appointment: ................................................................. 

Please note that a minimum of 30 working days will normally be required to check and confirm the 

information given above - if data is missing or omitted the process may take considerably longer. 

Page 2 of 8


Version No. 1 

APPLICATION FOR RNP APPROACH (RNP APCH) BASED ON GLOBAL NAVIGATION 

SATELLITE SYSTEM (GNSS) OPERATIONAL APPROVAL 

Issue Date: 17/06/2011 

SECTION FOUR: APPLICANT'S RNP APCH SUBMISSIONS MATRIX 

Expanded areas to be addressed by application 

1.0 - Reference Documents used in compiling submission 

Your submission should be based on current up to date regulatory 

material. 

You should publish a compliance statement showing how the criteria 

of AMC 20-27 have been satisfied. 

2.0 - Airworthiness Navigation System Capability compliance statement 

Compliance with the airworthiness and functional criteria and 

airworthiness compliance aspects of the Navigation Specification for 

RNP APCH normally requires the support of the Type Certificate 

Holder or Supplemental Type Certificate Holder in the case where an 

STC is involved. 

The detailed requirements contain both quantitative and qualitative 

requirements and are normally found in Chapters 6, 7 and 8 of the 

relevant EASA AMC 20 guidance document (in this case AMC 20-27). 

Reference Documentation and Sub-requirements 

AMC 20-27 

ICAO Doc 9613 

ICAO Doc 8618 PANS-OPS 

ETSO-C129a/ETSO-C145 (In CS-ETSO on the EASA 

website http://www.easa.europa.eu.) 

AMC 20-27, Chapters 6, 7 and 8 

ED-75/DO-236 

Operator’s Operations Manual 

Reference or Document Reference 

A detailed compliance checklist should be submitted by the operator 

against the requirements of Chapter 6, 7 and 8 of AMC 20-27 

complete with any supporting statements provided by the relevant 

TC/STC Holder. 

If necessary, aspects of the functional requirements may be 

demonstrated via simulation tools or demonstration flight 

2.1 - Aircraft Flight Manual (AFM) 

A statement or copy of the AFM showing the aircraft certification 

standard for RNP APCH operations. 

2.2 - Quality Control Navigation database integrity checks 

Database obtained from a supplier holding a Type 2 Letter Of 

Acceptance (LOA). This demonstrates compliance with 

EUROCAE/RTCA document ED-76/DO-200A. (See 

http://www.eurocae.eu and http://www.rtca.org.) 

Page 3 of 8


Version No. 1 



Issue Date: 17/06/2011 


2.3 – Navigation Chart supplier 

Does the supplier hold an ED-76 Approval? Show how you audit your 

supplier of navigation charts in order to establish the effectiveness of 

your supplier's quality system. 




2.5 - Navigation System FMS/Autopilot interface capability 

Full details of the Navigation System including type and number, e.g. 

specific capability. 

AMC 20-27 

Entire procedures loadable from aircraft database. 

• Database that can be updated in accordance with the 

AIRAC cycle. 

• Display active WP. 

• Display validity period of database. 

• Continuous display of computed RNAV (GNSS) desired 

path. 

• RNAV/GNSS system failure/integrity downgrade alerting 

capability. 

• 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). 

2.6 - Feedback and reporting of errors found 

Outline your process for error reporting/withdrawal of operational use 

of procedures. 

Note: In particular, 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 IAA through the SOTS scheme. 

3.0 - Standard Operating Procedures 

Manufacturer/operator developed. MEL handling: Items required for RNP APCH operations. 

Page 4 of 8


Version No. 1 



Issue Date: 17/06/2011 


Manufacturer's procedures recommended as starting point and must 

include at least the following. 


Required equipment list. 

Statement that autopilot/flight director should be used 

whenever possible. 

SOPs for which pages should be displayed on the FMC for 

RNP APCH (PF and PNF). 

Database Validity Check. 

Monitoring of system navigation accuracy. 

Navigation System Downgrade Procedure. 

Contingency procedures if unable RNP-APCH. 



4.0 - Operations Manuals 

Part A 

• RNAV concepts. 

• Navigation accuracy assessment at dispatch, for 

destination and alternates. 

• RTF phraseology. 

• MEL handling. 

• SOPs. 

Crew Authorisation required/validation. 

Part B Technical information and MEL. 

Part C Inclusion of RNP APCH procedures 

Part D 

4.1 - Pre-Dispatch 

Training programme (Modular) in accordance with RNP 

APCH operations 

• MEL. 

• RAIM/AIME. 

• NOTAMs/Navigation infrastructure. 

Page 5 of 8


Version No. 1 



Issue Date: 17/06/2011 


4.2 - Training package 


• Crew qualified. 

• Database valid. 

Compliant with Flight Crew Training and Testing requirements for 

RNP APCH Operations. 



• Performance requirements for RNP APCH. 

• Navigational equipment required to be operational. 

• Flight planning requirements. 

• Charting, database and avionics issues. 

• Use of RNAV equipment including: 

a) Retrieving a procedure from the database. 

b) Using the autopilot, flight director and auto throttle at different 

stages of the procedure. 

c) Flight mode annunciations. 

• Flying the procedure including: 

a) Use of lateral navigation mode and associated lateral control 

techniques. 

b) Use of vertical navigation mode and associated vertical control 

techniques. 

• Contingency procedures. 

All RNAV Operations 

Basic Area Navigation Concepts: 

• Theory of RNAV including differences between B-RNAV, P-RNAV 

and RNP-RNAV. 

• RNAV/RNP Definitions. 

• The meaning of RNP/ANP. 

• Limitations of RNAV. 

• Limitations of Baro-VNAV. 

• GPS concepts and limitations (if applicable). 

Some or all of: 

• Operations Manual content; 

• handouts (paper or electronic); 

• CBT; and 

• classroom; and 

• Flight Simulator Training including: 

a) at least one RNP APCH procedure flown as PF by 

each crew member; and 

b) failures such as map shift, sensor failure etc. 

Some or all of: 

• Operations Manual content; 

• handouts (paper or electronic); 

• Computer-Based Training (CBT); and 

• Classroom. 

Page 6 of 8


Version No. 1 



Issue Date: 17/06/2011 


• Charting, database and avionics issues including: 

1. WP naming and depiction concepts. 

2. Fly-by and fly-over WPs. 

3. Use of RNAV equipment including, where appropriate: 

a) Verification and sensor management. 

b) Tactically modifying the flight plan. 

c) Addressing discontinuities. 

d) Entering associated data such as: 

i) Wind. 

ii) Altitude/speed constraints. 

iii) Vertical profile/vertical speed. 

All RNAV Operations cont. 

• RTF phraseology for RNAV/RNP. 

• The implications for RNAV/RNP operations of systems 

malfunctions which are not RNAV related (e.g. hydraulic failure or 

engine failure). 

NOTE: Training in Basic Area Navigation concepts is required for 

all types of RNAV/RNP operations. However, credit may be 

given/taken for previous Basic Area Navigation concept training 

when adding a qualification for further type(s) of Area Navigation 

operations. 




Page 7 of 8


Version No. 1 



Issue Date: 17/06/2011 

Any Further Comments to Support your Application: 

Page 8 of 8

Application for RNP Approach (RNP APCH) - Irish Aviation Authority

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?