Skip to content

Mass and balance trace

Weight and balance evidence inside a component-history source file

Where a serialized component has meaningful mass, its installation history should be visible in the aircraft's weight and balance record, and this review checks that it is. The current weight and balance statement and its amendment chain are read against the component's removals, installations, and modifications as documented in the source file, to confirm each mass-relevant event produced a supported amendment. It is carried out during a serialized-component trace review, usually alongside the equipment-list check. The result is an amendment exception list identifying configuration events the weight record never absorbed.

When this review is needed

  • A heavy component was exchanged for a different part number and nobody can point to the weight amendment that followed.
  • The amendment chain jumps from one revision to another with configuration events in between that should have moved the numbers.
  • A modification with published weight impact is embodied on the part, yet the statement predates the embodiment.
  • Delivery or redelivery conditions require a current weight and balance statement consistent with the records package.

The problem

Weight and balance sits at the edge of most records teams' attention. Mechanics change parts, engineers embody modifications, and the assumption is that someone downstream updates the statement. On a busy aircraft that assumption fails quietly for years, until a trace review lines up the component's movement history against the amendment dates and finds long stretches where mass changed on paper everywhere except the one record that tracks mass.

What gets reviewed

  • The amendment chain of the weight and balance statement reconstructed in date order
  • Component removals and installations from the source file screened for mass or moment relevance
  • Embodied modifications checked against their published weight and balance impact
  • Each relevant configuration event matched to an amendment or a documented no-change rationale
  • The current statement checked for internal consistency and against the latest weighing report
  • Ballast and equipment-variation entries reconciled with the component's installation record

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

  • Every mass-relevant event in the component's history has a corresponding amendment dated after it
  • Amendment arithmetic carries forward correctly from the last physical weighing
  • Weight deltas used in amendments trace to manufacturer data or measured values, with the source identified
  • The statement's equipment basis agrees with the installed-part list at each amendment date
  • No amendment relies on a modification the modification-status check could not substantiate

Evidence normally required

  • The current weight and balance statement and its full amendment history
  • The most recent weighing report for each host aircraft in the relevant period
  • The component's removal and installation records from the source file
  • Modification records with their published weight and moment data
  • The equipment list revisions covering the amendment dates

Common discrepancies

  • A component exchange with a different-mass replacement absorbed into the record with no amendment at all
  • Amendments computed from a superseded weighing report after a later weighing existed
  • Weight deltas entered from estimates with no data source recorded
  • An amendment referencing a modification the file cannot show as embodied

What is at stake

An out-of-date statement is a finding in nearly every acceptance protocol, and it is a cheap one for a counterparty to make because the comparison is mechanical. Beyond the deal, a statement that drifted from the true configuration can eventually force a reweigh, which costs downtime and exposes every other record that quoted the stale figures.

How the work runs

01

Rebuild the chains

Lay out weighings, amendments, and the component's configuration events on one timeline.

02

Screen for mass relevance

Identify which removals, installations, and modifications should have moved the record.

03

Match events to amendments

Pair each relevant event with its amendment or documented no-change decision.

04

Report the gaps

Deliver the exception list and an assessment of the current statement's supportability.

What the buyer receives

  • An amendment exception list pairing each unabsorbed configuration event with the record it should have produced
  • A reconciled timeline of weighings, amendments, and component events over the trace period
  • A statement of whether the current weight and balance record can support delivery conditions as it stands

Who uses the output

  • Records leads clearing delivery-document requirements ahead of a transaction
  • Engineering staff deciding whether a reweigh is cheaper than reconstructing the amendment chain
  • Acceptance teams on the counterparty side, who receive a defensible rather than a stale statement

How the work fits into the transaction or program

This check closes the loop that the modification-status and equipment-list reviews open: those establish what changed on the component, and this one verifies the mass consequences reached the aircraft-level record. In the source review sequence it runs late for that reason, consuming the substantiated configuration events the earlier checks produced.

Start with a single asset

Confirm release certificates and component traceability are complete.

Jurisdiction-specific considerations

For FAA aircraft the current empty weight and center of gravity form part of the required records under 14 CFR 91.417, with the maintenance entries behind each change governed by Part 43. EASA continuing-airworthiness rules expect the CAMO to keep the weighing record current within Regulation 1321/2014, and some national authorities add fixed reweigh intervals that the amendment chain must respect.

Regulatory limits

The review audits documentation and arithmetic. It does not perform or witness weighings, does not compute a new weight and balance statement for operational use, and makes no determination about the aircraft's loading limits or airworthiness.

What this review does not cover

  • Physical weighing of the aircraft or component
  • Preparation of an operationally valid load and trim sheet
  • Assessment of flight-operations weight and balance procedures

Specific to this review

  • Exchanges between dash-number variants of the same component are the classic silent mass change: the part fits, the paperwork matches at a glance, and the two units differ by kilograms.
  • An amendment chain that shows activity only at heavy checks usually means line-level component changes were never assessed for weight impact at all.
  • The no-change rationale matters as much as the amendments: without a documented negligible-impact decision, silence after a component event is indistinguishable from an omission.
  • Reweighs reset the arithmetic but not the record: amendments made against the old weighing after a new one exists are a finding auditors catch by date comparison alone.

Sources

Frequently asked questions

The aircraft was reweighed last year. Does that not make the older gaps irrelevant?

A reweigh corrects the numbers going forward, but the trace period behind it still matters. If the record drifted before the weighing, figures quoted in earlier documents, lease returns, and status reports were wrong at the time, and a diligence team reviewing history will still raise them. The reweigh closes the arithmetic, and the review documents what it superseded.

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.