The problems of integrating aircraft using area navigation into the terminal A.T.C. environment are discussed. It is concluded that area navigation systems currently available are incompatible with current terminal A.T.C. approach sequencing and that integration is only possible in the context of both computer assistance to the approach controller and data link between the A.T.C. computer and the aircraft navigation system. The benefits of Terminal Area Navigation are briefly considered and it is suggested that the deployment of vertical navigation in a procedural role might be the better first step. The paper was presented at the 19th Technical Conference of I.A.T.A., Dublin, 1972. Crown copyright.Currently available area navigation (R NAV) systems range from simple station-oriented single waypoint systems, allowing flight on paths which do not coincide with VOR radials, to complex systems in principle enabling flight from origin to destination along a pre-programmed route, including flight on a standard terminal arrival route (from holding point or feeder-fix to the approach gate). As far as Terminal Area Navigation is concerned it appears that the main objective to the R Nav system designers has been to provide a system which enables automatic navigation along the standard terminal arrival routes, as depicted in the Jeppeson Charts, and to display to the pilot his progress along the route. It appears that designers of the more sophisticated systems have tacitly assumed that when an R Nav aircraft enters the terminal area A.T.C. will be able and willing to allocate it such a route.
Design and development of automatic navigation system using open source Arduino and Raspberry pie
