E-mail Subscription

Enter your email address:

Delivered by FeedBurner

Syndicate RSS
Welcome

Mission Statement 

The purpose of FLAPS-2-APPROACH is two-fold:  To document the construction of a Boeing 737 flight simulator, and to act as a platform to share aviation-related articles pertaining to the Boeing 737; thereby, providing a source of inspiration and reference to like-minded individuals.

I am not a professional journalist.  Writing for a cross section of readers from differing cultures and languages with varying degrees of technical ability, can at times be challenging. I hope there are not too many spelling and grammatical mistakes.

 

Note:   I have NO affiliation with ANY manufacturer or reseller.  All reviews and content are 'frank and fearless' - I tell it as I see it.  Do not complain if you do not like what you read.

I use the words 'modules & panels' and 'CDU & FMC' interchangeably.  The definition of the acronym 'OEM' is Original Equipment Manufacturer (aka real aicraft part).

 

All funds are used to offset the cost of server and website hosting (Thank You...)

No advertising on this website - EVER!

 

Find more about Weather in Hobart, AU
Click for weather forecast

 

 

 

 

  FEEDBACK:  

If you see any errors or omissions, please contact me to correct the information. 

Journal Archive (Newest First)

Entries in VOR (3)

Thursday
Aug272015

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

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

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

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

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

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

Screen Images

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

How To Set-Up An Arc

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

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

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

Approach Charts

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

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

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

CDU Instructions

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

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

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

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

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

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

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

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

A Note About /-+

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

Variation

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

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

Handy Hints

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

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

Hint One - visual descent point (VDP)

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

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

Hint Two - extend runway line

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

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

This enables three things:

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

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

LOWER LEFT:  The transition from LNAV to VOR has occurred and the autopilot and autothrottle are not controlling the aircraft. The aircraft is on short final with gear down, flaps 30 and the airspeed is slowly decaying to VREF+5.  The EFIS has been changed from MAP to VOR to allow manual tracking using the VOR needle. The NPS show good vertical alignment with a lateral left offset; the VOR indicator confirms this.  The Flight Mode Annunciator (FMA) displays LNAV (although the autopilot is disengaged) and the Flight Director (FD) and NPS show glidepath (GP) data.  The Flight Path Vector (FPV) symbol shows a continuous descent at roughly 3 degrees.  The altitude window and heading on the MCP has been set to the appropriate missed approach (4200/300).  Click image to enlarge.

Do Not Alter Constraints

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

Finding the Correct Radial/Bearing to Build Your Arc

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

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

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

Important Points

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

Final Call

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

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

Other posts that deal with similar subjects are:

Glossary

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

Images

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

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

 

 

 

 

 

 

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

 

 

 

 

 

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

 

 

 

 

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

 

 

 

 

 

LEFT:  In the example, RWY 30 has been selected from the arrivals (ARR) page.  In addition to situational awareness, the selection of the runway in the CDU provides glidepath (GP) assistance.

The result of this is that the runway line is extended from the threshold to 7 miles out; the same distance out from the threshold that the final waypoint was generated.

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

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

Wednesday
Jan292014

RMI Knobs Installed to Main Instrument Panel (MIP)

Following on with the theme from my last post, I have replaced the two tear-drop style RMI knobs supplied by Flight Deck Solutions on their Main Instrument Panel with two replacement knobs.

LEFT:  RMI knobs fitted to the RMI frame of the MIP.  ProSim737 allows for a number of differing style RMI gauges to be displayed - framed and frameless (click to enlarge).

The replacement knobs are highly detailed reproductions of the original B737-800 RMI knobs.  I would like to have used genuine knobs; however, as they are usually attached to an RMI gauge, finding the knobs alone at a reasonable price would be a difficult if not an impossible task.

The knobs have been individually sculptured using clear ABS plastic while the front plate is made from clear acrylic.  The knobs are then painted in the correct Boeing grey colour and the black and white stenciling applied directly to the front of the knob.  The knobs can be easily backlit using an LED, although I have yet to do this.  The sizing of the knobs can be determined from information supplied by EHC Knobs located in Farmingdale, New York.

Stand-by Instruments - RMI Gauge

There is no "stock standard" concerning how the stand-by instruments are displayed with a reproduction MIP.   You may have the capacity to include real stand-by gauges (lucky you…) or reproduction solid state gauges manufactured by Flight Illusion, Sim Kits or similar. 

Flight Deck Solutions (FDS) have choosen to use a single LCD monitor to cover the EICAS and stand-by gauges.  Fly Engravity use solid state Flight Illusion gauges. 

Looking Pretty.....

At the moment the knobs have not been interfaced and just sit there “looking pretty”

In the future, I may interface the knobs by installing micro-buttons and/or a micro- rotary behind each knob.  The knobs will then be connected to an interface card.  However, at the minimum this requires cutting the MIP to create additional space for the location of the micro-switches – something I do not want to contemplate at the moment.  If given a choice, procuring a genuine OEM RMI gauge would be my preferred option.

In the interim, the RMI Switch Assembly panel discussed in my earlier post will suffice.

The RMI knobs are now replaced with OEM knobs from a B737-800 that are fully functional.

Acronyms

MIP – Main Instrument Panel
RMIRadio Magnetic Indicator.  The gauge that displays VOR and ADF mode.  Part of B737 NG stand-by instrument cluster

Saturday
Jan182014

RMI Switch Assembly (ADF/VOR) Installed to Center Pedestal - Flying by VOR & NDB Made Easier

It probably seems an oddity to install into the center pedestal a switch manufactured in 1967 that in all probability was used in a an early model Boeing 737 or more lilely a B727.

My reasoning is quite simple; I enjoy flying using VORS and NDBS, and implementation of this switch allows the stand-by RMI gauge to be used more effectively when using these “older style” navigational aids.  

LEFT:  RMI Switch Assembly dated stamped 1967.  RMI switch has been custom fitted to blanking plate (click image for larger view).

VOR and NDB Flying (NG)

The NG allows tracking of the primary and secondary VOR/NDB with a visual display on the Navigation Display (ND).  The display can be turned on and off from the either the Captain or First Officer side EFIS.  Tuning to the VOR and NDB is accomplished by dialing in the correct frequency on the NAV and ADF radio panels. 

The navigation output is duplicated and shown as dual needle movement on the RMI gauge which is the third gauge within the stand-by instrument cluster.  In the real B737 aircraft, the mode of the RMI gauge can be toggled between VOR 1/2 and ADF 1/2 or a combination by the small knobs on the front of the RMI that protrude through the Main Instrument Panel (MIP).  

RMI Knobs

It’s unfortunate that many manufacturers of reproduction Main Instrument Panels (MIPS) do not include functionality to these two small knobs and provide only a 'rough' facsimile of an original knob.   We will will look further at the NG RMI knobs in the next post.

The use of the older style 737 Switch Assembly duplicates the functionality ( if it existed) of the stand-by RMI buttons on the MIP.

Interfacing, Wiring and Blanking Plate

The card was interfaced to Flight Simulator using a PoKeys55 interface card.  In my set-up the PoKeys card resides in the System Interface Module (SIM) and the five wires from the 737 switch were run through a piece of conduit (plastic piping) beneath the platform to the System Interface Module (SIM)  located forward of the MIP.

LEFT:  Early Boeing N737 RMI Switch Assembly showing detail of two switches, Canon plug, wiring harness and front panel (click image for larger view).

The five wires correspond to VOR 1/2 and ADF 1/2.  The fifth wire is the common (earth).  Two additional wires (positive and negative) connect to the 5 Volt bus bar located in the center pedestal and are used to power the backlighting of the panel.

Canon Plugs - Why Change a Perfect System

The switch assembly included a male Canon plug in very good condition; therefore, it was decided to use the Canon plug system rather than wire separately.  A female Canon plug was purchased from E-Bay and to determine the correct pin outs for the plug a multimeter was used to determine conductivity from each pin in relation to the mode toggled.   A longer wire harness was made to allow the harness to reach the System nterface Module forward of the MIP.  Using Canon plugs keeps the wiring very neat and allows for an easy disconnect should you need to remove the panel from the pedestal.

Blanking Plate

In the Boeing 727 and earlier 737 airframes, the RMI Switch Assembly is mounted within the Main Instrument Panel (from memory).  In this era (circa 1967) modern-style EFIS units had yet to be developed. 

As such, the switch does not require a blanking plate as it’s attached to the MIP by four screws.  To facilitate the switch being installed to the center pedestal, a blanking plate had the center portion cut out using a  dremil cutter.  The switch assembly could then by placed in the cut hole and attached directly into the blaking plate via the four screws.

LEFT:  The RMI Switch Assembly installed to the center pedestal.  Selection can be either ADF1/2, VOR1/2 or a combination.  Switches and panel are backlit by 5 Volts which is the standard voltage used in many panels. In the "real world" this panel would never be seen in three-bay center pedestal.

Mapping Functions

To configure the functionality of the Switch Assembly to ProSim737 was straightforward, as the functions have already been mapped within ProSim's configuration menu.  This is one of the major advantages to using ProSim737 as the avionics suite; many functions have been pre-mapped and you do not need to "delve" into the world of FSUPIC offsets in an attempt to get something working.

Not Standard Airline Order

Although it's not standard NG equipment -  "you would NEVER see this switch panel in a B737 NG", the Switch Assembly is very enjoyable to use and makes using the alternate RMI gauge more user friendly - at least until I add functionality to the NG RMI knobs or aquire a OEM RMI guage. 

In the next post we'll discuss the Next Generation (NG) RMI knobs.

Acronyms & Glossary

ADF – Automatic Direction Finder
Blanking Plate - An aluminium plate used to cover a gap in the pedestal or overhead.  The plate is equipped with DZUS fasteners for attachment to the DZUS rail VOR - Omni Directional Radio Range
EFIS – Electronic Flight Instrument System
IMM – Interface Master Module
MIP – Main Instrument Panel
NDB – Non Directional Beacon
PANEL – Refers to actual avionics module.  Panel and module are interchangeable
RMI – Radio Magnetic Indicator.  The gauge that displays VOR and ADF mode.  Part of B737 NG stand-by instrument cluster