1 / 27

R NAV – process in Tartu How EAVA can co-operate with service providers

R NAV – process in Tartu How EAVA can co-operate with service providers ONE example - still in progress,,. R NAV – process in Tartu How EAVA can co-operate with service providers. Tapani Keskikuru EAVA ATSTO. Backround. European Nav strategy …NDB, VOR will be history ( target 2016)

skimball
Download Presentation

R NAV – process in Tartu How EAVA can co-operate with service providers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RNAV – process in TartuHow EAVA can co-operate with service providers ONE example- still in progress,,

  2. RNAV – process in TartuHow EAVA can co-operate with service providers Tapani Keskikuru EAVA ATSTO

  3. Backround • European Nav strategy …NDB, VOR will be history ( target 2016) • http://www.ecacnav.com/downloads/NAV%20Application%20+%20NAVAID%20Infrastructure%20Strategy%2015MAY08%20Agreed%20at%20SCG-8.pdf • PRNAV approaches, replacing conventional Non-Precision approaches (VOR, NDB) and even CAT I ILS – with VNAV/BARO

  4. Background

  5. Background • What are the near future nav. requirements from service providers • RNAV approaches with VNAV – CAT I minima, without any ground equipment • (not to forget lights !!,, ) • WAM ,no need for SSR antennas, less expensive, surveillance can be built wherever, spread wherever

  6. Backround

  7. EAVA and Tartu PRNAV • Tartu case :ATCOs Marika, Piret and Martin, local knowledge • not much tools for ATC to separate IFR / IFR flights in TMA, no equipment for operators • Tartu speciality : IFR (and VFR) training flights

  8. Requirements: • Update approaches, started before EAVA joined ( operational in 2013) • for operators • for students, future pilots • Need to have tools for ATCOs to separate IFR traffic in TMA, present NDB surroundings is for one IFR, if levels crossed

  9. EAVA and Tartu PRNAV • from pilot/ operator point of view benefits are obvious • from airport point of view benefits are obvious, • from ATC point of view benefits are obvious

  10. EAVA and Tartu PRNAV • from safety point of view benefits are obvious ( one example - no circling) • from environmental side • shorter routes • in many cases continuous climb/ descend • in many cases shorter holding time on ground/ in air or no delay at all • noise can be taken account

  11. EAVA and Tartu PRNAV • No ICAO procedures for RNAV separations are published ! • PANS-ATM ICAO DOC 4444 • „Lateral separation of aircraft on published adjacent instrument flight procedures for arrivals and departures

  12. EAVA and Tartu PRNAV Lateral separation of departing and/or arriving aircraft, using instrument flight procedures, will exist: • a) where the distance between RNAV 1, Basic RNP 1, RNP APCH and/or RNP AR APCH tracks is not less than 13 km (7 NM); or

  13. EAVA and Tartu PRNAV Lateral separation of departing and/or arriving aircraft, using instrument flight procedures, will exist: • b) where the protected areas of tracks designed using obstacle clearance criteria do not overlap and provided: operational error is considered.

  14. EAVA and Tartu Rnav • Note 1.— The 13 km (7 NM) value was determined by collision risk analysis using multiple navigation • specifications. Information on this analysis is contained in Circular 324, Guidelines for Lateral Separation of Arriving and Departing Aircraft on Published Adjacent Instrument Flight Procedures.

  15. EAVA and Tartu Rnav • PANS-OPS (ICAO 8168) guidelines for obstacle clearance criteria

  16. EAVA and Tartu PRNAV -Plan is to create SID/STAR for Tartu linking TMA EXIT/ENTRY points to RNAV approaches with “designated points” where safety buffers are not overlapping ( ICAO DOC 4444) -Make easy tool for ATC to give clearances for IFR aircraftkeeping them on arrival/departure segments which are not overlapping, while no vertical separation exists.

  17. EAVA and Tartu Rnavs

  18. EAVA and Tartu PRNAV

  19. EAVA and Tartu PRNAV How to continue; • AIS to create maps, data into EAVA simu and drive first simulations • Make first changes if needed , create ATC documentation • In parallel, to create data for SMS

  20. EAVA and Tartu PRNAV End result: • Tartu PRNAV SIDs and STARs • get CAA approval for Tartu ATC procedures forPRNAV SID/STAR in non –radar environment • give a tool for ATC to have more than one IFR a/c in TMA on crossing levels

  21. EAVA and Tartu Rnavs End result: • procedures ready • ATC has necessary “tools” and uses them to provide user friendly service • SMS ready • training material ready

  22. EAVA envolvement • -previous knowledge • Synthetic Training Device ( simulator) • easy to make changes and run tests • - up to date training facilities • - If needed, capability to show CAA the procedures inSIMU environment during acceptance period • - capability to train TARTU ATC instructors ( or all staff)

  23. Our goal

  24. Not to confuse

  25. End result -

  26. All happy !

More Related