SB & modification status
Service bulletin status validation
A service-bulletin status validation confirms which manufacturer bulletins apply to the aircraft, which revision is recorded, and whether each is fully embodied, partially embodied, or open, with evidence linking the modification to the airframe, engine, or component. It is used by lessors, airlines, and acquisition teams when the modification standard affects value, AD closure, or operating capability. It reviews the SB status list, embodiment records, and the configuration the bulletins act on. You receive a bulletin-by-bulletin status with embodiment evidence and a list of unsupported or revision-mismatched entries.
When this review is needed
- A bulletin is a terminating action for an AD and the embodiment evidence has to be confirmed before the AD can be treated as closed.
- A return or sale references a defined modification standard and the actual embodiment has not been verified.
- A bulletin was recorded at one revision but the manufacturer has since reissued it at a higher revision.
- A capability or weight-variant modification affects what the aircraft can be operated or re-leased against.
The problem
Bulletin status is usually carried as a long list of bulletin numbers with an embodied or not-embodied flag. The flag rarely captures the revision actually accomplished, whether embodiment was full or partial, or which serialized components the modification touched. A bulletin shown as embodied at an old revision, or embodied on the airframe but not on a replaced component, leaves a configuration the next operator cannot rely on.
What gets reviewed
- Applicable bulletins for the airframe, engine, and components by effectivity and serial range
- Recorded revision against the current manufacturer revision of each bulletin
- Full versus partial embodiment, including multi-part bulletins accomplished in stages
- Embodiment evidence tying each modification to the specific aircraft or component
- Bulletins that act as terminating actions for an Airworthiness Directive
- Optional, capability, and weight-variant bulletins that affect operating standard
- The SB status list reconciled against the embodiment and work records
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 applicable bulletin is established from effectivity and serial range, not a generic type list
- The recorded revision matches the revision actually embodied and is identified against the current issue
- Partial embodiment is shown as partial, with the outstanding parts of multi-stage bulletins listed
- Embodiment is evidenced by work records that name the aircraft or the serialized component
- A bulletin claimed as an AD terminating action carries embodiment evidence sufficient to close the AD
- Modifications on replaced components are reflected against the component actually installed
- The status list reconciles with the embodiment records rather than standing alone
Evidence normally required
- Current service-bulletin and modification status list
- Embodiment records, work orders, and engineering orders for accomplished bulletins
- Manufacturer bulletin index showing current revisions and effectivity
- Component installation history for serialized parts affected by bulletins
- AD status where a bulletin is cited as a terminating action
Common discrepancies
- A bulletin recorded as embodied at a superseded revision while a later revision is current
- Partial embodiment shown as complete, with later parts of a multi-stage bulletin never done
- An embodiment claimed on the airframe but not carried to a replaced serialized component
- A terminating-action bulletin with embodiment evidence too thin to support the linked AD closure
- An optional or capability bulletin on the list that the actual configuration does not reflect
- A status flag that disagrees with the work records behind it
What is at stake
An overstated embodiment standard can break an AD closure that depended on the bulletin, misstate the modification standard the asset is sold or leased against, and force rework to reach the configuration the next operator actually needs. Catching it before the deal closes keeps the cost with the party that holds the records.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Establish applicability
Build the applicable bulletin list from effectivity and serial range for the airframe, engines, and serialized components.
Confirm revision and extent
Match the recorded revision to the current issue and determine whether each bulletin is fully or partially embodied.
Trace embodiment
Tie each accomplished bulletin to work records that name the aircraft or component, with attention to AD terminating actions.
Report status
Deliver the bulletin-by-bulletin status, flag mismatches and partial embodiments, and identify the evidence needed to resolve each.
What the buyer receives
- A bulletin-by-bulletin status with revision, embodiment state, and evidence trace
- A list of revision mismatches, partial embodiments, and unsupported entries
- A view of bulletins acting as AD terminating actions and whether the evidence supports the closure
- A closure path for each disputed bulletin with the evidence needed identified
Who uses the output
- Continuing-airworthiness teams confirming modification standard before acceptance
- Acquisition and asset teams pricing modification exposure and capability into a deal
- Records teams aligning the configuration baseline for a return or re-lease
How the work fits into the transaction or program
The validation establishes the modification standard the rest of the records rest on, feeding the configuration baseline and the AD compliance status review where directives close on an embodied bulletin.
Jurisdiction-specific considerations
Bulletin applicability does not change with registry, but the regulatory weight a bulletin carries can: a bulletin mandated by an AD or CRI in one authority may be optional in another. Where a bulletin closes a directive, the validation checks the embodiment against the authority whose directive is being relied on.
Regulatory limits
The validation confirms that the recorded bulletin status is complete, consistent, and supported by embodiment evidence. It does not embody bulletins, approve a modification, make an airworthiness determination, or guarantee an authority's acceptance of the configuration.
What this review does not cover
- Embodying or accomplishing any service bulletin or modification
- Approving a modification or its substantiation data
- Any airworthiness determination or configuration approval
Specific to this review
- A service bulletin is a manufacturer recommendation that gains mandatory force only when an AD or an authority requirement cites it, so a fully embodied bulletin and a closed AD are separate facts that must each be evidenced.
- Bulletins are frequently revised, and an embodiment recorded against an old revision can leave changes from later revisions unaccomplished.
- Multi-stage bulletins are commonly accomplished in parts, so a single embodied flag can mask outstanding stages.
- Embodiment on the airframe does not transfer to a serialized component that was later replaced, so component-level bulletins are checked against the part actually installed.
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). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
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
Why does the revision of a service bulletin matter if it is already embodied?
Manufacturers reissue bulletins to correct or extend the modification. A bulletin embodied at an earlier revision may not include the changes a later revision added, so the recorded revision is checked against the current issue.
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.
Walk through your situation with an engineer who has done this work.