Learn what the iniBuilds A350 MCDU can print in MSFS 2024 and how to create a PDF or reusable .PLN flight plan.
The iniBuilds A350 in MSFS 2024 cannot export its active FMS route as a .PLN, PDF or Windows print job. A working PRINT command produces paper only on the simulated cockpit printer. For a reusable file or full operational flight plan, print or export from the planner that created the route.
Can the A350 MCDU export a flight-plan file?
No. There is no reverse-export function that reads the active iniBuilds A350 route and writes it to a file on your PC or console. The aircraft can receive route data from supported planning sources, but that connection is not a two-way file converter.
Strictly speaking, the A350 presents its FMS pages on the multifunction displays, operated through the keyboard and cursor-control hardware, rather than through a conventional Airbus MCDU. Simmers still search for “A350 MCDU”, but instructions written for an A320-style unit often lead to the wrong controls.
If the route came from SimBrief, retrieve the same operational flight plan from its original dispatch entry and print or save that document. Our guide to transferring a SimBrief plan through the MSFS 2024 EFB explains the relationship between the source plan, the EFB and the aircraft FMS.
How do I print the flight plan inside the A350?
The A350 can print only to its simulated cockpit printer, and only where the installed aircraft build provides an active print command for that page or report.
- Finish and insert the route. Clear unintended discontinuities and ensure any temporary flight-plan revision has been inserted into the active plan.
- Open the FMS flight-plan or report page. Use the relevant multifunction display and the A350’s keyboard or cursor controls.
- Select PRINT or PRINT F-PLN if offered. The exact prompt depends on the displayed report and the functions implemented in the installed aircraft version.
- Collect the simulated output. The paper appears at the cockpit printer; it is not sent to a physical printer and is not saved as a PDF.
If no flight-plan print prompt appears, or the prompt does nothing with the aircraft powered and the route active, that report is not available in that aircraft build. There is no hidden MSFS keyboard command that converts it into a Windows print job. Also, a PRINT key on an ATSU or AOC message prints that message, not necessarily the complete route.
How can I create a PDF or reusable .PLN file?
Create the file in the planning tool before transferring the route to the aircraft. Choose the method according to what you need:
| Required output | Best method | What it contains |
|---|---|---|
| Paper copy or PDF | Print the original operational flight plan through the browser or planning application | Route plus any generated fuel, weather and dispatch information |
| MSFS-compatible route file | Save or export from the original route planner | Route data, normally without a full dispatch briefing |
| Plan made with the MSFS EFB | Keep and manage it in the EFB or World Map workflow | The simulator-side plan used for transfer to supported avionics |
| Route built only in the A350 | Recreate it manually in a planner | No direct FMS export is available |
For an EFB-created route, follow our explanation of the MSFS flight-planning and aircraft-transfer workflow. If you need a simulator-compatible file, Little Navmap can create and export flight plans, but exporting a generic route file does not automatically programme every part of the A350 FMS.
Why does the printed plan differ from the active route?
A printed report can differ when it was generated before a runway, SID, STAR or en-route revision was inserted. Print only after the active route is final, and check for temporary revisions and flight-plan discontinuities first.
An operational flight plan may also retain the route originally dispatched by the planner while the aircraft contains later changes made by the crew. Different navigation-data cycles can alter waypoint, airway or procedure availability as well. A mistake we see constantly is treating the dispatch document and the live FMS route as if they must remain identical after departure; use the FMS as the authority for what the aircraft will actually fly.