XFMC Tutorial

For release RC3

Installation of the files:

Just copy the XFMC and subdirs to pluginsfolder of Xplane.

Copy the XFMC_xxx.xpl to the plugins folder of Xplane

Copy the Fmodex.dll i (sound file) to plugins folder of Xplane. (so not in XFMC dir, just in the plugins
dir)

That’s all!

NOT included are the SID/STARS files. They can be downloaded at vasFMC projectfile on xplane.org

The VasFMC SIDS files must be located in the subdir SID of XFMC

The vasFMC STARfiles must be located in the subdir STAR of XFMC

Not included -but needed- is the pssawy.dat file from Navigraph. You have to buy this file or find it
somewhere. The pssawy must be installed in the XFMC dir.

Also not included are psswpt.dat (since RC2) psswpt.dat is needed for the NAT, The North Atlantic
Routes. This file should also be located in the root of XFMC dir.

Since RC2, the x737 of Benedikt Strattman is supported. See for guidance of setup the separate
document.

Keyboard:

The keyboard can be hooked up. Normally is’t always on, the extra button indication Yellow for
connected, and White for disconnected.

To get the keyboard in focus, just click somewhere on the XFMC screen. To release the keyboard
press ENTER.

Fire up Xplane.
You will hear “tada” sound if the plug-in and sound drivers are installed. If not, lookup in the root of
Xplane the file Log.txt and see what’s the problem. Somewhere in the lines you should read why
Xplane is not loading the XFMC.xpl or sound drivers.

In this Tutorial we go to make a flight from LMML to LOWL (leg 40 of IVAO tour 2010)

When we look up the route we gone to fly in Route Planner we get:

LMML SID LORED UM600 ERNAM UL58 PIMOR UL62 CDC UQ865 XOLTA UM725 ZAG UL604
LNZ STAR LOWL

Put your plane on the parking place of LMML. For the Tutorial I’m using the B737 which a config file
has been included. The B737 should be inserted in your Aircrafts dir + the configfile which was
included.

XFMC should look like this picture. Any time you can set XFCM out of
focus by F9. If this key isn’t working, then another key of a plug-in is holding this key. Lookup in the
pluginmanager and correct this.

Click on LSK1 “FMC”

Then we get the next IDENT screen:

Only information, nothing to change. Click on RSK6, POS INIT.

Then we got the Position page.

Type in the command line (key map of the XFMC or your PC keyboard) the Departure Airport LMML
and click on LSK2 ( REF AIRPORT). Next click on ROUTE.

We got the RTE1 page. Type in your keyboard the destination airport LOWL and click on RSK1. After

that Click on RSK6 ACTIVATE.

The light on the EXEC button will be lit, and you have to confirm it by clicking on it. Also you hear an
alerting sound. After you activated this screen, the altitudes of both airports are visible. and the
ACTIVATE key has changed to RTE1. You have to wait 1-2 seconds before you will see any reaction.
This is because the large data file of airports will be scanned.

Click on RTE1, and we get the Route page. The legs are already filled in to speed up the tutorial. You
have to do it, by inserted a waypoint on the right side, and an airway on the left side. Follow the
examples and all will be ok. Step through the pages with pageUp and PageDown.
If all done well click on the LEGS key and your legslist will be looked like:

First waypoint to go is LORED. If you wonder why the color of UPLAD is different: this waypoint was
not in the Xplane database and inserted in XFMC from the PSS Airway database.

Next we have to choose which runway we have to take + the SID if available.

You can query IVAO with the .metar command (if online), but easier: have a look at the departure
page)

To access: click on INIT and the choose LSK5 Take OFF

ON LSK4 we see the wind direction and force 140/ 13 knots

Back to the departure: Click on DEP/ARR key

You will get the DEP/ARR INDEX (wait 1-2 seconds!). Click on DEPT LSK1

Now we know are winddir, we can choose the runway: 13. Then you get on the left side the SIDS for
runway 13. I already did this to make a screenshot. You see the selected runway and SID marked by
an asterisk (*). Any time when you change your mind, you can go back, by clicking on RWY LSK6. And
select a new runway/and/or SID. The old SID should have been removed, but better is to check it
after this. Our legalist should be looking like this picture:

You see that more points have been inserted. D133B D162D. They are in different color, not because
these points are the SIDS, but because xplane’s database doesn’t contain these points.

Ready to go to the performance page.

Click on the PERF key on the FMC, and you will get this screen:

I already filled in what you have to fill in.

Starting with your flight level. I choose FL310, but you can select your own. Format 310 or 31000 in
RSK 1

Then our fuel, very important to avoid an emergency landing.

Put in LSK4 your reserves IN TONS, in this example 6 TON.

Then adjust in xplane aircraft-> Weight/Fuel your fuel, so you got a little positive fuel, in this
example 3839 (NO TONS). After that click on LSK1 GRWTADV

To finish this page, fill in 100 in LSK5 and then click on RSK6, thrust limit

After that we got the thrustlimitpage

You can play later on with this. On the left you see the takeoff limits, on the right the INITCLIMB
limits. - In fact the way it works it is not a limit, but a controlling the N1%.

By changing the speed and +v/s XFMC tries to get close to the N1% selected.

Last step for takeoff: the Take-Off page: click on TAKEOFF

I already filled in the page, but you have to select your flap setting. In blue the angles of the detents
possible. Your are the captain, it up to you what flap setting you will take!

I selected 5, because we are not fully loaded. Fill in your keyboard 5 (or 15 or 1) and click on LSK1

Then activate the SpeedRefs by clicking on RSK1, RSK2,RSK3 If you did all well, the preflight
completed is lit.

Don’t forget to set your flaps according what you have inserted. There is NO warning alert by mis-
setting the flaps!

Last final check: we go back to the legs page

This is how your picture should look like:

You see that XFCM has filled in the speeds and altitudes for you. Up to you, as pilot if you can agree
with this. Suppose we have ATC, and he commands us to level off at D162D at 2000 and no more
speed than 240 knots. Fill in the command line 240/2000 and click on RSK2 (waypoint D162D). After
that you have to confirm it by clicking on the EXE key.
You see that the color has changed:

Waypoint D162D will not be changed from now on by XFMC and the speed will be maintained o 240
knots. After D162D the ATC directs us to another waypoint DIRKA: but no more restrictions. Type in
the command buffer DIRKA, and click on TC. The EXE will be lit, and so you have to confirm the
insertion by clicking on the EXE key.

Now our leglist shows like this picture:

You see that XFMC recalculated the TD, inserted DIRKA, but didn’t change D162D

Our T/D is aprox 65 nm from takeoff. The same way you can delete waypoints, for example to delete
DIRKA, click on the DEL key , click then on LSK3 (DIRKA), after that confirm it by EXE.

We are finished the setup. Switch on your taxi lights, No Smoking, Seatbelts, Strobe etc etc

Ready to go? Taxi to the h/p, don’t forget to set the transponder to C, and line up the runway.
Click on the A/C button. You will get this picture:

If ok, ATR, AP on and Lineup should be yellow. You hear the voice saying” Flight Director”

DO NOT Activate other panel buttons. Leave NAV1 switch on NAV1 (never on FMC!!!) Do NOT
activate the A/P or Headline. This will be done for you by XFMC in the right order!

NOTE on some older Xplane’s aircraft this flightdir setting might not working. In this case check
yourself the flightdir is on AUTO

The FD is set now, don’t touch it! Also the RTO is set (you can disable this in the Config)

Also you may notice that the Brakes are set: leave it so!

Set your throttle MANUALLY to 85% N1.

The moment the engine thrust passes 80% N1%, you will hear “maximum thrust set”, and XFMC
changes to:

That moment the brakes are release and the plane starts to accelerate/rolling on the runway.

ONLY thing you got to do is stay in center of the runway by means of you pedals.

At around 80 knots you will hear “80 knots.” As a good pilot you have to check both indicators are
displaying 80 knots. But we are on a simulator, so you can trust it; we passed the 80 knots…..

Next reaching V1, you will hear “ V1”

Then at Vr, you will hear “Rotate”. Don’t pull you commands, you may observe that during the
acceleration the v/s was -1000, but at rotate you see +4400 v/s, thus the plane will take off
automatically (if you v1/v2/vr speeds are correct ). You see now pull-up in XFMC.

Next you will hear V2. Let the plane climb, only with your pedals you have to keep the path in line of
the runway (side wind…) Note: if the V1/VR/V2 speeds are incorrect the plane’s take-off will take
longer, more speed is needed . In that case you can “help” by pulling the yoke a little bit.
The moment you hear positive Rate Xplane A/P will be switched on, and you can release you
throttle. Airborne!.

The display must look like this:

XFMC is now showing INITCLIMB, the thrust limit Takeoff is now active. You see the v/s showing
2600 feet/min, BUT this will be recalculated to obtain the right v/s versus thrust limit. It is possible
that you will see the v/s stepping downwards during this INITCLIMB. The Initcllimb will be continued
by a following CLIMB, around 1500 AGL (the value inserted in the takeoff page, standard 1500 AGL).

During this INITCLIMB the gear will be retracted.(can be disabled in the config)

Passing this 1500 AGL level you hear a special sound. Now the ClimbTrustlimit will become active,
the v/s is lowering around 2200 f/m and the plane starts to accelerate. Also passing the 1500 AGL,
the flaps will be retracted step by step. (Can be disabled in the config).

The climb v/s will be adapted during the climb to obtain the best climb versus the thrustlimit/load
etc.

Let the plane climb to the final cruise level. In case it reaches a certain Flight level, you will hear a
short “Ping” as sign that the climb as stopped and will be continued later on next waypoint

=========================================================================
In the VNAV page CLB you can alter different data. To Access this page click on the VNAV key

Here you can:

1- Adjust the Climb speed

2- Set the Speed/Transition level
3- Set a 2nd speed/altitude restriction
4- Set the Transition Altitude
5- Disable the v/s from XFMC to manual settings (also the altitude) In that case you will see
(MAN) behind the actual cruise phase.Text Yellow: VNAV controlled by XFMC, text white:
VNAV controlled by operator

As long the plane is in the first Climb phase up to the Cruise, this page will be actual, but can
access the other 2 pages by the Page up Page Down keys.

In RSK1 you see the TOC calculated

In RSK2 the v/s calculated the moment this screenshot was taken.

1- RSK3 Transition Altitude .The altitude where the barometer is set to 1013 Hpa or 29.92
Mercury)

RSK4 Max Climb Angle ( not implemented)

==================================================================================

Next following the climb is the Cruise Phase. Up to our approach of LOWL, we can change our
cruisesspeed and cruise level.

To set a new Cruise level, go to LSK1, and enter a new altitude in the command line.

To set a new speed: enter a speed in Mach above 30000 or in KNOTS below 30000, and click on LSK2.

Note: in the cruise the thrust limit is also active. It is good possible that if you set the cruise speed
too high, the speed will not be accepted and reduced. In this example, the speed has been set to
0.82, but however, on this altitude and Weight XFMC has calculated 0.80 as best speed.
In RSK3 you see the ETA of LOWL/ and the fuel remaining at LOWL.

It’s also possible to change to Cruise Altitude by means of setting the MCP altitude rotator on your
panel and after that clicking on MCP in the upper right corner of the XFMC.

===============================================================

Progress Page

Here we see some actual data during the flight.

In LSK1 the last passed waypoint

In LSK2 the next waypoint + distance to go + the ETA of arrival, calculated on the actual groundspeed
+ fuel remaining at the waypoint

In LSK3 the following after that + distance to go + the ETA of arrival, calculated on the actual
groundspeed + fuel remaining at that waypoint

In LSK4 the distance to go up to LOWL, ETA, Fuel remaining

LSK5 the actual MCP cruise speed setting, not the by XFMC actual used cruise speed.
Next page in the Progress is some data of the flight

LSK1 head or Tail wind, in knots

RSK1 side wind in knots, Left or Right

LSK2 path offset in nm.

RSK2 vertical path offset in feet

LSK3 True airspeed

RSK3 Static air temperature

LSK4 fuel flow in lbs/minute left engine(s)

RSK4 fuel flow in lbs/minute right engine(s)

LSK5 Remaining fuel in TONS

RSK5 Not implemented

==============================================================

Side Wind during cruise

XFMC calculates the offset of the desired path and steers the headline to compensate the wind drift.

This is a slowly process, but passing every waypoint the plane is back on his track.

Sometime you will see a little wiggling when the plane comes close (1-2 nm) to the waypoint,
because he is steering to that point and recalculating the best headline setting.

===================================================================
As said, in the Progress page nr 2, you can see the offset lateral track in LSK2

Inserting a Waypoint Along Track

Type in the command line the fix and slash speed example, you want a waypoint along track
15 nm past LORET. Type in LORET/15 and click on LORET. The new waypoint along track will
be placed after LORET, and carry the name LORET-ATWP.

To place a waypoint before LORET, just type in LORET/-15 (as example).

Inserting a Waypoint Latitude Longitude

The format is in decimal degrees: XX.XXXXNXX.XXXXE or XX.XXXXSXX,XXXXW

Short notice is also allowed XXNXXE

In the legslist the lat/long will be showed as entered, in blue color

Inserting a Waypoint with Bearing and Distance.

The format is in following way: xxxxxBBB/DD. Where xxxx is the fix (VOR, waypoint) from
where a radial in degrees is taken to a distance DD on that radial.

Example of input SPY090/10 will give a point on a radial of 90 degrees from SPY and 10 nm
from SPY.

PUY109/41 will give a point on a radial of 109 degrees from PY and 41 nm distance of PUY

Max range is 200 nm from a point.

Example: here 2 points are inserted 1 before TMS, one after TMS. It will be displayed as
waypoint ”BDWP”

Approach

We coming near to the descent, and in this case, the wind is 100.

So to open the STARS go to the DEP/ARR and click on the LOWL arrival (RSK2)
Next we see the runway ILS 09 available, close to our winddir 100. There are no STARS, you will get a
message NO starfile found.

To obtain a smooth alignment of the ILS, we can use the API points

Select runway 09 and after that go MENU and then Approach

In LSK3 you see Vector plots, and the runway heading of 09 is exactly 086.5 degrees.

Click on LSK3, and confirm it with the EXEC key

Our runway length is 2986 meters, long enough for this B737.

Then go to the Legspage (LEG key) and see what happens:

You see 3 API points added, the last one API-1 exactly in line of the runway, and 12 nm distance of
the runway. Also XFMC calculated the altitudes.

Note: XFMC doesn’t know the terrain details. It might be possible that one of the API points is too
low to achieve (mountains etc). In this example, as you will do this flight, you will see that API-3 at
7000 AGL is quite correct, we pass the mountains high enough without danger

You are the pilot, and you have to check the flight levels. In case it is not correct, you always can
change the altitudes by inserting speed/altitude in command line

Descent after passing T/D Click again on VNAV and you will see that the DES is active.

In LSK2 we can change the descent speed: set this speed not too high

Also, like in the Climb phase you can set the altitude/speed restriction LSK3, and a second restriction
in LSK4
In LSK 5 it is possible to disable the v/s from XFMC to manual settings (also the altitude) In that case
you will see (MAN) behind the actual cruise phase.Text Yellow: VNAV controlled by XFMC, text white:
VNAV controlled by operator

In RSK1 you see the T/D where it has been calculated from the destination.

RSK3 Set the QNH altitude here

RSK4 set the local QNH of the destination airport here. You get it from the ATC or by query the
metar.

RSK6 When you come within 50 nm of the TOD, the option of DESNOW will become active. If you
activate this the plane starts a slow descent o 500/f min up to then next waypoint.

During this descent XFMC keeps an angle of 3 degrees. In case that a waypoint cannot achieve in
time, a higher descent will become active. This is an automated process.

Normally a descent around –2300 at high altitudes is correct, at lower levels, and lower speed you
will see 1200-1800 v/s

The moment has come to activate our ILS.

Go to the NAV/RAD key and the Navigation Radio page will be opened.

In LSK4 you see already the ILS, click on LSK4 and the ILS frequencies are copied to LSK1-RSK1.

On the Plane panel you will see that NAV1 has become active with VOR1 freq.

No more to do here.
Note: any time you can insert a VOR or NDB by typing the frequency in the command line and
clicking on LSK1-3 or RSK1-3. During the flight, when there are NDB’s or VOR’s in the flight plane,
XFMC will track these on NAV2 and both NDB1 and NDB2.

Also the crs2 of the VOR2 will be set.

Final Approach

We passed the last API point, on 5000 AGL, and it is time to activate the Approach Phase

Go again to MENU and then to Approach.

Activated the approach by clicking on the appropriate setting of the flaps in this case 25 or 30 or 40.

I selected flaps 40, and the flap speed of final approach will be 138 knots

As soon the ILS become active, click on the ILS and APP buttons on the panel. Watch your descent v/s
and watch the MCP setting. XFMC will not take account of these anymore; you must take care of
vertical interception of the glide slope.

As soon we pass the outer marker, you will hear our copilot this telling to you.

Also – if activated in the config- the flaps will be set, 1 detent at the time, starting below 4000 AGL
and within the distance of 12 nm of the airport.

At around 800 AGL the gear will come out (if selected)

The copilot will count down the AGL.

Around 200 feet AGL before landing the flare phase will become active. Leave you manual throttle at
0!

Around 30 feet AGL the autobrake will be set (if activated in the config) you will see it in the upper
display.
The moment the plane touches down, the reverse thrust will be set (if activated in the config)

Then when the speed is below 120 knots the brakes will become active. Indicated in the upper
display.

The brakes are not 100% effective. Normally the plane should stop before the end of the runway, but
you might help a little with you pedals. Also the pilot has to keep the plane in the center of the
runway (side wind!).

In this phase you will see ROLLOUT in the upper display.

And at the end when the plane’s speed is 0, you get the message “End Of Fllightplan” and in the
upper display “PLS taxi to the gate”

Last Note: in this tutorial the XFMC was the entire time active. But any time you want you can disable
it by clicking on the A/C. If XFMC is active, it will be marked in yellow in the upperow.

Also you can control manually the speed. Click on the left upper right screw ATR. If the auto throttle
is linked to XFMC ATR is yellow, if it is linked to xplane FMC it is white.

In case there is ATC, which is giving you vectors, XFMC will be not needed anymore. Best way is to
disabled it, skip all the legs before the destination airport, and as soon you are in line of the runway,
activate XFMC again.

This is the end of our trip. From now on you have to do it yourself.

Loading and saving a flight plan

A flight plan can loaded directly from Route planner. In this case operate in the following way:

Copy past your route from Route planner and save this in Notepad with the following file specifics:

SSSSDDDD.FPL where SSSS is the departure airport, and DDDD the destination airport.

For example EGLLLFML.FPL. Don’t save it as TEXT, but be sure you saved it as “all files”. The file
should be saved in the flight plans directory under XFMC directory.

Loading a flight plan: Always initialize the XFMC first, to be sure you got a clean desk. Then go to
POSITION, then RSK6 ROUTE, then fill in the command buffer your flight plan without the FPL
extension, as example again EGLLLFML, press on RSK3 CO ROUTE and then confirm it with the EXEC
key. If your flight plan is correct and both destination and departure airports exist in XPLANE scenery,
then you will get the message “flight plan loaded” and you will be transferred to the ROUTE PAGE.

NOTE: In case you want to manipulate ROUTEPLANNER, always be sure that in all cases there should
be a start and end in the flight plan, for example EGGL DCT xxxxxx DCT LFML or EGGL SID xxxxx STAR
LFML. There should always be or DCT or a combination of SID/STAR and DCT in the route
description. If not, the route will not be loaded. Good example: LFML SID ETREK UN854 DJL UM129
EPL UM624 DIK UN852 LNO STAR EBBR Bad Example: LFML DCT EBBR

Saving an entered flight plan: In this case you have entered a flight plan via the ROUTE PAGE. After
that this flight plan can be saved by clicking on RTE1 and then ROUTE COPY. The Route will then be
saved again in format of Route Planner and with filename SSSSDDDD.FPL

HOLD

To understand the principals of flying a hold I would refer to this link

http://www.pilotlist.org/zahar/howto.htm

To start a hold selects a waypoint in the legslist also shown in the HOLD page, or click on the
Plane Position to enter your actual position where to hold should start. After that EXEC goes
on, and the RTE1 HOLD page will come up.
To clear a waypoint entered in the list left under: go to CLR or change the page. Non
completed operations will be erased.

Entering the HOLD via the PPOS, will be executed directly.

In the RTE1 HOLD page we can adjust some details of the HOLD.
In case the HOLD is active, you will see ACT in the upper line.

1. LSK1 you see the fix where the holding is performed. Or you will see lat/Lon in case
the PPOS HOLD was started.
2. LSK2 Nothing visible at the moment here.
3. LSK3 Here you can enter via the command line, the course of the HOLD (normally
inline of the last track) and the turning direction Left or Right. Valid format are: XXX/L
and XXX/R
4. LSK4 the leg time of the hold performed. Range 1-20 minutes
5. In case you want the HOLD calculated on Leg distance, you can enter here the
distance. It is in this case or the Leg time you can enter, or the distance. Range is 4-50
nm
6. RSK1 the speed and altitude where the HOLD is performed
7. RSK2 ---Next Time the plane passes the entry point in Zulu time
8. RSK3 -- Estimated Further Clearance Time. The time you may leave the hold. Enter for
example 10 minutes in the command buffer, and you will see here the time in Zulu
when you are allowed to leave the hold. No warnings when you pass this Zulu time
9. RSK4 --- Estimated time left for the holding based on the fuel. The fuel left at arrival
MINUS the reserves are available for the hold and is expressed in XX+YY format. Thus
00+48 will say 48 minutes left to stay in the hold. 00-02 will say: you have to leave
the hold right away, because you will use your reserves at the end of this trip!
 10. RSK5 --- Holding speed. Can be adjusted, normally 240 knots
11. RSK6. When you want to leave the HOLD, click on EXIT HOLD, and after the
completion of the hold turn the plane will leave the hold and continues the f/p

---------------------------------------------------------------------------------------------------------------------

Config
For a good operation of the FMC a configfile is needed.
Standard are now 6 types programmed in the FMC, depending of you models grossmaxWeight the model will
be selected when no config file is found in the directory of your plane.
By this way you can fly, but the data is not quite correct.

To make a better configfile, i included a tool to make a specific configfile for your plane.

The operation is quite easy:

1. Start with this standardmodel. Not Online, No wind....

2. Go to YBCS runway 15
3. Type in the command line MAKECONFIG Click then on FIX key on the FMC
4. in the directory you will find now a configfile named xxx_1.cfg. (xxx=your planes name) You don't see .cfg.
for example B737-800ER_1
5. Open this file with notepad and have a look at the values, mach, climb speed, descent speed. Are there
correct? Don’t set these too high, because otherwise the test will fail, if the plane cannot reach the climb up to
fl 390....
6. Change the planes name and the engines to what your plane is. Save the file if all ok.
7. rename the file to xxx.cfg (so without the _1)
8. Click on Initialize. If all done well, you will see in IDENT your new planes configname and date of the config
9. type in the command line STARTCONFIG and click on FIX
10. set the flaps what needed for takeoff fuel + payload half loaded
11. Click the FMC on (ATC button)
12. let the plane take off, and wait
13. first the plane climbs to 38500
14. after that the plane descents to 1500
15. then the plane climbs in steps to 38500
16. If you hear "Tada" sound the config is written for your plane
17. Go to the directory of your plane and rename the config to your models name: example you made a test
for the B737-800ER. In the directory you will find then a config named B737-800ER_1.cfg Rename it to B737-
800ER
18. Final: check the data if all is correct. Watch the values in the NominalClimbspeed, NominalDescentSpeed,
NominalCruisespeed, ThrustN1, and ThrustN1Climb. There must be no 0 in there, and if there are values which
are too high according other values in the same row, change the values!. Every step you see data of 2000 feet,
for example
NOMINALFUELCRUISE=349,200,183,183,183,183,183,183,183,183,183,183,183,183,183,183,183,183,183,183,
is correct, but
#NOMINALFUELCRUISE=349,200,183,183,183,183,183,183,183,183,183,183,183,183,183,183,2100,183,183,18
3, is not correct. Change then the 2100 to 183. This can happen when the plane was not stable at the moment
the sample of the Fuel was taken.

A lot of things can happen during this test. If the plane cannot reach the flight level FL385, your climb speed is
too high, or the plane has not the power to climb half loaded to that level. Change then these values and try
again the test.

XFMC will not change the V1, V2, Vref and Approach Speeds. If not correct, you have to adopt these to better
values according your plane.
When the model is loaded there is a standard check on some values if they are correct. If XFMC will detect
something, you will read it in the command line...so don’t be surprised you see there an error after you
changed your configfile....

Automated functions

Included in this FMC are some automated functions.

These are handy, but of course NOT real.

You can let the FMC:

GearUp and GearDown ( takeoff at 200 feet AGL and 800 f AGL before landing)
Flaps retrack and deploy (in steps) (starts by take off after the first set transitionlevel,
normally 1500 AGL; at descent it started in steps the moment the Approach is activated
AND the plane is closer then 12 nm from the destination airport)
RTO switch setting before take off
Autobrake switch setting (position 3)
Reverse Thrust the moment the plane touches down
Brakes after the Reverse thrust. (when the speed is lower than 120 kn)

You can enable and disable these functions by setting the appropriate bit in the Config file
#A_CONFIG=63
CONFIG=0 all functions OFF
CONFIG=63 all functions ON

CONFIG=1 gear
CONFIG=2 flaps
CONFIG=4 RTO
CONFIG =8 Autobrake
CONFIG=16 Reverse thrust
CONFIG=32 Brakes
CONFIG=64 reserved
CONFIG=128 reserved

any combination can be made, thus Gear + flaps + RTO = 1 + 2+4 = CONFIG 7