Data Communications Federal Aviation

Administration

DCL Service Validation

Proposal

Presented to: Data Comm Program

By: Andy Fry
Thane Inc.
Date: September 23, 2010
Overview
• Airplane Architecture effect on DCL
Services
• Review of Boeing Lab Findings
• DCL using Route Clearance parameter in
CPDLC Message element
• Validating DCL Service using Route
Clearance
• DCL Validation Summary

Data Communications Program Federal Aviation 2

September 23, 2101 Administration
Airplane Architecture effect
concerning DCL Services
• Federated Architecture – Hosted Capability in Avionics
– Boeing: 737, 747-400, 757 and 767
• An ATC uplink is received by the FMC, and “ATC” message indication is
provided on a forward field of view display along with aural alert, and
CPDLC message is displayed on a MCDU “Small” format display
– Airbus: 320, 330 and 340
• Similar as above except message is viewed on a DCDU or Data
Communications Display Unit
• Integrated Architecture – Integrated Processor
– Boeing: 777 and 787
• Similar to above Federated architecture except that the uplink message is
automatically displayed in a separated forward field of view datablock
display area.
– If necessary a “Large” format display is available to display large
CPDLC message in its entirety
– Airbus: 350 and 380
• Similar to the Boeing Integrated Architecture description

Data Communications Program Federal Aviation 3

September 23, 2101 Administration
 Review of Boeing Lab Findings
Non- FMC Loadable
message elements
cannot be viewed on
small format screens,
such as:
•UM73 Mandatory
Fields
•EDCT
•Beacon
•Departure Freq

•Airbus aircraft cannot auto-load Route Clearances using UM73 into their FMC

Data Communications Program Federal Aviation 4

September 23, 2101 Administration
Review of Boeing Lab Findings – Con’t

•UM80 – Route Clearance

Data Communications Program Federal Aviation 5

September 23, 2101 Administration
DCL using Route Clearance CPDLC
Message element
• Route and Route Segment Clearances
– UM73/80
• Replaces FMC Route in its Entirety
• Messages are identical and perform the same when used on the
ground
– UM79/83
• Only replaces a segment of the route that of which is uplinked
• Best when used as part of a revision and the whole route is not to be
uplinked – Validation requirement
– Possible route discontinuity may be inserted in a route if a
UM79/83 fix does not already exist in the FMC route
• Airport and Procedure information
– Highly dependant on the context and when the uplink is
performed
• When used with a UM73/80 – Replaces existing information
• When used with a UM79 - Some info is not loadable - rules
• When used with a UM83 - Departure information is not loadable

Data Communications Program Federal Aviation 6

September 23, 2101 Administration
DCL Service using Route Clearance
FANS DCL Validation must resolve the ability to load and
display clearance information
– Options ( w/No Printer mandate):
• UM73
– Only works with Boeing Integrated Architecture aircraft
– Loadable and may be viewed in its entirety on Large Format Displays
(777 &787)
• UM80
– Loadable in all Airbus and Boeing product lines
– Viewable on both Federated and Integrated Architectures
– Best when used as the “Initial” DCL – Replaces FMC route in it’s
entirety
» Reduces the risk of previous flight information not being
removed during shut down process
• UM79/83
– On 737 aircraft, loadable parameters should not be used after a
Departure Parameter element – Validation Risk
– Not appropriate due to behavior of loading individual parameters

Data Communications Program Federal Aviation 7

September 23, 2101 Administration
UM 80 FANS DCL Service
FANS Departure Clearance FANS DCL Clearance as seen in FANCS DCL Clearance as seen in
Service Messages Integrated aircraft a Federated Aircraft - Boeing

UM80 CLEARED CLEARED CLEARED ROUTE CLEARANCE

[Routeclearance] ROUTE CLEARANCE
Initial DCL ORIGIN:KMIA
DEPARTURE: 08R
DEST:KLGA
VALLEY1
ARRIVAL:KORRY3.PXT
•Loadable VIA TO
DIRECT PERMIT
AR16 ILM
•Viewable J40 TYI
DIRECT HPW
J191 PXT
•Flexible
UM 169 [FREETEXT] ALT/EXP MAINTAIN 5000 FT MAINTAIN 5000 FT
Across all INFO EXPECT FL350 10 MINS EXPECT FL350 10 MINS
AFTER DEPT AFTER DEPT
Platforms UM169 [FREETEXT] DEPT DEPARTURE FREQUENCY 124.5 DEPARTURE FREQUENCY
FREQ, 124.5
UM 123 SQUAWK [CODE] SQUAWK 2014 SQUAWK 2014
UM169 [FREETEXT] EDCT 1700 EDCT 1700
ADDITIONAL INSTRUCTIONS

Data Communications Program Federal Aviation 8

September 23, 2101 Administration
Validation Requirements – UM80
• Do it Right, then do it Wrong
– Develop DCL Scenarios
• Test the robustness of UM80 to include:
– Multi-Element Messages sequencing
– Route Clearance, Airport and Procedure variables
» Procedure Naming
» Route Information
» Waypoints & Airways
» Additional Route Information – e.g. Holding & RTA
– Viewable across all FANS platforms
– Validate using Certified Avionics in a Engineering Lab
– Validate using a end-to-end air-ground sub network
– Determine follow-on validation requirements to define
FMC capability and route construction rules

Data Communications Program Federal Aviation 9

September 23, 2101 Administration
Validation Timeline
• Scenario Development
– Start Sept 23 with DCL Team
• Minimum of 2 Scenarios with variations
• Boeing Labs
– Engineering Lab visit to test against all Boeing Platforms – Week of 27
September
• Document all Test and Findings
• Airbus Labs
– Engineering/Certification Lab visit – TBD (1 month notice at Airbus
Request)
• Has offered to test DCL scenario’s and document findings – estimate 2-3 weeks
once test material is delivered and test is coordinated
• Summarize Documented results with Pictures and Video’s
• Determine if results meet DCP objectives
• Provide results to the DCP Leadership and SC-214 CSG &
VSG

Data Communications Program Federal Aviation 10

September 23, 2101 Administration
DCL Validation Proposal Summary

• Boeing and Airbus has agreed to provide us the resources

necessary to expedite DCL Validation
• UM80 Route Clearance with additional Concatenated ATC
clearance Elements will provide the same service as SC-214
development in their FANS/ATN DCL Template
• UM80 may be viewed and is loadable across all Airbus and
Boeing platforms
• Validating the use of UM80 will provide the framework to define
FANS Interoperability with planned FAA Air/Ground network
• Validation timeline can meet DCP near term time horizon for
FANS DCL Interoperability definition – weeks vs. months if
properly resourced

Data Communications Program Federal Aviation 11

September 23, 2101 Administration
Questions & Comments

Data Communications Program Federal Aviation 12

September 23, 2101 Administration