How to create and load an iniBuilds A330 plan in MSFS 2024?

In Microsoft Flight Simulator 2024, create the route in the simulator EFB or SimBrief, then transfer or import it to the iniBuilds A330 and verify every leg in the MCDU. Add any missing runway and procedures, resolve only genuine discontinuities, and complete INIT, fuel, weight and PERF data before departure.

What is the quickest way to load an A330 flight plan?

The simplest method is to build the route in the MSFS 2024 EFB and send it to the aircraft's avionics. The simulator-wide EFB and the A330's own tablet are separate interfaces, so seeing a route on a tablet does not prove that the FMGS has accepted it.

1. Power the aircraft and MCDUs. Wait for the avionics to finish starting. You can enter a route before the inertial reference system has aligned, although the normal navigation display will not be ready until alignment progresses.
2. Create the route in the MSFS 2024 EFB. Enter the departure and destination ICAO codes, choose an IFR route and set a suitable cruise altitude. Add the runway, SID, STAR and approach only when the expected weather or runway is known. Our full EFB planning and aircraft-transfer sequence covers the simulator controls in more detail.
3. Calculate and inspect the route. Check for obvious detours, repeated fixes and inappropriate low-level legs before using the EFB command that sends the plan to the avionics.
4. Check the MCDU INIT page. Confirm the departure and destination, then enter or verify the flight number, cost index and cruise level. These operational entries may remain blank even when the route itself transfers correctly.
5. Open the F-PLN page. Confirm that the departure, en-route fixes and destination appear in the correct order. If the page contains only the two airports, the detailed route has not loaded.
6. Add missing procedures. Select the departure runway and SID from the origin, then the STAR and approach from the destination. Do not select them again if they already arrived with the imported route, or duplicate fixes may be created.
7. Resolve discontinuities carefully. Use CLR against a discontinuity only when the legs on either side should connect directly. A manual or vector segment may be intentional and should instead be replaced when ATC or the procedure provides the next leg.
8. Review the route in PLAN mode. Step through every waypoint on the navigation display. Look for loops, sharp turns, duplicated procedures and a route that doubles back towards the previous fix.
9. Complete INIT B and PERF. Enter the weight, centre of gravity, block fuel and take-off performance data before departure. Route loading does not fill all of these fields.
10. File with ATC separately. Send the final plan to the simulator's ATC system after the route and runway choices are settled.

Which planning method should I use?

Use the MSFS EFB for speed, SimBrief for dispatch-style planning, or direct MCDU entry when importing fails or the route is short.

For SimBrief, generate the plan for the appropriate A330 configuration, import the latest operational flight plan through the supported EFB or aircraft-tablet route source, and then transfer it to the avionics. Follow our SimBrief creation and MSFS import workflow if the account linking or import stage is unfamiliar.

A mistake we see constantly is importing from one source, manually editing the MCDU, and then sending the original route again. That final transfer can replace the corrected route. Pick one primary source and make subsequent changes in the MCDU.

How do I enter the route manually in the A330 MCDU?

Manual entry starts on INIT A and continues through the F-PLN page, using lateral revisions for runways, procedures and airways.

1. On INIT A, enter the origin and destination as an ICAO pair in the FROM/TO field, followed by the flight number, cost index and cruise level.
2. On F-PLN, select the departure airport and choose the runway, SID and transition. Review the temporary flight plan before inserting it.
3. Select the relevant fix and use the AIRWAYS or lateral-revision page to enter each airway with its exit waypoint. Add direct fixes individually where required.
4. Select the destination and choose the expected STAR, approach and transition. It is reasonable to leave the arrival open until the runway becomes clear.
5. Insert the temporary plan, remove only unwanted discontinuities and inspect the complete route in PLAN mode.

Our Airbus MCDU route-entry procedure explains airway entry, temporary plans and discontinuity handling in greater depth.

Why does the flight plan not appear in the A330 MCDU?

A missing route usually means it was created but not transferred, the avionics were not ready, or the planner and aircraft navigation databases disagree.

• The plan exists only in the EFB: use the separate avionics-transfer command. Saving, calculating or viewing a route does not load it into the FMGS.
• The plan was filed only with ATC: ATC filing and avionics transfer are separate operations in MSFS 2024.
• The MCDUs were still starting: wait until the cockpit avionics are ready, clear the incomplete route and transfer it once more.
• Two route sources were mixed: clear the unwanted plan before importing from another source. Repeated transfers can produce duplicated procedures or restore an earlier route.
• The MCDU reports NOT IN DATABASE: the waypoint, airway or procedure may not exist in the A330's active navigation data. Check the identifier and choose the correct duplicate waypoint; if the planning data differs, enter an available equivalent route.
• The runway or SID/STAR is absent: many imports provide the en-route section but deliberately leave runway-dependent procedures for the pilot to select.
• The route is in the MCDU but not visible on the display: check the F-PLN page first. If the legs are present, investigate inertial alignment, navigation-display mode and range rather than importing the route again.

What must be entered after the flight plan loads?

A loaded route is only the lateral path; the A330 still needs weight, fuel and performance data. Complete INIT B before engine start where possible, because Airbus logic may restrict access to that page after an engine is running.

Enter zero-fuel weight and centre of gravity, block fuel, take-off flap and trim settings, V-speeds, thrust-reduction and acceleration altitudes, and any calculated thrust setting. Our guide to entering A330 fuel, weight and centre of gravity correctly covers the INIT B entries without repeating them here.

Does loading the route also file it with MSFS ATC?

No. Loading the flight plan into the iniBuilds A330 prepares the aircraft's FMGS, while filing it tells the simulator's ATC system which route to expect. Perform both actions, and file only after the route is final so ATC and the MCDU do not follow different versions.