Area Navigation (RNAV) and Required Navigation Performance (RNP)
**** Hidden Message ***** Presented to:<BR>By:<BR>Date:<BR>Federal Aviation<BR>Administration Area Navigation<BR>(RNAV) and Required<BR>Navigation<BR>Performance (RNP)<BR>Program Overview<BR>CDA Workshop<BR>Bruce Tarbert<BR>RNAV and RNP Group<BR>January 19,2006<BR>RNAV/RNP Program Overview<BR>Federal Aviation 2<BR>January 19, 2006 Administration<BR>Roadmap for Performance-Based<BR>Navigation<BR>• The FAA published the Roadmap in<BR>July 2003<BR>• Collaborative effort among aviation<BR>industry stakeholders<BR>– Performance-Based Operations Aviation<BR>Rulemaking Committee (PARC)<BR>• Aligned with FAA Flight Plan, ATO<BR>Business Plan, OEP, and RTCA<BR>• Updating December 2005 to reflect<BR>lessons learned<BR>RNAV/RNP Program Overview<BR>Federal Aviation 3<BR>January 19, 2006 Administration<BR>What is “Performance-Based<BR>Navigation”?<BR>• Aviation authorities specify the aircraft capabilities and<BR>performance requirements necessary to operate in a<BR>given airspace or use a given procedure (instead of<BR>specifying required technologies or specific avionics)<BR>– RNAV is achieved through a combined use of aircraft navigation<BR>accuracy, route separation and/or air traffic control intervention (e.g.,<BR>via radar monitoring, automatic dependent surveillance (ADS), multilateration,<BR>communications)<BR>– RNP is RNAV operations with on-board navigation containment,<BR>monitoring and alerting<BR>RNAV/RNP Program Overview<BR>Federal Aviation 4<BR>January 19, 2006 Administration<BR>Performance-Based Navigation<BR>Evolution<BR>Waypoints<BR>RNAV<BR>Increased Airspace<BR>Efficiency<BR>Optimized<BR>Use of Airspace<BR>“curved”<BR>paths<BR>Seamless<BR>Vertical<BR>Path<BR>Narrow TERPS<BR>RNP<BR>Limited<BR>Design<BR>Flexibility<BR>Conventional<BR>Routes<BR>Current Ground<BR>NAVAIDs<BR>• More complex routes<BR>• Tighter performance<BR>• No radar requirement<BR>• 30% capable US fleet<BR>• Point-to-point routes<BR>• Radar monitoring<BR>• 90% capable US fleet<BR>RNAV/RNP Program Overview<BR>Federal Aviation 5<BR>January 19, 2006 Administration<BR>Performance-Based Navigation<BR>In All Phases of Flight<BR>“Snapshot” of Current U.S. Implementations<BR>RNAV<BR>SIDs<BR>RNAV<BR>Q Routes, T Routes<BR>RNAV STARs<BR>RNP SAAAR<BR>approaches<BR>RNAV approaches<BR>RNAV/RNP Program Overview<BR>Federal Aviation 6<BR>January 19, 2006 Administration<BR>Enabling Criteria, Guidance and Tools<BR>• Part 75 Revision for RNAV routes<BR>• AC 90-100<BR>– US Terminal and En Route Area Navigation (RNAV) Operations<BR>• Order 7470.1<BR>– DME/DME Evaluation<BR>• Order 8260.44A<BR>– Civil Utilization Of Area Navigation (RNAV) Departure Procedures<BR>• RNAV-PRO DME Screening Tool<BR>• TARGETS development tool<BR>• Order 8260.53<BR>– United States Standard for Instrument Departures that use Radar Vectors to<BR>Join RNAV Routes<BR>• AIM Revisions for RNAV<BR>• Charting Specifications for RNAV routes and procedures<BR>• Notice 8000.302<BR>– Stand-Alone Area Navigation (RNAV) Transition Procedures<BR>RNAV/RNP Program Overview<BR>Federal Aviation 7<BR>January 19, 2006 Administration<BR>Enabling Criteria, Guidance and Tools<BR>(Completed)<BR>• AC 90-96A<BR>– Approval of U.S. Operators and Aircraft to Operate Under Instrument<BR>Flight Rules (IFR) in European Airspace Designated for Basic Area<BR>Navigation (B-RNAV) and Precision Area Navigation (P-RNAV)<BR>• AC 20-153<BR>– Acceptance of Data Processes and Associated Navigation<BR>Databases<BR>• Notice 8000.300<BR>– Required Navigation Performance (RNP) Airworthiness Approval,<BR>Operational Approval, and Design Guidelines for Special Aircraft and<BR>Aircrew Authorization Required (SAAAR) Approach Procedures<BR>• Order 8260.52<BR>– United States Standard for Required Navigation Performance (RNP)<BR>Approach Procedure with Special Aircraft and Aircrew Authorization<BR>Required (SAAAR)<BR>RNAV/RNP Program Overview<BR>Federal Aviation 8<BR>January 19, 2006 Administration<BR>Enabling Criteria, Guidance and Tools<BR>(Completed)<BR>• US RNP SAAAR Criteria (FAA Order 8260.52) was<BR>submitted to the ICAO OCP as a model for<BR>international criteria for RNP approach procedures<BR>– OCP accepted the order in total<BR>• A drafting group will adapt the order to be consistent with PANSOPS<BR>• Intent is to publish this criteria as a stand-alone document<BR>supplementing PANS-OPS<BR>– The end state objective is to have mature criteria for introduction into<BR>PANS-OPS at OCP/15 in the fall of 2007<BR>• AC 90-101<BR>– Approval for RNP procedures with Special Aircraft and Aircrew<BR>Authorization Required (SAAAR)<BR>RNAV/RNP Program Overview<BR>Federal Aviation 9<BR>January 19, 2006 Administration<BR>FY2005 Highlights<BR>• Published 6 RNP Special Aircraft and Aircrew<BR>Authorization Required (SAAAR)<BR>– 1 public RNP SAAAR<BR>– 4 special RNP SAAARs<BR>– 1 special RNP Parallel Approach Transition (RPAT)<BR>• Published/Implemented 25 RNAV Routes<BR>– 21 high altitude (Q-Routes)<BR>– 4 low altitude (T-Routes)<BR>• Implemented 58 Standard Terminal Arrivals<BR>(STARs) and Standard Instrument Departures<BR>(SIDs)<BR>RNAV/RNP Program Overview<BR>Federal Aviation 10<BR>January 19, 2006 Administration<BR>RNAV Departure and Arrival Procedures<BR>Examples of Near-term Implementation<BR>September 16 SIDs<BR>2005<BR>Dallas Fort<BR>Worth<BR>(American)<BR>Philadelphia March 2005 2 STARs<BR>(US Airways)<BR>4 STARs<BR>13 SIDs<BR>Atlanta April 2005<BR>(Delta)<BR>Dulles Jan 2005 4 STARs<BR>(United, Independence<BR>Air)<BR>4 STARs and<BR>5 SIDs<BR>Las Vegas Nov 2004<BR>(America West,<BR>Southwest)<BR>Airport Date Procedure<BR>RNAV/RNP Program Overview<BR>Federal Aviation 11<BR>January 19, 2006 Administration<BR>Atlanta RNAV Departure<BR>Procedures<BR>April 2005<BR>• Approx 90% of 1350 daily IFR<BR>departures are RNAV capable<BR>• Structured “lanes” to en route<BR>airspace<BR>• Over 4,000 routine daily<BR>pilot/controller voice transmissions<BR>eliminated (30% reduction)<BR>• Delta Airlines estimates $30M<BR>annual savings<BR>– Decreased taxi times<BR>– Decreased departure delays<BR>– Improved flight profiles<BR>– Reduced distances<BR>Before RNAV<BR>After RNAV<BR>RNAV/RNP Program Overview<BR>Federal Aviation 12<BR>January 19, 2006 Administration<BR>RNP SAAAR Approach Criteria<BR>Enabling Features<BR>R<BR>R<BR>2 RNP<BR>2 RNP<BR>2 RNP<BR>2 RNP<BR>STEP 2:<BR>Locate Turn Center<BR>STEP 1:<BR>Segment<BR>Initial<BR>Fix<BR>a=R<BR>b=R+(2xRNP)<BR>c=R-(2xRNP)<BR>Segment<BR>Terminating<BR>Fix<BR>STEP 3<BR>STEP 4<BR>STEP 5<BR>a<BR>b<BR>c<BR>Tangent Points<BR>Tangent Points<BR>Apply para 2-2<BR>Curved Segments Vertical Profiles & Missed Approach<BR>Narrow<BR>Segments<BR>Narrow lateral linear segments<BR>(RNP-0.3 or less with no secondary buffers)<BR>Curved segments anywhere along the approach<BR>(Radius-to-fix legs with shorter leg lengths)<BR>Guided, narrower turns on missed approaches<BR>(Radius-to-fix legs, and RNP-1 or less)<BR>Performance-based Vertical Profiles<BR>(Vertical Error Budget vs. Barometric Vertical Nav)<BR>RNAV/RNP Program Overview<BR>Federal Aviation 13<BR>January 19, 2006 Administration<BR>RNP SAAAR Approach Applications and<BR>Priorities<BR>Analysis of Top 100+ Airports<BR>• Single runway access and<BR>safety enhancement<BR>• Future airspace deconfliction<BR>Tier 3<BR>• Regional capacity impact<BR>• Access & safety<BR>enhancements<BR>Tier 2<BR>• Near-term capacity needs,<BR>with national impact<BR>• Safety enhancement<BR>applications<BR>Tier 1<BR>Airports Characteristics<BR>RNAV/RNP Program Overview<BR>Federal Aviation 14<BR>January 19, 2006 Administration<BR>Palm Springs RNP Approach<BR>January 2005<BR>• Avoids non-precision approach<BR>into a valley with mountainous<BR>terrain<BR>• Safety enhancement, with<BR>guided, stabilized 3D path to<BR>runway<BR>• Reduced time & distance<BR>(approximately 30 miles)<BR>• Reduced minima, averting<BR>cancellations & diversions<BR>– 20 flights “saved” in first few weeks<BR>of implementation<BR>– A SAVE is a flight that would have been<BR>canceled or diverted if the RNP<BR>procedure was not available<BR>RNAV/RNP Program Overview<BR>Federal Aviation 15<BR>January 19, 2006 Administration<BR>International Harmonization and<BR>Coordination<BR>Japan<BR>China<BR>ICAO<BR>Coordination & Singapore<BR>Harmonization<BR>Seminars and Workshops<BR>Standards & Criteria<BR>Procedure Design<BR>Implementation<BR>Brazil<BR>North<BR>American<BR>Roadmap<BR>Netherlands Switzerland<BR>Australia<BR>Airspace Issues<BR>Environment<BR>Standards & Criteria<BR>Procedure Design<BR>Implementation<BR>RNAV/RNP Program Overview<BR>Federal Aviation 16<BR>January 19, 2006 Administration<BR>International<BR>• Work with ICAO and EUROCONTROL on international standard for<BR>RNAV and RNP<BR>– ICAO RNP Study Group agreed to move forward single ICAO RNAV<BR>standard (AC90-100, TGL10)<BR>• Revise RNP Manual (Doc 9613)<BR>• Support international harmonization<BR>– North American Aviation Trilateral (NAAT)<BR>• Signed Joint Strategy for Implementation of Performance-Based Navigation in<BR>North America<BR>– FAA, Transport Canada, DGAC Mexico, NAV CANADA, and SENEAM<BR>– Departamento de Controle do Espaço Aéreo (DECEA) (Brazil)<BR>– Asia-Pacific Economic Cooperation (APEC)<BR>– European Organisation for the Safety of Air Navigation (EUROCONTROL)<BR>– Japan Civil Aviation Bureau (JCAB)<BR>– Civil Aviation Authority of China (CAAC)<BR>– Caribbean/South American (CAR/SAM) Regional Planning and<BR>Implementation Group (GREPECAS)<BR>RNAV/RNP Program Overview<BR>Federal Aviation 17<BR>January 19, 2006 Administration<BR>Flight Standards “Special” Approval<BR>Process<BR>• Waiting on slides from Les
页:
[1]