Use the Prepar3D flight planner to create, save and load VFR or IFR routes, connect GPS and ATC, and fix missing .PLN flight plans.
Open Prepar3D’s Flight Planner from the Navigation menu, choose departure and destination airports, select VFR or IFR and a routing method, set the cruising altitude, then generate and save the route. Load the saved plan into the scenario; the default GPS and ATC can then use it, but many add-on aircraft require a separate import.
How do I create and load a Prepar3D flight plan?
The reliable workflow is to build the route, inspect it, save the .PLN file and confirm that it is active before departure.
- Open Flight Planner: With a scenario running, open the Navigation menu and select Flight Planner.
- Select the departure airport: Search by airport identifier, name or location. Confirm that you have selected the intended airport, especially where several fields have similar names.
- Select the destination: Use the same search controls and verify the airport identifier. Add-on scenery can change runways without changing the underlying airport code.
- Choose VFR or IFR: Select VFR for a route that will be flown without an IFR clearance. Select IFR when you want Prepar3D’s default ATC to handle the flight as an instrument flight plan.
- Choose a routing method: Pick Direct–GPS, VOR-to-VOR, low-altitude airways or high-altitude airways according to the aircraft and type of flight.
- Enter a cruising altitude: Use an altitude suitable for the aircraft, route, terrain and direction of flight. The planner does not check every operational or performance constraint for you.
- Generate and inspect the route: Select Find Route, then review the waypoint list and map. On the route-editing view, you can adjust the path through suitable waypoints or navaids before saving it.
- Save the plan: Give the route a recognisable name and retain the
.PLNextension. The suggested Prepar3D files folder under Documents is the easiest location unless an add-on requires another folder. - Position the aircraft carefully: Prepar3D may ask whether it should move the aircraft to the departure airport. Choose Yes for a fresh start there, or No if the aircraft is already parked at the correct gate or stand.
To reopen a route later, return to Flight Planner, select Load, choose the saved .PLN file and accept it. Saving a plan and loading it as the active plan are separate actions, which is a common source of confusion.
Which routing option should I choose?
Choose the routing method that matches the aircraft’s navigation equipment and the way you intend to fly.
| Routing option | Best used for | Main limitation |
|---|---|---|
| Direct–GPS | Simple point-to-point flights and GPS-equipped general aviation aircraft | A straight line may cross unsuitable terrain, restricted areas or unrealistic airspace |
| VOR-to-VOR | Practising conventional radio navigation | Routes can be indirect, and each navaid must be within usable range |
| Low-altitude airways | Lower-level IFR flights, turboprops and shorter sectors | The generated route still needs altitude and airway checks |
| High-altitude airways | Airliners and faster aircraft operating at higher flight levels | It does not automatically create a complete airline-style SID or STAR |
The built-in planner uses Prepar3D’s simulator navigation database. If its airway choices are poor or you need finer control over procedures and exports, our guide to planning and exporting Prepar3D-compatible routes with Little Navmap explains the alternative workflow.
Does the flight planner load the GPS and ATC route?
A loaded plan is normally available to Prepar3D’s default GPS and default ATC, but it does not configure the entire aircraft for you.
In a compatible default-style cockpit, select GPS as the navigation source and use the autopilot’s NAV mode to follow the route. The autopilot will not set the cruising altitude, manage the throttle, select an approach or perform the flight automatically. NAV mode may also need the aircraft to be positioned where it can intercept the planned track.
With an IFR plan active, open the ATC window and request the appropriate IFR clearance. ATC follows the simulator’s active flight plan, not an unrelated route entered only into an add-on FMS. For the flying side of the process, see our guidance on setting up and flying an IFR route, approach and missed approach.
Why does my saved .PLN route not appear?
A missing route usually means the plan was saved but not activated, the aircraft uses its own flight-management system, or two navigation databases disagree.
- Saved but not loaded: Reopen Flight Planner, use Load and verify that the waypoint list shown is the intended route.
- Add-on FMS remains empty: Many complex aircraft do not read Prepar3D’s active plan automatically. Import the route using the aircraft’s documented format or enter it through the CDU. For some older aircraft, a utility that can convert a simulator .PLN into a legacy aircraft route format may help, although compatibility depends on the aircraft and Prepar3D version.
- Waypoints are rejected: The simulator and add-on avionics may use different navigation-data cycles. Rebuild the disputed segment using the database installed in the aircraft.
- The autopilot ignores the route: Check whether the cockpit is using GPS/FMS guidance rather than VOR or localiser guidance, then confirm that the correct lateral mode is armed or engaged.
- The aircraft moves unexpectedly: Choose No when Prepar3D offers to relocate it if you are already positioned at the departure airport.
- The route changed after loading: Confirm that you did not load an older file with the same name and save edited versions under distinct names.
What must I add before departure?
The built-in planner mainly creates the en-route path; it is not a full airline dispatch or FMS programming tool.
Check the departure position, runway, fuel, weather, terrain clearance and cruising altitude separately. For airline operations, enter or verify the SID, STAR, runway transition, performance data and approach in the aircraft’s own avionics. If you change that route, remember that Prepar3D’s default ATC will continue using the active .PLN until you update or replace it.