Airborne Navigation Database

Understanding the capabilities and limitations of the navigation systems installed in an aircraft is one of the pilot’s biggest concerns for IFR flight. Considering the vast number of RNAV systems and pilot interfaces available today, it is critical that pilots and flight crews be familiar with the manufacturer’s operating manual for each RNAV system they […]

Compiling and maintaining a worldwide airborne navigation database is a large and complex job. Within the United States, the FAA sources give the database providers information, in many different formats, which must be analyzed, edited, and processed before it can be coded into the database. In some cases, data from outside the United States must

The path and terminator concept is a means to permit coding of terminal area procedures, SIDs, STARs, and approach procedures. Simply put, a textual description of a route or a terminal procedure is translated into a format that is useable in RNAV systems. One of the most important concepts for pilots to learn regarding the limitations

Beginning in the 1970s, the requirement for airborne navigation databases became more critical. In 1973, National Airlines installed the Collins ANS-70 and AINS70 RNAV systems in their DC-10 fleet, which marked the first commercial use of avionics that required navigation databases. A short time later, Delta Air Lines implemented the use of an ARMA Corporation RNAV

Area Navigation (RNAV) systems, aeronautical applications, and functions that depend on databases are widespread. [Figure 1] Since the 1970s, installed flight systems have relied on airborne navigation databases to support their intended functions, such as navigation data used to facilitate the presentation of flight information to the flight crew and understanding and better visualization of