An AD search result is the start of an applicability review
A matching model name or part number is useful evidence for a question, not a completed technical decision. Keep the document, assessment and accomplishment record connected.

Illustrative image—not evidence of a real case or verified capability.
Begin with the exact subject
A buyer sees a bulletin title mentioning the same aircraft family as a component offer. That is a reason to investigate, not proof that the offered unit is affected or unaffected. Establish the manufacturer identity, part number, serial number, relevant modification state and intended installation context. Separate information supplied by the seller from configuration evidence held by the operator. A broad aircraft-family filter can help discovery, but it cannot express every effectivity condition. The useful output of the first search is a candidate list with source links and open questions. Avoid turning a missing search result into a statement that no directive applies, especially when the input identity is incomplete.
Distinguish the document's role
EASA's FAQ explains why the word mandatory in a manufacturer's Service Bulletin does not, by itself, describe the complete regulatory position. An AD and an SB have different roles, and incorporation into the applicable maintenance programme can also matter. That limited European explanation should not be flattened into the equally misleading claim that every SB without an AD is optional. For an Iranian operator, establish the competent authority's requirements and the approved programme before deciding the obligation. In a digital record, store the document type, issuer, identifier, revision and effective date separately. A red badge labelled mandatory cannot carry all of that context or replace the responsible technical interpretation.
Keep applicability distinct from accomplishment
An applicability assessment asks whether a requirement concerns the identified aircraft, engine or component under the stated conditions. An accomplishment record asks what was done, when, under which data and with what supporting release or record. A single yes/no field mixes those questions. A clearer review distinguishes awaiting assessment, assessed not applicable with reasons, applicable with action open, and supported accomplishment, while preserving any recurring requirements. These are proposed coordination states, not a replacement regulatory vocabulary. The organisation should map them to its controlled system. If evidence is absent, a blank attachment box must not silently inherit the supplier's claim that the work is complete.
Review change, not just the latest filename
When a revised document arrives, keep the earlier assessment and identify what needs reconsideration. The change may concern scope, instructions, references or a deadline; do not assume it always means the earlier work was invalid, or that it never affects the existing decision. Assign a reviewer and retain the change assessment with the source revision. A part can also change relevance after a modification or movement to another installation context. A shared record should therefore preserve which configuration and date were assessed. Renaming a PDF latest does not show that anyone evaluated the change. A reminder is useful when it points to an explicit review task and a responsible person.
Give purchasing a bounded question list
Purchasing does not need to impersonate an airworthiness authority to improve an RFQ. It can ask the supplier for the exact configuration statement, relevant status summary and identified supporting records required by the technical team. Record whether each item is promised before order acceptance, before dispatch or with the delivery pack. If the seller proposes an alternative part, route its identity back to technical review rather than copying the previous assessment. Preserve commercial acceptance separately from technical disposition. This avoids the familiar problem in which a buyer accepts a price and the transaction screen then appears to certify the component. Good coordination makes responsibilities clearer while allowing commercial questions to progress.
Test the record with a changed identity
For a safe training exercise, use a synthetic component and a clearly illustrative status record, never an invented assessment for a real aircraft. Have one person prepare the identity and another explain the source, relevance decision and evidence of action. Then change the serial number or modification state and check that the earlier conclusion is not automatically transferred. The exercise succeeds when users can identify what must be reassessed and who owns that work. This article provides a way to structure questions and records. It is not an AD evaluation, a compliance statement, an alternative method of compliance or permission to operate, maintain or install any aircraft or component.
Sources & scope
This is editorial educational analysis. Licensed manuals are not reproduced; Iranian applicability and independent technical approval are not established. Actual operations require current controlled sources and authorized decisions.
Continue with the Library tools
Related reading
On this page
Test the idea, not just your memory
Short learning scenarios with explained answers—not a qualification test, training certificate or operational decision.