What Are Operating Specifications?
Operating specifications—commonly called "OpSpecs"—are the legally binding documents issued by the FAA to each air carrier certificate holder that define, in precise detail, the conditions and limitations under which that carrier is authorized to operate. They are not suggestions or guidelines; they carry the full weight of federal regulatory authority. Under 14 CFR Part 119, every air carrier holding an Air Carrier Certificate or an Operating Certificate is required to have OpSpecs, and the carrier must conduct all operations in strict compliance with those specifications.
Think of OpSpecs as the individualized rulebook that sits on top of the general regulations. While 14 CFR Parts 121, 135, and 125 establish the minimum standards that apply to all operators in their respective categories, OpSpecs translate those standards into carrier-specific authorizations. One airline may be authorized to conduct Category III instrument approaches; another may not. One carrier may be approved for Extended Operations (ETOPS); another's OpSpecs may prohibit overwater flights beyond a certain distance. These distinctions are all captured in the OpSpecs.
The Legal Basis and Regulatory Framework
The authority for operating specifications flows directly from 49 U.S.C. § 44705, which empowers the FAA Administrator to issue air carrier operating certificates and to establish terms, conditions, and limitations on those certificates. Congress delegated this authority so that the FAA could tailor safety requirements to the complexity of each individual carrier's operation rather than applying a rigid, one-size-fits-all standard.
Under 14 CFR § 119.7, the certificate holder must keep a copy of its OpSpecs at its principal base of operations, and the OpSpecs must be made available for inspection by the FAA at any time. Under 14 CFR § 119.9, no person may operate as an air carrier without complying with the OpSpecs. This means crewmembers, dispatchers, maintenance personnel, and every other employee whose duties touch on the operation are legally bound by the contents of those specifications—not just the company's management.
Violations of OpSpecs are treated identically to violations of the FARs themselves. The FAA may pursue certificate action, civil penalties, or both against the carrier and, in some cases, against individual certificate holders (such as pilots holding ATP certificates) who knowingly operate outside the authorizations contained in the OpSpecs.
Structure and Organization of OpSpecs
FAA-issued OpSpecs are organized into standardized paragraphs, each identified by a letter prefix that indicates the general category of authorization:
- A-paragraphs cover general authorizations and limitations, including the types of operations the carrier is authorized to conduct (e.g., scheduled passenger operations, cargo operations, on-demand charter), the geographic scope, and the applicable regulatory part.
- B-paragraphs address en route authorizations, including the specific airways, routes, and areas of operation permitted. ETOPS authorizations, polar route approvals, and oceanic/remote area authorizations appear here.
- C-paragraphs cover airports and other ground facilities, including the specific airports the carrier is authorized to use as destinations, alternates, or diversions, along with any special airport authorizations such as those for airports requiring special terrain training.
- D-paragraphs establish aircraft-specific authorizations, including which aircraft types and registration numbers are on the carrier's operating certificate, approved maintenance programs, and minimum equipment list (MEL) approvals.
- E-paragraphs cover personnel and training authorizations, specifying approved training programs, checking programs, and qualification requirements that may deviate from or supplement the regulatory baseline.
Each paragraph within these categories is identified by a number (e.g., A001, B050, D085). The FAA and industry both reference these paragraph designators in correspondence, inspection reports, and legal proceedings, so familiarity with the structure is essential for anyone working in air carrier operations.
How OpSpecs Are Issued and Amended
OpSpecs are issued by the carrier's Certificate Holding District Office (CHDO)—the FAA Flight Standards District Office (FSDO) assigned geographic responsibility for that carrier. The CHDO works through a Principal Operations Inspector (POI), a Principal Maintenance Inspector (PMI), and a Principal Avionics Inspector (PAI) who together evaluate the carrier's applications, conduct inspections, and ultimately recommend approval or denial of specific OpSpec paragraphs to the FAA.
When a carrier seeks a new authorization—say, approval to conduct Category II instrument approaches or to add a new aircraft type—it must submit a formal request to its CHDO supported by documentation demonstrating compliance. This might include revised training syllabi, revised maintenance procedures, simulator evaluations, and route proving flights. The FAA does not simply grant requests; each new or amended paragraph must be supported by evidence that the carrier can safely conduct the proposed operation.
Amendments to OpSpecs may be voluntary (carrier-initiated) or involuntary (FAA-initiated). If the FAA determines that safety concerns warrant the removal or restriction of an existing authorization—for example, after an accident investigation reveals a systemic problem—it can amend the OpSpecs unilaterally. The carrier has appeal rights under 14 CFR Part 13, but in urgent safety situations the FAA may make the amendment effective immediately pending any appeal.
OpSpecs vs. the General Operating Manual and Other Documents
Students often confuse OpSpecs with other carrier documents such as the General Operations Manual (GOM), the Flight Operations Manual (FOM), or the Minimum Equipment List (MEL). Here is how they relate:
- The OpSpecs are the FAA-issued legal authority. They define the outer boundary of what is permitted.
- The GOM and FOM are carrier-developed internal documents that describe how the carrier will conduct operations within those boundaries. They must be consistent with the OpSpecs but cannot expand beyond them.
- The MEL is derived from the Master Minimum Equipment List (MMEL) developed by the FAA and the aircraft manufacturer, but the carrier's specific MEL is approved as part of its OpSpecs (typically in the D-paragraphs). The MEL cannot be less restrictive than the MMEL.
When a conflict exists between the OpSpecs and any internal carrier document, the OpSpecs govern. A carrier policy manual that attempts to authorize something the OpSpecs do not approve is legally void with respect to that authorization.
Why OpSpecs Matter to Pilots and Crew
For an ATP-certificate holder flying under Part 121 or Part 135, understanding OpSpecs is not merely an academic exercise. As noted above, individual crewmembers are bound by the carrier's OpSpecs. If a captain accepts a clearance to conduct an approach category that the airline's OpSpecs do not authorize—for instance, a Category III approach to an airport or with equipment not approved in the OpSpecs—that captain has violated federal regulations, regardless of the fact that the approach itself is generally legal under the FARs.
Aircraft dispatchers (certificated under 14 CFR Part 65, Subpart C) share legal responsibility for flights under Part 121's system of shared operational control. That system requires both the PIC and the aircraft dispatcher to co-sign the release for each flight, and both are responsible for ensuring the planned operation complies with the OpSpecs. A dispatcher who releases a flight to an airport not listed in the C-paragraphs is as legally exposed as a pilot who flies there.
Common Test Traps
- OpSpecs are not optional internal policies. They carry the same legal force as the FARs themselves. A carrier (or individual) who violates them violates federal law.
- Not all carriers have the same authorizations. Just because one Part 121 carrier is approved for ETOPS or Category III approaches does not mean all are. Approvals are specific to each carrier's OpSpecs.
- The MEL is part of the OpSpecs. The MEL is approved through the D-paragraphs; it is not a standalone document with independent legal authority. Its authority comes from its incorporation into the carrier's OpSpecs.
- The CHDO and POI are the primary FAA contacts. ATP written test questions sometimes probe whether applicants understand that OpSpecs are managed at the district level through the CHDO, not by FAA headquarters directly.
- Both the PIC and the dispatcher are legally bound. Under Part 121, the shared operational control system means that compliance with OpSpecs is not the pilot's burden alone—the dispatcher shares equal legal responsibility for any OpSpec violation embedded in a dispatch release.