Area Navigation Systems (RNAV) — Page 270, Lesson 263

Let's start with the big picture. We're talking about Area Navigation, or RNAV. In conventional navigation, you fly directly to or from a ground-based radio beacon, like a VOR or a DME station. RNAV changes that completely. It lets you fly along any desired path between two points that aren't necessarily defined by a ground station at all. Those points are called waypoints, and the system computes your position and steers you along that path. Now, for a system to be a true 4D RNAV system, it has to meet a very specific set of requirements. And I want to walk you through those one by one, because each one is a distinct capability the crew and the system depend on. First, the system must display your present position. It can show this in one of two ways: either as latitude and longitude coordinates, or as a distance and bearing to a selected waypoint. That's the fundamental output — you always know where you are. Second, you need to be able to select or enter the required flight plan through the control and display unit, which we call the CDU. That's your primary interface with the system. Third, the system must let you review and modify navigation data for any part of a flight plan at any stage of flight. And it must store enough data to carry out the active flight plan. So you're not just entering it once — you can go back and change things mid-flight. Fourth, you must be able to review, assemble, modify, or verify a flight plan in flight, and here's the key part — without affecting the guidance output. That means you can work on a plan while the aircraft keeps flying the current one. The system is doing two things at once. Fifth, and this is a safety-critical point: a modified flight plan can only be executed after positive action by the flight crew. The system will not just switch over on its own. You have to deliberately confirm and activate it. Sixth, where provided, the system must let you assemble and verify an alternative flight plan without affecting the active flight plan. So you can build a backup plan in the background while the active one continues. Seventh, we get into how you actually build a flight plan. You can assemble it by identifier — that's calling up a named route. Or you can select individual waypoints from the database. Or you can create waypoints from the database. Or you can create waypoints defined by latitude and longitude, or by bearing and distance parameters, or by other parameters. So there are multiple ways to define where you want to go. Eighth, you must be able to assemble flight plans by joining routes or route segments. So you can stitch together pieces of published routes to make a complete plan. Ninth, the system must allow verification or adjustment of the displayed position. You need to be able to check that what the system thinks is your position actually matches reality, and correct it if needed. Tenth, this one's about the flight path itself. The system must provide automatic sequencing through waypoints with turn anticipation. That means as you approach a waypoint, the system starts the turn before you actually reach it, so you fly a smooth path rather than overshooting. But manual sequencing must also be provided, to allow you to fly over a waypoint and then return to it if you need to. Eleventh, the system must display cross-track error on the CDU. That's the distance you are left or right of your intended track. You need to see that number. Twelfth, it must provide time to waypoints on the CDU. So you know not just where you are, but when you'll get there. Thirteenth, you must be able to execute a direct clearance to any waypoint. If ATC says "direct to XYZ," you can do it. Fourteenth, the system must be able to fly parallel tracks at a selected offset distance. And here's a critical safety point — the offset mode must be clearly indicated. If you're flying a parallel track offset from the published route, everyone on the flight deck has to know that, because it changes your clearance. Fifteenth, the system must be able to purge previous radio updates. That means clearing out old navigation data so it doesn't contaminate your current position solution. Sixteenth, it must carry out RNAV holding procedures, when those are defined. So holding patterns in an RNAV environment are handled by the system. Seventeenth, the system must make available to the flight crew estimates of positional uncertainty. This can be expressed either as a quality factor, or by reference to sensor differences from the computed position. In other words, you need to know how confident the system is in where it thinks you are. Eighteenth, the system must conform to the WGS-84 geodetic reference system. That's the worldwide standard for coordinates — the earth model everything is based on. If the system didn't use WGS-84, your position could be off by hundreds of meters just from the earth model mismatch. And finally, nineteenth, the system must indicate navigation equipment failure. If something goes wrong, you have to know about it. Now, I want to pause on one thing that ties several of these together — the CDU. That's your control and display unit. It's the device you use to enter the flight plan, review it, modify it, and see your cross-track error and time to waypoint. It's the crew interface to the whole RNAV system. And the 4D part — that's the key. Three dimensions are latitude, longitude, and altitude. The fourth dimension is time. That's why the system must give you time to waypoints. A 4D RNAV system manages your position in space and your timing along the route. So when you look at this list, think of it as a contract. Every one of these capabilities is required for the system to be certified as a 4D RNAV system. If any one is missing, you don't have full 4D RNAV capability. And as a professional pilot, you need to know what your system can and cannot do — because that determines how you fly it and what you can accept from ATC.