1. Complex Procedure Development Plan
LAAS
Complex Procedure Development Plan
for the
Memphis Terminal Area
20/21 November 2002
Bob Beal ISI/AND-720

2. Meeting Overview LAAS Program Commissioning 6 Cat I LRIP Systems
Memphis, Phoenix, Houston, Seattle, Chicago, Juneau
LAAS Program Office in Process of Awarding Development Contract
One Essential Benefit Users Expect from LAAS is Ability to Support Complex Terminal Operations
Purpose of this Meeting is to Begin to Define LAAS Procedures for MEMPHIS

3. WAAS and LAAS

4. LAAS - Extends Precision Approach Guidance from 10 to 20NM
Category I, II, III Precision Approach Capability with Extended Range
- Extends Precision Approach Guidance from 10 to 20NM
- Provides PVT Coverage to 60NM
Multiple Runway Coverage
One LAAS Will Provide Precision Approach Service for Multiple Runway Ends at an Airport
Advanced Approaches/Departures
To Avoid Obstacles, Noise Sensitive Areas, or Congested Airspace
Remote Coverage
Augments Wide Area Augmentation System (WAAS) in Various Locations (Terrain, Traffic Volume)
Aircraft Surface Navigation
Possible Data Input for Surface Movement (Supports)

5. LAAS

6. Initial LAAS Sites ANE AGL ANM AEA AWP ACE ASO ASW AAL Seattle Chicago
Phoenix
ASO
Memphis
AGL
Chicago
AAL
Juneau
AEA
Atlantic
City
ASW
Houston
Oklahoma

7. Procedure Development Process
AND-720 (Dave Peterson) has been Meeting with LAAS Users, Air Traffic Representatives, and Procedure Developers in Memphis, Chicago, and Juneau to
Better Define Anticipated LAAS Benefits
Understand Desired LAAS Operations
Establish What the LAAS Operational Integration Team Can Do to Implement Those Operations
Goal is to Develop Consensus on FAA Projects to Implement Desired LAAS Operations

8. Potential LAAS Benefits
Achieve Consistent, Accurate, Repeatable Performance
Expand Closely Spaced Parallel Runway Ops
Support Advanced/Complex Procedures
Support Surface Movement Applications
Eliminate Need for In-Aircraft Procedure Database
Support Extended Arrival Procedures

9. Potential LAAS Benefits
Support RNP Operations
Support Adjacent Airport Operations
De-conflict Airspace
Ability to Use Single LAAS System to Support Approaches at Multiple Runway Ends
Improved Terminal Area Surveillance Through Improved Navigation Accuracies
Reduce Aircraft Separation Requirements

10. Potential LAAS Benefits
Reduce Air Traffic Controller Workload
Reduce Obstacle Clearance Requirements
Ability to Change or Create Approach Procedures without Infrastructure Changes
Ability to Implement Multiple, Segmented, or Variable Glide Slopes
Support Runway Incursion Avoidance Systems
Compress the Density of Terminal Operations

11. Desired LAAS Capabilities
CAT II/III LAAS
Complex Terminal Operations
Arrivals
Approaches
Departures
Missed Approaches
Adjacent Airport Operations
Linear FAS/Simultaneous Parallel Approaches
RNP Operations
Surface Navigation
4-Dimensional Guidance

12. Chicago Improve Triple Convergent Procedure
Taking Three Phased Approach
Replace Vectored Approach to 9L with Guided LAAS Procedure Using RF-Leg
Reduce Aircraft Separation Requirements for Entire Procedure
VMC
IMC
Will Also Consider Potential Missed Approach Improvements

13. Triple Convergent Approach – Chicago O’Hare
               
                                                                                                                                   
Triple Convergent Approach – Chicago O’Hare

14. Guided Complex Approach to 09L

15. Juneau

16. Memphis

17. Top Level Complex Procedure Development Schedule

18. Memphis 1

19. Memphis 2

20. Memphis 3

21. Prototype Procedures Development Plan
Meet with Region, Airport, Users to Define Procedure Requirements
10/15/02
2/15/03
Establish Procedure Development Team (ASO, ATC, AFS, AVN, AND, ACB, Users …)
11/01/02
Review Existing Ops and Procedures, Identify Areas for Improvement, Identify Constraints, Assess How to Apply LAAS Attributes, etc.
1/15/03
Develop Conceptual Procedures
11/15/02
2/01/03
Prioritize Conceptual Procedures Considering Issues, Ease of Implementation, Improvement Potential. Consider Environmental Impacts, ATC Monitoring Requirements, Conflicts, etc.
12/01/02

22. Prototype Procedures Development Plan
Develop Prototype Procedures
2/15/02
8/01/03
Define Detailed Procedure Requirements
5/01/03
Establish RNP Requirements
Identify/Implement Needed Charting Changes
4/01/03
6/15/03
Chart Prototype Procedures
5/15/03

23. Follow-on Activities Establish Initial FAS Data Requirements 3/01/03
8/01/03
Analyze Prototype Procedures
5/01/03
Develop Proposed Parameters
4/01/03
6/15/03
Coordinate with RTCA/ARINC
Prototype Avionics/LAAS Test Facility
10/01/02
12/15/03
Develop Initial Software
Validation Test Flights
Final Software Delivery

24. Follow-on Activities
Validate Memphis Complex Procedure Implementation, FAS Parameters, Avionics Implementation, CONOPS, Database
5/01/03
10/01/04
Test Planning
10/01/03
Develop Memphis Procedure FAS
8/01/03
9/01/03
Code Procedure in FMS Database
Develop Memphis VDB Uplink
Validate Memphis Procedure
Data Collection Flights
6/01/04
Analyze Data/Report Results
3/01/04
9/01/04
Finalize Memphis Complex Procedure Implementation, FAS Parameters, CONOPS, …

25. Follow-on Activities Develop/Commission Complex LAAS Procedure
10/01/03
5/01/05
Develop/Validate TERPS Criteria
10/01/04
Generate Commissioned Memphis Procedure
12/01/04
RAPT/NAPT Coordination, IAPA Software Development and Training
Prepare Procedure
2/01/05
Flight Inspect and Publish Procedure
9/30/05
Other Associated Activities (Avionics Standards, Regulations, ATC Training, LAAS System Upgrades
1/01/04
8/30/05

26. Procedure Development
Review Existing Memphis Operations/Procedures
Discuss Advantages/Disadvantages/Areas for Improvement/New Concepts/Issues/Constraints
Initiate Process for Developing Conceptual Procedures
Discuss Implementation Priorities
Ease of Implementation
Potential Operational Benefit (Users/ATC)
Identify Procedure Development Team Members from Memphis Area and Southern Region

28. Backup Slides

29. LAAS Service Volume

30. LAAS Service Volume

31. LAAS Service Volume

32. LAAS Service Volume

33. Schedule Level 1_1

34. Schedule Level 1_2

35. Schedule Level 1_3

36. Schedule Level 1_4

37. Schedule Level 1_5

38. LRIP Coordinators Phoenix Juneau Memphis Seattle Houston Chicago
Tim Roe
Paul Ewing
Juneau
Bob Beal
Campbell Motley
Memphis
Bob Beal
Campbell Motley
Seattle
Rich Cole
Paul Wagoner
Houston
Tim Roe
TBD
Chicago
Jeff Cochrane
Larry Oliver

39. Site Coordinators Each Site has a Primary and Backup Coordinator
Facilitate the Development of the Advanced Procedures
Assist AND-720 Establish a Development Team for Each LRIP Airport
Coordinate with the Airports and Regions (Following Site Visits by AND-710 and AND-720)
Coordinate Development Team Meetings and Activities
Refine Detailed Schedules for Each Site, Track Progress, and Ensure Schedules are Being Met
Identify Issues