Lesson Overview

Welcome to Module 7 of the Flight Sim Mastery Academy.

This module focuses on the iniBuilds Airbus A300-600R, a classic wide-body airliner that combines older Airbus cockpit design with an advanced Flight Management System and automated flight guidance.

Unlike the modern A350, the A300 requires more manual management. Its cockpit contains:

• Conventional analogue-style system controls.
• Electronic flight displays.
• A dual Flight Management System.
• Traditional autopilot controls.
• Manual overhead-panel preparation.
• Older-generation Airbus automation.
• Passenger and freighter configurations.
• General Electric and Pratt & Whitney engine options, depending on the installed package.

The standard A300 product was originally developed for MSFS 2020 and has a compatible MSFS 2024 version. iniBuilds also offers a separate Premium MSFS 2024 edition that takes advantage of newer simulator features and is distinct from the compatible version.  

This lesson will teach students how to:

• Install the correct A300 version.
• Understand the MSFS 2020, compatible 2024 and Premium 2024 editions.
• Configure the EFB.
• Connect SimBrief and Navigraph.
• Calibrate controls.
• Load passengers, cargo and fuel.
• Prepare the aircraft from cold and dark.
• Program the FMS.
• Start the engines.
• Use the autopilot, LNAV and VNAV.
• Complete climb, cruise, descent and approach.
• Land and shut down.
• Test the aircraft for performance, loading, memory and add-on conflicts.

This is a practical normal-operations course. It does not replace the complete iniBuilds manuals or teach every abnormal and emergency procedure.

Lesson Objectives

By the end of this module, students will be able to:

Install iniManager and the correct A300 edition.

Distinguish the MSFS 2020, MSFS 2024 Compatible and MSFS 2024 Premium versions.

Install updates and liveries.

Select the correct passenger or freighter aircraft.

Select the correct GE or Pratt & Whitney configuration.

Create a matching SimBrief airframe.

Connect SimBrief and Navigraph.

Configure the EFB and aircraft options.

Calibrate throttle, rudder and tiller controls.

Load fuel and payload correctly.

Prepare the aircraft from cold and dark.

Program a basic FMS route.

Calculate take-off performance.

Complete engine start, taxi and take-off.

Use LNAV, VNAV and conventional autopilot modes.

Manage climb, cruise and fuel.

Prepare and fly an ILS approach.

Land, taxi in and shut down.

Test performance and diagnose conflicts.

STEP 1 – INSTALLATION

Installing the iniBuilds A300-600R

1. Choose the Correct Simulator Edition

Before purchasing or installing the aircraft, confirm which simulator you use.

The available A300 options can include:

MSFS 2020 Edition

Designed for Microsoft Flight Simulator 2020.

The standard MSFS 2020 product can also operate in MSFS 2024 through its compatible version, but it does not contain all the additional features of the native Premium edition.  

MSFS 2024 Compatible Edition

This is the updated standard A300 package made compatible with MSFS 2024.

It is based on the original product and does not include every enhancement created specifically for the Premium edition.

MSFS 2024 Premium Edition

This is the dedicated native MSFS 2024 version.

iniBuilds describes it as a separate edition designed to make greater use of MSFS 2024 technology, with improvements to areas such as the flight model, interactions, visual effects and other native features.  

Do not:

• Install both the Compatible and Premium versions together unless iniBuilds explicitly supports this.
• Copy the 2020 folder manually into MSFS 2024.
• Mix Premium liveries with an incompatible aircraft version.
• Assume a tutorial recorded using one version applies perfectly to every edition.

Record:

Simulator:

A300 edition:

Passenger or freighter:

Engine type:

2. Create an iniBuilds Account

Create or sign into your official iniBuilds account.

Use the same account for:

• Purchasing the aircraft.
• Accessing iniManager.
• Installing the aircraft.
• Downloading liveries.
• Receiving updates.
• Accessing support.

Make sure the aircraft appears in the account’s owned-product list before attempting installation.

3. Install iniManager V2

iniManager is the official product-management application for iniBuilds aircraft and scenery.

It provides one-click installation and automatically identifies available product updates.  

Installation Procedure

1. Close Microsoft Flight Simulator.
2. Download iniManager V2 from the official iniBuilds website.
3. Run the installer.
4. Sign into the iniBuilds account used for the purchase.
5. Open the application settings.
6. Allow iniManager to detect your simulators.
7. Confirm the MSFS 2020 Community Folder if installed.
8. Confirm the MSFS 2024 Community Folder if installed.
9. Correct any incorrect path before continuing.
10. Save the configuration.

Students with both simulators installed must confirm the selected simulator at the top of iniManager before every installation.

4. Install the Aircraft

Inside iniManager:

1. Select MSFS 2020 or MSFS 2024.
2. Open the aircraft-product section.
3. Locate the A300-600R.
4. Confirm the correct edition.
5. Select Install.
6. Confirm the destination folder.
7. Allow the download to complete.
8. Do not launch MSFS during installation.
9. Confirm the product appears as installed.
10. Record the version number.

The aircraft package may contain:

• Passenger version.
• Freighter version.
• GE-powered configuration.
• Pratt & Whitney-powered configuration.
• Additional liveries or optional content.

Availability can differ between product editions.

5. Passenger vs Freighter

The A300 may be used as either:

Passenger Aircraft

Configured for airline passenger operations.

It contains:

• Passenger cabin.
• Passenger loading.
• Baggage and cargo holds.
• Airline passenger liveries.

Freighter Aircraft

Configured for cargo operations.

It may include:

• Main-deck cargo.
• Cargo-door controls.
• Different loading configuration.
• Cargo-specific liveries.
• Different Zero Fuel Weight and centre-of-gravity behaviour.

Use the correct SimBrief airframe for the exact configuration.

Do not create a passenger flight profile and load it into a freighter without reviewing the aircraft weights and payload distribution.

6. Engine Variants

The A300 may be available with:

• General Electric engines.
• Pratt & Whitney engines.

The selected engine type affects:

• Engine indications.
• Fuel burn.
• Thrust.
• Take-off performance.
• Engine-start behaviour.
• SimBrief calculations.
• Aircraft handling.

Use a matching SimBrief airframe.

Do not use a GE airframe for a Pratt & Whitney aircraft.

7. Updating the Aircraft

Aircraft updates are installed through iniManager.

At the time of writing, iniBuilds continues to issue updates for the MSFS 2024 Premium A300, including systems, performance, visual, usability and audio improvements.  

Update Procedure

1. Close MSFS.
2. Open iniManager.
3. Select the correct simulator.
4. Select the A300.
5. Review the update notice.
6. Read the changelog.
7. Install the update.
8. Confirm the version.
9. Restart iniManager where required.
10. Complete a short test flight.

Do not install an update immediately before a long-haul or VATSIM flight without testing it first.

8. Installing Liveries

Use liveries made specifically for:

• The iniBuilds A300.
• Passenger or freighter version.
• Correct engine type.
• Correct simulator.
• Correct Compatible or Premium edition where relevant.

Installation Procedure

1. Open the livery section in iniManager.
2. Select the A300.
3. Choose the correct simulator.
4. Select the desired airline.
5. Confirm the aircraft type.
6. Select Install.
7. Wait for the download.
8. Launch MSFS.
9. Select the aircraft.
10. Inspect the livery.

Avoid:

• Duplicate versions.
• Liveries made for older simulator products.
• Passenger liveries installed on the freighter.
• Old manual installations left beside iniManager versions.

Begin testing with the default iniBuilds livery.

9. Create the Correct SimBrief Airframe

Choose the aircraft type:

A306 – Airbus A300-600

Then select or create an airframe matching:

• Passenger or freighter.
• GE or Pratt & Whitney engines.
• Registration.
• Operating Empty Weight.
• Maximum Zero Fuel Weight.
• Maximum Take-off Weight.
• Fuel capacity.
• Passenger or cargo configuration.
• Fuel-burn factor.

Using an incorrect profile can lead to:

• Too little fuel.
• Excessive fuel.
• Incorrect payload.
• Incorrect landing weight.
• Incorrect take-off performance.

10. Navigation Data

Compare the AIRAC cycle shown in:

• SimBrief.
• The A300 FMS.
• Navigraph.
• The simulator.

A mismatch may cause:

• Missing SIDs.
• Missing STARs.
• Missing runways.
• Invalid waypoints.
• Airways not found.
• Different approach procedures.

Navigation-data conflicts have previously been associated with missing procedures in A300 FMS reports, so testing the aircraft and Navigraph data together is important.  

11. Navigraph Integration

Where supported by the installed edition:

1. Open Navigraph Hub.
2. Select the correct simulator.
3. Locate the supported A300 navigation package.
4. Install or update it.
5. Start the aircraft.
6. Open the FMS IDENT page.
7. Compare the navigation cycle with SimBrief.
8. Confirm procedures appear.

If procedures disappear after an update, test:

• The default simulator navigation data.
• Navigraph data installed.
• Navigraph data removed.
• The latest aircraft version.

Change only one variable at a time.

12. Community Folder Management

After installation:

1. Record the core aircraft package.
2. Record all livery folders.
3. Check for an older manually installed A300.
4. Remove obsolete packages.
5. Keep MSFS 2020 and 2024 content separate.
6. Do not rename core folders.
7. Avoid activating Compatible and Premium editions together.
8. Create a clean A300 troubleshooting profile.

A clean profile should contain:

• Core A300 package.
• One default livery.
• Required navigation package.
• No premium airports.
• No traffic injector.
• No GSX.
• No external camera or sound utilities.

13. First Installation Test

Load:

• A default airport.
• A large parking stand.
• Clear Skies.
• Daylight.
• Default A300 livery.
• No traffic.
• No GSX.

Confirm:

• The aircraft appears.
• The cockpit loads.
• The EFB works.
• The displays initialise.
• Switches respond.
• The aircraft remains stable.
• No CTD or WASM error occurs.

Allow the aircraft time to initialise before operating switches.

STEP 2 – CONFIGURATION AND FLYING

Part A – EFB and Aircraft Setup

14. Configure the EFB

The A300 EFB is used for:

• Aircraft configuration.
• SimBrief import.
• Fuel.
• Payload.
• Ground services.
• Performance calculations.
• Doors.
• Aircraft state.
• Sound and realism options.
• Checklists.
• Maintenance or failures.

Review:

• Units.
• SimBrief Pilot ID.
• Aircraft variant.
• Engine type.
• Fuel-loading method.
• Payload-loading method.
• Ground services.
• Display or performance settings.

15. Select the Correct Units

Use either:

• Kilograms.
• Pounds.

Keep the same units in:

• SimBrief.
• EFB.
• FMS.
• Fuel page.
• Payload page.
• Take-off calculator.

A mismatch can produce major fuel and weight errors.

16. Aircraft State

Select:

Cold and Dark

Best for learning the full preparation.

Turnaround

Useful for shorter preparation.

Ready for Take-off

Useful for testing but unsuitable for learning normal procedures.

Use Cold and Dark for this lesson.

17. Configure Controls

Check:

• Pitch.
• Roll.
• Rudder.
• Throttle 1.
• Throttle 2.
• Brakes.
• Parking brake.
• Spoilers.
• Flaps.
• Nose-wheel steering.
• Reverse thrust.

Remove duplicate assignments.

Test every physical controller before beginning aircraft preparation.

18. Throttle Calibration

Depending on the current aircraft version, use either the aircraft’s EFB calibration or MSFS control settings.

Confirm:

• Both engines reach idle.
• Both engines reach maximum thrust.
• Reverse thrust works.
• No lever jumps.
• No unintended reverse activation.
• Engine 1 and Engine 2 move symmetrically.

Unlike a modern Airbus with CL and FLEX detents, the A300’s throttle management and autothrottle interface reflect its older design. Do not assume Fenix or FlyByWire calibration procedures apply directly.

19. Rudder and Tiller

The A300 is a large wide-body aircraft.

Configure:

• Rudder pedals for yaw.
• Tiller for larger taxi turns.
• Brake axes.
• Suitable sensitivity.

Test on an empty taxiway.

Remember:

• The cockpit is ahead of the nose gear.
• The main gear cuts inside the cockpit path.
• Tight turns require careful positioning.
• Excessive speed makes steering difficult.

20. Payload and Fuel

After generating the SimBrief plan:

1. Open the EFB.
2. Retrieve the latest flight.
3. Confirm passenger or freighter type.
4. Confirm engine type.
5. Review block fuel.
6. Review payload.
7. Load passengers or cargo.
8. Load fuel.
9. Confirm Zero Fuel Weight.
10. Confirm centre of gravity.
11. Confirm Take-off Weight.
12. Compare with SimBrief.

Do not use the EFB, MSFS Weight and Balance and GSX independently at the same time.

21. SimBrief Import

1. Generate the OFP.
2. Enter the SimBrief username or Pilot ID.
3. Open the EFB flight-planning page.
4. Retrieve the latest flight.
5. Confirm the aircraft type.
6. Confirm the origin.
7. Confirm the destination.
8. Review fuel and payload.
9. Import the route into the FMS.
10. Verify every route section.

A successful download does not prove the route is valid.

Part B – Cold and Dark Preparation

22. Establish Electrical Power

At the stand:

1. Set the parking brake.
2. Confirm throttles are idle.
3. Confirm fuel levers are shut off.
4. Turn the batteries on.
5. Connect external power through the EFB.
6. Confirm external power is available.
7. Select external power on.
8. Check electrical indications.
9. Set cockpit lighting.

The A300 overhead requires a more traditional manual flow than newer Airbus aircraft.

23. Navigation Alignment

1. Configure the inertial-navigation selectors.
2. Set them to the required navigation or alignment position.
3. Open the FMS position page.
4. Enter the reference airport.
5. Confirm the gate or GPS position.
6. Insert the aircraft position.
7. Allow alignment to finish.
8. Confirm the displays show valid navigation data.

Do not begin taxi before alignment is complete.

24. Overhead Preparation

Complete a logical overhead scan.

Check:

• Electrical system.
• Batteries.
• External power.
• Fuel pumps.
• Hydraulic pumps.
• Pneumatic and bleed-air system.
• Air-conditioning packs.
• Pressurisation.
• Window heat.
• Probe heat.
• Emergency lighting.
• Passenger signs.
• Anti-collision light.
• APU.

The exact configuration depends on:

• Engine type.
• Passenger or freighter version.
• Ground-power availability.
• Weather.
• Airline procedure.

25. Start the APU

Before pushback:

1. Confirm sufficient fuel.
2. Start the APU according to the overhead procedure.
3. Monitor APU indications.
4. Confirm electrical power is available.
5. Select the APU generator.
6. Confirm pneumatic air is available.
7. Configure the bleed system.
8. Disconnect external power when ready.

Part C – FMS Programming

26. IDENT and Position Pages

On the FMS:

1. Open the IDENT page.
2. Confirm aircraft model.
3. Confirm engine type.
4. Check the AIRAC cycle.
5. Open the position-initialisation page.
6. Enter the reference airport.
7. Confirm aircraft position.
8. Complete navigation alignment.

27. Route Programming

Enter or import:

• Origin.
• Destination.
• Flight number.
• Company route where available.
• Runway.
• Airways.
• Waypoints.

After import:

1. Step through the route.
2. Confirm every airway.
3. Check every waypoint.
4. Identify discontinuities.
5. Review manual or vector segments.
6. Check route distance.
7. Compare with SimBrief and Navigraph.
8. Activate and execute the route.

Do not delete discontinuities without understanding why they exist.

28. SID and STAR Selection

For departure:

1. Select the runway.
2. Select the SID.
3. Select the transition.
4. Insert it.
5. Check the first active waypoint.

For arrival:

1. Select the runway.
2. Select the STAR.
3. Select the transition.
4. Select the approach.
5. Check altitude restrictions.
6. Check speed restrictions.
7. Review the missed approach.

29. Performance Initialisation

Enter or confirm:

• Zero Fuel Weight.
• Reserves.
• Cost Index.
• Cruise altitude.
• Cruise temperature.
• Take-off weight.
• Centre of gravity.

The exact page structure differs from modern Airbus aircraft.

Use the SimBrief OFP and EFB values as references.

30. Take-off Performance

Use the EFB calculator where available.

Enter:

• Runway.
• Wind.
• Temperature.
• Pressure.
• Runway condition.
• Take-off weight.
• Flap setting.
• Anti-ice configuration.
• Bleed or pack configuration.
• Engine type.

Calculate:

• V1.
• VR.
• V2.
• Take-off thrust.
• Flap setting.
• Trim.
• Acceleration altitude.

Do not reuse speeds from an earlier flight.

31. Configure the Autopilot Panel

Set:

• Initial altitude.
• Initial heading where required.
• Speed.
• Flight directors.
• Autothrottle mode.
• LNAV or NAV mode where appropriate.
• VNAV or profile mode where appropriate.

The A300 uses an older automation philosophy than the A350 or A320neo.

Students must monitor the Flight Mode Annunciator after every selection.

Part D – Pushback and Engine Start

32. Before Pushback

Confirm:

• Fuel and payload loaded.
• Doors closed.
• Flight plan complete.
• Take-off data entered.
• APU available.
• Beacon on.
• Fuel pumps configured.
• Hydraulic system configured.
• Pneumatic system prepared.
• Ground equipment removed.
• Pushback clearance received.

33. Engine Start

The exact sequence may vary between GE and Pratt & Whitney configurations.

A general sequence is:

1. Select the appropriate engine-start mode.
2. Start the first engine.
3. Confirm engine rotation.
4. Introduce fuel at the correct point.
5. Monitor EGT.
6. Monitor oil pressure.
7. Monitor N1 and N2.
8. Confirm the engine stabilises.
9. Start the second engine.
10. Repeat the monitoring process.
11. Confirm both generators are online.

Never introduce fuel when there is no engine rotation.

34. After-Start Flow

After both engines stabilise:

• Generators confirmed.
• APU bleed off.
• APU shut down when no longer required.
• Hydraulic pumps configured.
• Engine bleeds configured.
• Packs configured.
• Probe heat on.
• Flaps set.
• Spoilers armed.
• Trim set.
• Flight controls checked.
• Taxi lights on.

Part E – Taxi and Take-off

35. Taxi

Release the parking brake and apply only enough thrust to begin moving.

During taxi:

• Maintain a controlled speed.
• Brake before tight turns.
• Use the tiller gently.
• Monitor the wing clearance.
• Check flight instruments.
• Check brakes.
• Complete the take-off checklist.

Freighter configurations may have different weights and handling characteristics from passenger versions.

36. Before Take-off

Confirm:

• Flaps set.
• Trim set.
• Spoilers armed.
• Autobrake configured.
• V-speeds displayed.
• Take-off thrust confirmed.
• Flight directors on.
• Initial altitude set.
• Departure route checked.
• Landing lights on.
• Strobes on.
• Checklist complete.

37. Take-off

1. Align with the runway.
2. Stabilise engine thrust.
3. Apply take-off thrust or engage the supported autothrottle take-off function.
4. Confirm thrust is symmetrical.
5. Maintain centreline.
6. At V1, continue unless a serious emergency requires rejection.
7. Rotate smoothly at VR.
8. Follow the flight director.
9. Select gear up after positive climb.
10. Monitor acceleration and flap retraction.

Avoid an aggressive rotation because of the aircraft’s length and tail-strike risk.

Part F – Climb and Cruise

38. LNAV and VNAV

LNAV controls lateral navigation along the FMS route.

VNAV or profile guidance manages vertical flight according to:

• Route.
• Speed schedule.
• Altitude restrictions.
• Aircraft weight.
• Performance data.

Before relying on automation:

• Confirm the route is active.
• Check the active waypoint.
• Confirm the correct lateral mode.
• Confirm the correct vertical mode.
• Monitor the Flight Mode Annunciator.

39. Climb

During climb:

1. Retract flaps according to the speed schedule.
2. Reduce to climb thrust.
3. Engage the autopilot when safely established.
4. Monitor speed.
5. Follow ATC altitude clearances.
6. Check engine indications.
7. Check pressurisation.
8. Monitor fuel.
9. Confirm the route.

Do not allow VNAV to climb through an uncleared altitude.

40. Cruise

At cruise:

• Confirm level-off.
• Check engine parameters.
• Compare fuel with SimBrief.
• Monitor pressurisation.
• Check aircraft weight.
• Review weather.
• Review destination.
• Prepare the arrival.
• Check the alternate.
• Monitor systems.

The A300 is suitable for medium- and long-haul operations, so fuel monitoring remains important.

Part G – Descent and Approach

41. Descent Planning

Before top of descent:

1. Confirm arrival runway.
2. Select the STAR.
3. Select the approach.
4. Review altitude restrictions.
5. Review speed restrictions.
6. Enter destination weather.
7. Set approach minimums.
8. Calculate landing performance.
9. Review landing weight.
10. Brief the missed approach.

42. Beginning Descent

1. Set the cleared lower altitude.
2. Confirm the route is valid.
3. Engage the required vertical mode.
4. Monitor the descent path.
5. Monitor speed.
6. Use speedbrakes only where required.
7. Follow ATC instructions.
8. Verify every mode change.

Older automation may require more pilot intervention than newer Airbus aircraft.

43. ILS Approach

1. Confirm runway and approach.
2. Tune or verify the ILS.
3. Confirm the identifier.
4. Set the final approach course.
5. Intercept from a suitable heading.
6. Arm the approach mode.
7. Monitor localiser capture.
8. Monitor glideslope capture.
9. Extend flaps progressively.
10. Lower the gear.
11. Select landing flaps.
12. Complete the landing checklist.

44. RNAV or Non-Precision Approach

For an RNAV or non-precision approach:

• Verify the procedure.
• Check navigation accuracy.
• Review minima.
• Confirm lateral guidance.
• Confirm vertical guidance if available.
• Monitor altitude carefully.
• Be prepared to use selected modes.
• Review the missed approach.

Do not expect every approach to have the same level of automation as a modern A350.

Part H – Landing and Shutdown

45. Manual Landing

1. Disconnect the autopilot at a comfortable height.
2. Maintain stable speed.
3. Keep the aircraft aligned.
4. Make small control inputs.
5. Begin the flare at the appropriate height.
6. Reduce thrust.
7. Touch down on the main gear.
8. Lower the nose.
9. Deploy reverse thrust.
10. Monitor autobrake or apply manual braking.
11. Reduce reverse thrust as speed falls.

46. After Landing

After leaving the runway:

• Flaps retract.
• Spoilers disarm.
• Landing lights off.
• Strobes off.
• Taxi lights on.
• Weather radar off.
• Transponder configured.
• APU started where required.
• After-landing checklist completed.

47. Shutdown

At the stand:

1. Set parking brake.
2. Connect external power or establish APU power.
3. Confirm electrical power.
4. Move fuel levers to shutoff.
5. Monitor engine shutdown.
6. Turn beacon off.
7. Turn fuel pumps off.
8. Configure hydraulics.
9. Configure pneumatic systems.
10. Open doors when safe.
11. Complete the parking checklist.

For full securing:

• Navigation systems off.
• Emergency lights off where appropriate.
• External power disconnected.
• Batteries off.

STEP 3 – PERFORMANCE AND COMPATIBILITY TESTING

Testing the iniBuilds A300

48. Establish a Controlled Benchmark

Use the same:

• Airport.
• Parking stand.
• Weather.
• Time.
• Traffic.
• Graphics settings.
• Camera view.

Compare the A300 with:

• A simple default aircraft.
• The iniBuilds A350.
• Another complex wide-body.

Record:

• Loading time.
• Average FPS.
• 1% lows.
• Frame times.
• MainThread status.
• GPU utilisation.
• RAM usage.
• VRAM usage.
• Temperatures.

49. Compatible vs Premium Performance

For MSFS 2024 users who have access to both editions, test: