Per 14 CFR §135.21, every FAA-certificated Part 135 operator must prepare and keep current a General Operations Manual (GOM) — and, where the operator maintains aircraft under its certificate, a General Maintenance Manual (GMM, sometimes called the Maintenance Operations Manual or MOM). The §135.21 manual must be furnished to the FAA, distributed to the personnel under §135.21(b), and acknowledged by each recipient under §135.21(g). The required content of the GOM is exhaustively specified by 14 CFR §135.23 — including the names and duties of each §135.37 management person, weight-and-balance procedures, §135.79 flight locating procedures, §135.83 operating information procedures, §135.65 mechanical irregularity reporting procedures, the OpSpecs or appropriate extracted information, §135.63 recordkeeping procedures, and other procedures specified by the Administrator. Aircraft requirements under 14 CFR §135.25 must be reflected; the §135.21 manuals must be available at the §135.27 principal business office under 14 CFR §135.27; and the operating information PICs must use under 14 CFR §135.83 must be made available. Civil penalties under 49 U.S.C. § 46301 reach $37,377 per violation in 2026 (inflation-adjusted annually under the Federal Civil Penalties Inflation Adjustment Act) — and §135.21 findings are typically systemic, because every operations record created against a missing or stale revision implicates the same §135.21 root cause.
The §135.21 GOM/GMM audit is the spine of every Part 135 surveillance visit. The Principal Operations Inspector requests the current GOM and GMM, walks the §135.23 content sections against current OpSpecs paragraphs, samples §135.21(b) distribution against §135.21(g) acknowledgment, traces operational records (§135.63 + §135.79 + §135.65 + §135.267) back to the §135.21 revision in effect at the time of the event, and looks for drift between the operator's OpSpecs envelope and what the GOM actually authorizes. The most common finding is not a deficient GOM — it is a GOM that was revised, but the revision was never distributed, never acknowledged, or never aligned to the OpSpecs paragraph that triggered it under FAA Order 8900.1 Vol. 3 Ch. 18.
The platforms ranked below split between the manual-revision-control layer and adjacent layers of the Part 135 stack. Per-tail maintenance platforms (CAMP Systems, Veryon/Traxxall, Flightdocs) feed §135.427 GMM/MOM content from per-tail maintenance records but are not purpose-built for §135.21 GOM revision distribution or §135.23 OpSpecs alignment. Charter operations platforms (WingX) handle live flight following and dispatch but thin on §135.21 manual revision workflow. Aviation-specialist authoring platforms (Web Manuals) include built-in regulatory text libraries and industry-standard GOM/GMM templates but at mid-five-figure annual subscription rates. Document-side compliance platforms (FileFlo) version, distribute, and prove acceptance of both the GOM and GMM/MOM at flat-rate pricing — aligning every revision to OpSpecs paragraphs under FAA Order 8900.1 Vol. 3 Ch. 18 and capturing §135.21(g) acknowledgment per recipient.
Primary regulations cited in this guide: 14 CFR §135.21 (Manual requirements), 14 CFR §135.23 (Manual contents), 14 CFR §135.25 (Aircraft requirements), 14 CFR §135.27 (Business office and operations base), 14 CFR §135.83 (Operating information required), and 49 U.S.C. § 46301 (FAA civil penalties). Operational citations: FAA Order 8900.1 Volume 3 Chapter 18 (Operations Specifications) for OpSpecs paragraph framework and FAA-acceptable manual revision procedure; FAA Order 2150.3C (Compliance and Enforcement Program) for the Enforcement Decision Process under which §135.21 findings are dispositioned.
§135.21 manual findings are systemic — one missing revision implicates every record created against it
Per §135.21 + §135.23, the GOM is the regulatory framework for every operational procedure the certificate authorizes. A POI surveillance finding under §135.79 flight locating, §135.65 mechanical irregularity reporting, §135.267 crew duty time, or §135.63 recordkeeping is usually a downstream consequence of a §135.21 revision that lapsed, was never distributed under §135.21(b), or was never acknowledged under §135.21(g). The certificate-side operational findings stack up — but the §135.21 root cause is what drives the Enforcement Decision Process under 49 U.S.C. § 46301. Manual revision software that enforces the revision-distribution-acknowledgment-OpSpecs-alignment chain structurally is the only defense that scales across multiple revision cycles.
The 7 Best Part 135 GOM/MOM Compliance Platforms
Ranked by §135.21 revision control, §135.23 content section coverage, §135.21(b) distribution tracking, §135.21(g) per-recipient acknowledgment, OpSpecs paragraph tie-back under FAA Order 8900.1 Vol. 3 Ch. 18, and the audit-trail completeness an FAA Principal Operations Inspector requests during surveillance.
FileFlo
Top Pick — Best for Part 135 GOM/MOM Revision Control + §135.21 Acknowledgment Audit TrailBest For
Part 135 charter, air taxi, on-demand, and commuter operators (1-50 aircraft) that need §135.21 GOM + GMM revision control, §135.23 content alignment, §135.21(g) acknowledgment capture, and OpSpecs-paragraph-to-manual-section tie-back under FAA Order 8900.1 Vol. 3 Ch. 18 — without per-manual pricing
Key Feature
AI document classification — upload any §135.21 GOM revision, GMM amendment, OpSpecs paragraph, or §135.23 content section and FileFlo files it against the correct §135 subpart, OpSpecs paragraph, and revision number with §135.21(g) acknowledgment automatically tracked per recipient
Part 135 Focus
§135.21 GOM + GMM revision control, §135.23 content section index, §135.21(b) distribution tracking, §135.21(g) per-recipient acknowledgment, §135.25 aircraft requirements documentation, §135.27 business office records repository, §135.83 operating information files, OpSpecs paragraph tie-back, FAA Order 8900.1 Vol. 3 Ch. 18 revision workflow, one-click POI surveillance binder
Strengths
- AI document parsing — every uploaded manual revision classified against the correct 14 CFR Part 135 subpart, §135.23 content section, and OpSpecs paragraph
- §135.21 revision control — every revision uniquely numbered, version-locked, and indexed to the OpSpecs amendment or regulatory change that triggered it
- §135.21(b) distribution tracking — surface which crewmembers, dispatchers, mechanics, and management personnel still owe acknowledgment on the current revision
- §135.21(g) per-recipient acknowledgment capture — date, recipient, revision number, OpSpecs paragraph, all retained for surveillance
- §135.23 content index — every required GOM content section mapped to a current GOM page or section; surfaces missing or stale §135.23 content automatically
- OpSpecs paragraph tie-back under FAA Order 8900.1 Vol. 3 Ch. 18 — every GOM/GMM section indexed against the OpSpecs paragraph it implements
- §135.25 aircraft requirements + §135.27 business office + §135.83 operating information all captured against the same revision-controlled manual repository
- One-click POI surveillance binder — produces a complete EDP-defensible packet of §135.21 + §135.23 + §135.25 + §135.27 + §135.83 + OpSpecs records in under 60 seconds
- $299/mo flat regardless of manual or recipient count — no per-manual or per-revision fees
- 5-day free trial, no credit card required, no annual contract
Limitations
- Not an aviation-specialist authoring platform — does not include built-in regulatory text libraries or industry-standard GOM templates (pair with Web Manuals or Comply365 if you need a starting template)
- Not a charter scheduling, dispatch, or flight following platform — pair with WingX, Avianis, or ARGUS PRO for live ops workflow
- Not a per-tail aviation maintenance tracking system — pair with CAMP, Veryon, or Flightdocs for inspection forecasting and AD applicability per aircraft
Our take: FileFlo is the purpose-built answer to the §135.21 + §135.23 manual revision control problem: it versions every GOM and GMM revision, distributes to the §135.21(b) required personnel, captures §135.21(g) acknowledgment per recipient, indexes every revision against the OpSpecs paragraph it implements under FAA Order 8900.1 Vol. 3 Ch. 18, and produces an EDP-defensible audit binder on demand. For Part 135 charter and on-demand operators whose primary surveillance risk is a §135.21 revision that was never distributed or a §135.23 content section that does not match current OpSpecs — not template authoring or per-tail maintenance forecasting — FileFlo fills the revision-control-and-acknowledgment gap at a flat rate that scales from a single-tail air taxi to a 50-aircraft on-demand fleet.
CAMP Systems
Best for Per-Tail GMM/MOM Maintenance Records (Aircraft-Side)Best For
Part 135 operators whose primary manual-side need is per-aircraft maintenance program documentation feeding the GMM/MOM — not §135.21 GOM revision control or §135.23 OpSpecs alignment
Key Feature
Decades-deep per-tail maintenance program documentation feeding the §135.427 maintenance manual content and the §135.443 airworthiness release procedures within the GMM/MOM
Part 135 Focus
Per-tail maintenance program documentation feeding §135.427 GMM content; secondary §135.429 RII workflow on the maintenance side; not purpose-built for §135.21 GOM revision control, §135.23 OpSpecs alignment, or §135.21(g) acknowledgment capture
Strengths
- Industry-leading per-tail maintenance records database feeding §135.427 GMM/MOM content with mature airframe and engine history
- Strong §135.443 airworthiness release support on the maintenance side of the certificate
- Deep integration with FAA AD and SB notification feeds for §91.417 aircraft record completeness
- Established vendor relationships across Part 135 charter and corporate flight departments
Limitations
- Per-aircraft pricing — costly for §135.21 GOM revision control that scales with personnel and revisions, not tails
- Not purpose-built for §135.21 GOM revision distribution under §135.21(b) or §135.21(g) acknowledgment capture
- §135.23 content section indexing and OpSpecs paragraph tie-back happen outside the platform — manual cross-referencing required
- Sales-led pricing — requires a sales engagement to evaluate
- Annual contracts standard; multi-week onboarding
- No 5-day free trial
Our take: CAMP Systems is the per-tail maintenance records incumbent feeding §135.427 GMM/MOM content and §135.443 airworthiness release. For the per-tail maintenance program documentation that lives in the GMM, CAMP is strong. For the §135.21 GOM revision control, §135.23 OpSpecs alignment, and §135.21(g) acknowledgment audit trail that an FAA POI requests during surveillance, CAMP is the wrong layer of the stack.
Veryon (Traxxall)
Best Post-Merger GMM Maintenance Records SuiteBest For
Part 135 operators that want consolidated per-tail GMM maintenance records and limited flight ops after the 2024 Traxxall + Continuum CMP rebrand
Key Feature
Combined per-tail GMM maintenance records and limited flight ops platform after Traxxall + Continuum CMP consolidation
Part 135 Focus
Per-tail GMM maintenance records + parts modules; per-aircraft architecture similar to CAMP; not purpose-built for the §135.21 GOM revision control, §135.23 content section alignment, or §135.21(g) acknowledgment chain
Strengths
- Post-2024 merger consolidated Traxxall + Continuum CMP into a single GMM-side maintenance records suite
- Cloud-first architecture with modern UI compared to legacy on-prem maintenance systems
- Strong international footprint (EASA + FAA dual-environment) for operators with cross-border charter
- Limited flight ops modules feed into the GOM maintenance-references section
Limitations
- Per-aircraft pricing — same structural mismatch as CAMP for §135.21 GOM revision control that scales with personnel and revisions
- Post-merger integration period creates feature-roadmap uncertainty on the GOM side
- Sales-led pricing — no published rates
- No purpose-built §135.21(b) distribution tracking or §135.21(g) acknowledgment capture across the personnel required to receive revisions
- Annual contracts standard; no 5-day free trial
Our take: Veryon is the rebranded post-2024 result of the Traxxall + Continuum CMP merger. For per-tail GMM maintenance records and the maintenance-side §135.427 program documentation, Veryon is competitive. For the §135.21 GOM revision control, §135.23 OpSpecs alignment, and §135.21(g) acknowledgment audit trail an FAA POI requests during surveillance, Veryon is not purpose-built.
WingX
Best Charter Scheduling, Dispatch, and Flight FollowingBest For
Part 135 charter and on-demand operators that need integrated scheduling, dispatch, quoting, crew pairing, and live flight following — with the GOM/GMM stored elsewhere
Key Feature
Purpose-built Part 135 charter scheduling, quoting, dispatch, crew-pairing, and live flight following platform with limited document storage
Part 135 Focus
Charter operations workflow — scheduling, dispatch, quoting, crew pairing, fuel uplift records, and live flight following; document storage is secondary; not purpose-built for §135.21 GOM revision control, §135.23 content alignment, or OpSpecs paragraph tie-back
Strengths
- Purpose-built Part 135 charter scheduling and dispatch workflow
- Strong adoption in mid-size on-demand and charter operators
- Live flight following helps satisfy the §135.79 monitoring expectation operationally — referenceable in the GOM
- Integrated quoting and crew-pairing reduces tool sprawl on the operations side
Limitations
- Primary value is charter operations workflow, not §135.21 manual revision control or §135.23 content management
- Per-operator pricing — not flat-rate
- No AI document classification for §135.21 GOM revisions or §135.23 content section indexing
- Limited §135.21(g) acknowledgment capture across personnel required to receive revisions
- Sales-led pricing — annual contracts standard
Our take: WingX is the Part 135 charter operations workflow incumbent. For dispatch, quoting, crew pairing, and live flight following, it is the right layer and addresses the operational side of §135.79. For the §135.21 + §135.23 + §135.21(g) manual revision audit trail an FAA POI requests during surveillance, WingX is not purpose-built — pair it with FileFlo for the certificate-side manual revision control.
Flightdocs
Best Cloud-First Maintenance Records (GMM-Side)Best For
Part 91 corporate flight departments and Part 135 charter operators that want a cloud-first per-tail GMM-side maintenance records platform — GOM revision control is secondary
Key Feature
Cloud-native per-tail maintenance records with strong mobile experience for technicians and pilots feeding the GMM/MOM
Part 135 Focus
Per-tail GMM maintenance records; secondary work order and parts modules feeding §135.427 maintenance program content; not purpose-built for §135.21 GOM revision control, §135.23 content section management, or §135.21(g) acknowledgment capture
Strengths
- Cloud-first, mobile-friendly UI ahead of legacy maintenance records systems
- Mobile §135.65 mechanical irregularity entry from the flight line feeds the GMM/MOM maintenance log workflow
- Modern API stack for integration with charter operations and dispatch platforms
- Per-tail subscription with predictable scaling for fleet operators
Limitations
- Primary value is per-tail GMM maintenance records, not §135.21 GOM revision control
- Per-aircraft pricing — structural mismatch for §135.21 manual revisions that scale with personnel and OpSpecs amendments
- No purpose-built §135.21(b) distribution tracking or §135.21(g) per-recipient acknowledgment
- No §135.23 content section index or OpSpecs paragraph tie-back
- Sales-led pricing; no 5-day free trial
Our take: Flightdocs is the modern cloud-first alternative to CAMP for per-tail GMM-side maintenance records. For operators whose primary records-side pain is the §135.21 GOM revision control layer — §135.23 content alignment, OpSpecs paragraph tie-back, and §135.21(g) per-recipient acknowledgment — Flightdocs is not the right tool. Pair it with FileFlo for the certificate-side GOM/MOM revision audit trail.
Web Manuals
Best Aviation-Specialist Manual Authoring PlatformBest For
Mid-size and larger Part 135 + 145 + 121 operators that need a built-in regulatory text library, industry-standard GOM/GMM templates, and structured authoring tooling — willing to pay aviation-specialist annual rates
Key Feature
Aviation-specialist authoring platform with built-in regulatory text libraries (FAA, EASA, ICAO) and industry-standard GOM/GMM templates
Part 135 Focus
Multi-manual authoring, versioning, and distribution; strong on §135.21 revision workflow and §135.23 content templates; aviation-specialist focus; higher annual price point than flat-rate records platforms
Strengths
- Aviation-specialist platform purpose-built for §135.21 + §135.23 manual revision workflow
- Built-in FAA/EASA/ICAO regulatory text library makes new-manual authoring faster
- Industry-standard GOM/GMM templates as starting points for small-to-mid Part 135 operators
- Strong §135.21(b) distribution + §135.21(g) acknowledgment workflow
- Established vendor across Part 135, Part 145, and Part 121 operators
Limitations
- Sales-led pricing — typical annual subscription $5,000–$25,000+/year, materially higher than flat-rate records platforms
- Per-manual or per-operator pricing — scales with manual count and recipient count
- Aviation-specialist authoring focus — not optimized for cross-regulation operators that also need OSHA, EPA, or DOT records in one platform
- Annual contracts standard; multi-week implementation timelines
- No 5-day flat-rate free trial — demo-only evaluation
Our take: Web Manuals is the aviation-specialist authoring incumbent for §135.21 + §135.23 + parallel Part 145/121 manual revision control. For operators that need built-in regulatory text libraries and industry-standard GOM/GMM templates and can absorb mid-five-figure annual subscription rates, Web Manuals is a strong fit. For Part 135 operators that already have a GOM/GMM and need the revision-control-and-acknowledgment layer without authoring tooling — at flat-rate pricing — FileFlo is structurally cheaper across the first surveillance cycle.
Paper / Word / Network Drive
The Status Quo Most Part 135 Operators Are QuittingBest For
Very small single-tail Part 135 operators with a single-pilot owner-operator structure, stable OpSpecs envelope, and no recent revision cycles
Key Feature
No software vendor relationship; full local control over the manual master file
Part 135 Focus
Whatever the director of operations or chief pilot builds in Word + a network drive — vulnerable to §135.21 revisions that never distribute, §135.23 content sections that drift from current OpSpecs, and §135.21(g) acknowledgment evidence that never gets captured during POI surveillance
Strengths
- Zero software cost
- No vendor lock-in
- Familiar to long-tenured directors of operations and chief pilots
- Works for a single-tail air taxi with one PIC, a stable OpSpecs envelope, and infrequent revision cycles
Limitations
- No structural §135.21 revision control — version numbering and revision history live in a Word document and an Outlook folder
- §135.21(b) distribution by email — recipients open and read at their own pace; no acknowledgment record under §135.21(g)
- §135.23 content sections drift from current OpSpecs paragraphs across revision cycles — the GOM and OpSpecs tell different stories
- No FAA Order 8900.1 Vol. 3 Ch. 18 revision-acceptance audit trail surfaced for POI surveillance
- No audit trail of who touched what revision when — fails §135.21 manual control intent
- Building an EDP-defensible §135.21 surveillance binder by hand takes days, not seconds
- Hidden labor cost: a director of operations spending 6+ hours/week on manual revision distribution and acknowledgment tracking costs more annually than the software
Our take: Paper, Word documents, and network drives are the status quo most Part 135 operators are actively quitting in 2026. The hidden labor cost of manual §135.21 revision distribution and §135.21(g) acknowledgment tracking plus the asymmetric downside of a single FAA Enforcement Decision Process (EDP) finding — up to $37,377/violation under 49 U.S.C. § 46301, with certificate amendment exposure for systemic findings — makes the status quo more expensive than a flat-rate manual revision platform within the first revision cycle.
Side-by-Side Comparison
All 7 platforms across the criteria that matter most for Part 135 GOM and Maintenance Manual compliance: §135.21 manual revision tracking, OpSpecs paragraph alignment under FAA Order 8900.1 Vol. 3 Ch. 18, §135.23 content section coverage, §135.21(b)+(g) distribution and acknowledgment log, pricing, and free trial.
| Criteria | FileFlo | CAMP | Veryon | WingX | Flightdocs | Web Manuals | Paper |
|---|---|---|---|---|---|---|---|
| Manual Revision Tracking | ✅ Versioned + indexed per OpSpecs | ⚠️ GMM side only | ⚠️ GMM side only | ⚠️ Limited | ⚠️ GMM side only | ✅ Authoring + versioning | ❌ Word docs |
| OpSpecs Alignment | ✅ Paragraph-to-section tie-back | ⚠️ Maintenance OpSpecs only | ⚠️ Maintenance OpSpecs only | ❌ | ⚠️ Maintenance OpSpecs only | ✅ Authoring-time alignment | ❌ Drift |
| §135.23 Content Coverage | ✅ All required sections indexed | ⚠️ §135.427 GMM only | ⚠️ §135.427 GMM only | ❌ | ⚠️ §135.427 GMM only | ✅ Aviation templates | ❌ Manual mapping |
| Distribution Log (§135.21(b)+(g)) | ✅ Per-recipient acknowledgment | ❌ | ❌ | ❌ | ❌ | ✅ Workflow capture | ❌ Email + spreadsheet |
| Pricing | $299/mo flat | ~$50–$500/aircraft | Per-aircraft | Per-operator ($500–$2,000+/mo) | Per-aircraft | $5,000–$25,000+/year | $0 + hidden labor |
| Free Trial | ✅ 5 days | ❌ Demo only | ❌ Demo only | ❌ Demo only | ❌ Demo available | ❌ Demo only | N/A |
⚠️ = partial or limited support. ❓ = unknown / not published. Data based on vendor documentation as of May 2026 and post-2024 Veryon merger context.
How to Choose the Right Part 135 GOM/MOM Compliance Platform
§135.23 Required Manual Contents
Per 14 CFR §135.23, the General Operations Manual must include — at a minimum — the names and duties of each §135.37 management person (director of operations, chief pilot, director of maintenance); procedures for ensuring compliance with aircraft weight and balance limitations; procedures for §135.79 flight locating; procedures for the assignment, release, and continuation of flight assignments; procedures ensuring each PIC is familiar with airports under §135.83; copies of the operator's Operations Specifications or appropriate extracted information including authorizations and limitations; procedures for §135.65 mechanical irregularity reporting; procedures for the §135.67 reporting of potentially hazardous meteorological conditions; the §135.63 recordkeeping procedures; and other procedures specified by the Administrator. The §135.23 content list is exhaustive on purpose — every operational procedure the certificate authorizes has to live somewhere in the GOM. The most common §135.23 finding during surveillance is a procedure operationally in use that does not appear in any §135.23 content section of the GOM, or a §135.23 section that contradicts current OpSpecs paragraphs. Compliance software must index every required §135.23 content section against a current GOM section and surface missing or stale content automatically.
FAA-Acceptable Revision Procedure (FAA Order 8900.1 Vol. 3 Ch. 18)
Per FAA Order 8900.1 Volume 3 Chapter 18 (Operations Specifications) — together with related Volume 3 chapters on §135.21 manual acceptance — every Part 135 GOM and GMM revision must follow an FAA-acceptable procedure: each revision uniquely identified (revision number, effective date), reviewed against the operator's current OpSpecs paragraphs to ensure the manual change does not exceed or contradict the OpSpecs authorization, distributed to the personnel required under §135.21(b), acknowledged by each recipient under §135.21(g), and available to the Principal Operations Inspector during surveillance. The most common finding under FAA Order 8900.1 Vol. 3 Ch. 18 is a manual revision the operator issued internally but never submitted for POI acceptance when the revision crossed an OpSpec amendment threshold, or a revision that was distributed by email but never acknowledged in writing. Compliance software must enforce the revision-acceptance-distribution-acknowledgment chain structurally — version-locking each revision, time-stamping distribution, and capturing per-recipient acknowledgment so the chain is reproducible on demand.
OpSpecs (Operations Specifications) Alignment
Operations Specifications — issued by the FAA under FAA Order 8900.1 Vol. 3 Ch. 18 — are the operator-specific authorizations, limitations, and standard procedures that the FAA approves for each Part 135 certificate. OpSpecs are issued in paragraphs (A001 General, A002 Definitions and Abbreviations, A003 Authorizations and Limitations, A025 Aircraft Authorizations, B033 IFR Approach Authorizations, B046 Special PIC Qualifications, C051 Class I Navigation, D085 Airworthiness Release, and many others). Every OpSpecs paragraph must be reflected in a §135.23 GOM content section or a §135.427 GMM content section — when OpSpecs change (FAA-issued amendment, operator-requested amendment, regulatory change), the GOM and GMM must be revised in parallel and submitted under the §135.21 revision procedure. The most common Part 135 surveillance finding is a GOM section that does not match the current OpSpecs paragraph — usually because the OpSpecs amendment took effect operationally but the GOM revision lagged by months. Compliance software must index every GOM/GMM section against the OpSpecs paragraph it implements, surface drift the moment OpSpecs change, and tie each revision to the specific OpSpecs amendment that triggered it. FileFlo treats the OpSpecs paragraph tie-back as the index key on every revision — so the §135.21 audit trail and the OpSpecs amendment history tell the same story without manual cross-referencing.
GOM vs GMM Distinction
The General Operations Manual (GOM) — sometimes called the Flight Operations Manual (FOM) — covers the operational side of the §135 certificate: §135.23 management responsibilities, §135.25 aircraft requirements, §135.27 business office, §135.79 flight locating, §135.83 operating information, §135.65 mechanical irregularity reporting on the flight crew side, crewmember duties, flight crew training and currency, and dispatch authorization procedures. The General Maintenance Manual (GMM) — sometimes called the Maintenance Operations Manual (MOM) — covers the maintenance side of the certificate when the operator maintains aircraft under its OpSpecs: §135.427 maintenance manual requirements for the maintenance program, §135.429 required inspection items (RII), §135.431 continuing analysis and surveillance, §135.433 maintenance and preventive maintenance training, §135.443 airworthiness release procedures, and the maintenance recordkeeping procedures under §135.439. Operators that contract their maintenance out to a Part 145 repair station may not maintain a separate GMM, but the GOM must reference the contract maintenance arrangement and the §135.427 maintenance program approval. Per 14 CFR §135.25, the aircraft requirements must be reflected in the GOM, and per 14 CFR §135.27, both manuals must be available at the principal business office. Compliance software must version, distribute, and prove acceptance of both manuals on parallel revision cycles tied to OpSpecs amendments — and surface §135.21 drift across the GOM/GMM boundary when an OpSpecs amendment changes both at once.
EDP Defense and POI Surveillance Binder
The FAA Enforcement Decision Process (FAA Order 2150.3C) is the administrative framework under which POI surveillance findings are investigated, dispositioned, and resolved — typically through compliance action, civil penalty, or certificate action. §135.21 findings — a GOM revision that was not distributed under §135.21(b), a §135.23 content section that does not exist in the current GOM, a GMM revision that contradicts current OpSpecs paragraphs, or a §135.21(g) acknowledgment that was never captured — are among the most consequential entries in EDP cases against Part 135 operators because §135.21 violations are typically systemic and implicate every operational record created against the missing revision. Civil penalties under 49 U.S.C. § 46301 reach $37,377 per violation in 2026. The most cost-effective structural defense is records software that versions every §135.21 revision, tracks every §135.21(b) distribution, captures every §135.21(g) acknowledgment, and ties every revision to the OpSpecs paragraph that triggered it under FAA Order 8900.1 Vol. 3 Ch. 18. FileFlo's one-click POI surveillance binder packages the §135.21 + §135.23 + §135.25 + §135.27 + §135.83 records — plus the OpSpecs paragraph cross-reference — for any time window into a single export the POI can review during a surveillance visit. The cost of reconstructing the §135.21 audit trail the morning of the POI visit plus the asymmetric downside of a civil penalty makes the records-side software pay for itself within the first revision cycle.
Part 135 GOM and GMM revisions, version-locked + acknowledgment-captured at issue
FileFlo versions every §135.21 GOM and GMM revision, distributes to the §135.21(b) required personnel, captures §135.21(g) per-recipient acknowledgment, indexes every revision against the OpSpecs paragraph under FAA Order 8900.1 Vol. 3 Ch. 18, and surfaces drift across the §135.23 + §135.25 + §135.27 + §135.83 content sections — for unlimited pilots, mechanics, manuals, and aircraft. AI document classification routes every uploaded revision to the correct OpSpecs paragraph automatically. $299/month flat, no contract, no per-manual fees.
Frequently Asked Questions
What is Part 135 GOM/MOM compliance software?
Part 135 GOM/MOM compliance software helps FAA-certificated air taxi, charter, on-demand, and commuter operators prepare, version, distribute, and prove acceptance of the two manuals required under 14 CFR §135.21 (Manual requirements) and §135.23 (Manual contents): the General Operations Manual (GOM) — sometimes called the Flight Operations Manual — and the General Maintenance Manual (GMM), often referred to as the Maintenance Operations Manual (MOM) when the operator maintains aircraft under its certificate. The best platforms version every revision against an FAA-acceptable revision procedure per FAA Order 8900.1 Vol. 3 Ch. 18, distribute revisions to the personnel required by §135.21(b), capture acknowledgment from each recipient under §135.21(g), and align manual content to the operator's OpSpecs paragraphs — closing the most common EDP finding on Part 135 surveillance visits: a manual revision that was issued internally but never distributed, acknowledged, or aligned to the operator's actual OpSpecs envelope.
What does §135.23 require the GOM to contain?
Per 14 CFR §135.23, the General Operations Manual must include — at a minimum — the names of each management person required under §135.37 (chief pilot, director of operations, director of maintenance) along with their duties, responsibilities, and authority; procedures for ensuring compliance with aircraft weight and balance limitations; procedures for compliance with §135.79 flight locating requirements; procedures for the assignment, release, and continuation of flight assignments; procedures for ensuring each pilot in command is familiar with airports under §135.83; copies of the operator's Operations Specifications (OpSpecs) or appropriate extracted information including authorizations and limitations; procedures for ensuring §135.65 mechanical irregularity reporting; procedures for the §135.67 reporting of potentially hazardous meteorological conditions; the §135.63 recordkeeping procedures; and other procedures specified by the Administrator. Section §135.23 is exhaustive on purpose — every operational procedure the certificate authorizes has to live somewhere in the GOM. The most common §135.23 finding during surveillance is a procedure operationally in use that does not appear in the §135.23 content sections of the GOM, or a §135.23 section that contradicts the operator's current OpSpecs paragraphs.
What is the difference between a GOM and a GMM/MOM?
The General Operations Manual (GOM) — sometimes called the Flight Operations Manual (FOM) — covers the operational side of the §135 certificate: §135.23 management responsibilities, §135.79 flight locating, §135.83 operating information, §135.65 mechanical irregularity reporting on the flight crew side, crewmember duties, flight crew training and currency, and dispatch authorization procedures. The General Maintenance Manual (GMM) — sometimes called the Maintenance Operations Manual (MOM) — covers the maintenance side of the certificate when the operator maintains aircraft under its OpSpecs: §135.427 maintenance manual requirements for the maintenance program, §135.429 required inspection items (RII), §135.431 continuing analysis and surveillance, §135.433 maintenance and preventive maintenance training, §135.443 airworthiness release procedures, and the maintenance recordkeeping procedures under §135.439. Operators that contract their maintenance out to a Part 145 repair station may not maintain a separate GMM, but the GOM must reference the contract maintenance arrangement and the §135.427 maintenance program approval. Compliance software must version, distribute, and prove acceptance of both manuals on parallel revision cycles tied to OpSpecs amendments, FAA Notices, and regulatory change.
What is the FAA-acceptable revision procedure under FAA Order 8900.1 Vol. 3 Ch. 18?
FAA Order 8900.1 Volume 3 Chapter 18 (Operations Specifications) — together with related Volume 3 chapters on §135.21 manual acceptance — sets the FAA expectations for how a Part 135 operator amends its GOM and GMM: each revision must be controlled (numbered or otherwise uniquely identified), the proposed revision must be reviewed against the operator's current OpSpecs paragraphs to ensure the manual change does not exceed or contradict the OpSpecs authorization, the revision must be distributed to the personnel required under §135.21(b), each recipient must acknowledge receipt under §135.21(g), and the revision must be available to the Principal Operations Inspector during surveillance. The most common finding under FAA Order 8900.1 Vol. 3 Ch. 18 is a manual revision that the operator issued internally but never submitted for POI acceptance when the revision crossed an OpSpec amendment threshold, or a revision that was distributed but never acknowledged. Compliance software must enforce the revision-acceptance-distribution-acknowledgment chain structurally — paper-based revision control routinely loses the acknowledgment evidence within the first two revision cycles.
How do OpSpecs align with the GOM and GMM?
Operations Specifications (OpSpecs) — issued by the FAA under FAA Order 8900.1 Vol. 3 Ch. 18 — are the operator-specific authorizations, limitations, and standard procedures that the FAA approves for each Part 135 certificate. OpSpecs are issued in paragraphs (A001 General, A002 Definitions and Abbreviations, A003 Authorizations and Limitations, A025 Aircraft Authorizations, B033 IFR Approach Authorizations, B046 Special PIC Qualifications, C051 Class I Navigation, D085 Airworthiness Release, etc.). Every OpSpecs paragraph must be reflected in the GOM or GMM content — when OpSpecs change (FAA-issued amendment, operator-requested amendment, regulatory change), the GOM and GMM must be revised in parallel and submitted under the §135.21 revision procedure. The most common Part 135 surveillance finding is a GOM section that does not match the current OpSpecs paragraph — usually because the OpSpecs amendment took effect operationally but the GOM revision lagged by months. Compliance software must index every GOM section against the OpSpecs paragraph it implements, surface drift the moment OpSpecs change, and tie each revision to the specific OpSpecs amendment that triggered it.
What is the §135.27 business office and operations base requirement?
Per 14 CFR §135.27, every Part 135 certificate holder must establish and maintain a principal business office, and the location of the business office and each operations base must be approved by the FAA. The principal business office is where the §135.63 records — the §135.21 manuals, the OpSpecs, the §135.63 crewmember and aircraft records, the §135.79 flight locating records, the §135.65 mechanical irregularity records, and the §135.267 crew duty time records — are maintained and made available to the Administrator. The §135.27 requirement is enforcement-relevant because a POI surveillance visit physically occurs at the principal business office, and the inability to produce a §135.21 manual revision, a §135.83 operating information record, or any other §135.23 content during the visit is itself a finding. Most modern Part 135 operators digitize records and host them in a single records repository — but the operator still must designate the §135.27 principal business office where those records are accessible. Compliance software must surface every §135.21 manual revision and every §135.23 content section at the §135.27 business office on demand.
How much does Part 135 GOM/MOM compliance software cost?
Pricing splits across the same three categories as broader Part 135 compliance tooling. Aviation-specialist manual platforms (Web Manuals, AvOps, Comply365) handle multi-manual versioning, distribution, and revision control for Part 135 + 145 + 121 operators — priced per-manual or per-operator under sales-led annual contracts, typically $5,000–$25,000+/year. Per-tail maintenance platforms (CAMP Systems, Veryon/Traxxall, Flightdocs) include limited GMM/MOM content management but are not purpose-built for §135.21 GOM revision control or §135.23 OpSpecs alignment — per-aircraft pricing $30–$500/tail/month. Charter operations platforms (WingX) handle dispatch and live flight following but thin on §135.21 manual revision workflow. Document-side compliance platforms (FileFlo) version, distribute, and prove acceptance of both the GOM and GMM/MOM, align every revision to OpSpecs paragraphs under FAA Order 8900.1 Vol. 3 Ch. 18, capture §135.21(g) acknowledgment from each recipient, and surface stale §135.23 content sections — $299/month flat for unlimited pilots, mechanics, manuals, and aircraft. Most Part 135 operators need software from at least two categories, and the manual revision layer is the one that most directly drives §135.21 EDP findings.
What FAA civil penalty applies to §135.21 GOM/MOM violations?
Under 49 U.S.C. § 46301(a)(1), the FAA may impose civil penalties up to $37,377 per violation for most Part 135 regulatory violations as of the 2026 inflation-adjusted schedule (penalties adjusted annually under the Federal Civil Penalties Inflation Adjustment Act). Manual-side findings — a §135.21 GOM revision that was not distributed under §135.21(b), a §135.23 content section that does not exist in the current GOM, a GMM revision that contradicts the operator's current OpSpecs paragraphs, or a §135.21(g) acknowledgment that was never captured — are some of the most common entries in EDP cases against Part 135 operators because §135.21 violations are typically systemic (one missing revision implicates every record created against it). Repeat or systemic findings under §135.21 can result in compliance action, certificate amendment, or certificate suspension exposure for charter and air ambulance operators with patterned findings. The §135.21 audit trail is the spine of every Part 135 surveillance visit — and the cost of reconstructing it the morning of the POI visit is the asymmetric exposure that justifies records software inside the first revision cycle.
Stop reconstructing §135.21 manual revisions the morning of the POI surveillance visit
FileFlo holds the §135.21 GOM and GMM revision audit trail across every revision cycle. §135.23 content section index, §135.21(b) distribution tracking, §135.21(g) per-recipient acknowledgment, §135.25 aircraft requirements documentation, §135.27 business office records repository, §135.83 operating information files, and OpSpecs paragraph tie-back under FAA Order 8900.1 Vol. 3 Ch. 18 — all for $299/month flat, no contract, no per-manual fees, no per-revision fees.
5-day free trial · No credit card required · Cancel anytime