Set up the Wilco 777 FMC in FSX: initialise position, enter and verify the route, add performance data, and fix LNAV or discontinuity problems.
To set up the Wilco 777 FMC in FSX, power the aircraft and align its inertial-reference system, initialise the CDU position, enter the origin, destination and route, select departure and arrival procedures, complete performance and take-off data, then activate and execute the route. Verify every waypoint before using LNAV or VNAV.
The keypad and display in the cockpit are the CDU; the FMC is the computer it controls. Wilco 777 editions vary slightly in page layout and route-import support, but they follow the same Boeing programming sequence.
What must be ready before programming the FMC?
The aircraft needs electrical power, functioning Wilco gauges and a valid present position before the FMC can guide it correctly. From a cold-and-dark state, establish external or APU power and place the aircraft's inertial-reference system in its normal alignment mode.
If the CDU remains blank after the cockpit is powered, reload the Wilco aircraft and check the add-on installation. That is a panel or gauge-loading problem, not an incomplete flight plan.
How to programme the Wilco 777 CDU step by step
Enter the route in the order below because later pages depend on the position, route and weight data entered earlier. Our standard Boeing FMC programming sequence explains the purpose of each page if the Wilco labels are unfamiliar.
- Initialise the position. Open the initialization or reference index, then select
POS INIT. Enter the departure airport's ICAO code as the reference airport and copy the displayed present or GPS position into the IRS position field. Wait for alignment if the Wilco aircraft state models it. - Enter the route endpoints. Open the
RTEpage and enter the four-letter origin and destination codes. Add the flight number if wanted. Entering the runway here is optional in some releases because it can also be selected throughDEP/ARR. - Build the en-route section. On subsequent route pages, enter an airway in the
VIAcolumn and its exit fix inTO. For a direct segment, enter the next waypoint without an airway. If an airway is rejected, enter its constituent fixes individually. - Select the procedures. Use
DEP/ARRto choose the departure runway and SID, followed by the arrival, transition and approach. Check that the runway agrees with the route and FSX weather. Changing it later can replace legs and create new discontinuities. - Inspect the LEGS page. Read the waypoint sequence from top to bottom and compare it with the intended route. Check for duplicate fixes, unexpected turns and
ROUTE DISCONTINUITYmessages before executing anything. - Complete PERF INIT. Enter the zero-fuel weight or gross weight requested by the page, fuel reserves, cost index and cruise altitude. A mistake we see constantly is entering gross weight in the zero-fuel-weight field. Accept automatically supplied values only after checking them.
- Complete take-off data. Review
THRUST LIMandTAKEOFF REF, then enter the flap setting and CG where requested. Confirm or insert V1, VR and V2 and set the indicated stabiliser trim in the cockpit. Leave assumed-temperature or derated thrust at its normal setting unless you understand the calculation. - Activate and execute. Select
ACTIVATEif it is displayed and pressEXECwhenever its light illuminates. A route still markedMODhas not been committed. Recheck the LEGS page and navigation display after execution. - Set the MCP. Enter the initial cleared altitude on the mode control panel and configure the flight directors and autothrottle. The FMC route does not set the MCP altitude for you. Arm LNAV or VNAV only after their required route and performance data are valid.
Can the Wilco 777 FMC load an FSX flight plan?
Loading a route into the FSX Flight Planner does not automatically transfer it to the Wilco FMC. FSX ATC, the default GPS and the add-on FMC can hold separate versions of the same flight.
You can use the FSX flight planner to create and save the route, then enter and verify its waypoints manually in the CDU. Some Wilco releases include a company-route or import function, but the accepted format and storage location vary; follow the documentation installed with that particular edition rather than assuming it accepts every FSX .PLN file.
The Wilco navigation database may also contain older waypoint, airway, SID or STAR identifiers than the planner expects. An expired database indication does not necessarily disable the FMC, but NOT IN DATABASE means that identifier is unavailable. Use a procedure recognised by the installed database or enter compatible fixes individually.
Why will LNAV or VNAV not work?
LNAV and VNAV usually fail because the route is not active, a discontinuity blocks it, or required performance data is missing.
| Symptom | Likely cause | What to check |
|---|---|---|
| CDU is blank | No aircraft power or Wilco gauges did not load | Establish electrical power; if other powered instruments work, reload or repair the add-on. |
INVALID ENTRY or NOT IN DATABASE | Incorrect format or a database mismatch | Check the ICAO code, waypoint spelling and the procedures available within the CDU. |
| EXEC light remains on | The modified route has not been committed | Review the change and press EXEC. |
| LNAV will not engage | Inactive route, unsuitable intercept or broken active leg | Confirm an active route, a sensible first leg and no unresolved gap ahead. |
| VNAV will not engage | Incomplete performance data or MCP setup | Check weight, cost index, cruise altitude, take-off data and selected MCP altitude. |
| Aircraft flies towards the wrong place | Incorrect IRS position or wrong active waypoint | Compare present position with the departure airport and inspect the first active leg. |
| FSX ATC gives different routing | FSX and the Wilco FMC contain different plans | Use matching routes or expect to amend the FMC when ATC issues vectors or direct clearances. |
How do I remove a route discontinuity?
Close a discontinuity only when the fixes on either side should connect directly. On the LEGS page, copy the first required waypoint below the gap into the scratchpad, place it over the discontinuity line and press EXEC.
Do not remove a vectors leg blindly. It represents an expected heading or ATC-vector segment; when cleared direct, select the required downstream waypoint, place it into the active-leg position and execute the change. Inspect the resulting track on the navigation display before allowing LNAV to follow it.