Weight and balance at closeout
Weight and balance records inside the shop-visit source file
This review tests whether the weight and balance statement in a shop-visit source file is actually supported by the work performed. A records specialist reads each weight-affecting task, modification, and equipment change in the work orders and non-routine cards, then confirms the statement or its amendment reflects them. It runs at shop-visit closeout, before the quality manager accepts the work package. The output is an exception list naming each weight change the statement does not carry and the source document that proves it.
When this review is needed
- A heavy check or engine shop visit embodied modifications that changed basic empty weight and the statement has not been amended.
- The operator's acceptance standard requires a current weight and balance amendment inside the closeout package.
- Equipment moved on or off the aircraft during the visit through non-routine cards that never reached the weight engineer.
- A lessor receiving the work package wants the weight change trail confirmed before signing acceptance.
The problem
Weight changes accumulate quietly across a shop visit. A galley removed on a non-routine card, an antenna added under an SB, ballast shifted for a repair: each is recorded on its own paper, and the weight and balance statement is amended only if someone collects them all. At closeout, the quality manager holds a statement that may be dated before half the work was performed, with no fast way to know which entries it misses.
What gets reviewed
- Every work order and non-routine card screened for tasks that add, remove, or relocate mass
- Modification and SB incorporation records compared against the amendment trail
- The weight and balance statement or reweigh report checked for currency against the visit's completion dates
- Ballast changes and equipment relocations traced to a supporting amendment entry
- Computed amendments checked for arithmetic and for the arm and moment data they rely on
- Release certificates matched to installed items that carry a weight change
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
- Each weight-affecting task in the source file appears in the statement, an amendment, or a documented reweigh
- The statement's effective date falls after the last weight-affecting task was completed
- Amendment arithmetic reproduces from the item weights and arms cited
- Removed equipment recorded on non-routine cards is reflected as a subtraction, never left in the baseline
- The amendment chain is continuous back to the last physical weighing on file
Evidence normally required
- The weight and balance statement, amendments, and the most recent reweigh report
- Work orders and non-routine cards from the shop visit
- Modification and SB accomplishment records with their weight change data
- Release certificates for installed equipment
- The operator's or lessor's acceptance standard for the closeout package
Common discrepancies
- A statement dated before modifications that added equipment late in the visit
- Ballast installed for a repair and never entered as a permanent change
- An amendment that cites item weights with no source document behind them
- Removals on non-routine cards that were never subtracted from basic empty weight
What is at stake
If the package is accepted with an unsupported statement, the error transfers straight into the operator's load control data. Later reconciliations then have to reopen the entire shop-visit file to find which task changed the weight, usually long after the mechanics who signed the cards are available to ask. A statement challenged at the next lease event costs far more to rebuild than to verify at closeout.
How the work runs
Screen the source file
Read work orders, non-routine cards, and modification records and flag every task that touches mass or moment.
Build the change ledger
List each flagged change with its weight, arm, and completion date from the source documents.
Test the statement
Compare the ledger against the statement and amendment trail and mark every change the trail does not carry.
Report exceptions
Deliver the exception list with the evidencing document for each item so the shop can amend before acceptance.
What the buyer receives
- An exception list pairing each unsupported weight change with the source document that evidences it
- A marked-up amendment trail showing where the statement diverges from the work performed
- A closure recommendation for each exception the shop can act on before acceptance
Who uses the output
- Quality managers deciding whether to accept the closeout package as delivered
- Weight engineers who must issue the amendment the exceptions call for
- Lessor technical representatives signing off the work package on behalf of the owner
How the work fits into the transaction or program
The review sits between physical completion of the shop visit and formal acceptance of the work package. It uses the same source file the shop assembles for closeout, so exceptions can be corrected while the shop still holds the records and the aircraft, rather than surfacing at the next lease transition.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Under 14 CFR 43 the maintenance provider records the work, while 91.417 places retention on the operator, so a weight change proven only in shop paperwork can vanish from the operator's file after closeout. EASA Part-145 organizations working under EU 1321/2014 typically hand over a certified work report, which changes where the amendment evidence lives but does nothing to tie it to the statement.
Regulatory limits
The review verifies documentary support for the weight and balance statement. It does not weigh the aircraft, issue or approve an amendment, determine airworthiness, or release the work package; those acts remain with the certificated organizations responsible for them.
What this review does not cover
- Physical weighing or center-of-gravity measurement of the aircraft
- Preparation of load and trim sheets for operations
- Approval of the amendment method used by the weight engineer
Specific to this review
- Weight changes are the most fragmented evidence type in a shop file because they arrive on routine cards, non-routine cards, and SB paperwork with no common flag.
- A computed amendment is only as good as the item weight it cites; many exceptions trace to catalog weights used where an actual weight was required.
- The statement's effective date is the fastest screen: any weight-affecting task completed after it is an automatic exception.
- Ballast is a recurring blind spot because it is often installed under a repair card rather than a modification, so it bypasses the amendment trigger.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Does the review replace a reweigh?
No. It establishes whether the paper trail supports the current statement. If accumulated unsupported changes exceed what an amendment can honestly carry, the finding will say a reweigh is the cleaner path, but performing one is the operator's call.
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.