April 13, 2022

Changing the Font Style and Colour in CDU

April 13, 2022/ Flaps 2 Approach

OEM 737-800 font style (courtesy Mick.C ©). An interesting point about this picture is the condition of the flightdeck which is far from the pristine appearance of many simulators

This article will discuss how to change the font style displayed in the Control Display Unit (CDU). Although the ProSim737 avionics suite comes with a default font style, many enthusiasts wish to change the font, colour and size to more closely mimic the font used in the OEM CDU, or so the information can be more easily read (not all of us are 20 years old…)

The font styles displayed in a simulator are linked to the fonts that have been installed in the computer’s operating system. Any font style can be displayed in the CDU – as long as the font style has been included in the style library used by Windows.

important Parameters

There are two parameters which depict how a font style is displayed: the actual font style itself and the CDU config file.

The location of the font style library is C:\\Windows\fonts (Windows 10/11).

Any of the fonts located in this library can be used to display parameters in the CDU. Likewise, if you have a preferred font that is not in the library then it can easily be added to the library (copy/paste).

The location of the config file is the CDU folder of the ProSim737 avionics suite.

To edit the config file, you must right click the file and select edit, otherwise the file will open in read only (HTML text). Once the config file is opened, it will become apparent that all the settings related to the CDU: screen location, screen size, font style, display parameters, etc are recorded in the file.

With a little experience, it is often easier to make setup changes to the CDU by opening and editing the config file, rather than opening the options box from the CDU display window. If editing the config file directly, always make a back-up copy of the file prior to making and saving any changes.

ProSim737 options box. The options box is opened by right clicking the CDU screen and selecting *config*

Selecting a Font Style and Colour

How to initially configure the CDU (line setting, screen position, frame settings, etc) is addressed in the ProSim737 manual (2012 edition) or in the wikipedia manual.

To alter the font style, open the options box by right clicking the CDU screen and selecting config; the options box is linked to the Windows style library discussed earlier. To change a font style, scroll through the styles available. Once a style has been selected, you can change the font size by either changing the size variable associated with the font, or by selecting +- in the ProSim options box.

Another way to change the font style is to open the config file and edit the line entry that relates to the small and large font sizes. If this method is used, ensure you transcribe the font style and size accurately to avoid errors.

To alter the font’s colour, the config file must be opened. Once opened search for the following two lines:

<largeFontColor>White</largeFontColor>

Type the required colour replacing the bolded section above.

ProSim737 CDU *config* file. The lines that need to be altered to change the style and colour are in red. With experience, other attributes can also be altered, however, always make a copy of the file prior to changing anything

OEM

OEM is an acronym for original equipment manufacturer. It refers to the hardware and software used in the real aircraft. In the Boeing aircraft the font colours displayed in the CDU can be readily changed.

The font style is more or less standardised across the Boeing fleet, however, variations to the font style can be found, and in part depend upon the software option selected by the airline when the aircraft was initially purchased, the U version in use, and the manufacturer of the CDU (Smiths, Collins and Honeywell).

Colour Conventions

The FMC software supports 5 colour conventions: green, cyan, magenta, white and amber. Bill Bulfer examines the text displayed for each colours in the FMC Guide. The information provided is from U10.2.

Final Call

Changing the font style, size and colour can be easily accomplished by editing the config file either directly from the CDU display or by opening the config file itself. If a specific style is needed, then this can be added to the Windows style library.

February 03, 2021

Flow Sequence To Enter Information To Flight Management Computer (FMC)

February 03, 2021/ Flaps 2 Approach

Specific information must be entered into the Control Display Unit (CDU) if the Flight Management Computer (FMC) and Flight Management System (FMS) is to function correctly. To ensure that all the appropriate data is entered, a flow sequence is usually used by a flight crew to enter data into the CDU.

Each aircraft is normally equipped with two Control Display Units; one on the Captain-side and one the First Officer-side. Each CDU can be used either in tandem or independently of each other.

In this article, I will discuss the preferred flow sequence that should be used to enter information into the CDU pre-flight. It should be noted that, like many aspects of aviation there are usually several ways to achieve a similar if not identical result. Often airline policy will dictate the sequence that the CDU is configured, and by which pilot. Therefore, the below information should be treated as a guideline rather than an inflexible set of rules.

The information used comes in part from the aircraft’s flight plan and load sheet.

The content of this article has been reviewed by a Boeing 737 Captain for accuracy.

FMC Software

The Flight Management System (FMS) is controlled by software and the software version used is often dependent on the age of the aircraft; not all software is identical. The information in this article refers to Software Version U10.8A. U10.8A is the version used by ProSim737 (other simulation avionics suites may differ). An earlier article discusses software variants.

Which Pilot Does What And When Is It Done

It is not uncommon for the pilot’s to share the task of setting up the CDU. Usually the pilot flying (PF) will enter parameters that are essential to flight, while the pilot not flying/monitoring (PM) will enter information pursuant to the route.

However, the hierarchy in a flight deck is that the Captain is the Pilot In Command (PIC), and it is assumed that the First Officer will complete most of the mundane, albeit important, navigation tasks leaving the Captain to deal with other matters.

CDU Verification and Cross Checking Procedure

The CDU is nothing more than a ‘glorified keypad’ and the maxim of ‘rubbish in rubbish out’ applies. Until execution (pressing the illuminated execute button on the keypad), none of the information entered into the CDU will be reflected in the FMC and FMS. Therefore, it is important that prior to execution, each pilot review and confirms the other’s inputs. Cross checking and verification minimises the chance that incorrect information has been entered.

At a minimum, a flight crew should compare the filed flight plan with the airways and waypoints entered on the ROUTE pages. The flight plan total distance and estimated fuel remaining at the destination should also be reviewed on the progress page of the CDU. If a discrepancy is noted, the LEGS page must be updated to ensure it is identical to the airways and waypoints in the filed flight plan. A cross check using the Navigation Display in PLAN mode and the CDU in STEP function (LEGS page) will aid is verification of the flight plan and in determining if there are any discontinuities that need to closed.

Taxi and Flight

Before taxi, the Captain or First Officer may make CDU entries. However, when possible, CDU entries should be made prior to taxi or when stopped. If CDU entries must be made during taxi, the pilot monitoring makes the entries and the pilot flying concentrates on steering the aircraft.

In flight, the pilot monitoring usually makes the CDU entries, however, the pilot flying may make simple CDU entries, but only when the workload allows. Essentially, the pilot flying concentrates on flying the aircraft and if they wish to enter data to the CDU, then the responsibly of flying the aircraft should be transferred to the First Officer.

The pilot flying is responsible for setting up the approach page in the CDU. To do this, the pilot flying will transfer command of the aircraft to the pilot not flying, and then make any amendments to the approach in the CDU. Upon completion, the command of the aircraft will be transferred and the pilot not flying will check the information.

Which Page in the CDU is Opened During Takeoff

The pilot flying usually will have the takeoff reference page displayed to enable the crew to have immediate access to V-speeds. This is to counter against the rare event that the V-speeds are inadvertently removed from the airspeed display on the Primary Flight Display (PFD) due to a display failure. Alternatively, the pilot flying may also elect (following the takeoff briefing in the Before Takeoff Procedure) to display the CLB page for takeoff.

The pilot monitoring normally displays the LEGS page during takeoff and departure to allow timely route modification if necessary.

CDU Sequence Flow

There are numerous ways to flow from one CDU function to another. The two commonly used methods are to use the Alpha Keys or the Line Select Keys (i.e. LSKL6). For example, LSKL6 refers to line select key left 6 or the sixth lower button on the left hand side.

As stated, the pilot flying will enter any information relevant to the takeoff of the aircraft, while the pilot not flying will enter information pertaining to the route of the aircraft (i.e. route, legs).

Bold CAPITALletters indicate that the command is an ALPHA menu key.

PILOT NOT FLYING (PM)

INIT REF / INDEX (LSKL6).
POS (LSL2) – Enter airport identifier into Ref Airport.
RTE or ROUTE (LSKR6) - Enter airport identifier (origin and destination), flight number (Flt No) and runway.
DEP ARR – Enter departure information (DEP LSKL1) - SID and runway.
LEGS– Enter airways, waypoints and navaids as required to a build a navigation route.
DEP ARR – Enter arrival information (ARR LSKL2) - STAR, approach, transition and runway.
On the EFIS, select PLAN and using the STEP function (LEGS Page) or PREV-NEXTPage, cycle through the waypoints checking the route on the Navigation Display. Check the route and close any route discontinuities. Return EFIS to MAP.
ACTIVATE (LSKL6) / EXECor RTE / ACTIVATE (LSKR6) / EXEC.

PILOT FLYING (PF)

INIT REF – Enter Zero Fuel Weight (ZFW), Fuel Reserves, Cost Index, Cruise Altitude (Crz Alt), Cruise Wind (Crz Wind), ISA Deviation (ISA Dev), Outside Air Temperature (T/C OAT) and Transition Altitude (Trans Alt).
N1 LIMIT (or LSKR6) – Enter Derates as desired.
LEGS / RTE DATA (LSKR6) – Enter wind (this determines fuel quantity on progress page). Note #1.
INIT REF / displays TAKEOFF REF page – Enter Flaps setting for departure and Centre of Gravity (Flaps and Trim). Go to page 2/2 and input data to various fields as and if required.
EXEC– Press illuminated execute key (this triggers the V-Speeds to be displayed on the TAKEOFF REF page).
To select V-Speeds, press Line Select keys beside each V-Speed to activate (LSR1, 2 & 3). Note #2.

Notes:

NOTE #1: Wind direction and speed (point 3) can be addedprior to or after the EXEC button has been selected. The flow sequence will alter dependent upon when this information is added. If the winds are not added, the flow will alter and TAKEOFF (LSKR6) will be selected instead of INIT REF.
NOTE #2: If V-Speeds on the Takeoff page are not displayed, it is because either the EXEC key has been pressed prior to the Takeoff Page being opened and data entered. If this occurs, cycle the QRH (LSKR6) on and off. The V-Speeds will then be displayed. Another reason that the V-Speeds may not be displayed is failure to input other essential pre-flight information.

There is often confusion to what the QRH designation means. When QRH is not selected (turned off) the V-Speeds will be automatically promulgated. If QRH is selected (turned on) the V-Speeds will be shown in green beside the appropriate line. This enables the flight crew to change the V-Speeds prior to executing them (note that ProSim-AR enables this to be altered in the IOS/Settings).

Additional Information

I usually do not link to outside resources, however, this U-Tube video from Mentour Pilot demonstrates the procedure quite well. Scroll to 0:31 seconds to begin video.

For those interested in reading more about how the CDU, FMC and FMS and how they interrelate concerning information input, Randy Walter from Smiths Industries has put together a very good article called Flight Management Systems.

Final Call

The CDU is an essential item that must be configured correctly if the aircraft’s internal navigation database is to be used. Likewise, LNAV or VNAV will only operate if the information has been entered into the CDU correctly.

The sequence you enter the information into the CDU is important, and although some latitude to the flow is accepted, a correct sequence flow will ensure all essential variables are inputted. Finally, cross verification of data, or any change to the data, ensures correct and accurate information is being entered.

Acronyms and Glossary

ALPHA Menu Key - Refers to the menu function keys.
CDU - Control Display Unit (the keypad).
FMC - Flight Management Computer.
FMS - Flight Management System.
LSK - Line Select Key. Used to enter lower level pages.
QRH - Quick Reference Handbook.

Download Flow Sequence

March 03, 2018

Wind Correction (WIND CORR) Function - CDU

March 03, 2018/ Flaps 2 Approach

OEM 737 CDU showing WIND CORR display in Approach Ref page

Wind Correction (WIND CORR)

The approach page in the CDU has a field named WIND CORR (Wind Correction Field or WCF).

WIND CORR can be used by a flight crew to alter the Vref + speed (speed additive) that is used by the autothrottle during the final approach. This is to take into account wind gusts and headwind that is greater than 5 knots.

Changing the Wind Correction to match increased headwind and gusts increases the safety margin that the autothrottle operates, and ensures that the autothrottle command a speed is not at Vref.

WIND CORR Explained

The algorithm of the autothottle includes a component that includes a speed additive. The speed additive is 1.23 times greater than the stall speed of the aircraft (at whatever flap setting). When the autothrottle is engaged, the speed additive is automatically added to Vref. This provides a safety buffer to ensure that the autothrottle does not command a speed equal to or lower than Vref. This added speed is usually 'bled off' during the flare ensuring landing is at Vref.

Although the autothrottle algorithm is a sophisticated piece of software, there is a time lag between when the sensors register a change in airspeed to when the physcial engines increase or decrease their spool (power). By having a speed additive (based on headwind and gust component) the speed of the aircraft (as commanded by the autothrottle) should not fall below Vref.

A Vref+ speed higher than +5 can be inputted when gusty or headwind conditions are above what are considered normal. By increasing the additive speed (+xx), the speed commanded by the autothrottle will not degrade to a speed lower than that inputted.

The default display is +5 knots. Changing this figure will alter how the algorithm calculates the command speed for the autothrottle; any change will be reflected in the LEGS page, however not in the APPROACH REF page.

The data entered into the Wind Correction field will only be used by the Flight Management System (FMS) when the aircraft is following an RNAV approach, or when using VNAV to fly an approach that has been manually constructed in the CDU. This is because these approach modes use the data from the FMS to fly the approach (as opposed to an ILS or other mode that doesn't use the FMS data).

If hand flying the aircraft, or executing another approach type, Wind Correction is advisory (you will need to add the speed additive (Vref+ xx knots) by mental mathematics).

Important Points:

Wind Correction is automatically added to Vref when flying an RNAV approach, or when using VNAV to fly an approach that has been manually constructed in the CDU.
Wind Correction is advisory for all other approach types or when manually flying an approach; +xx knots must be added to Vref by mental mathematics.

How To Use WIND CORR

The WIND CORR feature is straightforward to use.

Virtual CDU (ProSim737) showing the difference in landing speed with a Vref between a +5 and +13 Knot (Wind Correction) change. Vref altered from 152 knots to 160 knots

Navigate to the approach page in the CDU (press INIT REF key to open the Approach Reference page). Then double press the key adjacent to the required flaps for approach (for example, flaps 30). Double selecting the key causes the flap/speed setting to be automatically populated to the FLAP/SPD line.

Type the desired additive into the scratch pad of the CDU and up-select to the WIND CORR line. The revised speed will change the original Vref speed and take the headwind component into account. If you navigate to the LEGS page in the CDU, you will observe the change.

If the headwind is greater than 5 knots, then WIND CORR can be used to increase the additive from the default +5 knots to anything up to but not exceeding 20 knots.

It’s important to understand that the figure generated in the CDU is the Vref speed. This is the speed that the aircraft should be at when crossing the runway threshold or at a altitude of approximately 50 feet.

To this speed you must add the appropriate wind correction - either by mental mathematics or by using WIND CORR (if flying an FMS generated approach).

Boeing state that the +XX knots should be bled off during the flare procedure ensuring that touchdown speed is at Vref, however this rarely occurs in real life.

Recall from above, that any change using the Wind Correction field will have no bearing on calculations, unless the aircraft is being flown in RNAV / VNAV, or the approach has been manually constructed in the CDU.

For a full review on how to calculate wind speed, refer to this article: Crosswind landing Techniques - Calculations. A prompt sheet is displayed for quick reference.

Important Variables - Aircraft Weight and Fuel Burn

To obtain the most accurate Vref for landing, the weight of the aircraft must be known minus the fuel that has been consumed during the flight.

Fortunately, the Flight Management System updates this information in real-time and provides access to the information in the CDU. It's important that if an approach is lengthy (time consuming) and/or involves holds, the Vref data displayed on the CDU will not be up-to-date (assuming you calculated this at time of descent); the FLAPS/Vref display will show a different speed to that displayed in the FLAP/SPD display. To update this data, double press the key adjacent to the flaps/speed required and the information will update to the new speed.

How To Manually Calculate Fuel Burn

If wishing to manually calculate the final approach speed well before the approach commences, then it's necessary to manually calculate the fuel burn of the aircraft. Open the PROGRESS PAGE on the CDU and take note of the arrival fuel. Subtract this value from how much fuel you have in the tanks - this is the fuel burn (assuming all variables are constant).

Interestingly, the difference that fuel burn and aircraft weight can play in the final Vref speed can be substantial (assuming all variables, except fuel, are equal). To demonstrate:

Aircraft weight at 74.5 tonnes with fuel tanks 100% full – flaps/Vref 30/158.
Aircraft weight at 60.0 tonnes with fuel tanks 25% full – flaps/Vref 30/142.

Important Points:

During the approach, V speeds are important to maintain. A commanded speed that is below optimal can be dangerous, especially if the crew needs to conduct a go-around, or if winds suddenly increase or decrease. An increase or decrease in wind may cause pitch coupling.
If executing an RNAV Approach or using VNAV, it's important to update the WIND CORR field to the correct headwind speed based on wind conditions. This is because an RNAV approach and VNAV use the data from the Flight Management System (to which Wind Correction is added).
If an approach is lengthy (for example, during a STAR or when requested to hold), the Vref speed will need to be updated to take into account the fuel that has been used by the aircraft during the holding time.
Changing the WIND CORR speed in the CDU, does not alter the Vref speed displayed on the Primary Flight Display (PFD). Nor is the APPROACH REF page on the CDU updated. The change is only reflected in the LEGS page.
Boeing state that the speed additive should be 'bled off' during the flare so that the actual landing speed is Vref.

Autoland

Autolands are rarely done in the Boeing 737, however, if executing an autoland, the WIND CORR field is left as +5 knots (default). The autoland and autothrottle logic will command the correct approach and landing speed.

Simulated in Avionics Suite

WIND CORR may or may not be functional in the avionics software you use. Wind Correction is functional in the ProSim737 avionics suite.

Additonal Information

A very good video that discusses this in detail can be viewed at FlightDeck2Sim.

Acronyms

CDU – Control Display Unit
FMC – Flight Management Computer
FMS – Flight Management System (comprising the FMC and CDU)
Vref - The final approach speed is based on the reference landing speed
Vapp – Vapp is your approach speed, and is adjusted for any wind component you might have. You drop from Vapp to Vref usually by just going idle at a certain point in the flare

Updated 21 March 2022 (increased clarity)

August 04, 2017

Conversion of OEM CDU - Part Two

August 04, 2017/ Flaps 2 Approach

In this second article, I will explain how the OEM Control Device Unit (CDU) was converted to enable a SimStack Foundation Board to be installed inside the unit and connected to ProSim737.

SimStacks are manufactured by Simulator Solutions, which is a Sydney based company in Australia and their foundation boards can be used with ProSim737 and ProSim320 avionics suites.

This is but one method to convert an OEM item to be used with flight simulator.

This article will mainly address the mechanical conversion of the CDU. A future article, after flight testing, will provide a review of SimStacks interface cards.

Conversion of OEM CDU Part 1.
Various photographs of the CDU and conversion process can be viewed in the image gallery.

Conversion

Many of the OEM parts used in the simulator have been converted using Phidget cards, and to a lesser extent Leo Bodnar and PoKeys interface cards. Phidgets provide a stable platform, despite the disadvantage that they, at time of writing, can only connect via USB to the server computer, and don’t enable every OEM function to be used in ProSim-AR. The primary advantage of using Phidgets is that they have been used in a wide variety of applications, are inherently stable, and their configuration is well documented.

I decided that, rather than use Phidgets, a different system would be trailed to interface the CDU with ProSim737.

he SimStack Foundation Board mounted on an angular bracket inside the CDU. Fortunately there is ample room to mount the board inside the CDU

SimStacks by Simulator Solutions

The conversion of the CDU was done in collaboration with Sydney-based company Simulator Solutions Pty Ltd. Simulator Solutions use their propriety interface boards called SimStacks to convert OEM parts for use in commercial-grade simulators.

SimStacks is a modular, stackable, and scalable hardware interface that is designed to integrate OEM parts into your simulator with little or no modification. One of the many advantages in using a SimStack board is that the interface can connect with either the server or client computer via Ethernet (as opposed to Phidgets).

To date, Simulator Solution’s experience has been predominately with the conversion of B747 parts and Rodney and John (owners) were excited to have the opportunity to evaluate their software on the 737 platform using ProSim737.

Converting the CDU - Choose Your Poison

There are two main camps when discussing how to convert an OEM part. The first is to use as much of the original wiring and parts as possible. The second is to completely ‘gut’ the part and convert it cleanly using an interface that connects seamlessly with the avionics software in use (ProSim-AR). A third option, although expensive and in many respects ‘experimental’, is to use ARINC 429.

ARINC 429 is a protocol used in real aircraft to enable panels etc to be connected with the aircraft’s systems, and although it can be used in a simulated environment, it’s not without its shortfalls, in particular, the use of AC power (in contrast to DC power).

To use SimStacks the internal components of the CDU had to be removed, with the exception of the internal shelf divider and keypad. In hindsight, the pin-outs of the Canon plugs could have been used, but in doing so a female Canon plug would have been required, and for the use of a couple of pins, the price of a Canon female plug was expensive.

Keypad and Screen

The keypad and screen are the two most important parts of the CDU.

The keypad forms part of the lightplate. The backlighting for the keypad is powered by 21 5 Volt incandescent bulbs, strategically located to ensure even backlighting of the keys.

table 1: provides an overview of bulb location, part number and quantity

Like anything, bulbs have a limited left and, although OEM bulbs are renown for their longevity, there is always a chance that some bulbs are broken. In this case, there were 3 bulbs that needed replacement.

Disassembling and removing the keypad from the main body of the CDU is straightforward; several small Philips head screws hold the keypad in place. Once the keypad has been removed, any ‘blown’ bulbs can be replaced.

The most important area is the keypad is what is called the terminus (bus). Several wires from the keypad travel to the bus and then to the various (now removed) parts in the CDU. The Simstack Foundation Board is wired to the bus, therefore, care must be taken to not damage these wires between the bus and the keypad.

I found that the wires were quite short and needed to be lengthened; this can be done by splicing longer wire to the existing wire. Although it's possible to replace the wire to the keypad, this would entail re soldering the wires to the various keypad points - a process that requires very exact soldering.

CRT and LCD Screen

The Classic CDU from airframes up to the Boeing 737-500 is fitted with a solid glass cathode ray tube (CRT) screen.

The CRT screen is approximately 2 cm thick, curved in design, and fits snugly within the display frame of the CDU. Although it’s possible to make this screen operational, the display will be mono-colour (green) and the screen resolution poor. Therefore, the CRT was replaced with a custom-sized high resolution colour LCD screen.

To replace the CRT screen is not without its challenges. The first being that the LCD screen is not 2 cm in thickness and will not fit snugly within the curved display recess of the CDU frame. To rectify this shortfall, a piece of clear glass must be ground to correctly fit within the frame. This piece of glass replaces the 2 cm thick, curved CRT glass.

Photo showing how the thin LCD screen was secured with tape the glass screen. Although the process appears rudimentary, it's functional

The thin LCD screen is installed directly behind the clear glass using high density tape. Commercial grade double-sided sticky tape is the easiest method, but it is rudimentary. The reason that tape is used, is that should the screen fail, it’s easy to remove the tape, install a replacement screen, and then tape the screen in place.

During the design phase, it was thought that the thick piece of glass would cause a refraction problem. However, although the theory suggests refraction will occur, the practical application has been such that any refraction is not readily noticeable.

Installing the SimStacks Foundation Board and Screen Controller Card

To enable the CDU to operate, four items need to be mounted inside the CDU.

(i) The generic Interface card that controls the LCD screen;

(ii) The LCD screen controller (buttons that control brightness, contrast, etc);

(iii) The SimStack Foundation Board; and,

(iv) The wiring to connect the keyboard to the Foundation Board.

Fortunately, there is ample room in the cavernous interior of the CDU to fit these items.

The SimStack Foundation Board is mounted on an angular metal bracket that is attached directly to the bottom of the CDU, while the LCD interface card has been installed on the upper shelf along with the screen controller. A ribbon cable connects the LCD screen to the interface card while a standard VGA cable connects the LCD screen to the client computer and Ethernet switch.

The SimStack Foundation Board is Ethernet ready and requires a standard Ethernet cable (CAT 6) to connect from the card to an Ethernet switch (located behind the MIP). In addition to the Ethernet and VGA cable, six power wires leave the CDU via the rear of the casing; four from the SimStack Foundation Board (5 and 12 volts +-) and two from the keypad (5 volts +-) to control the backlighting.

The specialist switch and wiring (Ethernet, power and VGA cables) extruding from the rear of the CDU

Specialist Switch and Power Supply

A standard two-way toggle switch is mounted to the rear of the CDU casing.

This switch is used to control whether the LCD screen, used in the CDU, is always on, or is only turned on when ProSim-AR is activated.

To operate the CDU requires a 5 and 12 volt power supply. The backlighting of the keypad is powered by 5 volts while the SimStack Foundation Board and CDU operation require 12 volts.

Backlight Dimming (keypad)

To enable the CDU keypad to be dimmed, the 5 volt wires are connected to a dedicated 5 volt Busbar located in the center pedestal. This Busbar is used to connect the backlighting from all OEM panels. The Busbar is then connected to the panel knob on the center pedestal. The ability to turn the backlighting on and off is controlled by opening or closing a 12 volt relay (attached in line between the panel knob and Busbar). Dimming is controlled by a dimmer circuit (see earlier article).

Installing the OEM CDU to Flight Deck Solutions MIP

It can be challenging attempting to install OEM panels, gauges and other items to a reproduction Main Instrument Panel (MIP). Unfortunately, no matter what the manufacturer states, many MIPS do not comply with real world measurements.

Before and after photograph of the FDS CDU bay showing the small flange from the shelf that needed to be trimmed to enable the CDU to slide into the bay recess. A small notch was made at the corner to facilitate the safe routing of the wires used to enable the Lights Test

The MIP skeleton is manufactured by Flight Deck Solutions (FDS) and the CDU bay, although fitted with OEM DZUS rails, is designed to fit FDS’s propriety CDU unit (MX Pro) and not an OEM unit.

The casing for the OEM CDU is much longer than the FDS CDU and measures 20 cm in length.

The FDS MIP design is such that the aluminum shelf (used by FDS to mount various interface cards) protrudes slightly into the rear of the CDU bay. This protrusion stops the OEM casing from sliding neatly into the bay to its fullest extent. To enable the CDU to slide into the CDU bay, the shelf must be ‘trimmed’.

To trim the metal away from the shelf, a small metal saw was used, and although an easy task, care must be taken not to ‘saw away’ too much metal. Once the piece of offending aluminum is removed, the CDU slides perfectly into the bay, to be secured by DZUS fasteners to the DZUS rail.

Functionality and Operation

The CDU is not intelligent; it’s basically a glorified keyboard that must be interfaced with ProSim-AR to enable the CDU to function correctly. The fonts and colour of the fonts is generated by the avionics suite (in this case ProSim-AR, but arguably it could also be Sim Avionics or Project Magenta).

To enable communication between the avionics suite and the SimStack Foundation Board, proprietary software must be installed. This software has been developed by Simulator Solutions.

SimStack Software (simswitch)

Screen grab showing SimSwitch software User Interface. SimSwitch is standalone once the initial configuration has been completed. The software can be configured to open in minimised mode via a batch file

To enable communication between the Foundation Board and ProSim737, propriety software, called SimSwitch must be installed to the computer that has the CDU connected.

SimSwitch is a JAR executable file, that when configured with the correct static IP address and port numbers, provides communication between ProSim-AR (on the server computer) and the network (clients). The switch must be opened for communication to occur between the Foundation Board, SimSwitch and ProSim737. The jar file can easily be included into a batch file (with timer command) for automatic loading when flight simulator is used.

When opened, SimSwitch displays the User Interface. The User Interface displays all OEM panels that have been connected using a SimStacks, can be used to monitor connected panels, and can display debugging information (if required).

Independent Operation

The Captain and First Officer CDUs are not cloned (although this is easy to do), but operate as separate units. This is identical to the operation in the real aircraft, whereby the Captain and First Officer are responsible for specific tasks when inputting the information into the CDU.

First Officer CDU

The First Officer CDU will be converted using a similar technique, with the exception that this unit will be converted more ‘cleanly’. Rather than use an angled plate on which to attach the SimStacks Foundation Board, a solid aluminum plate will be used. The LCD screen controller card will also be attached to the rear of the LCD screen. Finally, to enable fast and easy removal of the CDU, the connection of the Ethernet cable will be outside of the unit.

Additional Information

SoarByWire (another enthusiast) has written an excellent article dealing with interfacing SimStacks.

Below is a short video demonstrating the operation of the OEM CDU using ProSim737.

Main points to note in the video are:

Heavy duty tactile keys.

The definite click that is heard when depressing a key.

The solid keypad (the keys do not wobble about in their sockets).

Although subjective, the appearance of the OEM CDU looks more aesthetically pleasing that a reproduction unit.

Final Call

The conversion has been successful and, when connected with ProSim737 via SimSwitch, all the functions available in the CDU work correctly.

Glossary

ARINC 429 – A standard used to address data communications between avionics components. The most widely used standard is an avionics data bus. ARINC 429 enables a single transmitter to communicate data to up to 20 receivers over a single bus.
Standalone – Two meanings. Operation does not require an interface card to be mounted outside of the panel/part; and, In relation to software, the executable file (.exe) does not need to be installed to C Drive, but can be executed from any folder or the desktop.

Updated for clarity and information 12 June 2020.

March 08, 2017

Conversion of OEM CDU - Part One

March 08, 2017/ Flaps 2 Approach

Completely gutted. All unnecessary and unusable electronic components have been removed

One of the more advanced projects is the conversion of two OEM Control Display Units manufactured by Smiths. The two CDUs came from a Boeing 500 series airframe that was retired from service in 2008 due to United Airlines decision to adopt the Airbus A-320. A chronometer located on the rear of each unit, shows the hours of use - one unit has 5130 hours while the other has 1630 hours.

The Control Display Unit (CDU) is the interface that the flight crew use to access and manipulate the data from the Flight Management Computer (FMC); it's basically a screen and keyboard. The FMC in turn is but one part of a complex system called the Flight Management System (FMS). The FMS is capable of four dimensional area navigation. It is the FMS that contains the navigational database. Often the words CDU and FMC are used interchangeably.

In this article I will discuss some of differences between OEM and reproduction CDUs. In addition to explaining some of the advantages that using an OEM unit brings. A second article will deal with the actual conversion of the units to operate with ProSim737.

Port side of CDU with casing removed to show the electronic boards that are secured by lever clips. Like anything OEM, the unit is constructed from solid component

Construction and Workmanship

The construction and workmanship that has gone into producing anything OEM is quite astounding.

The CDU is built like a battleship and no amount of use or abuse can damage the unit. The unit is quite large and heavy. I was surprised at the eight, a good 6 kilograms. Most of the weight is made up by the thick glass display screen CRT, and other components that reside behind the glass within the sturdy aluminium case.

A myriad number of small screws hold together the 1 mm thick aluminium casing that protects the internal components. In addition to screws, there are two special DZUS fasteners, that when unlatched, enable the side of the unit’s casing to be removed for maintenance.

When the casing of the CDU is removed, the inside is jammed full of components, from the large CRT screen to gold-plated electronic boards that are clipped into one of three internal shelves.

One aspect in using anything OEM is the ease at which the item can be inserted into the flight deck. DZUS attachments enable the unit, once it has been slid into the CDU bay, to be securely fastened. I use a MIP manufactured by Flight Deck Solutions and the CDU slides seamlessly into the CDU bay.

Detail of the keyboard and DIM knob. Interestingly the DIM knob dims the actual CRT screen and not the backlighting

Tactile Differences

Aside from external build quality, one of the main differences you immediately notice between an OEM and reproduction CDU, is the tactile feeling when depressing the keys on the keyboard. The keys do not wobble in their sockets like reproduction keys, but are firm to press and emit a strong audible click.

Furthermore, the backlighting is evenly spread across the rear of the keyboard panel with each key evenly illuminated.

Aesthetic Differences – 500 Series and Next Generation

As the CDU dates from 2008, the external appearance isn’t identical to the CDU used in the Next Generation airframe, however, it is very close.

Main Differences:

The dim knob is a slightly different shape.
The display screen is rounded at the corners od the screen (the NG is more straight-edged).
The absence of the horizontal white lines located on the inside edge of the display frame bezel.
The display screen is different (cathode ray tube (CRT) in contrast to liquid crystal display (LCD).
The illumination is powered by bulbs.

In terms of functionality, as this is controlled by software (ProSim737) the functionality is identical. This also holds true for the font type and colour.

To an absolute purist, these differences may be important, and if so, you will have to contend with a reproduction CDU, or pay an exorbitant amount for a decommissioned NG unit.

OEM CDU installed to MIP functioning with ProSim737

Conversion for use with ProSim737

There are many ways to convert a real aircraft part for use in Flight Simulator. By far the most professional and seamless is the integration of the real part using the ARINC429 protocol language (as used in the real aircraft). However, using ARINC429 is not a simple process for all applications. Not too mention that you often must use high voltage AC power.

For the most part I’ve used Phidgets to convert real parts, however, in this conversion I wanted to try a different approach. I’m going to liaise with an Australian company called Simulator Solutions. This company specialises in converting high-end electronic components used in commercial flight simulators, and manufactures an interface board that should enable seamless conversion of the CDU.

This article one part of two. Conversion of OEM CDU Part 2.
Additional photographs of the CDU can be viewed in the image gallery.

Glossary

ARINC 429 – A standard used to address data communications between avionics components. The most widely used standard is an avionics data bus. ARINC 429 enables a single transmitter to communicate data to up to 20 receivers over a single bus.
OEM - Original Equipment Manufacture (aka real aircraft part).

August 27, 2015

10 Mile ARC to VOR 30 Approach - Hobart, Tasmania Australia (YMHB)

August 27, 2015/ Flaps 2 Approach

Approach chart depicting VOR 30 Approach to YMHB. Important points to note are: initial approach courses to intercept the arc (295 & 334), the D10 HB arc, the altitude increments of 4000, 3000 and at 7 miles, 2400, and the Initial Approach Fix (IAF) and speed of 210 kias

Recently, I flew from Brisbane to Hobart and the pilot flying made a different style of approach to what normally is made at this airport. After landing, I approached the pilots and queried the approach. The Captain stated that he had decided to fly a semi-automated VOR approach along an arc to land at runway 30.

The reason being, that Air Traffic Control (ATC) had warned them of turbulent conditions near the airport. He commented that in such conditions, he felt more confident using the older style arc approach using LNAV/VNAV with Speed Intervention (SPD INTV) engaged, with a transition to Vertical Speed and VOR once on final.

The First Officer stated that this was the first time he had seen an arc being used to set-up for a VOR approach. He said that usually they use ILS into RWY 12 or RNAV into RWY 30. He commented that the only time he had made a VOR approach was during simulator training, and then he would probably only use such an approach, if the ILS was inoperative or there was an issue with RNAV.

The use of this approach is a prime example of the variation offered to pilots in relation to how they fly and land the Boeing 737.

Screen Images

Several screen captures from the Instructor Station, CDU and Navigation Display (ND) which I hope will make it easier to understand this post. The avionics suite used is ProSim737 distributed by ProSim-AR. Note that some of the mages are not sequential as I captured the images over two simulator sessions.

How To Set-Up An Arc

To set-up an approach using an arc is very easy.

The following example is for Hobart, Tasmania Australia (YMHB). The instructions assume that you are conversant with operating the CDU and have a basic understanding of its use.

Essentially, an arc is using a Place/Bearing/Waypoin t to define an arc around a point at a set distance. The distance between each of the generated waypoints along the arc, is at the discretion of the flight crew.

Approach Charts

To determine the correct distance to create the arc, the approach chart for the airport should be consulted. The chart, in addition to providing this information, will also aid you in decided where to place the final waypoint (if wanted) along the approach course.

In this example, the YMHB VOR 30 approach states that the aircraft must fly an arc 10 miles from the airport between an altitude of 4000 and 3000 feet before descending to be at 2400 feet 7 miles from the runway threshold.

The approach chart depicted is provided by Lufthansa Systems (LIDO/FMS) distributed by Navigraph.

Navigraph Charts 4 Review.

CDU Instructions

(i) Open the FIX page and type in the scratchpad the airport code (YMHB). After uploading, type the distance (/10 miles). This will create a green-dotted citcle around YMHB with a radius of 10 miles.

(ii) Open the LEGS page and type into the scratchpad the airport code (YMHB). Immediately following YMHB, type the required radial1 (in degrees) from the airport that you wish the initial waypoint to be generated. Follow this with a slash and type in the distance from the airport (YMHB340/10).

This will generate a waypoint 10 miles from YMHB on the 340 radial. This is the waypoint from which you will begin to build your arc.

Obviously, the radial you use to define the location of your first waypoint will depend upon the bearing that you are flying toward the airport.

(iii) To Generate the ARC you must repeat the above process (ii) changing the radial by 10 degrees (or whatever you believe is needed) to generate the required waypoints around the arc at 10 miles from the airport. As an example: YMHB320/10, YMHB340/10, YMHB000/10 and so forth until the arc is built.

As you upload each of the radials you will note that the name for the waypoint is changed to a sequential number specific to each waypoint. As an example; the above waypoints will each be named YMH01, YMH02 and YMH03.

If you make a mistake, you can delete a waypoint and start again; however, realize that the sequential numbers will not be in order. This is not an issue (it is only a number) but it is something be aware of.

In our example, the VOR approach is for runway 30. Therefore; your final waypoint on the arc will be YMHB121/10. Prior to reaching this waypoint, if flying manually, begin the right hand turn to intercept the approach on the 121 radial (bearing 300 degrees).

A Note About /-+

The more observant will note that the distances in the example above do not utilise the /+ key before the distance (YMHB340/+10). When entering the distance it can be with or without the + key.

Variation

Before going further, there are many ways to fly the B737. The method selected is at the discretion of the pilot in command and is dependent upon airline preferences, environmental conditions, and pilot experience. This statement was stressed to me when I spoke with the Captain of the aircraft.

Often an approach will incorporate a number of automated systems including VNAV, LNAV, Vertical Speed, Level Change, VOR Localizer and old fashioned manual VFR flying. In most cases the particular approach will be programmed into the CDU, at the very least for situational awareness. However, the CDU does not have to be used and often a step down approach is a good way to maintain flying skills and airmanship.

Handy Hints

The following hints will assist with situational awareness and in allowing the aircraft to be guided by the autopilot to a point to which manual flight can commence.

If you carefully study the approach chart for YMHB VOR 30, you will note that the altitude the aircraft should be at when at 7 miles from the threshold should be 2000 feet. The chart also depicts the letter D at this point meaning that a continuous descent can be made this point.

Hint One - visual descent point (VDP)

To make the transition from the arc to the approach easier, create a waypoint at the 7 mile point from the airport along the radial used for the approach (YMHB121/7). Using a waypoint allows the aircraft’s Lateral Navigation (LNAV) to be used. This type of waypoint is usually referred to as a Visual Descent Point (VDP).

When the waypoint at 7 miles from the threshold is reached, a transition to manual flying can commence, or Vertical Speed can be used to maintain a 3 degree glidepath (GP) while following the VOR. Remember to change the EFIS from MAP to VOR so you can use the VOR indicator during the approach.

Hint Two - extend runway line

Assuming you have not inserted an approach into the CDU, an aid to increase situational awareness is to select the correct runway from the CDU and enter a distance that the runway line is to be extended from the threshold.

To do this, select runway 30 from the ARRIVALS (ARR) page in the CDU (RWY30) and type the numeral 7 (or whatever distance you require) into the scratchpad and upload. This will extend the green line from the runway threshold to the previously generated waypoint at 7 miles. Ensure you clean up any discontinuity (if observed) in the LEGS page.

This enables three things:

The generation of a 3 degree glidepath (GP) from the distance entered (example is 7 miles) to the runway threshold.
It enables LNAV (even if the autopilot is not engaged) to continue to provide the Flight Director (FD) with heading information during the approach, and
It enables the Navigation Performance Scales (NPL) on the Pilots Flight Display (PFD) to provide glidepath (GP) guidance (assuming that the correct runway or approach is selected in the CDU and NPL is enabled within the ProSim737 avionics suite).

UPPER LEFT: Screen capture from the instructor station PFD and ND for the approach into YMHB. The aircraft, after turning right from the 10 mile arc, is aligned with the 121 radial approaching the waypoint YMH07 (the WP entered at the 7 mile point). LNAV is engaged and the aircraft is being controlled by the autopilot. As RWY 30 was inserted into the route, the Navigation Performance Scales (NPS) show Glidepath (GP) data in the Primary Flight Display (PFD). Note that the EFIS is still on MAP and is yet to be turned to VOR. In real life, VOR would have been selected earlier (click to enlarge).

LOWER LEFT: The transition from LNAV to VOR has occurred and the autopilot and autothrottle are not controlling the aircraft. The aircraft is on short final with gear down, flaps 30 and the airspeed is slowly decaying to VREF+5.

The EFIS has been changed from MAP to VOR to allow manual tracking using the VOR needle. The NPS show good vertical alignment with a lateral left offset; the VOR indicator confirms this. The Flight Mode Annunciator (FMA) displays LNAV (although the autopilot is disengaged) and the Flight Director (FD) and NPS show glidepath (GP) data. The Flight Path Vector (FPV) symbol shows a continuous descent at roughly 3 degrees. The altitude window and heading on the MCP has been set to the appropriate missed approach (4200/300). Click image to enlarge.

Do Not Alter Constraints

As alluded earlier, there are many ways to accomplish the same task. However, DO NOT alter any constraints indicated in the CDU if an approach is selected and executed. CDU generated approaches have been standardised for a reason.

Finding the Correct Radial/Bearing to Build Your Arc

Finding the correct bearing to use on the arc can be challenging for those less mathematically inclined. An easy method is to use one of the two MCP course selector knobs.

Rotate the knob until the green dotted line on he Navigation Display (ND) lies over the area of the arc that you wish the waypoint to be created. Consult the MCP course selector window - this is the figure you place in the CDU. Next, rotate the knob a set number of degrees and repeat the process. You can also consult the data displayed along the course indicator line on the Navigation Display (ND).

When you build the arc, ensure you have set the EFIS to PLN (plan). PLN provides more real estate to visualize the approach on the Navigation Display (ND). You can use STEP in the LEGS page to cycle through the waypoints to ensure you have an appropriate view of the surrounding area.

Important Points

Always double check the Place/Bearing/Waypoint entries in the CDU and in the ND (PLN) before executing. It is amazing how easy discrepancies can occur.
Always check the approach plate for the approach type you are intending to make. Once again, mistakes are easy to make.
If using VNAV, double check all speed and altitude constraints to ensure compliance with the approach chart and situation (some airlines promote the use of the speed intervention button (SPD INTV) to ensure that appropriate speeds are maintained).
If need be, select the approach (ARR) in the CDU to provide added situational awareness.

Images

The following are screen captures from the instructor station CDU and Navigation Display (ND). Ignore altitude and speed constraints as these were not set-up for the example. Click each images to enlarge.

LEFT: Circular FIX ring has been generated around YMHB at 10 mile point. The arc waypoints will be constructed along this line.

LEFT: Various waypoints have been generated along the 10 mile fix line creating an arc. The arc ends at the intersection with the 212 radial for the VOR 30 approach into YMHB. The route is in plan (PLN) view and is yet to be executed.

LEFT: The constructed arc as seen in MAP view. From this view it is easy to establish that the aircraft is approaching TTR and once reaching the 10 mile limit defined by the 10 mile FIX (green-coloured dotted circle), the aircraft will turn to the left to follow the arc waypoints until it intersects with the 121 radial.

LEFT: This image depicts the waypoint generated at 7 mile from the threshold (YMHB121/7). This waypoint marks the point at which the aircraft should be on the 121 radial to VOR 30 and at 2400 feet altitude (according to the VOR 30 approach plate.

LEFT: RWY 30 has been selected from the arrivals (ARR) page. This displays the guidepath (GP) assistance. it also generates a runway line extending from the threshold to 7 miles out; the same distance out from the threshold that the final waypoint was generated.

The course line is coloured pink indicating that LNAV is enabled and the aircraft is following the programmed route.

At the final waypoint (YM10) the autopilot (if used) will be disengaged and the aircraft will be flown manually to the runways using the VOR approach instrumentation and visual flight rules (VFR). The EFIS will be changed from MAP to VOR. LNAV will remain engaged on the MCP to ensure that the NPL indications are shown on the PFD. The NDL indicators provide glidepath (GP) guidance that is otherwise lacking on a VOR approach.

Final Call

I rarely use automated systems during landing, unless environmental conditions otherwise dictate. I prefer to hand fly the aircraft where possible during the approach phase, and often disengage the autopilot at 5000 feet. If flying a STAR and when VNAV/LNAV is used, I always disengage the autopilot no later than 1500 feet. This enables a safe envelope in which to transition from automated flight to manual flight.

Using an arc to fly a VOR approach is enjoyable, with the added advantage that it provides a good refresher for using the Place/Bearing/Waypoint functionality of the CDU.

Additional articles that address similar subjects are:

Glossary

CDU – Control Display Unit (aka Flight Management Computer (FMC).
EFIS – Electronic Flight Instrument System.
LNAV – Lateral navigation.
RADIAL/BEARING – A radial radiates FROM a point such as a VOR, whilst a bearing is the bearing in degrees TO a point. The bearing is the direction that the nose of the aircraft is pointing.
VNAV – Vertical Navigation.

January 19, 2015

Direct-To-Routing, ABEAM PTS and INTC CRS - Review and Procedures

January 19, 2015/ Flaps 2 Approach

In an earlier post, a number of methods were discussed in which to create waypoints ‘on the fly’ using the Control Display Unit (CDU). Following on a similar theme, this post will demonstrate use of the Direct-To Routing, ABEAM PTS and Course Intercept (INTC CRS) functionality.

CDU use an appear very convoluted to new users, and by far the easiest way to understand the various functionalities is by ‘trial and error and experimentation’.

The software (Sim Avionics and ProSim737) that generates the math and formulas behind the CDU is very robust and entering incorrect data will not damage the CDU hardware or corrupt the software. The worst that can happen is having to restart the CDU software.

Line Style and Colour

The style and colour of the line displayed on the Navigation Display (ND) is important as it provides a visual reference to the status of a route or alteration of a route.

Dashed white-coloured lines are projected courses whilst solid magenta-coloured lines are saved and executed routes. Similar colour schemes apply to the waypoints in the LEGS page. A magenta-coloured identifier indicates that this is the next waypoint that the aircraft will be flying to (it is the active waypoint).

Direct-To Routing

A Direct-To Routing is easily accomplished, by selection of a waypoint from the route in the LEGS page, or by typing into the scratchpad (SP) a NAVAID identifier and up-selecting this to LSK 1L. Once up-selected, the Direct-To route will be represented on the Navigation Display (ND) by a dashed white-coloured line. Pressing the EXEC button on the CDU will accept the route modification and precipitate several changes:

The route line displayed on the ND, previously a white-coloured dashed line will become solid magenta in colour;
The previous displayed route will disappear from the ND;
All waypoints on the LEGS page between the aircraft's current position and the Direct-To waypoint in LSK 1L will be deleted; and,
The Direct-To waypoint in LSK 1L will alter from white to magenta.

Once executed the FMS will direct the aircraft to fly directly towards the Direct-To waypoint.

ABEAM PTS

Following on from the Direct-To function is the ABEAM PTS function located at LSK 5R.

ABEAM points (ABEAM PTS) are one or more fixes that are generated between two waypoints from within a programmed route. The ABEAM PTS functionality is found in the LEGS page of the CDU at LSL 5R and is only visible when a Direct-To Routing is being modified, within a programmed route (the LEGS page defaults to MOD RTE LEGS). Furthermore, the ABEAM PTS dialogue will only be displayed if the the up-selected fix/waypoint is forward of the aircraft's position; it will not be displayed if the points are located behind the the aircraft.

If the ABEAM PTS key is depressed, a number of additional in-between fixes will be automatically generated by the Flight Management System (FMS), and strategically positioned between the aircraft’s current position and the waypoint up-selected to LSK 1L. The generated fixes and a white-coloured dashed line showing the modified course will be displayed on the Navigation Display (ND).

To execute the route modification, the illuminated EXEC button is pressed. Following execution, the white-coloured line on the ND will change to a solid magenta-coloured line, and the original displayed route will be deleted. Furthermore, the LEGS page will be updated to reflect the new route.

Nomenclature of Generated Fixes

The naming sequence for the generated fixes is the first three letters of the original waypoint name followed by two numbers (for example, TTR will become TTR 01 and CLARK will become CLA01). If the fixes are regenerated, for instance if a mistake was made, the sequence number will change indicating the next number (for example, TTR01, TTR02, etc).

Technique

Up-select a waypoint from the route in the LEGS page to LSK 1L, or type into the scratchpad a NAVAID identifier. This is a Direct-To Routing; when executed the waypoints between the up-selected waypoint and LSL 1L are deleted.
Press ABEAM PTS in LSK 5R to generate a series of fixes along a defined course from the aircraft’s current location to the up-selected waypoint. The fixes can be seen on the ND.
Pressing the EXEC button will accept and execute the ABEAM PTS route.

Example and Figures

The below figures are screen captures using ProSim737 avionics suite. The programming of the CDU has been done with the aircraft on the ground. Click any image to enlarge.

**FIGURE 1:** The LEGS page shows a route HB-TTR-CLARK-BABEL-DPO-WON. The route is defined by a solid magenta-coloured line

**FIGURE 2:** The Route is altered to fly from HB to BABEL. Note that in the LEGS page, the title has changed from ACT to MOD RTE 1 LEGS. The ND displays the generated ABEAM PTS and projected course (white-coloured dashed line), beginning from the aircraft’s current position and traveling through HB01, TTR01, CLA01 to BABEL. The EXEC light is also illuminated

**FIGURE 3:** When the EXEC light is pressed, the ABEAM PTS and altered route (Figure 2) will be accepted. The former route will be deleted and the white-coloured dashed line will be replaced by a solid magenta-coloured line. The magenta colour indicates that the route has been executed. The LEGS page will also be updated and display the new route, with the waypoint HB01 highlighted in magenta

The Intercept Course (INTC CRS)

To understand the INTC CRS, it is important to have a grasp to what a radial and bearing is and how they differ from each other. For all practical purposes, all you need to know is that a bearing is TO and a radial is FROM. For example, if the bearing TO the beacon is 090, you are on the 270 radial FROM it.

The Intercept Course (INTC CRS) function is located beneath the ABEAM PTS option in the LEGS page of the CDU at LSK 6R. Like the ABEAM PTS function, the INTC CRS function is only visible when a when a Direct-To Routing, is being modified within a programmed route (the LEGS page defaults to MOD RTE LEGS).

The function is used when there is a requirement to fly a specific course (radial) to the fix/waypoint. By default, the INTC CRC displays the current course to the fix/waypoint. Altering this figure, will instruct the FMS to calculate a new course, to intercept the desired radial towards the fix/waypoint (1) The radial will be displayed on the ND as a white-coloured dashed line, while the course to intercept the radial (from the aircraft’s current position) will be displayed as a magenta-coloured dashed line.

Visual Cues

An important point to note is that, if the course (CRS) is altered, is that the displayed (ND) white-coloured line will pass directly through the fix/waypoint, but the line-style will be displayed differently dependent upon what side of the fix/waypoint the radial is, in relation to the position of the aircraft. The line depicted by sequential long and short dashes (dash-dot-dash) shows the radial TOWARDS the fix/waypoint while the line showing dots, displays the radial AWAY from the fix/waypoint.

It is important to understand, that for the purposes of the FMS, it will always intercept a course TO a fix/waypoint; therefore, the disparity in how the line-style is represented provides a visual cue to ensure a flight crew does not enter an incorrect CRS direction.

Intercept Heading

However, the flight crew may wish not fly directly to the fix/waypoint, but fly a heading to intercept the radial. In this case, the flight crew should select the particular heading they wish to fly in the MCP heading selector window, and providing LNAV is armed, the aircraft will fly this heading until reaching the intercept course (radial), at which time the LNAV will engage and the FMS will direct the aircraft to track the inbound intercept course (radial) to the desired fix/waypoint.

Technique

Up-select a waypoint from the route in the LEGS page to LSK 1L, or type into the scratchpad a NAVAID identifier and up-select. This is a Direct-To Routing and will delete all waypoints that the aircraft would have flown to prior to the up-selected identifier.
Type the course required into INTC CRS at LSK 6R.
This will display on the ND a white-coloured long dashed line (course/radial). Check the line-style and ensure that the course is TOWARDS the waypoint. The line, closest to the aircraft should display sequential long and short dashes.
Prior to pressing the EXEC button to confirm the route change, check that the intended course line crosses the current course line of the active route (solid magenta-coloured line).
If wishing to fly a heading to intercept the radial, use the MCP heading window. If LNAV is armed the FMS will direct the aircraft onto the radial.

Example and Figures

The below figures are screen captures using ProSim737 avionics suite. The programming of the CDU has been done with the aircraft on the ground. Click any image to enlarge.

**FIGURE 1:** The LEGS page shows a route HB-TTR-CLARK-BABEL-DPO-WYY-WON. The route is defined by a solid magenta-coloured line. ATC request ‘QANTAS 29 fly 300 degrees until intercepting the 345 degree radial of BABEL; fly that radial to BABEL then remainder of route as filed

**FIGURE 2:** From the LEGS page, locate in the route the waypoint BABEL (LSK 4L). Recall that the INTC CRS will only function in Direct-To Routing mode. Up-select BABEL to LSK 1L. Note that a dashed white-coloured line is displayed on the ND showing the new course from HB to BABEL. The original course is still coloured magenta and the EXEC light is illuminated

**FIGURE 3:** Type the radial required (345) into INTC CRS at LSK 6R. This action will generate (fire across the page) a white-coloured dashed line displaying the 345 course to BABEL (the 165 radial). Check the line-style and ensure the radial crosses the aircraft’ current course which is 300. Recall that this line style indicates that the radial to TO BABEL

**FIGURE 4:** Press EXEC to save and execute the new route. The dashed line alters to a solid magenta-coloured line and joins with the remainder of the route at BABEL. The magenta colour indicates this is now the assigned route. Note that the magenta line continues across the ND away from the aircraft and BABEL. This is another visual cue that the radial is traveling TO BABEL
If the aircraft continues to fly on a course of 300 Degrees, and LNAV is armed, the FMS will alter course at the intersection and track the 345 course to BABEL (165 radial). The LEGS page is also updated to reflect that BABEL is the next waypoint to be flown to (BABEL is coloured magenta

Final Call

Direct-To Routings and ABEAM Points are usually used when a flight crew is required to deviate, modify or shorten a route. Although the use of ABEAM PTS can be debated for short distances, the technology shines when longer routes are selected and several fixes are generated. The Intercept Course function, on the other hand, is used whenever published route procedures (STAR and SID transitions), or ATC require a specific course (radial) or heading to be followed to or from a navigation fix.

Caveat

The content of this post has been checked to ensure accuracy; however, as with anything that is convoluted minor mistakes can creep in (Murphy, aka Murphy's Law, reads this website). If you note a mistake, please contact me so it can be rectified.

Acronyms and Glossary

ATC – Air Traffic Control
CDU – Control Display Unit
Direct-To Routing – Flying directly to a fix/waypoint that is up-selected to LSK 1L in the CDU. All waypoints prior to the u-selected waypoint will be deleted
DISCO – refers to a discontinuity between two waypoints loaded in a route within the LEGS page of the CDU. The DISCO needs to be closed before the route can be executed
DOWN-SELECT - Means to download from the CDU LEGS page to the scratchpad of the CDU)
FIX – A geographical position determined by visual reference to the surface, by reference to one or more NAVAIDs
FMC – Flight Management Computer
FMS – Flight Management System
Identifiers – Identifiers are in the navigation database and are VORs, NDB,s and published waypoints and fixes
LSK 5L – Line Select: LSK refers to line select. The number 5 refers to the sequence number between 1 and 6. L is left and R is right (as you look down on the CDU in plan view)
MCP – Mode Control Panel
NAVAIDS – Any marker that aids in navigation (VOR, NDB, Waypoint, Fix, etc.). A NAVAID database consists of identifiers which refer to points published on routes, etc
ND – Navigation Display
RADIALS – A line that transects through a NAVAID representing the points of a compass. For example, the 045 radial is always to the right of your location in a north easterly direction (Bearings and Radials Paper)
ROUTE – A route comprising a number of navigation identifiers (fixes/waypoints) that has been entered into the CDU and can be viewed in the LEGS page
SP - Scratchpad
UP-SELECT – Means to upload from the scratchpad of the CDU to the appropriate Line Select (LSK)
WAYPOINT – A predetermined geographical position used for route/instrument approach definition, progress reports, published routes, etc. The position is defined relative to a station or in terms of latitude and longitude coordinates.

1: The FMS will calculate the new course based on great circle course between the aircraft’s current location and the closest point of intercept to the desired course. This course is displayed on the ND as a white dashed line.

May 17, 2014

Approach Tools: Vertical Bearing Indicator, Altitude Range Arc and Vertical Deviation Scale

May 17, 2014/ Flaps 2 Approach

qantas 737 (Aero Icarus from Zürich, Switzerland, Qantas Boeing 737-400; VH-TJI@SYD;31.07.2012 666im (7863511354), CC BY-SA 2.0)

On 12 February 2012, the flight crew of a Boeing 737 aircraft, registered VH-TJS and operated by Qantas Airways Limited, was conducting a scheduled passenger service from Sydney, New South Wales to Canberra, Australian Capital Territory. Due to scheduled maintenance the instrument landing system at Canberra was not available and the crew prepared for an alternate instrument approach that provided for lateral but not vertical flight path information. The flight was at night with rain showers and scattered cloud in the Canberra area.

Shortly after becoming established on the final approach course with the aircraft’s automatic flight system engaged, the flight crew descended below the minimum safe altitude for that stage of the approach. The crew identified the deviation and leveled the aircraft until the correct descent profile was intercepted, then continued the approach and landed. No enhanced ground proximity warning system alerts were generated, as the alerting thresholds were not exceeded.

During those phases of flight when terrain clearance is unavoidably reduced, such as during departure and approach, situation awareness is particularly crucial. Any loss of vertical situation awareness increases the risk of controlled flight into terrain. This occurrence highlights the importance of crews effectively monitoring their aircraft’s flight profile to ensure that descent is not continued through an intermediate step-down altitude when conducting a non-precision approach (Australian Transport safety Bureau, 2013).

Determining the correct rate of descent (RoD) or vertical speed (V/S) is a critical attribute if an aircraft is to arrive at the correct altitude and avoid excessive descent rates. Control of the vertical path uses two different methods: the step-down method and the constant descent method. Both methods assume that the aircraft is being flown in landing configuration at the final approach speed (VaPP) from the final approach fix (FAF) to the landing initiation of the missed approach.

Non Precision Approaches (NPA)

Historically non precision approaches reference ground navigation aids that exhibit a degree of inaccuracy, which is often enhanced by the poorly defined vertical path published on an approach chart; NPA charts typically provide only an assigned altitude at the FAF and the distance from the FAF to the MAP. Thus, flight crew awareness of the aircraft’s vertical position versus the intended vertical path of the final approach can be quite low when executing traditional style step-down approaches.

To determine the best vertical speed to use during a non precision approach, flight crews use a number of 'back of the envelope' calculations.

Rate of Descent & Glideslope Calculations

There are several calculations that can be used determine rate of descent – some more accurate than others. Search ‘determine descent rate’ in Google. Some of the more commonly used rules of thumb are:

Divide your ground speed by 2, then add a zero (120 kias / 2 = 60, add 0 = 600 fpm).
Rate of descent (RoD) in ft/min should be equal to 5 times the ground speed in knots (same as above but different calculation).
To maintain a stabilized approach, add a zero to your indicated air speed and divide by two (150 kias + 0 = 1500 / 2 = 750 fpm).
To determine distance from threshold to start a 3 degree glideslope, take the height above ground level and divide by three hundred (600 ft AGL / 300 = 2 nm).
To maintain a 3 degree glideslope (ILS), multiply your ground speed by 5. The resulting number is the rate of descent to fly (110 kias x 5 + 550 fpm on 3 degree glideslope).
If the glideslope is not operational on an ILS approach with DME, multiply the distance ‘to go’ by 300. This will provide the height in feet above the threshold of the runway (4 nm to the threshold; multiply x 300 = 1200 ft).

Flight crews today, especially those flying in and out of busy intercity hubs, rarely execute step down approaches as computer and GPS-orientated systems have replaced traditional methods of navigation. However, as the flight into Canberra revealed, the best system may at times be inoperative or fail and it is good airmanship to understand and be able to remember one or more of the above equations.

Today's systems provide a high level of redundancy and the Boeing 737-800 NG incorporates a number of integrated aids to assist a flight crew during descent and approach. In this post some of less commonly understood aids will be discussed.

CDU showing DES Page, waypoint/altitude and VBI interface (*Key RSK3 & RSK4*)

Vertical Bearing Indicator (VBI))

A tool often overlooked with regard to positional awareness is the Vertical Bearing Indicator (VBI). The VBI display is accessed and displayed in the CDU.

The VBI can calculate an accurate rate of descent to a particular spatial point. It is basically an angle calculator that provides ‘live’ vertical speed information based upon a desired descent angle, the current speed of the aircraft and an end location.

A flight crew enters into the VBI the final altitude that the aircraft should be at (for example, the Final Approach Fix or runway threshold). This figure is determined by consulting the appropriate approach chart for the airport. The CDU will then calculate the descent rate based on flight variables. As the aircraft descends, the VBI readout will continually update the descent rate based upon aircraft speed and rate of descent.

The flight crew can either manually fly the descent rate or use part or full automation to maintain the rate of descent. A common method is to use the Vertical Speed (V/S) function on the MCP.

It is important to understand that the VBI has nothing to do with VNAV. The VBI takes the raw distance between the aircraft and a selected altitude point and calculates a vertical bearing to that point. If that point is part of a route in the CDU, then the next altitude constraint will be displayed, unless the user changes this.

Accessing the VBI

Navigate to Descent page on the CDU by pressing the DES key.

At lower right hand side of the DES page you will see the following: FPA, V/B, V/S. This is the Vertical Bearing Indicator.

Key RSK3 (right line select 3) allows manual entry of a waypoint and altitude or altitude restriction. Type the waypoint and altitude separated by a / slash symbol into the scratchpad of the CDU and upload to the correct line. (for example, MHBWM/200).

The VBI provides three fields:

FPA (Flight Path Angle). This is the vertical path in degrees (angle of descent) that the aircraft is currently flying.
V/B (Vertical Bearing). This is the computed vertical path in degrees that the aircraft SHOULD be flying to reach the CDU waypoint or altitude restriction.
V/S (Vertical Speed). This is the vertical bearing (V/B) converted into a vertical speed (RoD) for easy input into the MCP. The V/S is the vertical speed (RoD in feet per minute) required to achieve the displayed vertical bearing (VB).

Observe the vertical bearing. The idle descent in a 737 is roughly 3.0 degrees. Wait until the V/B moves between 2.7 and 3.0 degrees (or whatever descent angle you require based upon your approach constraints) and note the descent rate (V/S). At its simplest level, the V/S can be entered directly into the MCP and is the rate of descent required to achieve the computed vertical path.

If using automation, it will attempt to follow the vertical bearing calculated and displayed on the CDU. For example, if a VNAV descent is activated before the Top of descent (ToD) is reached, the Flight Management System (FMS) commands a 1250 fpm descent rate until the displayed V/B is captured. This is done while maintaining a VNAV connection.

Important Points:

The VBI can be used for any waypoint, fix and altitude and acts in conjunction with the AFDS
The vertical bearing when the aircraft is on final approach calculates data from the Final Approach Fix (FAF) to the runway threshold.

To read an earlier post concerning the Vertical Bearing Indicator.

737-800 Altitude Range Arc and Vertical Deviation Scale and Pointer

Other Approach Aids

Altitude Range Arc (ARA)

A handy feature often overlooked is the Altitude Range Arc (ARA). The ARA is a green coloured half semicircle which can be viewed on the Navigation Display (ND). The ARA indicates the approximate map position where the altitude, as set on the mode control panel is expected to be reached. Once the aircraft is well established on the vertical bearing (V/B) calculated by the CDU, the ARA semicircle should come to rest on the targeted waypoint.

Vertical Deviation Scale and Pointer (VDS)

The Vertical Deviation Scale is another feature often misunderstood. The scale can be found on the lower right hand side of the Navigation Display (ND).

The VDI will be displayed when a descent and approach profile is activated in the CDU (such as when using VNAV). However, the tool can be used to aid in correct glideslope for any type of approach (RNAV, VNAV, VOR, etc). To display the VDI, an appropriate approach be selected in the CDU; however, the flight crew fly a different type of approach without VNAV engaged).

The Vertical Deviation Scale presents the aircraft’s vertical deviation from the flight management computer’s determined descent path (vertical bearing) within +- 400 feet. It operates in a similar way to the Glideslope Deviation Scale on the Instrument Landing System (ILS).

The VDS is a solid white-coloured vertical line with three smaller horizontal lines at the upper, lower and middle section, on which a travelling magenta-coloured diamond is superimposed. The middle horizontal line represents the aircraft’s position and the travelling diamond represents the vertical bearing (V/B).

When the aircraft is within +- 400 feet of the vertical bearing the diamond will begin to move, indicating whether you are above, below or on the V/B target. When the aircraft is on target (middle horizontal line) with the indicated vertical bearing, the FMA will annunciate IDLE thrust mode followed by THR HLD as the aircraft pitches downwards to maintain the V/B.

In some literature this tool is referred to as the Vertical Track Indicator (VTI).

Vertical Development (VERT DEV)

The Vertical Development (VERT DEV) is the numerical equivalent of the vertical deviation scale and is found on the Descent Page of the CDU. The VERT DEV allows a flight crew to cross check against the VBI in addition to obtaining an accurate measurement in feet above or below the targeted vertical bearing. The VERT DEV will display HI or LO prefixed by a number which is the feet the aircraft is above or below the desired glideslope.

The Vertical Deviation Scale and pointer (VDS) will remain visible on the Navigation Display (ND) throughout the approach, and in association with the Vertical Development display on the CDU are important aids to use for Non Precision Approaches (NPA).

Final Call

The traditional method of a step down approach, which was the mainstay used in the 1970s has evolved with the use of computer systems and GPS. In the 1980s RNAV (area navigation) approaches with point to point trajectories began to be used, and in the 1990s these approach procedures were further enhanced with the use of Required Navigational Performance (RNP) in which an aircraft is able to fly the RNAV approach trajectory and meet specified Actual Navigation Performance (ANP) and RNP criteria. From the 1990s onward with the advent of GPS, the method that non precision approaches are flown has allowed full implementation of the RNP concept with a high degree of accuracy.

Although the nature of non precision approaches has evolved to that of a 'precision-like' approach with a constant descent angle, their are operators that widely use these techniques, despite their flaws, weaknesses and drawbacks. Even if modern navigational concepts are used in conjunction with traditional methods, aids such as the VBI, ASR and VDI should not be overlooked. Appropriate cross checking of the data supplied by these aids provides an added safety envelope and avoids having to remember, calculate and rely on ‘back of the envelope’ calculations.

The flight crew landing in Canberra, Australia did not use all the available aids at their disposal. If they had, the loss of vertical situational awareness may not have occurred.

Abbreviations

ANP - Actual Navigation Performance
ARA - Altitude Range Arc
CDU – Control Display Unit (used by the flight crew to interface the with the FMC)
FAF - Final Approach Fix
FMS – Flight Management System
FMA – Flight Mode Annunciation
FMC – Flight Management Computer (connects to two CDU units)
ILS – Instrument Landing System
KIAS - Knots Indicated Air Speed
MAP - Missed Approach Point
MCP – Mode Control Panel
ND – Navigation Display
NPA – Non Precision Approach
RoD – Rate of Descent
RNP - Required Navigation Performance
RNAV - Area Navigation
ToD – Top of Descent
V/B – Vertical Bearing
VBI – Vertical Bearing Indicator
V/S – Vertical Speed
VDS – Vertical Deviation Scale and pointer (also called Vertical Track Indicator)
VERT DEV – Vertical Development

March 29, 2013

Reference Nav Data - CDU Functionality Explained

March 29, 2013/ Flaps 2 Approach

In past posts, I’ve documented some of the functionality of the Flight Management Computer (FMC) as displayed by the Central Control Unit (CDU). Following on with this theme, let’s look at four navigation data functions the FMC is capable of: Reference Nav Data, Nav Options, Nav Status and Nav Frequency Changes.

Before continuing, the FMC/CDU is controlled by the avionics suite you are using; whether it is ProSim737, Sim Avionics or whatever. Each avionics suite provides differing functionality; therefore, if something does not operate as indicated, it maybe a limiting factor of the avionics suite in use.

Note: This post follows standard terminology. lsk3R means line select key 3 right.

------------------------------

A: REFERENCE NAV DATA

Occasionally, you will need to cross check information and the frequency of a specific navaid.

The Reference Nav Data display is part of the Nav Data page and can be assessed by the INDEX page:

INIT REF / INDEX / NAV DATA (lsk1R)

The screen will show three available options: Enter WPT Ident, Navaid Ident and Airport Ident.

Example: Type HB into the navaid Ident. Two pages will be displayed showing all the HB Idents from the navigation database. Selection of the appropriate navaid (HB) will present a further page displaying the following information: Navaid WPT, Airport and Ident code, Latitude, Longitude, Frequency, Elevation and magnetic variance.

NOTE: If you cannot identify the ident by name use the Longitude and Latitude coordinates.

------------------------------

B: NAV OPTIONS & NAV STATUS

Following on from the Reference Nav Data page are: Nav Options and Nav Status.

Nav Options and Nav Status can be assessed two ways:

1: INIT REF/ INDEX / NAVDATA (lsk1R) / NAV OPTIONS (lsl6R)

2: PROG (progress) / NAV STATUS (lsk6R) (use when in flight)

Two consecutive pages are available: Nav Options and Nav Status. By default, Nav Status (page 2/2) is displayed. Use the PREV and NEXT PAGE keys to cycle between the two pages.

Nav Status - page 1/2

This page provides you with a list of the closest navaids including frequencies. It also indicates the currently set identifier and frequency for NAV 1 and NAV 2 (as set on the NAV 1/2 radio).

Nav Options - page 2/2

This page can be used to inhibit a particular waypoint or station. By inhibiting a navaid, it will not be able to be used by the CDU to calculate a navigation solution. By default all navaid types are activated. At crew discretion, two VOR and two DME stations can be inhibited. When you inhibit a navaid it will be removed from page 1/2 and not be visible in the Nav Status page list. The inhibited navaid will be reset when you reset the CDU.

------------------------------

C: FREQUENCY CHANGE - ALTERING THE THE CDU

In usual practice, crew will alter the navigation, communication, ADF and transponder frequency on the actual panel located in the central pedestal. However, often you may need to cross check frequencies, dial in a third frequency for positional awareness, or use a frequency from an avionics module not present in the pedestal or that is malfunctioning.

The alter Nav Data screen can be assessed by:

MENU / MAINT (lsk6R) / COM/NAV (lsk3L)

This will display a page showing all idents and frequencies currently being used.

COM 1, COM 2, NAV 1, NAV 2, ADF 1, ADF 2 AND EXPR

To alter a frequency, type into the scratch pad the frequency of the navaid and upload to the appropriate line. To upload, select and press the key to the left or right of the nominated radio. Changing a frequency in the CDU will also cause a corresponding change in the frequency of the selected radio (in the center pedestal).

Flow Route

When you work through the above four functions of the CDU, you will note that the INDEX function is always available. This allows you to easily develop a flow route as you move between the various pages. Once you know how the flow route operates, you will discover that the CDU is very much like a book with several hundred pages of information that is easily accessible via a few select menu keys.

As with all my posts, if you discover a discrepancy please contact me so it can be rectified.

BELOW: Montage of images from the CDU showing various pages displayed within the Reference Nav Data. CDU is manufactured by Flight Deck Solutions (FDS). Click image to see larger.

Montage of images from the CDU showing various pages displayed within the Reference Nav Data. CDU is manufactured by Flight Deck Solutions (FDS)

September 20, 2012

Creating Waypoints on the Fly with the CDU

September 20, 2012/ Flaps 2 Approach

Often you need to inject into the flight plan a Place Bearing Waypoint or an Along Track Waypoint. There are several ways to do this with each method being similar, but used in differing circumstances. Depending upon the FMC software in use, either the LEGS or the FIX page is used.

A Place Bearing Waypoint (PBW) is a waypoint along a defined bearing (radial) that is created at a specified distance from a known waypoint or navigation aid (navaid). A PBW is used to create a waypoint that is not in the active route.

An Along Track Waypoint (ATW) is a waypoint inserted into a route that falls either before or after a known waypoint or navaid.

Although the PBW and ATW are similar, they are used in differing circumstances.

In the following examples I will use the waypoint TETRA as an example. TETRA is a waypoint near Narita, Japan (RJAA).

Creating a Place Bearing Waypoint

Type into the scratchpad the waypoint name, bearing and distance.
For example, type into the scratchpad a TETRA340/10. TETRA is the waypoint that we want to create the new waypoint from. This is called an anchor waypoint. 340 is the bearing in degrees from the anchor waypoint that the new waypoint will be generated. 10 is the distance in nautical miles from the anchor waypoint that the waypoint will be generated at.
Up-select TETRA340/10 to the LEGS page.
Press EXECUTE.

To insert the waypoint before the anchor waypoint use the negative key (TETRA340/-10). Do not use the negative symbol if you want to insert the waypoint after the anchor waypoint (TETRA340/10). Take note that the slash (/) is after the bearing and the waypoint name and vector are joined with no spaces.

Creating an Along Track Waypoint

Type into the scratchpad the waypoint or navaid that will be used as an anchor waypoint.
Up-select this into the correct line of the route in the LEGS page.
Press EXECUTE.

Important Points:

If the waypoint is already part of the route, it is not necessary to type the identifier in to the scratchpad. Rather, press the appropriate Line Select Key adjacent to the identifier (in the LEGS page) to down select to the scratchpad. Then add the /-10 or /20 after the identifier and up-select. Using this method eliminates the possibility of typing the incorrect identifier into the scratchpad.

The FMC software will generate subsequent waypoints with a generic name and numerical sequence identifier. For example, TETRA, TETRA01, TETRA02, TETRA03.

Creating a Circle around a Waypoint using the FIX Functionality

The purpose of creating a circle (ring) around a point in space is to increase spatial awareness when looking at the Navigation Display (ND). A circle at a set distance may be used to define the Missed Approach Altitude (MAA), the distance from the runway threshold that the landing gear should be lowered, or to designate an important waypoint.

I nearly always use two or three circles depending upon the approach being executed. One circle will be at 12 miles while the second circle will be at 7 miles. The use of circles can be very helpful when flying a circle-to-land approach; one circle will define the MAA and the other circle will define the 'protected area' surrounding an airport.

To create a circle (ring) around a known point

Press FIX on the CDU to open the FIX page.
Type into the scratchpad, the name of the waypoint or navigation aid (VOR, NDB, etc). For example TETRA.
Up-select this to the FIX page (LSK1L).

This will display a small circle around the identifier in the Navigation Display in green-dashed lines.

If you want the circle to be at a specific distance from the point in question.

Type into the scratchpad the distance you require the circle to be drawn around the waypoint. For example /5.
Up-select this to the FIX page (LSL2L).

To add additional circles around the selected point, repeat the process using different distances and up-select to the next line in the FIX page.

Important Point:

A quick way to insert a waypoint from a route into the FIX page is to press the waypoint name in the LEGS page. This will down select the waypoint to the scratchpad saving you the time typing the name and removing the possibility of typing the incorrect letters. Up-select to the FIX page.

Creating a Single Along Track Waypoint (at the edge of the circle)

One or more waypoints can be created anywhere along the circumference of the circle (discussed earlier) by inserting a bearing and distance into the FMC page.

To create a waypoint at the edge of the circle

Create a circle around a point as discussed earlier (TETRA).

Type in the scratchpad the bearing and distance that you wish the new waypoint to be created (for example 145/5).
Up-select this information to the FIX page (LSK2L). This will place a green-coloured line on the 145 degree radial from the waypoint (TETRA) that intersects a circle at 5 miles on the ND.
Next, select the 145/5 entry from the FIX page (press LSK2L). This will copy the information to the scratchpad. Note the custom-generated name – TETRA145/5.
Open the LEGS page and up-select the copied information to the route. Note that TETRA145/5 will now have an amended name – TET01.
Copy TET01 to the scratchpad.
Open a new FIX page (there are 6 FIX pages that can be used). Up-select TET01 to the FIX page (LKL1L). This will create a small circle around TET01 on the ND.
To remove the waypoint (TET01) from the route (if desired), open the LEGS page and delete the entry. If desired, the waypoint can easily be added again to the route from the FIX page.

The above appears very convoluted, however once practiced a few times it becomes straightforward. There is a less convoluted way to do this, however, the method is not supported by ProSim737.

Inserting an Additional Along Track Waypoint around the Arc of the Circle (DME Arc)

A DME arc is a series of Along Track Waypoints that have been created along an arc at a set distance from the runway (waypoint or navigation fix). This is often used when flying a NDB Approach.

Usually, the arc begins on the same bearing as the navigation track of the aircraft, and ends a set point, usually at the turn from base to final. Subsequent bearings after the initial bearing are at a 30 degree spacing.

To create a DME Arc

First, ensure you have a circle created around the waypoint (TETRA) at the distance required (FIX page).

Select the anchor waypoint (TETRA) for the arc from the LEGS page and down select it to the scratchpad.
Type into scratchpad after TETRA (as separate entries) the bearing and distance. For example: TETRA200/5, TETRA230/5, TETRA260/5, TETRA290/5 TETRA320/5 and so forth. Note the bearings differ by 30 degrees. This creates the arc.
Up-select each of the above entries to the route in the LEGS page (after the anchor waypoint TETRA).

This will create an arc 5 miles from TETRA.

If you want the first waypoint to be along your navigation track, use the bearing for this initial waypoint as indicated in the LEGS page of the CDU.

The FIX page can also be used to create an arc using the same technique. Using the FIX page will enable the arc to be seen on the ND, but not form part of the route.

Important Point:

It is important to note that user and along track waypoints are given a generic name and numerical sequence identifier by the FMC software (TETRA01, TETRA02. TETRA03, etc).

Understanding the CDU

What I have described above is but a very brief and basic overview of some functions that are easily performed by the CDU.

CDU operation can appear to be a complicated and convoluted procedure to the uninitiated. However, with a little trail and error you will soon discover a multitude of uses. It is important to remember, that there are often several ways to achieve the same outcome, and available procedures depend on which FMC software is in use.

I am not a professional writer, and documenting CDU procedures that is easily understood is challenging. If this information interests you, I strongly recommend you purchase the FMC Guide written by Bill Bulfer. Failing this, navigate to the video section of this website to view FMC tutorials.

Navigation display showing map view. Left to right.
**image 1:** 5 mile ring surrounding TETRA.
**image 2**: 2 and 5 mile ring surrounding TETRA.
**image 3:** 5 mile ring surrounding TETRA showing PBW on circumference TET01.
**image 4:** DME arc along circumference of 5 mile ring surrounding TETRA.

Acronyms

Anchor Waypoint – The waypoint from which additional waypoints are created from.

Bearing – Vector or radial.

CDU – Control Display Unit.

FMC – Flight Management Computer.

ND – Navigation Display.

Target Waypoint – The waypoint that has been generated as a sibling of the Anchor waypoint.

Waypoint – Navigation fix, usually an airport, VOR, NDB or similar.

Updated 05 June 2022.

download article

July 23, 2012

Vertical Bearing Indicator (VBI) - How To Calculate A Controlled Idle Descent

July 23, 2012/ Flaps 2 Approach

vertical bearing indicator (vbi) displayed on reproduction cdu manufactured by flight deck solutions (fds)

Often you are requested by ATC to alter altitude, or must intercept a desired point in space at a certain altitude for operational reasons. There are several methods available to the pilot to initiate the change in altitude; outlined below are three methods.

A: Initiating Level Change or Vertical Speed on the MCP will activate an advancing and contracting green line arc (Altitude Prediction Line) on the CDU. This green arc identifies the location that the aircraft will reach ,if the vertical speed is maintained, in relation to the active CDU waypoint.

B: You can calculate the distance and vertical descent using mathematics, but this can be cumbersome and may illicit possible mistakes.

C: You can alter the LEGS page of the CDU keying in the new altitude constraints (this assumes you are using VNAV & LNAV.

The CDU Vertical Bearing Indicator (VBI) can help you. The VBI is basically an angle calculator that provides "live" vertical speed information based upon a desired descent angle. An example using the waypoint TESSI is provided.

Navigate to Descent page by pressing the DES key.
At lower right hand side of the DES page you will see the following: FPA, V/B, V/S. This is the Vertical Bearing Indicator.
Key RSK3 (right line select 3) and enter the waypoint and altitude (TESSI/17000)

The VBI provides 3 fields:

FPA (Flight Plan Angle) is the vertical path in degrees that the aircraft is currently flying.
V/B (Vertical Bearing) is the vertical path in degrees that the aircraft SHOULD be flying to reach the keyed waypoint (TESSI/17000).
V/S (Vertical Speed) is the vertical bearing (V/B) converted into vertical speed for easy input into the MCP.

Observe the V/B. The idle descent in a 737 is roughly 3.0 degrees (PMDG use 2.7 degrees)

Wait until the V/B moves between 2.7 and 3.0 degrees (or whatever descent angle you require)

When the value is reached, dial in the required altitude and indicated Vertical Speed on the MCP

The Altitude Prediction Line will now intersect the selected waypoint (TESSI) and the aircraft should fly a perfect idle descent to TESSI. Note that the original altitude selected for the pinpoint in the LEGS page does not reflect the new change.

Benefits

One of the advantages in using the Vertical Descent Indicator is that the pilot can instigate an accurate controlled idle descent, following a desired glide path to the desired waypoint. This advantage can be used in a number of scenarios:

Descent from cruise altitude.
Approaching the runway from a straight-in approach course.
Approach the runway from base or via an ARC approach.
Approaching the runway for a downwind approach.

I often use the VBI from FL10 to FAF on approach, when other constraints are not required.

Video

I’ve made a short video showing the procedure.

In the video, TESSI has been selected from the LEGS page and downloaded to the scratchpad. Pressing DES opens the required page where the VBI resides. In the scratchpad, the altitude constraint is entered for the waypoint – TESSI/17000 and uploaded to the WPT / ALT section of the Vertical Bearing Indicator (right line select 3).

If you watch the indicator you will see the V/B and V/S changing as the aircraft approaches TESSI.

Select the new altitude and vertical speed on the MCP (17000 & 780 - or nearest numeral) and you will note the FPA begins to change, indicating the new vertical path of the aircraft. The Navigation Display (ND) will then show the Altitude Projection Line moving towards and stopping at TESSI. The aircraft will now descend at the nominated angle of descent until reaching TESSI. Note that the original altitude in the LEGS page does not reflect the new change.

To read another article on the Vertical Bearing Indicator.

February 09, 2012

FMC Guide by Bill Bulfer - Review

February 09, 2012/ Flaps 2 Approach

The Control Display Unit (CDU) is the pilot interface to the FMC (Flight Management Computer). It’s one of the more complex items that real and virtual aviators need to the master.

Historical Context

First introduced on the 737-200 in 1979 as the Performance Data Computer System (PDCS), the Flight Management Computer (FMC) was a technological step forward in in-flight navigation The PDCS was trailed on two in-service 737-200 series aircraft and crew reports indicated a fuel saving of 2.95% and an increase in trip time (based on a 71 minute trip). As a result, the PDCS became a standard fit and over time was developed to be reincarnated as the FMC will see today in the later 737 series aircraft.

The FMC is only one component of the Flight Management System (FMS) which is defined as being capable of four dimensional area navigation (latitude, longitude, altitude & time). The FMS contains the navigational database.

Learning CDU Functionality can be Frustrating if not Adequately Trained

Many virtual aviators blunder through the CDU line detents trying to understand what they do; often failing. For the most part, the uninitiated will blame buggy software for the aircraft’s sudden dive or climb in response to a CDU command. The algorithm behind the functionality of a CDU is not simplistic – it is complex, and mastering the CDU is not achieved overnight.

Real-world pilots attend lengthy pre-flight classes to understand the use of the CDU, and although there are several training guides available on the Internet, many are not peer-reviewed and fall short of being comprehensive.

Software Variations

One of the reasons that learning the CDU can be tiresome, is that the software that provides the intelligence behind the Flight Management System, has over time been upgraded to take into account technological advances. This is in addition to there being several software variants available. Software variants have been developed to cater towards individual airline options; an airline may want, or not want a particular function available to its flight crews.

Precision Manual Development Group (PMDG) produces a very good section in one of their manuals that deals with CDU usage (PMDG 737 FMC Guide). Tom Metzinger and Fred Clausen have also documented in their excellent tutorials, a segment on using the PMDG style variant CDU (PMDG use the latest software version). I suggest googling on the Internet to see if you can find these documents.

Invest in Education - FMC Guide

If you are serious about your virtual flying or have a bent for technology, I strongly recommend you purchase Captain Bill Bulfer’s FMC Guide.

The guide is a real-world guide designed for 737 pilots, and not only provides detailed information on a vast array of FMC commands, screens and nuances, but also examines many of the options relating to specific software versions.

The guide is a high quality production and has been written in a style that provides clear and a concise guidance. It can be purchased either in colour (recommended) or in black and white.

Like anything in life, you get out what you put in. With a good working knowledge gained from the study of this text, you will soon discover that the carrying out a procedural turn with altitude and speed restrictions, before flying a complex STAR and approach is not that difficult to fathom.

The information in this guide will allow you to be confidently and correctly operate the CDU.

To purchase a copy you can either navigate to Leading Edge Publishing.

I will be reviewing another of Bill Bulfer's text in the near future - The 737 Cockpit Companion.

My Rating 10/10

Please note that this review is not endorsed.

February 03, 2012

CDU by Flight Deck Solutions - Review

February 03, 2012/ Flaps 2 Approach

The Control Display Unit (CDU) is the pilot interface to the Flight Management Computer (FMC). The FMC integrates with the Flight Management System (FMS) of the aircraft. The FMS contains the navigational database.

Historical Context

The first true FMC was introduced in 1984 with the release of the Boeing 737-300. In its most basic description, the FMC can be described as a computer that can store flight and navigation data and perform detailed and comprehensive assessments of the stored data, providing the pilot with up date information that is relative to safe and accurate flight.

Flight Management Computer (FMC) & Control Display Unit (CDU)

The CDU interface enables the flight crew to interact with the FMC and FMS to access, amougst other things: the navigational database, autopilot, flight director, auto-throttle and internal reference system (IRS).

An aircraft will only have one CDU installed, however, dependent upon company regulations, air safety and routing (flying over water), many operators will have two CDU units installed for redundancy and independent use by the Captain and First Officer. Think of the CDU as a keyboard to the FMC which in turn is a component of the FMS.

This said, the acronyms CDU and FMC are often used interchangeable in aviation parlance.

Flight Management System (FMS)

The FMS is an integrated system of which the FMC and CDU is just one component. The FMS is capable of four dimensional area navigation (latitude, longitude, altitude & time) while optimizing performance to achieve the most economical flight possible.

The FMS stores the navigation database and route information which the autopilot will fly when in LNAV mode. When given data such as YMHB & KSEA, it takes inputs from the fuel summation unit to give a gross weight and best speeds for take off, climb, cruise, descent, holding, approach, etc. These speeds can all be flown directly by the autopilot & auto-throttle in VNAV mode.

Flight Deck Solution's PRO Mx CDU

The CDU manufactured by Flight Deck Solutions (FDS) is an outstanding piece of simulation engineering. The unit is well built, solid, and replicates a real B737 style CDU 1:1.

The CDU body and bezel (front plate) is manufactured from high grade metal while the rear section that houses the electronics is plastic. A USB and VGA cable connects to the video card output on the computer. The connections to the cable are located on the rear of the unit allowing easy connectivity to the computer. The CDU has been painted in the correct Boeing grey colour and the paint has been applied professionally in several thin layers; the paint does not chip or wear off with use. Importantly, for those using genuine aviation parts, the unit is DZUS complaint and drops into the rails in the CDU bay with perfect precision. FDS includes four DZUS fasteners to allow connection to the rails.

High Fidelity Dimable Keyboard

The keyboard used in the CDU is made from high definition injection-molded plastic and the keys are dimpled and back-lit. The keys are very tactile and when depressed an audible click is heard ensuring you know the key has been depressed.

For night operations, the unit has a knob that can be rotated to dim the back-lighting brightness level of the keys. A functional metal carry bracket, that folds out from the edge of the bezel is also included. This replicates the carry handle on the real CDU.

Functionality - Software (Sim Avionics & ProSim737)

It is important to understand that the functionality of the CDU is not generated by software that comes bundled with the unit, but by the avionics suite you have chosen to use. Therefore, I have chosen not to discuss the various options that each software suite may or may not replicate. In the real world, airline companies have the opportunity to purchase specific options they believe are relevant to their flight operations. This said, many of the variations have been replicated in both software suites.

I have used the CDU with Sim Avionics and ProSim737; both software suites provide excellent functionality and work flawlessly with the unit.

The CDU is used throughout a flight; therefore, reliability is expected. The solid construction of the FDS CDU has not let me down and after endless pressing on keys they still function as you would expect them to.

The CDU at night showing only illumination from the unit. The backlighting is adjustable and able to be dimmed by turning the dim knob on the unit

Navigation Database

The unit does not ship with navigation data included. The navigational database which includes STARS and SIDS, Runways, airports must be purchased separately from Navigraph and then installed into your avionics software suite. Download and installation of the database is very easy and most of the installation is automated.

WOW Factor

The best feature of the CDU I have left to last – the display. 'WOW' is the only word to describe the display.

The display is a colour VGA display unit sporting 800 x 600 resolution. What this means is that the script on the display is VERY clean, VERY readable and VERY sharp. Being a colour display means that differing colours (white, green and magenta) can be used for the fonts that your avionics software generates. The use of colour helps distinguish between functions that are activated or in stand-by mode, not to mention enhancing the units display readability.

The display is equally distinguishable in full daylight and in darkness and does not exhibit screen cut off when viewed at an angle (as some laptop screens are prone).

Configuring the CDU

Configuring the CDU using Sim Avionics was relatively painless. You must designate which CDU you are installing (Captain, First Officer or Instructor), edit a few lines in the .ini file to ensure it recognises the correct CDU, and configure the display location. The only teething issue I had was ensuring that the monitor display window size was correctly positioned on the screen for the location of the CDU. It took quite a few attempts to get the position 'just right'.

The set-up with ProSim737 is equally straightforward, however, to ensure correct operation you must install and enable additional software supplied by ProSim737. Installing and initiating the software is relatively straightforward, however, it's important to follow the provided instructions to ensure trouble free operation.

Manual and Tuition

A manual explaining the functions of the CDU and/or tutorial is not included. In my opinion, FDS should develop a video tutorial that runs you through the basic functions of the unit including a simulated flight. This said, there are several dozen excellent tutorials that can be found on U-Tube that provide basic and advanced CDU use.

When you purchase the CDU a basic manual explaining the installation and set-up procedure is included..

The FMC Guide written and sold by Bill Bulfer is strongly recommended as this guide provides basic and advanced tuition in how to use the CDU. A review of the FMC Guide can be read here.

I cannot fault the CDU unit manufactured by Flight Deck Solutions and believe it to arguably be the best piece of reproduction hardware currently available.

Additional photographs of the Flight Deck Solutions CDU can been viewed in the image gallery.

My Rating 10/10

Please note that this review is not endorsed by Flight Deck Solutions (FDS) or by any other reseller.

A short video depicting some of the more commonly used keystrokes of the Flight Deck Solutions CDU. No particular key sequence has been followed. The video is to demonstrate the screen resolution and the uptake speed after depressing a key. Double click video to view full screen. Note that this video was produced using Sim Avionics software suite. ProSim737 software provides slightly different options.

Update

on 2016-01-10 23:27 by FLAPS 2 APPROACH

The CDU was purchased in February 2012 and has seen solid use to January 2016 in both Sim Avionics and ProSim-AR avionics suites. During this time, the unit has worked perfectly.

For any reproduction item to operate over a four year period without any problems, can only support my view that Flight Deck Solutions (FDS) produces high quality hardware that has not been designed to fail after a short period of time.