Learn to use the iniBuilds A350 checklist in MSFS, from cold-and-dark preparation through take-off, approach, landing and shutdown.
Use the iniBuilds Airbus A350 checklist in Microsoft Flight Simulator as a verification tool: complete the cockpit flow for the flight phase, open the matching checklist, confirm each item against the actual switch position, display or ECAM memo, and advance only when every item is satisfied. It does not replace the full aircraft procedure.
Use flows first and the checklist second
Airbus normal operations are based on completing a cockpit flow and then using the checklist to catch omissions. A mistake we see constantly is treating each checklist line as an instruction to begin configuring that system.
| Tool | Purpose |
|---|---|
| Cockpit flow | Configure the aircraft in an efficient, repeatable order. |
| Normal checklist | Verify the safety-critical results of that flow. |
| ECAM and aircraft indications | Show the actual system state, warnings, memos and abnormal procedures. |
Use an A350-specific checklist that matches the installed aircraft build. Aircraft-supplied documentation is preferable to an old generic Airbus list because system modelling and checklist automation can change after an update. Our comparison of built-in, PDF and printed checklist formats explains when each format works best.
How do I run the iniBuilds A350 checklist?
- Load a known aircraft state. Decide whether the flight begins cold and dark, in a turnaround state or ready for departure. The opening checklist phase must match that state; otherwise, several items may already be completed or appear out of sequence.
- Open the matching checklist source. If your installed A350 build provides an electronic checklist through an aircraft display or tablet, use that. Where an A350-specific list appears in the MSFS Checklist panel, it can also be used, but panel placement and assistance features differ between simulator editions and updates.
- Complete the cockpit flow. Set up electrical power, aircraft systems, loading, the flight plan and performance data before reading the corresponding checklist. For a powered-down aircraft, follow the complete A350 cold-and-dark start sequence alongside the checklist rather than expecting the checklist to teach the whole procedure.
- Read and verify every item. For a switch item, look at the actual switch and its indication. For an FMS item, inspect the relevant page rather than assuming imported data are correct. For an ECAM item, confirm the displayed memo or system status.
- Handle sensed and non-sensed items correctly. An electronic checklist may complete sensed items automatically when the aircraft reaches the required state. Items the simulation cannot monitor must be confirmed manually, but only after checking them.
- Advance at the correct trigger. Close a phase only when its items are complete, then continue the flight. Do not tick every future phase at the gate; that removes the checklist's value when the configuration changes later.
Route, departure, take-off-speed and performance checks belong in the preflight flow. If those terms are unfamiliar, use our guide to setting up an airliner FMC in MSFS before attempting to clear the associated checklist items.
When should I use each A350 checklist phase?
Run each checklist at its operational trigger, not merely when its title looks relevant. Exact phase names and any split sections can vary with the checklist revision.
| Typical phase | When to run it |
|---|---|
| Cockpit preparation | At the stand while establishing power and setting up the aircraft. |
| Before start | After loading, route and performance preparation are complete, before engine start or pushback. |
| After start | Once both engines are stable and before taxi. |
| Before take-off | Near the holding point. If the list is split, complete its final section only at the stated trigger. |
| After take-off or climb | After the gear is up and the aircraft has reached the required clean configuration. |
| Descent and approach | Prepare before top of descent, then verify the approach configuration as the arrival progresses. |
| Landing | When established and configured for landing, before the checklist's stated cut-off point. |
| After landing and parking | Run the first after clearing the runway and the second once stopped at the stand. |
Why will an A350 checklist item not complete?
An open item usually means the aircraft has not reached the required state, the item is not automatically sensed, or the native MSFS checklist cannot read that custom A350 system.
- Non-sensed item: inspect it and mark it manually. Do not wait indefinitely for an automatic tick that the simulation does not support.
- Hardware binding conflict: a throttle, flap, spoiler or switch assignment may repeatedly overwrite the cockpit position. Move the physical control, remove duplicate bindings or add a suitable dead zone.
- Incomplete aircraft set-up: entering payload, fuel or performance figures is not always the same as applying or confirming them. Check that the aircraft displays accepted the data.
- Wrong starting state: a turnaround preset may leave systems configured differently from a cold-and-dark checklist.
- Checklist version mismatch: use the documentation delivered with the installed aircraft version rather than forcing an older list to fit.
- MSFS assistance limitation: automatic completion can operate or confirm the wrong control when custom systems are involved. Verify the cockpit indication afterwards instead of trusting the tick alone.
What should I do if ECAM disagrees with the checklist?
The aircraft indication takes priority over a manually ticked checklist box. Stop, find the configuration error and clear the warning before continuing; ticking an item never changes the underlying switch, FMS entry or system state.
For an abnormal condition, follow the modelled ECAM procedure before returning to the interrupted normal checklist. A take-off configuration warning means the aircraft is not ready to depart, even if the before-take-off list appears complete.
During approach, verify the selected procedure, navigation source, displayed ILS data and approach mode rather than ticking “approach” items from memory. If the localiser or glideslope still fails to capture, follow our iniBuilds A350 ILS troubleshooting checks.