Learn how to use an Airbus A320 checklist in Microsoft Flight Simulator, choose the right version, follow phase triggers and fix unticked items.
Use an Airbus A320 checklist in Microsoft Flight Simulator as a verification tool: complete the cockpit flow from memory or a procedure guide, then read each checklist item and confirm the aircraft state. Run the checklist at its named flight-phase trigger, stop on any failed item, correct it, and only then continue.
Which A320 checklist should I use?
Use a checklist written for the exact A320 variant and add-on you are flying. Microsoft Flight Simulator 2020 and 2024 do not have one universal A320 implementation; cockpit functions and checklist integration can differ between the original A320neo, later simulator variants and third-party aircraft.
The aircraft developer's checklist should take precedence where switch names or procedures conflict. A generic list remains useful for learning the sequence, and our phase-by-phase A320 normal checklist sequence shows how the checks fit together from cockpit preparation to securing the aircraft.
| Checklist format | Best use | Main limitation |
|---|---|---|
| Built-in MSFS Checklist panel | Guided learning and supported default aircraft | May not recognise custom-coded add-on systems |
| Aircraft EFB checklist | Detailed operation of that specific add-on | Must match the installed aircraft version |
| PDF or printed checklist | Flow-and-check operation on a second screen or paper | Requires manual verification |
If the aircraft provides a built-in checklist, open it through the simulator's in-flight panel system or the aircraft's electronic flight bag. The location and available assistance vary by simulator version, platform and aircraft. Our comparison of built-in, EFB and PDF checklist tools explains when each format works best.
How do I work through the checklist correctly?
- Load the intended aircraft state. Decide whether the flight begins cold and dark, powered at the gate, engines running or ready for take-off. Start with the checklist section that matches that state.
- Complete the cockpit flow. Scan the panels in a consistent order and configure the aircraft for the next phase. A checklist verifies selected critical actions; it is not a list of every switch you must touch.
- Open the relevant checklist. Read the item and its expected response, then look at the actual switch, annunciation, display or lever detent. In single-pilot simulation, saying both parts aloud helps prevent silent assumptions.
- Correct discrepancies immediately. Do not tick an item because you intend to complete it later. Set the control, check that the commanded system responds, then mark the item complete.
- Finish before the workload rises. Complete the before-take-off checks before entering the runway and the landing checks before the final approach becomes demanding. Avoid prolonged head-down checklist work while taxiing or on an active runway.
Airbus cockpit logic deserves care: an unlit pushbutton does not necessarily mean that a system is off. Many controls are dark in their normal automatic state, so verify the labelled mode and associated system indication rather than judging the light alone.
When should each A320 checklist be completed?
Each checklist is tied to a trigger, not merely a convenient moment. Use these practical triggers unless the checklist supplied with your aircraft specifies a different sequence.
| Checklist phase | When to run it | Typical items verified |
|---|---|---|
| Cockpit preparation | After electrical power is established | Power source, ADIRS, fuel and payload, MCDU setup and initial panel configuration |
| Before start | Doors closed and pushback or start clearance obtained | Doors, beacon, fuel pumps, parking brake and pushback readiness |
| After start | Both engines are stable and pushback is ending | APU as required, engine mode, anti-ice, flight controls, trim, flaps and spoilers |
| Before take-off | At the holding point, before runway entry | Take-off configuration, cabin status, transponder and exterior lights |
| After take-off or climb | Once safely airborne and during clean-up | Landing gear, flap retraction, lights and altimeter change at the transition altitude |
| Approach | Before intercepting the final approach | Briefing, weather, landing data, minima, altimeters and autobrake |
| Landing | Established on final before the stabilisation gate | Landing gear, flaps, speedbrake arming, cabin readiness and landing memo |
| After landing | After clearing the active runway | Lights, flaps, spoilers, transponder and APU as required |
| Parking and secure | At the stand with the aircraft restrained | Engines, fuel pumps, beacon, electrical supply and batteries last |
Do not copy flight-specific values from somebody else's checklist. V-speeds, flap setting, stabiliser trim, fuel, minima and runway data must come from the flight you have prepared. Missing take-off data often becomes apparent during the before-start or before-take-off checks; our A320 route and performance entry procedure covers the MCDU work behind those items.
The checklist also does not explain what to do between its triggers. For departure, automation, descent and approach technique, use the complete A320 flight workflow from setup to shutdown alongside the checklist.
Why will an A320 checklist item not complete?
An unticked item usually means the expected aircraft state has not been detected, or the checklist was designed for a different A320 implementation. Check the cockpit indication first rather than repeatedly toggling a correctly positioned control.
- The lever is between detents. Thrust levers, flaps and speedbrakes may look approximately correct while the simulator still reads another position.
- A prerequisite is missing. An engine, electrical or pneumatic item may require another system to be stable before its condition becomes valid.
- The aircraft uses custom systems. Some add-ons do not report every switch state to the standard MSFS Checklist panel. Confirm the condition using the aircraft's displays and mark it manually if the add-on permits.
- Assistance changed a control. AI piloting, automatic checklist completion and other assistance options can reverse a deliberate setting without making the reason obvious.
- The wrong checklist is loaded. Similar A320 variants can have different engine, avionics and EFB procedures even though the cockpit layout appears familiar.
Automatic completion is useful for locating an unfamiliar control, but it can move switches and mask the procedure you are trying to learn. With a ready-to-fly or engines-running start, skip completed preparation sections and verify the aircraft from the appropriate phase; do not run the cold-and-dark list backwards and disturb an already configured cockpit.