Which aviation rule version are you using? A source-check routine
Record authority, document type, edition and applicability before using an aviation regulatory citation in a manual review.
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.
A search result can take you to the right paragraph in the wrong edition. A bookmarked PDF can remain useful long after a newer amendment appears. An AI answer can sound specific while leaving out the source date. Before turning a regulatory reference into a manual-review action, make the authority, document type and version visible. The method applies to work involving FAA, EASA, UK CAA, CAAC and national oversight material; the EASA example below illustrates one source format rather than the limits of the workflow.
This article offers a practical recordkeeping routine. It does not determine which requirements apply to your approval or replace the responsible reviewer’s judgement.
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.
Start with the publication, then follow the source
EASA publishes Easy Access Rules in several formats. The books combine regulatory material for navigation; the publication date is a useful starting point for a source record. EASA’s XML FAQ expressly says the Easy Access Rules are not an official publication. Keep the underlying legal instrument or decision in view when forming a conclusion. EASA’s XML FAQ
Avoid a citation that says only “latest aviation rules.” A later reviewer cannot reproduce what you read. Write the issuing authority, document type, title, edition label, source URL, retrieval date and exact clause. Where relevant, record the amendment or decision behind the text and the date information the reviewer used. Two authorities can use similar terminology while addressing different approvals or activities; do not merge their source records just because clause numbers resemble each other.
Keep three dates apart
In your review record, give publication, retrieval and applicability separate fields. Publication describes when a source appeared. Retrieval describes when you obtained your copy. Applicability is a question to establish from the relevant source and your circumstances. One date should never silently stand in for another.
For example, “downloaded this morning” does not mean the rule changed this morning. Nor does an amendment’s appearance in a consolidated book tell you, on its own, whether every provision applies to your work today. Record unresolved date questions explicitly so the reviewer can resolve them before approving an action.
A fictional source register
Use one row per source you actually inspect. The following example is an invented review record, not a regulatory finding:
| Field | Example entry |
|---|---|
| Review question | Is our procedure reference still pointing to the text reviewed last quarter? |
| Source title | Selected EASA Easy Access Rules book |
| Authority and document type | EASA; consolidated navigation publication |
| Edition | Edition shown on the downloaded publication |
| Exact location | Clause heading and page or stable link |
| Underlying source | Instrument or decision identified in the publication |
| Retrieved | 3 October 2026 |
| Applicability | Pending responsible reviewer confirmation |
| Internal reference | Procedure QA-12, revision 4, paragraph 3 |
| Decision | Reference checked; substantive impact not yet assessed |
The distinction in the last row matters. Finding the correct source is one completed task. Establishing its effect on the organisation is another.
Check beyond the book you downloaded
Open the relevant official publication page, inspect its edition information, and look for later amendments in the appropriate official source collection. The Information Security EAR page, for example, explicitly directs readers to check the regulations page for rules adopted after the book’s publication. This is a useful reminder to avoid treating a consolidated volume as a complete update service. EASA Information Security EAR
Keep the copy you reviewed with the source register if your organisation’s retention and copyright arrangements permit it. A link alone may change; a saved file alone can lose its provenance. Together, a dated source record and identifiable copy make the review easier to reproduce.
What to do when versions disagree
Do not quietly overwrite the old source and leave the original decision untouched. Record what differed, which conclusion relied on the earlier copy, and who will assess the effect. Your worklist might say “confirm whether the revised paragraph changes the rationale for QA-12.” That is more useful than an unsupported “procedure non-compliant” label.
The same approach works when an AI answer cites an inaccessible page. Treat it as a lead to investigate. Open the official material, confirm the passage and record the edition before carrying the statement into controlled work.
Where Aviation.Bot fits
Aviation.Bot’s upcoming regulatory library and desktop/web features are designed to support source-version review like this. The starting libraries cover EASA, FAA, UK CAA, CAAC and Dutch IL&T across multiple document categories. The workflow lets a reviewer select the authority and edition, inspect the cited provision, then find where that reference appears in the organisation’s manuals. 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.
For the next step, see the MOE review workflow and the worked change-impact matrix. Sign up on Aviation.Bot to stay up to date about upcoming releases.
Prepared with AI assistance and editorial checks against linked official sources. Illustrative examples do not represent authority or independent expert approval.