X-Plane 11 Default FMC Tutorial
By Paul Mort
Overview
Hello and welcome to this tutorial. This time I will be covering the use and facilities of the updated default FMC used in X-Plane 11. As I am sure you all know, in most cases in X-Plane 10, the FMC in a large aircraft was a fairly basic 'point and shoot' affair, with the exception of good payware models. This is not so in X-Plane 11. Here we are given a more useful and feature-packed FMC as standard, and it is from this we will take our example for this tutorial, using the default X-Plane 11 Boeing 737-800.
The Route
Being from the UK, naturally I chose a route in an area I was familiar with. Starting from my local airport, Manchester International (EGCC), I was going to fly the short distance to Bristol Airport (EGGD). Using an online route finder, the data for my flight was mapped out, as shown below.
Cruise altitude between 5000 and 5000
EGCC (0.0nm) -SID-> MONTY (42.6nm) -N42-> RETSI (67.9nm) -STAR-> EGGD (136.0nm)
Details:
ID | TRK | DIST | Coords | Name/Remarks |
EGCC | 0 | 0 | N53°21'14.00" W002°16'30.00" | MANCHESTER |
MONTY | 229 | 43 | N52°53'34.00" W003°10'26.00" | MONTY |
RETSI | 154 | 25 | N52°30'42.00" W002°52'33.00" | RETSI |
EGGD | 174 | 68 | N51°22'57.61" W002°43'08.76" | BRISTOL |
Note: Tracks are magnetic, distances are in nautical miles.
EGCC SID MONTY N42 RETSI STAR EGGD
This is a fairly basic route and ideal for the purposes of this tutorial.
The FMC
To begin with, we will use Runway 23L as the departure runway, as our route takes us in a south-westerly direction. So here we are on Runway 23L at Manchester, ready to roll with the pop out FMC (Figure 1) on view.

Figure 1
If we take a closer look (Figure 2) we can see the default FMC index page outlined in red, and that it is page 1 of 1. The message at the bottom also tells us that the navaid database is not current but this can be easily rectified with an update from the Navigraph web site (for a small fee). However, it is still functional, so for the purpose of this tutorial it can remain as it is.

Figure 2
vBulletin Message