WEIGHT, BALANCE AND THE LAST-MINUTE LOAD REVISION
Treat loading as a developing aircraft state until it has been reconciled with the final information. A preliminary loadsheet can be appropriate to an earlier stage and still be unsuitable for final takeoff preparation. Check sector, date, registration and edition before using its figures. Distinguish zero-fuel mass, block fuel, taxi fuel and takeoff mass: each answers a different question about what is aboard or expected to be consumed. A correct total does not establish a correct distribution. The centre of gravity and trim entry must also belong to the accepted load. [93, PDF pp. 1–4] [66, PDF pp. 123–128]
Airbus's weight-and-balance discussion explains why CG errors affect more than a line on a sheet. An excessively aft loading condition can reduce nosewheel loading and directional control, particularly at low aircraft mass and on a slippery surface; it also changes rotation behaviour and tailstrike risk. The operational lesson is to check the distribution and trim assumptions even when the mass appears comfortably below a structural maximum. A generous mass margin cannot make an incorrect CG acceptable. [124, Takeoff: nosewheel controllability, aft CG and rotation consequences]
After a load revision, close the loop across actual aircraft mass, accepted ZFW/ZFWCG, fuel, trim and takeoff performance. Inspect the received values in their labelled fields rather than applying a memorised field order from another FM standard. If a performance-relevant input changes, repeat the affected calculation and verify the resulting speeds, thrust request and configuration. The aircraft, the tablet and the MCDU should now describe one departure. Keep the revision identifiable so a later message does not accidentally return the preparation to an older edition. [93, PDF p. 4] [66, PDF pp. 123–128]
The developer's 24–25 October 2026 V3 snapshot states that mass-and-balance Send to MCDU transfers live aircraft weights and trim rather than loadsheet values. Preserve that date when using the finding. A discrepancy should prompt a comparison of actual loading, sheet edition and accepted entries before it is labelled a calculation fault. The snapshot does not establish that every subsequent build behaves identically. For a repeatable test, record the load before transfer, the particular transfer performed and the receiving fields afterwards, then compare that observation with the build-specific information. [83]
Use a deliberate last-minute-change exercise after a normal sector has become familiar. At the stand, make one documented passenger, cargo or fuel revision, then identify every preparation item it affects. Predict which figures should change before using the transfer. Preserve the before/after loadsheets and calculation results, and explain why each surviving entry remains valid. This author-proposed exercise tests the dependency chain without introducing an invented operational limit. Repeat it in a different family member only after confirming that its loading and performance model matches the aircraft selected. [93, PDF pp. 1–4] [106, Official profiles by aircraft variant and configuration]