RVSM Airspace Analysis for CDM DRVSM Work Group – Houston Meeting

1. RVSM Airspace AnalysisforCDM DRVSM Work Group – Houston Meeting January 27, 2004

2. Purpose • Discuss airspace analysis approach to support RVSM implementation • Provide preliminary data on airspace changes • Appended - Background information on RVSM implementation in Domestic U.S.

3. RVSM Airspace Analysis • Airspace analysis through National Airspace Redesign (NAR) processes • RVSM Airspace Analysis Kickoff • All U.S. Centers and San Juan CERAP • Airspace and Traffic Management focal points • October 28 – 29, 2003 • Airspace analysis completion date - 7/1/04

4. Nov 2003 Jan 2005 June 2004 Oct 2003 Feb 2004 Sep 2004 User Coordination User Coordination RVSM Airspace Analysis Schedule Airspace Kickoff 10/28 11/1 - 12/31 Internal Analysis Inter-facility Analysis NAR tasking ends here: July 1, 2004 12/15 - 2/28 Modeling (SDAT) as needed 2/15 - 6/30 Frequency Assessment 2/15 - 6/30 Define Airspace, SOP/LOA & automation changes 6/15 - 8/31 DRVSM Go/Delay 9/15 Revise SOP/LOA and automation 9/15 - 1/20 1/20 Implement DRVSM

5. DRVSM Assumptions • RVSM aircraft will choose to fly from 1,000 -5,000 feet higher. • Current intra-facility and inter-facility altitude crossing procedures may need to be revised • Non-RVSM certified aircraft will operate between FL250 - 280 • No increases in number of sectors • RVSM should simplify air traffic control workload of equivalent volumes. • NAR support will be available for intra-facility and inter-facility meetings as needed.

6. Internal Airspace Analysis • Timeframe: Nov 1-Dec 31, 2003 • Traffic Analysis: • RVSM certified: Traffic breakdown by new flight levels • Non-RVSM certified: • FL250 - FL280 • Minimal aircraft requesting FL430 and above • U. S. Military (tactical), lifeguard and state aircraft exemptions

7. Internal Airspace Analysis: Stratification Considerations • Impacts of changes in aircraft operating altitudes and distributions among altitudes • Impacts of changes to cardinal altitudes • Ensuring FL300, 320, 340, 360, 380 & 400 are assigned to appropriate sectors • Other reasons to change vertical stratification? • Will stratification changes affect frequency service volumes? • Impacts of non-certified aircraft added within FL250 - 280 environment to stratification

8. Milestone #1: • Report results of internal facility analysis to Nat’l RVSM Airspace Leads: • List of sectors with potential impacts to stratification • List of internal procedures potentially impacted • List of potential frequency service volume changes • Draft due to Nat’l Airspace Leads by 12/18/03 • Copy to facility RVSM focal points • Final Report due NLT 12/31/03 • Leads will provide desired report format

9. Milestone 1 Status • Reports summary from 22 facilities • Follow-up activities on-going • Note: New sectors outside of RVSM program

10. External Analysis • Timeframe: Dec 15, 2003-Feb 28, 2004 • Stratification analysis – similar to internal analysis, but between facilities • LOA’s • Historical Traffic Management Initiatives • Involve Canadian/Mexico facilities • Initial coordination meetings - early Jan. • Two national meetings – half at each • Some mid-continent facilities to attend both

11. Milestone #2 • Report results of external facility analysis to RVSM Airspace Leads: • Update - sectors with stratification impacts • Update – internal procedures impacted • LOA procedures impacted • Update - potential frequency service volume changes • Report sectors that are proposed to change • Include categorization (H, M, L) • Report to Nat’l Airspace Leads NLT 2/28/04 • Copies: NAR PMO, MITRE, Regional ALT members & facility RVSM focal points • Nat’l Airspace Leads will provide desired report format

12. Modeling • Timeframe: Feb 15-June 30, 2004 • SDAT (analytical tool) level, as needed • MITRE support • Send proposed sector, LOA/SOP changes. • MITRE will supply revised data bases.

13. Final Report • Report: • Sectors with stratification changes – include description of change • Procedure changes – include description of change • Due NLT 7/1/2004 • Provide to Nat’l RVSM Airspace Leads • Copy to facility RVSM focal points and regional ALT members

14. Implementation of RVSM • Not a part of this tasking • Responsibility assigned to Air Traffic Manager (ATM) • ATM will task implementation of: • Revision of LOA’s & SOP’s • Implement vertical boundary changes • Adaptation changes • Training • LMR • Implementation Date: Jan 20, 2005

15. Airspace Related Activities • Briefed ASR concerning potential frequency impacts • Briefed AOS concerning foreseen automation impacts • Participated in Tri-lateral meeting with Mexico and Canada • Follow-on bi-lateral meetings: • Canada will participate in U.S. January Coordination meetings • Meeting of Mexico with ZLA, ZAB and ZHU planned for February 18-20 • Identified potential RNAV/RNP equipment filing suffix issue • Advanced Notice to be contained in January 22 NOTAM publication

16. Discussion

17. DRVSM Program Background

18. DRVSM Program Objectives • Implement DRVSM from FL290-FL410 in the airspace of the United States, Alaska, the Gulf of Mexico where the FAA provides air traffic services and the San Juan FIR. • DRVSM is scheduled to be implemented on January 20, 2005 0901UTC. • Six new altitudes available immediately upon implementation – new “capacity” for solving separation problems vs. new “capacity” for traffic growth.

19. Air Traffic DRVSM Responsibilities

20. RVSM AirspaceNon-RVSM Airspace FL410 FL 410 FL 400 FL 400 FL 390 FL 390 FL380 FL 380 FL 370 FL 370 FL 360 FL 360 FL 350 FL 350 FL 340 FL 340 FL 330 FL 330 FL 310 FL 300 FL 320 FL 320 FL 310 FL 300 FL 290 FL 290 RVSM Altitudes

21. Operator/Aircraft Categories Percent of Total Flights Projected RVSM Compliant Cumulative Total ATA, Airlines, Large Air Cargo operators 60% 60.0% 60% NACA Operators 1.4% 1.4% 61.4% Non-US Operators/Aircraft 5.6% 5.6% 67% RAA, Regional Jet operators 14% 7.0 - 10.5% (50 - 75% compliant) 74 - 77.5% DOD 1.5% .9% 74.9 - 78.4% Small Commercial and GA Operators/Aircraft 16% 8 - 12% (50 - 75% compliant) 82.9 - 90.4% Unknown 1.5% Range of Compliance Projected for Jan 2005 82.9 - 90.4% Projection of RVSM Compliance Jan 2005

22. N. Canada RVSM results

23. European RVSM results

24. Memorandum of UnderstandingFAA and DoD • Memorandum of Understanding signed between FAA and DoD in December 2001. • Agreement governs the use of DRVSM Airspace by DoD aircraft. • Policy: The FAA will accommodate non-compliant DoD aircraft operation within DRVSM airspace. Note: Large DoD transport and tanker fleets are already RVSM compliant

25. Major Milestones • Published Final Rule October 27, 2003 • Safety Assessment July 2004 • Operational Readiness September 2004 Assessment (Go/Delay) • RVSM Implementation January 2005

26. FAA HQ Deliverables (1) • International Agreements with Mexico, Canada and Caribbean States • National Procedures, Order Changes and Briefing Guides • NAS Automation Changes • Analysis support within Airspace Redesign for sectorization changes

27. FAA HQ Deliverables (2) • ATFM Flow Plans for Initial Operations • Non-Approved Aircraft biggest liability • Flight Planning compression could overload sectors • Training Plan templates • National CADRE training instruction • Facilitation of local coordination to prepare for implementation (workshops, telecons, templates)

28. FAA HQ Deliverables (3) • Labor I&I negotiation • Funding support for simultaneous national training effort • Any other assistance required to keep program on track!

29. Regional & Facility Deliverables • Revisions to Virtually all En Route LOAs and SOPs • Local validation that all NAS automation changes thoroughly tested and properly implemented • Simultaneous DYSIM Training by CADRE of Instructors for over 9,000 controllers • Local labor I&I on issues not covered by national agreements • Local coordination with industry within established forums • Leadership to keep program on track!!