Small Aircraft Manufacturers Association

Weather in the Cockpit Workshop IIConsensus WIC ConOps Development

18 October 2006

SAMA

Weather in the Cockpit Workshop II18 October 2006

• Welcome to NBAA and thanks!• Weather in the Cockpit Workshop I, quick summary• Workshop II Agenda

– Opening Remarks and Welcome. NBAA, Steve Brown, Senior Vice President, Operations

– FAA AVS Vision Update– JPDO WxIPT-i ICWP Update– EFB Update and Operational Benefits. United Airlines, Brian

Haynes, EFB/Weather Project Lead– Draft WIC Concept of Operations review and comment

• Please sign in!

Problems to be Addressed“…is authorized for operational use by meteorologists and dispatchers.”

• What is needed for a source of weather information to be authorized for unrestricted operational use? – What is needed beyond AWTT D4 (operational) to allow

unrestricted use?– Is AWTT approval for the algorithm, or the implementation of that

algorithm?– Now, what about vendor-created weather products, both value-

added features and products created using vendor software?• Approval of process to obtain, verify, grids; produce products

uniformly from grids; transmit to data link processor and aircraft; parallel transmission to AOC, ATC

• Weather impact translation issues associated with DSS

How to Get There…Needs are there, technology is ready

We need to consider • The FAA environment

– ADS-B driven; vendor will provide the service if the FAA specifies it, industry demands it

• Weather service providers are moving ahead—WxWorx, Garmin, WSI, Honeywell, Rockwell, etc…– Customer driven, various links available

• What is needed: a process to link AWTT D4 to regulatory “operationally suitable” status for all users– Makes total approval traceable by product

Define “Weather in the Cockpit”

“…a system combining and presenting various types of weather information [or decision support, weather impact variables] obtained through multiple data-link sources, on-board remote sensors, and in-situ sensors to aid crews with effective flight management” NASA AvSP

“Employ the aircraft as a node in the National Airspace System’s communications, navigation, and surveillance (CNS) network. Enable flight deck weather information technologies that allow pilots and aircrews to engage in shared situational awareness and shared responsibilities with controllers, dispatchers, Flight Service Station (FSS) specialists, and others, pertaining to preflight, en route, and post

flight aviation safety decisions involving weather.” FAA-AVS Vision

FlightInformation

DecisionAids

Processor Presentation

Position

Flight Plan

NavigationInformation

Aircraft Capabilities

User Capabilities

UserInterface

OnboardSensors

WeatherProducts

Ground WxSystem

Wx Report

Data Link

Data Link

Special Use Airspace

Traffic Terrain

Obstacles

Other Aircraft Air-Air

Air-Ground

Ground-Air

Data Link

Satellite Observations

Aviation Weather Information System

Goals and ObjectivesWorkshop I

• Gain consensus within and between the user, research, and regulatory communities on– Weather related problems with aircraft– Weather information in the cockpit that is needed

to address these problems– How best to get advanced weather products into

the cockpit/flight deck• Develop a roadmap of tasks, dates, needed

to ensure continued operational approval of weather products

• Plan for future forums as needed

Implementation Issues-AVS Vision

• Use of Airborne Data Sensors• Development of Weather Products• Training and Human Factors Considerations• Integration of Weather Data from Multiple Sources• Determine What Weather Information is Needed By Each

Group of Decision Makers

Action, request from AVS: Develop strawman WIC Concept of Operations that represents consensus from group. AVS POC is Steve Van Trees

Breakout SessionsDefine User Needs, Workshop I

• Low-end general aviation, helicopters—Parts 91/135

• High-end unscheduled—Parts 91/135, DoD, NBAA

• High-end scheduled—Parts 121/135

Breakout Session

• Issues– Operational problems with weather– Weather information needed in the cockpit– Obstacles– Gaps in the current way of operating—informational and

procedural– Suggested interventions to resolving obstacles and gaps

Obstacles Identified During Breakout Sessions

• Aircraft equipage

• Access to grids or data

• Certification or approval of product grids

• Certification or approval of vendor or value-added features

• Information content standardization for SSA

• Bandwidth availability

Product Areas from BreakoutsHigh Spatial/temporal Resolution

Graphical, Related to Flight Profile

• Turbulence• Icing• Ceiling and visibility

– Terminal– National

• Storms– Winter– Convective

• Oceanic/remote• ADDS

Review of ConOps

• R&D Advisory Committee, REDAC– Advisory to FAA on weather decision support to

ATM– This ConOps is a coordinated report-out to the

REDAC from our group– REDAC “WIC Day” on 13 Dec. An opportunity for

vendors, users, and R&D community to present WIC-related R&D to the REDAC

• ConOps is a coordinated document for FAA-AVS

Review of ConOpsComments Received

• NASA Langley, Ray McAdaragh (already included in draft)

• FAA AIR-130 and others (Cathy Bigelow)• Ray Lafrey and others• Gene Wilhelm, MITRE

Note that the draft ConOps is meant to be totally consistent with current NGATS planning by the JPDO. It is a living document; comments will always be welcomed.

Review of ConOps

First, comments from the group…

• Cathy Bigelow’s markup embodies most others’ concerns. I recommend we use this as our point of departure.

• Then, other comments• Finally, capture business aviation operators’ inputs• Recommend reference to the draft ConOps as we go• Remember—this is a consensus document to meet

the needs of AVS and REDAC

What’s Next?

• Timeline for process implementation: To mesh with ADS-B deployment phases at the least, but as quick as possible

• OPR: FAA AVS (Flight Standards and Certification)– Users, R&D communities, vendors make implementation a

team effort– Steve VanTrees

• Complete and coordinate Weather in the Cockpit Concept of Operations. This is a group consensus, requested by FAA-AVS, coordinated by NCAR

• Next meeting