AD baseline gap
AD applicability baseline rebuild for missing lines
This page is for operators, CAMOs, Aircraft records teams dealing with Audit or diligence surfaces an unlisted applicable AD. The review starts with the disputed or high-risk status claim, then checks it against current AD status list, airframe and engine configuration records, installed appliance list, STC and mod status. Findings identify absent source pages, wrong-asset evidence, timing conflicts, and limits that should be disclosed rather than hidden. The buyer receives rebuilt AD applicability baseline, missing AD compliance research log, corrected status list change file so closure work can be assigned and tracked.
When this review is needed
- A counterparty has challenged the records position or asked for deeper evidence.
- The internal team can see a gap but has not defined the cure route.
- Several record families point to the same unresolved source document or status conflict.
- Commercial or program timing requires a defensible position before every document is recovered.
The problem
The difficult part is deciding what the records actually prove before the deadline or transaction pressure takes over. A display, radio altimeter, seat, or other appliance AD is absent from the airframe list. A modification changed applicability but the AD filter was not updated.
What gets reviewed
- Rebuild AD applicability from installed equipment and configuration, not only model type.
- Identify component, appliance, and STC-triggered ADs missing from the list.
- Research compliance evidence for each newly surfaced applicable AD.
- Correct the status list with applicability rationale and source references.
- Set a re-baseline interval after configuration changes.
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
- Pass when applicability is supported by part number, serial, model, or configuration evidence.
- Fail when model-based filtering misses installed appliance ADs.
- Pass when each new applicable AD has a compliance or open-action disposition.
- Fail when inherited status lists are accepted without an independent sweep.
Evidence normally required
Common discrepancies
- A display, radio altimeter, seat, or other appliance AD is absent from the airframe list.
- A modification changed applicability but the AD filter was not updated.
- An inherited list was generated at delivery and never re-baselined.
- Newly found ADs have no compliance evidence because nobody tracked them before.
What is at stake
A weak response can turn a curable records defect into a holdback, delivery condition, audit repeat, or grounded planning assumption. The practical risk is carrying forward an unsupported position because nobody separated evidence gaps from administrative cleanup.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Frame Missing Status
Confirm the exact event, affected file set, buyer role, and decision standard before any ad status list is treated as sufficient.
Trace Remediation Applicable
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Baseline Rebuild
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Gap Finding
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- rebuilt AD applicability baseline
- missing AD compliance research log
- corrected status list change file
- configuration trigger checklist
Who uses the output
- CAMO manager uses the findings to decide which gaps block the next milestone.
- Technical records manager uses the evidence map to request, correct, or reserve records items.
- Quality manager uses the summary to brief stakeholders without reopening the full file.
How the work fits into the transaction or program
The review sits between raw document collection and the decision to accept, reject, reserve, or escalate. It gives the next team a page-referenced position instead of another narrative summary. The page-specific framing is The most dangerous AD finding is the line that isn't there: an applicable AD absent from the status list because the effectivity filter was built on airframe model alone. Problem definition: appliance and engine-accessory ADs (displays, radio altimeters, seats, fire bottles, oxygen generators), ADs triggered by STC-modified configurations, and ADs against installed part numbers all escape model-based filters. Remediation evidence: a rebuilt applicability baseline from installed-equipment data, component records,. For missing status list remediation, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The ad missing from status list remediation scope is intentionally narrow: Fix an AD status list with applicable ADs missing from it.. The Missing Status List evidence question is tested against ad status list and not against a generic checklist copied from another page. The Remediation Applicable Applicability trigger is audit or diligence surfaces an unlisted applicable ad, so the review ranks gaps by decision impact instead of document volume. The Baseline Rebuild Lines searcher pattern is A records manager or auditor who found an unlisted applicable AD searches how to re-baseline applicability and remediate.. The Gap Finding Fixing evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Holes Record Review exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Closure Trace Baseline handoff is written for camo manager, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on rebuilt ad applicability baseline, which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is The most dangerous AD finding is the line that isn't there: an applicable AD absent from the status list because the effectivity filter was built on airframe model alone. Problem definition: appliance and engine-accessory ADs (displays, radio altimeters, seats, fire bottles, oxygen generators), ADs triggered by STC-modified configurations, and ADs against installed part numbers all escape model-based filters. Remediation evidence: a rebuilt applicability baseline from installed-equipment data, component records, and mod status; then compliance research for each newly surfaced AD. The failure pattern includes status lists generated once at delivery and never re-baselined, avionics upgrades adding applicable ADs nobody mapped, and inherited lists from prior operators trusted without an independent applicability sweep. The ad missing from status list remediation missing status list lane records how applicability baseline rebuild affects finding fixing holes, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation list remediation applicable lane records how rebuild lines gap affects holes most dangerous, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation applicable applicability baseline lane records how gap finding fixing affects dangerous line isn, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation baseline rebuild lines lane records how fixing holes most affects isn there absent, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation lines gap finding lane records how most dangerous line affects absent because effectivity, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation finding fixing holes lane records how line isn there affects effectivity filter was, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation holes most dangerous lane records how there absent because affects was built airframe, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation dangerous line isn lane records how because effectivity filter affects airframe model alone, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation isn there absent lane records how filter was built affects alone problem definition, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation absent because effectivity lane records how built airframe model affects definition appliance, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation effectivity filter was lane records how model alone problem affects missing status list, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation was built airframe lane records how problem definition appliance affects list remediation applicable, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation airframe model alone lane records how appliance affects applicable applicability baseline, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation alone problem definition lane records how status list remediation affects baseline rebuild lines, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation definition appliance lane records how remediation applicable applicability affects lines gap finding, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation missing status list lane records how applicability baseline rebuild affects finding fixing holes, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation list remediation applicable lane records how rebuild lines gap affects holes most dangerous, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad missing from status list remediation applicable applicability baseline lane records how gap finding fixing affects dangerous line isn, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Fix an AD status list with applicable ADs missing from it.. The operating angle for this page is The most dangerous AD finding is the line that isn't there: an applicable AD absent from the status list because the effectivity filter was built on airframe model alone. Problem definition: appliance and engine-accessory ADs (displays, radio altimeters, seats, fire bottles, oxygen generators), ADs triggered by STC-modified configurations, and ADs against installed part numbers all escape model-based filters. Remediation evidence: a rebuilt applicability baseline from installed-equipment data, component records, and mod status; then compliance research for each newly surfaced AD. Failure modes: status lists generated once at delivery and never re-baselined, avionics upgrades adding applicable ADs nobody mapped, and inherited lists from prior operators trusted without an independent applicability.
Jurisdiction-specific considerations
FAA and EASA references are used as evidence criteria for records completeness and traceability. The review does not treat one authority's records as automatic acceptance by another authority or by a transaction counterparty.
Regulatory limits
The output does not replace regulator review, authorized release, engineering approval, conformity finding, or the buyer's own acceptance process. It documents records support and records limits for the responsible parties to use.
What this review does not cover
Specific to this review
- The highest-risk AD gap is the line absent from the list because no one knows to ask for evidence.
- Installed equipment records are the control point for component and appliance AD applicability.
- Configuration changes can add AD exposure without changing aircraft model.
- A rebuilt baseline should explain why non-applicable ADs were excluded as well as why applicable ones were added.
- The scope uses the Missing Status List Remediation question as the control point, so the review stays tied to Audit or diligence surfaces an unlisted applicable AD and the buyer decision behind it.
- The evidence starts with AD status list and follows Applicable Applicability Baseline Rebuild references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for CAMO manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Lines Gap Finding Fixing questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from rebuilt AD applicability baseline; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
What makes this problems review different from a general file audit?
The scope is tied to missing status list remediation and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block audit or diligence surfaces an unlisted applicable ad or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad status list, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives camo manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.