How To Add Co Route To Flight Factor 757
Entering a company route (co route) into the Flight Factor 757 Control Display Unit (CDU) streamlines flight planning by instantly loading saved flight plans directly from navigation databases. Mastery of this procedure prevents manual waypoint entry errors and ensures seamless integration with the aircraft's authentic Smiths Industries Flight Management Computer (FMC) logic.
Pre-Operation & Flight Planning Checklist for the Flight Factor 757
Operating the Flight Factor 757 requires strict adherence to proper simulation workflows, particularly when managing navigation databases and flight plans. Before attempting to load a co route into the FMS, pilots must ensure the simulation environment is properly configured, the navdata is up to date, and the required route files reside in the correct directory structures to avoid loading failures or alignment errors.
- Essential gear/tools/materials: Flight Factor 757 (Pro or Extended edition), an active Navigraph or Aerosoft AIRAC cycle matching the simulator database, a validated flight plan file generated via SimBrief or built manually, and a fully powered aircraft with an aligned Inertial Reference System (IRS).
- Mandatory prerequisite knowledge/standards: Familiarity with Boeing FMC architecture, understanding of standard ICAO four-letter airport codes, and correct formatting conventions for flight plan text files within X-Plane custom data paths.
- Estimated budget/duration benchmarks: Zero financial cost beyond the initial aircraft purchase; procedural execution requires approximately two to three minutes during the pre-flight cockpit setup phase.
Step-by-Step Procedure to Load a Company Route in the FF757
Step 1: Initialize the Flight Management System and Enter Route Identifiers
Begin the procedure once the aircraft is powered via external power or the auxiliary power unit (APU) and the Inertial Reference Systems are fully aligned. Navigate to the Captain or First Officer Control Display Unit (CDU) and press the RTE (Route) line select key to bring up the Route page. On this screen, locate the line select key designated for CO RTE, which stands for company route. Type the exact alphanumeric identifier of your saved flight plan using the scratchpad, ensuring it matches the naming convention required by your navigation data provider. For example, if your route connects Los Angeles International to San Francisco International, you might enter KLAXKSFO or a custom alphanumeric string corresponding to your saved text file.
Step 2: Push the Identifier to the CO RTE Field and Execute
Once the route name appears in the CDU scratchpad, press the line select key adjacent to the CO RTE prompt to transfer the string into the active field. You will notice the CDU fields populate with the origin and destination airports associated with that specific file. Review the generated route data carefully on the CDU screen, checking that the origin and destination match your current flight plan requirements. After verifying the basic airport pair, press the illuminated EXEC (Execute) key located at the bottom right of the CDU keypad to lock the route into active memory.
Pro-Tip: Always verify that your active AIRAC cycle in the simulator matches the AIRAC cycle used to generate the co route file. Mismatched database cycles are the primary cause of route discontinuity errors and missing waypoint identifiers in Boeing flight management systems.
Step 3: Load Associated Departure Procedures and Airways
With the base route successfully executed, return to the DEP/ARR (Departure and Arrival) index page by pressing the corresponding hard key on the CDU. Select your origin airport to view available standard instrument departures (SIDs) and runways. Choose the assigned runway and departure transition matching your clearance, then execute the changes. Next, return to the RTE page to inspect the route legs sequentially, utilizing the step tool to scan through every waypoint, airway entry, and terminal arrival procedure to ensure a continuous and logical flight path without manual routing gaps.
Mango Studios Flight Factor Boeing 757 Sound Pack - iniBuilds Store
Flight Factor 757 Navigation Data and Route Specifications
| Parameter | Specification / Standard | Operational Impact |
|---|---|---|
| File Format | Standard .rte format or plain text | Determines compatibility with the X-Plane Custom Data folder structure. |
| Directory Path | X-Plane Output / FMS plans | The designated storage location where the FF757 reads saved company routes. |
| Naming Convention | ICAO to ICAO (e.g., EGLLLFPG01) | Allows the FMC to quickly index and cross-reference flight plans. |
| Database Dependency | Navigraph or Aerosoft AIRAC | Must synchronize with the active simulation cycle to prevent waypoint load failures. |
Common Loading Failures and Field Fixes
- Root Cause: The flight plan file is placed in the incorrect directory within the X-Plane file structure.
- Actionable Fix: Ensure your saved .rte or flight plan text file is moved directly into the Output/FMS plans folder within your main X-Plane directory so the FF757 avionics can access it.
- Root Cause: Outdated navigation database cycles causing unrecognized waypoint errors during route execution.
- Actionable Fix: Update both your flight planning software export settings and your simulator navigation data to the exact same current AIRAC cycle to ensure complete waypoint compatibility.
- Root Cause: Syntax errors or invalid characters within a custom-created flight plan text file.
- Actionable Fix: Open the route file in a text editor, verify that all waypoint names and airport identifiers use valid uppercase ICAO formatting, and remove any stray spaces or unsupported symbols.
Frequently Asked Questions
Where should I save my co route files for the Flight Factor 757?
Company route files must be saved directly inside the Output/FMS plans folder located within your root X-Plane directory. The Flight Factor 757 avionics specifically query this directory when you enter a co route identifier into the CDU scratchpad.
Why does the CDU display a Not in Database error when loading a co route?
This error occurs when a waypoint, airway, or procedure within the saved route file does not exist in your currently active simulator navigation database. To resolve this, regenerate your flight plan using an export format that matches your installed AIRAC cycle.
Can I load SimBrief flight plans directly as co routes into the FF757?
Yes, you can download the X-Plane or generic flight plan format directly from the SimBrief dispatcher and place the resulting file into the Output/FMS plans folder. Once placed there, typing the designated route name into the CO RTE field on the CDU will load the complete flight plan.
Do I need to enter origin and destination airports before loading a co route?
No, loading a valid company route automatically populates the origin and destination fields on the CDU Route page. However, you must still verify these entries and execute them before proceeding to select runways, SIDs, and STARs.
What should I do if my route contains discontinuities after execution?
Route discontinuities are normal when transitioning from airways to terminal procedures or direct waypoints. Use the CDU line select keys to bridge the gap by copying the waypoint after the gap and placing it over the discontinuity, then press execute.
Master Your Flight Deck Operations Today
Enhance your virtual piloting precision by integrating automated route loading into every pre-flight checklist for your Flight Factor 757. Master advanced FMC procedures to reduce cockpit workload and achieve airline-standard realism on every journey.
