Cross-authority airworthiness directive review workflow
Review FAA, EASA, UK CAA and CAAC directive sources against fleet configuration and records without assuming every authority's AD is interchangeable.
About this article: This information illustrates the potential benefits of Aviation.Bot’s upcoming regulatory library and desktop/web document-review features. It is not compliance guidance, legal advice or a basis for a regulatory, certification or operational decision. Examples demonstrate the workflow; verify applicable official sources and use qualified professional judgement for actual work.
Workflow at a glance
Original workflow illustration. Candidate findings remain subject to qualified human review; the diagram does not establish an approval or compliance decision.
Similar aircraft do not establish identical obligations
A fleet review often starts with an AD alert and ends with a question about a particular aircraft, engine or installed component. Between those points, the team must resolve jurisdiction, configuration, dates, previous actions and evidence. Finding a directive with the right model name is the start of the assessment.
The FAA explains that an AD's applicability identifies affected models and may include installed-part or modification considerations. Its compliance time governs when the required action is due. Those details belong in the review record, not just in a link to a search result. FAA applicability and compliance guidance.
A useful cross-authority process also asks why a given source creates an obligation for the aircraft under review. Flying to another jurisdiction does not, by itself, answer every continuing-airworthiness applicability question. Establish the aircraft's regulatory context, State of Design and applicable adoption or other authority provisions with the responsible specialist.
Follow each authority's source path
The FAA describes ADs as enforceable rules under 14 CFR part 39. Its AD resources include issuance, compliance and alternative-method-of-compliance information. Keep final directives distinct from proposals and advisory publications when building the working register. FAA AD overview.
EASA's AD FAQ discusses EASA directives, foreign directives and safety-information publications. Its treatment of an adopted FAA emergency AD illustrates why adoption and timing matter: the source relationship is part of the review, rather than an assumption that every foreign notice is automatically interchangeable. EASA AD FAQ.
The UK CAA states that UK-register aircraft must comply with applicable ADs and that the process of identifying them changed after EU withdrawal. It points reviewers to the CAP 747 flowcharts and publishes relevant UK and non-adopted State-of-Design material. A pre-2021 source habit therefore needs an explicit check against today's UK route. UK CAA AD guidance.
CAAC provides a public CAD query with new, emergency, domestic-aircraft and historical directive categories. That is a discovery route, not evidence that an English listing alone is complete for a particular product. Retrieve the authoritative directive and establish the applicable Chinese requirements before interpreting its effect. CAAC public CAD query.
Make the applicability assessment reproducible
Use one row per directive and affected asset, with aircraft registration, model, serial number, relevant installed equipment, configuration evidence, directive revision, effective date, compliance trigger and review status. Include the source of the obligation and the linked work or inspection record.
Record why a directive was included or excluded. “Not applicable” without configuration evidence leaves the next reviewer to repeat the investigation. “Complied with” without the linked record leaves a different gap. Keep preliminary research conclusions separate from the organisation's approved AD status and maintenance-control systems.
Supersedure also needs its own field. A superseding directive may alter requirements, retain actions or introduce new ones; the title alone does not settle what carries forward. Compare the actual text and the evidence for previous action before changing the register.
Synthetic example: a component moves between aircraft
Imagine a fictional engineering team reviewing a component transferred between aircraft in a group with separate EU and UK regulatory contexts. An AD search returns several related authority notices concerning the component family. The team cannot close the task by choosing the newest date across all results.
The research pack contains the aircraft and component records, installation history, source directives, relevant authority routing material and previous work evidence. A reviewer creates an applicability worksheet, a source-relationship note and an evidence-request list. One row identifies missing component serial-number evidence. Another records that the current source needs comparison with a superseded directive before earlier work can be relied on.
These outputs help the team identify precisely what remains unresolved. They do not establish a compliance deadline for the fictional aircraft or authorise its operation. Any approved alternative method, allowance or previous-action credit must be checked against its actual scope and competent-authority treatment.
Use AI to organise the investigation
A source-backed assistant can locate applicability paragraphs, extract compliance triggers and find references to directive identifiers inside maintenance records. It can draft a comparison and flag missing fields. Reviewers should verify numerical limits, exceptions, tables and quoted source passages before using the draft in controlled work.
A strong result includes uncertainty. If the installed part number is absent, the draft should say what record is needed rather than infer the configuration from the aircraft model. If one authority's relationship to another notice is unclear, preserve the question for a specialist instead of generating a blanket equivalence statement.
Building the worklist with Aviation.Bot’s upcoming workspace
Aviation.Bot’s upcoming regulatory library and desktop/web features are designed to support AD research like this. The starting libraries cover EASA, FAA, UK CAA, CAAC and Dutch IL&T across multiple document categories. The workflow lets a reviewer compare identified directives with selected aircraft configuration and maintenance records, keeping authority-specific applicability questions and missing evidence separate. Desktop users work with selected local folders and files; browser users upload selected documents to their workspace. Available sources and editions remain visible parts of the review rather than an assumed complete collection.
The practical difference from a typical ChatGPT upload session is the aviation-specific source collection and repeatable document-review workflow: selected regulatory material sits alongside the organisation’s manuals, procedures and evidence, with references the reviewer can reopen. ChatGPT also supports file analysis; Aviation.Bot’s differentiation is how the source set and review task are organised, rather than a claim that general assistants cannot read documents.
Complex tables and forms deserve the same inspection as prose. The workflow is being developed to retain table relationships, headings, footnotes and form context, and to let the reviewer check the original page when extraction is uncertain. Reliable review depends on seeing that structure—not merely receiving a confident summary. Better accuracy, complete table fidelity and time savings require task-specific validation; they are not established by having a curated database.
The review output is an AD research worksheet with exact sources, configuration evidence and unanswered questions. Responsible people retain the applicability, compliance and approval decisions. Assess the benefit through completed, reviewed tasks rather than the speed of the first answer.
Suggested CTA: Explore the current EASA assistant at aviation.bot and follow updates on the planned multi-authority document workflow.
Prepared with AI assistance and editorial checks against linked official sources. Illustrative examples do not represent authority or independent expert approval.