Weight and balance records read against the continuing-airworthiness source file

When this review is needed

• Cabin reconfigurations, galley changes, or equipment swaps have accumulated since the last reweigh and the amendment trail is thin.
• The fleet reweigh interval in the operator's program is coming due and the CAMO wants the paper position settled first.
• A transition inbound aircraft arrived with a weight and balance statement whose amendment history stops years short of its modification history.
• Dispatch or performance engineering has queried figures that no one can trace to a signed amendment.

The problem

Weight and balance drifts by omission. Nobody decides to let the statement go stale; a seat change here and an antenna installation there each seemed too small to trigger an amendment, or the amendment was computed but never filed into the statement's history. The CAMO file records all of those events, which makes it the one place the drift can be measured, yet the statement and the file are almost never read together until an auditor does it first.

What gets reviewed

• The current weight and balance statement, its amendment chain, and the last physical weighing report
• Modification and STC lines from the CAMO file screened for weight and moment effect
• Equipment installations, removals, and swaps recorded in status reports and work summaries
• Interior configuration changes, including seating, galleys, and emergency equipment relocations
• Amendment arithmetic re-derived where the file provides the underlying change data
• Alignment between the statement's effectivity and the operator's reweigh policy

What gets validated

• Every weight-affecting event in the CAMO file maps to an amendment, a recomputation, or a documented below-threshold judgment
• Amendment entries chain back to the last weighing without gaps or unexplained restatements of basic weight
• The weighing report on file names this aircraft, this configuration, and a date consistent with the statement it anchors
• Moment arms and stations used in amendments match the type data referenced in the file
• The statement in operational use is the same revision the CAMO file holds as current

Evidence normally required

• Current weight and balance statement with its full amendment history
• The most recent weighing report and any prior ones held in the file
• CAMO status reports, modification status, and open-item log for the period since the last weighing
• Interior configuration records, including LOPA revisions where applicable
• The operator's reweigh policy or program reference

Common discrepancies

• A cluster of small equipment changes, each individually below the amendment threshold, that together shift basic weight materially
• An amendment computed and signed but applied to a superseded statement revision, so the current one is silently wrong
• A weighing report inherited at transition that describes a different interior configuration than the aircraft now carries
• Ballast changes recorded in work summaries with no trace in the weight and balance history

What is at stake

Operating against a statement the file contradicts exposes the operator on two fronts at once. Performance and loading calculations inherit an error nobody can size, and the airworthiness review or a ramp-level audit can convert the discrepancy into a finding that grounds the schedule while a reweigh is arranged at the least convenient time available.

How the work runs

What the buyer receives

• An exception list of weight-affecting events without supporting amendments, dated and sourced
• A reconciled amendment chain from the last weighing to the present, with breaks marked
• A recommendation on whether the paper position can be repaired or a reweigh is the honest answer

Who uses the output

• The continuing-airworthiness manager deciding whether to amend, recompute, or schedule a weighing
• Performance and dispatch engineers who need to know how much trust the current figures deserve
• Records staff filing the repaired amendment chain into the source file

How the work fits into the transaction or program

This check leans on the modification status review that usually precedes it: once the embodied-change picture is trusted, weight effects can be screened from it mechanically. Downstream, its exceptions inform the equipment-list review and give the airworthiness review a settled weight position instead of an open argument.

Jurisdiction-specific considerations

For US-registered aircraft the obligation flows through 14 CFR 43 and the operator's own program, with the current empty weight and center of gravity treated as required records under 91.417. EASA operators work under Regulation 1321/2014, where the continuing-airworthiness management organization must be able to show the statement's currency at each airworthiness review, and many national authorities add fixed reweigh intervals on top. Transitions between the two regimes are where amendment conventions diverge and errors hide.

Regulatory limits

The review measures the gap between the statement and the file. It does not perform weighings, issue amendments, approve loading systems, or make any airworthiness determination. Corrective action and its approval remain with the operator and the responsible authority.

What this review does not cover

• Physical weighing of the aircraft or supervision of a weighing event
• Recalculation of operational loading or performance data
• Design judgment on whether a given change required approved data

Specific to this review

• Amendment thresholds create a ratchet problem: many changes are individually ignorable, and no routine process sums them until a reweigh reveals the accumulated drift.
• The weighing report is the anchor document, and it is also the document most often lost at lease transition because it lives outside the logbook set.
• Statements maintained in two formats, an operator system and a paper master, diverge more often than either goes wrong alone.
• A reweigh ordered under audit pressure typically costs a maintenance slot; the same reweigh planned from an exception list costs a quiet night shift.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits