Applicability conflicts
Resolving effectivity conflicts in operator modification records
Effectivity conflict remediation settles cases where a Service Bulletin, STC, or status report claims applicability that the aircraft's configuration contradicts. Operators bring it in when their records show a bulletin accomplished on a serial number outside its effectivity, an AD marked not applicable on the strength of a disputed configuration, or a modification whose effectivity language no longer matches the airplane. The review establishes the aircraft's actual configuration from primary records, re-reads each disputed effectivity clause against it, and corrects the status conclusions with the reasoning attached. Output is a conflict register with a resolved position per item, corrected status entries, and substantiation an auditor or lessor can follow.
When this review is needed
- A status list shows a Service Bulletin accomplished on a serial number the bulletin's effectivity does not include.
- An AD was closed as not applicable based on a configuration the modification records no longer support.
- Two status reports for the same aircraft disagree on which bulletins apply because they assume different mod states.
- A pre-purchase or authority review asked why a recorded compliance action does not fit the published effectivity.
The problem
Effectivity is where configuration and compliance meet, and a conflict there means one of them is wrong. Status reports are built by reading effectivity clauses against an assumed configuration, so a single stale assumption about an unreported modification or a customer-specific variant propagates through every later applicability call. Engineers then spend review meetings arguing about what the aircraft is instead of what to do about it.
What gets reviewed
- Reconstruction of the aircraft's configuration for each disputed item from delivery documents, modification records, and alteration entries
- Close reading of the effectivity language in each disputed SB, STC, and related AD, including revision changes to that language
- Comparison of manufacturer line-number, serial, and customer-variant identifiers used across the documents
- Re-derivation of the applicability conclusion for every conflicted item
- Correction path for status reports, with the configuration evidence that supports each change
- Identification of any compliance action required where applicability flips
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 applicability conclusion cites the configuration evidence it depends on, at the document level
- Effectivity is checked against the revision of the bulletin actually in force at the compliance date
- Serial, line-number, and variant identifiers are reconciled across OEM, authority, and operator documents
- Where an SB drives an AD's applicability, both conclusions move together and neither is corrected in isolation
- Corrected status entries preserve the prior conclusion and the reason it changed
Evidence normally required
- Current AD, SB, and modification status reports with their assumed configuration basis
- Delivery configuration documents and the modification and alteration history
- The disputed bulletins, STCs, and ADs at all relevant revisions
- Accomplishment records for items claimed complete
- Any prior applicability reviews or engineering dispositions on the disputed items
Common discrepancies
- Effectivity read from an outdated bulletin revision after the OEM expanded or narrowed the affected serials
- Applicability derived from line number where the bulletin's terms turn on installed configuration
- An embodied STC that changed the aircraft's effectivity group without the status reports being rebased
- Compliance recorded against a sister aircraft's status line during a fleet update
What is at stake
An effectivity conflict casts doubt in both directions. If the aircraft really is inside the effectivity, a not-applicable AD closure becomes a potential compliance lapse. If it is outside, recorded accomplishments and their downstream credit are misdirected effort at best and evidence of configuration confusion at worst. Either way, auditors and buyers who find one conflict start re-deriving the whole applicability baseline, at the operator's expense.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Register the conflicts
List every item where recorded status and configuration cannot both be true, with the documents on each side.
Fix the configuration facts
Establish the aircraft's actual build and modification state for each item from primary records.
Re-read the effectivity
Apply the governing revision's effectivity language to the established configuration and re-derive each conclusion.
Correct and route
Update status entries with rationale preserved and route flipped conclusions to engineering and compliance owners.
What the buyer receives
- A conflict register with a resolved, evidence-backed applicability position per item
- Corrected status-report entries with change rationale preserved
- A configuration evidence file supporting each resolved position
- A list of compliance actions or engineering referrals arising from flipped conclusions
Who uses the output
- Records staff issuing status reports that survive external re-derivation
- Maintenance leadership deciding what action follows where applicability changed
- Counterparty-facing teams answering lessor and buyer questions with documents instead of assertions
How the work fits into the transaction or program
Effectivity resolution is upstream of nearly every compliance product the operator issues: AD statements, SB status, and modification summaries all inherit its conclusions. It typically runs alongside a configuration-baseline check, and its conflict register feeds the same closure machinery the operator uses for other records discrepancies.
Jurisdiction-specific considerations
For FAA operators, the configuration side of the question rests on alteration records under 14 CFR 43 and design-change effectivity under 14 CFR 21, with status records kept under 91.417. EASA-managed aircraft add Part-M and Part-CAMO expectations under Regulation (EU) 1321/2014 that applicability assessments stay demonstrably current. The same airframe can sit in different effectivity groups under FAA and EASA issuances, so aircraft that changed registry get both readings checked.
Regulatory limits
The review resolves what the records support about applicability. It does not issue engineering dispositions, approve alternative methods of compliance, or declare the aircraft airworthy where a conclusion flips; those decisions stay with the operator's engineering authority and its regulator.
What this review does not cover
- Engineering redesign or approved-data development for configuration corrections
- AMOC applications or other authority submissions
- Physical configuration verification on the aircraft
Specific to this review
- Effectivity language is revision-sensitive: OEMs expand and narrow affected-serial lists between bulletin revisions, so the correct reading depends on which revision governed at the compliance date.
- Line number, serial number, and customer variant are three different identity systems, and conflicts often trace to a document that silently switched between them.
- A flipped applicability conclusion is a compliance event in its own right, and its handling differs sharply depending on whether the item moved into or out of scope.
- Fleet-level status updates are a common contamination path; one aircraft's accomplishment gets written across siblings whose configurations differ in exactly the relevant way.
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). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
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
If a bulletin was accomplished on an aircraft outside its effectivity, is there anything to fix?
Usually yes. The accomplishment itself may be harmless, but the record claiming it distorts the aircraft's modification state, can misdirect AD applicability that keys on the bulletin, and signals to reviewers that applicability calls were not controlled. The correction documents why the work was recorded, what was physically done, and what the status should now say.
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.