Aviation document management that ties every change bar to its rule and checks every manual before the FAA sees it
Each revision tied to its rule and checked across every manual before the FAA sees it.
See one case, screen by screen ↓Aviation document management, also called aviation manual management or airline manual revision control, is how an airline keeps its controlled manuals — the flight operations manual, dispatch manual, deicing program, fleet supplements — current, consistent with the regulations and in every crewmember's hands. Aviation Document Management adds seven agents that watch the FAA, EASA, IATA and manufacturer sources, draft each revision as change bars cited to the rule, check it against every other manual, build the FAA package and track crew acknowledgment, while flight standards decides and the manual owner signs.
How to choose AI for airlines: a buyer's guide to agentic AI solutions →
Updated
Every Part 121 airline has to keep its manuals current, never contrary to the regulations or its operations specifications, and in the hands of every crewmember who needs them (14 CFR 121.133, 121.135, 121.137). When the FAA, EASA, IATA or a manufacturer changes something, flight standards hears about it by email, searches 40-plus manuals for every paragraph it touches, writes the revision with change bars, and hopes no other manual still says the old thing. Then come the reviews, the manual owner's signature, the principal operations inspector's package — transmittal letter, list of effective pages, highlights of change — and thousands of crew read-and-acknowledge records chased by spreadsheet.
The risk sits in the companion manuals nobody had time to read. A new holdover time table lands in the Flight Operations Manual, the Dispatch Manual, the ground deicing program and an acquired airline's legacy FOM. Miss one and a pilot and a dispatcher read two different values for the same departure. A flight manual that missed a directive is the kind of finding the FAA has proposed a $400,000 civil penalty for.
Estimated split, in working days, for one regulatory change at a large network airline, by hand and with the solution; the six-week baseline is estimated for the fictional airline.
Seven agents draft every change bar, cite the rule behind it and check each other; the manual owner signs.
On August 11 the FAA issues its Holdover Time Guidelines, Winter 2026–2027. Corvane Airways, a fictional network carrier with 304 aircraft, 42 controlled manuals and 11,205 pages, has to get them into its manuals and onto every tablet before the winter season. Here is how the flight standards team works with the agents in conversation, decides every change bar and signs, screen by screen, in the working solution.
Maren opens Today. Overnight the agents read 412 documents from 9 sources: the FAA's Winter 2026–2027 holdover tables are drafted into FOM Revision 47, 5 change bars wait for her, 4 changes need a decision, and the package is due to the FAA on Sunday, August 16, 3 days away. Beside her list, each agent reports in plain words in one thread, with numbered citations and a button to open its work, and she can ask or instruct them right there.
Requirement mapper: “I agree with bars 1 to 4. I’m holding bar 5.”
The Regulatory watch agent reads 9 sources every night: FAA notices, airworthiness directives and circulars, the Federal Register, EASA, the IATA IOSA Standards Manual and the manufacturers' portals. It opened change RC-2614 at 04:10 on August 12 and says why it applies: Corvane's approved ground deicing program follows the FAA holdover times under 14 CFR 121.629(c). The Impact analyst found 14 paragraphs in 4 manuals (FOM 8.4.2, Dispatch Manual 5.3.2, Ground Deicing Program 3.2 and 4.1, and the Halden Air FOM 6.11), plus 4 that only cite the tables: the requirement map is updated, with no text change.
“Applies. … every manual that quotes last season’s tables must change before the season.”
FOM page 8.4-7 reads as a crewmember will read it, with the revision and date on the page. Each proposed edit is a black change bar. Click bar 1 and the panel shows the proposed text at 97% draft confidence against the Rev 46 text, why it changes, the second check by the Requirement mapper (agrees, 96%) and every other Corvane manual on the topic: two in conflict, two consistent.
Other Corvane manuals on this topic: DM 5.3.2 “still quotes the Winter 2025–2026 table for dispatch release remarks”.
Every bar cites the rule that forces it — here the FAA Holdover Time Guidelines, Winter 2026–2027, Notice N 8900.784 and 14 CFR 121.629(c). One click opens the passage the agents read from the source feed, with the sentence they rely on highlighted: the new guidelines replace those issued for winter 2025–2026.
“Read by the Regulatory watch agent from the source feed. The highlighted passage is the one the agents cite.”
The Revision agent drafted bar 5 to let crews calculate holdover times from the FAA regression information. The Requirement mapper re-derives the rule on its own and disagrees at 71%: the FAA intends that information for holdover time determination systems, and Corvane's approved program uses only the EFB Deicing app. Maren types “Why do you disagree?” on the bar; the mapper answers with both citations and proposes wording.
“Held: edit or reject”
Maren rewrites bar 5 — “Holdover times from the FAA regression information are used only through the EFB Deicing app. Crews do not calculate them by hand.” — with the reason “Scope — keep within our approved program”. The mapper re-checks her wording and agrees at 95%. She accepts the other four where both agents agree, with “Meets the requirement as drafted”. Five of 5 decided; Send for review lights up. Each decision is part of the airline's manual revision control record.
“4 bars accepted · each on the audit trail”
The Consistency checker compared 11,205 pages. The Dispatch Manual 5.3.2 has dispatchers enter a holdover time from last winter's generic Type IV table; the Ground Deicing Program 3.2 forbids the allowance times bar 3 allows; the Halden Air FOM 6.11 still names the 2024–2025 tables. For each it drafts a fix for that manual's owner — Dispatch Manual Rev 22 for Ray Castellano, Deicing Program Rev 9 for Nadia Brooks, bulletin HB-26-14 for Halden Air crews.
“3 open · Revision 47 cannot go to the FAA while one is open”
The review rules route chapter 8 to the Chief Pilot and the deicing program owner, and anything the Dispatch Manual quotes to the Chief Dispatcher. Capt. Simone Reyes, Ray Castellano and Nadia Brooks record their reviews. Capt. Lena Aldana signs FOM Revision 47 as manual owner with the meaning “Approved for submission to the FAA” and her password; a writer can never sign their own revision.
“Your signature, the time and its meaning go on the audit trail and cannot be changed.”
The Package builder has drafted the transmittal letter to Gwen Talbot, POI at the FAA Denver CMO, and 8 of 8 items are ready: the list of effective pages, highlights of change, the requirement map extract, the conflict resolution record, the approved and accepted parts (GDM Rev 9 for approval; FOM Rev 47 and DM Rev 22 for acceptance, under Order 8900.1 Vol 3 Ch 32), the EASA notification for third-country routes, and the revision record with signatures. It stayed locked until the owner signed; a person sends it.
Package builder: cannot send — a person sends after the owner signs.
Revision 47 is scheduled to go out through EFB document distribution on September 15, to 6,940 pilots, 214 dispatchers and Halden Air pilots by bulletin, to be acknowledged by September 29, before the season starts October 1, with a three-question understanding check drafted from the change bars. The last revision, Rev 46, stands at 98.3% — 7,031 of 7,154 — with 41 on leave excused from the crew roster and 82 overdue, reminded at 06:00; three are 7 or more days late, so the chief pilot is copied.
Distribution tracker: “I never mark anyone acknowledged.”
The same revision, seen by the five people who carry it — what their week looked like, and what it looks like now.
Seven agents draft every change bar, cite the rule behind it and check each other; the manual owner signs.
Reads the FAA, EASA, IATA and manufacturer sources every night — notices, ADs, ACs, InFOs, SAFOs, the Federal Register, the IOSA Standards Manual, FCOM, QRH and flight manual revisions — and assesses whether each change applies to the airline's fleet, operations and certificate, with the reason and the passage.
Finds every paragraph in all 42 controlled manuals that a change touches, using paragraph search and the requirement map.
Drafts the smallest change that meets the requirement as a change bar on the affected paragraph, in the house style, quoting the passage that forces it — and redrafts when the person asks.
Re-derives the requirement behind every bar on its own, without the drafter's notes, from 14 CFR 121, 117 and 91, the OpSpecs, the IOSA Standards Manual, EASA Part-TCO and FAA guidance, and keeps the requirement map current.
Compares every changed paragraph with every other manual, including the acquired airline's legacy manuals, and drafts the companion revision for the other manual's owner.
Builds the FAA package — transmittal letter, list of effective pages, highlights of change, requirement map extract, conflict record, revision record — and the EASA notification.
After FAA acceptance, publishes the revision to every tablet, sends the understanding check, chases acknowledgements by base and excuses leave and training from the crew roster.
Decide every bar; the Director of Operations signs. The agents propose; a named person decides.
Ask in plain words, or tell the agents what to do. Every answer cites its source and opens the screen it is about.
What changed in the FAA holdover tables, and where does it land?
The FAA issued the Holdover Time Guidelines, Winter 2026–2027 on August 11, to be used with Notice N 8900.784. Our approved deicing program follows them (14 CFR 121.629(c)). The Impact analyst found 14 paragraphs in 4 manuals: FOM 8.4.2 (5 bars, Revision 47), Dispatch Manual 5.3.2, the Ground Deicing Program 3.2 and 4.1, and the Halden Air FOM 6.11.
Why do the agents disagree on bar 5?
The Revision agent drafted “crews may calculate holdover times from the FAA regression information”. The Requirement mapper says the FAA intends that information for holdover time determination systems, not for crews, and our program lets crews use only the EFB Deicing app. So bar 5 is held at 71% until you edit or reject it.
Which manuals still quote last winter’s tables?
Dispatch Manual 5.3.2 quotes the Winter 2025–2026 table; the Ground Deicing Program 3.2 forbids the allowance times bar 3 allows; the Halden Air FOM 6.11 names the 2024–2025 tables. Each has a drafted fix for its owner.
Remind everyone overdue on Rev 46
Reminding the 82 overdue crew on FOM Rev 46 now, through the EFB and email. 41 on leave stay excused until their first duty. Three are 7 or more days past due, so the rule copies the chief pilot. The reminders go on the audit trail.
13 screens from the working solution, on its sample data. Pick one to see it large.
The thresholds, clocks, review routing and permissions the agents work to are settings, and changes to them are on the audit trail.
| Setting | Default | Choose from |
|---|---|---|
| Show a drafted bar from | 80% draft confidence | Step up or down, 5 points at a time; below it the Revision agent asks instead of drafting |
| Second check must agree | On | The Requirement mapper re-derives every bar; a disagreement holds it |
| Submit to the FAA | 30 days before the effective date | Step up or down, 5 days at a time |
| Acknowledge within | 14 days after the effective date | Or before the first duty after leave · reminder at day 7 · chief pilot 7 days past due |
| Understanding check pass mark | 3 of 3, with one retry | 3 of 3 · 2 of 3 |
| Review routing | Chapter 8 · cold weather and icing → Chief Pilot and deicing program owner | Any paragraph quoted in the Dispatch Manual → Chief Dispatcher · fleet supplements → Chief Pilot and fleet technical pilot · anything in an FAA-approved program → program owner, then approval, not acceptance |
| Sign as manual owner | Manual owner only | Locked: a writer can never sign their own revision |
| Reason codes for an edit | Scope — keep within our approved program | Wording — plain language for crews · Scope · House style · Accuracy — the draft overstates the rule |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the six-week baseline and the split of working days are estimated for a fictional airline) · “typical” = published figures (FAA newsroom, July 2024: a proposed $400,000 civil penalty over a carrier's flight manual allegedly not updated for a directive, 44 flights; a proposal, not a final finding). Rules named for context: 14 CFR 121.133, 121.135, 121.137 and 121.629(c); FAA Holdover Time Guidelines, Winter 2026–2027 and Notice N 8900.784; FAA Order 8900.1 Vol 3 Ch 32; EASA ORO.MLR.100. Source passages on screen are paraphrased for the demo, and the table changes in bars 2–5 are illustrative. Corvane Airways, Halden Air and the people named on this page are fictional — characters and sample data in the working solution.
Aviation document management, also called aviation manual management or airline manual revision control, is how an airline keeps its controlled manuals — the flight operations manual, dispatch manual, deicing program, fleet supplements — current, consistent with the regulations and in every crewmember's hands. Aviation Document Management adds seven agents that watch the FAA, EASA, IATA and manufacturer sources, draft each revision as change bars cited to the rule, check it against every other manual, build the FAA package and track crew acknowledgment, while flight standards decides and the manual owner signs.
Section 121.135 says a manual may not be contrary to the regulations or the operations specifications. For operations manual compliance, every changed paragraph is tied to the requirement it answers, and a second agent re-derives that requirement on its own. The requirement map holds 2,316 requirements from 14 CFR 121, 117 and 91, the OpSpecs, the IOSA Standards Manual, EASA Part-TCO and FAA guidance, with the paragraphs that meet each one, and shows what is not yet mapped; the mapper proposes a paragraph and a person confirms.
The Consistency checker compares every changed paragraph with all the other manuals — 11,205 pages in the demo, including an acquired airline's — and shows both passages side by side with an explanation. It drafts a companion revision for the other manual's owner, and a revision cannot go to the FAA while a conflict is open.
After the manual owner signs, the Package builder assembles the package for FAA acceptance: the transmittal letter, list of effective pages, highlights of change, requirement map extract, conflict record and revision record, and separates the parts for approval from those for acceptance. It also drafts the EASA notification for third-country routes. A person sends it and records the FAA's response.
After FAA acceptance, the Distribution tracker publishes the revision to every crew tablet through your EFB document distribution, with read and acknowledge built in and a short understanding check drafted from the change bars and approved by crew training. It shows acknowledgment by base, excuses crew on leave or in training from the roster, reminds the overdue and copies the chief pilot 7 days past due. It never marks anyone acknowledged.
Yes. In the demo, 9 legacy manuals of an acquired airline are checked alongside the airline's own until they retire onto its certificate: 1,904 of 2,118 of their paragraphs are mapped to their equivalents, and a stale holdover table in the legacy FOM is caught with a crew bulletin drafted.
No, and yes. The agents draft, cite, check and remind; they never accept a bar, sign, send to the FAA, change another owner's manual or mark anyone acknowledged, and a revision goes to the tablets only after the owner signs and a person records FAA acceptance. Flight standards accepts, rewrites or rejects every bar with a reason, reviewers record their reviews and only the manual owner signs.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your manuals, OpSpecs, house style and review rules — and it goes live once every quality gate has passed. We will walk you through it on one of your own recent regulatory changes first.
Recovery plans in minutes, each one rehearsed and costed, signed before anything moves.
1-min demoFlight Dispatch ReleaseEvery release checked before signature, with a source behind every number.
1-min demoNOTAM Briefing238 notices become the 6 that change the flight, each with its reason and original text.
1-min demoWe'll run Aviation Document Management on a recent regulatory change and a sample of your own manuals.