Custom Flight Management System

This page outlines features and issues provided by the initial integration of our custom FMS. Please also make ensure you have read the special notes section.

Features

We will always list the latest updates in the following section. As we improve our custom flight management system older versions will be listed in a collapsible format in the Older Versions section.

Latest - Version 1.5

We have introduced new features to the custom flight management system as part of a minor update. Please see the list below:

• LNAV Updates
• Holding Patterns
• Turn direction constraints on non-TF legs
• Overfly restriction support
• ARINC424 Leg Types
  • AF, CA, CI, CR, CF, DF, HF, HM, HA legs (See List of Leg Types)
• Turn Prediction Types
  • Path capture
  • Course capture
  • Direct to fix turn
  • Holding pattern entry turn
• Navigation Display
• Removed flight plan loading from localStorage
• Corrected active waypoint ETA display
• Added EfisVectors systems with optimized transmit task queue + support for future display of OFFSET, SECONDARY, SECONDARY DASHED, MISSED APPROACH, ALTERNATE and EOSID flight paths.

Older Versions

Guides and Information

• MCDU Fix Info
• Flight Plan Discontinuities

Known Issues

• CA leg terminations are sometimes in the wrong place, and does not adapt to V/S.
• Some path captures will be incorrectly drawn. This will not affect guidance.
• INTCPT calculation can be off on large distances.
• Course captures do not adapt to PPOS when nextLeg is active. This can cause the final path to be off to the side.
• WX on ND are not implemented yet. We are waiting for better API support by Microsoft Flight Simulator. See our Forums Feature Request.
• Rendering of flight path on the ND of terminal procedure legs may be glitched or incorrect during cruise. - See Special Notes.
• Rendering of flight path on the ND of legs will be glitched or incorrect if you are flying faster than the appropriate/correct speed. - See Special Notes.
• Syncing the aircraft flight plan with the sim's flight plan for default ATC and VFR map is not 100% supported. - See Special Notes.
• Defining both FROM/TO in the world map shows in the FROM/TO INIT A page but does not populate the airport list in our METAR (AOC) integration.
• DIRECT-TO: Turning point is not correctly implemented yet.
• ETA in F-PLN A on the MCDU may not be 100% accurate.
• Flight plan frozen on loading in (Please post the specific route on which this occurs and under what circumstances, i.e. spawning in c&d using the MSFS flight planner, or simBrief, or loading in .PLN generated by simBrief or other external program).
• Fuel calculations might be incorrect.
• Route on VFR map will not match up with what is shown on the ND.

Special Notes

Our custom FMS provides better accuracy and features over the default offering in MSFS which results in issues syncing the flight plan from the MCDU back into the simulator. Flight plans with complex routing may have significant issues if synced backwards or loaded externally through MSFS's simplified flight planning.

This will always be problematic unless Asobo improves the built-in flight planner. Other aircraft with complex flight planning capabilities also have this limitation.

The options below allow you to use to utilize the built-in MSFS ATC and VFR Map:

• Sync the MCDU flight plan to MSFS ATC -> After pressing "Fly"
• Load the same flight plan in the World Planner and the MCDU -> Before pressing "Fly"

When using either method will allow for the following:

• IFR clearance access through the MSFS ATC
• Although these methods allow you to use MSFS ATC with our custom FMS throughout the flight it does not fix the MSFS ATC system.
  • Do not expect MSFS ATC to be aware of altitude constraints in SIDs and STARs.
  • Do not expect MSFS ATC to provide descent clearance at the proper time.
• Usage of the VFR map

Sync the MCDU flight plan to MSFS ATC

If you choose to use our built-in simBrief import on the MCDU to bypass the world menu planner (as we recommend), we have provided a feature that helps sync the aircraft's flight plan back to the MSFS' built-in flight planner. This feature can be configured on the EFB and is set to None by default.

Using this method MSFS ATC will most likely not detect your planned cruising flight level. You would need to request further climb once established on your initial cleared altitude after takeoff.

Load the same flight plan in the World Planner and the MCDU

You can also use the same flight plan in both the MSFS World Planner and the MCDU to have MSFS ATC be aware of your flight plan. This can be done in two different ways:

Both options are described in more detail below.

We recommend the flyPad flight plan sync feature is set to None before attempting this. This would allow MSFS to follow your flight plan independently of our custom FMS. While the order you switch the sync feature to None may vary it is still important that the sync feature is set appropriately and done before you load any flight plan into the MCDU.

Importing a 3rd party flight plan

You can attempt to load any saved .pln file from 3rd party flight planners (i.e. simBrief) into the world map flight planner. This would populate the world menu with the following:

• FROM/TO
• Routing
• SID + STAR

Follow these steps:

1. Create a flight plan from simBrief or another 3rd party flight planner.
   1. When using simBrief please ensure you generate an OFP for the same flight plan you will use for your flight.
2. Download and save the fight plan for FS2020 in the .pln format to your PC.
3. Load the .pln file in the MSFS world map.
4. Make sure to select a starting gate and destination approach from the world map's drop down menus.
5. Load your flight.
6. Use our built-in simBrief integration to populate the MCDU with your flight plan.
7. Reminder: This is done by using the INIT REQ. line on the INIT A MCDU page which will download the generated OFP from simBrief to provide an accurate flight plan with our custom FMS while having MSFS ATC support.

Using the World Planner to generate a flight plan

You can also use the World Planner to generate a flight plan and then enter that same flight plan manually in the F-PLN page in the MCDU.

Follow these steps:

1. In the World Planner, select a departure airport, a departure gate or runway and a destination airport.
2. Select "IFR" (low or high altitude planning) from the planning dropdown.
3. Select a Departure (SID), an Arrival (STAR) and an Approach.
4. Take note of the route the World Planner generates for you. You need each individual waypoint noted down.
5. Load your flight.
6. In the INIT A page of the MCDU, enter the FROM/TO airports. An example is shown in our Beginners Guide section on the INIT A page.
7. In the F-PLN page of the MCDU, enter your flight plan as it was generated by the World Planner, starting with the SID, the regular waypoints and finally the STAR. An example is shown in our Beginners Guide section on the Flight Plan.

WX/TER

It is important to note that the weather radar is not available yet with the latest version of our cFMS(v1.5). Our current focus is to deliver a more realistic flight planning and navigation experience while maintaining performance and reliability. However, we are not satisfied with how the default code performs together with our custom systems.

We believe the benefits that cFMS provides outweigh the temporary lack of WX functionality. Weather will still prove to be a challenge due to the lack of a native SDK API. We have posted about it on the MSFS forums, where it currently sits at the top of the wishlist and Asobo are investigating how to best improve their API.

Read more about weather and terrain API. Please note again that terrain radar is being tested in our Experimental version.

Flight Path Rendering

In certain instances some legs may not render correctly with our current implementation and may look strange in PLAN mode or while en-route. In most cases the A32NX will attempt to fly the route and you won't experience any major issues.

Additionally, some flight plans may have extraneous waypoints that can lead to wrongly drawn flight paths. While this can be an edge case, going through your flight plan in PLAN mode you can find offending waypoints that need to be removed which will provide a much more reasonable drawn flight path.