This is a guide to the 757/767 FMS Tutorial.
It assumes you have an iPad with the tutorial installed.
To purchase the tutorial, see the home page at watts.aero/b767.
This document is written for instructors who use the tutorial during ground school presentations, although students who want to learn more about the FMS will get something out of this as well.
When the tutorial starts for the very first time, it looks like this:
When restarting after some progress has been made in the tutorial,
it looks like this:
Let's jump ahead to a completed preflight.
T9 is a shortcut that executes the entire preflight tutorial, and leaves you on the TAKEOFF REF page.
A shortcut is a single letter for the page, a single number for the step.
For example, T9 is the TAKEOFF REF page, 9th step - the last step. P1 is the POS INIT page, first step.
Shortcuts can be entered into the IDENT page, 4R (CO DATA) or RTE page 1, 3R (CO ROUTE).
Links can be created for a shortcut, perhaps for emailing to a student,
or to show a particular page during a presentation:
aero.watts.b767:t9
And there are QR codes for each shortcut.
Here's the T9 shortcut
to the completed TAKEOFF REF page:
These QR codes only work on iPads with the tutorial installed.
For more information, see Appendix A - Shortcuts.
At any point during the tutorial or in free play, you can access the SETTINGS page.
The SETTINGS page allows you to change aircraft model, engine model, or fuel loaded.
It also shows the software revision of the tutorial.
Some pages and function keys behave differently when airborne.
To get “airborne,” do this:
The FMS Tutorial is now airborne.
INIT REF takes you to the APPROACH REF page.
RTE takes you to RTE page 2.
DEP ARR takes you to the ARRIVALS page, and if you select an approach, an INTC> prompt is shown.
ALTN pages now have a DIVERT NOW> prompt.
To get out of airborne mode, and back into ground mode, do this:
The Honeywell PEGASUS system is a scratchpad-based system.
If you look at almost any computer system, you'll see a blinking cursor, directing your attention to where your keystrokes go.
We don't like blinking things in the cockpit.
The scratchpad is a neat innovation! No need for a cursor if everything you type goes into one location.
There is a separate scratchpad for each system.
The CDU is usually
connected to the FMC
but it can also connect to ACARS, or the satellite phone,
or other systems as installed.
Hover over the A: to reveal the answer!
Q: Does the MENU page have a scratchpad?
Q: Does the FMC scratchpad keep your data if you connect to a different system?
Q: Does the ACARS scratchpad keep your data if you connect back to the FMC?
Let's take a look at a typical LEGS page.
RTE 1 LEGS 1/3
092°HDG
(INTC) ---/------
111° 7NM
JAMBA ---/------
126° 4NM
KBOLA ---/------
118° 24NM
KLADA ---/------
120° 66NM
MEDLI ---/------
------------------------
<RTE 2 LEGS ACTIVATE>
The small text is the path. This is how the FMC will fly this leg.
The large text is the terminator. Your FCOM may refer to this as a waypoint or conditional waypoint. This is the condition that will sequence the FMC to the next leg.
In the above example, the FMC will fly a 92° heading, until it intercepts the 111° course to JAMBA.
The RTE page is built from the LEGS page.
When the RTE page is shown, the FMC sequences through all legs, grouping the legs with the same VIA route.
Imagine the above legs, as stored in the FMC:
Path
Terminator
VIA
092° HDG
(INTC)
---/-----
KLADA2.BITAC
111°
7NM
JAMBA
---/-----
KLADA2.BITAC
126°
4NM
KBOLA
---/-----
KLADA2.BITAC
118°
24NM
KLADA
---/-----
KLADA2.BITAC
120°
66NM
MEDLI
---/-----
KLADA2.BITAC
Continuing on the next page...
123°
62NM
BITAC
---/-----
KLADA2.BITAC
125°
406NM
HAGIT
---/-----
Y290
…
137°
56NM
BEANO
---/-----
Y290
To construct the RTE page, the FMC
collects all legs with the same KLADA2.BITAC, then collects all the legs
with Y290.
RTE 1 2/2
VIA TO
KLADA2.BITAC BITAC
Y290 BEANO
----- -----
------------------------
<RTE 2 ACTIVATE>
Likewise, to construct the DEPARTURES or ARRIVALS page, the FMC uses the LEGS table to see which departure or arrival is active.
If there is no leg associated with a departure or arrival procedure, it won't remember that procedure!
To prove this, run the tutorial, building a flight from KMIA to TJSJ.
Then, select the BEANO3 arrival. Do not select a runway or a transition!
Now, press the RTE key. Look at page 2. There is no BEANO3 arrival.
Press the DEP ARR key. Try to find your selected BEANO3 arrival. It won't be selected.
If you select the BEANO3 arrival, then select an approach, there will be a route discontinuity because the FMS forgot the BEANO3 arrival.
You must select an approach or a runway first. Then the FMS will insert the necessary legs into your flight path, and it will remember the arrival.
The app can demonstrate flying past a holding fix.
Try this:
Notice that the distance to JAMBA changes to 5 NM, then slowly counts down. This emulates the airplane flying towards the holding fix.
Once you're past JAMBA, press 6L.
Some operators are authorized to perform RNP (Required Navigation Performance) AR (Authorization Required) approaches.
Those operators will have navigation databases with all the normal approaches, but will also have RNP approaches.
This tutorial has two airports that include these RNP approaches: KPSP (Palm Springs) and KLGB (Long Beach).
When the tutorial first starts up, you can type a two-character shortcut. This shortcut is a letter for the page to jump to, and a number indicating the sequence in the tutorial: 1 is the first step, 9 is the last step.
For example: D3 for Departure page, 3rd step. R9 for Route page, 9th step.
Each shortcut resets the app, as if you're starting it for the first time.
The shortcuts also automatically switch the app to free play - removing the tutorial pages.
A comprehensive list of shortcuts, including links, and a reference to the associated tutorial page:
Each tutorial page is named: this name can be used to create a link to that page.
For example, the out-of-date database scenario is named
tut-basics-db1. The link to the start of this scenario is:
These links reset the app, as if you're starting it for the first time.
Unlike shortcuts, these links leave the tutorial running: i.e. they do not enter free play.
Each link has an associated QR code, which may be convenient on a slideshow or ground school presentation.
tutorial-lobby![]() | Swipe up to start the tutorial from the beginning. Or press any function key INIT REF through NAV RAD to get a tutorial of that key. News update! Swipe up for details
| |
tut-lobby![]() | Swipe up to start the tutorial from the beginning. Or press any function key INIT REF through NAV RAD to get a tutorial of that key. News update! Swipe up for details
| |
news![]() | ||
tut-basics0![]() | IDENT MODEL ENGINES 767-3003W CF6-80C2B6 NAV DATA ACTIVE FMS2310001 SEP07OCT05/23 2309001 AUG10SEP07/23 OP PROGRAM CO DATA 3411HNP02C10 BCG01902 OPC DRAG/FF 3409BCG01J65 +0.0/+0.0 ------------------------ <INDEX POS INIT> |
Swipe up, or tap anywhere on this tutorial text box
to continue.
You can always scroll to review earlier sections of the tutorial.
|
tut-arrow![]() | The
![]() Sometimes, you will be instructed to press one of the keys.
The ⊻ | |
tut-basics-x![]() |
At any point, you can close the tutorial with the
![]() You can then use this app in free play. To get back to the tutorial, use the MENU key, then press the — button next to TUTORIAL>. ⊻ | |
tut-scratchpad![]() | This is the Scratchpad.
Anything you type will show up here. ⊻ | |
tut-basics-lsk1![]() | These are Line Select Keys - LSKs. The LSKs on the left are 1L through 6L.
This is 1L. ⊻ | |
tut-basics-lsk2![]() | This is 6L.
⊻ | |
tut-basics-lsk3![]() | The LSKs on the right are 1R through 6R.
This is 4R. ⊻ | |
tut-basics-db1![]() | Scenario: out-of-date database
Every once in a while you will show up to the airplane, and the FMS aviation database will have expired. Let's explore that scenario now. The scratchpad now has a message. This message is telling us we need to update the active database. Note that the date range under the ACTIVE label has expired. Note also that the MSG light is on. ⊻ | |
tut-basics-db-clr![]() | None of the Line Select Keys work when
there's an error message in the scratchpad.
Before we proceed, we must clear out the message. Keep an eye on the MSG light. Press the CLR key to continue | |
tut-basics-db2![]() | IDENT MODEL ENGINES 767-3003W CF6-80C2B6 NAV DATA ACTIVE FMS2310001 AUG10SEP07/23 2309001 SEP07OCT05/23 OP PROGRAM CO DATA 3411HNP02C10 BCG01902 OPC DRAG/FF 3409BCG01J65 +0.0/+0.0 ------------------------ <INDEX POS INIT> | Sure enough, the message on the scratchpad goes away,
and the MSG light goes out.
Now we can update the database! Use 3R to line select the up-to-date database. Press the 3R key to continue |
tut-basics-db3![]() | IDENT MODEL ENGINES 767-3003W CF6-80C2B6 NAV DATA ACTIVE FMS2310001 AUG10SEP07/23 2309001 SEP07OCT05/23 OP PROGRAM CO DATA 3411HNP02C10 BCG01902 OPC DRAG/FF 3409BCG01J65 +0.0/+0.0 ------------------------ <INDEX POS INIT> SEP07OCT05/23 | The entry shows up in the scratchpad.
⊻ |
tut-basics-db4![]() | Use 2R to set the active database to what's displayed in the scratchpad.
Press the 2R key to continue | |
tut-basics-db5![]() | IDENT MODEL ENGINES 767-3003W CF6-80C2B6 NAV DATA ACTIVE FMS2310001 SEP07OCT05/23 2309001 AUG10SEP07/23 OP PROGRAM CO DATA 3411HNP02C10 BCG01902 OPC DRAG/FF 3409BCG01J65 +0.0/+0.0 ------------------------ <INDEX POS INIT> | You have switched the active database to the selected database.
⊻ |
tut-basics-prompt1![]() | This is a prompt.
Pressing the LSK next to a prompt will perform an action — in this case, to go to the INDEX page. ⊻ | |
tut-basics-prompt2![]() | This prompt will go to the POS INIT page.
⊻ | |
tut-basics-prompt3![]() | Every page in the pre-flight sequence can be stepped through
by pressing 6R.
Press the 6R key to continue | |
tut-basics-data1![]() Shortcut: P1
| POS INIT 1/4 LAST POS N25°47.4 W080°18.0 REF AIRPORT ---- GATE #1028 UTC(GPS) GPS POS 1251Z N25°47.4 W080°18.0 SET IRS POS □□□°□□.□ □□□□°□□.□ ------------------------ <INDEX ROUTE> | Squares indicate missing required data - the page isn't complete
until something is entered.
This is also known as a box prompt. ⊻ |
tut-basics-data2![]() | Dashes indicate optional data.
This is also known as a dash prompt. ⊻ | |
tut-basics-data3![]() | Dealing with mistakes
Let's set the REF AIRPORT. But, we'll make an intentional mistake to see how the FMS deals with it. ⊻ | |
tut-basics-data3a![]() | Type in KMIXA – or anything, really, as long as it's not a
valid 4-letter ICAO airport identifier.
Then, press the LSK next to REF AIRPORT. Type KMIXA and press 2L to continue | |
tut-basics-data3b![]() | POS INIT 1/4 LAST POS N25°47.4 W080°18.0 REF AIRPORT ---- GATE #1028 UTC(GPS) GPS POS 1251Z N25°47.4 W080°18.0 SET IRS POS □□□°□□.□ □□□□°□□.□ ------------------------ <INDEX ROUTE> INVALID ENTRY | An error message appears over our input.
Messages stack over previous scratchpad entries, like cards. ⊻ |
tut-basics-data3c![]() | And sure enough, the message light
is on.
⊻ | |
tut-basics-data3d![]() | The CLR key will remove the
top message from the scratchpad.
If there are multiple messages, the next one will appear. CLR removes one message at a time. Press the CLR key to continue | |
tut-basics-data3e![]() | POS INIT 1/4 LAST POS N25°47.4 W080°18.0 REF AIRPORT ---- GATE #1028 UTC(GPS) GPS POS 1251Z N25°47.4 W080°18.0 SET IRS POS □□□°□□.□ □□□□°□□.□ ------------------------ <INDEX ROUTE> KMIXA | Your original entry appears in the scratchpad.
The message light is out. Now, the CLR key will erase one character at a time from the scratchpad, like a backspace. ⊻ |
tut-basics-data3f![]() | Edit your entry to fix the mistake.
Use the CLR key and letter keys to edit the scratchpad. When KMIA is in the scratchpad, press 2L to continue | |
tut-basics-data4![]() Shortcut: P2
| POS INIT 1/4 LAST POS N25°47.4 W080°18.0 REF AIRPORT KMIA N25°47.7 W080°17.4 GATE -----#1028 UTC(GPS) GPS POS 1251Z N25°47.4 W080°18.0 SET IRS POS □□□°□□.□ □□□□°□□.□ ------------------------ <INDEX ROUTE> | Success!
We can now use the KMIA airport's latitude/longitude for position initialization.
Remember, anything you type will go into the scratchpad. There are no blinking cursors. ⊻ |
tut-basics-data5![]() | Copy and paste
When the scratchpad is empty, pressing the LSK next to a data line will copy that data into the scratchpad. When there's data in the scratchpad, pressing the LSK next to a data entry line will move what you entered to that data entry item. Choose LSK 1R or 4R to copy the co-ordinates into the scratchpad. Then, move that entry into SET IRS POS by pressing 5R. Press 1R or 4R, then press 5R to continue | |
tut-basics-pages1![]() | POS INIT 1/4 LAST POS N25°47.4 W080°18.0 REF AIRPORT KMIA N25°47.7 W080°17.4 GATE -----#1028 UTC(GPS) GPS POS 1251Z N25°47.4 W080°18.0 SET IRS POS N25°47.4 W080°18.0 ------------------------ <INDEX ROUTE> | When information cannot fit on one screen, it is broken into
pages.
The page you're on is shown here. We're on page 1 of 4. ⊻ |
tut-basics-pages2![]() | Use the PREV PAGE and NEXT PAGE keys to move between the pages.
If you're on the first page, PREV PAGE will jump to the last page. If you're on the last page, NEXT PAGE will jump to the first page. Go ahead and explore the other pages to continue | |
tut-basics-pages3![]() | When you're done exploring the POS INIT and POS REF pages, go to page 1 and select the ROUTE> prompt.
Go to page 1 and press 6R to continue | |
tut-basics-dspy![]() | RTE 1 1/2 ORIGIN DEST □□□□ □□□□ RUNWAY FLT NO ----- ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 ACTIVATE> | This is the DSPY - display - light.
Basically, this lights up when:
The full rules are rather complex, and we'll cover them later in the tutorial. ⊻ |
tut-route-origin1![]() | Entering a route
Let's program a flight from Miami, Florida (KMIA) to San Juan, Puerto Rico (TJSJ). ⊻ | |
tut-route-origin2![]() | Type KMIA and put it into 1L.
Use the CLR key if you make a mistake. | |
tut-route-origin3![]() Shortcut: R2
| RTE 1 1/2 ORIGIN DEST KMIA □□□□ RUNWAY FLT NO ----- ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 ACTIVATE> | Once the ORIGIN airport is set,
the RUNWAY can be set.
We can set the runway here, or later by pressing the DEP ARR key. ⊻ |
tut-route-dest1![]() | Our destination is San Juan, Puerto Rico (TJSJ).
Type TJSJ and press 1R to continue | |
tut-route-dep1![]() Shortcut: R3
| RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO ----- ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 ACTIVATE> | Our clearance is KLADA2 BITAC Y290 BEANO.
⊻ |
tut-route-dep2![]() | KLADA2 is a departure procedure.
Departure procedures can be selected with the DEP ARR key. Press DEP ARR to continue | |
tut-route-dep4![]() | Arrival procedures, approach procedures, and runways for your destination airport can be accessed here.
⊻ | |
tut-route-dep4a![]() |
So can the arrivals, approaches, and runways for your origin airport, in case you need to return in a hurry.
⊻ | |
tut-route-dep3![]() Shortcut: D1
| DEP/ARR INDEX RTE 1 <DEP KMIA ARR> TJSJ ARR> --------RTE 2 ---------- <DEP ARR> ARR> ------------------------ DEP OTHER ARR <---- ----> | Departure procedures and runways
for your origin airport can be accessed here.
⊻ |
tut-route-dep5![]() | Go ahead and select the <DEP prompt.
Press 1L to continue | |
tut-route-dep6![]() Shortcut: D2
| KMIA DEPARTURES 1/3 SIDS RTE 1 RUNWAYS ALTNN1 08L TRANS BNGOS3 08R DORRL1 09 FLMGO1 12 FOLZZ2 26L ------------------------ <INDEX ROUTE> | Departure procedures are on the left, and runways are on the right.
Use the PREV PAGE and NEXT PAGE keys to find the page with the KLADA2 departure. |
tut-route-dep7![]() | KMIA DEPARTURES 2/3 SIDS RTE 1 RUNWAYS GLADZ2 26R TRANS GWAVA2 27 HURCN3 30 KLADA2 LIFRR1 ------------------------ <INDEX ROUTE> | Once you find the KLADA2 departure, select it using the LSK next to it.
Press the LSK next to KLADA to continue |
tut-route-dep8![]() Shortcut: D3
| KMIA DEPARTURES 1/2 SIDS RTE 1 RUNWAYS KLADA2<SEL> 08L TRANS BITAC 08R JAGOR 09 RAJAY 12 26L ------------------------ <INDEX ROUTE> | If the procedure has transitions, they show up here.
We're looking for the BITAC transition. Press the LSK next to the BITAC transition to continue |
tut-route-dep9![]() | KMIA DEPARTURES 1/2 SIDS RTE 1 RUNWAYS KLADA2<SEL> 08L TRANS BITAC <SEL> 08R 09 12 26L ------------------------ <INDEX ROUTE> | Only the runways appropriate to the departure are
shown now.
If you had selected the runway first, only the departures appropriate to the runway would be shown. ⊻ |
tut-route-dep10![]() | Choose a runway and select the ROUTE> prompt.
Press a LSK 1R .. 5R, then press 6R to continue | |
tut-route1![]() Shortcut: R4
| RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 ACTIVATE> | We're back to the RTE pages.
Page 1 of the RTE pages always shows this summary information. Notice that the runway has been filled in. ⊻ |
tut-route2![]() | There are more pages available.
Press the NEXT PAGE key to continue | |
tut-route3![]() Shortcut: R5
| RTE 1 2/2 VIA TO KLADA2.BITAC BITAC ----- ----- ------------------------ <RTE 2 ACTIVATE> | Here's our selected KLADA2 departure.
The rest of our clearance is Y290 BEANO.
Y290 is an airway, so it goes into the VIA column. Type Y290 and press 2L to continue |
tut-route4![]() Shortcut: R6
| RTE 1 2/2 VIA TO KLADA2.BITAC BITAC THEN Y290 □□□□□ ----- ------------------------ <RTE 2 ACTIVATE> | We take Y290 to BEANO.
Endpoints go into the TO column.
Type BEANO and press 2R to continue |
tut-route5![]() Shortcut: R7
| RTE 1 2/2 VIA TO KLADA2.BITAC BITAC Y290 BEANO ----- ----- ------------------------ <RTE 2 ACTIVATE> | The RTE page shows our route as a set
of named procedures or airways.
Each airway or procedure may have multiple legs. To look at each specific step in the flight plan, use the LEGS page. Press the LEGS key to continue |
tut-route6![]() | RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 118° 24NM KLADA ---/------ 120° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS ACTIVATE> | One clearance — and one route, but two different ways to look at the same thing: RTE and LEGS.
⊻ |
tut-route7![]() | Let's go back to the RTE page.
Press the RTE key to continue | |
tut-route8![]() | RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 ACTIVATE> | When we're on the ground, the RTE key will take us to page one of the RTE pages.
Now, to fly this route, we need to activate it. Select the ACTIVATE> prompt to continue |
tut-route9![]() Shortcut: R8
| RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND ------------------------ ALTN> <ERASE PERF INIT> | The Execute Key
The light by the EXEC key illuminates any time the flight path of the airplane is about to be changed. The change won't be made until the EXEC key is pressed. Good CRM requires that any change to the flight path of the airplane is confirmed by both pilots. The pilot making the entries should ask “verify?” and the other pilot should check and respond “execute.” ⊻ |
tut-route10![]() | Your co-pilot has reviewed the changes, and says
“execute.”
Press the EXEC key to continue | |
tut-perf1![]() Shortcut: R9
| ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 PERF INIT> | We're ready to proceed to performance initialization.
Select the PERF INIT> prompt to continue |
tut-perf2![]() Shortcut: F1
| PERF INIT GR WT CRZ ALT □□□.□ □□□□□ FUEL COST INDEX 63.6LB CALC □□□□ ZFW □□□.□ RESERVES CRZ CG □□□.□ 25.0% REQUEST STEP SIZE <SEND ICAO ------------------------ <INDEX TAKEOFF> | All of the data on this page can be entered in any order.
Pilots typically get cruise altitude, cost index, and reserves from a flight planning department. Weight & Balance might come from another department, perhaps right before the scheduled departure time. ⊻ |
tut-perf3![]() | CRZ ALT
Our filed cruise altitude is Flight Level 370. The FMS will accept 37000, but it also understands FL370. Three digit numbers are interpreted as flight levels, so you can also type 370. Enter flight level 370 (any way you choose) and press 1R to continue | |
tut-perf4![]() | PERF INIT GR WT CRZ ALT □□□.□ FL370 FUEL COST INDEX 63.6LB CALC □□□□ ZFW □□□.□ RESERVES CRZ CG □□□.□ 25.0% REQUEST STEP SIZE <SEND ICAO ------------------------ <INDEX TAKEOFF> | COST INDEX
The cost index is a measure of the dry cost of the airplane versus the cost of fuel. Higher numbers will burn more fuel, and get there faster. Lower numbers will burn less fuel, but get there slower. Enter a number (say 60) and press the 2R key to continue |
tut-perf5![]() | PERF INIT GR WT CRZ ALT □□□.□ FL370 FUEL COST INDEX 63.6LB CALC 60 ZFW □□□.□ RESERVES CRZ CG □□□.□ 25.0% REQUEST STEP SIZE <SEND ICAO ------------------------ <INDEX TAKEOFF> | RESERVES
Our flight release says: ALTERNATE 00:24 005000 RESERVE 00:31 005616 HOLDING 00:30 003923 EXTRA 00:00 000000 Adding these up (14539) gives us all the fuel for everything EXCEPT getting to our destination. Round to the nearest decimal in thousands of pounds gives us 14.5 ⊻ |
tut-perf6![]() | RESERVES
Enter 14.5 into RESERVES. Type 14.5 and press 4L to continue | |
tut-perf7![]() | PERF INIT GR WT CRZ ALT □□□.□ FL370 FUEL COST INDEX 63.6LB CALC 60 ZFW □□□.□ RESERVES CRZ CG 14.5 25.0% REQUEST STEP SIZE <SEND ICAO ------------------------ <INDEX TAKEOFF> | RESERVES
If our calculated fuel at our destination is less than 14.5 (thousand pounds), the FMS will warn us INSUFFICIENT FUEL. ⊻ |
tut-perf8![]() | ZFW
Our weight & balance paperwork has arrived! Our Zero Fuel Weight is 214,500 pounds and must go into ZFW. Type 214.5 and press 3L to continue | |
tut-perf9![]() | PERF INIT GR WT CRZ ALT 278.1 FL370 FUEL COST INDEX 63.6LB CALC 60 ZFW 214.5 RESERVES CRZ CG 14.5 25.0% REQUEST STEP SIZE <SEND ICAO ------------------------ <INDEX TAKEOFF> | The FMS has calculated our gross weight.
If we had entered a number into GR WT, the FMS would calculate our ZFW – Zero Fuel Weight. ⊻ |
tut-perf10![]() | One last page before the preflight sequence is complete.
Select the TAKEOFF> prompt to continue | |
tut-takeoff1![]() Shortcut: T1
| TAKEOFF REF 1/2 FLAPS V1 □□ --- THRUST VR --°C TO --- CG TRIM V2 □□% --- RWY/POS TOGW 09 /---- ---.- REQUEST <SEND ---------------- PRE-FLT <INDEX COMPLETE | Acceptable takeoff flaps on a Boeing 767 are 5,
15, or 20.
Enter a flap setting and press 1L to continue |
tut-takeoff2![]() | TAKEOFF REF 1/2 FLAPS V1 5° --- THRUST VR --°C TO --- CG TRIM V2 □□% --- RWY/POS TOGW 09 /---- ---.- REQUEST <SEND ---------------- PRE-FLT <INDEX COMPLETE | The THRUST setting is for assumed temperature
reduced thrust.
This is optional. Set a value or proceed to the next step. ⊻ |
tut-takeoff3![]() | CG is required. This comes from your weight & balance paperwork, typically under %MAC or Mean Aerodynamic Chord.
Enter a CG (say 25) to continue | |
tut-takeoff4![]() | TAKEOFF REF 1/2 FLAPS V1 5° --- THRUST VR --°C TO --- CG TRIM V2 25% 3.3 --- RWY/POS TOGW 09 /---- ---.- REQUEST <SEND ---------------- PRE-FLT <INDEX COMPLETE | The 6R PRE-FLT prompt changes to COMPLETE
when all required data have been entered.
If anything has been missed, the 6R prompt will take you to the required page. ⊻ |
tut-gen1![]() | Congratulations!
You have completed a basic preflight!
You can use the INIT REF key when you're on an unfamiliar page, or you don't know what to do next for the preflight. ⊻ | |
tut-gen2![]() | If you're on the ground before takeoff,
the INIT REF key takes you to the first page that needs input.
If no pages need input, it will take you to the TAKEOFF page. If you're in the air, it will take you to the APPROACH REF page. ⊻ | |
tut-gen3![]() | To see all the initialization pages, select the
<INDEX prompt.
Press the 6L key to continue | |
tut-summary![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | You have completed the pre-flight tutorial.
If you ever get lost, use the INIT REF key and follow the <INDEX prompt. That will always take you to a set of familiar pages. Rate This App! If you have a moment, please rate this app. This will help other pilots who may find this tutorial useful. ⊻ |
ref1![]() |
There is an in-depth tutorial for each of the function keys
— all the keys from INIT REF to
NAV RAD.
Press any of the function keys to continue | |
ref-init-ref1![]() |
The INIT REF key takes you to an
appropriate initialization page.
Each of these pages will have an <INDEX prompt. Press 6L to continue | |
init-ident1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> |
We will be looking at each page on this index, in order.
Let's start with the <IDENT prompt. Press 1L to continue |
init-ident2![]() | IDENT MODEL ENGINES 767-3003W CF6-80C2B6 NAV DATA ACTIVE FMS2310001 SEP07OCT05/23 2309001 AUG10SEP07/23 OP PROGRAM CO DATA 3411HNP02C10 BCG01902 OPC DRAG/FF 3409BCG01J65 +0.0/+0.0 ------------------------ <INDEX POS INIT> | The IDENT page is the first page shown on power-up.
This page allows us to confirm the specific airframe and engine types. We can also confirm that the nav database is up-to-date. Switching databases is easy: LSK 3R, then 2R. Switching databases erases any flight plans that we have entered! Select the <INDEX prompt to continue |
init-pos1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | The <POS prompt leads to the POS INIT
pages.
Press 2L to continue |
init-pos2![]() | POS INIT 1/4 LAST POS N25°47.4 W080°18.0 REF AIRPORT KMIA N25°47.7 W080°17.4 GATE -----#1028 UTC(GPS) GPS POS 1251Z N25°47.4 W080°18.0 SET IRS POS N25°47.4 W080°18.0 ------------------------ <INDEX ROUTE> |
This page sets the IRS - Inertial Reference System - position.
The INIT REF key will take you directly to this page on these conditions:
Select the <INDEX prompt to continue |
init-perf1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | The <PERF prompt leads to the PERF INIT page.
Press 3L to continue |
init-perf2![]() | PERF INIT GR WT CRZ ALT 278.1 FL370 FUEL COST INDEX 63.6LB CALC 60 ZFW 214.5 RESERVES CRZ CG 14.5 25.0% REQUEST STEP SIZE <SEND ICAO ------------------------ <INDEX TAKEOFF> |
The INIT REF key will take you directly to this page on these
conditions:
Select the <INDEX prompt to continue |
init-takeoff1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | Select the <TAKEOFF prompt.
Press 4L to continue |
init-takeoff2![]() | TAKEOFF REF 1/2 FLAPS V1 5° --- THRUST VR --°C TO --- CG TRIM V2 25% 3.3 --- RWY/POS TOGW 09 /---- ---.- REQUEST <SEND ---------------- PRE-FLT <INDEX COMPLETE |
We've seen these pages before, but it's worth going into a little more
detail here.
The TAKEOFF REF section has two pages. Press NEXT PAGE to continue |
init-takeoff3![]() | TAKEOFF REF 2/2 ACCEL HT 1000FT WIND ---°/---KT RWY WIND LIM TOGW REF OAT ---°C ------------------------ <INDEX | Note that the ACCEL HT value is
in smaller lettering.
In general, default values and FMS-computed values are in this small lettering. You can override this value. Type 1500 and press 2R to continue |
init-takeoff4![]() | TAKEOFF REF 2/2 ACCEL HT 1500FT WIND ---°/---KT RWY WIND LIM TOGW REF OAT ---°C ------------------------ <INDEX | Our overriding value is in normal lettering.
To erase our modification, press the delete key – the DEL key on the bottom row of keys. Press the DEL key to continue |
init-takeoff5![]() | TAKEOFF REF 2/2 ACCEL HT 1500FT WIND ---°/---KT RWY WIND LIM TOGW REF OAT ---°C ------------------------ <INDEX DELETE | The DELETE message is displayed in the scratchpad. This is an instruction to the FMS to delete the data next to whatever LSK we press.
Now line select the value to delete. Press 2R to continue |
init-takeoff6![]() | TAKEOFF REF 2/2 ACCEL HT 1000FT WIND ---°/---KT RWY WIND LIM TOGW REF OAT ---°C ------------------------ <INDEX | The ACCEL HT is now back to its
default value.
Select the <INDEX prompt to continue |
init-approach1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> |
Select the <APPROACH prompt.
Press 5L to continue |
init-approach2![]() | APPROACH REF 1/1 GROSS WT FLAPS VREF 278.1 20° 144KT 25° 139KT 30° 135KT KMIA09 13016FT3967M ILS 09 FRONT CRS 110.90IBUL 92° ------------------------ <INDEX |
The APPROACH REF page gives you VREF speeds based on
landing flaps.
If the FMS knows the current weight, it is displayed here. But we can also enter a different weight. Let's suppose we burn 40,000 pounds of fuel heading to our destination. 278.1 - 40.0 = 238.1 Type 238.1 and press 1L |
init-approach3![]() | APPROACH REF 1/1 GROSS WT FLAPS VREF 238.1 20° 133KT 25° 128KT 30° 124KT KMIA09 13016FT3967M ILS 09 FRONT CRS 110.90IBUL 92° ------------------------ <INDEX |
New VREF speeds are calculated.
Note that if you leave this page, GROSS WT is reset to your current weight. Select the <INDEX prompt to continue |
init-nav-data1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | |
init-nav-data2![]() | REF NAV DATA IDENT FREQ ------ LATITUDE LONGITUDE ELEVATION FT NAVAID INHIBIT ---- ---- VOR ONLY INHIBIT ---- ---- -------------VOR/DME NAV <INDEX OFF←→ON> | |
init-nav-data3![]() | REF NAV DATA IDENT FREQ SKIPS LATITUDE LONGITUDE N25°33.2 W079°16.5 ELEVATION FT NAVAID INHIBIT ---- ---- VOR ONLY INHIBIT ---- ---- -------------VOR/DME NAV <INDEX OFF←→ON> | |
init-nav-data3a![]() | ||
init-nav-data4![]() | REF NAV DATA IDENT FREQ DHP 113.90 LATITUDE LONGITUDE N25°48.0 W080°20.9 MAG VAR ELEVATION W4 10FT NAVAID INHIBIT ---- ---- VOR ONLY INHIBIT ---- ---- -------------VOR/DME NAV <INDEX OFF←→ON> | |
init-nav-data4a![]() | REF NAV DATA IDENT FREQ KMIA LATITUDE LONGITUDE N25°47.7 W080°17.4 ELEVATION 10FT NAVAID INHIBIT ---- ---- VOR ONLY INHIBIT ---- ---- -------------VOR/DME NAV <INDEX OFF←→ON> | |
init-nav-data4b![]() | REF NAV DATA IDENT FREQ RW08 LATITUDE LONGITUDE N18°26.3 W066°00.9 LENGTH ELEVATION 10400FT 10FT NAVAID INHIBIT ---- ---- VOR ONLY INHIBIT ---- ---- -------------VOR/DME NAV <INDEX OFF←→ON> | |
init-nav-data5![]() | ||
init-nav-data6![]() | ||
init-nav-data7![]() | REF NAV DATA IDENT FREQ RW08 LATITUDE LONGITUDE N18°26.3 W066°00.9 LENGTH ELEVATION 10400FT 10FT NAVAID INHIBIT VKZ ---- VOR ONLY INHIBIT ---- ---- -------------VOR/DME NAV <INDEX OFF←→ON> | |
init-altn1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> |
Select the ALTN> prompt.
Press 2R to continue |
init-altn2![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KHST > KFLL > REQUEST ALTN INHIBIT <SEND ----/---- WXR REQUEST <SEND | This page displays four alternates for immediate diversion.
On the ground, this list shows the four closest airports with acceptable runways. Once you're in the air, the ETA and FUEL columns fill in. Then the list is sorted, with the shortest ETA at the top. ⊻ |
init-altn3![]() |
Let's say that the weather in Homestead (KHST) is below minimums. We can inhibit up to two airports with ALTN INHIBIT.
Type KHST and press 5R to continue | |
init-altn4![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KFLL > KTNT > REQUEST ALTN INHIBIT <SEND ----/KHST WXR REQUEST <SEND |
Notice that KHST is off the list, and another airport appears on line 4.
To inhibit two airports, use the / slash key. Since we want to set the entry before the slash, we type the airport identifier and then type / . ⊻ |
init-altn4a![]() |
Let's add Fort Lauderdale (KFLL) to the inhibit list.
We can type KFLL/ to set the first airport, or we could also type KFLL/KHST to set both at once. Type KFLL/ or KFLL/KHST and press 5R to continue | |
init-altn5![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KTNT > KPBI > REQUEST ALTN INHIBIT <SEND KFLL/KHST WXR REQUEST <SEND | Use the DEL key to delete the ALTN INHIBIT airports.
Press the DEL key to continue |
init-altn6![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KTNT > KPBI > REQUEST ALTN INHIBIT <SEND KFLL/KHST WXR REQUEST <SEND DELETE | The DELETE message is displayed in the scratchpad. This is an instruction to the FMS to delete the data next to whatever LSK we press.
Press 5R to continue |
init-altn7![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KHST > KFLL > REQUEST ALTN INHIBIT <SEND ----/---- WXR REQUEST <SEND | We're back to our original list.
We can also add our own alternates. Let's put KRSW (Southwest Florida International) at the top of the list. Type KRSW and press 1L to continue |
init-altn8![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KHST > KRSW > REQUEST ALTN INHIBIT <SEND ----/---- WXR REQUEST <SEND | Because KRSW is farther than the other airports, it shows up at the bottom of the list.
We can remove our entry by using the DEL key and line-selecting KRSW. Press the DEL key to continue |
init-altn9![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KHST > KRSW > REQUEST ALTN INHIBIT <SEND ----/---- WXR REQUEST <SEND DELETE | Now, line select KRSW
Press 4L to continue |
init-altn10![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KHST > KFLL > REQUEST ALTN INHIBIT <SEND ----/---- WXR REQUEST <SEND | The prompts on the right take us to the ALTN airport page for the selected airport.
Choose one now. Press 1R .. 4R to continue |
init-altn11![]() | KMIA ALTN 1/4 VIA ALT DIRECT TO <SEL> ----- ECON L00 OFFSET ---- OVERHEAD WIND JAMBA ---°/--- ALT/OAT -----/---°c ETA/FUEL <ENG OUT ------------------------ <ALTN | Note that there are four pages, one for each
airport on the previous page's list.
Select the <ALTN prompt to continue |
init-altn12![]() | ALTN 1/2 ETA FUEL KMIA > KOPF > KHST > KFLL > REQUEST ALTN INHIBIT <SEND ----/---- WXR REQUEST <SEND | Experiment with this page. When done, we'll explore
page 2.
Press the NEXT PAGE key to continue |
init-altn13![]() | ALTN LIST 2/2 REQUEST ALTN LIST <SEND PURGE> ------------------------ <INDEX | If your airline supports it, you can have
your dispatch office send you a list of alternates.
The ALTN page 2 lists these previously uplinked alternates. You cannot change this list. You can send a request to get a list of alternates uplinked. Select the <INDEX prompt to continue |
init-fmc-comm1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | Select the FMC COMM> prompt.
Press 3R to continue |
init-fmc-comm2![]() | FMC COMM <RTE 1 POS REPORT> <ALTN <PERF <TAKEOFF DATA LINK <DES FORECAST READY | This is the same page you get to
by using the FMC COMM key.
⊻ |
init-fmc-comm3![]() | You may have noticed that some
pages have <SEND prompts.
The RTE page has them, for example. Press the RTE key, or select the <RTE 1 prompt to continue | |
init-fmc-comm4![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 TAKEOFF> | There they are!
Press the FMC COMM key to continue |
init-fmc-comm5![]() | FMC COMM <RTE 1 POS REPORT> <ALTN <PERF <TAKEOFF DATA LINK <DES FORECAST READY | The FMC COMM key
(and the FMC COMM> prompt on the INIT/REF INDEX page) is a quick link to all pages that have a SEND function.
⊻ |
init-fmc-comm6![]() | Let's get back to the INIT/REF INDEX page.
Press INIT REF to continue | |
init-fmc-comm7![]() | TAKEOFF REF 1/2 FLAPS V1 5° --- THRUST VR --°C TO --- CG TRIM V2 25% 3.3 --- RWY/POS TOGW 09 /---- ---.- REQUEST <SEND ---------------- PRE-FLT <INDEX COMPLETE | Select the <INDEX prompt.
Press 6L to continue |
init-maint1![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | The MAINT> prompt only shows up on the ground.
Select the MAINT> prompt. Press R6 to continue |
init-maint2![]() | MAINTENANCE INDEX <AIRLINE POLICY <IRS MONITOR <CROSS LOAD <SENSORS <DISCRETES ------------------------ <INDEX | Most of these entries are for maintenance,
but there's one entry that may be of interest to pilots.
Select the <IRS MONITOR prompt to continue |
init-maint3![]() | IRS MONITOR IRS L 0.2NM/HR IRS C 0.3NM/HR IRS R 0.2NM/HR ------------------------ <INDEX | This page displays the hourly drift for
each of the IRS units.
Select the <INDEX prompt to continue |
init-maint4![]() | MAINTENANCE INDEX <AIRLINE POLICY <IRS MONITOR <CROSS LOAD <SENSORS <DISCRETES ------------------------ <INDEX | Select the <INDEX prompt.
Press 6L to continue |
init-summary![]() | INIT/REF INDEX <IDENT NAV DATA> <POS ALTN> <PERF FMC COMM> <TAKEOFF <APPROACH MAINT> | Summary
The INIT REF key will take you to the first incomplete initialization page. If all init pages are complete, the INIT REF key will take you to the TAKEOFF REF page. If in the air, the INIT REF key will take you to the APPROACH REF page. Starting from the IDENT page, the entire preflight sequence can be stepped through to TAKEOFF. The APPROACH REF page shows your VREF speed at any specified weight. ⊻ |
ref-rte1![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 TAKEOFF> |
On the ground, the RTE key brings up page 1 of the RTE
(route) pages.
Page 1 is a summary.
In the air, this key brings up page 2. Press the NEXT PAGE key to continue |
ref-rte2![]() | ACT RTE 1 2/2 VIA TO KLADA2.BITAC BITAC Y290 BEANO ----- ----- ------------------------ <RTE 2 TAKEOFF> | The rest of the RTE pages show your flight
plan.
The format is similar to a filed flight plan, or the clearance you receive from ATC. New pages will be created as you add more elements to your route. Let's go back to the first summary page. Press the PREV PAGE key or the RTE key to continue |
ref-rte3![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 TAKEOFF> | There is storage for two routes. We are currently looking at RTE 1.
We normally put our filed route in RTE 1. ⊻ |
ref-rte4![]() | The route that the airplane will
actually fly is the active route.
The ACT on the title indicates that this route (RTE 1) is the active route. ⊻ | |
ref-rte5![]() | The <RTE 2 prompt lets us view and modify
the second route.
We can use this second route for flying to our alternate, or for the next trip, or as a backup of route 1. Select the <RTE 2 prompt. Press 6L to continue | |
ref-rte6![]() | RTE 2 1/2 ORIGIN DEST □□□□ □□□□ RUNWAY FLT NO ***** ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 1 ACTIVATE> | We are looking at route 2.
Note that the DSPY light is on. This light comes on when you could be looking at the active leg, but aren't. Specifically, it is illuminated on RTE, LEGS, RTE DATA, HOLD and HOLD LEGS pages when you're not looking at the active route and the active (first) leg. Select the <RTE 1 prompt. Press 6L to continue |
ref-rte7![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 TAKEOFF> | This RTE COPY> prompt copies route 1 into
route 2.
Let's try it. Select the RTE COPY> prompt. Press 4R to continue |
ref-rte8![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT RTE COPY <SEND COMPLETE ------------------------ ALTN> <RTE 2 TAKEOFF> | The prompt changes to a confirmation that the
copy is successful.
Let's look at the new route. Select the <RTE 2 prompt. Press 6L to continue |
ref-rte9![]() | RTE 2 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND COMPLETE ------------------------ ALTN> <RTE 1 ACTIVATE> | Sure enough, the active route has been copied to route 2.
Note the ACTIVATE> prompt. Only one RTE can be active at a time. Selecting this prompt will activate RTE 2. We're not doing that now. Press 6L to continue |
rte-summary![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 TAKEOFF> | Summary
The RTE key brings up the RTE pages. Page 1 is a summary, the other pages show your flight plan as entered. There is room for two routes. Only one can be active. Pressing the EXEC key is required after activating a route or changing the active route. ⊻ |
ref-deparr1![]() | KMIA DEPARTURES 1/3 SIDS RTE 1 RUNWAYS ALTNN1 08L TRANS BNGOS3 08R DORRL1 <ACT> 09 FLMGO1 12 FOLZZ2 26L ------------------------ <INDEX ROUTE> |
Use the DEP ARR key to add named departure and
arrival/approach procedures to your flight plan.
The page it goes to depends on the phase of flight:
We have an active route, so it takes us to the DEPARTURES page. To get to the index, select the <INDEX prompt. Press 6L to continue |
ref-deparr2![]() | DEP/ARR INDEX RTE 1 (ACT) <DEP KMIA ARR> TJSJ ARR> --------RTE 2 ---------- <DEP ARR> ARR> ------------------------ DEP OTHER ARR <---- ----> | If RTE 1 is active, ACT is shown here.
⊻ |
ref-deparr3![]() | If RTE 2 is active, then ACT will be shown here.
⊻ | |
ref-deparr4![]() | FMS Pro Tip: Don't assume that you're using RTE 1.
You will get accustomed to using RTE 1. The key sequence DEP ARR and 2R will become a habit - a bad habit. ⊻ | |
ref-deparr5![]() | One day you'll be using RTE 2 as the active route.
Perhaps you're flying to your alternate?
But now, the correct key sequence to load an approach is: DEP ARR, 4R. ⊻ | |
ref-deparr6![]() | The OTHER section allows us to review departure and arrival information for other airports.
⊻ | |
ref-deparr7![]() | Let's try it out for KRSW (Southwest Florida International)
Type KRSW and select the ARR> prompt. | |
ref-deparr8![]() | KRSW ARRIVALS 1/2 STARS APPROACHES JOSFF5 ILS 06 SHFTY5 LOC 06 TYNEE2 RNV 06 RNV 24 VDM 24 ------------------------ <INDEX | This is only to show you the procedures and runways.
None of these entries can be selected. Select the <INDEX prompt to continue |
deparr-summary![]() |
Summary
DEP ARR is for named procedures (both departures and arrivals), instrument approaches, and runways. Be mindful when you're using RTE 2. Runways, approaches, and procedures can be listed for any airport with the OTHER prompts. ⊻ | |
ref-atc1![]() | ATC LOGON/STATUS 1/2 LOGON TO □□□□ FLT NO TAIL NO □□□□□□□ MAX U/L DELAY ---SEC -------------- DATA LINK <ATC INDEX READY | The ATC key goes to
a CPDLC login page.
CPDLC - Controller Pilot Data Link Communications - allows structured textual communications between you and ATC. ⊻ |
atc-summary![]() |
Your airline may or may not have CPDLC.
Discussion of this is beyond the scope of this tutorial. ⊻ | |
ref-vnav![]() | 250KT CLB 1/3 CRZ ALT FL370 ECON SPD --- SPD TRANS TRANS ALT 250/10000 18000 SPD RESTR MAX ANGLE ---/----- ------------------------ <ECON ENG OUT> | |
ref-clb![]() | Before you get to cruise, pressing the VNAV
key will take you to the CLB page.
⊻ | |
ref-clb2![]() |
You can change the CRZ ALT field.
Changing this field will modify this page and require the EXEC key to be pressed. ⊻ | |
ref-clb3![]() |
The aircraft will, by default, climb at 250 knots until
10,000 feet.
You can change that here. ⊻ | |
ref-clb4![]() | The aviation database will set the
default transition altitude — TRANS ALT.
Altitudes at or above this will be displayed as flight levels. You can change this, as well. ⊻ | |
ref-clb5![]() |
The ECON SPD field is the speed the airplane will
fly once above the SPD TRANS altitude.
This field requires knots and Mach number. ⊻ | |
ref-clb6![]() |
ATC: “FMS 100, maintain 280 knots in the climb”
If you just enter 280, you're asking the airplane to climb at 280 knots all the way to your cruise altitude. This will exceed MMO at some point. ⊻ | |
ref-clb7![]() |
You: “FMS 100 unable to climb at 280 knots to 370.”
ATC: “Okay, FMS 100, maintain 280 knots and Mach .8 at the crossover” Type 280/.80 and press 2L to continue | |
ref-clb8![]() | MOD 250KT CLB 1/3 CRZ ALT FL370 SEL SPD 280/.800 SPD TRANS TRANS ALT 250/10000 18000 SPD RESTR MAX ANGLE ---/----- ------------------------ <ECON ENG OUT> <ERASE |
Like all other changes, this requires confirmation and the EXEC
key.
Note that the label has changed to SEL SPD and the <ECON prompt has appeared. Selecting <ECON will reset your speeds to FMS-computed economy climb speed. Let's erase these changes. Press 6L to continue |
ref-clb9![]() | 250KT CLB 1/3 CRZ ALT FL370 ECON SPD --- SPD TRANS TRANS ALT 250/10000 18000 SPD RESTR MAX ANGLE ---/----- ------------------------ <ECON ENG OUT> |
The CRZ - cruise - page is on the next page.
Press the NEXT PAGE key to continue |
ref-crz1![]() | ECON CRZ 2/3 CRZ ALT FL370 ECON SPD --- STEP OPT MAX ICAO ------------------------ <ECON <RTA PROGRESS LRC> | In cruise, pressing the VNAV key
will take you to the CRZ page.
⊻ |
ref-crz2![]() | You can change the CRZ ALT here, as well.
Like before, changing this field will modify this page and require the EXEC key to be pressed. ⊻ | |
ref-crz3![]() |
Just like the CLB page, the FMS will calculate an efficient
ECON speed.
Unlike the CLB page, you only need a single number here. Either knots or a Mach number will work. ⊻ | |
ref-crz4![]() |
ATC: “FMS 100, slow to Mach .78”
Type .78 and press 2L to continue | |
ref-crz5![]() | MOD M.780 CRZ 2/3 CRZ ALT FL370 SEL SPD .780 STEP OPT MAX ICAO ------------------------ <ECON <ERASE LRC> |
Changing the speed has made the <ECON prompt appear again.
ECON speeds use the cost index previously entered into the PERF INIT page. ⊻ |
ref-crz6![]() |
The LRC> (Long Range Cruise) prompt is similar, but
it changes your speed to the most fuel-efficient speed.
⊻ | |
ref-crz7![]() |
Erase these changes as well.
Press 6L to continue | |
ref-crz8![]() | ECON CRZ 2/3 CRZ ALT FL370 ECON SPD --- STEP OPT MAX ICAO ------------------------ <ECON <RTA PROGRESS LRC> |
The STEP field can be set in thousand-feet increments.
Valid values are 0, 1000, 2000, etc.
up to 9000.
Changing this will change your ETA. The FMS assumes you will make the step climbs at the appropriate times. DELETE the field to revert back to ICAO step-climbs. ⊻ |
ref-crz9![]() |
The <RTA PROGRESS goes to a Required Time of Arrival
progress page.
Use that page to change speeds to reach a waypoint at a specified time. ⊻ | |
ref-crz10![]() |
The DES - descent - page is on the last page.
Press the NEXT PAGE key to continue | |
ref-des1![]() | ECON DES 3/3 E/D AT AT BEANO 60 RW10 11000 ECON SPD --- SPD TRANS 240/10000 ------------------------ <ECON FORECAST> <OFFPATH DES | During descent, pressing the VNAV key
will take you to the DES page.
⊻ |
vnav-summary![]() | ||
ref-fix1![]() | FIX INFO 1/2 FIX BRG/DIS FR □□□□□ BRG/DIS ETA DTG ALT ABEAM <ABEAM PRED ETA-ALT <ERASE FIX ----- | The FIX key takes you to the FIX pages.
There's a lot you can do on these pages - consider them the multi-function calculator for navigation. ⊻ |
ref-fix2![]() | Scenario #1 - Abeam
ATC: “FMS 100, report abeam Zulu Quebec Alpha” Type ZQA and line select into the squares with 1L to continue. | |
ref-fix3![]() | FIX INFO 1/2 FIX BRG/DIS FR ZQA 293/161 BRG/DIS ETA DTG ALT ---/--- ---/--- ---/--- ABEAM <ABEAM PRED ETA-ALT <ERASE FIX ----- | The FIX page opens up!
In particular, the <ABEAM prompt is available. Press 5L to continue |
ref-fix4![]() | FIX INFO 1/2 FIX BRG/DIS FR ZQA 293/161 BRG/DIS ETA DTG ALT ---/--- ---/--- ---/--- ABEAM 205/17 0639z 373 FL320 PRED ETA-ALT <ERASE FIX ----- | Nice! We will be abeam ZQA on radial 205° from
the ZQA waypoint at a DME of 17 nautical miles.
⊻ |
ref-fix5![]() | We also know our ETA to this point and the DTG – Distance To Go
⊻ | |
ref-fix6![]() | The <ABEAM prompt has turned into
data.
We can pull that data down into the scratchpad, using 5L. Press 5L to continue | |
ref-fix7![]() | FIX INFO 1/2 FIX BRG/DIS FR ZQA 293/161 BRG/DIS ETA DTG ALT ---/--- ---/--- ---/--- ABEAM 205/17 0639z 373 FL320 PRED ETA-ALT <ERASE FIX ----- ZQA204.8/017.0 | This is in standard Point/Bearing/Distance (PBD) format.
We can actually insert this point into our flight plan, using the LEGS page. Press the LEGS key to continue |
ref-fix8![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> ZQA204.8/017.0 | Insert this new point after MEDLI and
before BITAC.
To do this, we need to place this new point over BITAC. BITAC is on the next page. Press the NEXT PAGE key to continue |
ref-fix9![]() | ACT RTE 1 LEGS 2/3 123° 62NM BITAC ---/------ 125° 406NM HAGIT ---/------ 136° 158NM CALTO ---/------ 136° 64NM ZIBER ---/------ 136° 23NM _____ ---/------ ------------------------ <RTE 2 LEGS RTE DATA> ZQA204.8/017.0 | Once you find BITAC, press the LSK next
to it.
This inserts the scratchpad waypoint in front of BITAC. Use the appropriate LSK on the left to continue |
ref-fix10![]() | MOD RTE 1 LEGS 2/3 122° 61NM ZQA01 ---/------ 123° 62NM BITAC ---/------ 125° 406NM HAGIT ---/------ 136° 158NM CALTO ---/------ 136° 64NM ZIBER ---/------ ------------------------ <ERASE RTE DATA> | With the abeam point on our flight plan,
it's easier to maintain situational awareness, and report
to ATC: “FMS 100 is abeam ZQA at this time.”
⊻ |
ref-fix11![]() | You can either cancel our changes (by selecting
the <ERASE prompt) or execute them.
Press 6L or EXEC to continue | |
ref-fix12![]() | ACT RTE 1 LEGS 2/3 123° 62NM BITAC ---/------ 125° 406NM HAGIT ---/------ 136° 158NM CALTO ---/------ 136° 64NM ZIBER ---/------ 136° 23NM _____ ---/------ ------------------------ <RTE 2 LEGS RTE DATA> | Let's go back to the FIX page.
Press the FIX key to continue |
ref-fix13![]() | FIX INFO 1/2 FIX BRG/DIS FR ZQA 293/161 BRG/DIS ETA DTG ALT ---/--- ---/--- ---/--- ABEAM 205/17 0639z 373 FL320 PRED ETA-ALT <ERASE FIX ----- | The FMS talks to your flight instruments,
so you would see ZQA show up on your EHSI,
if it was in range.
⊻ |
ref-fix14![]() | There are two FIX pages.
If you need information about two fixes, you can use the second page. Press NEXT PAGE to continue | |
ref-fix15![]() | FIX INFO 2/2 FIX BRG/DIS FR □□□□□ BRG/DIS ETA DTG ALT ABEAM <ABEAM PRED ETA-ALT <ERASE FIX ----- | The second FIX page is identical to the
first.
Press PREV PAGE to continue |
ref-fix16![]() | FIX INFO 1/2 FIX BRG/DIS FR ZQA 293/161 BRG/DIS ETA DTG ALT ---/--- ---/--- ---/--- ABEAM 205/17 0639z 373 FL320 PRED ETA-ALT <ERASE FIX ----- | The <ERASE FIX prompt clears
out the page.
Press 6L to continue |
ref-fix17![]() | FIX INFO 1/2 FIX BRG/DIS FR □□□□□ BRG/DIS ETA DTG ALT ABEAM 205/17 0639z 373 FL320 PRED ETA-ALT <ERASE FIX ----- | PRED ETA-ALT can accept an
altitude or a Zulu time.
⊻ |
ref-fix18![]() | Scenario #2 — Heating our crew meal
Throw your glazed salmon in the oven, and set the timer for 20 minutes. ⊻ | |
ref-fix19![]() | When you get back to your seat, you can put the Zulu time that your salmon is done in
PRED ETA-ALT.
Don't forget the trailing Z! If you forget, the FMS will interpret the 4 digit number as an altitude. Enter a zulu time (say 1435Z) and press 6R to continue | |
ref-fix20![]() | FIX INFO 1/2 FIX BRG/DIS FR □□□□□ BRG/DIS ETA DTG ALT ABEAM 205/17 0639z 373 FL320 PRED ETA-ALT <ERASE FIX 1435z | The point where you will be at that time
will be shown on your EHSI.
⊻ |
fix-summary![]() | Summary
Two FIX pages for navigation calculations based on named fixes. Abeam points can be calculated and added to your route legs. Times and altitudes can be shown on your EHSI. ⊻ | |
ref-legs1![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> | The LEGS key brings up the LEGS pages.
This is an expanded view of your flight plan, with one line per flyable segment. Changes here are reflected in the RTE pages, and changes to the RTE pages are reflected here. ⊻ |
ref-legs2![]() | Scenario #1: Direct To
ATC: “FMS 100, cleared direct KLADA” Find KLADA, then press the LSK next to it. You may need to use the PAGE keys to find the correct page | |
ref-legs2a![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> KLADA | FMS Pro Tip:
If you press the wrong LSK, you might “oops,” and quickly press the correct LSK.
This will overwrite the correct waypoint. ⊻ |
ref-legs2b![]() | A Line-Select Key sets an entry if there's something in the scratchpad,
and retrieves data if there isn't.
If you really get messed up, clear the scratchpad, select the <ERASE prompt and try again. Make sure the scratchpad says KLADA before continuing ⊻ | |
ref-legs3![]() | KLADA is in the scratchpad.
Now, we want the airplane to fly to KLADA. KLADA should be the first waypoint on the LEGS list. We can make it the first waypoint, by line selecting the first leg while KLADA in the scratchpad. Make sure we're on page 1 of the legs page! Check that you're on page 1, then press 1L to continue | |
ref-legs3a![]() | MOD RTE 1 LEGS 1/2 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ 123° 62NM BITAC ---/------ 125° 406NM--------- HAGIT ABEAM PTS> 136° 158NM CALTO RTE COPY> ------------ INTC CRS TO <ERASE 11#°> |
Note the DSPY light.
This lights up when there's an active leg, and you're not looking at it. Specifically, it will illuminate on the following pages:
⊻ |
ref-legs3c![]() | If you do put the fix at the top of the wrong page, it is easy to mend.
⊻ | |
ref-legs3b![]() | FMS Pro Tip:
“Direct to” is a pretty common clearance, and the fix we're cleared to is usually
on the first page of the LEGS page.
But if you're not on page 1, 1L isn't the first leg. Avoid building the bad habit of finding and selecting the fix, then quickly pressing 1L without checking the page number. You must be on page 1. ⊻ | |
ref-legs5![]() | The MOD in the title tells us the active route
is being modified.
Also note the ABEAM PTS> prompt. This creates points abeam of each skipped fix. ⊻ | |
ref-legs6![]() | Like other changes we've made,
we can erase these changes (by selecting the <ERASE prompt),
or we can confirm and execute with the EXEC key.
Let's erase these changes. Select the <ERASE prompt to continue | |
ref-legs7![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> | Scenario #2: After xxx, cleared DIRECT yyy
ATC: “FMS 100, after KLADA, cleared direct CALTO” Find CALTO, and press the LSK next to it to continue |
ref-legs8![]() | ACT RTE 1 LEGS 2/3 123° 62NM BITAC ---/------ 125° 406NM HAGIT ---/------ 136° 158NM CALTO ---/------ 136° 64NM ZIBER ---/------ 136° 23NM _____ ---/------ ------------------------ <RTE 2 LEGS RTE DATA> CALTO | Move it below KLADA.
Remember, the <ERASE prompt resets all your changes. Use it if you get tangled up. Find the line below KLADA, and press the LSK next to it to continue |
ref-legs9![]() | MOD RTE 1 LEGS 1/2 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 124° 69#NM CALTO ---/------ ------------------------ <ERASE RTE DATA> | This looks good. CALTO follows KLADA, just like the clearance said.
Again, erase these changes. Select the <ERASE prompt to continue |
ref-legs10![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> | Scenario #3: Point-Bearing-Distance
ATC: “FMS 100, cleared direct ZQA 190 radial, 20 DME” ⊻ |
ref-legs10a![]() | This is entered in the same order ATC says it: PBD – Point, Bearing, Distance.
A single slash separates the numbers.
Type ZQA190/20 and press 1L to continue | |
ref-legs11![]() | MOD RTE 1 LEGS 1/3 ZQA01 ---/------ THEN □□□□□ -- ROUTE DISCONTINUITY - (INTC) ---/------ 111° 7NM--------- JAMBA ABEAM PTS> 126° 4NM KBOLA RTE COPY> ------------ INTC CRS TO <ERASE □□□ | The FMS shoe-horns the full ZQA190/20 into
a 5 letter waypoint by taking the first three letters, and adding a two-digit number to it.
The first waypoint you add like this will have 01 at the end, the next will have 02, then 03, etc. ⊻ |
ref-legs12![]() | Note the ROUTE DISCONTINUITY.
When the FMS doesn't know what to do AFTER a point you add, it puts a ROUTE DISCONTINUITY. In this case, the airplane will fly to ZQA 190° radial, 20 DME, and then keep going on the same track. You'll need to edit the legs by placing a known fix over the empty route discontinuity. Erase this change as well. Select the <ERASE prompt to continue | |
ref-legs13![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> | Other acceptable entries:
⊻ |
ref-legs14![]() | The RTE DATA> prompt allows us to add
weather data — in particular, this is where we can give the
FMS our wind forecasts.
Select the RTE DATA> prompt to continue | |
ref-legs15![]() | ACT RTE 1 DATA 1/3 ETA WPT FUEL WIND (INTC) > JAMBA > KBOLA > KLADA > MEDLI > ---------------- REQUEST <LEGS SEND> | The RTE DATA page has one line
for each leg — just like the LEGS pages.
We don't have to add wind data for every point. Pick a leg and select the right LSK next to it. Press 1R .. 5R to continue |
ref-legs16![]() | ACT KBOLA WIND 3/11 ALT OAT DIR/SPD ----- °/ KT °/ KT °/ KT ALT/OAT -----/---°C ------------------------ RTE DATA> | This leads to a WIND page.
There is one WIND page for each leg.
You can tell the FMS the winds at several altitudes. Our planned altitude is Flight Level 370. Type 370 and press 1L to continue |
ref-legs17![]() | MOD KBOLA WIND 3/11 ALT OAT DIR/SPD ----- °/ KT °/ KT FL370 ---°/---KT ALT/OAT -----/---°C ------------------------ <ERASE RTE DATA> | Now we can tell the FMS the wind speed and direction
at this altitude.
The wind forecast says 280@15. Type 280/15 and press 4R to continue |
ref-legs18![]() | MOD KBOLA WIND 3/11 ALT OAT DIR/SPD ----- °/ KT °/ KT FL370 280°/ 15KT ALT/OAT -----/---°C ------------------------ <ERASE RTE DATA> | There is one WIND page per leg.
Press NEXT PAGE to continue |
ref-legs19![]() | MOD KLADA WIND 4/11 ALT OAT DIR/SPD ----- °/ KT °/ KT FL370 280°/ 15KT ALT/OAT -----/---°C ------------------------ <ERASE RTE DATA> | Note the same winds are shown in small lettering.
The winds at this leg are set to the previous leg's wind. If this is acceptable, just move to the next leg. Press NEXT PAGE to continue |
ref-legs20![]() | MOD MEDLI WIND 5/11 ALT OAT DIR/SPD ----- °/ KT °/ KT FL370 280°/ 15KT ALT/OAT -----/---°C ------------------------ <ERASE RTE DATA> | The wind forecast says 300@20.
Type 300/20 and press 4R to continue |
ref-legs21![]() | MOD MEDLI WIND 5/11 ALT OAT DIR/SPD ----- °/ KT °/ KT FL370 300°/ 20KT ALT/OAT -----/---°C ------------------------ <ERASE RTE DATA> | The updated winds are shown in larger, normal lettering.
Since we're changing the potential flight path of the airplane, the EXEC light is lit. These changes require confirmation. Press the EXEC key to continue |
legs-summary![]() | Summary
The LEGS page shows the individual steps that the airplane will fly. You can fly “DIRECT waypoint” by entering the waypoint into the first leg. You can fly “AFTER waypoint1 DIRECT waypoint2” by putting waypoint2 in the scratchpad and line selecting the waypoint after waypoint1. ⊻ | |
legs-summary2![]() | Summary (cont'd)
Point/Bearing/Distance is in the same order as given: for example HNL160/10 is the 160° radial off of HNL, 10 DME. Intersecting radials are in the format PTAxxx/PTBxxx. For example, HNL110/CKH240 The RTE DATA> prompt lets you enter wind forecasts per leg. ⊻ | |
ref-hold1![]() | ACT RTE 1 LEGS 1/3 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ --------HOLD AT--------- □□□□□ PPOS> | The HOLD key defines
a holding pattern.
Rule #1 about holds — if there isn't a hold already in your flight plan, the HOLD key brings up the LEGS page. ⊻ |
ref-hold1a![]() | Let's quickly add a hold into our flight plan, by loading an instrument approach.
Press the DEP ARR key to continue | |
ref-hold1b![]() | KMIA DEPARTURES 1/3 SIDS RTE 1 RUNWAYS ALTNN1 08L TRANS BNGOS3 08R DORRL1 <ACT> 09 FLMGO1 12 FOLZZ2 26L ------------------------ <INDEX ROUTE> | We have an active route. The DEP ARR key
takes us to the DEPARTURES page.
We want an arrival, so select the <INDEX prompt to get to the DEP/ARR INDEX page. Press 6L to continue |
ref-hold2![]() | DEP/ARR INDEX RTE 1 (ACT) <DEP KMIA ARR> TJSJ ARR> --------RTE 2 ---------- <DEP ARR> ARR> ------------------------ DEP OTHER ARR <---- ----> | Instrument approaches always end in a hold.
Press the 2R key to continue |
ref-hold3![]() | TJSJ ARRIVALS 1/3 STARS RTE 1APPROACHES BEANO3 ILS 08 CHAKA4 ILS 10 JOSHE3 RNV 08 SAALR2 RNV 10 TROCO3 RNV 26 ------------------------ <INDEX ROUTE> | Choose any approach. Perhaps the ILS to runway 8?
Any approach, any transition is good. Select an approach (one of 1R .. 5R) to continue |
ref-hold3a![]() | TJSJ ARRIVALS 1/1 STARS RTE 1APPROACHES BEANO3 <SEL> ILS 08 TRANS CHAKA4 DDP JOSHE3 SJU SAALR2 VARNA TROCO3 ------------------------ <ERASE ROUTE> | Say “verify?” and wait for your co-pilot to say “execute”
before pressing the EXEC key.
Press the EXEC key to continue |
ref-hold4![]() | TJSJ ARRIVALS 1/3 STARS RTE 1APPROACHES BEANO3 <ACT> ILS 08 CHAKA4 ILS 10 JOSHE3 RNV 08 SAALR2 RNV 10 TROCO3 RNV 26 ------------------------ <INDEX ROUTE> | Now, press the HOLD key.
Press the HOLD key to continue |
ref-hold5![]() | ACT RTE 1 HOLD 1/1 FIX SPD/TGT ALT DEEDY ---/------ QUAD/RADIAL FIX ETA --/--- INBD CRS/DIR EFC TIME 184°/R TURN ----Z LEG TIME HOLD AVAIL 1.0MIN LEG DIST BEST SPEED --.-NM ------------------------ <NEXT HOLD |
You are looking at the hold defined by the missed approach procedure
at the end of the instrument approach you just loaded.
⊻ |
ref-hold5a![]() | Rule #2 about holds — if there is a hold already in your flight plan, the HOLD key shows that hold.
If there is more than one hold, the HOLD key brings up the first. ⊻ | |
ref-hold6![]() | To create a new hold, we need to go back to
the hold LEGS page.
This is what the <NEXT HOLD prompt does. Press 6L to continue | |
ref-hold7![]() | ACT RTE 1 LEGS 1/# 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ --------HOLD AT--------- □□□□□ PPOS> | The FMS assumes that you are being asked to hold on
a point in your flight plan.
But what if the point has already passed? Or ATC clears you to hold at some waypoint that's not on your flight plan? ⊻ |
ref-hold8![]() | ATC: “Ah, FMS 100, I need you to hold EAST over
ZQA, 090 radial”
First, the fix. Enter ZQA into the HOLD AT entry. | |
ref-hold9![]() | ACT RTE 1 LEGS 1/# 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ □□□□□ PPOS> HOLD AT ZQA | The message HOLD AT ZQA is the FMS
asking us a question.
Where do we want to put this hold? Before we fly to KBOLA? KLADA? ⊻ |
ref-hold10![]() | Rule #3 about holds — holds that aren't waypoints in our flight plan still need to be inserted into our flight plan.
Press the LSK at the waypoint the hold will be inserted in front of. Press any LSK 2L .. 5L to continue | |
ref-hold11![]() | MOD RTE 1 HOLD 1/2 FIX SPD/TGT ALT ZQA ---/------ QUAD/RADIAL FIX ETA --/--- INBD CRS/DIR EFC TIME 112°/R TURN ----Z LEG TIME HOLD AVAIL 1.5MIN LEG DIST BEST SPEED --.-NM ------------------------ <ERASE | ATC asked us to hold EAST on the 090 radial.
Type 090 and enter it into 2L |
ref-hold12![]() | MOD RTE 1 HOLD 1/2 FIX SPD/TGT ALT ZQA ---/------ QUAD/RADIAL FIX ETA E /090° INBD CRS/DIR EFC TIME 270°/R TURN ----Z LEG TIME HOLD AVAIL 1.5MIN LEG DIST BEST SPEED --.-NM ------------------------ <ERASE | Notice that the QUAD changes to E,
allowing us to verify that we are, indeed, holding EAST.
⊻ |
ref-hold12a![]() | Notice also that the INBD CRS
inbound course changes to the reciprocal of the RADIAL.
You can change the radial, and the FMS will update the INBD CRS. If you change the inbound course the QUAD/RADIAL fields will be blanked. ⊻ | |
ref-hold12b![]() | Changing the LEG TIME will
clear the LEG DIST and vice versa.
⊻ | |
ref-hold13![]() | Why are there two pages?
Each hold in the flight plan has a page for its definition. Remember, there's a hold at the end of our instrument approach. ⊻ | |
ref-hold14![]() | Right turns are assumed.
If ATC had asked for left turns, just type L and LSK 3L. ⊻ | |
ref-hold15![]() | We are changing the flight path of the airplane.
This requires confirmation. The exec light is lit.
Before we do anything, let's see what a hold looks like on the LEGS page. Press the LEGS key to continue | |
ref-hold16![]() | MOD RTE 1 LEGS 1/5 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ ZQA ---/------ HOLD AT ZQA ------------------------ <ERASE RTE DATA> | Look for ZQA, then the HOLD AT after it.
⊻ |
ref-hold17![]() | The <ERASE prompt will remove
the hold, by canceling all unconfirmed changes.
Either erase our changes, or execute the changes to continue | |
hold-summary![]() | ACT RTE 1 LEGS 1/# 092°HDG (INTC) ---/------ 111° 7NM JAMBA ---/------ 126° 4NM KBOLA ---/------ 11#° 2#NM KLADA ---/------ 12#° 66NM MEDLI ---/------ ------------------------ <RTE 2 LEGS RTE DATA> | Summary
Rule #1 — if there isn't a hold already in your flight plan, the HOLD key brings up the LEGS page. Rule #2 — if there is a hold already in your flight plan, the HOLD key shows that hold. Rule #3 — holds that aren't waypoints in our flight plan still need to be inserted into our flight plan. ⊻ |
ref-fmc-comm1![]() | FMC COMM <RTE 1 POS REPORT> <ALTN <PERF <TAKEOFF DATA LINK <DES FORECAST READY |
The FMC COMM key takes you to the FMC COMM page.
Flight Management Computer - Communications: if this feature is installed, it allows the FMS two-way communications with your airline's operations via ACARS. ⊻ |
ref-fmc-comm2![]() | You may have noticed that some
pages have <SEND prompts.
The RTE page has them, for example. Press the RTE key, or select the <RTE 1 prompt to continue | |
ref-fmc-comm3![]() | ACT RTE 1 1/2 ORIGIN DEST KMIA TJSJ RUNWAY FLT NO RW09 ---------- REQUEST CO ROUTE <SEND ---------- REPORT <SEND RTE COPY> ------------------------ ALTN> <RTE 2 TAKEOFF> | There they are!
Press the FMC COMM key to continue |
ref-fmc-comm4![]() | FMC COMM <RTE 1 POS REPORT> <ALTN <PERF <TAKEOFF DATA LINK <DES FORECAST READY |
Another way to get to this page is through
the INIT/REF INDEX page and selecting the
FMC COMM> prompt.
⊻ |
fmccomm-summary![]() | Summary
The FMC COMM key (and the FMC COMM> prompt on the INIT/REF INDEX page) is a quick link to all pages that have a SEND function. ⊻ | |
ref-prog1![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 DEST TJSJ 8## ECON SPD .787 -------------- GPS <POS REPORT POS REF> | The PROG key takes you to
the PROGRESS pages.
It shows the Distance-To-Go (DTG) to the:
⊻ |
ref-prog2![]() | Scenario #1 — waypoints on our route
We can get estimates to other points besides our destination. ⊻ | |
ref-prog2a![]() | ATC: “FMS 100, say estimate to CALTO”
Type CALTO and press 3L to continue | |
ref-prog3![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 EN ROUTE WPT CALTO 72# ECON SPD .787 -------------- GPS <POS REPORT POS REF> | The label changes to EN ROUTE WPT.
This distance is measured along each leg in our route. ⊻ |
ref-prog4![]() | Scenario #2 — planning a diversion
How far is an unplanned alternate? Let's use Florida Regional International Airport (KRSW). Type KRSW and press 3L to continue | |
ref-prog5![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 DIR TO FIX KRSW 90 ECON SPD .787 -------------- GPS <POS REPORT POS REF> | The label changes to DIR TO FIX.
This distance is measured direct from present position. ⊻ |
ref-prog6![]() | Any fix or destination we enter into this field
will be reset if we move to another page.
We can also use the DEL key. This will also reset this field to the original DEST estimate. Press the DEL key to continue | |
ref-prog7![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 DIR TO FIX KRSW 90 ECON SPD .787 -------------- GPS <POS REPORT POS REF> DELETE | The DELETE message is displayed in the scratchpad. This is an instruction to the FMS to delete the data next to whatever LSK we press.
Press 3L to continue |
ref-prog8![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 DEST TJSJ 8## ECON SPD .787 -------------- GPS <POS REPORT POS REF> | Our original destination and estimates are displayed.
⊻ |
ref-prog9![]() | There are more pages to explore.
Press NEXT PAGE to continue | |
ref-prog10![]() | PROGRESS 2/3 H/WIND WIND X/WIND XTK ERROR VTK ERROR TAS SAT +26°C LEFT FUEL USED RIGHT 0.0 TOT 0.0 0.0 FUEL QTY TOTALIZER CALCULATED 63.6 63.6 | The PROGRESS page 2 gives us
flight conditions.
Wind, temperature, and fuel quantity is displayed. When in the air, XTK ERROR (Cross-Track Error) shows us how far we are from our expected route center-line. Press NEXT PAGE to continue |
ref-prog11![]() | RTA PROGRESS 3/3 FIX RTA □□□□□ □□□□.□z□ RTA SPD ALT/ETA T/O ----.-Z MAX SPD .840 ------------------------ | PROGRESS page 3 can calculate a Required Time to Arrival (RTA).
Press NEXT PAGE to continue |
ref-prog12![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 DEST TJSJ 8## ECON SPD .787 -------------- GPS <POS REPORT POS REF> | We're back to PROGRESS page 1.
There are some handy links at the bottom of this page. The <POS REPORT prompt gives us a position report. Press 6L to continue |
ref-prog13![]() | POS REPORT POS ATA ALT BITAC 0858z FL350 EST ETA HAGIT 0944z NEXT DEST ETA CALTO 1142z TEMP WIND SPD -47°c 279°/ 67KT .79 POS FUEL 54.8 COMPANY ----------- ATC <SEND NO ATC COMM | The POS REPORT page gives you
all the information for a standard ATC position report.
You to ATC: “FMS 100 at BITAC 0848 zulu at flight level 350, estimating HAGIT 0944 zulu, next CALTO.” ⊻ |
ref-prog13a![]() | Let's get back to the PROGRESS pages.
Press the PROG key to continue | |
ref-prog14![]() | PROGRESS 1/3 TO DTG ETA FUEL (INTC) NEXT JAMBA 7 DEST TJSJ 8## ECON SPD .787 -------------- GPS <POS REPORT POS REF> | The POS REF> prompt gets us to the
POS REF pages.
Press 6R to continue |
ref-prog15![]() | POS REF 2/4 FMC (GPS) UPDATE N25°47.4 W080°18.0 ARM> IRS(3) ACTUAL 0.26NM N25°47.4 W080°18.0 GPS ACTUAL 0.01NM N25°47.4 W080°18.0 RADIO ACTUAL NM RNP/ACTUAL 1.00/0.01NM ------------------------ <INDEX BRG/DIST> | These are the same pages we saw in the preflight.
Scenario: receiving an ELT You to ATC: “Center, FMS 100 is picking up an ELT” ATC: “Roger, report position where the signal is strongest” You can quickly record your location at a point by line-selecting 1L. Try it now. Press 1L to continue |
ref-prog16![]() | POS REF 2/4 FMC (GPS) UPDATE N25°47.4 W080°18.0 ARM> IRS(3) ACTUAL 0.26NM N25°47.4 W080°18.0 GPS ACTUAL 0.01NM N25°47.4 W080°18.0 RADIO ACTUAL NM RNP/ACTUAL 1.00/0.01NM ------------------------ <INDEX BRG/DIST> N2547.4W08018.0 | The lat/lon appears in the scratchpad. Your GPS location will be updated in 1L, but the scratchpad saves your location.
A tip: pressing and holding the CLR key for 2 seconds clears the entire scratchpad. Press and hold the CLR key to continue |
prog-summary![]() | POS REF 2/4 FMC (GPS) UPDATE N25°47.4 W080°18.0 ARM> IRS(3) ACTUAL 0.26NM N25°47.4 W080°18.0 GPS ACTUAL 0.01NM N25°47.4 W080°18.0 RADIO ACTUAL NM RNP/ACTUAL 1.00/0.01NM ------------------------ <INDEX BRG/DIST> | Summary
The PROG key brings up the PROGRESS pages. Distances and, in flight, estimates to the next waypoint, the waypoint after that, and our destination are displayed. We can get estimates to various fixes by entering data into DEST. Other pages give us flight conditions, or RTA (Required Time of Arrival). ⊻ |
ref-menu1![]() | MENU
<FMC <ACT>
<ACARS TUTORIAL>
<SAT-I
<DFDAU
| |
ref-menu2![]() | ||
ref-menu3![]() | ACARS-APPLICATION MENU AOC STD> ATS> TECHNICAL> HH:MM | |
menu-summary![]() | ||
ref-navrad1![]() | NAV RADIO VOR L VOR R 113.90ADHP VKZP117.10 RADIAL 107 290 PRESELECT ------ ------ | |
ref-navrad2![]() | ||
ref-navrad3![]() | ||
ref-navrad4![]() | ||
ref-navrad5![]() | ||
ref-navrad6![]() | NAV RADIO VOR L VOR R 114.40RFLL VKZP117.10 RADIAL 209 290 PRESELECT ------ ------ | |
ref-navrad7![]() | ||
ref-navrad8![]() | NAV RADIO VOR L VOR R 114.40RFLL VKZP117.10 RADIAL 209 290 PRESELECT ------ ------ DELETE | |
ref-navrad9![]() | NAV RADIO VOR L VOR R 113.90ADHP VKZP117.10 RADIAL 107 290 PRESELECT ------ ------ | |
navrad-summary![]() |