PBN Deployment – New Zealand Domestic Airspace CAA PBN Forum November 18 2009 Auckland

Click here to load reader

  • date post

    02-Jan-2016
  • Category

    Documents

  • view

    214
  • download

    0

Embed Size (px)

Transcript of PBN Deployment – New Zealand Domestic Airspace CAA PBN Forum November 18 2009 Auckland

  • PBN Deployment New Zealand Domestic Airspace CAA PBN ForumNovember 18 2009Auckland

  • Background DriversModern FMSGround aids reaching end of lifeOperational efficiencyEnvironmental

    ICAOIATA

  • 70 % ruleFAA experience.

    Less than 70% users able to use dont implement

    More than 70% users able to use implement and withdraw conventional

  • In the beginningEstablish RNAV as the default language/method of navigation and ATM

    at AA, WN and CH1/. RNAV STAR 2/. RNAV SID 3/. RNAV En-route between4/. RNAV approach as supplement to ILS

  • Followed byEstablishing RNAV as default language/method of navigation and ATM

    at all airports with regional control towers1/. HN, RO, TG2/. NV, DN, WP3/. NS, WB4/. OH, PM, NP5/. NR, GS

  • Ideal roll out ATC perspectiveAirport specific - implement as a package

    RNAV STARRNAV Approach RNAV SID Separation charts to enable management

    Staff training

  • Current anomalies/difficulties Some regional airports have parts of the package.

    Result of nav aids reaching end of life.

    Mixed fleet equipage.

    Complex lateral separations Mixed messages.

  • Existing PBN proceduresRNP10 (RNAV 10) in OCARNP4 Trans-TasmanRNAV EnrouteRNAV SIDs and STARsRNAV(GNSS) 57 locationsAPV @ 16 runwaysRNP AR @ QueenstownRNP AR @ RO, AA, WN, CH coming

  • So whats to comeEstablish/confirm the Regional PBN Plan

    Initial scoping meeting July 09ATC planning meeting - 5,6,7,8 Oct 09

    Feedback from regional CCsOngoing coordination with users.User meeting 1 Dec 09 Generic Tower Model established (Feb 2010)

  • Generic Regional Tower modelMcDonaldsSupermarket

    From RNAV En-route to Feeder FixRNAV STAR to Approach.

    Approach will be RNAV (GNSS).Upgrade to APV (Baro V NAV). Need to limit choicesAssume VORs (used as approach aid) will go ?ICAO PBN APV to all instrument runways by 2016

  • Chunks step oneQueenstown

    By itself unique jet terrain RNP AR Current ATM very inefficient with regards to traffic flowDeparture example, 23 minute delay once RNP approach committed.Review in progress.Next meeting 23, 24, November

  • Chunks - step twoRO, HN, TG

    Plan Feb, March, April2010

    Implement Nov2010

  • Chunks step threeNV, DN, WPPlanMay, June2010NS, WBPlanJuly, Aug2010 OH, PM, NPPlanSept, October2010NR, GSPlanFeb March2011

    Implement through 2011

  • PBN Issues/ConsiderationsCustomer needs sort this out firstFleet capability Charting standardsProcedure design capabilityRegulator capability (rules) to approve PBN operationsPublic vs. Tailored RNP ARATM considerations - Mixed mode operations What noise there is gets concentratedWhos going to pay?

  • PBN Issues/Considerations (2)Equipment performance standardsRAIM Prediction serviceBack-up proceduresContingency DME/DME, DVORFlight planning requirements ATMTraining requirements

  • ATM system abilityA lost message.ATM system still needs to monitor and assist the aircraft with PBN Current ground system could provide much more.Off track alert - Turn initiation - Cleared altitude vs actual climbFor ATC to use this ability aircraft need Enhanced mode s - capable of up grade toADS-B

  • RNAV Arrivals Noise Concentration

  • Thank you

    **This batting list is able to change.It is currently dependent on 1/. State or ICAO Rules articulating aircraft and ATM equipment levels.2/. Effect of Multi Lat in the QN and wider lower S.I ****This slide is intended to show the need to have STARs wider than the current situation.This will be required as traffic builds to about 25% greater than the current levels. **