How do I start the Fenix A320 from cold and dark in MSFS?

To start the Fenix A320 from cold and dark in Microsoft Flight Simulator, switch on BAT 1 and BAT 2, use external power if available, set all three ADIRS to NAV, switch on the fuel pumps, then start the APU and select APU BLEED. Select IGN/START and start engine 2 followed by engine 1.

Prepare the Fenix A320 for a cold-and-dark start

Load the aircraft at a parking stand rather than on a runway, then select the cold-and-dark aircraft state in the Fenix controls if it did not load that way. Allow the state to finish loading before moving switches; saved or turnaround states can leave systems partly powered.

Set the parking brake, confirm both thrust levers are at idle, and check that both engine master switches are off. If the overhead layout is unfamiliar, our panel guide to the A320 overhead, ECAM and MCDU identifies the controls used below.

A generic MSFS 2020 auto-start command is not a dependable substitute for this flow. Duplicate hardware bindings for engine masters, fuel controls or starter functions can also override the cockpit switches.

Fenix A320 cold and dark startup: the reliable sequence

1. Switch on both batteries. Press BAT 1 and BAT 2. Battery power wakes the essential systems, but it is not intended for a long cockpit setup.
2. Connect external power if available. Wait for the EXT PWR pushbutton to show AVAIL, then select it so that it indicates ON. If no GPU is connected, continue using the batteries and start the APU.
3. Set all three ADIRS selectors to NAV. Begin alignment early and complete any position-initialisation prompt shown by the MCDU. Keep the aircraft stationary while a full alignment is taking place.
4. Configure the fuel pumps. Switch on the wing tank pumps and set the centre tank pumps according to the loaded fuel and normal checklist. Confirm that fuel is actually present; pump switches cannot supply an empty aircraft.
5. Start the APU. Select APU MASTER, wait briefly for the intake flap sequence, then press APU START. Do not continue until the APU indicates AVAIL.
6. Select APU bleed. Turn on APU BLEED to provide pneumatic pressure for engine cranking. Leave X BLEED at AUTO, the pack pushbuttons in their normal on configuration, and the generator pushbuttons in their normal on state.
7. Use the alignment period for cockpit setup. Enter the route, departure, arrival and performance data while the ADIRS align. Our walkthrough for entering an A320 route and performance data covers that separate task without interrupting the startup flow.
8. Prepare the area for engine start. Finish boarding and fuelling, close the doors, remove ground equipment as required, and switch on the beacon. If a tug is connected, follow its parking-brake instructions rather than fighting the pushback with the brakes.
9. Select IGN/START. Move the engine mode selector from NORM to IGN/START. This arms the normal start logic.
10. Start engine 2. Move ENG MASTER 2 to ON. Monitor N2 rotation, fuel flow, EGT rise and oil pressure, then wait for a stable idle before starting the other engine.
11. Start engine 1. Move ENG MASTER 1 to ON and monitor the same indications. Engine 2 followed by engine 1 is the conventional sequence, particularly during pushback, although the aircraft can start either engine first when all required conditions are present.
12. Return the mode selector to NORM. Once both engines are stable, move the engine mode selector back to NORM. Do not leave it in IGN/START for taxi.

Minimum working flow

The memory flow is batteries, electrical power, ADIRS, fuel pumps, APU, APU bleed, beacon, IGN/START, engine 2, engine 1, NORM. It is useful for recall, but it does not replace the ECAM checks or the aircraft’s normal before-start and after-start checklists.

Why won’t the Fenix A320 start?

A failed start usually means that electrical power, pneumatic pressure, fuel or a start command is missing. Read the engine indications rather than moving unrelated switches.

If the whole aircraft remains unresponsive despite a correct state and power setup, restart the aircraft session and check the required Fenix components rather than repeatedly cycling the switches. Our broader Fenix A320 fault checks cover installation, loading and control-conflict problems.

Do I need external power or only the APU?

External power is optional, but the APU is the normal source of bleed air for a self-contained engine start.

• Use external power for a longer cockpit setup at the stand. It supplies electricity without running the APU.
• Use the APU alone when no GPU is available. The batteries can initiate the APU start, after which the APU supplies electrical and pneumatic power.
• Use both in sequence by completing the setup on external power, starting the APU before pushback, confirming APU AVAIL and APU BLEED ON, then disconnecting the GPU.

External electrical power by itself does not crank the engines. Unless you are deliberately simulating a separate ground-air start, establish APU bleed before selecting an engine master.

Must the ADIRS finish aligning before engine start?

No; the engines can be started while the ADIRS are still aligning, but the aircraft should not depart until alignment is complete.

An incomplete alignment can leave the navigation display without a valid map position and make flight guidance or autopilot behaviour appear faulty. Alignment duration depends on the simulation setting, and a full alignment may also require the aircraft position to be initialised through the MCDU.

How should I use GSX Pro with the Fenix A320?

GSX Pro handles ground services and pushback in MSFS; it does not replace the Fenix A320 cockpit startup.

1. Request services before engine start. Complete boarding, catering and fuelling while the aircraft is on external power or battery/APU power.
2. Select the GPU in the cockpit. A GSX ground unit beside the aircraft does nothing electrically until EXT PWR AVAIL appears and the Fenix pushbutton is selected.
3. Avoid competing door commands. Let either the Fenix controls or GSX manage a door at a given moment rather than repeatedly changing it in both systems.
4. Start the APU before the GPU is removed. Confirm APU AVAIL and APU BLEED ON before pushback or engine start.
5. Close doors and clear equipment before beacon on. Remove chocks when instructed and follow GSX parking-brake prompts during tug connection and pushback.
6. Start when the area is clear. During a normal push, select IGN/START, start engine 2, wait for stable idle, then start engine 1. A stand or airport procedure may require delaying one or both starts.

The two common Fenix–GSX mistakes are treating a connected GPU as already selected and leaving ground services active while attempting pushback. Resolve the ground-service state first; random cockpit switching will not clear a tug, door or equipment conflict.

After-start flow before taxi

Once both engines are stable, return the aircraft to its normal taxi configuration before releasing the parking brake.

• Set the engine mode selector to NORM.
• Switch off APU BLEED, confirm the packs return to normal operation, then shut down the APU when it is no longer required.
• Set engine anti-ice as conditions require.
• Arm the ground spoilers and set take-off flaps, rudder trim and pitch trim.
• Complete the flight-control check and review the ECAM memo and status indications.
• Confirm the flight plan, take-off data, barometric setting, transponder and taxi lights.
• Ensure the tug, chocks and ground equipment are clear before taxiing.

For the sequence from taxi preparation through take-off and flight, continue with our step-by-step A320 flying procedure in Microsoft Flight Simulator.