RAAS Professional By FS2Crew - Review

/

KLAX airport diagram showing the maze that hundreds of aircraft each day must safely navigate.  Given the complexity of many airports, it's amazing there are not more runway incursions

Runway incursions are a leading cause of aviation fatalities and account for approximately $1 billion annually in aircraft damages. To help prevent such losses, close calls and collisions, the industry requested a safety system that would help maintain situational awareness during taxiing and preparing for takeoff and landing. 

Honeywell stepped in to fill the gap by developing an easy-to-install heads-up advisory system with aural alerts (call-outs) to increase flight crew situational awareness during ground and air operations relative to the runway. 

This system was then further improved upon, with the collaboration of Emirates.

I previously used a shareware version of RAAS developed by PlaneMan in South Korea.  This small FS add-on worked well, however, recently it stopped working on my system for an unknown reason.  I wrote a review on FsRAAS by Planeman in 2011.  Searching for a replacement, I came across RAAS Professional developed by FS2 Crew.  

What is RAAS

RAAS is an acronym for Runways Awareness And Advisory System (RAAS).  RAAS was developed by Honeywell Aerospace as a simple to install but effective software addition to the Honeywell Enhanced Ground Proximity Warning System (EGPWS).  Although the base-line RAAS is still in operation, Honeywell has improved the software by integrating additional aural advisory call-outs; in particular, relating to stabilised approaches.  SmartRunway and SmartLanding are the next generation of RAAS.

RAAS Professional replicates the complete aural Honeywell suite (RAAS, SmartRunway and SmartLanding), however, does not simulate the visual advisory displays.

Simulator Platforms

RAAS will operate on FS9, FSX and P3D V3 simulation platforms in 32 Bit.  A 64 Bit version of the program caters towards those using P3D V4. if using MSFS-2020 another version of RAAS is required called RAAS Professional by FS2Crew. The RAAS Professional software is more or less identical to the RAAS software but installation is slightly different.

Installation

Installation is via an installer and is straightforward.  The software installs a .ddl file which is loaded automatically when you begin a new simulation flight.  Once installed, a tab (RAAS Professional) will be added to the menu bar in flight simulator; this is where the user interface is opened to configure the program.  I did not experience any issues installing this program.

RAAS uses Simconnect to connect to flight simulator and does not require the use of FSUPIC.

Be aware that problems can occur when attempting to connect any add-on software that uses Simconnect (as opposed to FSUPIC).  If a problem occurs, the easiest way to rectify it is to re-install the Simconnect module of flight Simulator.

Initial Configuration (Managing the Runway Database)

The most important task to complete prior to configuring RAAS is to download a small standalone program called MakeRunways.  This software has been developed by Peter Dowson and is available gratis from his website.  The MakeRunways utility should be placed in your main flight simulator folder where the Scenery.cfg file is located.    

When run, MakeRunways interrogates the scenery folder and generates several database files that include, amongst other things, the runways found in flight simulator.  The generated files are automatically saved to your main flight simulator folder, for programs such as RAAS, to access and read. 

Whenever you install new scenery you must run the MakeRunways utility to ensure that the database is synchronized and up-to-date, otherwise RAAS will not work with the new add-on airport scenery.

Of importance, is that the 64 Bit version of RAAS requires an additional program to be installed.  The reason for this, is that vP3D V4 use a dedicated addons folder.  The Add-on organizer enables the add-on folder in P3D V4 to be interrogated by the MakeRunways program. 

Important Point:

  • If using RAAS Professional for MSFS-2020 MakeRunways is not required.

The Lorby Prepar 3D Addon Organizer can be downloaded gratis at the developer’s website (see downloads section). 

The installation of these programs is very straightforward and instructions are provided in the supporting documentation.

Advanced Configuration

RAAS, like its real world counterpart, is highly configurable from the User Interface (UI) accessed from the Add-Ons menu bar in flight simulator.

The following aural call-outs (advisory) are available.

  • Approaching Runway (On Ground): advisory provides the flight crew with an awareness of when a runway is being approached.

  • Approaching Runway (In Air): advisory provides the flight crew with an awareness of which runway the aircraft is lined-up with during approach.

  • On Runway: advisory provides the flight crew with an awareness of which runway the aircraft is lined up with on the ground.

  • Runway End: advisory is used to improve crew awareness of the runway end during low visibility operations.

  • Taxiway Take-off: advisory alerts pilots to excessive taxi speeds or an inadvertent takeoff on a taxiway.

  • Insufficient Runway Length (On Ground): provides the crew of an awareness of which runway the aircraft is lined-up with and if the runway length available is less than the defined minimum takeoff length.

  • Extended Holding on Runway: alerts the crew of an extended holding period on the runway.

  • Approaching Short Runway (In Air): offers an advisory of which runway the aircraft is lined-up with and if the runway length available is sufficient as defined in the Runways section.

  • Taxiway Landing: alerts the crew if they are not lined up with a runway at low altitudes.

  • Takeoff Flap Monitor: alerts the crew if the aircraft's flaps are not in the defined takeoff range.

  • Landing Distance Remaining: provides the flight crew with an awareness of the runway length remaining during roll-out.

  • Distance Remaining (Rejected Takeoff): provides the flight crew with an awareness of the runway length remaining during a rejected takeoff.

  • Landing Flap Monitor: advisory alerts the crew if the landing flaps are not set.

  • Excessive Approach Speed: is an alert if the aircraft speed become excessive compared to the final approach speed.

  • Excessive Approach Angle: is an alert if the aircraft's approach angle becomes too steep.

  • Altimeter Setting (Above Transition): alerts the crew if the altimeter is not set to standard after climbing above the transition altitude.

  • Altimeter Setting (Below Transition): provides the flight crew with an awareness of improper corrected altitude setting while below the transition altitude.

  • Long Landing: alerts the flight crew if the aircraft has not touched down within the defined Touchdown Zone Length.

  • Caution Enabled: adds the phrase ‘Caution’ to select aural calls.

Any of the aural call-outs can be turned on or off and several parameters are configurable from the UI.  Additionally, specific parameters can be changed depending upon aircraft type or airline policy, such as:

  • Aircraft type.

  • Runway takeoff and landing length, runway length and touchdown zone. Hold times (initial hold time and repeats).

  • Flaps configuration (takeoff, landing, upper and lower altitudes).

  • Approach speeds.

  • Transition altitudes.

  •  Extended hold times and frequency of the aural call-out.

If you fly different aircraft, any number of user profiles can be created.  The profiles are associated with the aircraft type selected in flight simulator.

rAAS Professional User Interface (UI)

Comparison - RAAS Professional to the  Honeywell System

RAAS Professional by Fs2Crew replicates the real Honeywell system surprisingly well.  The aural call-outs are identical and the female voice sounds very similar to the voice used by Honeywell - which provide either a female or male voice.  If you’re keen to compare RAAS to the Honeywell system I recommend you visit the Honeywell website, search RAAS and watch the videos.

Turning RAAS On and Off (RAAS Master Switch)

RAAS can be turned on and off ‘on the fly’ from the User Interface (UI), or by assigned a hot-key (key event API) in flight simulator.  By default the on/off function has been assigned to the water rudder (R) function (from within the flight simulator control panel).  It is also possible to assign this functionality to a switch/toggle.

Sound Cards and System Test

RAAS has been designed to be used within multiple speaker environments, and changing the speaker preference is made directly in the User Interface (UI).  With a little tinkering you should be able to dedicate the RAAS aural call-outs to a separate speaker while maintaining engine noise and Air Traffic Control to other speakers and a headset.  A master volume control tab enables the sound levels to be adjusted (if the speaker does not have volume control knob).

The UI has a System Test to determine correct configuration and connection (audio test) and an error log.  The error log can be used during troubleshooting (if necessary).  

Voice Sets and Memory Use

Currently RAAS only supports English in a female voice.  I believe that additional foreign language voice sets may be released in due course.

When RAAS is running, there is no discernible effect on the computer or flight simulator.

Support

A detailed and easy to read manual is supplied with the program.  The manual, in addition to providing detailed installation instructions, also has a very good troubleshooting section in the unlikely event that you have problems during the installation process.

RAAS supports a dedicated support forum and the developer replies to questions when asked.  

Program Shortfalls

At the moment it is not possible to install RAAS on a client computer and run the program across a network.  Although RAAS does not use a lot of computer resources, some users may wish to display the UI (when required) on a client screen in association with the Instructor Station.

Another shortfall is the inconsistent operation of the key event API (that enables you to connect a switch/toggle to the on/off function / RAAS Master Switch).  Sometimes it works and at other times it does not work correctly.

Final Call

If you seek realism, RAAS is a worthwhile addition to flight simulator.   When configured to an appropriate aircraft, the aural call-outs are timely and helpful to situational awareness.  Two features I particularly like are the ability of RAAS to remind you to set the appropriate flaps detente prior to takeoff, and the aural call-out that is generated which identifies the runway you are aligned with during final approach.

I must admit there was one occurrence when I was conducting a VOR approach to a parallel runway in limited visibility.  The aural call-out stated I was aligned to runway 24 Left when I was supposed to landing on runway 24 Right!  But isn’t this the reason RAAS was designed – to stop incursions and provide situation awareness to flight crews.

References and Affiliation

This article was written with reference material obtained from Honeywell Aerospace.  

Please note I have no affiliation with FS2Crew.  I have not been provided with ‘free’ software, nor did I receive a discount in return for a favourable review.  The comments and recommendations I have made are my own.  Further information on RAAS Professional can be obtained directly from the FS2Crew website.

Flight Simulator, in this article, refers to FSX/FS10.  I use the B737 avionics suite developed by ProSim-AR.

BELOW:  Honeywell promotional video (courtesy & with permission Honeywell).

 
 

BELOW:  RAAS Professional promotional video (courtesy FS2Crew).

 
 

TaxiSigns HD - Review

/

Example of the high definition sign showing night lighting which creates a pleasing  illumination in front of sign.  This feature is missing in the default textures

A small add-on program which may interest some is TaxiSigns HD.  Essentially this software replaces all the default taxiway signs in flight simulator (FS) with a selection of several higher resolution 3D images with enhanced lighting effects.  For those that spend considerable time taxiing the aircraft this program is sure to please.

Installation and Features

Installation is via a wizard installer which will ask where you wish to install the program and also ask which directory flight simulator is installed. 

Once installed, a sub menu (TaxiSigns HD) will be placed within the flight simulator Add-Ons menu.

TaxiSigns HD works be adding its own scenery area, called TaxiSigns HD layer, to the FS scenery library.  The default textures are not overwritten or deleted and outside of its own scenery area, the program does not modify any flight simulator files.  To uninstall the product, and restore the default signs, use the Windows Control Panel to uninstall the program.  

The program has a user interface screen accessible from the FS Add-Ons menu.  The interface enables the user to easily alter the 3D model, daytime and night textures, and whether the signs illuminate the ground at night.   

One of the main advantages, other than appearance (the signs actually look like signs), is the night lighting effects.  Each sign can be front lit to allow the ground in front of the sign to be illuminated.  

The following outlines the features of the program:

  •  3D taxiway signs instead of default rectangles 

  • Crystal clear text and FAA mandated font (high resolution textures) 

  • Choice of several 3D taxiway sign textures and shading effects (day and night) 

  •  Illumination of the ground in front of each taxiway sign 
 

The user interface in which various options can be selected.  Note the posts that hold the sign

Evaluation of TaxiSigns HD

If you spend considerable time taxiing or take photographs and video within flight simulator then this program is well worthwhile. 

The textures are very sharp and the signs are much easier to read than the default textures.  They are also much more attractive to look at in comparison to the default signage.

A problem observed in flight simulator (FSX) is the slight blurring of the signs as the aircraft taxis past the sign.  The replacement textures remain sharp and do not blur as do the default signs.  Furthermore, I could not discern any appreciable drop in frame rates.

Compatibility an Support

TaxiSigns HD is fully compatible with both DirectX 9 and DirectX 10 modes of FSX, and also with FS9 and Prepar3D (versions 1.0-5.0).  

A succinct manual is provided with the program and although the program is very simplistic, a support forum is available.

  • The program can be downloaded from the developers website and tested for a period of 10 minutes: TaxiSigns. HD

Note I do not have any affiliation with the software developer.

White Caps for Locking Toggle Switches on Overhead

/

Lower electrical panel showing reproduction latex-style cap (ELEC 2) and OEM Honeywell Switch Accessory 15PA90-6W (ELEC 1). For those with keen eyes - yes that is a voice recorder in the lower panel - more to follow in later posts.  Of interest are the two different white caps (read main text)

It has taken a very long time to collect the assortment of OEM needed parts to complete the forward and aft overhead panels.  Finally the build is now in progress and it’s hoped completion will be towards the end of 2016.

OEM Overhead Panel Switches (2 main types)

There are two main types of switches used on the forward and aft overhead panel.  The push/throw switches (Honeywell switches pictured above) and the normal toggle-type switches.  The Honeywell switches use a screw on white cap while the standard toggle switches use use a condom style white cap.

Honeywell Switch Accessory 15PA90-6W showing internal screw thread.  The thread screws onto the stem of the toggle switch

Anatomy of the OEM White Cap

The Honeywell switch caps are not a slip-on latex cover but a solidly-produced head with an internal aluminium thread.  The head is designed to be screwed directly to the shaft of the toggle switches.  Firmly attached to this head is the white latex cap. This is the cap that is used on the push/throw switches. 

Reproductions

Most of the reproduction white caps for the push / throw switches are either push-on style condoms, or a white-capped head attached to a slender hollow shaft.  The shaft then slides over the existing switch stem. 

The reproduction slip-on caps currently available on the market bear little resemblance to those made by Honeywell.

Important Point:

  • Bear in mind that the push / throw switches are used regularly and are usually forcefully manipulated; many reproductions do not stand up to continued abuse.

Choice - so many options

I had purchased several dozen OEM Honeywell toggle switches, however, for whatever reason the white caps on the toggles were either missing or damaged.  Honeywell OEM switches are not inexpensive, so I was going to use reproduction white push-on caps (aka white condoms), but the caps failed to  fit snugly to the OEM switches, and their appearance was slightly different to the OEM version - the ends of the caps looked rather bulbous.

My next choice was to use latex caps that are used in automotive industry.  Once again, the appearance was slightly different and the automotive caps sported a small nipple at the end of each cap where they had been connected to the plastic retaining spur; I found the appearance of the nipple disconcerting.

Short of viable options, I purchased the OEM white caps from Honeywell which is the company that supplies Boeing.  If you carefully look at the above picture of the lower electrical panel (click image to enlarge picture), you will observe the nearest toggle switch has been fitted with an automotive style cap; the nipple and joining line is clearly visible.  The second toggle switch is fitted with the Honeywell white cap.

Installing the White Toggle Cap

To mount the white cap to a Honeywell switch you must first gently heat the switch stem.  The heat will loosen the head of the toggle.  It then is an easy matter to screw off the head and replace it with the OEM head.  To heat the stem use either a hair dryer or paint dry gun (used to dry paint).

Measurements

Not everyone wants to utilise OEM parts.  As such I have provided the measurements of the switch head (courtesy of Honeywell) for those who wish to try their hand at making their own white caps.

If you are searching for the other style of white caps used on the standard toggle switches, the part number for the correct condom white cap is 69-44578-2.

Reproduction Condoms - suppliers

For those not wishing to use OEM, there are several companies that manufacture reproduction white toggle caps.  For example, PC Flights and GLB United Kingdom.

Glossary

  • Honeywell – Avionics conglomerate that is heavily involved in the defense and aviation industries.

  • OEM – Original Equipment Manufacture.

Assembly of Forward Overhead Panel

/

Forward overhead using OEM parts

Construction of the simulator began in 2011.  It is now 2016 and I am perplexed to why the build has taken so long to complete.   Of course, opting to try and use OEM (Original Equipment Manufacture) parts whenever possible has added significant time to the project - especially the procurement of parts.

Most of the parts that make up the forward overhead have now been obtained and assembly of the components is well advanced.   Very soon the wiring from the panels to the Phidgets cards will begin.  This will be followed by several hours of testing to check correct functionality and to ensure perfect harmony between components and systems. 

A basic frame has been constructed to enable the overhead to be easily positioned to enable the wiring to be done with a little more ease.  After the forward overhead is completed, work on the aft overhead will commence.  Rome, it seems, was not built in a day.

Certainly, completion of the forward overhead will be the major project over the next few months.

FS-FlightControl Instructor Operating Station (IOS) - Review

/

Opening screen for FS-FlightControl IOSon the server computer.  IOS can be easily configured to automatically open after Windows start-up

Virtual flyers can be grouped into three broad groups.  Those that are satisfied using a desktop simulator, those that gravitate toward a professional simulator, and those that strive to replicate, as close as possible, a Level D simulation.  No matter which group you belong, there is a requirement for a feature-rich, reliable, and stable Instructor Operator Station (IOS).

This post will introduce the Instructor Station FS-FlightControl, developed by AB-Tools GmbH, a company located in Germany.  The review is not meant to be comprehensive as such a document would be as long as the product’s operating manual.  Rather, we will examine some of the product’s features prior to making an assessment of the software’s reliability and ease of use.

What is IOS - Do I need It

IOS is an acronym for Instructor Operating Station.  At its simplest, it's the menu system in Flight Simulator that enables you to choose from several parameters to create a pre-programmed flight scenario. 

A dedicated instructor station is far more than a few options to alter the time, place, and scenario in the simulator.  A good instructor station should enable you to set basic flight scenarios, in addition to being able to monitor set tasks and parameters.  The software should provide clear and readable displays, be set out logically, be easy to operate, and also be able to initiate system failures.  Furthermore, the software must be stable, reliable and consistent in its output.

There are several Instructor Operating Stations available on the market and most high-level avionics suites come with a ready-made IOS as part of their software.  Therefore, the question must be asked - why is there a need to purchase a stand-alone IOS.  

Put bluntly, many generic instructor stations have been added at the back-end of an avionics suite.  These instructor stations can lack functionality, features, and ease of use.  Furthermore, their layout is often not optimal or configurable.

Screen shot showing the POSITION page display of IOS.  Note the easy to navigate menu at the bottom area of the screen (twelve modules).  This menu system is available on allIOS pages and enables quick and easy navigation between modules

IOS Features - FS-FlightControl

The features and functionality that are supported by IOS are extensive, however, bear in mind that the instructor station has been designed to operate across different simulator platforms and avionics suites; not every feature may operate with the intended avionics suite.  For example, flight plans can be generated and sent to FSX in the standard .pln format, but they cannot be send directly to ProSim-AR in the correct format (as at the time of writing).

I have purposely not duplicated what has already been written on the FS-FlightControl website.  The website provides a well detailed description of the features and functionality of the software and includes numerous screen shots.

Broadly speaking, IOS has been developed around 12 main modules.  Like-minded themes have been grouped into whatever module is specific to the subject.  If the information exceeds what can be displayed on one page, then one or more sub-pages (sub-tabs) are provided.  There is a gamut of features

Main Modules

Position:   Aircraft re-position, runway preference, aircraft scenario, approach presets, airport selection and re-position options.

Map:   Street map, satellite map and height map.   Navaids, AI aircraft, weather, aircraft location, compass and route/flight plan overlay.

Flight Planing: Route and flight plan generation with load tool.  Importing and exporting of data with flight plan generated onto roving MAP.

Conditions:   Environmental conditions relating to weather (artificial and real-time), visibility (CAT presets), winds, clouds, precipitation, altitude levels, barometric pressure, presets, time and season, accelerated time, and user-generated conditions.  This section is very detailed and is examined in several sub-tabs.  Many of the presets are as easy as clicking a button on the screen.  For example, ILS visibility conditions can be generated by clicking one of the CAT buttons (CAT I, II, III, IIIa/b/c).

Push back:   Graphical interface enabling push back of aircraft at any angle and distance.

Fuel/Load:   Fuel volume, passenger, crew and cargo weights, aircraft weights (ZFW), center of gravity (%CG) and load tool.

View/Slew:   Alters external camera views of aircraft and enables the slewing of aircraft.

Failures:   Aircraft system failure conditions that can be triggered immediately, at pre-defined times, or at random.

Statistics:   Approach statistics - Graphical representation of aircraft in relation to vertical and lateral position, aircraft position, ground altitude, vertical speed, pitch, and bank angle.  Results can be exported to Google Earth for further analysis.

Network:   Module to control all computers and software within your simulation network (server and any number of client computers).

Aircraft:   Selectable list of aircraft options re: altitude, speed, direction, radios, TCAS alert status, engine parameter outputs, throttle outputs, autopilot, light and switches, etc. 

Settings:   Customization of all aircraft, map, and program parameters: colours, fonts, map layouts, etc.  Additionally, other variables can be customised such as CAT visibilities and decision heights.

Favoured Features

I’ll be honest, the more I use IOS the more I enjoy my simulation experience.  At the very least, IOS provides a reliable way to store various approach scenarios to numerous airports at different times, seasons and weather conditions.   Granted, that this can be done from the flight simulator menu, however, it cannot be done as cleanly nor as quickly as it can from the IOS module.

Although I do not use all the features available in the program, there are several that I continually use.  It is these I will discuss in further detail.

POSITION:  Position refers to the position of the aircraft whether it be on the ground or in the air.  IOS enables the user to select from several ground positions such as the gate, runway, terminal, base approach, straight-in approach, etc. A click of the mouse will position your aircraft to any of several preset locations. 

I find this to be a very good time saver, especially if you do not want to simulate a long taxi or some other part of the flight but wish to concentrate only on one aspect – such as the approach phase.  In addition to various presets, this page also allows customized approaches to be generated and saved.

Another aspect of this page deserves mention; the ability to select a chosen aircraft livery, parameter list (fuel state, trim, radio frequencies, etc) and save this to custom-named 'slot'.  This is another time-saving feature and easy method to choose a pre-saved livery of an aircraft type.

STATISTICS:   For those who fly by the numbers and want to improve their approach techniques, the statistics section provides a graphical interface that records the vertical and lateral deviation of the approach.  It also records airspeed, vertical speed and several other characteristics.

CONDITIONS:   Conditions broadly refers to environmental and weather conditions at the airport selected, or at various pre-selected waypoints or weather stations.  Changing weather conditions, visibility, season and time is as easy as clicking a button.

This page is exceptionally feature-rich and the instructor station can generate live weather, weather from an imported METAR string or any number of pre-saved weather themes.  For those interested in setting up specific weather events, for flight training, it is very easy to do so.  

Screenshot showing MAP display page.  Many advanced features that can be displayed as a map overlay.  The tabs along the sides of the page can be clicked to turn features on or off

MAP:  The map is a hidden gem that enables you to overlay a wealth of information onto a street or satellite map of the area of operation. 

For example, the user aircraft and AI aircraft are graphically represented along with all navigation aids which includes VORS, NDBs, high and low jetways, ILS feathers and waypoints.  Wind direction and current barometric pressure can also be displayed along with the current SID, STAR or route.  Whilst on the ground all aprons, runways and taxiways are shown.  Navigating to an assigned runway could not be easier as the user aircraft icon shows the position of the aircraft at all times. 

As with all windows, the MAP can be displayed as a separate screen on another monitor.  Therefore, it is possible to have IOS open on two monitors with one monitor showing the MAP view while the other monitor displays a different view.

An added advantage is the ability to position your aircraft anywhere on the map and create a position fix along with altitude, direction, pitch, bank, airspeed and radio frequencies.  This information can be saved for future activation from the POSITION page.  This enables you to quickly and easily set-up an approach and save this approach for future use.

For those that fly on-line, VATSIM, IVAO and PilotEdge are supported.

NETWORK: IOS enables the user to program the software to control what programs open or close on any computer that is connected to the network.

For example, I use a batch file  to open and close flight simulator, ProSim-AR and other FS related programs (weather, flight analysis, etc).  IOS when turned on from the client will automatically execute the opening of the batch file on the server computer.  Likewise, when triggered, IOS will engage the batch file I use to close flight simulator and other ancillary programs.  Additionally, a time delay can be configured to cause a delay between the closure of programs and the turning off of the server computer.  

Screenshot showing the PUSH BACK display page

Installation of IOS - Server and Client

The software package is downloaded from the developer’s website and consists of a self-extracting .exe file. 

As IOS has networking capability, it's not necessary to install IOS to the computer that has flight simulator installed; it will operate on a client computer.  Additionally, a wizard is used to direct you through the installation process and configuration.  Networking to a client is done via SimConnect.  FSUPIC and WideFS are not required.

Although networking is achieved through the use of SimConnect which can, at times, be problematic, I did not experience any issues.

Configuration

Configuring the program to suit your requirements is done from the SETTINGS page.  Variables can be altered for each aircraft, and aircraft profiles can easily be created that save particular parameters or conditions.  Likewise, the software can be altered to enable a particular font style and colour to be displayed along with a zoom value and size.  The process is straightforward.

Pretty much everything in IOS is able to be configured to your liking.

One aspect of IOS I found to be very handy, was that when you close the instructor station it will keep the last known settings.  This means the parameters for the next flight session (if not altered) will be identical to the last.

Ease of Use

Screenshot showing the FAILURES display page.  Note the open conditions call-out box.  There are several sub-pages (sub-tabs) that deal with failures.  Failures are an important asset to enthusiasts striving for realism

The IOS program is set-out intuitively and the various pages (modules) follow a logical sequence with like-minded themes bundled together on the same page.  The twelve page main menu located at the bottom of each page is promulgated across all pages and enables quick access to various features. 

Unlike other instructor stations, all information relating to a specific theme is located on the one main page (for example, failures or position page); it is not necessary to navigate between several pages trying to find the information.  Furthermore, the screen display can resized to either fill your display or only part fill it.

Another advantage is the implementation of large-style buttons that enable quick and accurate identification of a module.  Everything is easy to find and access.

Program Administration

Program administration encapsulates the opening and closing of programs from one or multiple computers. 

Without an instructor station or the use of batch files, several programs must be opened on the client and server computer to begin a flight.  This takes time and the process can be unwieldy.

If the instructor station is configured correctly, it is a two-step process to begin a flight.  First the computers must be turned on.  Second, from the client the FS-ControlControl IOS icon is depressed.  Once IOS opens on the client computer it will communicate with the server computer (via SimConnect) and open any number of programs on the server (assuming they have been configured correctly in the IOS NETWORK page).  

Once Flight Simulator opens and you are on the flight line it’s only a matter of using the instructor station to alter any variables particular to the flight (airport, aircraft position, weather, fuel, weight, etc).  All changes are automatically promulgated across the network to Flight Simulator.

The important aspect to note, is that other than turning on the server and client computers, everything is done from the one screen on the client computer using the one mouse/keyboard.  Likewise, when closing the simulator session everything can be done, including turning off the server computer, from the instructor station.

Cross-Platform Operations

The IOS operates with Microsoft Flight Simulator X (FSX/FS10) including Steam Edition, and with Lockheed Martin Prepar3D® 1.x, 2.x and 3.x. in a Windows environment.  A separate APP is available for Android and Apple (iOS).  The software works traditionally using the keyboard and mouse in addition to being optimized for touch screens.  IOS can be run either on the computer that has Flight Simulator installed or from a networked client computer.

Stability and Speed

The last thing anyone wants is a crash to desktop caused by a bug-ridden piece of software that exhibits stability issues, poor performance, and does not operate consistently.  

The stability of the instructor station is excellent.  In my simulator set-up the IOS is installed on a client computer and networked to Flight Simulator located on a server computer.  The software loads quickly and interacts with the simulator seamlessly.  

The speed at which software interacts with Flight Simulator is important and it’s pleasing to note that IOS commands do not exhibit any significant time lag between the client and server computers.  There is no time lag when switching between any of the interface screens on the instructor station.  Surprisingly, this includes the MAP mode.  Often a high definition map with several overlays cannot generate its resultant map within an acceptable time. 

This said, internet connection speed may cause users to experience different speeds.

The time taken to open the instructor station from the icon on the client computer is approximately 10-15 seconds.

Screenshot showing the CONDITIONS display page.  This page has several sub-pages that deal with conditions.  For example, real weather, presets, season, ILS visibility and accelerated time.  Note the display box in the lower left side that shows the frame rates

Updates to IOS (Annual Fee)

The software developer is very proactive and software updates with improvements, minor fixes and new features are regularly provided free of charge.  

However, the update period is only for one year following purchase.  After this period has lapsed, an annual fee will need to be paid to enable future updates to be used.  The annual fee is only for updates, the original software will still function.

Do you need to update ?  If you are happy with what you have, then no.  However, if you are seeking specific functionality then an update may have this functionality.  A list showing the updates can be read in the INFO section of the software. 

The developer realizes that each person’s requirements for an instructor station is different, and as such, entertains ideas and suggestions for additional features or improvements from end-users.

Support

FS-FlightControl does not have a dedicated forum, however the developer replies promptly to all e-mails sent via the software help page.  

A benefit of sending e-mail directly from the software is that the log files from your system are automatically attached to any outgoing message.  This enables the developer to easily understand the issue, saves time in asking for further information, and leads to a faster resolution.

Dedicated Manual

A manual for any in-depth software is an absolute necessity.  It is pleasing to note that the developer has written a manual and does not rely on a forum to provide answers to common questions.

The manual, which reflects the latest software build, is accessed from the FS-FlightControl IOS website.  If necessary a .pdf is available on request.  

Additionally, the manual can also be accessed directly from the software.  Each page has several small question marks (?) that when clicked navigate the user to the appropriate help section in the manual.  If you find the questions marks unsightly, then they can be turned off from the SETTINGS page.

Software Trial

This review has only examined several of the features that the instructor station is capable of.  To enable a comprehensive examination of the software, IOS can be installed with full functionality (including any prospective updates) for a period of 14 days.  After this time has elapsed, the software will need to be purchased.

Final Call

Considering the scope of what an instructor station does and how it can be used to enhance the effectiveness of a simulator, there is little doubt that a good IOS is essential.    

I've spent considerable time using the FS-FlightControl IOS and although this review touches on but a few of the features of IOS, I believe this software to be superior to other contemporary products.   It certainly has enhanced how I use the simulator leading to a more enjoyable experience.

The IOS software and further information can be downloaded at FS-FlightControl IOS.

  • Please note I have no affiliation with FS-FlightControl.  I have not been provided with ‘free’ software, nor did I receive a discount in return for a favourable review.  The comments and recommendations I have made are my own.

  • Flight Simulator, in this article, refers to the use FSX/FS10.  I use the B737 avionics suite developed by ProSim-AR.

Update

Since this review there have been several updated releases that have implemented a number of new ideas and rectified shortcomings.

ProSim-AR users will be pleased that an update includes the ability to import and export flight plans to the ProSim-AR database as an .xml file (10 character file name).  The update also enables synchronisation with the FMS, and display of the flight plan on the IOS map.

VNAV 'Gotchas' - Avoiding Unwanted Level-Offs

/

RAAF 737-800 Wedgetail transitioning a STAR into YSSY (Sydney Australia)

One aspect of using VNAV during published instrument departures, arrivals, and approaches is that it can cause unnecessary level-offs. 

These level-offs can cause engines to spool needlessly, increase fuel cost and stagger a Continuous Descent Final Approach (CDFA) such as when executing  an RNAV approach. 

It is not only domestic airliners that must meet altitude constraints; military aircraft also  must meet the same requirements when landing at a non-military airport (click to enlarge).  Image is copyright xairforces.net.  For those interested in flying the Wedgetail, there is a model available for ProSim-AR users on their forum page.

To avoid this, and ensure that minimum altitude constraints are met, two techniques can be used.

METHOD 1:  Constraints Are Not Closely Spaced.

This technique is normally used when waypoints with altitude constraints are not closely spaced (in other words, there is a moderate distance between altitude constraints).

During climbs, the maximum or hard altitude constraints should be set in the Mode Control Panel (MCP).

Minimum crossing altitudes need not be set in the MCP as the FMC message function will alert the crew if these constraints cannot be satisfied.

During descent, the MCP altitude is set to the next constraint or clearance altitude, whichever will be reached first.

Immediately prior to reaching the constraint, when compliance with the constraint is assured, and when cleared to the next constraint, the MCP altitude is reset to the next constraint/altitude level.

METHOD 2: Constraints Are Closely Spaced.

Where constraints are closely spaced to the extent that crew workload is adversely affected, and unwanted level-offs maybe a concern, the following is approved:

For departures, set the highest of the closely-spaced constraints.

For arrivals, initially set the lowest of the closely-spaced altitude constraints or the Final Approach Fix (FAF) altitude, whichever is higher.

IMPORTANT: When using either technique, the FMS generated path should be checked against each altitude constraint displayed in the CDU to ensure that the path complies with all constraints.  Furthermore, the selection of a pitch mode other than VNAV PTH or VNAV SPD should be avoided, as this will result in the potential violation of altitude constraints.

To enlarge more on VNAV is beyond the scope of this post.  A future post will address this topic in more detail.

Crew Controls Automation - Not Vice Versa

However, the system is only as good as the knowledge of the person pushing the buttons.  It is very important that a flight crew control the automation rather than the automation control the flight crew. 

If VNAV begins to do something that is unplanned or unexpected, do not spend precious time ‘thinking about the reasons why’ – disconnect VNAV and use a more traditional method or hand floy the aircraft.  Then, determine why VNAV did what it did.  The most common comment heard in today's modern cockpits is ‘What is it doing now…’

Final Call

VNAV is an easy concept to understand, but it can be confusing due to innumerable variables associated with vertical navigation.  VNAV is probably one of the more complicated systems that virtual and real pilots alike have to understand.  When using VNAV it is paramount to maintain vigilance on what it is doing at any one time, especially during descent and final approach.     Furthermore, it is good airmanship to always have a redundancy plan in place – a ‘what if’ should VNAV fail to do what was anticipated. 

The below article also discuss VNAV:

An interesting article concerning VNAV:

Acronyms and Glossary

  • CDU - Control Display Unit (aka FMC)

  • FAF – Final Approach Fix

  • FMC - Flight Management Computer

  • FMS - Flight Management System.  Supply of data to the FMC and CDU

  • Gotcha - An annoying or unfavorable feature of a product or item that has not been fully disclosed or is not obvious.

  • LNAV – Lateral Navigation

  • MCP – Mode Control Panel

  • NPA - Non Precision Approach

  • VNAV – Vertical Navigation

  • VNAV PTH – Vertical Navigation Path

  • VNAV SPD – Vertical Navigation Speed

RNAV Approaches

/

RNAV 07 L - one of several RNAV approach charts for Los Angeles International Airport (LAX).  The most important aspect of an RNAV approach is that it is a Non-Precision Approach (NPA).  Note the word GPS is written in the title of the approach plate

My previous post provided of overview on RNAV and RNP navigation.  This article will explain what a RNAV approach is, provide incite to the operational requirements, and discuss the approach.  I will also briefly discuss Approach Procedures and Vertical Guidance (APV) and RNP/ANP values.

The operational criteria for RNAV approaches is complicated and not easy to explain.  There are a number of RNAV approaches (often different for differing areas of the globe) and each is defined by the accuracy of the equipment used in the execution of the approach.  As such, this article is not all encompassing and I encourage you to read other technical articles available on this website and elsewhere.

RNAV Approaches - Background Information

The Global Positioning System (GPS) is the brand name owned by the US military.  Initially all RNAV approaches were GPS orientated, however, in recent years this has changed to include Global Navigation Satellite System (GNSS) applications.  GNSS applications are not owned (or controlled) by the US military.  As such, an RNAV approach chart uses the words GPS and GNSS interchangeably.

What is an RNAV Approach

The definition for an RNAV approach is 'an instrument approach procedure that relies on the aircraft's area navigation equipment for navigational purposes'.  In other words, a RNAV approach is any non ILS instrument-style approach that does not require the use of terrestrial navigation aids such as VOR, NDB, DME, etc. 

Rather than obtain navigational information directly from  land-based navigational applications, the aids for the approach are obtained from a published route contained within the aircraft's Flight Management System (FMS) and accessible to the crew through the Control Display Unit (CDU).   Broadly speaking, the  approach uses signals, that are beamed from navigational satellites orbiting the Earth, and compares this data with the information from the FMC navigation database.

All Boeing Flight Management Systems (FMS) are RNAV compliant and have the ability to execute an RNAV approach.

Important Point:

  • An RNAV approach is classified as a Non-Precision Approach (NPA).

Non-Precision Approaches (NPA)

Before writing further, a very brief overview of Non-Precision Approaches is warranted.

There are three ways to execute a Non-Precision Approach.

(i)   IAN (integrated Approach Navigation).   IAN is a airline customer option and makes a NPA similar to an ILS approach.  A separate article has been written that addresses IAN.

(ii)   Vertical Speed (V/S).  V/S is not normally used when flying a RNAV approach that uses positional information from the aircraft's database.  However, V/S can be used for other Non-Precision Approaches and to transition to a RNAV approach.

(iii)   VNAV (Vertical Navigation).  VNAV is the preferred method to execute an NPA (provided the approach is part of the FMS database). 

(iv)   LNAV (Lateral Navigation).  LNAV is mandatory for all approaches that are GPS/GNSS/RNP based.

RNAV Approach Types

The following are RNAV approaches:

(i)    RNAV (GPS) approach;

(ii)   RVAV (RNP) approach;

(iii)  RVAV (RNP) AR approach; and,

(iv)  RNAV (GNSS) approach.

The RNAV (GNSS) approach can further be sub-divided into an additional three possible types of approach, each identified by a different minima.  These approaches are:

(i)    RNAV (GNSS) LNAV;

(ii)   APV Baro VNAV approach;

(iii)  APV SBAS approach.

It's easy to become confused by the various types of RNAV approaches, however, the actual flying of a RNAV approach does not differ greatly between each approach type.  The main difference lies in the level of accuracy required for the approach to be flown.

Approach Procedures with Vertical Guidance (APV)

APV refers to any approach which has been designed to provide vertical guidance to a Decision Height (DH).  An APV approach is characterised by a constant descent flight path, a stable airspeed, and a stable rate of descent.  This type of approach rely upon Performance Based Navigation (PBN).

The difference between the two APV approaches (ii and iii mentioned above) is that an APV Baro VNAV approach uses barometric altitude information and data from the FMS database to compute vertical guidance.  in contrast the APV SBAS approach uses satellite based augmentation systems, such as WAAS in the US and Canada and EGNOS in Europe, to determine lateral and vertical guidance. 

I will now discuss the RNAV (GNSS & RNP) approach.

Flying The RNAV (GNSS) Approach

The RNAV (GNSS) approach is designed to be flown with the autopilot engaged.  The recommended roll mode is LNAV or HDG SEL.  The preferred method for pitch is VNAV.  If LNAV and VNAV are engaged, the aircraft will fly the lateral and vertical path as determined by the FMS database; the route is displayed in the LEGS page of the CDU.

The aircraft uses the FMS database to determine its lateral and vertical path.  As such, it is very important that the RAW data published in the navigational database is not altered by the flight crew.  Furthermore, the data presented in the CDU should be cross-checked with the data on the approach chart to ensure it is identical.

As discussed previously, an RNAV (GNSS) approach is classified as a Non-Precision Approach.  Therefore, minima is at the Minimum Descent Altitude (MDA).   It is good airmanship to add +50 feet to the MDA to reduce the chance of descending through the MDA.  If a RNAV (RNP) or APV approach is being flown, the minima changes from a MDA to a Decision Height (DH). Whatever the requirement, the minima will be annotated on the approach chart.

LIDO chart (Lufthansa Systems) depicting the RNAV (RNP) 01 approach into BNE-YBBN (Brisbane Australia).  Note that this chart has a Decision Altitude (DA) rather than a Minimum Descent Altitude (MDA).  Chart courtesy of NaviGraph

RNAV (RNP) Approaches

RNP stands for Required Navigation Performance which means that specific navigational requirements must be met prior to and during the execution of the approach.

There are two types of RNAV (RNP) approaches:

(i)   RNAV (RNP) approach; and,

(ii)  RNAV (RNP) AR approach.

Both approaches are similar to a RNAV (GNSS) approach, however, a RNAV (RNP) approach, through the use of various sensors and equipment, achieves far greater accuracy through the use of Performance Based Navigation (PBN), and can therefore be flown to a DA rather than a MDA.

RNP/ANP - How It Works

An RNAV (RNP) approach compares the position that the aircraft should be in with the actual position of the aircraft.  If this value exceeds the prescribed distance (RNP exceeds ANP), the approach must be aborted.    The use of RNP/ANP enables greater accuracy in determining the position of the aircraft.

RNP/ANP Alerts

If an anomaly occurs between RNP and ANP one of two RNP alerts will be generated:

(i)    VERIFY POSITION - displayed in the scratchpad of the CDU; or,

(ii)   UNABLE REQD NAV PERF-RNP - displayed on the Navigation Display (ND) (if EFIS is set to MAP). 

It should be noted that different versions of CDU software will generate different alerts.  This is because newer software takes into account advances in PBN.  To determine which software version is in use, press IDENT from the CDU main page (LSK1L) and check OP PROGRAM.  ProSim-AR uses U10-8a.

The variables for RNP/ANP can be viewed in the CDU in the POS REF page (page 3), the LEGS page when a route is active, and also on the Navigation Display (ND).

A second type of RNP approach is the RNAV (RNP) AR approach.  This approach enables you to have curved flight paths into airports surrounded by terrain and other obstacles. Hence why special aircraft and aircrew authorization (AR) is required for these approaches.  Other than AR and additional flight crew training, the approach is identical to the RNAV (RNP) approach.

Advantages of RNAV and RNAV (RNP) Approaches

The benefit of using an RNAV approach over a traditional step-down approach is that the aircraft can maintain a constant angle (Continuous Descent Final Approach (CDFA)) until reaching minima.  This has positive benefits to fuel savings, engine life, passenger comfort, situational awareness, and also lowers flight crew stress (no step-downs to be followed).   Additionally, it also minimises Flight Into Terrain (CFIT) events.

A further advantage is that the minimas for an RNAV approach are more flexible than those published for a standard Non-Precision Approach not using RNAV.  RNAV approach charts have differing descent minima depending upon the type of RNAV approach.

For example, if flying a RNAV (RNP) approach the MDA is replaced by a DH.  This enables a lower altitude to be flown prior to a mandatory go-around if the runway threshold is not in sight.  The reason that a RNAV (RNP) approach has a DH rather than a MDA (and its resulting lower altitude constraint) is the far greater accuracy achieved through the use of Performance Based Navigation (PBN).

Approach To Land Using RNAV

The following addresses the basics of what is required to execute an RNAV approach.

Prior to beginning the approach, the crew must brief for the approach and complete ant required preparation. This includes, but is not limited to, the following items:

(i)     Equipment must be operational prior to starting the approach;

(ii)    Selection of the approach procedure, normally without modifications from the aircraft's navigation database (CDU);

(iii)    For airplanes without Navigation Performance Scales (NPS), the map display should be set to the 10 NM or less range.  This is to monitor path tracking during the final approach Segment and provide greater navigational awareness;

(iv)    For airplanes with NPS, the map display range may be set to whatever distance is desired;

(v)     TERR display must be selected on either the Captain or First Officer side of the ND;

(vi)     For airplanes without Navigation Performance Scales (NPS), the RNP progress page on the CDU should be displayed. For airplanes equipped with NPS, selection of the CDU page is at the crew's discretion;

(vii)    The navigation radios must be set according to the type of approach; and,

(viii)   There must be no alerts generated (UNABLE REQD NAV PERF and/or VERIFY POSITION).

In addition to the above, airline Standard Operational Procedures (SOPs) may require additional caveats.  For example, the setting of range rings on the ND to provide enhanced situational awareness at specific points (range rings can be set on the FIX page in the CDU).

Important Points:

  • Select the approach procedure from the arrivals page of the CDU and cross-check this data with that published on the approach chart, especially the altitude constraints and the Glide Path (GP).

  • If the Initial Approach Fix (IAF) in the CDU has an ‘at or above’ altitude restriction, this may be changed to an ‘at’ altitude restriction that uses the same altitude. Speed modifications (using speed intervention) are allowed as long as the maximum published speed is not exceeded. No other lateral or vertical modifications should be made at or after the IAF.

Beginning the Approach

Select LNAV no later than the IAF. If on radar vectors, select LNAV when established on an intercept heading to the final approach course. VNAV PTH must be engaged and annotated in the Flight Mode Annunciator (FMA) for all segments that contain a Glide Path (GP) angle, as shown on the LEGS page, and must be selected no later than the Final Approach Fix (FAF) or published glide path intercept point.

Speed Intervention (INTV), if desired, can be used prior to the GP.  Good airmanship directs that the next lower altitude constraint is dialled into the MCP altitude window as the aircraft passes through the previous constraint.  When 300 feet below the Missed Approach Altitude (MAA) re-set the altitude window in the MCP to the MAA.

Final Approach using RNAV

When initiating descent on the final approach path (the GP), select landing flaps, slow to final approach speed, and do the landing checklist. Speed limits published on the approach chart must be complied with to enable adequate bank angle margins. 

At minima, or as directed by the airline's SOP, the autopilot followed by the autothrottle is disconnected and a visual 'hands on' approach made to the runway threshold.

Once established on final approach, a RNAV approach is flown like any other approach.

Final Call

The Boeing aircraft is capable of several types of Non-Precision Approaches, however, outside the use of ILS and possibly IAN, the RNAV approach enables an accurate glide path to be followed to minima.  While it's true that the differing types of RNAV approaches can be confusing due to their close relationship, the approach is straightforward to fly.

This short article is but a primer to understanding an RNAV approach.  Further information can be found in the FCTM, FCOM and airlines SOP.

In my next article we will look some of the possible 'gotchas' that can occur when using VNAV.

References

Flight Crew Training Manual (FCTM), Flight Crew Operations Manual (FCOM) and airline SOP.

Acronyms and Glossary

  • Annunciator – Often called a korry, it is a light that illuminates when a specific condition is met

  • ANP - Actual Navigation Position

  • APV - Approach Procedure with Vertical Guidance

  • CFIT - Continuous Flight Into Terrain

  • DME – Distance Measuring Equipment

  • FAF - Final Approach Fix

  • FCOM - Flight Crew Operations Manual (Boeing)

  • FCTM - Flight Crew Training Manual (Boeing)

  • FMA - Flight Mode Annunciator

  • FMC – Flight Management Computer

  • FMS – Flight Management System

  • Gotcha- An unfavorable feature of a product or item that has not been fully disclosed or is not obvious.

  • GPS – Global Positioning System

  • GNSS - Global Navigation Satellite System

  • IAF - Initial Approach Fix

  • Korry - See annunciator

  • LNAV – Lateral Navigation

  • LPV - Localizer Performance with Vertical Guidance

  • MAA - Missed Approach Altitude

  • MCP – Mode Control Panel

  • ND – Navigation Display

  • NPA - Non Precision Approach

  • PBN - Performance Based Navigation

  • RNAV – Area Navigation

  • RNP - Required Navigation Performance

  • SOP - Airline Standard Operational Procedure.  A manual that provides additional information to the FCTM and FCOM

  • SBAS - Satellite based augmentation systems.  In the U.S. called WAAS and Europe called EGNOS.

  • VNAV – Vertical Navigation

  • VNAV PTH – Vertical Navigation Path

  • VNAV SPD – Vertical Navigation Speed

  • VOR – VHF Omni Directional Radio Range

  • Updated 11 November 2021

RNAV, RNP, LNAV and VNAV Operations - Overview

/

Collins Mode Control Panel (MCP) showing illuminated LNAV annunciation. This is the mcp used in the simulator. lnav is illiminated

New flyers to the Boeing 737NG often become confused understanding the various terminology used with modern on-board navigational systems.

Although the concepts are easy to understand, the inter-relationship between systems can become blurred when the various types of approaches and departures are incorporated into the navigational system.

This post will not provide an in-depth review of these systems; such a review would be lengthy, confusing and counterproductive to a new virtual flyer.  Rather, this post will be a ‘grass-roots’ introduction to the concept of RNAV, RNP, LNAV and VNAV.  I will also touch on the concept of Performance Based Navigation (PBN).

In the Beginning there was RNAV

RNAV is is an acronym for Area Navigation (aRea NAVigation). 

Prior to complex computers, pilots were required to use established on-the-ground navigational aids and would fly directly over the navaid.  Such a navaid may be a VOR, NDB or similar device.  Flying over the various navaids was to ensure that the flight was on the correct route.  Often this entailed a zigzag course as navaids could not be perfectly aligned with each other in a straight line - airport to airport. 

When computers entered the aviation world it became possible for the computer to 'create' an imaginary navigation aid based on a direction and distance from a ground-based navaid.  Therefore, a straight line could be virtually drawn from your origin to destination and several waypoints could be generated along this line.   The waypoints were calculated by the computer based on ground VORs and positioned in such a way to ensure more or less straight-line navigation.

In essence, RNAV can be loosely defined as any 'straight line' navigation method similar to GPS that allows the aircraft to fly on any desired path within the coverage of referenced NAVAIDS.

Required Navigation Performance (RNP) and Performance Based Navigation (PBN)

Simply explained, Required Navigation Performance (RNP) is a term that encompasses the practical application of advanced RNAV concepts using Global Navigation Satellite Systems (GNSS).

However, there is a slight difference between RNP and RNAV although the principles of both systems are very similar. 

RNAV airspace generally mandates a certain level of equipment and assumes you have a 95% chance of keeping to a stated level of navigation accuracy.  On the other hand, RNP is performance based and requires a level of on-board performance monitoring and alerting.  This concept is called Performance Based Navigation (PBN).

RNAV and RNP both state a 0.95 probability of staying within 1 nm of course.  But RNP (through PBN) will let you know when the probability of you staying within 2 nm of that position goes below 0.99999.  In essence, RNP and PBN enable an aircraft to fly through airspace with a higher degree of positional accuracy for a consistently greater period of time. 

To achieve this level of accuracy a selection of navigation sensors and equipment is used to meet the performance requirements.  A further enhancement of this concept is the use of RNP/ANP (Required Navigation Performance and Actual Navigation Performance.  Advanced RNAV concepts use this comparative analysis to determine the level or error between the required navigation (the expected path of the aircraft) and the actual navigation (what path the aircraft is flying.)  This information is then displayed to the flight crew.

LNAV and VNAV

LNAV and VNAV are parts of the Flight Guidance System, and are acronyms for Lateral Navigation and Vertical Navigation'.  Both these functions form part of the automation package that the B737NG is fitted with.

LNAV is the route you fly over the ground. The plane may be using VORs, GPS, DME, or any combination of the above. It's all transparent to the pilot, as the route specified in the clearance and flight plan is loaded into the Flight Management System (FMS), of which the Flight Management Computer (FMC) is the interface.

The route shows up as a magenta line on the Navigation Display (ND), and as long as the LNAV mode on the Mode Control Panel (MCP) is engaged and the autopilot activated, the aircraft will follow that line across the ground. LNAV however, does not tell the plane what altitude to fly, VNAV does this.

VNAV is where the specified altitudes at particular waypoints are entered into the FMS, and the computer determines the best way to accomplish what you want.  The inputs from VNAV are followed whenever the autopilot is engaged (assuming VNAV is also engaged).  

The flight crew can, if necessary alter the VNAV constraints by changing the descent speed and the altitude that the aircraft will cross a particular waypoint, and the computer will re-calculate where to bring the throttles to idle thrust and begin the descent, to allow the aircraft to cross the waypoint, usually in the most economical manner.

VNAV will also function in climb and take into account airspeed restrictions at various altitudes and will fly the aircraft at the desired power setting and angle (angle of attack) to achieve the speed (and efficiency) desired.

There is not a fast rule to whether a flight crew will fly with LNAV and VNAV engaged or not; however, with LNAV and VNAV engaged and the autopilot not engaged, LNAV and VNAV will send their signals to the Flight Director (F/D) allowing the crew to follow the F/D cue display and hand fly the aircraft the way the autopilot would if it were engaged.

Reliance on MCP Annunciators

Flight Mode Annunciator (FMA) showing LNAV and VNAV Path Mode engaged.  The Flight Director provides a visual cue to the attitude of the aircraft while the speed is controlled by the the FMC.  CMD indicates that the autopilot is engaged (ProSim737 avionics suite)

LNAV and VNAV have dedicated annunciators located on the Mode Control Panel (MCP).  These annunciators illuminate to indicate whether  a particular mode is engaged. 

However, reliance on the MCP annunciators to inform you of a mode’s status is not recommended.  Rather, the Flight Mode Annunciator (FMA) which forms part of the upper area of the Primary Flight Display (PFD) should be used to determine which modes are engaged.  Using the FMA will eliminate any confusion to whether VNAV (or any other function) is engaged or not.

This post explains the Flight Mode Annunciators (FMA) in more detail.

Final Call

RNAV is a method of area navigation that was derived from the use of VOR, NDBs and other navaids.  RNP through it use of GNSS systems has enabled Area Navigation to evolve to include LNAV and VNAV which are sub-systems of the Flight Guidance System -  LNAV is the course across the ground, and VNAV is the flight path vertically. 

Historically, navigation has been achieved successfully by other methods, however, the computer can almost always do things better, smoother and a little easier – this translates to less workload on a flight crew.  

In my next post, we will discuss RNAV approaches and how they relate to what has been discussed above.

References

The information for this article came from an online reference for real-world pilots.

Acronyms and Glossary

  • Annunciator – Often called a korry, it is a light that illuminates when a specific condition is met

  • DME – Distance Measuring Equipment

  • FMA - Flight Mode Annunciator

  • FMC – Flight Management Computer

  • FMS – Flight Management System

  • GPS – Global Positioning System

  • GNSS - Global Navigation Satellite System

  • LNAV – Lateral Navigation

  • MCP – Mode Control Panel

  • ND – Navigation Display

  • NPA - Non Precision Approach

  • PBN - Performance-based Navigation

  • RNAV – Area Navigation

  • RNP - Required Navigation Performance

  • VNAV – Vertical Navigation

  • VNAV PTH – Vertical Navigation Path

  • VNAV SPD – Vertical Navigation Speed

  • VOR – VHF Omni Directional Radio Range

Trim Wheel Nut Tool - New Design

/

The redesigned Trim Wheel Nut Tool. Fabricated from a solid piece of aluminium

A potential problem when using an OEM Boeing throttle unit, is removing the nut that secures the trim wheels to the side of the throttle.  The nut has been designed in such a way that loosening it can only be done with a specialised tool.  Attempting to use a screwdriver or pliers may burr the nut, or slip causing damage to the trim wheel.

In an earlier post I examined how a simple tool had been designed to easily remove the nut from the spline shaft that holds the trim wheels in place.   Although this tool was functional there was room for improvement in its design and manufacture.

New Design and Improved Engineering

The tool, has been redesigned and incorporates an aluminium cylinder that has been produced from a solid block of aluminium using a milling machine.  The inside of the cylinder has been milled and a set screw securely inserted.  The set screw mates with the screw that holds the spline shaft in place.

The outer flange, adjacent to the set screw has then been machined so that two ridges, approximately 1mm in height are either side of the set screw.  The set screw mates with the female located on the end of the spline shaft while the ridge provides extra purchase by mating with the indents in the nut. 

In addition, a circular hole 8mm in diameter has been drilled through the upper portion of the cylinder enabling a similar sized piece of metal, or the shaft of a screwdriver to be inserted.  This allows additional purchase and leverage should the nuts be difficult to loosen.   Finally, the aluminium on the outside of cylinder has been slightly scoured to facilitate better grip.

New design has easier mating which enables greater purchasing power for removing tight spline nuts

Round and Round

The trim wheels are continually rotating back and forth as the aircraft is trimmed.  This rotation causes the nut, that secures the trim wheels to the spline shaft to, over time, become tighter and therefore more difficult to loosen.  This firmness is often exacerbated if working on a throttle unit removed from a real aircraft, that has not had the spline nuts removed for several years; corrosion and caked grease can easily cement the nuts in place.

This tool, although not an OEM part, is more than adequate to loosen the most determined trim wheel nut.

Knobs Aren't Knobs - Striving for the Perfect Knob

/

The real item – a Boeing Type 1 General Purpose Knob (GPK) and issue packet.  There can be nothing more superior to an OEM part, but be prepared to shell out a lot of clams

In Australia during the early 1980’s there was a slogan ‘Oils Ain't Oils’ which was used by the Castrol Oil Company.   The meaning was simple – their oil was better than oil sold by their competitors.  Similarly, the term ‘Knobs aren’t Knobs’, can be coined when we discuss the manufacture of reproduction knobs; there are the very good, the bad, and the downright ugly.

Boeing Knobs

As a primer, there are several knob styles used on the Main Instrument Panel, forward and aft overhead, various avionics panels, and the side walls in the 737-800 Next Generation. 

If you search the Internet you will discover that there are several manufacturers of reproduction parts that claim their knobs and switches are exactly identical to the OEM knobs used on Boeing aircraft – don’t believe them, as more often than not they are only close facsimiles.

In this article, I will primarily refer to the General Purpose Knobs (GPK) which reside for the most part on the Main Instrument Panel (MIP).  Boeing call these knobs Boeing Type 1 knobs.

oem 737 -800 next generation knob. note different location of set screw. knob used on overhead

Why Original Equipment Manufacturer (OEM) Knobs Are Expensive

Knobs are expensive, but there are reasons, be they not be very good ones.  

The average Boeing style knob is made from painted clear acrylic resin with a metal insert. On a production basis, the materials involved in their manufacture are minimal, so why do OEM knobs cost so much…   Read on.

There are two manufacturers that have long-term contracts to manufacture and supply Boeing and Airbus with various knobs, and both these companies have a policy to keep the prices set at an artificially high level.

Not all flight decks are identical, and the requirements of some airlines and cockpits are such that they require knobs that are unique to that aircraft model; therefore, the product run for knobs for this airframe will be relatively low, meaning that to make a profit the company must charge an inordinate amount of money to cover the initial design and production costs.

A high-end plastic moulding machine is used to produce a knob, and while there is nothing fancy about this type of technology and the process is automated, each knob still requires additional work after production.  This work is usually done by hand.

Cross section of a Boeing Type 1 General Purpose Knob

Once a knob has been produced, it must be hand striped and finished individually to produce a knob that is translucent and meets very strict quality assurance standards.  Hand striping is a complex, time consuming task. 

Additionally, each knob must undergo a relatively complex paint spraying procedure which includes several coats of primer and paint, and a final clear protective coating.  Spray too much paint and the translucent area (called the pointer) inside the twin parallel lines will not transmit light correctly.  Spray too little paint and the knob can suffer from light bleed.  There is a fine line during production when it is easy to ruin an otherwise good knob with a coat of thickly applied paint. 

Finally, any part made for and used by the aviation industry must undergo rigorous quality assurance, and be tested to be certified by the countries Aviation Authority.  Certifying a commercial part is not straightforward and the process of certification takes considerable time and expense.  This expense is passed onto the customer.

Often disregarded during the manufacture of reproduction knobs is the inner metal sleeve.  The sleeve protects the material from being worn out from continual use

Replicating Knobs - OEM Verses Reproduction

It’s not an easy process to replicate a knob to a level that is indiscernible from the real item.  Aside from the design and manufacture of the knob, there are several other aspects that need to be considered: functionality, painting, backlighting, robustness and appearance to name but a few. 

Backlighting and Translucency

To enable the knob to be back lit calls for the knob to be made from a translucent material.  Unfortunately many reproduction knobs fall short in this area as they are made from an opaque material.

The knob must also be painted in the correct colour, and have several coats of paint applied in addition to a final protective layer.  The protective layer safeguards against the paint flaking or peeling from the knob during normal use.  In the photograph below, you can see where extended use has begun to wear away part of the knob's paint work revealing the base material.

Detail of the grip and metal set screw.  The set screw is important as it enables the knob to be secured against the shaft of the rotary.  This knob previously was used in a Boeing 737-500

Set Screws and Metal Inserts

Often lacking in reproduction knobs is a solid metal set screw (grub screw).

The task of the set screw to secure the knob against the shaft of the rotary so that when you  turn/twist the knob it does not rotate freely around the shaft.  Plastic set screws can be easily worn away causing the knob to freely rotate on the shaft of the rotary encoder. 

The position of the set screws on the knob also deserves attention.  Correctly positioned set screws will minimize the chance of rotational stress on the shaft when the knob is turned.

Of equal concern is the hole on the underside of the knob where the rotary shaft is inserted.  The hole should be sheathed in metal.  This will increase the knob’s service life.  If the hole does not have a metal sheath, it will eventually suffer from wear (disambiguation) caused by the knob being continually being turned on its axis.   Finally, the knob must function (turn/twist) exactly as it does in the real aircraft.

Reproduction knobs may fail in several areas:

(i)    The knob has various flaws ranging from injection holes in the molded plastic to being the incorrect size or made from an inferior plastic material;

(ii)    The knob does not use metal set screws, and the set screws are not located in the correct position on the knob;

(iii)    The knob has a poorly applied decal that does not replicate the double black line on Next Generation General Purpose Knobs.  The adhesive may not be aligned correctly and may peel away from the knob;

(iv)    The knob is made from a material that does not have the ability to transfer light (translucent pointer);

(v)    The knob does not appear identical in shape to the OEM part (straight edge rather than curved);

(vi)    The paint is poorly applied to the knob and peels off.  OEM knobs have several thin coats of paint followed by hard clear coating of lacquer to ensure a long service life;

(vii)    The colour (hue) of the knob does not match the same hue of the OEM product; and,

(viii)    The circular hole in the rear of the knob, that connects with the shaft of the rotary encoder does not have inner metal sleeve.  

The time it takes to manufacture a knob is time consuming, and to produce a quality product, there must be a high level of quality assurance throughout the manufacturing process.

Older Classic-style Knobs

It's common knowledge that many parts from the classic series airframe (300 through 500) are very similar, if not identical to the parts used in the Next Generation airframe.  Unfortunately, while some knobs are identical most are not.

The knobs may function identically and be similarly designed and shaped, but their appearance differs.  Knobs used in the Next Generation sport a twin black-coloured line that abuts a translucent central line called the pointer, classic series knobs have only a central white line.

Rotary Encoders

Although not part of the knob, the rotary encoder that the knob is attached deserves mention.

A fallacy often quoted is that an OEM knob will feel much firmer than a reproduction - this is not quite true.  Whilst it is true that an OEM knob does has a certain tactile feel, more often than knot the firmness is caused by the rotary that the knob is attached to.

Low-end rotary encoders that are designed for the toy market are flimsy, have a plastic shaft, and are easy to turn.  In contrast, rotaries made for the commercial market are made from stainless steel and are firmer to turn.

Also, low end rotaries and knobs are made from plastic and with continual use the plastic will wear out prematurely resulting in the knob becoming loose.

Many reproduction knobs fit the bill, and for the most part look and feel as they should.   t's easy to criticize the injected plastic being a little uneven along the edge, but this is unseen unless you are using a magnifying glass

Final Call

Whether you use reproduction or OEM knobs in your simulator is a personal choice; It doesn't play a huge part in the operation of a simulator.  After all, the knobs on a flight deck are exactly that – knobs.  No one will know you have used a reproduction knob (unless low end reproductions have been chosen).

However, the benefit of using a real aircraft part is that there is no second guessing or searching for a superior-produced knob.  Nor is there concern to whether the paint is the correct colour and shade, or the knob is the correct shape and design – it is a real aircraft part and it is what it is.  But, using OEM knobs does have a major set-back - the amount of money that must be outlaid.  

But, second-hand OEM NG style knobs are not easy to find and often there is little choice but to choose ‘the best of the second best’.

Increasing Paint Longivity - Avionics Panels

/

Testers Dullcote.  Although it can be applied by a brush, a better approach is to use an airbrush and spray a thin coat onto the panel. When applying Dullcote to a panel, it is best to spray an even thin coat

One of the most important items in a simulator is the panel; after all, you spend a lot of time looking at panels, and a scratch or major blemish can be rather off-putting.  

It is unfortunate, that the final grey-coloured coat of paint on many reproduction panels does not conform to the same level of quality assurance that Gables or Smiths provide on an OEM item. 

Some reproduction panels can easily be scratched and chipped, and after installing and removing a panel several times, or using it for a few months, the panel quickly can appear to look like a well-used item. 

Quality assurance is a term frequently used to discuss the quality of an item.  Many manufacturers of reproduction panels only apply one or two coats of paint which may or may not be applied over a primer.  The strength and longevity of the paint depends upon whether a primer has been used, the thickness of the paint, the quality of the paint and the number of applications.  Three thinly applied coats of grey-coloured paint over primer base is far better than one or two thick coats of paint without a primer. 

The final paint finish should not be shiny but be non-reflective.

So how can you improve the durability of paint after it has been applied? 

A product called Testers DullCote has been used in the modelling arena for many years.  Modelers apply a layer of Dullcoat to their models prior to applying other painting effects which may be damaging to the underlying base coat.   Dullcote dries to a clear matt texture that adds a layer of protection to the base coat of paint.  

The application of Dullcote can be either by rattle spray can, airbrush or by a standard modeling brush.  Whatever application method is chosen, always trial the product on a lesser item prior to applying to an expensive avionics panel.

If applied correctly, Dullcote will minimize the chance of a panel being scratched or blemished and provide a clear, durable, and flat texture that can easily be cleaned.  Additionally, if Dullcoat is applied to an OEM annunciator, the application will enhance the appearance of the annunciator making it appear clearer than possibly what it is.

Glossary

  • Gables and Smiths – Two manufacturers of OEM Boeing 737 avionics panels

  • Light Plate – The actual plate that contains the lighting array to backlight the cut-out sections on a panel

  • OEM – Original Equipment Manufacture aka real aircraft part

  • Panel – Used loosely to mean a avionics panel or module (for example Fire Suppression Panel or radio panel)

BRT / DIM Functionality - Lights Test Switch

/

Lights Test switch.  The three way switch located on the Main Instrument Panel (MIP) Captain-side is used to toggle the intensity of connected annunciators.  The panel label reads TEST, BRT and DIM.  The switch in the photograph is an OEM switch which has been retrofitted to a Flight Deck Solutions (FDS) MIP

The annunciators in the Boeing 737 are very bright when illuminated, and the reason for the high intensity is justified - the designers want to ensure that any system warnings or cautions are quickly noted by a flight crew.

However, when flying at night for extended periods of time the bright lights can be tiring on your eyes.  Also, during critical flight phases such as during a night-time approach, the bright lights can become distracting.  At this time, the flight deck is usually dimmed in an attempt to conserve night vision. 

For example, the three green landing annunciators (Christmas tree lights), speed brake and flaps extension annunciators are all illuminated during the final segment of the approach.  At full intensity these annunciators can, at the very least, be distracting.

To help minimize eye strain and to enable night vision to be maintained as much as possible, pilots can select from two light intensity levels to control the brightness output of the annunciators. 

Anatomy of the Lights Test Switch

The switch (a three-way toggle) which controls the light intensity (brightness level) is called the Lights Test switch.  The switch is located on the Main Instrument Panel (MIP).  The switch is not a momentary switch and whatever position the switch is left at it will stay at until toggled to another position.  The switch has three labelled positions: Lights Test, BRT and DIM. 

(i)           UP controls the lights test (labeled Lights Test);

(ii)          CENTER is the normal position which enables the annunciators to illuminate at full intensity (labeled BRT); and,

(iii)         DOWN lowers the brightness level of the annunciators (labeled DIM).

OEM annunciators have a built-in Push-To-Test function, and each annunciator will illuminate when pushed.  The brightness level is pursuant to the position the Lights Test switch (DIM or BRT). 

The Lights Test will always illuminate all the annunciators at their full intensity (maximum brightness). An earlier article explains the Lights Test switch in more detail.

Special Conditions

When the Light Test switch is set to DIM, all the annunciators will be display at their minimum brightness.  The exception is the annunciators belonging to the Master Caution System (MCS), which are the master warning, fire bell and six packs, and the Autopilot Flight Director System (AFDS).  These annunciators will always illuminate at their full intensity because they are construed as primary caution and warning lights.

Variable Voltage

There is nothing magical about the design Boeing has used to allow DIM functionality; it is very simplistic.

Annunciators for the most part are powered by 28 volts; therefore, when the Lights Test switch is in the neutral position (center position labeled BRT) the bulbs are receiving 28 volts and will illuminate at full intensity.  Moving the switch to the DIM position reduces the voltage from 28 volts to 16.5 volts with a correspondingly lower output.  In the real aircraft, the DIM functionality (and Light Test) is controlled by a semi-mechanical system comprising relays and zener-type diodes that vary the voltage. 

Two Controlling Systems - your choice

The DIM and Lights Test functionality can be achieved in the simulator by using one of two systems - software or mechanical.

Software Controlled

The avionics suites developed by Prosim-AR, Project Magenta and Sim Avionics have the ability to conduct a full Lights Test in addition to allowing DIM functionality.  However, depending upon the hardware used, the individual Push-To-Test function of each annunciator may not be functional.  The DIM functionality is controlled directly by the avionics suite software; it is not a mechanical system as used in the real aircraft.

In ProSim737 the DIM function can be assigned to any switch from the configuration/switches and indicators menu.  In Sim Avionics the function is assigned and controlled by FSUIPC offsets within the IT interface software.

Mechanically Controlled

I have chosen to replicate the Lights Test and DIM functionality in a similar way to how it is done in the real aircraft. 

There are no benefits or advantages to either system – they are just different methods to achieve the same result.

Two Meanwell power supplies are used to provide the voltage required to illuminate the annunciators.  A 28 volt power supply enables the annunciators to be illuminated at their brightest intensity, while the less bright DIM functionality is powered by a 16.5 volt power supply (or whatever voltage you wish).

A heavy duty 20 amp 12 volt relay enables selection of either 28 volt or 16.5 volts.

The DIM Board is surprisingly simple and comprises a single terminal block and a heavy duty 12 volt relay.  Wires are coloured and tagged to ensure that each wire is connected to the correct terminal

DIM Board

A small board has been constructed from ABS plastic on which is mounted a 20 amp 12 volt relay and a terminal block. The board, called DIM is mounted behind and beneath the MIP. This facilitates easy access to the required power supplies mounted within the Power Supply Rack (PSR). 

An important function of the DIM board is that it helps to minimise the number of wires required to connect the DIM functionality to the various annunciators and to the Lights Test switch.   

Interfacing and Connections

Prior to proceeding further, a very brief explanation is required to how the various panels receive power. 

Rather than connect several panels directly to a power supply, I have connected the power supplies to two 28 volt busbars - one busbar is located in the center pedestal and other is attached to the rear of the MIP.  The busbars act a centralised point from which power is distributed to any connected panels.  This allows the wiring to be more manageable, neater, and easily traceable if troubleshooting is required.

Likewise, there is a lights test busbar located in the center pedestal that provides a central area to connect any panel that is lights test compliant.  Without this busbar, any panel that was lights test compliant would require a separate wire to be connected to the Lights Test switch in the MIP. 

The below mud schematic may make it easier to understand.  To view the schematic at full size click the image.

Mud schematic.  Note that grey box should say 12 Volts - not 28 Volts

A 28 volt busbar located in the center pedestal is used as a central point from which to connect various panels to (lower pale blue box).  

The busbar is connected to the terminal block located on the DIM board.  Wires from the terminal block then connect to a 16.5 and 28 volt power supply located in the PSR (orange boxes). 

The relay is also wired directly to the terminal block on the DIM board and a single wire connects the relay with the Lights Test switch located in the MIP (green box). 

From the Lights Test switch, a single wire connects with the lights test busbar located in the center pedestal (pale blue box).  The purple box represents any panel that is Lights Test compliant - a single wire connects between a panel and the lights test busbar.

Although this appears very convoluted, the principle is comparatively simplistic.

How it Works

When the Lights Test switch is toggled to the DIM position the relay is closed.  This inhibits 28 volts from entering the circuit, but allowing 16.5 volts to reach the 28 volt busbar (located in the center pedestal); any annunciators connected to this busbar will now only receive 16.5 volts and the annunciators will glow at their lowest brightness level.  Conversely, when the switch is toggled  to BRT or to Lights Test, the relay opens and the busbar once again receives 28 volts.

Which Annunciators are Connected to DIM Functionality

The annunciators that connect with the DIM board are those in the fire suppression panel, various panels in the center pedestal, the forward and aft overhead, and in the MIP.  If further annunciators in other systems require dimming, then it is a matter of connecting the appropriate wires from the annunciator to the 28 volt busbar, and to the and lights test busbar, both of which are located in the center pedestal.

  • The nomeclature for the 12 Volt relay is: 12 V DC coil non-latching relay part number 92S7D22D-12 (Schneider Electric).

BELOW:  A rather haphazard video showing the two brightness levels.  The example shows the annunciators in the OEM Fire Suppression Panel (FSP).  The clicking sound in the background is the Lights Test switch being toggled from BRT to DIM and back again.  Note that the colour of the annunciator does not alter - only the intensity (brightness).  The colour change in the video, as the lights alter intensity, is caused by a colour temperature shift which is not visible to the naked eye but is recorded by the video.

 

DIM functionality test

 

Glossary

  • Annunciator - A light that illuminates under set conditions.  Often called a Korry.

  • Busbar - A bar that enables power to distributed to several items from a centralised point.

  • Mud Schematic - Australian colloquialism meaning a very simplistic diagram (often used in geological mapping / mud map).

  • Push-To-Test Function - All annunciators have the ability to be pushed inwards to test the circuit and to check if the globe/LED is operational.

  • OEM - Original Equipment Manufacturer aka real aircraft part.

  • Panel/Module - Used interchangeably and meaning an avionics panel that incorporates annunciators.

  • Toggled- A verb in English meaning to toggle, change or switch from one effect, feature, or state to another by using a toggle or switch.

Flight Testing The SimWorld MCP and EFIS

/

SimWorld MCP retrofitted into a Flight Deck Solutions (FDS) MIP.  Initial impressions exceed expectations, especially when comparing the appearance of the MCP to the OEM item

I have been using the Mode Control Panel (MCP) and Electronic Flight Instrument System (EFIS) produced by CP Flight.  These units have been the mainstay in the flight simulation community for several years and for the most part they are robust, reliable, and more or less look similar to the OEM units. 

Recently, other companies have begun to manufacture MCP and EFIS units to replicate the real aircraft part as closely as possible in both appearance and functionality. 

SimWorld, located in Poland is a relatively new company that is making great leaps forward designing and manufacturing reproduction 737 Next Generation panels and other components.  One of SimWorld's premier items is their 'plug and play' MCP and EFIS.

I am currently in possession of a SimWorld MCP and two EFIS units.  These units have been retrofitted into a Flight Deck Solutions (FDS) MIP and flight testing has begun.  In due course a detailed review will be published.  I also will be, at the same time, reviewing the CANBUS system that SimWorld use to connect their various panels to the computer and Flight Simulator.

To test and evaluate the unit will take some time as the protocols I use are very thorough.  In the next few months (depending upon time) I should have enough data to enable a detailed review to be written.  The review will address at the minimum the following:

  • Manufacturing technique (materials, painting, lazer cutting, etc);

  • Accuracy and scale to the OEM MCP/EFIS

  • Robustness and longevity;

  • Functionality to OEM unit;

  • Quality assurance;

  • SimWorld pre-sales and after-sales support;

  • Reliability and consistency in operation; and,

  • An overview of the CANBUS system.

Note that I have no affiliation with SimWorld, or any other manufacturer.  This review will be a balanced opinion based on my use and the use and opinion of other users of the MCP and EFIS unit.

Glossary

  • EFIS - Electronic Flight Instrument System.

  • MCP - Mode Control Panel.

  • MIP - Main Instrument Panel.

  • OEM - Original Equipment Manufacturer (aka real aircraft parts).

Update

UPDATE 07-03-2017 by FLAPS 2 APPROACH: There have been a few problems that needed to be sorted out on the MCP that was sent to me for evaluation.  After considerable testing by myself and SimWorld, it was determined the problem stemmed from a number of unreliable potentiometers.  These potentiometers were part of a bad batch delivered by the supplier.  Filip at SimWorld decided the best option was to manufacture a new MCP and this has only just been received via UPS.

Interestingly, the replacement MCP has a number of improvements over the old-style model which includes the use of Swiss-made commercial-grade potentiometers.

Over the next few weeks I will flight test the new-style MCP and document the results in a separate post.

Update

on 2017-04-07 07:02 by FLAPS 2 APPROACH

UPDATE 07-04-2017 by FLAPS 2 APPROACH: Finally, after considerable flight testing and editing a review which was very long, the final review of the SimWorld MCP and EFIS has been published.   I hope it answers the questions that many have been asking me in private messages and e-mails.

And to answer the question to whether I am impressed with the panels and will be keeping them in my simulator - Yes I will be - unless an OEM Collins panel appears at a reasonable price :)