Learn how GPS navigation in a flight simulator calculates position, follows routes, drives the CDI and autopilot, and why guidance sometimes fails.
In a flight simulator, GPS navigation takes the aircraft’s simulated position, compares it with waypoints and procedures in the avionics navigation database, then calculates desired track, distance, bearing and cross-track error. The cockpit GPS or FMS displays that guidance; a CDI, HSI, flight director or autopilot can then follow it.
In general flight simulators, GPS may mean a standalone panel navigator, a glass-cockpit function or a position source feeding an airliner’s flight-management system. The controls and level of realism vary, but the underlying process is much the same.
What is actually being simulated?
- Aircraft position: The simulator engine already knows the aircraft’s latitude, longitude, altitude and movement. A basic GPS receives this as an effectively perfect position, while more detailed avionics may model satellite acquisition, receiver integrity, outages or blending with inertial sensors.
- Route data: The navigator reads waypoints, airways, airports and instrument procedures from its navigation database. Each fix has defined coordinates, and advanced systems also interpret different leg and turn types.
- The active leg: The GPS identifies the leg being flown and calculates the desired track between its start and end points. It then measures how far the aircraft is left or right of that track.
- Cockpit guidance: The result appears as a magenta route, CDI deviation, bearing, distance and estimated time. If the correct source and mode are selected, the flight director or autopilot can use the same lateral guidance.
The desired track is not necessarily the heading to fly. Wind may require the aircraft to point left or right of course while maintaining the correct track over the ground.
Most simulator GPS units do not receive real satellite signals, so GPS navigation itself does not inherently require an internet connection. Streaming maps, live services and navigation-data updates are separate features.
Why does the navigation database matter?
The GPS can only recognise fixes and procedures contained in the database available to that aircraft’s avionics. Simulator scenery, the route planner and an add-on FMS may use different data, which can produce missing waypoints, changed procedure names or a runway that does not align perfectly with the displayed approach.
A database mismatch is particularly noticeable when importing routes or selecting departures and arrivals. Our explanation of simulator navdata and database updates covers when an update is useful and why every installed component should use compatible data.
What do the GPS indications mean?
| Indication | What it tells you |
|---|---|
| DTK | The desired ground track for the active leg. |
| TRK | The aircraft’s actual track over the ground, which may differ from heading because of wind. |
| BRG | The direct bearing from the aircraft to the selected waypoint; this is not always the same as the leg’s desired track. |
| CDI or XTK | How far the aircraft is left or right of the active course. |
| DIS and ETE | Distance and estimated time to the active waypoint, based on the unit’s calculated groundspeed. |
| Magenta line | The mapped route or active leg. Its presence does not prove that the autopilot is coupled to it. |
On avionics that model flight phases, CDI sensitivity becomes tighter during terminal and approach operations. This makes small deviations more obvious near the runway than during the en-route phase.
How do you start following a GPS route?
- Load the route into the aircraft’s actual GPS or FMS. Do not assume a route made in the simulator’s planning screen has transferred into every add-on aircraft.
- Check the fixes, departure, arrival and approach. Remove unintended discontinuities, but retain any manual or vector leg required by the procedure.
- Activate the intended leg. A displayed flight plan can still have an old waypoint, direct-to command or wrong leg active.
- Select GPS or FMS as the navigation source. Labels vary by aircraft; common alternatives include
GPS,FMS,NAVandVLOC. - Follow the CDI manually, or intercept the course and arm the appropriate autopilot lateral mode.
- Monitor waypoint sequencing. Check that the next expected fix becomes active after each turn.
For the cockpit actions behind these steps, see our practical guide to operating simulator GPS units.
How does GPS guidance reach the autopilot?
GPS does not move the controls directly. It supplies lateral guidance, while the autopilot’s NAV or LNAV mode commands bank to intercept and maintain the calculated course.
The navigation source must be correct, and the mode must become active rather than merely armed. If HDG mode remains active, the aircraft will continue following the selected heading even though the GPS route is displayed. A large intercept angle, excessive speed or activating a leg behind the aircraft can also cause an overshoot or turn in the wrong direction.
Aircraft differ in how their FMS, flight director and mode annunciator interact. Our autopilot mode and capture guide explains the distinction between selecting, arming and capturing a navigation mode.
Can simulator GPS provide vertical guidance?
Basic GPS navigation is lateral only; it does not automatically control altitude or descent. A unit may calculate an advisory VNAV profile, while suitably equipped aircraft can follow coded approach guidance or an FMS-managed vertical path.
An RNAV approach may provide LNAV-only guidance, advisory vertical information, LNAV/VNAV or an LPV-style glidepath, depending on the procedure, database and simulated avionics. That glidepath is not an ILS glideslope, even if the cockpit indication looks similar. The worked RNAV approach procedure for Microsoft Flight Simulator shows how route navigation transitions into approach guidance.
Why is GPS not following the flight plan?
| Symptom | Likely cause and fix |
|---|---|
| The route appears, but the autopilot flies straight | The aircraft is probably in heading mode, or NAV/LNAV is only armed. Establish a sensible intercept and confirm the lateral mode annunciation. |
| The autopilot follows a VOR instead | The CDI source is set to VLOC or a conventional NAV receiver. Change it to the aircraft’s GPS or FMS source. |
| The aircraft turns back towards an old waypoint | The wrong leg is active. Activate the intended leg or use direct-to only when that is operationally appropriate. |
| The route stops sequencing | Look for OBS, SUSP, a discontinuity, vectors or a manual-sequence leg. Resolve it only when cleared or ready to continue. |
| The cockpit route differs from the planning map | The route may not have transferred, or the planner and aircraft may use different navigation data. Verify the route inside the aircraft rather than trusting the external map. |
| An approach has no glidepath | The procedure may not provide vertical guidance, may not be activated, or may be unsupported by that navigator. Confirm the approach type, active leg and displayed navigation source. |
If every selection looks correct but the behaviour remains implausible, check whether the aircraft uses an independent add-on FMS rather than the simulator’s default flight plan. That separation is a common reason for seeing one route on the world map and another in the cockpit.