Operational Context and Use Case Focus Group

1. Operational Context and Use Case Focus Group Use Case May 30, 2019

2. Agenda • Document Delivery Schedule • Aeronautical Use Case Document – Review

3. Delivery Schedule • Due to shutdown, presented Flow draft and Meteorological storyboard in February • Return to normal schedule in April • Deliver one domain Use Case Document every two months Added DLD to April 2019, all other Ops Context Docs move 1 month to the right *OCD – Ops Context Document UCD – Use Case Document

4. Use Case Document Domains Storyboard – 4/25 Draft – 5/30 Closeout – 6/27 Document Complete Document Complete Document Complete

5. Review Aeronautical Use Case

6. Aeronautical Use Case Table of Contents 1 Introduction 1.1 SWIM Aeronautical Information Services 1.1.1 SWIM Aeronautical Data Functionality 1.1.2 Aeronautical Information Service Definitions 1.2 Overview of Use Case 2 Problem Statement 2.1 Current State 2.2 Perspectives 2.3 Current State Operational Example 2.3.1 Overview of Departure Operations in the Current State 2.3.2 En Route Operations in the Current State 2.3.3 Arrival Operations in the Current State 3 Future State 3.1 Data Exchanges 3.2 Future State Operational Examples 3.2.1 Departure Operations in the Future State 3.2.2 En Route Operations in the Future State 3.2.3 Arrival Operations in the Future State 3.3 Benefits 3.4 Conclusion Appendix A – FNS-NDS and SFDPS Airspace Messages Appendix B – Acronym Listing

7. Introduction • Airspace constraints and NOTAM data are critical to stakeholders • Possessing current and accurate airspace/NOTAM data is necessary • Acquiring usable airspace/NOTAM data can be challenging • Data changes frequently, making data freshness a challenge • Message formats make it difficult to determine which flights are impacted • Uncertainty about airspace/NOTAM data creates operational problems • Flights are unnecessarily routed around Special Activity Airspace (SAA) that is inactive • Flights are tactically rerouted after departure to avoid SAA • Last minute airspace/NOTAM changes cause safety concerns for flight crews • An improved method of sharing airspace/FNS data is needed

8. Data Flows in Current State

9. Overview of Use Case • AUs must understand airspace constraints and NOTAMS • Thorough flight planning – including understanding NOTAMs and airspace constraints – is critical • Much data is available • Accessing pertinent and timely data is currently a challenge • The lack of knowledge about airspace constraints or NOTAM activities may result in: • Increased Risk • Incident • Safety concerns • Less efficient flight • Violation of a FAR

10. Aeronautical SWIM Services • SWIM Flight Data Publication Service (SFDPS) Airspace data • Special Activity Airspace (SAA) • Prohibited areas: Areas where flight is prohibited. • Restricted Areas: Areas where flight access is sometimes restricted. • Temporary Flight Restrictions (TFR) Areas: Flights are limited due to VIP movement, security • Federal NOTAM System (FNS) NOTAM Distribution Service (NDS) • NOTAMs are notices about information essential to flight operations • Disseminate changes about facilities, services, procedures, or hazards in the NAS • Data is transitory-not known far enough in advance to be published by other means

11. Departure Activities: Current State Data

12. Delays Result from Imprecise Data “N123, Tower, Runway 25, cleared for takeoff.” “Tower, N123, we are going to need to delay here. We’re still checking our numbers due to the crane at the departure end of the runway.” Manual interpretation of data is slow & inefficient.

13. En Route Activities: Current State Data

14. Imprecise Data Results in Inefficient Routes CANCELLED R4404 Cancelled. Flight Crew Unaware. Longer route flown.

15. Arrival Activities: Current State Data

16. Partial Data Causes Uncertainty Is the TFR a problem? Are the centerline lights working yet? What is the condition of the runway with all this snow? Questions arise due to data uncertainty. TFR 3000’

17. Operational Problems Summary • Airspace/NOTAM data changes frequently, and the data is cumbersome • A large amount of airspace/NOTAM data exists • The data changes frequently • No effective means of efficiently managing this data exists • A solution is needed that will provide data that is: • Fresh • Easily accessible • Easily consumable • Flight specific • Understandable • Presented graphically • Readily available to flight crews • Can be displayed in relation to a particular flight plan

18. Overview of Future State Operations • Stakeholders will access SFDPS airspace/FNS data via SWIM • Airspace/FNS data will be shared in a machine-readable format • Stakeholders will receive current and planned activities and changes • Access to schedules, locations, boundaries will be improved • Graphical depictions of impacts will enhance understanding • AUs can determine the status, timing and impacts in all phases of flight • Flight crews will have access via EFB application • Situational awareness will increase with less uncertainty • AUs will be able to devise more effective solutions • Fewer tactical interventions will be needed

19. Future Airspace/FNS Data Flows

20. Departure Activities: Future State Data

21. Improved Data Maximizes Safety and Efficiency R4404 will be active and we have a good route to avoid it. The crane at the end of the runway is no problem. No other NOTAMS affect us. “Tower, N123 is ready to go.” Clear data enhances operations

22. En Route Activities: Future State Data

23. Reliable Data Facilitates Efficiency Center, N123. We see R4404 is now inactive. Request direct to destination. Old Route • CANCELLED New Route N123, correct. R4404 is inactive. Proceed direct. Current data enhances operations

24. Arrival Activities: Future State Data

25. Reliable Data Improves Confidence and Efficiency The EFB says the TFR has ended. The centerline lights are working again. The runway was plowed. The braking action is good. We are ready for the approach. TFR Cancelled Accessible data enhances operations

26. Data Availability Using FNS/Airspace DataImproves AU event awareness and strategic planning

27. Conclusion • SFDPS airspace/FNS data will facilitate greater efficiency with reduced workload by presenting data that is user-friendly. • Data will be clear, current, accurate, accessible • Updates will be received quickly • Graphical depictions will be available • Time constraints will be clear • Data will be flight-specific • Data will be available to flight crews on EFB • When data is well understood and easily accessible, AUs will be equipped to make improved decisions.

28. Benefits • Better understanding of airspace/FNS data • Clearer picture of impacts • Improved routing decisions • Fewer delays • Fewer unanticipated impacts • Improved fuel efficiency • Increased predictability • More on-time arrivals • Improved resource management • Improved TFM system collaboration • Improved customer experience

29. References • SWIFT Focus Group Website • http://connect.lstechllc.com/index.cfm/main/opconfocusgroup • Aeronautical Use Case Document Draft v0.2 • http://connect.lstechllc.com/files/Aeronautical%20Data%20Use%20Case%20Doc%20Draft%20v0.2_2019_05_30.docx • Next meeting is scheduled for June 27, 2019 • Will close out Aeronautical Use Case • Contacts • Jay Zimmer jay.zimmer@lstechllc.com • Felisa White felisa.white@faa.gov

30. Backup

31. Problem Statement • Acquiring accurate and fresh airspace/NOTAM data is difficult for AUs • Occasionally SAA is published as active during specific times, yet is never activated • Some SAA is managed by NOTAM but often NOTAMs are not current • Military airspace is often restricted, but is not actually being used • SAA can become active after a flight departs, causing an unplanned reroute • Airspace/NOTAMS change frequently, causing difficulties accessing fresh data • AUs do not have clear understanding of airspace/NOTAM data • Awareness of airspace/NOTAM data is difficult due to volume of data and accessibility • Creates safety/efficiency concerns • Flight planning and management become more difficult • Flights must be re-routed tactically, creating problems for AUs and ATC • Flights are often re-routed unnecessarily • Better methods of managing airspace/FNS data are needed

32. Departure Operations in Current State • Before departure, flight crews are given several pages of NOTAMS • Flight crew must manually sort through data • Flight crews have too much data and insufficient clarity • Cryptic language makes understanding difficult • Absence of graphics makes understanding location of constraints and obstacles difficult • Timings are difficult to determine • Results in flight crews having limited understanding of impacts • Vendor-provided products may provide some NOTAMs visually, but solutions are incomplete

33. En Route Operations in Current State • Sometimes SAA is activated or deactivated without AU knowledge • If SAA is activated and AU is unaware, tactical reroutes occur • If planned SAA activity is cancelled, stakeholders could benefit by flying more efficient routes, but often are unaware • Either situation has negative impact on regulatory compliance and efficiency • Unplanned or unnecessary deviations around airspace • Use of less efficient arrival or departure routes • Increased flight crew and controller workload at critical times

34. Arrival Operations in Current State • Flight crew reviews NOTAMs for destination before flight • During the flight, new NOTAMs are published at destination • Equipment outages, runway and taxiway closures occur • Runway conditions change continuously, especially during snow events • SAA can be activated • During busy arrival phase it is difficult to search for pertinent NOTAMs • Pilots must interpolate the data manually • Fuel, weather, and approach challenges arise • Pilots can be fatigued • No automated sorting mechanism or display tool is available to help • Introduces possibility of error or exclusion of pertinent NOTAM

35. Departure Operations in Future State • Before flight, airspace/FNS data presented to AOC and flight crew on EFB • Data is flight-specific and sorted for relevance • Textual descriptions are in plain language • Graphic depictions are displayed for easier understanding • Activation times are coded for easy understanding • Locations of obstacles are plainly displayed • No plotting is required • No manual calculation of times is required • Confidence in having thorough airspace/FNS understanding goes up • Flight planning is simplified and more efficient • Routes are appropriate for situation

36. En Route Operations in Future State • As flight progresses, airspace/FNS data is continuously monitored by automated system • Alerting mechanisms will notify pilot of changes on EFB • Enroute and destination conditions will be monitored • Current activities and changes will be displayed on moving map display • More time available to understand impacts and devise solutions

37. Arrival Operations in Future State • During a flight, NOTAMs change • Equipment outages, runway and taxiway closures occur • Runway conditions change often, especially during snow events. • Flight crews will have sorted airspace/FNS data available on EFB • Configurable alerts on EFB will notify flight crews of changes • Airspace/FNS data will be presented graphically to aid understanding • Pertinent times will be displayed • Reduces heads-down time in cockpit • Ensures pilots have current data • Improves confidence

38. Perspectives • Air Traffic Control: • Responsible for safe and efficient use of airspace • Success is defined by efficient use of airspace, effective strategic planning, minimized impacts of SAA, and minimal use of tactical interventions that add delay to flights • Airline Flight Ops: • Responsible for regulatory compliance, on-time operations, managing resources, maintaining flight schedules, fleet management, and applying the airline’s business model. • Success is defined by regulatory compliance, predictable operations, on-time operations, effective resource management, reduced fuel use and positive customer experience. • Flight Crews: • Responsible for safety risk management, fuel management, SAAFNS compliance, on-time operations, regulatory compliance • Success is defined by maintaining appropriate safety margins during flight, efficient fuel management, regulatory compliance including SAA avoidance, on time operations.

39. Metrics • AU Flight Ops • Safe flights • Efficient and effective operations • Efficient delay management • Minimum fuel consumption • Increased predictability • More on-time arrivals • Effective resource utilization, (gates, aircraft, human resources) • Regulatory compliance • Improved customer experience

40. Metrics • Flight Crews • Improved awareness of airspace/FNS data • High level of confidence in data • Improved safety risk management • Regulatory compliance • Efficient routings • Minimum fuel consumption • On-time operations • Improved customer experience

41. Metrics • Air Traffic Control • Safer flight operations • Maximum airspace usage • Minimum impacts from SAA/NOTAMs • Fewer tactical interventions needed • Effective traffic management initiatives • Effective delay management • Effective collaboration with AUs