1 / 16

Evaluation of the CDTI CS 247B / MS&E 430 (Pamela Hinds) NASA Ames (Richard Mogford)

Evaluation of the CDTI CS 247B / MS&E 430 (Pamela Hinds) NASA Ames (Richard Mogford). Honor Gunday Joe Sacco Luke Swartz Stanford University www.stanford.edu/~lswartz/cs247b. CDTI. Now: can’t see other planes Cockpit Display of Traffic Information situation awareness of other planes’

adamdaniel
Download Presentation

Evaluation of the CDTI CS 247B / MS&E 430 (Pamela Hinds) NASA Ames (Richard Mogford)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Evaluation of the CDTICS 247B / MS&E 430 (Pamela Hinds)NASA Ames (Richard Mogford) Honor Gunday Joe Sacco Luke Swartz Stanford University www.stanford.edu/~lswartz/cs247b

  2. CDTI • Now: can’t see other planes • Cockpit Display of Traffic Information • situation awareness of other planes’ • locations • altitudes • intentions • route changes

  3. Free Flight • Now: all adjustments need approval, handoffs from one controller to another (see handout) • Free flight: during en route, let pilots make their own course changes

  4. Methodology and Process • Interviews • 5 pilots, 4 controllers • Pilots: not in workspace… • Observations • Prototype testing • Oakland TRACON • Design Meetings and Focus Groups

  5. Pilots’ Work (now) • Drawings: PFD and Nav Display • Flight Management System (FMS) • En route • generally quiet • route change requests usually granted

  6. Controllers’ Work (now) • Environment • laid back, fun • love their job • pride • “Having a deal” • Unexpected events

  7. Pilots’ Work (free flight) • Over-water versus over-land • Worried about • time • distractions • attention • safety • General Aviation pilot: didn’t want self-separation responsibility either

  8. Controllers’ Work (free flight) • Want clear responsibilities • “all or nothing” • Concern over efficiency • will this actually help? • free flight might actually make things worse!

  9. Interface Observations • Not the subject of our course, but… • CDTI display itself: liked, seemed easy to use (based on ND) • Bar on bottom of CDTI: perceived as “hard to use” • Feedback on sending flight plans? • Toggle switches (e.g. pulse)?

  10. Process Recommendations • Subjects • “lab rats become very well trained” • Simulation • currently distracting, problems of validity? • Mindset • “demonstration, not an experiment”

  11. Design Principles for Pilots • Fit into physical workspace • Shouldn’t increase workload substantially, or require constant attention • Present pertinent info

  12. Design Principles for Controllers • High attention, short time (active vs. passiveness) • Present visually • “Handoff-able”; deal with unexpected situations, error • Clear roles and responsibilities (distributed, not shared)

  13. How does the CDTI do?

  14. High-Level Recommendations • What is the motivation behind CDTI and free flight? • Pilot skepticism: “how busy are they?” • Controller skepticism: “this will make it slower!” • FAA, controllers, NASA, pilots…and airlines

  15. High-Level Recommendation • CDTI can be (best?) used without free flight • Further ensure safety • Reduce workload on controllers without changing roles • Get rid of FMS • Only free flight over water? • Presentation to pilots

  16. Questions? www.stanford.edu/~lswartz/cs247b

More Related