The Human Element in Performance Based Navigation: Air Traffic Controller Acceptance of Established on Required Navigation Performance Procedures

  • Lauren ThomasEmail author
  • Alicia Serrato
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 964)


This paper provides a summary of results from a research project commissioned by the Federal Aviation Administration NextGen Human Factors Division to explore the factors associated with air traffic controller acceptance of a Performance Based Navigation (PBN) procedure, “Established on Required Navigation Performance” (EoR). Interviews were arranged at two terminal air traffic control facilities that were “early adopters” of EoR approaches. A total of 38 interviews were conducted with facility personnel, including 24 Certified Professional Controllers. Questions focused on how air traffic controllers integrated the new procedures into their controlling style and practice, and the organizational and operational factors that either supported or hindered controller utilization of the new procedures. A framework of the results is presented, providing insights into how to support air traffic controllers in moving towards trajectory-based operations. The results could be used to increase the probability that the potential benefits of PBN procedures can be realized.


Performance Based Navigation Trajectory based operations User acceptance Procedures Established on Required Navigation Performance Air traffic control 



The authors would like to record their appreciation to Bill Kaliardos, Federal Aviation Administration NextGen Human Factors Division, and to Mitchell Bernstein, Federal Aviation Administration NextGen Technology Development and Prototyping Division (Navigation Branch) for their support and guidance throughout this research project.


  1. 1.
    Federal Aviation Administration: Performance Based Navigation Strategy. U.S. Department of Transportation, Washington D.C. (2016)Google Scholar
  2. 2.
    Mayer, R.: Established on required navigation performance (EoR) concept validation. Technical report, MITRE (2016)Google Scholar
  3. 3.
    Pollock, M., Hudak, T., Spelman, J.: Methodology for established on required navigation performance (RNP) concept validation for a dependent parallel approach operation. Technical report, MITRE (2015)Google Scholar
  4. 4.
    Chandra, D.C., Markunas, R.: Line pilot perspectives on complexity of terminal instrument flight procedures. In: IEEE/AIAA 35th Digital Avionics Systems Conference, pp 1–10. IIEEE Press, Sacramento (2016)Google Scholar
  5. 5.
    Chandra, D.C., Markunas, R.: Line pilot perspectives on complexity of terminal instrument flight procedures. Technical report, Volpe National Transportation Systems Center (2017)Google Scholar
  6. 6.
    Federal Aviation Administration: Performance based navigation implementation process. Air traffic organization policy JO 7100.41. Effective April 29, 2016. U.S. Department of Transportation. Washington, D.C. (2016)Google Scholar
  7. 7.
    Federal Aviation Administration: Unites States standard for performance based navigation (PBN) instrument procedure design. JO8260.58A. Effective 03/14/2016. U.S. Department of Transportation. Washington D.C. (2016)Google Scholar
  8. 8.
    Garcia, R., Goodlin, T.: Converging runway display aid CRDA denver TRACON RNP-AR sequencing with straight-in approaches. Technical report, Denver Terminal Radar Approach Control (2016)Google Scholar
  9. 9.
    Thomas, L.J., Serrato, A., Newton, K.: Established on required navigation performance (EoR) (RNP) concept validation and implementation plans: human factors gap analysis. Technical report, Evans Incorporated (2018)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  1. 1.Evans IncorporatedFalls ChurchUSA

Personalised recommendations