A Human Factors Approach to Bridging Systems and Introducing New Technologies

The application of human factors in aviation has grown to cover a wide range of disciplines and methods capable of assessing human-systems integration at many levels. For example, at the individual level, pilot workload may be studied while at the team level, coordinated workload distribution may be the focal point. At the organizational level, the way in which individuals and teams are supported by training and standards, policies and procedures may introduce additional, relevant topics. A consideration of human factors at each level contributes to our understanding of successes and failures in pilot performance, but this system focused on the flight deck alone -- is only one part of the airspace system. In the FAA's NextGen plan to overhaul the National Airspace System (NAS), new capabilities will enhance flightdeck systems (pilots), flight operations centers (dispatchers) and air traffic control systems (controllers and air traffic managers). At a minimum, the current roles and responsibilities of these three systems are likely to change. Since increased automation will be central to many of the enhancements, the role of automation is also likely to change. Using NextGen examples, a human factors approach for bridging complex airspace systems will be the main focus of this presentation. It is still crucial to consider the human factors within each system, but the successful implementation of new technologies in the NAS requires an understanding of the collaborations that occur when these systems intersect. This human factors approach to studying collaborative systems begins with detailed task descriptions within each system to establish a baseline of the current operations. The collaborative content and context are delineated through the review of regulatory and advisory materials, letters of agreement, policies, procedures and documented practices. Field observations and interviews also help to fill out the picture. Key collaborative functions across systems are identified and placed on a phase-of-flight timeline including information requirements, decision authority and use of automation, as well as level of frequency and criticality