Create and fly a flight plan in X-Plane Mobile, find the map on Android, enter a KMIA route, fix NAV/LNAV, and understand route imports.
In X-Plane Mobile, create a flight plan in the app’s editable route map when available, or enter it directly in the aircraft’s GPS/FMC. Add the departure, destination and fixes in order, activate the route, select GPS/FMS guidance, then engage NAV or LNAV only after establishing an intercept with the active leg.
X-Plane is also commonly typed as X Plane or XPlane. The correct aviation term is flight plan; if you searched for a “plane plan”, this is the ordered route that the navigator and, when configured correctly, the autopilot can follow.
The mobile app does not present one identical planner in every aircraft or screen context. An editable app map, a cockpit moving map and an airliner’s FMC are separate tools, and a route entered into one may not automatically appear in another.
Which X-Plane Mobile flight planner should I use?
Use the app planner for a simple route when editing controls are available; otherwise, enter the flight plan in the aircraft’s GPS or FMC.
| Route-entry method | Choose it when | Main limitation |
|---|---|---|
| App map or route planner | The map lets you search for airports and add or reorder route points | Some maps are display-only, and transfer to cockpit avionics varies |
| Panel GPS | The aircraft has a Garmin-style navigator or integrated glass cockpit | The route must be entered and activated through that unit’s controls |
| Airliner FMC/CDU | The aircraft uses an FMS and LNAV | The app-level route may not synchronise with the FMC |
How do I create a flight plan in the mobile map?
Use this method only when the installed X-Plane Mobile interface provides an editable map, route or flight-plan screen.
- Choose the aircraft and starting position: Selecting an airport or runway positions the aeroplane, but it does not necessarily create a route or load a departure procedure.
- Open the editable planner: Inspect both the pre-flight setup and the in-flight app controls for a map, route or flight-plan function. Its icon and position can differ by device, aircraft and app context.
- Add the origin: Search by ICAO identifier, such as
KMIA, and confirm that the airport appears in the route list. Merely centring an airport on the map is not enough. - Add the destination: Enter its ICAO identifier and make sure it becomes the final route point rather than another map selection.
- Insert fixes in order: Add recognised waypoints, navaids or airports in the sequence you intend to fly. If the planner rejects an airway name, add the relevant fixes individually or use the FMC.
- Add procedures separately: A departure, arrival or approach must be selected independently when supported. For the procedure workflow and common database limitations, see our guide to adding SIDs and STARs in X-Plane Mobile.
- Apply and check the route: Use Activate, Load, Execute or the equivalent control when one is shown. If changes apply when the planner closes, verify that the navigator displays a sensible next waypoint, bearing, distance and highlighted leg.
A common mistake is entering the right fixes in the wrong order. Also check the full name and type associated with each identifier: duplicated or similar identifiers can place a leg far away from the intended route.
Worked example: entering a KMIA flight plan
This training example uses KMIA-DHP-RSW-KRSW to demonstrate airport identifiers, ordered fixes and route activation; it is not presented as a real-world ATC clearance.
- Set the origin to KMIA: Search for
KMIAand confirm that the result is Miami International Airport. Choosing a KMIA runway alone may only set the starting location, so make sure KMIA also appears as the route origin. - Set the destination to KRSW: Add
KRSWas the final airport. Do not confuse it withRSW, which the navigation database may identify as a nearby navaid. - Add the ordered fixes: Insert
DHPafter KMIA, followed byRSW. The displayed sequence should beKMIA-DHP-RSW-KRSW. - Activate or execute the route: Accept the changes using the control provided by the planner, GPS or FMC. In an FMC, resolve any route discontinuity before execution.
- Verify the active leg: When departing KMIA, the expected next fix will normally be DHP. Depending on the navigator, it may show a KMIA-to-DHP leg or a direct leg to DHP. Check that the bearing and distance are plausible and that the highlighted course leads away from KMIA.
- Select an approach separately: Adding KRSW as the destination does not load a runway, transition or instrument approach. Choose the required approach through the supported GPS/FMC procedure controls and verify the new legs before using them.
Where is the flight plan map in X-Plane Mobile on Android?
On Android, the map and planner controls vary with the selected aircraft, whether the flight has started, and whether you are viewing an app overlay or a cockpit display.
- Reveal hidden overlays: Tap once away from cockpit switches to reveal app controls that have faded or been hidden. Check the general menu and map icons rather than assuming the control is permanently visible.
- Check both app contexts: Inspect the Free Flight or pre-flight setup before departure, then inspect the in-flight menu after loading the cockpit. A planner available in one context may not appear in the other.
- Distinguish the app map from the cockpit map: A navigation display or multifunction display can show aircraft position and route data without accepting map taps or route edits.
- Look for actual editing controls: If the map has no Add, Edit, Route or equivalent function, treat it as display-only. Enter the route through the panel GPS or FMC instead.
- Ignore desktop-only instructions: Menu paths, plugins and flight-plan folders described for desktop X-Plane do not become available merely because the mobile device runs Android.
If a route line appears on the Android map but not in the cockpit navigator, the two systems have not synchronised for that aircraft. Re-enter the route in the GPS or FMC and activate it there.
No veo el mapa interactivo: qué hacer
En X-Plane Mobile, “no veo el mapa interactivo” suele significar que la superposición está oculta, que el mapa actual solo muestra información o que el avión seleccionado exige introducir la ruta en el GPS/FMC.
- Toque una zona libre de interruptores para mostrar los controles ocultos y revise tanto el menú previo al vuelo como el menú durante el vuelo.
- Si el mapa no ofrece controles para añadir o editar puntos, es un mapa de visualización, no un planificador.
- En ese caso, introduzca el origen, el destino y los puntos de ruta directamente en el GPS o FMC del avión, active la ruta y compruebe el tramo activo.
How do I enter the route in the aircraft’s GPS or FMC?
Use the cockpit navigator when no editable app planner exists or when the aircraft expects its own avionics to hold the active route.
In a general-aviation aircraft, open the GPS flight-plan page, enter the origin and destination, insert intermediate fixes, load any supported procedure and activate the intended route or leg. Knob, touchscreen and menu operation depends on the navigator fitted to that panel.
In an airliner, the FMC/CDU is normally the authoritative route source. Enter the airports and route legs, remove unintended discontinuities, execute the route and confirm that it appears on the navigation display. Our mobile FMC route-entry instructions explain that process in more detail.
Do not assume that a flight plan visible on the app map has populated the GPS or FMC. Open the cockpit flight-plan page and check the waypoint sequence itself.
How do I make the aircraft follow the flight plan?
The flight plan must be active, the correct navigation source must be selected, and the aircraft must be positioned where NAV or LNAV can capture the active course.
- Check the next waypoint: Confirm that the active fix, bearing and distance make sense. If an earlier leg remains active, select the intended leg or use Direct-To cautiously.
- Select GPS or FMS guidance: On a G1000-style panel, the CDI source normally needs to show GPS rather than VLOC. Other aircraft may label the source GPS, FMS or NAV source.
- Engage the autopilot if the aircraft should turn itself: A flight director can display steering commands without moving the controls. The autopilot or the aircraft’s supported automatic flight system must be engaged for automatic tracking.
- Intercept the active course: Use heading mode or hand-fly towards the route at a shallow angle. Do not fly parallel to the leg and expect immediate capture.
- Arm NAV or LNAV: Use NAV for the relevant general-aviation GPS installation or LNAV in an airliner that models it.
- Watch the mode annunciator: Confirm that the mode changes from armed to captured and that the aeroplane begins correcting towards the course. The annunciator is more informative than the button light.
You can also hand-fly the plan by following the active course and keeping the course-deviation indication centred. For aircraft-specific mode checks, see our NAV and GPS autopilot troubleshooting steps.
“I pressed it, nothing happened” — why did NAV or LNAV not work?
Pressing NAV or LNAV requests the mode; it does not guarantee an immediate turn. An armed mode is waiting for capture conditions, while a captured mode is actively steering the aircraft.
Use this immediate recovery sequence:
- Return to heading control: Select heading mode and establish a safe, stable track rather than repeatedly pressing NAV.
- Confirm automatic control: Check that the autopilot is engaged if you expect the aircraft to turn itself. Flight-director bars alone are only commands for the pilot to follow.
- Check the navigation source: Select GPS or FMS for a GPS route. VLOC, LOC or a radio-navigation source will not follow the en-route GPS flight plan.
- Correct the active leg: Activate the intended next leg, or use Direct-To for the next fix if appropriate. Direct-To normally bypasses preceding route points.
- Set an intercept heading: Use heading mode to approach the active course at a shallow angle. If the leg is behind the aircraft, turn towards a sensible intercept rather than waiting for NAV to reverse the aeroplane.
- Arm and monitor: Press NAV or LNAV once, then watch the flight-mode annunciation. Keep heading mode in command until the navigation mode captures.
| Symptom | Likely cause | Action |
|---|---|---|
| The route is visible but the aircraft continues straight ahead | The autopilot is off, or NAV/LNAV remains armed | Engage the appropriate automatic flight system and establish an intercept |
| HDG remains active while NAV is armed | The aircraft has not reached capture conditions | Keep using heading mode to converge with the active leg |
| The aircraft turns back towards departure | An earlier leg or waypoint is still active | Activate the intended leg or select Direct-To for the correct next fix |
| The CDI shows VLOC or LOC | The panel is following a radio receiver | Select GPS until a radio-based approach requires VLOC or LOC |
| No route appears in the cockpit navigator | The app planner did not transfer it | Enter and activate the route directly in the GPS or FMC |
Does the flight plan control altitude and the approach?
An X-Plane Mobile flight plan mainly defines the lateral route; it does not automatically manage every altitude, speed, descent or landing task.
Set climb, cruise and descent targets using the modes supported by the aircraft, and manage power separately. VNAV can follow programmed constraints only where the aircraft, procedure and avionics implementation support that function.
For an ILS, the GPS route can take you towards the final approach area, but the aircraft must use the localiser at the appropriate stage. Tune and identify the frequency where required, select VLOC or LOC, establish a valid intercept and arm approach mode. For an RNAV approach, retain GPS guidance and activate the loaded approach; vertical guidance appears only when the navigator and procedure provide it.
Can X-Plane Mobile import or share a flight plan?
X-Plane Mobile does not use the universal desktop workflow of copying an .fms file into a user-accessible flight-plan folder and loading it through desktop menus.
| Task | Mobile behaviour | What to do |
|---|---|---|
| Copy a desktop route file to Android storage | Desktop folder instructions do not apply to the mobile app | Recreate the route manually unless the installed app exposes a specific import command |
| Open a route through the Android share menu | There is no import method that can be assumed across all builds and aircraft | Use it only when X-Plane Mobile explicitly appears as a supported destination and presents an import result |
| Transfer an app-map route to the cockpit | Transfer depends on the aircraft and avionics implementation | Inspect the GPS/FMC route page and enter the plan there if it is empty |
| Share a route with another mobile user | A universal cross-device route file cannot be assumed | Share the ordered identifier string and procedure details, then have the recipient recreate and verify it |
Manual recreation is the dependable fallback. Copy the route as an ordered string such as KMIA DHP RSW KRSW, enter each identifier into the mobile planner or cockpit navigator, add supported procedures separately, activate the plan and check the active leg. If an airway name is not accepted, enter its required fixes individually.
Do not assume a saved route will persist after changing aircraft or starting another session. Recheck the waypoint sequence, procedures and active leg before departure.
Desktop X-Plane has different file access, menus and loading behaviour. Desktop users should follow the separate X-Plane 12 flight-plan creation and loading process rather than applying mobile instructions in reverse.