Skip to content

Weight and balance

Weight and balance records traced through the modification baseline

Every modification that adds, removes, or relocates mass should leave a mark on the weight and balance record, and this review checks that it did. Starting from the last physical weighing, it walks the amendment chain forward against the modification history in the source package, confirming that each weight-affecting change produced a supported amendment and that the current statement is the sum of what the documents show. It is performed during a configuration baseline, by records specialists working for the configuration manager. Findings land in an amendment-chain exception list that joins the configuration support package.

When this review is needed

  • Cabin reconfigurations or connectivity installations were embodied and the current statement predates some of them.
  • The amendment history jumps between formats from different operators and the chain from the last weighing is unclear.
  • A counterparty has asked for weighing evidence and the file holds only computed statements.
  • Equipment-change paperwork shows removals the weight and balance record never picked up.

The problem

Weight and balance records fail by omission. The mod gets embodied, the aircraft flies, and the amendment that should have followed sits in someone's queue until it is forgotten. Across a few operators the statement becomes a number with a pedigree nobody can recite: the last weighing is a decade back, amendments exist for some changes and are absent for others, and the equipment-change record contradicts the amendment log. Reconstructing the chain means matching every weight-relevant mod to a specific amendment, one document at a time.

What gets reviewed

  • The most recent physical weighing report and its raw data
  • The full amendment chain from that weighing to the current statement
  • Weight-affecting modifications in the source package, each matched to an amendment or logged as unmatched
  • Equipment-change records reconciled against amendment content
  • Moment and center-of-gravity calculations spot-recomputed on the larger amendments
  • Format transitions between operators, checked for dropped or re-based amendments

Scope this review

Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.

Send a representative, redacted record set and we will scope the review.

What gets validated

  • The current statement equals the last weighing plus the documented amendment chain, within rounding
  • Each modification flagged as weight-affecting in the source package has a corresponding amendment
  • Amendment source data traces to the modification record, kit weight sheet, or removal documentation cited
  • Equipment-change entries and amendment entries tell the same story over the same date range
  • No amendment relies on an estimated weight where the modification data provides an actual figure

Evidence normally required

  • Weighing reports with raw scale data where available
  • The amendment log and all individual amendment records
  • The modification status report and kit weight data from the source package
  • Equipment-change records for the same period
  • The current weight and balance statement in operational use

Common discrepancies

  • A galley or seating change embodied years ago with no amendment anywhere in the chain
  • Amendments computed from estimated weights when the mod kit documentation states actuals
  • An operator transition where the new format silently re-based the statement without a weighing
  • Removal of equipment recorded in maintenance documents while the statement still carries its weight

What is at stake

A statement that cannot be traced from a weighing through complete amendments is an assertion, and both operational load control and any downstream buyer treat it as one. The usual remedy is a fresh weighing, which costs downtime, and if the discovered discrepancy is large it raises questions about the period flown on the wrong figures.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Fix the anchor

Identify the last physical weighing with usable raw data and set it as the chain's starting point.

02

Match changes to amendments

Pair every weight-affecting modification and equipment change with its amendment, logging each unmatched item.

03

Recompute the spine

Rebuild the running totals along the chain and compare the end state to the current statement.

04

Report the pedigree

Deliver the reconstruction, exceptions, and a reasoned view on statement supportability.

What the buyer receives

  • An amendment-chain reconstruction from the last weighing to the current statement
  • An exception list of weight-affecting changes lacking amendment support
  • A recommendation on whether the chain supports the statement or a reweigh is the cleaner path

Who uses the output

  • Configuration managers deciding whether the baseline can carry the current statement
  • Operations engineering staff responsible for load-control data integrity
  • Asset and transition teams anticipating counterparty questions on weighing currency

How the work fits into the transaction or program

Weight and balance findings depend directly on the modification-status strand: only after the embodied-mod list is verified can weight-affecting changes be identified with confidence. In turn, unmatched equipment removals discovered here feed back into the equipment-list strand, so the two reviews usually exchange interim results before either closes.

Jurisdiction-specific considerations

The FAA side treats weight and balance data as part of the maintenance record chain under 14 CFR 91.417, with amendment practice following the approved flight manual and operator procedures, while EASA operators manage revision and periodic reweigh expectations through their continuing-airworthiness arrangements under Regulation 1321/2014. Aircraft moving between the systems often need the amendment chain re-expressed in the receiving operator's format, and that translation is a known place where amendments vanish.

Regulatory limits

The review reconciles documents; it does not weigh the aircraft, approve or amend the weight and balance statement, or make any determination about load-control compliance. Where the chain cannot support the statement, the finding says so and stops there.

What this review does not cover

  • Performing or arranging a physical weighing
  • Issuing revised weight and balance statements or amendments
  • Load-control or performance engineering analysis

Specific to this review

  • Amendment chains break most often at operator transitions, because the receiving operator re-bases the statement in its own format and the audit trail to the weighing stays behind.
  • Estimated weights in amendments are a quiet accuracy leak; a chain of small estimates can drift far enough that the next weighing produces an awkward surprise.
  • Equipment-change records are the best independent witness for this review because they are maintained by a different process than the amendment log.
  • A missing amendment for a removal overstates weight, which looks conservative but still invalidates the statement's pedigree just as surely as an understatement.

Sources

Frequently asked questions

If the chain has gaps, is a reweigh always required?

Not always. Small gaps with recoverable modification weight data can sometimes be closed on paper by the responsible operator through its own amendment process. The review's role is to size the gap honestly; when unmatched changes are numerous or the data is estimated, it will say that a reweigh is the more defensible route, and the operator decides.

Relevant glossary terms

Related pages

Where this fits

Talk to an engineer who has done this work

We will walk through your current state, the records or evidence involved, and a scoped first engagement.

Talk through the aircraft, records, evidence, deadline, and next useful step.