Aeronautical Information Services (AIS) Data Link

Ernie R. DashRaytheon (FAA FISDL)

RTCA SC-206/EUROCAE WG-44/53

Weather in the Cockpit (WIC)

August 9, 2006

2

AIS and Met Data Link Services

• Joint RTCA SC-206/EUROCAE WG-44/53 tasks:– Define requirements for AIS and Met Data Link Services– Develop necessary data link system “standards and approval”

documentation• Insures standardization and interoperability

• Organized into two Subgroups– AIS Subgroup– Met Subgroup

• Meetings– Meet quarterly, Alternate between Europe and US– 1st Meeting: July 2006– 6th Meeting: RTCA/Washington DC, 11-15 September

• Approach– Follow guidelines for approval of Air Traffic Service data link

communications

3

RTCA DO-264 / EUROCAE ED-78“Guidelines for Approval of the Provision and Use of Air Traffic Services

Supported by Data Communications”

• Provides guidance and templates for “Minimum Acceptable Criteria” needed to support “Approvals”– Approvals include:

• Operator Operational Approval (i.e., Ops Specs, AC)• Aircraft Type Design Approval (i.e., TSO, STC)• ATS Provider Operational Approval (?? – a “New Cat”)

– Minimum Acceptable Criteria are provided as either:• Process Objectives, and/or• Guidance for Evidence (that the Process Objective was met)

– Key Process Objectives include:• OSED – Operational Services and Environment Definition• SPR – Operational Safety and Performance Requirements

– OSA – Operational Safety Assessment– OPA – Operational Performance Assessment

• INTEROP – Interoperability Requirements

4

AIS / MET OSEDs – Drafts in Progress

• AIS Data Link Services – (Uplink – Combined into one OSED)

– NOTAM Text

– NOTAM Graphic

– AIRAC Cycle – Complete

– AIRAC Cycle – Updates

– Non-AIRAC Cycle – Complete

– Non-AIRAC Cycle – Updates• MET Data Link Services – (Potential for two separate OSEDs)

– Ground MET Data (Uplink)

– Aircraft MET Data (Downlink/Crosslink)

5

Met OSED Challenges (Uplink)

• Defining specific ground Met products required to perform cockpit functions

– Three classifications of pilot use or cockpit application identified• Planning Decisions (greater than 20 minutes up to two hours or more)

• Near-Term Decisions (1-20 minutes)

• Reactive Decisions (immediate to less than 1 minute)

– Candidate METLINK products are classified relative to the pilot use or cockpit application

• Defining the required timelines for data link communications and cockpit receipt

– Little/no ICAO Annex 3 guidance

– Especially new (potential) products

6

Pilot Use / Cockpit Application

Decision

Time

Flight Environment

Terminal Cockpit

Briefing Briefing Cruise Terminal Area Hazardous Situation

Day/Hours

Hours Planning Decisions

Hour

1-20 Minutes Near-Term Decisions

< 1 Minute Reactive Decisions

7

Candidate METLINK Products

Candidate

Meteorological

Products

METLINK Data

Point Data Text Area Vector Graphic Gridded Data

Aerodrome Products

Meteorological Aerodrome Report (METAR) P / N

Terminal Aerodrome Forecast (TAF) P

Wind Shear Warnings N / R

Volcanic Activity Report P / N / R

P = Planning Decision Product

N = Near-Term Decision Product

R = Reactive Decision Product

8

•Current/Forecast Icing Potential (CIP/FIP)     [ CIP Performance Statistics ]     [ FIP Performance Statistics ]

Future Product (?): AWC – ADDS - Icing

               

0200 UTC CIP0200 UTC CIP-SLD0300 UTC FIP0400 UTC FIP0600 UTC FIP0900 UTC FIP1200 UTC FIP

•See more detailed CIP/FIP plots in the Java Flight Path Tool

•Freezing level graphics:0-hour    3-hour    6-hour    9-hour    12-hour 

•Current Icing advisories:

                                                            

                     

•Pilot reports of Icing:

                                                                    

               

FYI/Help

9

Data Link Service Criteria

Broadcast

10

RCTP Communications Time Criteria: METLINK Planning (and Near-Term) Products

TRANSACTION

Initiator1 Responder

2

10 Sec4

95% Met Data Hub Response Time

3

30 Sec4

Transaction Expiration

Time

20 Sec4

95% Transaction

Time

Operational Data link service Initiation

Operational Data link service Completion

REQUEST

RESPONSE

Notes:1. Initiator = Pilot or Avionics2. Responder = Met Data Hub; Met Service Provider populates the Hub with appropriate data (see Note 3)3. Met Data classified according to each category of service:

Planning Decision Support Near-Term Decision Support Reactive Decision Support

4. RCTP Transaction Times based on published criteria for D-ATIS (Ref: DO-290/ED-120: Safety and Performance Requirements for Air Traffic Data Link Service in Continental Airspace, Table 1, page 211)

11

Service Time ConstraintsCOCR Version 1.0: Pg 85/Table 5-3

Parameter ET TT95 C AUSE APROVISION I

RCTP: D-ATIS 30 20 0.995 0.993 N/A 10-5

DO-290/ED120: Pg 211/Table 1

12

Summary

• AIS and MET Data Link Services being defined

– Minimal existing ICAO / WMO (or FAA) guidance that may be applied to defining OSED criteria

– Feedback / input from WIC Workshop welcome

• Many RTCA SC-206/EUROCAE WG-44/53 Members attending WIC including :

– MET Subgroup Chair: Rocky Stone (United Airlines)

• Meetings open for all to attend

– Proceedings posted on website: http://www.avmet.com