1. By: R. Scott Stevens, ATO-P, Aviation Weather Office, Weather Policy & Requirements Group, WTIC Program Manager Date: October 9, 2008 Federal Aviation Administration SEGMENT ONE NEAR TERM DEMONSTRATIONS Integration of Ground and Cockpit Weather into Decision Making

2. 2 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 2

3. 3 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 3 Objectives of WTIC The objective of the Weather Technology in the Cockpit (WTIC) program is to ensure the adoption of cockpit, ground, and communication technologies, practices, and procedures that will: –Provide pilots with shared and consistent weather information to enhance common situational awareness –Provide airborne tools to exploit the common weather picture –utilize the “aircraft as a node”, functions to autonomously exchange weather information with surrounding aircraft and ground systems –Facilitate integration of weather information into cockpit NextGen capabilities (e.g. Trajectory Based Operations) –Result from WTIC R&D supporting certification and operational approvals

4. 4 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 4 What Must Be Accomplished to Effectively Conduct Weather Technology in the Cockpit Services and Operations 1.What incremental weather information is needed in cockpit operations (and when is it needed)? a.For tactical decision support (121, 135, 91)? b.For situational awareness (121, 135, 91)?

5. 5 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 5 What Must Be Accomplished to Effectively Conduct Weather Technology in the Cockpit Services and Operations 2.What communication services are needed to provide the weather information needed in cockpit operations as outlined in answering (1) above? a.Signals in space? b.Ground support /infrastructure (interface/processing/archiving, etc.)?

6. 6 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 6 What Must Be Accomplished to Effectively Conduct Weather Technology in the Cockpit Services and Operations 3.What airborne equipage and/or software is needed? a.Communication equipage/software (121, 135, 91)? b.Interface/processing/storage, etc. equipage/software (121, 135, 91)? c.Display and decision support equipage/software (121, 135, 91)? d.Sensor equipage/software? e.Additions/modifications to existing onboard technologies (e.g. FMS)?

7. 7 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 7 What Must Be Accomplished to Effectively Conduct Weather Technology in the Cockpit Services and Operations 4.What policy and guidance will need to be modified, created, or rescinded in support of (1) through (3) above (121, 135, 91)? a.Certifications (avionics, procedures, etc.)? b.Standards? c.Guidance (AIM, Pilots Handbook, etc.)? d.Rules and regulations?

8. 8 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 8 What Must Be Accomplished to Effectively Conduct Weather Technology in the Cockpit Services and Operations 5.What training will be needed to support and implement the results of (1) through (4) above (121, 135, 91)?

9. 9 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 9 Thank you Please hold questions till end of Near Term Demonstrations - Segment One

10. 10 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 10 BACKUP SLIDES

11. 11 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 11 Conclusion Research is needed: Integration of weather information into the fully implemented NextGen highlights the need to address several questions: –What Weather information is needed in the cockpit and what are the “ilities” associated with each element? –What technologies for cockpit display of weather information can be utilized and what / how will display be standardized? –What technologies for cockpit decision support will be necessary to support Nextgen Capabilities (e.g. TBO)? –What comm/datalink capabilities will be needed to support various onboard processing and visualization capabilities and to support the aircraft as a node? –What procedures, standards, certifications, and equipage changes will be necessary? –What ground interface and processing capabilities will be required for seamless ground-air and air-ground exchange of weather information?

12. 12 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 12 Challenges Allocation of capabilities between the ground systems and the aircraft systems has yet to be determined for the near, mid, and far terms With the standards development and avionics upgrade cycles, we have a small window of opportunity to identify priorities for aircraft equipage through 2018

13. 13 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 13

14. 14 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 14 2025 NextGen Concept Net-Enabled Information Access Performance-Based Services Weather-Assimilated Decision Making Layered, Adaptive Security Broad-Area Precision Navigation Trajectory-Based Aircraft Operations “Equivalent Visual” Operations “Super Density” Operations Key Capabilities Operating Principles “It’s about the users…” System-wide transformation Prognostic approach to safety assessment Globally harmonized Environmentally compatible to enable continued growth

15. 15 Federal Aviation Administration Weather Technology in the Cockpit September 17, 2008 15 Assumptions NextGen benefits will rely on aircraft avionics changes Initial operational improvements should be based on aircraft capabilities that are already available or are in development, with standards already completed or well along Avionics implementation timeframes will not be significantly shortened Implementation decision will be driven by a solid business case (i.e. quantitative data) If operational concepts are not well defined now, they are unlikely to be implemented by 2018