14 CFR § 135.21
Manual requirements
See your compliance status for this section
3-minute free audit. CFR-cited gap report. No signup.
What does 14 CFR § 135.21 require?
14 CFR 135.21 is the cornerstone of Part 135 compliance — the manual rule. Every Part 135 certificate holder (except single-pilot operators under §135.3) must prepare and keep current a written operations manual setting forth the operator's procedures and policies acceptable to the FAA. The manual is two-part in practice: a General Operations Manual (GOM) covering flight operations + dispatch + ground procedures + emergency response, and a General Maintenance Manual (GMM) covering maintenance program + recordkeeping + inspection procedures. The manual must be distributed to all flight, ground, and maintenance personnel who need it to perform their duties, and revisions must be furnished using an FAA-acceptable revision procedure documented in the operator's Operations Specifications. Manual-related findings are one of the most-cited Part 135 enforcement categories during FAA surveillance — outdated content, missing distribution records, and procedures that don't match the operator's actual OpSpecs are the most common triggers.
Regulation text (summary)
§135.21(a) requires each certificate holder, other than one who uses only one pilot in the certificate holder's operations, to prepare and keep current a manual setting forth the certificate holder's procedures and policies acceptable to the Administrator. The manual must be made available to the certificate holder's flight, ground, and maintenance personnel in the performance of their duties. §135.21(c) requires the manual to be kept current — revisions must be furnished to all personnel required to use the manual, with revision dates and an FAA-acceptable revision procedure documented in the operator's Operations Specifications. §135.23 specifies the required contents of the manual (General Operations Manual and General Maintenance Manual content), and §135.25 + §135.27 + §135.83 establish parallel manual-availability requirements for flight crew, dispatch personnel, and maintenance personnel.
Read full regulation at eCFR.govWho must comply with 14 CFR § 135.21?
All FAA Part 135 certificate holders (air taxi, commuter, on-demand operators) except (1) single-pilot operators authorized under §135.3 — the rule's stated exception for certificate holders using only one pilot in operations — and (2) helicopter operators conducting operations specifically excluded under §135.1(c). Approximately 2,000+ Part 135 certificate holders in the US are in scope. Single-pilot operators remain subject to other §135 documentation requirements (training records per §135.63, recordkeeping, OpSpecs) even when exempt from the §135.21 manual requirement itself.
What happens if you violate 14 CFR § 135.21?
FAA civil penalties: $1,500–$25,000 typical for manual-related violations; higher for systemic findings or willful non-compliance. Manual deficiencies are routinely cited during §135.421 surveillance inspections and pre-renewal Operations Specifications reviews. Common findings include: (1) outdated manual content that no longer matches current OpSpecs or aircraft configuration, (2) missing or incomplete distribution records showing which personnel received which revisions, (3) procedures that conflict with the operator's FAA-approved training program, and (4) electronic-distribution access failures during ramp checks where flight crew cannot produce required manual sections. Per FAA Enforcement Decision Process summaries, manual-related findings are one of the top-cited Part 135 enforcement categories — driving certificate-action exposure where systemic. Repeated findings can lead to increased FAA surveillance frequency, mandatory corrective action plans, and in severe cases certificate suspension or revocation.
Penalty range
Annual citations
YoY penalty trend
How to comply (implementation checklist)
- 1Draft the General Operations Manual (GOM) covering all §135.23 required contents — flight operations procedures, dispatch + flight following, weight + balance, weather minimums, emergency procedures, security, OpSpecs cross-reference, and operator-specific procedures reflecting the operator's actual aircraft + authorizations.
- 2Draft the General Maintenance Manual (GMM) covering the maintenance program required under §135.427 through §135.443 — inspection program, RII (Required Inspection Items) procedures, parts traceability, recordkeeping, and the maintenance organization's procedures + responsibilities.
- 3Document an FAA-acceptable revision procedure in the operator's Operations Specifications (typically OpSpec A005 or equivalent) — defining how revisions are proposed, FAA-coordinated where required, approved internally, distributed, and acknowledged. Per FAA Order 8900.1 Vol. 3 Ch. 18, revision procedures are coordinated with the operator's Principal Operations Inspector (POI).
- 4Maintain a distribution log showing which manual revision was provided to each flight, ground, and maintenance personnel member required to use the manual, including revision number, date provided, and acknowledgment of receipt. Distribution records are routinely reviewed during §135.421 surveillance.
- 5Perform at minimum an annual review of the entire manual for currency — but revise immediately whenever procedures, equipment, OpSpecs authorizations, training programs, or applicable regulations change. Annual review is the floor, not the ceiling, of the keep-current obligation.
- 6Cross-check manual content against the operator's current Operations Specifications — every OpSpec authorization (RVSM, RNP, LOA, training authorization, geographic limitation) must have corresponding manual procedures. Surveillance findings frequently catch manual content that lags an OpSpec change.
- 7Conduct a compliance review of the full manual prior to any scheduled FAA inspection (SVE, §135.421 surveillance, OpSpecs renewal) — verifying distribution completeness, currency against OpSpecs, alignment with training program, and electronic-access reliability in the field.
Common misinterpretations
- Misinterpretation: 'Single-pilot operators are exempt from any manual requirement.' Reality: §135.3 provides the single-pilot exemption from the §135.21 manual requirement specifically, but other §135 documentation requirements still apply. Single-pilot operators must still maintain training records per §135.63, OpSpecs, MEL documentation, weight + balance records, and the airworthiness recordkeeping required under §135.421 + Part 91. The exemption is narrow — it removes the obligation to prepare a formal operations manual, not the obligation to document operations and maintenance.
- Misinterpretation: 'The manual can be the FAA's standard manual or a generic industry template.' Reality: §135.21(a) requires the manual to set forth THIS operator's procedures and policies acceptable to the Administrator — meaning operator-specific content reflecting the operator's actual aircraft, OpSpecs authorizations, training program, and operational environment. A generic template downloaded from a trade association is not compliant; FAA Principal Operations Inspectors (POIs) routinely cite manuals that do not reflect operator-specific procedures during surveillance. The manual must match what the operator actually does, not what a template says.
- Misinterpretation: 'Annual review is enough to satisfy the keep-current requirement.' Reality: §135.21(c) requires the manual to be kept CURRENT — meaning revised whenever procedures, equipment, OpSpecs authorizations, personnel qualification standards, or applicable regulations change. Annual review is a minimum hygiene practice, not the standard. If the operator adds a new aircraft type, modifies an OpSpec, changes a training curriculum, or adopts a new regulatory requirement, the manual must be revised promptly under the FAA-acceptable revision procedure documented in the operator's OpSpecs — not held for the next annual review cycle.
- Misinterpretation: 'Electronic distribution satisfies the access requirement without further procedure.' Reality: §135.21(d) requires the manual to be readily accessible to personnel in the performance of their duties. Electronic distribution (PDF on a tablet, EFB, cloud document portal) is acceptable when access is reliable in the field — but the procedure must actually work where it needs to. Flight crews need access in the aircraft (EFB battery + connectivity considerations), maintenance personnel need access on the hangar floor, and ground personnel need access at the dispatch station. Electronic-only distribution that fails during ramp checks or in remote operations is non-compliant, regardless of how robust the cloud portal looks at HQ. Most operators retain a paper backup or offline-cached copy for this reason.
Real enforcement examples
Anonymized from public FMCSA enforcement summaries. Penalty amounts reflect assessed and final settled values where disclosed.
Part 135 on-demand charter operator received a $22,000 FAA civil penalty in 2024 after a §135.421 surveillance inspection identified multiple §135.21 findings: (1) the General Operations Manual had not been revised to reflect an OpSpec change authorizing a new aircraft type that had been added 11 months earlier, (2) distribution records showed two flight crew members had never acknowledged receipt of the prior three revisions, and (3) the GOM's emergency procedures section conflicted with the operator's FAA-approved training program. Corrective action plan required full manual reissue under a revised OpSpec A005 revision procedure plus mandatory distribution acknowledgment from all personnel within 60 days. Operator's surveillance frequency was increased pending corrective-action close-out.
Source: FAA Enforcement Decision Process summaries, anonymized; consistent with FAA Compliance + Enforcement Program reporting in FAA Order 2150.3C
How FileFlo handles 14 CFR § 135.21
FileFlo's compliance rule-pack FAA-14CFR135.21 automatically checks every document you upload against this regulation. Auto-detects document type, parses key fields, sets renewal alerts, and surfaces this section in your audit binder if a gap is found.
Already evaluating? Start a 5-day free trial →
Frequently asked questions
What's the difference between the GOM and the GMM?▾
The General Operations Manual (GOM) covers flight operations: dispatch procedures, weight + balance, weather minimums, flight following, emergency procedures, security, crew duties, OpSpecs cross-reference, and operator-specific procedures reflecting how the operator actually conducts flights. The General Maintenance Manual (GMM) covers the maintenance program required under §135.427 through §135.443: inspection program, Required Inspection Items (RII) procedures, parts traceability, return-to-service procedures, recordkeeping, and the maintenance organization's structure + responsibilities. §135.21(a) does not literally name 'GOM' and 'GMM' — those are the industry-standard names operators use to organize the manual content that §135.23 + §135.427 require. Many operators issue both as separate physical or electronic volumes for distribution to different personnel groups (flight crew get the GOM; maintenance personnel get the GMM; some personnel groups receive both). The combined content is collectively 'the manual' under §135.21.
Do single-pilot operators really not need a manual at all?▾
Single-pilot operators authorized under §135.3 are exempt from the §135.21 manual requirement itself, but not from other Part 135 documentation requirements. The single-pilot operator must still maintain: training records per §135.63, current Operations Specifications, MEL where applicable, weight + balance documentation, airworthiness records per §135.421 + Part 91, drug + alcohol testing records per 49 CFR Part 120, and any documentation specifically required by OpSpec authorizations (RVSM, RNP, LOA, etc.). The §135.21 exemption is narrow — it removes the obligation to prepare a formal operations manual, not the obligation to document operations + maintenance. Most single-pilot operators voluntarily maintain a streamlined operations checklist or procedures binder because the underlying documentation is required regardless of the manual-rule exemption.
How often must the manual be updated?▾
§135.21(c) requires the manual to be kept current — meaning revised whenever procedures, equipment, OpSpecs authorizations, training programs, personnel qualification standards, or applicable regulations change. There is no fixed revision interval prescribed in §135.21; the keep-current obligation is event-driven. Annual review is a widely-accepted minimum hygiene practice but does not satisfy the rule when a triggering change has occurred between reviews. Operators with FAA-acceptable revision procedures documented in OpSpec A005 (or equivalent) typically batch minor revisions on a defined cadence (quarterly or semi-annually) and issue out-of-cycle revisions when an OpSpec change, new aircraft addition, or regulatory amendment occurs. Distribution records must show the revision was furnished to all required personnel under the revision procedure.
Who is required to have the manual?▾
§135.21(b) + (d) require the manual to be made available to the certificate holder's flight, ground, and maintenance personnel in the performance of their duties — meaning personnel who need the manual to do their job receive access. In practice this covers: all flight crew (PIC, SIC, flight attendants on applicable aircraft), dispatchers + flight followers, maintenance personnel including A&P mechanics + inspectors + RII inspectors, ground operations personnel involved in dispatch + weight + balance + servicing, and management personnel with operational responsibility. Distribution can be tiered — flight crew receive the GOM, maintenance personnel receive the GMM, dispatchers receive relevant GOM sections — but the rule requires personnel to have access to the portions they need for their assigned duties. §135.83 + §135.25 + §135.27 establish parallel availability requirements for specific personnel categories. Distribution records must demonstrate which personnel received which revisions.
What does an FAA-acceptable revision procedure require?▾
Per §135.21(c) and FAA Order 8900.1 Vol. 3 Ch. 18, the operator's revision procedure must be documented in the Operations Specifications (typically OpSpec A005 or the operator's equivalent) and coordinated with the operator's Principal Operations Inspector (POI). The procedure typically defines: (1) how revisions are proposed and authored, (2) whether the revision requires FAA coordination or approval (some changes — e.g., OpSpec-driven revisions — require FAA review prior to issue; others can be self-approved by the operator under the operator's revision authority), (3) how revisions are numbered + dated + identified with change bars or revision notation, (4) how revisions are distributed to required personnel, and (5) how acknowledgment of receipt is recorded. The procedure must be followed every time the manual is revised; failure to follow the operator's own revision procedure is itself a §135.21 finding even when the underlying revision content is correct. Most operators retain a controlled revision log + distribution log as part of the manual's front matter for surveillance review.
Does electronic distribution (EFB, tablets, cloud portal) satisfy §135.21?▾
Yes — electronic distribution is acceptable when access is reliable in the field for personnel performing their duties. Most modern Part 135 operators distribute the GOM via Electronic Flight Bag (EFB) tablets to flight crew and via a maintenance cloud portal to maintenance personnel, with the revision procedure handling push-updates and acknowledgment tracking electronically. Three practical considerations apply: (1) the access procedure must work in the field — flight crews need access in the aircraft (EFB battery + offline cache + connectivity considerations), maintenance personnel need access on the hangar floor, and ground personnel need access at the dispatch station, (2) revision distribution + acknowledgment records must demonstrate that each required personnel member received and acknowledged each revision — electronic logs are acceptable when they capture revision ID + personnel ID + timestamp, and (3) most operators retain a paper backup or offline-cached copy as a fallback against electronic-access failures during ramp checks or in remote operations. Electronic-only distribution that fails during a surveillance inspection is non-compliant regardless of how robust the cloud portal looks at HQ.
Related regulations
Sources + reviewer
Primary source: eCFR.gov — 14 CFR § 135.21
Reviewed by Chad Griffith (Founder + CEO, FileFlo) on