Data Comm Flight Deck Human­in-the-Loop Simulation

NASA Ames Research Center

Sandy Lozito

Lynne Martin

John Kaneshige

Shivanjli Sharma

Vicki Dulchinos

•

https://ntrs.nasa.gov/search.jsp?R=20120016029 2020-05-28T10:05:58+00:00Z

Previous Data Comm Tasks:

NASA & Volpe

Compile flight deck and air-ground Data Comm

human factors issues

Indicate methodologies that might be most

appropriate to address issue

Provide a prioritization of those issues

•

Get feedback regarding prioritization of those issues

from the FAA's Data Comm Office

Consider Hill to address flight deck human factors . Issues

Previous Research/Operational Concerns • Terminal area use of Data Comm may be required for NextGen clearance types

Terminal area creates flight crew challenges when using Data Comm

Timing concerns for busy phase of flight

Heads-down issues

Message length has been an issue for flight crews in voice and data comm (Lozito et. ai, 2004)

Autoload of data comm messages has indicated some loss of situation awareness (Logsdon et aI., 1996)

Resea rch Questions

What are the acknowledgment times and transaction times for the terminal area?

•

What is the impact on message timing when comparing two

small messages v. a longer concatenated message?

What is the impact on crew errors (spoken errors and data entry errors) when comparing two small messages v. a longer concatenated message?

What is the impact on the autoloading of message components when comparing two small messages v. a longer concatenated message?

Methods

Boeing 747-400 Level D Certified Simulator

SFO Terminal Airspace

Current message set

Participants will be current line pilots (CAs and F/Os)

Controller as confederate

Pseudopilot for background chatter

Data Comm/Voice mix

Short v. Long messages

Subset of messages will be autoloadable (mostly route messages)

•

Example Scenario: Modesto 3 Arrival • o ~Ol 83.:1 ~ ~ OJ 0 ~Ol NVr v ~ 'l-MS

CLOVIS TRANSITION ICza.MOD3): From over cza VORTAC via cza R-305 and MOD R-092 to MOD VOR/DME. Thence .... COALDALE TRANSITION (OAl.MOD31: From over OAL VORTAC via OAL R-246 and MOD R-064 to MOD VOR/DME. Thence .... MINA TRANSITION (MVA.MOD3): From over MVA VORTAC via MVA R-204, OAL R-246 and MOD R-064 to MOD VOR/DME. Thence .... MUSTANG TRANSITION IFMG.MOD31: From over FMG VORTAC via FMG R-182 and MOD R-064 to MOD VOR/DME. Thence ....

.... From over MOD VOR/DME via MOD R-245 to CEDES INT, then via OSI R-056 to OOMEN INT, then via OSI R-056 to MEHTA INT. Expect vectors to the final approach course. LOST COMMUNICATIONS: Intercept and proceed via SFO RWY 28R localizer to DUMBAINT.

MODESTO l14.6 MOD :::=;-

OAKlAND CENTER O~ 134.37 281.5

NORCAl APP CON 0 128.325 254.3 m

ATIS en '--____ -.,. 113.7 118.85 -10

MUSTANG 1..lL.2. FMG :::::

Chan 126 N39°31.88' -WI19°39.36'

l-9,H-3

MINA 115.1 MVA ::.:-­

Chan 98 N38°33.92'-WI18°01.97'

l-9,H-3

-I :::I: :;::c m m » :;::c :;::c

~ r-

N ~ ~ Z z~

~~ ~~ z~ ~z ~ ~ CLOVIS ~ z~ Z 0 112.9 CZQ ::=::.. 0 () , Chan 76 ' n Ui n N360S3.06'-W119048.91' n Ui () » WOODSIDE » n

~ ~~~ ~O 00 113.90SI :::-- 0_ Z~ 0,0n86 "'z ~ L _____ -===========~ ______________ ~~~~~~~_~~~~~~~~-~~~z--t ?> >~

SW-2, 14 JAN 2010 to 11 FEB 2010

Study Metrics Crew acknowledgment time

Total transaction time

Errors

Acceptance of erroneous clearance

Additional crew errors

ATC queries

Voice

Data Comm (use of downlink or message log)

Workload

NASA TLX

WAK

Situation Awareness

•