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 the governing aeronautical flight charts. With the overwhelming upgrades to navigation systems and fully integrated flight management systems (FMS) that are now installed in almost all corporate and commercial aircraft, the need for reliable and consistent airborne navigation databases is more important than ever.
Figure 1. Area navigation (RNAV) receivers
The capabilities of airborne navigation databases depend largely on the way they are implemented by the avionics manufacturers. They can provide data about a large variety of locations, routes, and airspace segments for use by many different types of RNAV equipment. Databases can provide pilots with information regarding airports, air traffic control (ATC) frequencies, runways, and special use airspace. Without airborne navigation databases, RNAV would be extremely limited. In order to understand the capabilities and limitations of airborne navigation databases, pilots must understand the way databases are compiled and revised by the database provider and processed by the avionics manufacturer. Vital to this discussion is understanding of the regulations guiding database maintenance and use.
There are many different types of RNAV systems certified for instrument flight rules (IFR) use in the National Airspace System (NAS). The two most prevalent types are GPS and the multisensory FMS. [Figure 2]
Figure 2. GPS with a flight route on display
A modern GPS unit accurately provides the pilot with the aircraft’s present position; however, it must use an airborne navigation database to determine its direction or distance from another location. The database provides the GPS with position information for navigation fixes so it may perform the required geodetic calculations to determine the appropriate tracks, headings, and distances to be flown. [Figure 3]
Figure 3. FMS display
Modern FMS are capable of a large number of functions including basic en route navigation, complex departure and arrival navigation, fuel planning, and precise vertical navigation. Unlike stand-alone navigation systems, most FMS use several navigation inputs. Typically, they formulate the aircraft’s current position using a combination of conventional distance measuring equipment (DME) signals, inertial navigation systems (INS), GPS receivers, or other RNAV devices. Like stand-alone navigation avionics, they rely heavily on airborne navigation databases to provide the information needed to perform their numerous functions.
We use cookies to ensure our website functions properly, analyze website traffic, and improve your browsing experience. You can accept all cookies, reject non-essential cookies, or customize your preferences.
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
