UNS-1 - FMS - MSFS - Manual 2
UNS-1 - FMS - MSFS - Manual 2
UNS-1 - FMS - MSFS - Manual 2
CONTENTS
INTRODUCTION.......................................................................................................... 4
Page layout.............................................................................................................. 4
General usage.......................................................................................................... 6
INIT PAGE.................................................................................................................. 27
TUNE PAGE............................................................................................................... 34
CREDITS.................................................................................................................... 52
COPYRIGHT.............................................................................................................. 52
This manual provides details of how to use the Universal UNS-1 Flight Management System (FMS) which is
integrated into the Just Flight Professional series of aircraft for Microsoft Flight Simulator (MSFS).
Please note that some file directories mentioned in this manual include ‘justflight-aircraft-146’. The aircraft name
in these instances will, of course, vary depending on which Just Flight aircraft you are flying with the UNS-1 FMS.
Page layout
Most pages are presented with this common structure:
Page title – shows the name of the current page on the top line of the page.
Page number – shows the current page number and the total number of available pages on the right of the top
first line.
M – indicates that there is a menu related to this page, accessible by pressing the MENU key.
Content – page content is shown on the following lines. If a line content has an arrow that points to the adjacent
key, it is an action that can be triggered by pressing that key.
Cursor – indicated by a line shown in highlighted text (black on white). This indicates that the content in the
highlighted line can be edited or that it needs to be validated by pressing the ENTER key.
RETURN – pressing the adjacent key will return the UNS-1 to the previously displayed page.
MSG – indicates that new messages are available and accessible through the MSG key.
INIT page
FUEL page
The page number 1/2 shows that page 1 is currently being displayed and one other page is available, accessible
by pressing the NEXT key.
The CARGO value is being edited, as shown by the highlighted field, and can be validated by pressing the
ENTER key.
An ‘M’ symbol at the top right of the screen indicates that a menu is available which is accessible by pressing
the MENU key.
Some FMC function keys have the same function, whichever page is displayed:
• When multiple pages are available, shown on the first page with the page number:
o NEXT key shows the next page
o PREV key shows the previous page
• When a framed ‘M’ symbol is shown in the title line, this indicates that a menu is available for that page
and can be accessed by pressing the MENU key.
• On some pages a selection can be made in a list instead of by entering data. In such cases, pressing the
LIST button shows the relevant list.
• When user validation is required, the ENTER key is used. This key is used each time an active cursor is
shown on the page.
• If messages are available, pressing the MSG key shows the message page with all the existing
messages.
• The PWR DIM key can be used with any page to adjust the screen brightness or turn the FMC on/off.
This section describes the way this FMC should be used to plan and fly a route, from departure to destination.
It shows a typical sequence for the use of the different FMC pages that are explained in further detail in the
following sections of this manual.
For a full tutorial flight, please refer to the FLYING WITH THE UNS-1 section of the manual.
When all this is done, the FMC is capable of managing lateral navigation and monitoring vertical navigation.
The aircraft’s autopilot needs to be set up in an R NAV or L NAV mode in order for it to track the FMC’s lateral
navigation. Please refer to the Operations Manual of the aircraft you are flying for further information on the
aircraft’s autopilot.
Pressing the DTO function key brings up the ‘direct to’ page. This is used to fly directly to any waypoint in the
flight plan.
The DTO page lists all the waypoints in the flight plan. To fly directly to one of them, enter the reference number
of the desired waypoint by using the alphanumeric keys and press ENTER. The selected waypoint will then turn
magenta on the DTO, FPL and NAV pages, indicating that this is now the active waypoint and the aircraft will
now start flying directly to that waypoint.
Pressing RSK 5 whilst on the DTO page will cancel the operation and return to the previous page.
The FPL page is accessed by pressing the FPL function key. If a flight plan has not yet been created but the
departure airport’s ICAO code was entered on the INITIAL POS ID field on the INIT page, the departure airport
will automatically be entered on the first line.
If the departure airport was not entered on the INIT page and the current GPS position has been used, the FPL
page will appear empty and the departure airport will need to be entered into the first line of the flight plan.
To do this, highlight the first line by pressing LSK1 and then type the airport’s four-letter ICAO code with the
alphanumeric keys.
Press ENTER to confirm this selection and a new page will appear, showing the airport details. Check the details
on the screen are correct and then press ENTER again.
With the departure airport entered into the first line of the flight plan, the cursor can then be placed on the
second line by pressing LSK2, in preparation for adding the first waypoint on the flight plan.
Method 1
The waypoint name can be entered by using the alphanumeric keys and then pressing the ENTER key to confirm.
If the waypoint exists, a page shows the waypoint details with the option to confirm the waypoint insertion with
ACCEPT or ignore it with RETURN.
Several waypoints with this name may exist; if this is the case, one of them will have to be selected. See the
Duplicate waypoint names section for more details.
In the following screenshot, the waypoint named KARRL is added manually using the alphanumeric keys:
On pressing ENTER, the waypoint details are then shown to be confirmed or discarded. Note that in this example
page number 1/2 is displayed, indicating that there are two waypoints in the database with the same name.
Oceanic waypoints that are comprised of latitude and longitude coordinates can be entered as waypoints by
using a five-digit format. Some examples are listed below:
VORs are shown first. The type of waypoint can be changed by using the LSK/RSK. For example, pressing LSK 1
gives access to the list of airports near the current position.
Any waypoint can be selected by entering its reference number in the list and pressing ENTER to confirm. It is
then added as the next waypoint on the flight plan.
The flight plan is created by adding all the necessary waypoints, including SID and STAR waypoints (see the
Managing runways, SIDs/STARs and transitions section for more details).
Note: The first waypoint of any flight plan should always be the departure airport and the last one should always
be the arrival airport.
Pressing NEXT will cycle through the various detail pages for all the waypoints whose code is also NS.
Once the correct waypoint is shown on the display, pressing the ENTER key or LSK 5 for ACCEPT will insert that
waypoint into the flight plan.
When the airway is selected, the list updates to show all the waypoints on the selected airway. Again, any
waypoint in this list can be selected through its reference number, and when you press ENTER all waypoints and
the chosen airway between the two selected waypoints will be entered into the flight plan.
In the following example, all the waypoints on the H384 airway after KARRL are shown on this page. Selecting
the NP waypoint by entering the number 1 and then pressing ENTER inserts all the waypoints from KARRL to NP
into the flight plan.
On the DEPARTURE page the runway must first be selected, as indicated by the cursor automatically highlighting
the runway field. The departure page lists all the runways available at the departure airport in the flight plan. The
page number indicates whether several pages are available; the number of pages depends on the number of
runways at the departure airport.
The desired runway can be selected by entering its reference number from the list and then pressing ENTER to
select it. Pressing RSK 5 (FPL) cancels the operation and returns you to the flight plan page.
Once a runway has been selected, the cursor will automatically move down to the SID field and a list of all
available SIDs for that runway will be displayed. Several pages can be available, depending on the number of
SIDs available for that runway. The desired SID is selected by entering its reference number from the list and then
pressing ENTER.
If no SID or transition is available for the selected runway, pressing RSK 3 when one of these fields is highlighted
will remove the cursor from that field and leave it empty.
When the runway, SID and transition process is finished, the DEPARTURE page will show all of the pilot’s
selections and proposes a return to the flight plan page.
Inserting a waypoint
To insert a new waypoint before an existing waypoint, first select the existing waypoint. Then proceed as if
you wanted to create a new waypoint, by entering its name with the keyboard and then pressing ENTER, or by
pressing the LIST function key to select it from a list.
The NS waypoint must first be selected by pressing the respective LSK, and then the new waypoint can be typed
with the alphanumeric keys. Press ENTER to insert the waypoint into the flight plan.
A *NO LINK* or ‘VECTORS’ message may appear as a waypoint when inserting a new waypoint into the flight
plan. If one of these messages appears, the pilot should check that the changes to the flight plan are correct
before deleting the *NO LINK* or ‘VECTORS’ message from the flight plan in the same manner as for deleting a
waypoint.
The newly added waypoint is now inserted at the same line of the flight plan as the previously highlighted
waypoint, with all the following waypoints moved down one line.
Pressing RSK 1 triggers the DEL (delete) action that deletes the waypoint. This action must be confirmed by
pressing RSK 1 twice – once to make the action active and a second time to confirm it and proceed. Once RSK
1 has been pressed twice, the waypoint will be deleted from the flight plan.
As the name suggests, the FPL SUMMARY page can be used to calculate and view a summary of the proposed
flight plan:
DEPART – departure airport’s ICAO code. This field will be filled automatically, based on the departure airport
inputted on the FPL page.
ARRIVE – arrival airport’s ICAO code. This field will be filled automatically, based on the arrival airport inputted
on the FPL page. The distance between the two airports is shown in nautical miles between the two fields.
ETD UTC – estimated time of departure in UTC and local time. Once the ETD UTC and a time zone difference
have been manually entered, the local time is automatically calculated.
The import function imports the departure and arrival airports as well as all waypoints and airways between the
two, but it will NOT import departure and arrival procedures. These will need to be set up manually by the pilot,
depending on ATC and weather requirements.
Flight plans listed in the COPY PLT RTE menu are stored locally on your PC in an .RTE file format at the following
file directory: C:\Users\**USERNAME**\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\
LocalState\packages\justflight-aircraft-146\work\JustFlight\FlightPlans.
For SimBrief users, once an OFP has been generated, the flight plan can be saved in an .RTE format by
expanding the ‘Flight Plan Downloads’ box at the bottom of the page and then clicking the ‘Download’ button
in the box displaying the name of the aircraft you are flying. The route file will then download to the normal
download location on your PC and will need to be manually copied across to the file directory listed above.
The Simbrief Downloader app can also be used to automatically save the flight plan to the correct location
whenever an OFP is generated on the SimBrief website. To do this, the file directory listed needs to be added to
the ‘Download Directory #1’ field (next to the name of the aircraft you are flying) in the Simbrief Downloader app.
Flight plan files can be added to this file directory while the simulator is running or with the simulator closed.
Adding a flight plan to this folder whilst the simulator is running should allow the flight plan to be shown on the
COPY PLT RTE page and therefore does not require the simulator to be restarted.
On the PLT RTE page, the current flight plan can be exported/stored by first giving the flight plan a name
(typically the name should consist of the ICAO codes of the departure and destination airports on the flight plan,
e.g. ‘NZAANZCH’). Pressing ENTER will export the flight plan and save it at the following file directory:
C:\Users\**USERNAME**\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\
packages\justflight-aircraft-146\work\JustFlight\FlightPlans.
The flight plan is saved in an .RTE format to the same file directory as outlined in the Flight plan import section,
therefore the flight plan will subsequently be listed on the COPY PLT RTE page and can be imported by following
the appropriate steps.
This simulation of the UNS-1 includes Navdata from the ARINC 2301 cycle as standard which will probably
generate a **NAV DATABASE EXPIRED** message on the INIT page. Although this is not the most up-to-date
ARINC cycle, this Navdata should be sufficient in the majority of cases and should have little to no effect on your
overall simulator experience.
Users with an active Navigraph subscription can update their Navdata by using the NAVIGRAPH HUB desktop
application and clicking the green UPDATE button for the required Just Flight aircraft. Once the Navdata has
been successfully updated, the button will turn red and show REMOVE, allowing you to remove this newly
installed Navdata.
The Navdata for the UNS-1 is located in the following file directory: …\Community\justflight-aircraft-146\Work\
JustFlight\navdata.
The FUEL page is accessed by pressing the FUEL function key. It has two sub-pages that manage the fuel
quantity and the aircraft weight, which are important for performance calculations. The information shown on
these pages is only relevant if a flight plan is defined.
The first page (1/2) shows the following information, some of which can be edited by the pilot. Note that when
you enter a value and press ENTER, the cursor automatically jumps to the next editable value. If no data entry is
necessary, the adjacent line select key can be pressed to cancel the entry and remove the cursor.
The information displayed on the FUEL page will adjust automatically based on the aircraft current weight, and
should match the aircraft’s current fuel and weight values shown on the EFB.
When all fields have correct information, the FMC can compute all the data, especially the gross weight which
takes all the fuel and weight information into account.
The second fuel page (2/2) shows computed information based on the information entered on page 1, including
the current fuel flow and the ground speed shown on line 1. All values displayed on this page vary constantly
depending on the aircraft’s current state, therefore values such as fuel flow and range will vary depending on the
aircraft’s current speed and engine settings.
Five different units of measurement are available on the left side of the screen which serve as a useful tool
for converting weight between pounds, kilograms, US gallons, imperial gallons and litres (‘LITERS’). Once a
value has been entered into one of these fields, the conversion to each of the other units will be calculated and
displayed. The weight/volume conversion is based on a fuel density of 6.7lb/gal and is rounded up to the nearest
whole number.
INIT PAGE
The INIT page allows for the definition of the initial aircraft position. It shows the following information:
• Current aircraft position, as it was defined. If not defined, a yellow POS message appears in the top left
corner of the screen.
• Current date and time as defined in the simulator.
• Navigation database expiry date as defined in the database according to the AIRAC cycle.
• FMC software version.
When the initialisation is complete, there is no need to have access to this page again and it can therefore only
be accessed by powering OFF the FMC and then powering it back ON.
The messages page displays the FMC messages. If there is an unread message, a yellow MSG label appears in
the top right corner of the screen. Pressing the MSG function key brings up the message page so you can read it.
The NAV page is accessed via the NAV function key and is responsible for lateral navigation.
The NAV page provides an immediate overview of the flight plan, with the previous waypoint that you are flying
from (FR), the active waypoint that you are flying towards (TO) and the next waypoint on your flight plan (NX):
FR – the previous ‘from’ waypoint.
TO – the active ‘to’ waypoint (the waypoint to which the aircraft is flying).
NX – the ‘next’ waypoint that follows the active waypoint. The heading and distance between these waypoints is
also indicated.
Two further functions adjacent to the right select keys, labelled HDG and MNVR, allow for control over the
aircraft’s heading and intercept paths, and also allow for the programming of holding patterns.
CMD HDG – the heading the FMC can use whilst the autopilot is still in an LNAV mode. A new heading can
be entered by using the alphanumeric keys and then confirmed with the ENTER key. When a new heading is
confirmed, the FMC assumes the shortest direction of turn and begins flying on that heading with the aircraft’s
LNAV mode still engaged.
Pressing RSK 2 on the NAV page will toggle between HDG SEL and INTERCEPT modes.
HDG SEL – the FMS will follow the assigned heading until manually changed or cancelled.
INTERCEPT – the FMS will follow the assigned heading until intercepting the active navigation leg. Once an
active navigation leg is intercepted, the FMS will revert to normal navigation.
HOLDING DEFN – opens the HOLDING FIX page where a holding pattern can be programmed.
The current TO waypoint will appear highlighted in the HOLD FIX field. To change the selected waypoint, press
LSK 2, enter the reference number of the waypoint and then press ENTER.
The HOLDING PATTERN DEFINTION page will then open, displaying a visualisation of the holding pattern with
default values. These values can be edited by pressing the respective LSK/RSK, inputting the new values with
the alphanumeric keys and then pressing ENTER.
The performance (PERF) page is accessed by pressing the PERF function key. The PERF page shows some
weight information that is also found on the FUEL pages. Similar to the FUEL page, all information displayed on
the PERF page will adjust automatically based on the aircraft’s current state.
GS – ground speed, computed or estimated, depending on whether the aircraft is flying or still on the ground.
HEADWIND/TAILWIND – current headwind/tailwind component speed.
ESAD – equivalent still air distance (the distance the aircraft would fly without wind).
TEMP – current outside air temperature.
DIST – flying distance, according to the flight plan.
ETE – estimated time en route (the time needed to reach the destination).
GND NM/KG. (or LB.) and AIR NM/KG. (or LBKG.) – estimated ground/air nautical miles per kilogram/pound,
based on ground/true airspeed.
Text coloured blue is for items that are not relevant to the aircraft and are therefore inoperative. One option on
this page that is functional is the ETP/PNR page.
Pressing LSK 5 will open the ETP/PNR page.
The first ETP/PNR page (1/2) is a useful tool for viewing the time, distance and fuel required to reach a selection
of airports. Airports can be entered on this page by pressing the relevant LSK 2-5 keys, typing the four-digit
airport ICAO code with the alphanumeric keys and then pressing the ENTER key.
The PWR DIM function key gives access to the FMC’s power and brightness control. This menu can be accessed
from any page on the FMC.
If the FMC is off, pressing this button turns it on.
If the FMC is on, pressing the PWR DIM function key brings up a new set of options on the right of the screen,
adjacent to the right select keys.
TUNE PAGE
The TUNE page is simulated as inoperative to reflect the real-world configuration of an aircraft with analogue
radio equipment in the cockpit.
The COM and NAV frequencies that would otherwise be inputted on this page can be inputted using the
analogue controls in the aircraft’s cockpit.
The PATH VNAV page can be opened by pressing the VNAV function key.
Once TOD has been reached, the TOD distance will be removed from view. The vertical speed display will then
be updated constantly throughout the descent, providing a useful tool for the pilot to confirm that they are still on
the correct descent path.
If the vertical speed displayed here is constantly followed by the aircraft, the aircraft will reach the waypoint at
the specified altitude.
In order to stay on the planned descent path, the pilot should aim to keep the vertical speed displayed here
matching the target vertical speed that was entered prior to the top of descent.
The TO and NX waypoints and their respective altitude constraints/restrictions can be edited by pressing the LSK
2-5 keys, entering the reference number for the desired waypoint and then pressing ENTER.
This tutorial flight will cover a generic flight between two airports and can be used with any Just Flight
Professional series aircraft that is fitted with a Universal UNS-1 Flight Management Computer (FMC). It will
therefore cover all the procedures required to set up and operate the UNS-1, but will not cover options of the
aircraft itself. For information on how to operate the aircraft you are flying, please see the relevant Operations
Manual located in the same folder as this manual.
In this tutorial flight we will be departing from Auckland International Airport, the busiest airport in New Zealand,
and flying south to Christchurch Airport, the second busiest airport in the country and the gateway to Antarctica.
We will be flying south down the western coastline of New Zealand’s North Island before crossing the Cook
Strait, the body of water that separates New Zealand’s North and South Islands, and beginning our descent into
Christchurch.
Covering approximately 413 nautical miles, this regional flight is the ideal length for learning UNS-1 operations on
board any Just Flight Professional aircraft.
Pre-flight
With the aircraft powered up and passenger/cargo boarding in progress, we can run through the set-up process
to get the UNS-1 ready for flight.
Turn on the unit by pressing the PWR DIM key. The unit will then run through a self-test procedure.
Once the self-test is complete, the first page shown will be the INIT page. Check that all data listed on the page
is correct before pressing LSK 5 or the ENTER key to accept.
We can now begin to input the flight plan for today’s flight.
Press the FPL function key to open the flight plan page.
Input our departure airport into the first empty field in the flight plan. If it is not already highlighted white, press
LSK 1 to highlight the first field and input NZAA using the alphanumeric keys on the FMC.
You will now be returned to the FPL page and NZAA will be inserted into the top field of the flight plan. We can
now begin entering the waypoints on our flight plan.
We can start by inputting the SID (Standard Instrument Departure) that is listed on our flight plan: LEVR1P.
Ensuring that we are on the FPL page (press the FPL function key if not), press the MENU key and then press
LSK 4 to open the DEPARTURE menu.
The field highlighted will then automatically move down to the SID field and a list of available SIDs for the runway
will be displayed. We will be flying the LEVR1P SID which has a reference number of 6, so input the reference
number into the SID field and press ENTER.
The field highlighted will then automatically move to the TRANSITION field and a list of available transition points
for that SID will be displayed. As KARRL is the first waypoint in our flight plan, and the last waypoint on the SID,
this will be our transition point, so input the reference number into the transition field and press ENTER.
We will follow a similar procedure later in the flight when we enter the arrival procedures, but for now we will
focus on adding the remainder of the waypoints on our flight plan.
We could enter each waypoint manually but, as our flight plan includes airways, we can instead build our flight
plan with a mixture of waypoints and airways to speed up the process.
To enter an airway from KARRL, ensure the next empty field in the flight plan is highlighted and then press the
LIST function key.
On the LIST page, press RSK 2 to open the AIRWAYS list, where all the airways that intersect the KARRL
waypoint are shown.
As per our flight plan, we want to fly from KARRL, on the H384 airway, to NP. Therefore we need to input the
reference number for the H384 airway with the keypad and press ENTER.
We will then see a list of all the waypoints on the H384 airway. As we will be flying on the airway as far as NP, we
can select the NP waypoint by inputting its reference number and pressing ENTER.
We will now repeat this process for the next airway on our flight plan. Highlight the next empty field on the FPL
page, then press the LIST function key, and then RSK 2 to open the AIRWAYS list. Input the reference number of
the H252 airway and press ENTER. Then input the reference number for the NS waypoint and press ENTER.
Returning to the FPL page, we can see that significantly more waypoints have been added to the flight plan this
time due to the larger distance we will be travelling on the H252 airway. This shows why this method of flight
plan entry is the most efficient, as adding each of those waypoints to the flight plan manually would be much
more time consuming, whereas this method lets you add all of those waypoints by simply selecting an airway
and a start and end point.
Once all the waypoints on the flight plan have been inserted, input the destination airport (NZCH) as the last
entry on the flight plan and press ENTER.
Now that all waypoints have been entered, it is good practice to double-check that the flight plan in the FMC
matches our planned route, and to delete or edit any waypoints that are not correct.
Note: We have not yet inputted our arrival procedures and that is intentional, as typically we wouldn’t be sure
of what the wind direction will be on our arrival into Christchurch until we are further into our flight. To keep this
tutorial realistic, therefore, we will save setting up our arrival procedure until later in the flight.
With the flight plan entered, we can now move to the FUEL page by pressing the FUEL function key.
The CARGO field, where the weight of the cargo can be inputted, will then be highlighted automatically. Ensure
that the cargo weight matches up with the weight on the EFB and then press ENTER. If it is not correctly set,
input the correct value and press ENTER.
The FUEL ONBOARD field, where the weight of the fuel can be inputted, will then be highlighted automatically.
This field should also be automatically synchronised with the current fuel level in the aircraft, so only a cross-
check is normally required. Pressing ENTER will confirm the current figure.
Climb
As we climb on the SID, we can monitor the UNS-1 FPL and NAV pages to confirm that the aircraft is tracking
the correct waypoints, and that once a waypoint has been overflown, the next waypoint becomes active
automatically.
If ATC instructions cleared you to perform a short cut on your route, you can achieve this by pressing the DTO
function key and inputting the reference number of the waypoint you have been cleared direct to. Pressing the
ENTER key will confirm this and will turn the selected waypoint magenta. The aircraft will then fly directly to the
new active waypoint.
On the PERF page we can see the aircraft’s current fuel situation, including the time at which we are currently
estimated to arrive at NZCH and the amount of fuel we expect to have remaining once we land. If, for instance,
we had a very strong headwind, we could be burning more fuel than expected and would be able to tell from this
page if we could still make it to NZCH with a safe amount of fuel remaining. As we are flying a short route today
with full fuel tanks, this shouldn’t be an issue.
Continuing on the PERF page, pressing the MENU key followed by LSK 5 will open the ETP/PNR page. This
page shows us the direct distance to our departure and destination airports, as well as the estimated time it
would take to fly there and the amount of fuel remaining upon landing. In one of the empty fields we can enter
Wellington Airport, NZWN. Wellington airport is located on the southern coast of New Zealand’s North Island, so
it would be a good choice of an alternate airport if we suddenly had to divert. With the time, distance and fuel
indicated on this page, we could quickly plan our top of descent and know far in advance if we were going to be
under or over our maximum landing weight.
The field highlighted will then move down to the STAR field and a list of available STARs for that runway will
be displayed. We will be flying the PEAK8B STAR so press NEXT to scroll through the pages until we find the
correct STAR, then input the reference number into the STAR field and press ENTER.
The field highlighted will then move across to the TRANSITION field and a list of available transition points for the
STAR will be displayed. We will be flying the ODISI transition, which is the waypoint at the end of the STAR and
the beginning of the ILS approach. Input the reference number for ODISI into the transition field and then press
ENTER.
We can now input the target vertical speed of our descent by pressing RSK 1 and then inputting the desired
figure. For this flight we will input 2000 and then press ENTER.
The PATH VNAV page is now in cruise mode and a new line of data indicating the distance still to fly until the top
of descent will appear at the top of the page.
Underneath this line the required vertical speed from the aircraft’s current position to the first altitude restriction
is displayed. This is a useful tool during the descent as it provides a visual reference as to how high or low the
aircraft is, compared to the target vertical speed. In order to achieve a smooth, on-target descent, the aircraft’s
vertical speed should match the target vertical speed shown here throughout the descent.
If the indicator starts to indicate -1700ft/min, that means we are too low with respect to the target descent path
and we need to reduce our descent rate to -1700ft/min in order to still reach our first altitude restriction at the
correct altitude.
As we pass over the PEAKS waypoint, the TO waypoint on the PATH VNAV page will automatically change to the
next waypoint with an altitude restriction. This is BLUNT, which we have to cross above 7,000ft.
As we descend, the PATH VNAV page will continue to show and update the required vertical speed for the
remainder of the descent, so it is a useful tool to monitor.
During the approach we can continue to monitor the NAV, FPL and VNAV pages to keep track of our progress. If
the aircraft has multiple UNS-1s fitted, it can be useful to have each UNS-1 displaying a different screen during
these high workload situations.
Approach
As the aircraft turns onto the final approach course for runway 20, it is important to remember that the UNS-1
does not have any command over the aircraft’s vertical navigation, In order for the aircraft to intercept and track
the ILS localiser and glideslope, therefore, the correct course and frequency must be tuned into the aircraft’s NAV
radios. The ILS for runway 20 at Christchurch uses a course of 196 degrees and a frequency of 110.30 MHz.
Once within intercept range of the localiser and glideslope, we can disengage the aircraft’s LNAV/RNAV capability
and engage the aircraft’s traditional autopilot approach modes.
We can then switch off all UNS-1 units in the cockpit by pressing the PWR DIM function key, followed by RSK 5.
COPYRIGHT
©2024 Just Flight. All rights reserved. Just Flight and the Just Flight logo are trademarks of JustFlight London
Limited, St. George’s House, George Street, Huntingdon, PE29 3GH, UK. All trademarks and brand names
are trademarks or registered trademarks of the respective owners and their use herein does not imply any
association or endorsement by any third party.