Application of P-RNAV in The Netherlands

1. Application of P-RNAV in The Netherlands ATC The Netherlands Jeroen Vermeij

2. Content General: application of RNAV operations Experience during 2003 with RNAV transitions Highlights of other RNAV applications Concluding remarks

3. Application of P-RNAV in The Netherlands RNAV Transitions during night optimum descent profile optimum lateral profile Standard Instrument Departure Predictable = safety Noise preferential routings RNAV transitions for regional airports Low capacity application RNAV intermediate approach operations during day-time Parallel approaches

4. Why P-RNAV in the TMA? Reduce environmental effects Advanced Approach and Departure operations Improve pilot situational awareness expected approach profile in TMA Longer term: improve TMA procedures APP workload: standard approach procedures

5. Concluding remarks P-RNAV offers enormous potential in relation to TMA procedure design Capacity Environment Safety Conditions Non-RNAV aircraft restrict benefits of RNAV procedures

6. Any Questions?

7. RNAV Transitions during night Objective: Develop, design and implement continuous descent approaches via the sea. Optimize location with respect to the environment Minimum capacity 20 movements per hour

8. Approaches towards RWY 18R & 06

9. Design team Team of experts consisting of: Active APP controllers; Pilots from the home carriers (KLM, Transavia, Martinair); PANS-OPS experts; ATC design experts Close co-ordination with: regulator database manufacturers

10. Design of the procedure

11. Transition RWY 06

12. Aircraft requirements Minimum requirements: B-RNAV (TGL 2 or 3.3) fly-over / fly-by waypoints application of turn anticipation availability of TMA database Preferred requirement P-RNAV (TGL 10)

13. Implementation issues ATC and flight procedure development Charting: human factor issue ! Internal ATC procedures: co-ordination & R/T & minimum separation, etc Adaptations in ATC system: inbound planning maps of routes sequence lines / distances ATC training: ACC & APP

14. Verification Discussions with database manufacturers during charting process Database was checked manually Database was verified in Flight-SIM in the week before operations started Maps from Jeppesen and home carriers were checked

15. Evaluation of transition RWY 06 (555)

16. Dataset NARIX (166)

17. Dataset NIRSI (484)

18. Evaluation Transitions on RWY 18R and 06

19. 95%-containment area

20. DC10 and B744

21. Stepdown vs continuous descent

22. Conclusions Aircraft perform the approaches as expected Better vertical performance is desired Standardization of ATS procedures is required Cleared for approach; or Transition Critical aspect is controller training How to deal with non-RNAV aircraft ? Ongoing discussion on concentration of noise

23. RNAV and Standard Instrument Departures Avoid urban areas Predictable flight patterns for APP Parallel departures � accuracy at initial departure

24. Intermediate approach operations Objective: Avoid long line-ups Standardize APP procedures Evaluated but not yet applied: ATC training Communication with the environment Not 100% P-RNAV aircraft