Analysis of Safety Reports Involving Area Navigation and Required Navigation Performance Procedures Abhizna Butchibabu1, Alan Midkiff1, Andrew Kendra2, R. John Hansman1, Divya C. Chandra2 1Massachusetts Institute of Technology 2United States Department of Transportation 77 Massachusetts Avenue, Cambridge, MA USA Volpe National Transportation Systems Center {abhiznab, rjhans}@mit.edu,
[email protected] 55 Broadway, Cambridge, MA 02142, USA {Andrew.Kendra, Divya.Chandra}@dot.gov ABSTRACT However, there are human factors concerns because RNAV In order to achieve potential operational and safety benefits and RNP procedures can result in paths that are complex to fly enabled by Area Navigation (RNAV) and Required and typically require the assistance of a Flight Management Navigation Performance (RNP) procedures it is important to Computer (FMC) to negotiate precise speed, altitude, and monitor emerging issues in their initial implementation. lateral path constraints. A list of related human factors issues Reports from the Aviation Safety Reporting System (ASRS) was collected and summarized by Barhydt and Adams in a were reviewed to identify operational issues related to RNAV comprehensive research report (2006a). Separately, Barhydt and RNP procedures. This review is part of a broader effort to and Adams (2006b) reported on an exploratory study using the understand emerging human factors issues for performance Aviation Safety Reporting System (ASRS) database to based navigation. A total of 285 relevant reports filed between identify 124 reports filed between 2000 and mid-2005 related January 2004 and April 2009 were identified and analyzed. to RNAV and RNP departure and arrival procedures at seven For departure procedures, the majority of reports mention specific airports.