Flight Sim Live Traffic Liveries (FSLTL) - Short Review

View fullsize

FSLTL ANA and JAL at Toyama (RJNT), Japan

Those who have used flight simulator for many years will recall the days when you flew alone, with no other aircraft except a few poorly defined airliners, or a Cessna or two parked at the airport. Flight simulator has come a long way since then, and today it’s possible to fly on-line with several other user-piloted aircraft, or at the very least have several well-made AI (artificial intelligence) aircraft in the sky around you.

As simulator AI evolved, so did the number of AI programs and add-ons that were available, with some packages providing real world airline schedules and user adjustable aircraft liveries. Needless to say as AI grew, so did the complexity in installing and running these programs. Unless you enjoy the complexities of software, I dare say that you want an AI package that works, is easy to use, and runs in the background, allowing you to fly the simulator and not continually have to tinker with AI. FSLTL is such a program.

This is a short review, meaning I am not going to delve into the intricacies of FSLTL. The developer has included a very easy to understand manual and a video; to rehash what is already written in the manual is counter productive to the product.

General

FSLTL (Flight Sim Live Traffic Liveries) is a free, easily configurable AI program that can be turned on or off at will and runs in the background. The program is VATSIM compliant and interacts with the default Air Traffic Control in MSFS-2020 and AI Air Traffic Control programs, such as Beyond ATC and Say Intentions.

FSLTL does not use imaginary flight schedules. Rather, it extrapolates flight data from FlightRadar 24 (FR24) and replicates these flights in flight simulator using the appropriate aircraft types and liveries. Therefore, when you see an airbus A380 taking off from Adelaide International (YPAD) the AI is reflecting the actual flight schedule of the real airline. The real time flight information from FR24 is pinged every 20 seconds so the replication is not exactly real time, but it is very close.

Although there is no reason to use other AI traffic, FSLTL has the capability to also incorporate AI aircraft models and liveries from third party providers (for example, Just Traffic). The aircraft type and liveries used by FSLTL come from a variety of sources with FAIB (FSX AI Bureau) creating many of the models and liveries.

FSLTL is updated from time to time with new aircraft and liveries.

Installation

Installation of the program is very straightforward. An installer (Fly-By-Wire installer) is downloaded to your computer from the FSLTL website. After running the installer, you select the components you want to use. You will need the Traffic Injector and the Traffic Base Models package. The base model package is quite large; therefore, be certain there is appropriate space in your computer to store the files. Both the traffic injector and base model package must be installed into the community folder of MSFS-2020. If you wish to install these items outside of the community folder then this can be done; however. the files will need to be linked to the community folder using a program such as MSFS add-ons linker.

Important Point:

• FSLTL uses simconnect. At a minimum, VC++ Redist 2015-2022 x64 must be installed on your computer.

View fullsize

FSLTL Traffic Injector User Interface

Traffic Injector and User Interface (UI)

The traffic injector is the .exe file that starts FSLTL and injects the traffic into flight simulator. A shortcut can be made to this file and stored anywhere you wish: on your desktop, in the menu bar, or it be added to a batch file to automatically load when flight simulator is started. The base models package is only a folder with the various models. It requires nothing be done to it other than placing the folder in the correct location.

The traffic injector user interface (UI) can be accessed either by selecting the icon from the inflight menu system in MSFS-2020, or as discussed by a standalone .exe icon. Opening the User Interface enables the user, amongst other things, to streamline the program and control the number of aircraft being spawned at any one time, either in the air or on the ground. The UI also can re-spawn AI aircraft, set the distance that AI aircraft can be spawned, or remove AI aircraft during the final landing phase. This can be beneficial when landing in airports that have high density traffic.

In my simulator, I have the FSLTL .exe icon in the menu bar. After loading flight simulator and ProSim737, I click the icon and within 1 minute AI traffic has been spawned.

View fullsize

File structure to open the preference panel for FSLTL

Traffic Injector Preferences

The traffic injector user interface can be changed to suit individual preferences. This is done by opening the user interface configuration file located at %APPDATA%\ fsltl-traffic-injector and selecting the fsltl-trafficinjector-config.json file. The .json file can be opened in a text editor by right clicking the file. Once the file is open you will note the various preferences that can be changed and saved.

Frame Rates and Resources

With normal use, with the exception of hard drive space to store the base models package, FSLTL uses minimal computer resources and does not affect frame rates. If you decide to have the maximum number of aircraft at an airport, in flight at varying distances, and also use other third party AI traffic, then there is a slight hit to frame rates.

Aircraft Types and Liveries

FSLTL AI aircraft have been built using glTF models for better performance, reduced stutters, and CTD avoidance. Apart from the visual appeal of looking at a well constructed model, this improves AI ground roll during take-off and landing. it also enables the display of custom lighting, contrails, heat haze and other effects, including interaction with jetways and ground services.

The base model package includes over 1900 liveries and includes all major airline aircraft types and light aircraft. At the time of writing, military aircraft and helicopters are not included.

Downsides and Known Issues

There are several known limitations with MSFS-2020 that can cause issues with AI traffic. Thankfully, none of these shortfalls relate to resource usage and frame rates. FSLTL have listed the known issues in their on-line manual.

Pink Liveries

One particular problem that did occur to me, was that several AI models were displayed as checkered designs or were coloured hot pink (rather than the correct airline livery). Whenever this occurs, it is an indication of a problem concerning the aircraft’s texture folder, or the file has been corrupted.

In my case, the problem was that the aircraft type in question (the Beechcraft King Air) was not installed into MSFS-2020. In an effort to streamline my set-up, I had deleted various aircraft types and models that I did not use. Once I reinstalled the King Air aircraft type (not the various liveries) using the content manager, the pink colours disappeared and I was presented with the correct livery (in this case a Royal Flying Doctor Service livery).

If this issue persists, and you have the aircraft types installed into MSFS-2020, the next step is to determine where the problem lies. It is relativity easy to troubleshoot this problem.

1. Open MSFS-2020 in developer mode.

2. Navigate to the debug/console tab (at the top of the screen).

3. Open console and check through the various listings.

You are searching for any listings which have been tagged in yellow. As you scroll through the listings, you will eventually find the aircraft type that you noticed the problem with (checkered design or hot pink colour). This is the aircraft file that potentially has a corrupted texture file. Note the aircraft type, and then navigate to the MSFS-2020 file structure (msfs/Official/OneStore/Asobo Aircraft folders/SimObject/Airplanes/aircraft folder in question/Textures).

Open the Asobo aircraft files and scroll through the listings until you find the folder that contains the files for the aircraft in question. Open the aircraft folder and check that the appropriate texture files are included. Each aircraft should have a number of texture folders. For example, texture, texture01, texture02 and texture03. Sometimes the texture folder (no number) is missing. If this is the case, delete the aircraft folder, run MSFS-2020 and allow the program to reinstall the aircraft from the cloud. This should resolve the problem.

Final Call

I have used this program since I began using MSFS-2020. Previously, I used a number of payware AI programs which always seemed to require me to tweak or tinker with airline schedules. These programs also had a relatively steep learning curve. FSLTL works out of the box and does exactly what it says it will do, with minimal fuss - and it will cost you nothing other than a donation to the developer if you like the program.

• FS Live Traffic Liveries (FSLTL).

Scale ID Annunciation (RW/APP CRS Error)

View fullsize

Scale ID Annunciation display in upper left hand corner of the Primary Flight Display

The Scale ID annunciation (often called the approach reference), displayed in the upper left of the Primary Flight Display (PFD), is one of a suite of displays that comprise the PFD Navigation Performance Scales (NPS) Indications. 

In the image a runway approach course error (RW/APP CRS Error) is being displayed.  The airport is Hobart, Tasmania and the ILS approach is to runway 12.  The error has been generated because the CRS window in the MCP has the incorrect approach course (140 degrees).  If the approach course was correct, the display would be coloured white - not amber with a strike-through line.

The Scale ID Annunciation display provides, the for the selected approach type, the following approach reference information:

• Airport identifier;

• Runway approach course;

• Distance to the runway threshold; and,

• Approach type.

The display also indicates whether a runway approach course error (RW/APP CRS) has occurred.

Possible approach type displays include:

• LNAV/VNAV (LNAV and VNAV deviations).

• LOC/VNAV (Localiser with VNAV deviation).

• FAC/VNAV (IAN final approach course with VNAV deviation).

• LNAV/G/S (LNAV deviation and glideslope).

• LNAV G/P (LNAV deviation with IAN glidepath).

• ILS (ILS approach).

• FMC (IAN approach).

• GLS (GLS approach).

Airport Identifier and Display Colour

The airport identifier comprises the identifier and airport name (abbreviated).  The identifier will change depending upon the approach type.  For an ILS (and IAN approach) the identifier will be the letter I followed by the airport abbreviation.  For example, Hobart airport is YMHB.  In this case for an ILS approach the airport identifier will be IHB.

The identifier is displayed in two colours: white and amber; amber being cautionary.  The later also incorporates a strike-through line (this line dissects the airport identifier and approach course).

White indicates that all the parameters required for the approach have been completed correctly.  An amber colour/strike-through indicates that one or more of the required parameters have not been met.

Colour Combinations

The following colour combinations can be observed (further information is discussed later in the article). 

• Frequency and approach course displayed in white:

When the navigation radio is tuned to the ILS frequency, the identifier will initially display the ILS frequency (109.90) for the approach.  The frequency will then change to display the airport identifier (IHB).  Whether the colour displayed remains white or changes to amber will depend on whether both navigation radios and CRS course windows are set to the correct ILS approach.

If either display is coloured amber it indicates a RW/APP CRS error has occurred.

• Airport Identifier displayed in amber:

One navigation radio is tuned to the ILS frequency.  Tuning the second radio to the same frequency will cause the display to change from amber to white.

• Approach course displayed in amber:

One or both courses in the CRS course windows (MCP) is not set to the correct ILS approach course.

• DME and approach type:

The DME and approach type (ILS) are always displayed in white.  The DME will display the distance to the runway when the glideslope is captured by the aircraft.

Pre-Approach Tasks

Prior to commencing an approach, the following should be carried out:

• The correct frequency entered into to the navigation radios (NAV 1 & NAV 2);

• The correct approach course (for the runway selected) entered into the Captain and First Officer side CRS course windows in the MCP;

• An appropriate approach selected from the FMS database (depends on the approach type being used); and,

• The approach course for the runway entered into the heading window in the MCP.

Delay

The logic controlling the scale ID annunciation periodically interrogates that data entered into the navigation radios and MCP.  This means that a delay is often observed between the annunciation changing colour from white to amber or back again.  I am unsure of the timing.

Discussion

The indication that a RW/AP CRS error has been triggered doesn’t alwasy preclude an approach from being carried out (although it’s not recommended).  The annunciation indicates that, for the selected approach, something hasn’t been completed with regard to the configuration of the avionics.  It's rarely the case that the frequency hasn't been correctly entered into to the navigation radio; more often than not the cause of the annunciation is a CRS course discrepancy, or failure to configure the second navigation radio to the same frequency as the controlling navigation radio.   

Using the ILS approach as an example.  To correctly configure the instruments for an ILS approach and not receive a cautionary warning, the following must be completed:

• Enter the correct ILS frequency into the BOTH navigation radios; and

• Enter the correct approach course into BOTH the CRS course windows in the MCP.

It’s also recommended, but not mandatory to:

• Enter the approach course into the heading window in the MCP; and

• Enter an appropriate approach into the CDU/FMC.

If you enter the ILS frequency into the controlling navigation radio, and enter a different frequency into the other navigation radio, an amber-coloured RW/APP CRS annunciation will be generated.  Likewise, a caution will occur if the Captain-side and First Officer side CRS windows don’t display the identical ILS approach course.

View fullsize

IMAGE A-1: ILS approach into runway 12 for Hobart, Tasmania (IHB).  The approach course for this approach is 120 degrees.  The controlling navigation radio (Captain-side/not shown) has been set to the correct ILS frequency (109.90).  The heading that the aircraft is flying is 120 degrees, and the compass rose is offset to the course direction that is displayed in the Captain-side CRS window (140 degrees)

Example (Hobart, Tasmania IHB)

Image A-1 shows an ILS approach into runway 12 for Hobart, Tasmania (IHB).  The approach course for this approach is 120 degrees.  The controlling navigation radio (Captain-side/not shown) has been set to the correct ILS frequency (109.90).  The heading that the aircraft is flying is 120 degrees, and the compass rose is offset to the course direction that is displayed in the Captain-side CRS window (140 degrees).

In the example, a RW/APP CRS annunciation has been triggered for an ILS approach.  The airport identifier and approach course are coloured amber with a strike-through line.   The DME is 9.4 miles and is coloured white (correct data).

This approach can be flown despite the discrepancy between the four courses (120, 180, 130 & 140 degrees) and a RW/APP CRS annunciation.  This is because the ILS approach course (120 degrees) is coupled to the ILS frequency set in the controlling navigation radio  – not the course as indicated in the CRS windows in the MCP. 

In the example you can see that the localiser has been captured (this is identified by the magenta-coloured course deviation line being centered/in-line with the course pointer) despite the CRS window displaying a course of 140 degrees.  Once the aircraft has captured the localizer it will fly the localiser heading no matter what course is displayed in the CRS window (provided it does not exceed 90 degrees).

While this example holds true for an ILS approach other approach types may behave differently.

Important Points:

• The scale ID annunciation is an amber-coloured display that annunciates when the avionics have not been correctly configured for the selected approach.  The display is a cautionary.

• The approach cannot be flown If the CRS course discrepancy is greater than 90 degrees from the ILS approach course.  This is because the aircraft will follow the direction of the course set in the CRS window (if greater than 90 degrees).

ProSim-TS

The ProSim737 avionics suite replicates the RW/APP CRS logic used in the real aircraft. 

Database Inconsistencies

In some instances the annunciation is displayed despite entering the correct information.  A possible reason for this is a scenery navigation database inconsistency. 

In older scenery designs the physical location of the localiser beacons was part of the scenery file and this information is what the simulator referred to.  With the advent of up-to-date navigational points (supplied by Navigraph) the simulator now refers to a navigational database rather than a scenery database.  An inconsistency will occur if there is a discrepancy between the location of the localiser beacons in the scenery and the information recorded in the navigational database.

Final Call

The RW/APP CRS annunciation, although confusing to the uninitiated, does not necessarily mean that an approach cannot be carried out.  However, it’s prudent before flying the approach to understand why the RW/APP CRS error has been displayed. 

In more cases than not, the reason for the cautionary annunciation is a failure to configure the navigation radios to the same frequency and/or enter the same ILS approach course into both the CRS course windows in the MCP.

Batch Files to Open and Close Flight Simulator

Opening and closing the various files and ancillary programs to operate a flight simulator can be onerous and time consuming.  While there have been several programs released that enable you to launch flight simulator with a press of a key, they seldom work with complicated platforms such as flight decks. 

One of the most commonly used methods to open files and programs is to use the start menu within Windows.  However, this is not without it’s shortcomings, and specialist knowledge is required.  An easy and trouble free approach is to use batch files.

What is a Batch File

A batch file is a script file that stores commands to be executed in a serial order.  It helps automate routine tasks without requiring user input or intervention. Some common applications of batch files include loading programs, running multiple processes or performing repetitive actions in a sequence in the system.

Also known as a batch job, a batch file is a text file created in Notepad or some other text editor.  A batch file bundles or packages a set of commands into a single file in serial order.  Without a batch file these commands would have to be presented one at a time to the system from a keyboard.

Usually, a batch file is created for command sequences when a user has a repetitive need.  A command-line interpreter takes the file as an input and executes the commands in the given order.  A batch file eliminates the need to retype commands, which saves the user time and helps to avoid mistakes.  It is also useful to simplify complex processes.

Windows usually uses the .bat extension for batch files.

Whilst there are several methods that can be used to write a batch file, I have found that the examples below operate flawlessly.

Writing a Batch File

It's a simple process to write a batch file. 

Prior to beginning, it’s wise to think about the order you want the programs to open, and whether you want a pause between opening particular files and programs.  While a pause is probably not necessary, it’s a good idea as it allows a file or program to complete its opening sequence, prior to the next file or program opening.

When you have completed writing the batch file in notepad save the file with a .bat extension.  To test the batch file double click on the saved .bat extension.

Although others will disagree, I always open the MSFS-2020 or P3d and allow the program to settle before opening any batch file or other programs.

The following examples of batch files are user-specific.  You will need to substitute the file structure with the file structure you are using.

Opening Files and Programs

• An example of a batch file to open the main flight simulator computer (server).

@Echo  off

//Alpha Main Server Computer (ALPHA-SERVER-P3)  - 09:38 - 25/08/2023

//ProSim738 V3

//ProSim Ancillary Programs

start /d "D:\Flight Simulator Files\SimStacks October 2021\SimStackSwitchv702" Switch.jar

Timeout 0.5

start /d "D:\Flight Simulator Files\FS Set Volume" FSSetvol.exe

Timeout 0.5

start /d "D:\Flight Simulator Files\SimSounds 4.0" SimSounds.exe

Timeout 1

start /d "D:\REX WeatherForce.exe

//ProSim Main Programs

start /d "D:\Flight Simulator Files\ProSim738 V3\ProSimAudio" ProsimAudio.exe

Timeout 1

start /d "D:\Flight Simulator Files\ProSim738 V3\ProSimB738" ProSimB738.exe

An example of a batch file to open the avionics suite on the second computer (client 1).

@Echo off

//Client 1 - ProSim-AR B738 Avionics Suite V3    14:07 5/09/20

//PS738 V3

//Ancillary Programs

start /d "C:\Users\user name\Documents\FSF\Programs\MSFS WideFS7" kilo

start /d "C:\Users\user name\Documents\FSF\Programs\Landing Rate Monitor" LRM.exe

start /d "C:\Users\user name\Documents\FSF\Programs\SimSounds 4.0" SimSounds.exe

//Hardware Connector

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\ProSimB738-HardwareConnector" ProSimB738-HardwareConnector.exe

//ProSim737 Displays and Indicators

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\Displays\CAPT PFD" ProsimDisplay.exe

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\Displays\CAPT ND" ProsimDisplay.exe

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\Displays\FO PFD" ProsimDisplay.exe

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\Displays\FO ND" ProsimDisplay.ex

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\Displays\EICAS" ProsimDisplay.exe

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\Displays\FLAPS" ProsimDisplay.exe

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\PS738ChronoCaptain" ProsimDisplay.exe

Timeout 3

start /d "C:\Users\user name\Documents\FSF\ProSim738 V3\ProSimIOS" ProSimIOS.exe

Closing Files and Programs

Likewise, you can also use a batch file to close files and programs sequentially or simultaneously (kill all).

An example of a batch file used to close programs on the main flight simulation computer (server).

@Echo off

//Alpha Main Server Computer (ALPHA-SERVER-P3)  - 09:38 - 25/08/2023

//ProSim738 V3 – closure batch

taskkill /IM wideclient.exe

Timeout  2

taskkill /IM ProSimAudio.exe

Timeout  1

taskkill /IM PMSounds.exe

Timeout 1

taskkill /IM Prosim737.exe

Timeout  4

taskkill /IM fs2020.exe

• im specifies the image name of the process to be terminated (for example, PMSounds.exe or ProSim737.exe).

• @echo on/off defines whether a name or message will be displayed on the console.  It’s also used for other tasks such a script troubleshooting.  I have used it in my batch files because I was told it was a good idea to do so, but if you don’t use the @echo command the batch file still works.  If you do use the @echo command I recommend you use @echo off as this will turn off this feature.

• The // syntax is used to stop the line from being read by the batch file. 

In the examples, the Taskkill command has been used to close the programs.  Taskkill will cause the program to terminate gracefully, asking for confirmation if there are unsaved changes.

To forcefully kill a process, add the /F option to the command line. Be careful with the /F option as it will terminate all matching processes without confirmation.

An example using the /F command is: Taskkill /F /IM ProSimAudio.exe.

There is debate in the computer community to the validity of closing files and programs simultaneously, as ‘killing a program’ may not allow the program enough time to save information it may be saving during the closure process.

For this reason, I'm hesitant to close flight simulator (or other programs) using a closure batch file without a timeout or delay sequence.  Needless to say, it's an easy process to configure a time delay into a batch file to create a delay before closing each program.

Timeouts

Depending upon your computer specifications, some programs may open and close at differing speeds.  If you want a program is open or close before the next program, then a delay sequence will need to be timed into your batch file. 

The timeout command is used to trigger a delay between the programs, enabling any read/write requirements to occur prior to the next program beginning it closure routine.  The numeral denotes seconds or part thereof. 

Streamlining

Once you have created and saved the batch file, a suggestion is to create a shortcut to the file.  Doing this will enable you to make changes to the batch file such as how the file is executed (minimised or maximised), the position on the screen, colour and font style used, and whether to use an icon for easy identification.  Additionally, by creating a shortcut it enables you to place the shortcut on your task bar.

To create a shortcut, right click the batch file and save as a shortcut.

Using Batch Files and ProSim IOS

View fullsize

ProSim-TS IOS screen in opened to network page.  Rather than explain everything, copy the details and use trial and error to achieve your desired result

If you are using multiple computers, you may want to use the ProSim Instructor Operator Station (IOS) to trigger the opening or closure of programs (via the batch file).  When IOS is configured correctly, you will be able to open and close a batch file on one or more networked computers from one computer screen.

To configure IOS, open the network tab, select add a new action or type and select start program.  In the path to executable file on client box type the file address of the batch opening file.  Choose the start option you prefer and ensure that enabled in checked.

To close your programs, open a second action and type in to the path to executable on client box the file address of the batch closure file.

The accompanying image should be self explanatory.

There are other ways to do this, however, this method is probably the simplest.

Caveat

I am not computer technician.  I have used batch files similar to the examples shown for many years without issues.

Final Call

Batch files are but one way to minimise workload and automate the opening and closure of ancillary programs that are used with flight simulator.  The use of IOS to trigger batch files also enables the user to open and close ancillary programs from the one computer screen (instructor station).

Switch-mode Power Supplies

Upper unit is a MeanWell switch-mode power supply with internal cooling fan.  The lower unit is a generic Chinese made power supply with no internal cooling fan; ventilation is provided by the perforated outer case and by inclusion of an internal aluminium heat sink.  Note that the MeanWell power supply has easier access to the terminals and is much thinner in depth than the lower unit

Every simulator needs some type of power supply, whether it be a converted multi-volt computer power supply, a plug in the wall type power pack, or a dedicated set voltage AC/DC switching power supply.  I dare say that most flight simulators have an assortment of different types that convert 240/110 volts AC power to DC power at a specific wattage and amperage.

In this article, I will discuss switching power supplies (switch-mode).  I will also very briefly address how to measure amperage using a multimeter.

Switch-mode Power Supplies

There are many types of power supplies.  However, for the most part a switch-mode power supply is the most versatile.

A switch-mode power supply is an electronic power supply that incorporates a switching regulator to convert electrical power efficiently from a higher AC voltage to a lower specified lower DC voltage.   This is done by converting the incoming mains power into a frequency between 20-kHz to 500-kHz AC that is then stepped down to a lower voltage (using a small integrated transformer).  The voltage is then rectified, filtered and regulated.

Clean Power

Clean power refers to power that is filtered and regulated, meaning the power is clean and is regulated to a predefined voltage.   This is important in the simulator environment because many interface cards and OEM components do not tolerate inconsistent voltage which can easily be the cause of inconsistent operation and USB disconnects.

In general,  a less expensive power supply will generate unclean power.

Power Supply Selection

Several companies produce power supplies – most of them are manufactured in China.  However, one company that stands out from the many is MeanWell (MW).  MeanWell is a Taiwanese company (not Chinese) that is a leading manufacturer of power supplies, and their switch-mode power supplies provide many advantages to the flight simulator builder.

Some of the advantages of using MeanWell power supplies are summarised below:

• Constant source of clean power rated at 20% above the certification provided.  What this means is that if you run the power supply at 100% it has a further 20% before the unit will be damaged.

• Protection from short circuit, overload and over voltage.

• Fixed switching at 25 kHz (produces a cleaner and better regulated power).

• Two or three year replacement warranty (model dependent).

• Internal cooling fan (model dependent).  Fan operation is temperature controlled.

• Audible alarm that sounds if operating temperature is exceeded (model dependent).

• Adjustable voltage (the voltage can be manually adjusted up or down (-+) to ensure correct voltage).

• Wide range of operating conditions (-25 Celsius to 70 Celsius).

• Solid enclosure with perforated holes (efficient heat sink and cooling).

• Easy screw attachment point or ability to use a rail system.

How Many Power Supplies Do I Need ?

This is a difficult question to answer as every simulator platform is different. 

The most effective way to determine the number and size of each power supply is to calculate the amperage draw of the items that will be connected to the power supply.  Armed with this information, you can decide what power supply and amperage is needed.

A flight simulator will usually require switch-mode power supplies in 5, 12 and 28 volts of varying amperages, and the cost of each unit will increase as the amperage rating increases.

While it’s possible to wire a number of lower amperage rated power supplies together, I believe using two or three individual larger amperage units is better than several smaller amperage units.

Amperage Draw and Calculating Amperage

Every item that draws power uses amperage, and the amount of amperage necessary for the component to operate must be calculated prior to selecting a power supply of a set amperage.   Using a power supply that is over-rated, in other words has more amperage than is necessary for a given situation is not a problem, however, using a power supply that does not have enough amperage for the attached device will result in either partial or complete failure of the connected device (for example, a bulb or LED may not illuminate to full intensity).

Amperage is the strength of electricity flowing through a circuit, usually from positive to negative.

To calculate amperage draw for a specific component, for example a 5 volt bulb, you will require a multimeter that has the capacity to read amperage.

There are several U-Tube videos on the Internet that provide guidance in how to use a multimeter to read amperage, so I will not replicate what is available.  

To begin, the mulimeter's red wire from is placed into the AMP outlet and the black lead is placed into the COM outlet of the multimeter. 

You then break the closed circuit of the Korry by removing the Korry from its holder.  You connect the red wire (AMP) from the multimeter to the positive side of the Korry.  The black wire (COM) is attached to the connector (holder) that the Korry was removed from. 

Essentially you are closing the circuit with the multimeter in-line.  Make sure the multimeter is set to read amperage (A).  Then turn on the DC power to the Korry.  The multimeter will read the amperage draw when the Korry is illuminated.

Important Point:

• Prior to connecting the wires from the multimeter, check that the fuse (usually 10 amps) is functioning inside the multimeter.   If you have a blown fuse and connect power to the multimeter, you may damage the device’s internal components.  Every multimeter is slightly different, therefore, consult the operating manual    

Rather than duplicate what already has been done, below are three links to U-Tube videos that explain how to use a multimeter to measure amperage. 

• Using a Multimeter.

• Using a Digital Multimeter to Check Amperage.

• How to Measure Amperage or Current.

Installation of Switch-mode Power Supplies

An advantage of using the same type/brand of power supply is the ease in mounting the power supplies.  Most power supplies have a number of screw holes that enable the unit to be screwed to a prefabricated bracket, or mounted to a solid board; some can also be attached to a rail system.

My Simulator Set-Up

In my simulator, I have installed what is called a Power Supply Rack (PSR) which is located forward of the Main Instrument Panel (MIP) on the platform floor. 

The rack is essentially an open frame L-shaped bracket made from wood (nothing fancy).  To this the power supplies are mounted.  The individual power supplies are wired together in parallel (wire connects between positive terminals on each power supply) to enable connection to the mains power by one power cable.

The open frame L-bracket has several advantages: all the power supply units are located in the one location, it’s straightforward to add another power supply as needed, and an open frame structure enables good ventilation and airflow; power supplies when operated for an extended period of time can generate considerable heat.

View fullsize

Present on all power supplies is the voltage regulator.  This enables the outgoing voltage to be adjusted, usually to a few volts either side of the advertised voltage.  Also note the barriers between each of the terminals and the nomenclature marking above each of the terminals

Safety

Switch-mode power supplies usually have at the end of the unit a terminal bar.  The incoming mains power (three wires) is connected to the two AC and Earth terminals.  Directly adjacent are four or six terminals marked +V and -V (outgoing).   This is where you connect the +- wires from your device.  The two AC terminals (incoming) when connected to mains power are always LIVE; touching these terminals will cause a life-threatening electric shock.  Therefore, it’s paramount that these terminals are covered.

Some power supplies come with a plastic protective cover that is clipped in place after the wires are connected; all have plastic barriers between each terminal to minimise the accidental touching of wires. 

If the power supply does not have a cover, one can easily be made using a piece of plastic and held in place by electrical tape.  Clear silicon or hot glue can also be used to cover the AC and Earth terminals; the advantage of hot glue being that it’s easily removed by applying 80% alcohol.  At the minimum, red-coloured electrical tape should be used to tape over the terminals.

Safety is important when working around 240/110 volts AC and strict protocols should be followed at all times.  If in doubt, always disconnect the power supply from the mains power prior to doing any maintenance.

View fullsize

Single circuit busbar and multiple circuit terminal bar

Power Distribution (busbars and terminal blocks)

Any flight simulator requires various voltages to function.  For example, backlighting requires 5 volts DC while OEM annunciators (Korrys) require 28 volts DC. 

Power distribution, depending upon your skill level, can become quite elaborate and complicated, but at its simplest level is the use of busbars and terminal blocks.

Busbars and terminal block appear similar, however, are used for differing applications.

The main difference is that a busbar gathers multiple wires together for power distribution in a single circuit (one voltage).  In contrast, a terminal block has separate circuits where each wire is paired with an outgoing wire.  A simple way to think about it is, that a busbar is a single circuit whereby a terminal block is multiple circuits. 

There are as many manufacturers as there are types of busbars available;  it's also relatively straight forward to convert an inexpensive terminal bar into a busbar by routing the power wire between each terminal/circuit (the wires look like the letter U between each of the circuits/terminals).  Doing this enables one terminal to be allocated to incoming power (for example 5 volts) rather than an incoming power wire being connected to each circuit.

Importantly, when wiring busbars or other items care must be taken to the gauge of wire used.  You don't want to use a thin piece of wire (minimal number of wire strands) when connecting to a high amperage item.  If you do, the wires will become very warm and the amperage that travels through the wire will drop (which may cause inconsistent operation or a USB dropout - if the wired item is connected to the computer by a USB cable).  A worse case scenario is the wire will melt and a fire may occur.

View fullsize

Blue Sea Systems busbar with transparent cover

My Simulator Set-Up

In my simulator, installed behind the Main Instrument Panel (MIP) is a small shelf on which three heavy duty high amperage busbars are mounted (5, 12 and 28 volts respectively).  Each busbar connects directly to various components. 

A further 5 and 12 volt busbar has been installed to the inside of the center pedestal, and these busbars provide 5 and 12 volt power to OEM panels, Belkin USB hubs and an Ethernet switch. 

Additional 5 and 12 volt busbars are located within the Throttle Communication Module (TCM); a small box mounted to the forward firewall of the throttle quadrant.

For the most part, I have used marine-grade busbars manufactured by Blue Sea Systems (an American company).  Although the clear acrylic covers are not necessary, they do minimise the chance of a short circuit occurring should something drop onto the busbar.

Dedicated Power Supply to Specific Aircraft Systems

It is preferable to dedicate individual power supplies to specific aircraft systems.

The advantage of linking a dedicated power supply to a particular aircraft system, is if a catastrophic failure should occur, the problem will be maintained within that system and any power leakage/spike will not be able to travel to other systems (located on a separate power supply). 

A further benefit is that the amperage draw for each power supply can be easily measured to ensure it doesn't exceed 80% of the total draw available.  Effectively, this should increase the longevity of each power supply as it will not be operating at full output. 

Troubleshooting is also easier when you know what functions are connected to each power supply.

Operating OEM components requires a relatively high amperage draw, and whilst it's feasible to 'piggy back' two power supplies of the same amperage to effectively double your amperage, this is not advisable. 

Maintenance

In general, power supplies do not require maintenance.  However, depending upon the working environment, dust can build-up on the internal workings of the unit.  If dust does build up, the unit should be routinely cleaned with a small vacuum cleaner or lint free cloth – this is especially so for those units that have an internally-driven fan which can ingest dust particles.  If a ‘thick’ layer of dust is allowed to accumulate, there is a chance that the unit may operate at a slightly higher temperature, thereby minimising service life, and perhaps altering voltage output.

Final Call

There are several types of power supplies that can be used to power components in a flight simulator; the most versatile are switch-mode power supplies.  MeanWell, a Taiwanese company, manufactures a number of switch-mode power supplies that in many ways are superior to its competition.  However, prior to using any power supply the total amperage draw of the simulator’s components should be calculated to ensure that the most appropriate switch-mode power supply is used.

Using The Tiller To Taxi The Boeing 737

View fullsize

oem captain-side steering tiller. (737ng-info, 737controls, CC BY-SA 3.0)

To taxi an aircraft around the airport the pilot uses either the rudder pedals and/or a steering wheel device called a tiller.  The half-moon shaped tiller is mounted to the sidewall of the flight deck.  The number of tillers in an aircraft is not standard; some aircraft have one tiller while some have two.  The tiller controls the lateral movement of the aircraft’s nose wheel, located below and behind the flight deck.

The rudder pedals when pressed do provide some lateral movement, however, nose wheel steering is no more than 7 degrees.  To enable full lateral movement of the nose wheel  requires using the tiller with some forward thrust (called break-away thrust) from the aircraft’s engines.   

If the aircraft is to be moved backwards (for example from the ramp), then a push-back truck and ground controller is required.  The controller will connect a bar from the push-back truck to the main coupling of the nose wheel to lock the nose wheel in the forward position.  Once this is done, the push-back truck will lift the nose wheel enabling the aircraft to be reversed backwards.  A push-back truck can also be used to pull the aircraft forwards.

The ground controller will be in communication with the pilot and will instruct the pilot when it is safe to release the parking brake or start the engines (it is the responsibility of the ground controller, amongst other things, to check that the doors are closed and that personnel are clear of the aircraft).  Prior to the aircraft being moved, the pilot will speak with Air Traffic Control to obtain starting and push-back approval.

After ATC has given clearance, the pilot will:

1. Check and cross check the taxi route instructions issued by ATC.

2. Release the parking brake by pressing the upper section of the toe brakes.

3. Apply forward thrust by advancing both thrust levers to around 32%.  The actual percentage N1 depends on the weight of the aircraft.  The forward thrust should not exceed 40%N1.

4. Use the tiller to maneuver the aircraft.

5. To stop the aircraft the thrust levers are brought back to idle, the toe brakes are pressed to stop any forward movement of the aircraft, and the parking brake applied.

Although not recommended, it is possible to aid in the turn by applying appropriate thrust only to one engine.

Important Points:

• Reverse thrust should not be used to move the aircraft backwards primarily because of the likelihood on ingesting foreign material into the engine.

• Whenever the aircraft is at a standstill the parking brake should be applied.

Taxi Speeds

Taxi speeds vary.  Generally, in good conditions the maximum permissible speeds are:

• 10 knots – when doing turns;

• 30 knots – when traveling in a straight-line along a runway;

• 50 knots – when back-tracking along a runway; and,

• If the runway is contaminated (ice, snow, etc) the taxi speeds are reduced to 5 knots.

How To Taxi

The nose wheel is located under and to the rear of the flight deck.  Therefore, to turn onto and follow the taxi lines accurately you must slightly overshoot the line prior to turning.

OEM Tiller

Another article addresses how to convert an OEM tiller and use in ProSim737 -  OEM tiller in ProSim737.

Final Call

With a little practice taxing the aircraft in the flight simulator is straightforward.  Points to consider are turning the nose wheel at the correct time (before crossing the line) and applying the correct amount of thrust based on aircraft weight.

Installing the Navigraph Database to ProSim-AR (ProSim737)

No matter which avionics suite is used, the navigational database and approach charts will need to be kept up-to-date.  Navigraph (the company) have for many years been the mainstay in supplying accurate navigational data to the flight simulator community.

The navigation database and monthly updates can be downloaded from the Navigraph website, and can either be manually installed to Flight Simulator, or alternatively you can use Navigraph’s FMS Data Manager software to install the files.

This short article will benefit only those using the ProSim-AR (ProSim-737) avionics suite Version 3.  ProSim-AR Version 2 uses a different file structure and navigation path.

Database Files and Installation

Navigraph is the navigation database used by ProSim737.   The database is purchased separately to ProSim-AR and navigation updates (AIRAC cycles) are released monthly.

The correct navigational database for ProSim737 to download from the Navigraph website is: ProSim737 2.24b1 (and above).

When installed the database consists of three files:

• cycle.json;

• cycle_info.txt; and,

• nd.bb3.

Cycle-info.txt is a text file that indicates which navigation database has been installed.  This is the file you need to open if you are unsure of which AIRAC cycle has been installed.  The other two files relate directly to the database.

Once the database is installed or updated, the ProSim737 main module (.exe file) must be run, and the database rebuilt.

To rebuild the database, open the ProSim main module, select Config/Database and Build Database.  The process to rebuild the database will take around 5 minutes.  When completed, the installed database AIRAC cycle number will be displayed.

Database Fails to Update

If the database does not update, there is a possibility that either the downloaded file is corrupt, or more than likely the database has been installed to the incorrect folder structure within ProSim-AR.

In this case, download the required files from Navigraph, uncompress the files to your computer desktop (or anywhere else) and copy the three database files to:

C:/Program Data/Prosim-AR/Navdata.

View fullsize

FMS Database Manager Mapping page.  This is where you select the folder structure to upload the AIRAC cycle to

FMS Data Manager

Navigraph have an installer (FMS Data Manager) which is a standalone program that is free to use.  The Data Manager is quite a powerful program and it’s worth the effort examining what this software can do.

When setup correctly, the installer will download, uncompress, and install the Navigraph files to the correct folder structure with ProSim.  The installer also will create a backup of the existing database (if selected).

View fullsize

Navigraph FMS Data Manager main front page.  This is the page where you select Update to update the navigational database with the latest AIRAC cycle

To ensure that the database is installed to the correct folder on your computer, the Data Manager must be configured correctly.  This can be done a number of ways, however, the easiest and most straightforward way is to setup the folder structure manually.

• Open the FMS Data Manager and select Addon Mappings.

• Select the black coloured folder adjacent to the purple coloured box named Manual.

• Select the correct folder in your computer (C:/Program Data) and save the configuration.

To update the database, navigate back to the front page of the manager and select the check box adjacent to ProSim737 2.24b1 and select update.

View fullsize

ProSim-AR (ProSim737) main menu showing the Config page open with the Build Database page overlaid

Important Points:

• Whenever you install or update the Navigraph database, rebuild the database and check the AIRAC cycle.

Final Call

Maintaining the navigation database is important if you are to get the most from Flight Simulator.  Navigraph AIRAC cycles are released monthly, and it stands to reason that the FMS Data Manager should be used to streamline the installation process.  Problems, when they do occur, usually relate to the FMS Data Manager trying to install files to the incorrect folder structure.

Reverse Thrust Procedure

View fullsize

The reverse thrust levers are clearly visible in the first detent position.  OEM throttle quadrant converted for flight simulator use

Pilots tend to be numbers-orientated individuals.  They like concise instructions and do not like ambiguity.  Nor do they like being presented with something that is in ‘shades of grey’ rather than ‘black and white’. 

When, how, and for how long to deploy the reverse thrust (reversers) falls into the 'grey area'.

In this article, I will endeavour to unravel some of the uncertainties as to when and how to use reverse thrust.  I will also briefly discuss the relationship between the use of the autobrake and reverse thrust.

I am not going to delve deeply into every environmental consideration that needs to be analysed prior to the use of reverse thrust; this information is more than readily available from the Flight Crew Operations Manual (FCOM), Flight Crew Training Manual (FCTM) and other specific airline policy documentation.

Reverse Thrust Basics

Reverse thrust (reversers) is used only for ground operations and is used after touchdown to slow the aircraft;  it is used to reduce the stopping distance, minimise brake temperatures and decrease wear and tear.

Reverse thrust comprises four détentes and an interlock position, that are engaged by moving the thrust levers from the stowed down position through to the fully up position.  

1. No reverse thrust (thrust levers are closed / stowed position).

2. Detent 1 (idle reverse / thrust levers are at first position).

3. Detent 2 (thrust levers are at second position).

4. Full maximum reverse thrust (thrust levers are at fully upward position).

Between detent 1 and full maximum reverse thrust there is scope for the thrust levers to be positioned part way; thereby, altering the amount of thrust generated.

View fullsize

Schematic showing various positions for the thrust reverser levers

The interlock mechanism is felt when the reverse thrust levers are advanced to detent 1. The purpose of the interlock is to restrict movement of the reverse thrust lever until the reverser sleeves have approached the deployed position.

The procedure to use reverse thrust is very straightforward, however, questions arise as to whether to use detent 2 or full maximum reverse thrust, and when to begin reducing thrust and for how long.

Procedure

Following touchdown, without delay, move the reverse thrust levers to the interlock position and hold light pressure until the interlocks release (as the sleeves move rearwards).

For most landings, detent 1 and detent 2 will usually provide adequate reverse thrust (for normal operations).  If additional reverse thrust is needed (wet, slippery or short field landing), full maximum reverse thrust can be selected by raising the thrust levers past detent 2 to full maximum reverse thrust.  

To come out of reverse, the reverse thrust levers are returned to the detent 1 position, the engine allowed to spool down, and the levers then returned to the stow position.

Practically speaking, after touchdown maintain reverse thrust as required up to maximum thrust until the airspeed approaches 60 knots. Reverse thrust is then slowly reduced to detent 1 and then to reverse idle by taxi speed. Wait until the generated reverse thrust has bleed off, then slowly close the reversers and place them in the stow position.

Bringing the reverse thrust levers to detent 1 is important because it prevents engine exhaust re-ingestion and minimises the risk of foreign object debris (FOD) ingestion.  Idle thrust also bleeds off forward thrust from the engines.

The autobrake is disarmed when a safe stop of the aircraft is assured, or when the aircraft reaches taxi speed.

Important Point:

• If transitioning from using the autobrake to manual braking, use reverse thrust as required until reaching taxi speed and then disarm the autobrake.  

Disarming the autobrake before closing reverse thrust provides a relativity seamless transition which increases passenger comfort (there is no aircraft jolt).

Conditions Required To Engage Reverse Thrust

The reversers can be deployed when either of the following conditions occur:

1. The radio altimeter senses less than 10 feet altitude;

2. When the air/ground sensor is in ground mode; and,

3. When the forward thrust levers are in the idle position.

Until these conditions occur, the movement of the reverse thrust levers is mechanically restricted and the levers cannot be moved into the aft position.

It is important to always deploy reverse thrust as soon as possible following touchdown.  Do not wait for the nose wheel to touch down, but engage reverse thrust when the main wheels are on the runway.  Timely deployment will increase stopping power; thereby, increasing safety and reducing heat build-up in the brake system.  

A study determined that there was roughly a 17 second difference in stopping time when reverse thrust was deployed immediately the landing gear was on the runway as opposed to waiting several seconds for the nose gear to also be on the runway - reverse thrust is most effectual at high airspeeds and its effect decays on a linear scale as forward airspeed decreases.

Important Points:

• Reverse thrust should always be used with the autobrake, unless the runway is exceptionally long without a possibility of runway overrun (the reason for this will be explained shortly).

• When closing the reversers, always pause at detent 1.  Monitor the REV thrust output on the Primary Engine Display (center panel) and stow the reversers only after reverse thrust has dissipated.

Call-outs

The pilot monitoring usually makes the following call-outs:

• ‘60 knots’;

• ‘Reversers normal’ -  when both REV indications are green;

• ‘No reverser engine No: 1’ - if no REV indication or colour is amber; or,

• ‘No reverser engine No: 2’ -  if no REV indication or colour is amber; or,

• ‘No reversers’ -  if no REV indications or colour is amber.

NOTE:  Annunciators and displays are discussed later in the article.

During landing, the pilot monitoring (PM) should call out 60 knots to advise the pilot flying (PF) in scheduling the reduction of reverse thrust.  

When landings are in conditions that are suboptimal (heavy rain, snow, slush, etc), some operators stipulate that the PM operate and control the reverse thrust .  This enables the PF to concentrate solely on the landing roll out rather than having the extra responsibility of also controlling the reverse thrust.  

This said, although this procedure may lower pilot workload, it can cause problems when the PF is landing on a slippery runway or in marginal crosswind conditions.   At these times, the PF may wish to use the reverse thrust in conjunction with the brakes and there is little time to call out instructions to the PM.

Technical Aspects (basic operation)

Each engine on the Boeing 737 Next Generation is equipped with an hydraulically operated thrust reverser, consisting of left and right translating (moving) sleeves.  Aft movement of the reverser sleeves cause blocker doors to deflect fan discharge air forward, through fixed cascade vanes, producing reverse thrust.  

Hydraulic pressure for the operation of the thrust reversers comes from hydraulic systems A and B, respectively.  If hydraulic system A and/or B fails, alternate operation for the affected thrust reverser is available through the standby hydraulic system.  When the standby hydraulic system is used, the affected thrust reverser deploys and retracts at a slower rate and some thrust symmetry can be anticipated.

When reverse thrust is selected an electro-mechanical lock is released.  This causes the  isolation valve to open which results in the thrust reverser control valve moving to the deploy position, allowing hydraulic pressure to unlock and deploy the reverser system.

The system is designed in such a way that an interlock mechanism restricts movement of the reverse thrust lever until the reverser sleeves are in the deployed position.

Closing the thrust levers past detent 1 to the stow position initiates the command to stow the reverser.  When the lever reaches the full down position, the control valve moves to the stow position allowing hydraulic pressure to stow and lock the reverser sleeves.  After the thrust reverser is stowed, the isolation valve closes and the electro-mechanical lock engages.

Relationship with Flaps

There is an interesting relationship between the use of reverse thrust and flaps 40.

When the aircraft has flaps 40 extended, the drag is greater requiring a higher %N1 to maintain airspeed. This higher N1 takes longer to spool down when the thrust levers are brought to idle during the flare; this enables more energy to be initially transferred to reverse thrust.

Therefore, during a flaps 40 landing more energy is available to be directed to reverse thrust, as opposed to a flaps 30 landing.

Annunciators and Displays

Thrust reverse indicators are displayed in the Primary Engine Display located in the center panel slightly above the No: 1 and No: 2 %N1 indicators.  When reverse thrust is commanded, REV will be displayed initially in amber followed by green dependent upon the position of the thrust reverse levers.

• Amber:  Thrust reverser has been deployed from the stowed position and both sleeves have travelled ~10-90% to the deployed position.

• Green:  Thrust reverser has been deployed from the stowed position and both sleeves have travelled greater than 90% to the deployed position.

When either reverser sleeve moves from the stowed position, the amber REV indication annunciator, located on the upper display will illuminate.  As the thrust reverser reaches the deployed position, the REV indication illuminates green and the reverse thrust lever can be raised to detent 2.  

View fullsize

Electronic Engine Control (EEC) panel (AFT overhead). ProSim737 avionics suite virtual display

Additional reverse thrust annunciators are located on the aft overhead panel in the Electronic Engine Control (ECC) panel.  These annunciators are triggered by the retraction of the reverse thrust levers to the stow position.   

The annunciators will illuminate during a normal reverse thrust / stow operation for 10 seconds and then extinguish 10 seconds later when the isolation valve closes.  

A system malfunction has occurred if the reverser (REV) annunciator illuminates at any other time, or illuminates for more than approximately 12 seconds (in the later instance, the master caution and ENG system annunciator will also illuminate).

Possible reasons for a system malfunction are that the isolation valve, thrust reverser control valve, or one or both of the thrust reverser sleeves are not in their correct position.

Autobrake and Reverse Thrust Use (the grey area)

Both the autobrake and timely application of reverse thrust can be used to slow the aircraft, however, both come at a cost.  

Using the autobrake generates considerable heat in the braking system, translating to increased expenditure in maintenance and possible delays in turn around times (waiting for brakes to cool to operational temperature).  Conversely, reverse thrust consumes excess fuel.  Clearly there is a middle point where each will cancel out the other.

The immediate initiation of reverse thrust at main gear touchdown, and use of maximum reverse thrust, enable the autobrake system to reduce brake pressure to the minimum level – this is because the autobrake system senses deceleration and modulates brake pressure accordingly.  Therefore, the proper application of reverse thrust results in reduced braking and less heat generation for a large portion of the landing roll.

Based on this premise, it stands to reason that this is why Boeing recommend to use the autobrake in conjunction with reverse thrust.

Boeing states in the FCTM that: ‘After touchdown, with the thrust levers at idle, rapidly raise the reverse thrust levers up and aft to the interlock position, then to reverse thrust detent 2.  Conditions permitting, limit reverse thrust to detent 2’.

It appears to be Boeing’s intention to use reverse thrust as the major force to stop the aircraft, and as the use of maximum reverse thrust further minimises brake system heating, it would appear to be a preferred choice, despite the FCTM stating detent 2 is the preferred position for normal operations.

The official literature does not satisfactorily address this ‘grey area’   The result being that many 737 pilots use differing techniques when deploying and stowing the reversers.

Various Methods

If you observe how other pilots use the reversers, you will discover that there are several variations that follow the same theme.

1.    A pilot will, when the aircraft passes through 60 knots, close reverse thrust by lowering the reverse thrust levers through detent 1 to the stow position without stopping at detent 1;

2.    Try to locate detent 1 by ‘feel’ resulting in pushing the levers too far towards the stow position, causing forward thrust to unexpectedly occur momentarily;

3.    Deliberately close maximum reverse thrust at the 60 knots by placing the reverse thrust levers into the stow position.

In the above three scenarios, the reverse thrust levers have not been allowed to pause at  the detent 1 position.  Pausing at detent 1 is important as %N1 requires several seconds to reduce to idle thrust after maximum reverse thrust has been used, and it is during this ‘wind down’ period, as the reverse sleeves fully close, that %N1 will transition through 55-60%N1, which is forward thrust.  

By not allowing the reversers to pause momentarily at detent 1, to enable thrust to disparate below 55-60%N1, may cause the aircraft to momentarily accelerate.  This can be rather disconcerting, especially on a short field landing or landing in marginal conditions.

So What Do I do (normal procedure)

1. At touchdown I engage reverse thrust – either detent 2 or maximum reverse thrust (or part thereof).

2. Approaching 60 knots I slowly and smoothly retard the reverse thrust levers to detent 1.

3. I always allow a few seconds at detent 1 to enable %N1 to dissipate.

4.  Approaching taxi speed I disarm the speedbrake and close the reversers.

• At no time do, unless in an emergency, do I close the reversers suddenly; I always close the reversers smoothly and slowly. This enables %N1 to dissipate gradually.

Final Call

The procedure to deploy reverse thrust is straightforward and very easy to accomplish, and there is little argument that reverse thrust should be used on all, but the longest runways in optimal environmental conditions.   However, there is confusion and often disagreement to when the reversers are deployed, whether maximum reverse thrust should be used, and for how long the reversers should be left in the open position before retraction and stowing.

It is unfortunate that the information written in the Flight Crew Training Manual (FCTM) and Flight Crew Operations Manual (FCOM) does not provide a more objective ‘black and white’ answer to this procedural dilemma.

Video

The below video shows the REV indicators on the Primary Engine Display (when reverse thrust is commanded) and the REVERSE annunciators on the ECC panel (AFT overhead).  Video taken directly from ProSim-AR 737 avionics suite (virtual software).  Video upload to U-Tube rather than VIMEO).

REVERSE THRUST ANNUNCIATIONS - ECC PANEL AFT OVERHEAD

Circle-to-Land Approach Procedure

View fullsize

Although a circle-to-land is a VFR approach, it is recommended to use whatever automation and equipment is available.  This includes the FMC to generate waypoints and radials to increase situational awareness (Petr Beran, Aerosvit Boeing 737-400 on final approach into Tivat Airport, CC BY-SA 4.0)

Landing can be a challenge to new virtual flyers, and this is especially so when there are so many different types of approaches that an airline pilot can use.  Often the approach selected is based on environmental conditions, the type of equipment used in the aircraft, and the type of equipment and technology available at the airport.

This article will explain the technique used in circle-to-land (CTL) approaches.  I have purposely tried to simply the details to cater to all levels of experience.  However, aviation often is not a simple subject; issues can be complex and overlap.

What is a Circle-to-Land

A circle-to-land approach is similar to entering a VFR traffic pattern, but you are following a published approach prior to entering the pattern directly.  A CTL is an hybrid between a standard non-precision visual approach and a precision approach; you use information gleaned from the circle-to-land information block on the chart in a 100% visual environment.   

The initial approach used can be either a precision or non-precision approach. RNAV (GPS), NDB, VOR and ILS approach types are allowed, however, only CAT 1 approaches can be used (CAT 2 & CAT 3 approaches cannot be used).   It is important to realise that if an ILS is used, you do not fly the ILS.  Rather, you fly the Localizer and use Vertical Speed (V/S) to descend at the appropriate rate of descent (following the ILS vertical guidance).

Although the approach is VFR, you still utilise whatever instruments necessary to increase spatial awareness and lower pilot workload.  The autopilot, autothrottle and vertical speed are often used during the approach, however, this is not a hard and fast rule and flying the aircraft manually is allowed.  Boeing recommend the use of the autopilot when intercepting the landing profile.

The approach is usually executed at a low altitude; typically 1000 feet AGL within a defined boundary around the airport (usually a 4.5 nautical mile ‘protection area’).  This is in contrast to a standard visual traffic pattern whereby an altitude of ~1500 feet AGL is used.  

View fullsize

Approach chart for Hobart, Tasmania (YMHB).  Note the circle-to-land information block outlined in red.  Also note the MDA and visibility for a Category C aircraft highlighted in yellow © Navigraph/Jeppesen

MDA and Speed Management

The minimum altitude that the CTL is to be flown is specified by the MDA, while the minimum required visibility and other pertinent points are displayed in the circle-to-land section of the approach chart (see chart diagram).   The general rule is that if something is not prohibited, then it is allowed.  If there is no note on the chart prohibiting a CTL then circling to land is implicit.

The MDA is the lowest altitude that you can descend to when conducting a CTL.  This said, there is absolutely no reason why you must descend to this altitude.  Providing horizontal visibility is within range, often a higher altitude (similar to a pattern altitude) will make the approach easier.  If using a higher altitude than the MDA, ensure you do not exceed the boundary as defined by the 'protected area'.

Speed management and a stabilised approach is paramount, as the aircraft is relatively low to the ground and is in landing configuration.  The aircraft’s speed should not be below Vref+15 (approximately 160 kias) as the aircraft will need to be banked in a standard 25 degree turn when it has reaches the MDA.  The final approach speed and descent occurs during the turn to short final and on final.

NOTE:  I purposely have not discussed ICAO and US TERPS.  If you want to read about the differences between the two protocols, navigate to Skybrary.

Circle-to-Land Procedure

1. Consult the approach chart to determine the Minimum Descent Altitude (MDA).  Whatever this figure is, round the number up to a even number by adding 100.  For example, if the MDA is 1430 feet round the number to the nearest 100 feet, which is 1500 feet.  Dial this altitude into the altitude window on the MCP (if desired, a higher altitude to the published MDA can be used). 

2. Fly the Localiser and use V/S to alter your rate of descent.  Speed management is important.  Although not required, it is a good idea to adjust your heading selector on the MCP to read 45 degrees either left or right of the localiser course.  This saves you doing it when the aircraft reaches the MDA.

3. The landing gear and flaps(flaps 15) are to be extended no later than the MDA.  However, if necessary this can be done prior to the MDA to aid in establishing a stabilised approach (for example, between 10 and 7 nautical miles from the runway).  The speed brake should be armed.

4. Fly the localiser to the MDA until ALT HOLD (ALT ACQ will be displayed on the FMA) and level off at the MDA.  Set the Missed Approach Altitude (MAA) in the altitude window on the MCP.  If you are not visual by this stage, a Go Around must be executed.  Note that is if VNAV is being used select ALT HOLD on the MCP (this will disable VNAV).

5. Press Heading Select (HDG SEL) on the MCP.  The aircraft will turn 45 degrees L/R at a 25 degree bank (assuming you preset the HDG SEL as mentioned earlier).  Once the wings are level (more or less by a few degrees) continue to fly this course for 20 seconds.  Use the timer to record the elapsed time.

6. After 20 seconds has elapsed (some procedures suggest 30 seconds), adjust your heading (HDG SEL) to fly downwind (the original localiser course).  Fly this heading until the aircraft is abeam of the runway threshold (the triangle that represents the aircraft on the ND should align with the end of the runway).  Either look out of the window to gauge your position and/or use the Navigation Display to check the aircraft’s position in relation to the runway.

7. Start the clock when the aircraft is abeam of the runway and fly outbound for 3 seconds per 100 feet AGL.  For example, if the MDA is 1500 feet, you divide 1500 by 100 and times by 3 to determine the time (t) of the outbound leg – which is 45 seconds  (t=1500/100*3).

8. When 45 seconds has elapsed, call for landing flaps, adjust the speed, and set the HDG SEL on the MCP to the runway heading.  Begin a descent using V/S at 300 fpm and complete the landing checklist. 

It is recommended to use the position trend vector on the Navigation Display, in conjunction with outside references (runway PAPI, etc), to judge the turn.  The aircraft’s bank should not exceed 25 degrees during the turn.  

The prevailing wind and distance from the runway will determine if the turn is continuous or to base and then final. 

If using the autopilot, remember to adjust the bank angle selector accordingly, otherwise the aircraft’s bank may exceed stipulated parameters.  Intercept the normal visual glide path (final) and disconnect the autopilot and autothrottle.  Verify that the missed approach altitude is set on the MCP and recycle the Flight Director switches (if required).

After disconnecting the autothrottle, an initial 'good' thrust setting is around 55%N1; from this point you can increase or decrease thrust to maintain Vref+5.  Also, as you turn to final, glance at the runway PAPI lights and adjust vertical speed accordingly.  As a  rough guide:

PAPI Lights

4 RED - do nothing (maintain V/S).

3 RED - increase V/S to 500 fpm.

2 RED - increase V/S 800-850 fpm

1 RED - increase V/S 1000 fpm

9. If the MDA is breached or visual references are lost, a Go Around must be executed.  Depending upon the aircraft’s position, climb to the Missed Approach Altitude (MAA) remaining in the ‘protected area’ (fly in circles) 

If a Go Around is executed prior to the final approach, always turn the aircraft in the direction of the runway, as this will ensure the aircraft remains in the ‘protected area’.

Winds

Any tail or crosswind must be taken into consideration.  Failure to do so will place the aircraft in the wrong position relative to the approach.

To correct for wind, you take half the tail component and subtract it from the outbound time.  For example, if the tail component is 5 knots and the outbound time is 24 seconds, you would subtract 5 from 24 giving you an adjusted time of 19 seconds.

Another way to determine this is to press the progress page (page 2) on the CDU (PROG)

and halve the tailwind component displayed.

View fullsize

The Navigation Display showing several aids that have been used to facilitate a circle-to-land on runway 30 at Hobart, Tasmania (YMHB).  A circle ring at 4 mile, a radial (030), and a point/bearing/distance waypoint (RW301).  The heading bug has been preset to a turn of 45 degrees

Aids to Increase Spatial Awareness

Although this is a visual only approach, there is no reason not to use whatever tools are at hand to increase spatial awareness and make the approach a little easier. 

Use the CDU to:

1. Make a waypoint (Place/Bearing/Distance waypoint) at whatever distance desired that is adjacent to the runway.  This waypoint will act a point in space that the turn to base is made. 

2. Note that this waypoint/fix is only for added reference and is not a point from which to create a route.

3. Create a radial 90 degrees from the end of the runway.  This will display a straight line from the runway that will be a visual reminder when the aircraft is abeam of the runway.

4. Create distance rings.  The rings are displayed on the Navigation Display.  At the very least, a ring should  be used to delineate the 'protected area' around the airport.  Further rings can be used to help show the MDA and other flight specific events.

5. Use the Vertical Bearing Indicator (VBI).  The VBI provides a defined vertical speed that can be used as a reference to the correct 3 degree glide path.

How to make a distance ring, radial, waypoint, and use the Vertical Bearing Indicator (VBI)

Although this has been mentioned elsewhere on this website, a review is in order.  In the following examples I will use the approach chart YMHB Runway 30 (see chart diagram below).  This is a VOR approach, however, it could equally another approach type.  LSK1L means Line Select 1 Left.

NOTE:  There are differences between avionics suites.  ProSim737 use the acronym RW to define a runway.  PMDG use RWY.

Before continuing, the following functionality overlaps with each other.  Therefore, it is easy to become discombobulated.  When you are in the simulator you will find it makes sense.

Distance Rings

Distance rings are created from the FIX page in the CDU.

1. Open the FIX page and type into the scratchpad a known waypoint or navaid (For example YMHB or RW30). 

2. Up-select the identifier to the FIX page (LSK1L).   A dashed-green coloured circle will be displayed around the waypoint in the Navigation Display.

3. To enlarge the ring to a desired distance around the waypoint, type into the scratchpad the distance (for example /2).  Up-select this to LSK2L.  This will display the ring around the waypoint at a distance of 2 miles.

Creating a Radial to a Specified Waypoint

To create a radial a set distance from a known point (waypoint/navaid).  For example RW30.

1. Open the FIX page and type into the scratchpad the desired waypoint/navaid, bearing vector and distance. 

2. Type into the scratchpad the bearing and distance of the radial wanted (for example 030/2).

3. Up-select this to the appropriate line in the FIX page (LSK2L).  For example, entering RW30030/2 will create a green dashed line along the 030 bearing to intersect with a circle surrounding RW30 at a distance of 2 miles.

4. If you want the point (where the line insects the circle) to become a waypoint, read the next section.

Creating a Specified Waypoint (Place/Bearing/Distance Waypoint)

There are a few ways to do this.   I have discussed one way (which works with ProSim737).

1. Type into the scratchpad RW30.  This will create a green coloured circle around RW30 on the Navigation Display (ND).  

2. Type in the scratchpad the bearing and distance (030/2). 

3. Up-select this information to the FIX page (LSK2L).  This will place a green-coloured radial at 030 degrees from RW30 that intersects the circle at 2 miles on the ND.

4. Next, select the 030/2 entry from the FIX page (press LSK2L).  This will copy the information to the scratchpad.  Note the custom-generated name - RW30030/2.

5. Open the LEGS page and up-select the copied information to the route.  Press EXECUTE. 

6. RW30030/2 will now have an amended name - RW301.  Note that RW301 will form part of the active route.

7. Copy RW301 to the scratchpad.

8. Open a new FIX page (there are 6 FIX pages that can be used). 

9. Up-select RW301 to the FIX page (LKL1L).  This will create a circle around RW301 on the ND.

10. To remove the waypoint (RW301) from the route, open the LEGS page and delete the entry. 

11. Press EXECUTE. 

RW30 will be displayed on the Navigation Display

There is a less convolted way to do this, however, the method is not supported by ProSim737.

VBI

To input a variable into the VBI, an appropriate approach must be selected from the ARRIVALS page.  This approach information can be deleted from the route after the information for the VBI has been generated.

1. Select the DEP/ARR page in the CDU.

2. Select ARR and then select RW30. RW30 is shown on the last page.

3. Choose a desired distance to generate a runway extended line (RWY EXTLSK3R).

4. Open the LEGS page and close any discontinuity; or,

5. Delete all entries except RW30 (unless wanting them).  Ensure RW30 is the active leg (LSK1L).  The entry will be coloured magenta. 

6. Press EXECUTE. 

Open the VBI by pressing DES on the CDU.  RW30 should be displayed in the VBI.

Important Points:

• A quicker way to do this is to select RW30 to the scratchpad and then up-select to the upper most entry (LSK1L).  This will delete all entries except this one (assuming you do not want other entries).

• When loading an approach, often a RX-XX will be displayed.  The RX-XX waypoint is not part of the database but is a generated waypoint based on the approach type selected (it will have a different altitude).  Do not use the RX-XX entry (delete it).

View fullsize

Diagram 1: representing a circle-to-land approach © Boeing FCOM

Go Around

To perform a Go Around using a published missed approach you need to enter the missed approach details into the FMC (the missed approach is displayed in the LEGS page immediately AFTER RW30).

1. Select DEP/ARR in the CDU and select an approach for Runway 30.  This will display in the LEGS page an appropriate approach, runway and a missed approach.

2. Open the LEGS page and delete all entries prior to runway 30 (RW30) and clean up any discontinuity.  Check the LEGS page to ensure the runway and missed approach are correct.

• Additional information: Creating Waypoints on the Fly.

Important Points:

• A circle-to-land approach can only be conducted when the pilot flying is able to see the airport and runway.  If at anytime visual reference is lost, a Go Around must be executed.

• The aircraft must not descend below the Minimum Descent Altitude (MDA)  stipulated on the approach chart.  Although the aircraft must not descent below the MDA, a higher MDA can be used if desired.

• The initial approach can be flown using one of several chart types.  If using an ILS approach it is recommended to not engage the ILS mode (if you do, ensure you do not accdently descend past the MDA - change out to V/S prior to reaching the MDA).  If using an RNAV approach make sure that VNAV is disengaged at the MDA.

• Speed management is critical as you are flying at low altitude in landing configuration.  A stable approach is paramount.

• Do not construct a route in the CDU to overlay onto the circle-to-land route.  The procedure is designed to be flown using HDG SEL. 

• The circle-to-land is VFR.  Do not end up 'tail-up' with your head in the CDU.  Look outside!

      To learn why an overlay is not recommended, watch this video by Mentour Pilot.

Recommended Actions:

To aid in spatial awareness the following actions are suggested:

• If the Captain is flying the aircraft, try and turn right as this will place the airport on the left side of the aircraft enabling the pilot flying better visual reference.  Vice versa if the First Officer is the pilot flying (unless the direction is stipulated otherwise in the approach chart).

• Use the CDU to create distance rings and a waypoint/radial.  Use the VBI.

Flight Simulation - avionics suite

Unfortunately, not all flight simulation avionics suites are identical to each other.  This is readily apparent when using the CDU to program the FMC.  Users report subtle difference between ProSim737, PMDG and the real aircraft.  If any of the above commands do not function correctly, you will need to try and find a workaround; often this is quite easy, but does require a little lateral thought.  Hopefully, one day all major suites will be identical.

Variability

Many things in aviation can be done multiple ways.  The rules concerning the circle-to-land procedure are for the most part solid.  It would be foolish to descend below the MDA, navigate outside the 'protected area' or to continue landing when viability has obscured the runway. 

Wind, however, is one aspect that can alter the time used to fly the various legs; 30 seconds may be more prudent than 20 seconds, while an initial 40 degree turn may be more effective than a 45 degree turn.

Likewise, the boundary of the 'protected area' and the pilot's ability and confidence will determine the distance from the runway they fly.  One pilot will be confident flying a tight pattern with a continuous descending turn from downwind to final while another may want to extend the distance to enable more time to carry out the landing.  Variably is allowed provided you keep within the parameters discussed earlier.

Airline Operator Policy

In the real world, an operator will often publish their own approved limitations, including those for circling approaches. They are usually based on several factors, including the speed category of the aircraft and also a minimum height to fly at while carrying out any sort of visual approach (this is sometimes referred to as the Approach Ban).

The objective of the exercise is to fly the published procedure safely by remaining clear of cloud, in sight of the surface and keeping as close as possible to the landing runway.  This is best achieved by the pilots flying at a familiar height which is typical of a normal visual circuit.

Video and Discussion Paper

• A good video on U-Tube showing a circle-to land can be watched at: https://youtu.be/zDsaXqUVa2A.

• An interesting discussion paper concerning Circling to Approach.

Useful Points:

• Using the ILS during the initial approach is not recommended as the aircraft can easily descend below the MDA (unless you are vigilant).  Use the localiser and V/S.

• If the ILS glideslope is used, enter into the altitude window the MDA + 500 feet.  Then, when the altitude horn sounds (750 feet ASL) change the descent mode to V/S with an appropriate descent rate.  This will ensure that the aircraft does not descent below the MDA.

• As you descend to the MDA dial the offset heading into the heading window (rather than wait until you reach the MDA).  Then, when you reach the MDA and ALT HOLD is displayed on the MDA select the HDG selector.

• When turning to the offset course, always use a 45 degree turn left or right for roughly 20 seconds (factor in wind).

• Change the degree of bank selector to 20 degrees (if using the MCP to navigate the aircraft).

• To aid in spacial awareness, set-up a suitable approach in the FMC so that navigational cues can be followed when turning to final (for example, an IAN Approach will display diamond markers on the PFD.  Using the Vertical Bearing Indicator (VBI) in CDU will display a rate of descent to the runway threshold).

• When flying downwind, it can be advantageous to fly a little longer than the time calculated.  This enables more time to turn to final and stabilise the aircraft prior to reaching 1000 feet ASL.

• Select gear down when adjacent to the runway (if not before).  Then, after flying the stipulated downwind time select landing flaps, set speed, and set a 300 feet descent rate using V/S.  Then begin the turn to final.

• At 300 feet AGL the aircraft wings should be level and the aircraft aligned to the runway.

Final Call

The circle-to-land approach is not difficult, however, depending upon your flight simulator set-up, it can be challenging because you cannot look out of a physical window and see the airport.  By far the most important variables are speed management and a stabilised approach regime.

Review and Updates

Released 27 May 2022. 

Updated 01 June 2022.

Changing the Font Style and Colour in CDU

View fullsize

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.

View fullsize

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:

<smallFontColor>Lime</smallFontColor>

<largeFontColor>White</largeFontColor>

Type the required colour replacing the bolded section above.

View fullsize

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.