AD market sizing
Affected-fleet and compliance-option review for an AD-driven STC
At new ad affecting a large fleet, the buyer needs to know whether the evidence supports the claimed condition. EE extracts and compares AD applicability language, compliance deadline and terminating-action wording, affected fleet census, reviews the exceptions by specialist judgment, and records what was verified from source. The output is affected-fleet sizing register, compliance-option map, demand-risk memo, built for technical and commercial teams that need a defensible answer without treating AI output as approval.
When this review is needed
- Questions about New AD affecting a large fleet cannot be answered from the summary alone.
- AI extraction can reduce search time if specialist QA is retained.
- Missing evidence would change acceptance, price, due status, or supportability.
- Record owners need a precise request list.
The problem
The decision is whether an AD creates a viable market for a new STC, and how large and urgent the affected fleet really is. The risk is that a tidy spreadsheet hides the source-page problem that matters most.
What gets reviewed
- Inventory AD applicability language using the source file and note the evidence path.
- Recompute compliance deadline and terminating-action wording using the source file and note the evidence path.
- Match affected fleet census using the source file and note the evidence path.
- Escalate service bulletin coverage gaps using the source file and note the evidence path.
- Document existing STCs or AMOCs using the source file and note the evidence path.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Verify AD applicability language back to source, then test adjacent status lines for the same weakness.
- Treat low-confidence extraction as a review queue, not as rejected evidence.
- Close only items with a named reviewer and a retained rationale.
- Mark commercial exposure separately from records repair actions.
Evidence normally required
- AD applicability language
- Compliance deadline and terminating-action wording
- Affected fleet census
- Service bulletin coverage gaps
- Existing STCs or AMOCs
Common discrepancies
- Applicability is read at model level even though serial or configuration limits reduce the true fleet.
- A service bulletin option is assumed unavailable until the support data is checked.
- A claimed terminating option only extends an interval or applies to a narrower group.
What is at stake
A weak review lets unsupported claims become planning inputs. That can affect maintenance due lists, asset value, certification path, or release timing depending on the event.
How the work runs
Frame Driven STC
Confirm the exact event, affected file set, buyer role, and decision standard before any ad applicability language is treated as sufficient.
Trace Assessment Suppliers
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 Fleet Compliance
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Review Market
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
- affected-fleet sizing register
- compliance-option map
- demand-risk memo
- STC opportunity action list
Who uses the output
- Product manager use the register to decide which exceptions affect the event.
- Business development director use the evidence map to request or close source records.
- avionics suppliers leaders use the summary to brief the next approval, release, or deal meeting.
How the work fits into the transaction or program
The decision is whether an AD creates a viable market for a new STC, and how large and urgent the affected fleet really is. The evidence set centers on AD applicability and compliance deadlines, affected fleet census by model and serial range, OEM service bulletin coverage and its gaps, and competing STCs or AMOCs already on file. The likely weak points are the OEM releasing a free terminating SB that kills demand, a deadline extension flattening the demand spike, and misread applicability inflating the addressable fleet. The output gives the product manager a cleanup register for Affected-fleet and compliance-option review for an AD-driven STC before new AD affecting a large fleet.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
No approval, compliance finding, or airworthiness determination is made by EE. The deliverable is an evidence review for the parties who hold those responsibilities.
What this review does not cover
- Authority application filing
- Approval of design or maintenance data
- Physical conformity inspection
- Selection of a kit or vendor
Specific to this review
- The first useful split is missing evidence versus conflicting evidence; the closure path is different for each.
- A service bulletin option is assumed unavailable until the support data is checked usually needs a direct request to the record owner or holder.
- Sampling is least defensible where the failed item would change acceptance, price, or due status.
- Every confirmed exception should identify the exact document that would close it.
- The scope uses the Driven STC Demand Assessment question as the control point, so the review stays tied to New AD affecting a large fleet and the buyer decision behind it.
- The evidence starts with AD applicability language and follows Suppliers Affected Fleet Compliance 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 Product 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 Option Review Market Sizing questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from affected-fleet sizing register; 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). 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.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to driven stc demand assessment and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block new ad affecting a large fleet or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad applicability language, 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 product 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.