What is the normal Airbus A330 checklist flow?

The normal Airbus A330 checklist flow runs from cockpit preparation to securing: FMGS setup, before start, engine start, after start, taxi, before take-off, climb, cruise, descent, approach, landing, after landing and parking. Crews complete each cockpit flow first, then use the checklist to verify safety-critical items.

Within our Aviation & Real-World Flying library, we treat this as an operational overview rather than a substitute for approved documentation. Exact checklist names, calls and switch positions vary with the A330 model, engine installation, operator and simulator add-on.

Is the Airbus A330 checklist read-and-do?

Normally, no: Airbus line operations use a flow-and-check discipline for normal procedures. The pilot completes a familiar pattern across the panels, after which the checklist verifies selected items rather than directing every switch movement.

The pilot monitoring usually reads the challenge and the responsible pilot confirms the actual indication or control position. ECAM memos and system pages support this process, but they do not replace the normal checklist. The family logic closely resembles the method covered in our explanation of Airbus flow-and-check technique, although A330 systems and operator procedures must still be followed.

Airbus A330 normal checklist flow by phase

A complete A330 flow should follow the aircraft through these phases in order, with the checklist performed at the trigger specified by the operator or add-on manual.

1. Preliminary cockpit preparation. Review the aircraft status, establish electrical power in the approved order and check safety equipment, oxygen, emergency equipment and required documents. Confirm that landing-gear pins, covers and maintenance devices are accounted for, alongside the exterior inspection.
2. Cockpit preparation and FMGS setup. Scan the overhead, centre pedestal and instrument panels; start ADIRS alignment; and confirm the navigation database and aircraft status. Enter the route, alternate, cruise level, cost index, fuel and weight data, then calculate and independently cross-check take-off speeds, thrust settings and acceleration altitudes when the final figures are available.
3. Before start. Confirm the clearance, departure runway, take-off briefing and final load data. Check that doors and windows are closed, passengers and cargo are ready, fuel pumps and signs are configured, the beacon is on before engine movement, and the pushback or start arrangement is understood.
4. Engine start. Make the required pneumatic source available, normally the APU bleed or approved ground air, select the engine mode selector as specified and operate each ENG MASTER in the prescribed sequence. Monitor core rotation, EGT, fuel flow and oil pressure until each engine reaches stable idle. Do not switch packs manually unless the aircraft-specific procedure requires it; automation and add-on modelling differ.
5. After start. Return the engine mode selector to its normal position, configure the APU and bleeds as required, and verify generators, hydraulics and ECAM status. Set take-off flaps and pitch trim, check rudder trim, complete the flight-control check and confirm that no unexplained fault remains.
6. Taxi. Check the brakes at low speed, verify nose-wheel steering and compare the flight instruments during turns. Maintain a sterile cockpit while confirming the taxi route, take-off runway and any clearance change that affects the FMGS or performance calculation.
7. Before take-off. Reconfirm the runway, SID, initial altitude, take-off speeds and flap configuration. Verify that the cabin is ready, the flight-control check is complete and the ECAM take-off memo has no unresolved blue item, then run the T.O CONFIG test and resolve any warning rather than cancelling it.
8. Line-up and take-off. Configure exterior lights, weather radar, transponder and TCAS according to the clearance and operator procedure. Check the runway designation and heading against the instruments before applying take-off thrust.
9. After take-off and climb. Select the landing gear up after a positive climb, retract flaps and slats on the proper speed schedule, and move the thrust levers to the CL detent when prompted. Verify pressurisation, anti-ice, lights and ECAM status before completing the after-take-off check.
10. Cruise. Monitor fuel quantity and balance, navigation accuracy, weather, pressurisation and ECAM. Many operators use a cruise flow rather than a lengthy formal checklist, but destination data and fuel predictions should be reviewed well before descent.
11. Descent preparation. Load and verify the arrival, approach and missed approach; obtain landing performance; set minima and autobrake; and brief threats such as terrain, weather or a short runway. Our guide to programming and flying SIDs and STARs explains how constraints and clearances should be handled rather than blindly accepted from the FMGS.
12. Approach. Cross-check QNH, minima, approach aids, final course and go-around altitude. Activate the FMGS approach phase at the appropriate point if it has not activated automatically; doing this too early can command an unwanted reduction in managed speed. Configure progressively while respecting flap and landing-gear limits.
13. Landing. Confirm landing gear down, the required flap setting, ground spoilers armed, autobrake selected as needed and the cabin ready. Complete the landing checklist only after checking the indications, and go around if the approach does not meet the operator's stabilisation criteria.
14. After landing. Clear the runway before beginning the flow. Disarm the spoilers, retract the flaps, switch off the weather radar, configure the transponder, lights and anti-ice as required, and start the APU when it will be needed at the stand.
15. Parking and securing. Set the parking brake or confirm chocks, establish APU or external power where required, shut down the engines and switch off the fuel pumps. After the engines have stopped, configure the beacon, signs and remaining systems; for full securing, turn off the ADIRS and batteries last so power is not removed prematurely.

What changes between A330 variants and operators?

The overall sequence remains recognisable across the A330 family, but the detailed actions and checklist wording are not universal.

Why does an A330 checklist flow fail in the simulator?

Most failed A330 flows come from missing electrical or pneumatic prerequisites, unfinished ADIRS/FMGS work, or a generic checklist that does not match the aircraft being flown. Our cold-and-dark starting sequence covers the basic relationship between power, fuel, ignition and engine stabilisation.

• The starter does not turn: check for APU bleed or ground air, adequate pressure, the correct engine mode and an available electrical source. External electrical power alone does not provide pneumatic air.
• The engine rotates but does not light: verify the relevant fuel pumps, ENG MASTER and fuel state, then check whether the add-on models failures or ground-service restrictions.
• ADIRS or managed navigation is unavailable: confirm that alignment was started before moving the aircraft, the present position was entered correctly and the FMGS route has no unintended discontinuity.
• T.O CONFIG produces a warning: read the ECAM message and inspect the actual flap/slat setting, spoiler lever, trim, parking brake and other sensed items. Repeatedly pressing the test or clearing the warning does not make the aircraft correctly configured.
• Managed approach speed changes unexpectedly: check the arrival constraints, approach phase, destination pressure setting and entered landing data. Premature approach-phase activation is a frequent cause.
• The cockpit goes dark during shutdown: establish APU or external power before switching off the engines, then leave the batteries until the end of the securing flow.

Which A330 checklist should I use?

For real flying, use only the approved checklist and SOP for that aircraft and operator. In a simulator, choose the checklist that most closely matches the add-on's model, variant and engine rather than treating every A330 procedure as interchangeable.

• Add-on documentation: use this first when the aircraft models detailed electrical, pneumatic, hydraulic and FMGS logic.
• Built-in interactive checklist: prefer it when checklist completion is tied to the add-on's actual switch states.
• Generic phase checklist: use one for a simplified aircraft, but mark any unsupported or automated item instead of forcing an action copied from another model.

For a classic FSX implementation, our phase-by-phase A330-300 manual and checklist covers cold-and-dark preparation, start, taxi, take-off, cruise, approach, landing and securing. It is a simulator reference, not approved material for operating a real aircraft.