Comprehensive Guide To Uploading Flight Factor Flight Plans To The FMC

Successfully uploading a flight plan to a Flight Factor FMC requires exporting a compatible .flp or .fpl file from a flight planner like SimBrief into the specific aircraft data folder within your X-Plane directory. Once the file is correctly placed, pilots must use the CO ROUTE function on the Boeing CDU or the INIT page on the Airbus MCDU to initialize the lateral navigation path. Ensuring AIRAC cycle synchronization between your planner and the aircraft database is the primary benchmark for avoiding database errors during the uplink process.

Critical Pre-Flight Configuration and Directory Mapping

Before attempting to uplink data to a high-fidelity Flight Factor aircraft, you must establish a bridge between your external flight planning software and the X-Plane 11 or X-Plane 12 file structure. Unlike default aircraft, Flight Factor products—specifically the A320 Ultimate, the 757 Professional, and the 767 Professional—utilize proprietary data handling for their Flight Management Computers (FMC) and Multipurpose Control and Display Units (MCDU).

To ensure a seamless data transfer, you must have an active SimBrief account (or a similar dispatch tool) and the SimBrief Downloader utility installed. The Downloader automates the placement of files, which is critical because manual placement often leads to directory errors. You also need to verify that your AIRAC cycle (Aeronautical Information Regulation and Control) matches across all platforms. If your SimBrief plan uses cycle 2403 but your aircraft is running an older base cycle, the FMC will reject specific waypoints or airways, leading to a "Not in Database" error.

Essential Pre-Flight Checklist

• Aviation Dispatch Tools: A SimBrief account or PFPX (Professional Flight Planner X) is mandatory for generating the operational flight plan (OFP) and the machine-readable route file.
• Directory Access: You must have administrative write-access to the X-Plane 11/12 Aircraft folder and the Output/FMS plans folder.
• AIRAC Synchronization: An active Navigraph subscription is highly recommended to ensure the FMS database and the planner use identical navigational data.
• Plugin Dependencies: Ensure the latest version of the X-plane "FlightFactor" plugin is active in your plugins menu; otherwise, the custom data-link features will be unresponsive.
• Time Commitment: Initial setup takes approximately 15 minutes, while subsequent uploads take less than 60 seconds during the pre-flight phase.

Technical Execution of the Flight Plan Uplink

The process differs significantly between the Flight Factor Boeing series (757/767/777) and the Airbus A320 Ultimate. Both require a specific file format, usually an .fpl or .flp file, which contains the sequence of waypoints, airways, and terminal procedures.

Step 1: Generating and Exporting the Flight Plan

Open your browser and navigate to SimBrief to create a new flight. Input your departure, arrival, and alternate airports along with your airframe type (e.g., B752 for the 757 or A320 for the Airbus). Once the plan is generated, use the SimBrief Downloader.

For Flight Factor Boeing aircraft, you must target the "X-Plane 11/12 / Output / FMS plans" directory. The file should be saved in the .fms format.

For the Flight Factor A320 Ultimate, the file path is more specific. You must navigate to "X-Plane / Aircraft / FlightFactor A320 Ultimate / data / routes". The A320 requires the file to be in a specific .flp format that its custom systems can parse.

Step 2: Initializing the Boeing FMC (757/767/777)

Once the simulator is loaded and the aircraft is at a cold-and-dark state or on APU power, bring up the CDU (Control Display Unit).

1. Press the RTE (Route) button on the CDU keypad.
2. Locate the CO ROUTE (Company Route) field, which is usually at LSK 2L (Line Select Key 2 on the left).
3. Type the filename of the exported plan into the scratchpad. For example, if your file is named "EDDFEGLL.fms", you only need to type "EDDFEGLL".
4. Press LSK 2L to insert the name. The FMC will now "read" the file from the Output/FMS plans folder and populate the departure, arrival, and all intermediate waypoints.
5. Press the ACTIVATE soft key followed by the EXEC (Execute) button to finalize the lateral path.

Pro-Tip: If the FMC returns an "Invalid Entry" error, double-check that the filename in the scratchpad matches the filename in your Output/FMS plans folder exactly, excluding the .fms extension.

Step 3: Initializing the Airbus MCDU (A320 Ultimate)

The Flight Factor A320 Ultimate utilizes a more modern "Datalink" system that mimics real-world AOC (Aeronautical Operational Control) communications.

1. On the MCDU, press the MCDU MENU button.
2. Select ATSU followed by AOC MENU.
3. Navigate to the INIT/PRES page. Here, you should see an option for INIT DATA REQ (Initialization Data Request).
4. Pressing this will trigger the aircraft to look into its internal "data/routes" folder. If you have placed the .flp file correctly, the MCDU will pull the flight number, from/to pair, and alternate.
5. Return to the main INIT page. You should see your departure and arrival airports populated. Press the INSERT or INIT REQUEST prompt to load the full string of waypoints into the Flight Plan (F-PLN) page.

Warning: Do not attempt to load the flight plan while the aircraft is in motion. The Flight Factor A320 system logic may crash the plugin if the FMGC (Flight Management Guidance Computer) attempts to recalculate V-speeds and performance data while the IRS (Inertial Reference System) is in a state of flux during taxi.

Step 4: Performance Data and Secondary Flight Plan

Loading the route is only the lateral half of the equation. You must also provide the FMC with vertical data.

1. Go to the PERF (Boeing) or INIT B (Airbus) page.
2. Input your Zero Fuel Weight (ZFW) and Fuel On Board (FOB).
3. On the Airbus, you must also input the "Cost Index," which determines the trade-off between fuel burn and time. This value is found on your SimBrief OFP.
4. Confirm the "Flight Level" or "Cruise Alt." If the uploaded plan includes step climbs, the FMC should automatically reflect these in the VNAV (Vertical Navigation) profile.

Comparative Specifications for Flight Factor FMC Integration

The following table outlines the technical differences in how various Flight Factor models handle external data files. This reference is crucial for pilots who fly multiple airframes within the FF ecosystem.

Troubleshooting Common Uplink Failures

Root Cause: AIRAC Mismatch

If the FMC loads the route but leaves large gaps (Discontinuities) or displays "Waypoint Not Found," the navigation database in the simulator is likely older than the one used to create the flight plan.

• Actionable Fix: Update your X-Plane "Custom Data" folder using the Navigraph Hub or the Aerosoft NavDataPro tool. Ensure you also select the "Flight Factor A320" specific mapping in the update tool, as it occasionally uses its own internal folder separate from the global X-Plane data.

Root Cause: Incorrect File Extension

A common error is saving a Boeing-formatted file for an Airbus or vice-versa. SimBrief offers different export formats; selecting the wrong one will result in the FMC being unable to see the file.

• Actionable Fix: In the SimBrief Downloader, ensure the "Flight Factor A320" entry points to the .flp format and the "X-Plane 11/12" entry points to the .fms format. Never manually rename a .fms file to .flp, as the internal syntax structure is fundamentally different.

Root Cause: Plugin State Desynchronization

Sometimes the Flight Factor "Phone" (EFB) or MCDU becomes unresponsive to "INIT REQUEST" commands, even if the file is in the correct folder.

• Actionable Fix: Ensure the IRS (Inertial Reference Systems) are set to "NAV" and have reached at least a "Quick Align" state. Most FF aircraft logic gates the FMC upload functions behind the IRS alignment to simulate real-world electrical and navigational dependencies.

Frequently Asked Questions

Why does my Flight Factor A320 say "No Company Route Found"?

This typically occurs when the .flp file is named differently than the From/To string expected by the MCDU. Ensure the filename follows the format "DEPARTUREARRIVAL.flp" (e.g., KJFKLAX.flp) and that it is placed in the "data/routes" subfolder within the A320 aircraft folder, not the general X-Plane FMS plans folder.

Can I upload a flight plan directly from the SimBrief website without the Downloader?

Yes, you can manually download the file from the SimBrief "Generate" page. However, you must manually move it from your "Downloads" folder to the correct X-Plane directory. For the Boeing fleet, this is "Output/FMS plans," and for the A320, it is "Aircraft/FlightFactor A320 Ultimate/data/routes."

Does the Flight Factor FMC support SIDs and STARs via upload?

Most Flight Factor aircraft will load the en-route waypoints but require you to manually select the Standard Instrument Departure (SID) and Standard Terminal Arrival Route (STAR) via the DEP/ARR page. This is because runway-specific transitions often change based on real-time weather and ATC instructions provided during your clearance.

How do I fix "Program Error" on the FMC when loading a route?

A "Program Error" or "MCDU Timeout" usually indicates a syntax error within the flight plan file, such as a coordinate formatted in a way the plugin cannot read. This often happens with transoceanic tracks (NATs). To fix this, regenerate the plan in SimBrief ensuring "Detailed RNAV" is selected and try the upload again.

Master Your Virtual Flight Deck

Enhance your flight simulation realism by mastering the complex systems of Flight Factor aircraft through consistent practice and proper data management. For more advanced tutorials on oceanic procedures and automated flight guidance, continue exploring our technical aviation library.