1 / 24

Performance-Based Navigation

Performance-Based Navigation. Area Navigation (RNAV) and Required Navigation Performance (RNP). Aviation System Context . Air transportation is projected to grow both domestically & internationally Business and General Aviation segments are expected to grow

evaline
Download Presentation

Performance-Based Navigation

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. Performance-Based Navigation Area Navigation (RNAV) and Required Navigation Performance (RNP)

  2. Aviation System Context • Air transportation is projected to grow both domestically & internationally • Business and General Aviation segments are expected to grow • Upward pressure on fuel costs demands expediting implementation of solutions that improve efficiencies of operations • OEP 35 Airports will need additional capacity • Other airports will be in need of additional capacity

  3. Updated Roadmap Published • Collaborative effort among aviation industry stakeholders • Performance-Based Operations Aviation Rulemaking Committee (PARC) • Three Planning Horizons (aligned w/ JPDO NextGen plan) • Near-term 2006 to 2010 • Mid-term 2011 to 2015 • Far-term 2016 to 2025 • Harmonization considerations • Focuses on operational capabilities in: • En route domain • RNAV Q-Routes • RNAV T-Routes • Terminal domain • RNAV Standard Terminal Arrivals (STARs) • RNAV Standard Instrument Departures (SIDs) • Approach domain • RNP Special Aircraft and Aircrew Authorization Required (SAAAR) • RNP Parallel Approach Transition http://www.faa.gov/ats/atp/rnp/rnav.htm

  4. RNAV/RNP Accomplishments and Plans

  5. RNAV Production Plan- FY2007 • March 2007 • Midway • O’Hare • Las Vegas • Baltimore • Los Angeles • Charlotte • Atlanta • May 2007 • Tampa • Las Vegas • Portland • Minneapolis • Seattle • Phoenix • July 2007 • Covington • Portland • Tampa • Glendale • San Diego • Tampa • Baltimore • Los Angeles • Seattle to Portland to Phoenix (Q-Route) • November 2006 • Seattle • Memphis • Las Vegas • Holyoke • January 2007 • Perryville • Nucla • Newark • Covington • Las Vegas • Pennsylvania V-106 (GPS MEA) • Maryland V-44 (GPS MEA)

  6. RNAV Production Plan- FY2007 (continued) • August 2007 • Tucson • Anchorage • Salt Lake City • Phoenix • Long Beach • Anaktuvuk Pass • Production schedule is available at: http://avnweb.jccbi.gov/schedule/production

  7. Reduced Lateral and Vertical Obstacle Clearance Take advantage of improved aircraft performance Curved Paths Radius-to-Fix (RF) legs used where appropriate Precise Missed Approach Guidance Enable lower minima where precise guidance is required for extraction RNP SAAAR ApproachCharacteristics

  8. RNP SAAAR Accomplishments- FY2006 • Published 28 procedures • San Francisco • Hailey • Palm Springs (3) • Chicago Midway • Newark (2) • Gary (2) • Long Beach (2) • Tampa • Tucson (2) • Fort Lauderdale (3) • Honolulu (2) • Guam (4) • Quito (2) • New York Kennedy (2) Additional 5 procedures developed for future publication • Houston (2) • Chicago Midway • Portland (2) Portland - Horizon Special

  9. RNP SAAAR Production Plan FY 2007 • November 2006 • Hailey, ID (1) • Oklahoma City, OK (2) • January 2007 • Jackson Hole, WY (3) • May 2007 • Atlanta, GA (10) • Dallas/Fort Worth, TX (3) • July 2007 • Bishop, CA (2) • Honolulu, HI (1) • August 2007 • Baltimore, MD (1) • DeKalb-Peachtree, GA (2) • LaGuardia, NY (2) • August 2007 (cont) • Miami, FL (6) • Minneapolis, MN (1) • San Francisco, CA (1) • Washington Dulles, DC (2) • Washington National, DC (1) • September 2007 • Long Beach, CA (1) • Ontario, CA (3) • TBD Status • Chicago Midway (1) • Houston (2) • Portland, OR (2) • Teterboro, NJ • Wenatchee, WA (3)

  10. RNP SAAAR Requests from NBAA • Under development • Dekalb-Peachtree (PDK)- under development • Eastern Sierra Regional (Bishop, CA) (BIH) • New requests as of January 2007 • Albuquerque International Sunport (ABQ) • Garfield County Regional (RIL) • Scottsdale (SDL) • Ernest A. Love Field (PRC) • Glacier Park International (GPI) • Monterey Peninsula (MRY) • Lihue (LIH) • Fulton County Airport- Brown Field (FTY) • DuPage (DPA)

  11. RNP SAAAR Operator Authorization Status

  12. ILS 750’ to 4300’ DA (h) AAP PFAF RNP RPAT Concept (Initial Implementation) Pairs RNP SAAAR with parallel ILS Radar monitoring with ASR-9 to PFAF Guided path with visual separation Abandon approach procedure provided RNP SAAAR missed approach applies at DA Increased acceptance rate when unable VA NORMAL OPERATING ZONE 1500’ NO TRANSGRESSION ZONE 2000’ WX minima: 500 feet above PFAF crossing altitude and 4 miles VSBY or distance from AAP waypoint to RWY threshold, if greater NORMAL OPERATING ZONE 1500’

  13. Enabling Criteria and Guidance • AC 90-100 U.S. Terminal and En Route Area Navigation (RNAV) Operations • Airworthiness, Operational Approval, Operating Procedures, and Training guidance for RNAV Departure Procedures, RNAV Standard Terminal Arrivals, and RNAV routes • Currently in revision by FAA and Industry team to incorporate lessons learned and harmonize with international developments • Order 8260.52 United States Standard for Required Navigation Performance (RNP) Approach Procedure with Special Aircraft and Aircrew Authorization Required (SAAAR) • Written for approach procedure designers to develop public RNP SAAAR instrument approach procedures • AC 90-101 Approval for RNP procedures with Special Aircraft and Aircrew Authorization Required (SAAAR) • Airworthiness, Operational Approval, Operating Procedures, and Training guidance for RNP SAAAR Instrument Approach Procedures • AC 20-153 Acceptance of Data Processes and Associated Navigation Databases • How to evaluate whether data processes comply with the requirements of RTCA/DO-200A, Standards for Processing Aeronautical Data • How to obtain a Letter of Acceptance (LOA) from the Federal Aviation Administration (FAA) • How to define the aeronautical data quality requirements when obtaining airworthiness approval of new equipment or installations where the function of the equipment is dependent on an updateable database

  14. Guidance Material Update:Pending Revisions to AC 90-100 (US RNAV) • New version (AC 90-100A) planned publication March 2007 • Provides connectivity with proposed ICAO standards for RNAV-1 and RNAV-2 • Focuses on operational lessons learned • Addresses DME/DME/IRU and GPS systems only • Guidance to better define turn performance • Requirements to support successful RNAV implementation • STAR Runway Transitions or equivalent functionality • Allows for additional path terminators

  15. RNAV Substitution • Effective August 3, 2006 the FAA began allowing increased RNAV (primarily GPS) substitution for navigation aids throughout the NAS • As a substitute means of navigation guidance when • A VOR, NDB, DME, or compass locator facility is out-of-service • An aircraft is not equipped with conventional equipment such as ADF or DME • The conventional equipment on an aircraft, such as ADF or DME, is not operational • NOTAM language has been amended to reflect these changes

  16. Ongoing Industry Challenges • FMS Programming • Initial runway entry • Runway changes and verification • Entry of en route transitions • Databases • Validation • Implementation • Training • Track compliance/leg and waypoint type • Equipage • RNP SAAAR Approval Process

  17. RNP SAAAR Approval Consultants • AC90-101 RNP SAAAR approval complex and the success of the process depends on the quality of the application • FAA has limited resources to assist new entrants in the approval process • Consultants will assist in approval process • Consultants will screen/prepare application package in accordance with AC90-101 • OTA in Federal Register during December • Formal applications must have been received by December 31, 2006

  18. OEM RNP SAAAR Customer Package • Need OEM guidance on RNP SAAAR (similar to ILS or VOR) • Once published, OEM guidance could significantly reduce application process • Currently working with Boeing, Airbus, Embraer • In the process of scheduling Bombardier, Cessna, Gulfstream and others

  19. Third Party Procedures • Work is progressing on an Other Transaction Agreement that will allow for third party procedure development • FAA Flight Plan goal to have this vehicle in place during FY2007 • End-to-end procedure production • Development • Quality Assurance • Flight Check • Maintenance

  20. PARC Vertical Flight Working Group (VFWG) • VFWG current activities • Evaluating draft FAA Order 8260.42B, Helicopter Area Navigation (RNAV) Instrument Procedure Construction • Recommendations to FAA on additions to (Special) criteria and • Will request for evolution to public criteria with Special Aircraft and Aircrew Authorization Required (SAAAR) • Expected at 18-19 Jan 2007 PARC meeting • RNAV RNP Program is supporting the implementation of helicopter performance based navigation utilizing the NYC SNI project • Project initially includes • Five Special Copter RNAV Point-in-Space (PinS) instrument approaches to service Manhattan’s three public heliports • Designed to increase capacity at LaGuardia, JFK, and Newark airports by de-conflicting helicopter IFR arrivals and departures • Procedure packages are in Aviation System Standards review

  21. International Activities • ICAO RNP Special Operations Requirements Study Group - primary forum for harmonization • Australia, Brazil, Canada, EUROCONTROL, France, Japan, United Kingdom, United States, IATA, ICCAIA, IFALPA • Rewriting ICAO Doc 9613, Performance-Based Navigation Manual • Globally consistent definitions of RNAV and RNP • Standardized Navigation Specifications • ICAO RNAV harmonizes Europe’s P-RNAV and US RNAV • Implementation considerations & guidance • Editorial meetings Oct 2006 & Jan 2007 • Publication planned for March-April 2007 • ICAO/FAA/EURCONTROL planning series of PBN Manual Familiarization Seminars in all ICAO Regions (Sept-Oct 2007: Bangkok/New Delhi) • Developing FAA Academy course for RNP (AR) procedure design training (PANS OPS)

  22. Synchronizing with Navigation Evolution Roadmap • PBN Roadmap & Navigation Evolution Roadmap were developed in close coordination and collaboration • Navigation Evolution Roadmap comment period closed December 22 • Over 360 comments received and are now being adjudicated • Navigation Evolution Customer Council (NECC) • Director of Navigation Services request to ATMAC • Develop updates for future versions of the Roadmap • Assure viability of the implementation process • Liaison between policy-makers and the aviation community • Forum to address concerns/issues

  23. ATC Aircraft Ops Concepts Ground Automation Benefits Metrics Mixed Operations Human Factors Phraseology Procedure Design Charting Aircraft Suffix Training Summary:Focus on Implementation & Integration Issues Criteria FMS Variances Equipage/Capability Database Integrity OEM Documentation

  24. Questions?

More Related