Direct Answer
To do more under Part 135 — add IFR, a new area of operations, overwater/Class II navigation, or another authorization — you amend your operations specifications under 14 CFR §119.51, not your certificate. You apply to the responsible Flight Standards office, the FAA reviews it, and the new authority is legal only once the amended OpSpec is issued.
Timing follows §119.51(c)(1): most amendments are filed at least 15 days ahead, but the bigger ones — a change in the kind of operation under §110.2, mergers, acquisitions needing an added safety showing, resumption after bankruptcy, or introducing an aircraft not before proven — must be filed at least 90 days ahead. Some additions also require a demonstration: validation tests, or proving tests under §135.145.
FileFlo does not file your amendment, decide whether you qualify, or run your proving tests. What it does is keep the records that prove each authorization — your OpSpec versions, the amendment paperwork and FAA correspondence, the proving/validation records, and the supporting manuals and LOAs — organized and audit-ready.
Your Certificate Says What. Your OpSpecs Say How Much.
A Part 135 air carrier certificate is, by itself, fairly bare. It says you are authorized to conduct commuter and on-demand operations. The detail — every operation you may actually fly, every authorization, every limitation — lives in your operations specifications. That is by design. 14 CFR §119.1(b)(2) says the rules prescribe the certification requirements an operator must meet to hold a certificate “and operations specifications for each kind of operation to be conducted and each class and size of aircraft to be operated.” Your authority is granular, and it is granular in the OpSpecs.
So when an operator says “we want to add IFR” or “we want to start flying the Bahamas” or “we’re adding single-engine IFR,” the mechanism is always the same: an OpSpec amendment. You are not reissuing your certificate; you are asking the FAA to add a paragraph to the document that defines what you are allowed to do. The governing rule for that process is §119.51, “Amending operations specifications.”
This article is about adding kinds of operations, authorizations, and areas — the “what are we allowed to do” side. It is the companion to our guide on adding an aircraft, which is the separate “what airframe are we allowed to fly” side. If you have not read it yet, start with operations specifications (OpSpecs) explained for what these documents are in the first place, then adding an aircraft to a Part 135 certificate (conformity) for the airframe side.
The authority is the issued OpSpec — not the request
The single most expensive mistake here is flying the new operation before the amended OpSpec is actually issued. A pending application is not authority. Under §119.51 the responsible Flight Standards office adopts, partially adopts, or denies the amendment, and a holder-requested amendment is effective on the date the Administrator approves it. Until that date, the operation is outside your authorizations. Plan your customer commitments and aircraft schedule around the issued date, never the filed date.
Two Different Amendments: Adding a Kind of Operation vs Adding an Aircraft
People routinely collapse these into one idea — “we’re adding to our 135” — but the FAA treats them as two distinct OpSpec changes, and the evidence each one requires is different. The cleanest way to see why is the text of §119.1(b)(2): your operations specifications exist for each kind of operation to be conducted and each class and size of aircraft to be operated. Two separate axes, two separate amendments.
| Adding a kind of operation / authorization (this guide) | Adding an aircraft (separate guide) | |
|---|---|---|
| What changes? | What you are allowed to do — IFR, overwater, a new area, single-engine IFR, EWINS, special authorizations | What airframe you are allowed to operate — a specific tail / make & model |
| CFR mechanism | OpSpec amendment under §119.51 | OpSpec amendment under §119.51 (plus conformity) |
| Core evidence the FAA wants | Manuals, training, and a validation that you can do the new thing safely | Aircraft conformity inspection; proving for a new type not before proven |
| Typical demonstration | Validation test under §135.145(d), where required | Conformity; proving tests under §135.145(a)/(b) for certain new aircraft |
| When 90 days applies | If it is a change in the kind of operation per §110.2 | If you are introducing an aircraft not before proven |
“Kind of operation” is a defined term — and narrower than you might think
The 90-day trigger keys off a change in the kind of operation as defined in §110.2. And §110.2 defines “kind of operation” precisely: “one of the various operations a certificate holder is authorized to conduct, as specified in its operations specifications, i.e., domestic, flag, supplemental, commuter, or on-demand operations.” So moving between, say, on-demand and commuter is a change in kind of operation. Adding IFR or an EWINS authorization is adding an authorization within your existing kind of operation — still a §119.51 amendment, but not necessarily the 90-day kind. Knowing which bucket your change falls into is exactly the kind of question to confirm with your principal inspector before you file.
Because the two are separate, you can be adding an aircraft and a new authorization at the same time, or just one. Don’t assume that authority to fly a new tail comes bundled with authority for a new operation, or vice versa. For the airframe side end to end, see adding an aircraft to a Part 135 certificate (conformity); for what your authorizations even are, see OpSpecs, MSpecs & LOAs explained.
The 90-Day vs 15-Day Filing Rule (and Why It Is Not Your Approval Date)
When a certificate holder applies for an amendment, §119.51(c) sets minimum lead times — how far ahead of your desired effective date you must file. There are two tiers.
File at least 90 days ahead
§119.51(c)(1)(i) — the bigger changes
- A change in the kind of operation as defined in §110.2
- Mergers
- Acquisitions of airline operational assets that require an additional showing of safety (e.g., proving tests)
- Resumption of operations following a suspension as a result of bankruptcy actions
- The initial introduction of aircraft not before proven for use in air carrier or commercial operator operations
File at least 15 days ahead
§119.51(c)(1)(ii) — in all other cases
Every amendment that is not on the 90-day list defaults to a minimum 15-day filing window before your proposed effective date. The rule also allows a shorter time if the FAA approves it. In practice many routine additions live here — but “routine” is the inspector’s call, not yours.
A filing window is not a turnaround promise
This is the most common misread of §119.51. “At least 15 days” and “at least 90 days” are minimum lead times for filing — they tell you how early to apply, not how quickly the FAA must approve. The actual calendar depends on FAA workload, whether validation or proving tests are required and how those go, and how complete your application and supporting manuals are. Treat the statutory windows as the floor and build real margin on top — especially when a demonstration flight has to be scheduled.
How the amendment moves through Flight Standards
You apply
You file an application to amend your operations specifications with the responsible Flight Standards office, in the form and manner prescribed, at least 15 or 90 days before your proposed effective date (§119.51(c)(1)–(2)).
The FAA evaluates — and may want a demonstration
The inspector reviews your manuals, training, and supporting documentation, and determines whether a validation test (or, for a new aircraft, proving tests) under §135.145 is required before the authority can be granted.
The FAA decides
Per §119.51(c)(3), the office notifies you of adoption, partial adoption, or denial of the amendment you applied for.
It becomes effective when approved
§119.51(c)(4): once approved — following coordination with you on implementation — the amendment is effective on the date the Administrator approves it. That issued date, not your filing date, is when the new operation is legal.
The FAA can also amend your OpSpecs without you asking
§119.51(a) lets the Administrator amend OpSpecs when the holder applies or when the FAA determines safety and the public interest require it. For an FAA-initiated change, §119.51(b) gives you written notice, a reasonable period of not less than 7 days to respond, and an effective date generally not less than 30 days after you receive notice (subject to emergency action or reconsideration). Either way, if a holder-requested amendment is denied, §119.51(d) lets you petition for reconsideration within 30 days of the notice. The point: your authorizations are a living document that can change in both directions, so a clean version history is not optional.
If an inspector asked which OpSpec was in force on a given flight, could you show it?
FileFlo does not file your amendment or get your authorization issued — that is your management team and your FAA Flight Standards office. What it does is the records work that makes a new authorization provable: classifying and version-controlling your OpSpec pages, the amendment application and FAA correspondence, the validation/proving test records, and the manuals and LOAs that supported it — with effective dates, so the operative version on any date is never in doubt. Starter at $89/mo, Professional at $299/mo. 5-day free trial, no credit card required.
When You Have to Prove It First: Validation and Proving Tests
Adding an authorization is not always a paperwork-only exercise. For certain operations the FAA wants you to demonstrate that you can actually do the new thing safely before it signs the OpSpec. 14 CFR §135.145 draws a line between two kinds of demonstration, and it is worth understanding which one a given addition triggers.
Proving tests — about the aircraft
Required when you introduce certain aircraft not previously proven under Part 135 — a turbojet, or an aircraft requiring two pilots under VFR. The rule sets at least 25 hours of proving tests acceptable to the Administrator, including:
- Five hours of night time, if night flights are to be authorized
- Five instrument approach procedures, if IFR flights are to be authorized
- Entry into a representative number of en route airports
Validation tests — about the operation
Required to confirm you can conduct an operation safely and in compliance. §135.145(d) lists the authorizations that need validation:
- Addition of an aircraft of a type not previously proven or validated
- Operations outside U.S. airspace
- Class II navigation authorizations
- Special performance or operational authorizations
A few practical notes from the text itself. Validation tests must use methods acceptable to the Administrator, and an actual flight may not be required where you can demonstrate competence and compliance without one — so “validation” does not always mean a flight. Proving and validation tests may be conducted simultaneously when appropriate. And the Administrator may authorize deviations where special circumstances make full compliance unnecessary. None of that is a license to skip the demonstration; it is flexibility the FAA controls, not the operator.
“Add a new area” can pull in more than you think
Expanding where you fly is a classic example of a deceptively simple-sounding addition. A domestic area addition may be straightforward; but operations outside U.S. airspace are squarely on the §135.145(d) validation list, and an international expansion can drag in Class II navigation, RVSM, and other authorizations — each its own OpSpec or letter of authorization with its own evidence. Scope the whole chain of authorizations a new area requires before you commit to a date, and confirm it with your inspector.
For the proving-and-validation mechanics in depth — what counts as 25 hours, how the FAA scopes the en route airport requirement, and how this interacts with adding a new type — see Part 135 proving runs requirements, and for the airframe-conformity side, adding an aircraft to a Part 135 certificate (conformity).
The Records Behind Every Authorization You Hold
Here is where the certification work hands off to a documentation one — and where FileFlo fits. The job of getting an authorization issued belongs to your management team, your inspector, and (where law is involved) your aviation attorney. But once it is issued, the authorization only does you good if you can prove it on demand. An OpSpec amendment generates a specific set of records, and an FAA surveillance audit will expect to see them line up. These are the record families a new authorization produces, and how FileFlo keeps them audit-ready.
Current and superseded OpSpec pages
Why it matters
The issued OpSpec paragraph that grants the new authority, plus every prior version. When an inspector asks which authorizations were in force on a given flight date, you need the operative version — and proof of what it superseded.
How FileFlo keeps it audit-ready
FileFlo version-controls each OpSpec page with effective dates and a retained history, so the operative version on any date is unambiguous and the supersession chain is intact.
The amendment application & FAA correspondence
Why it matters
Your filed application to amend, and the FAA notice of adoption, partial adoption, or denial under §119.51(c)(3) — plus any petition for reconsideration under §119.51(d). This is the paper trail that shows the authority was granted properly.
How FileFlo keeps it audit-ready
FileFlo classifies and indexes the application and FAA letters together, time-stamped, so the full request-to-issuance story is one search away.
Proving & validation test records
Why it matters
Where a demonstration was required — proving-test hours and content, or the validation test results — the records showing it was accomplished by methods acceptable to the Administrator. These are the evidence that backs the authorization the OpSpec grants.
How FileFlo keeps it audit-ready
FileFlo indexes the proving/validation records against the authorization they supported, so the demonstration behind an authority is retrievable, not lost in a flight-ops folder.
Supporting manuals, training & companion LOAs
Why it matters
The manual revisions and training records that supported the new operation, plus the companion authorizations a change often requires — RVSM, Class II navigation, EWINS, and other LOAs/MSpecs — each with its own validity and renewal date.
How FileFlo keeps it audit-ready
FileFlo tracks manual revisions, training currency, and each companion authorization with expiration alerts, so a lapsed LOA does not quietly invalidate the operation it supports.
Related reading: OpSpecs, MSpecs & LOAs explained · Adding an aircraft (conformity) · Part 135 proving runs requirements · What records a Part 135 operator must keep · What is operational control in Part 135
FileFlo is the records layer — not your certification team, not legal counsel, not your tax advisor
To be unambiguous: FileFlo is a compliance document intelligence platform that classifies, indexes, version-controls, and tracks expirations on your compliance documents. It does not file your OpSpec amendment, decide whether you qualify for an authorization, run your proving or validation tests, get the amendment issued, structure your entity, or provide legal, financial, or tax advice. Whether and how to add a kind of operation is a matter for your management team and your FAA Flight Standards office (with an aviation attorney where law is involved, and a tax advisor on tax). Once an authorization is issued, keeping the records that prove it — complete, current, and audit-ready — is the document problem FileFlo solves. (FileFlo does not claim SOC 2 certification.)
Frequently Asked Questions
How do I add operations to a Part 135 certificate?
You do not edit your certificate — you amend your operations specifications (OpSpecs). Under 14 CFR §119.51(c), a certificate holder applies to the responsible Flight Standards office to add a new authorization (for example IFR, a new area of operations, overwater/Class II navigation, or a special operational authorization). The FAA reviews the application and either adopts it, partially adopts it, or denies it. Some additions also require an actual demonstration — validation tests under §135.145, or proving tests if you are introducing an aircraft not previously proven for use. The new authority is only legal once the amended OpSpec is issued; you cannot start flying the new operation on the strength of a pending request.
How long does it take to amend Part 135 OpSpecs, and is there a 90-day rule?
It depends on what you are adding. 14 CFR §119.51(c)(1) sets the filing lead time: most amendments must be filed at least 15 days before the date you want them effective, but you must file at least 90 days in advance for the bigger changes — a change in the kind of operation as defined in §110.2, mergers, acquisitions of operational assets that require an additional showing of safety such as proving tests, resumption after a bankruptcy suspension, or the initial introduction of an aircraft not before proven. Those are minimum filing windows, not promised approval times: the actual calendar depends on FAA workload, whether validation or proving tests are required, and how complete your application is. Build in margin and do not assume same-week turnaround.
What is the difference between adding an aircraft and adding a kind of operation?
They are two different OpSpec changes that people blur together. 14 CFR §119.1(b)(2) says your operations specifications cover both each kind of operation to be conducted and each class and size of aircraft to be operated. Adding an aircraft is about the airframe — getting a specific tail and make/model onto your OpSpecs through a conformity inspection so you are authorized to operate that aircraft. Adding a kind of operation (or a new authorization or area) is about what you are allowed to do — IFR, overwater, a new geographic area, single-engine IFR, EWINS, and so on. Both are §119.51 amendments, but the evidence the FAA wants is different: an aircraft addition turns on conformity and (sometimes) proving/validation for a new type; an operational addition turns on your manuals, training, and a validation that you can do the new thing safely. This article is about the operational side; see our companion guide on adding an aircraft for the airframe side.
Do I need proving runs or validation tests to add a new operation?
Sometimes. 14 CFR §135.145 separates two demonstrations. Proving tests (at least 25 hours, including five hours at night if night is to be authorized and five instrument approaches if IFR is to be authorized) apply when you introduce certain aircraft not previously proven under Part 135 — for example a turbojet or an aircraft requiring two pilots under VFR. Validation tests are required for specific authorizations: the addition of an aircraft of a type not previously proven or validated, operations outside U.S. airspace, Class II navigation authorizations, and special performance or operational authorizations. Validation testing confirms you can actually conduct the operation safely and in compliance; the FAA may accept methods other than a live flight where you can demonstrate competence without one. Not every operational addition needs a test, but assume the FAA will want to see how you will do the new thing before it signs the OpSpec.
Can I add an area of operations to my Part 135 certificate?
Yes — a new geographic area is an OpSpec amendment under §119.51, the same mechanism as any other added authority. You apply to the responsible Flight Standards office, and the area is added to your operations specifications once approved. The supporting work depends on the area: domestic expansion may be straightforward, while operations outside U.S. airspace are one of the §135.145(d) authorizations that require validation testing, and may pull in additional authorizations (such as Class II navigation, RVSM, or international procedures) each with its own OpSpec/LOA paperwork. If the expansion changes your kind of operation as defined in §110.2, the 90-day advance filing under §119.51(c)(1)(i) applies. Whether a specific area triggers validation or extra authorizations is a planning question to work through with your principal inspector.
Can the FAA change my OpSpecs without me asking?
Yes. 14 CFR §119.51(a) lets the Administrator amend operations specifications either when a certificate holder applies or when the FAA determines that safety in air commerce and the public interest require it. When the FAA initiates the change, §119.51(b) sets the procedure: the responsible Flight Standards office notifies you in writing, gives you a reasonable period of not less than 7 days to submit written information, views, and arguments, and then adopts, partially adopts, or withdraws the proposed amendment. An FAA-initiated amendment generally becomes effective not less than 30 days after you receive notice, unless there is an emergency requiring immediate action or you petition for reconsideration. So OpSpecs are a living authorization that can move in both directions, which is exactly why keeping a clean record of each version matters.
What if the FAA denies my OpSpec amendment?
Under §119.51(c)(3), after reviewing your application the responsible Flight Standards office notifies you of adoption, partial adoption, or denial of the amendment you applied for. If it is denied, §119.51(d) gives you a path: you may petition for reconsideration within 30 days of receiving the notice of denial (the same window applies if you are contesting an FAA-initiated amendment). The petition is submitted to the responsible Flight Standards office. Practically, denials usually trace back to a gap the inspector could not close — incomplete manuals, training not yet in place, or a demonstration not yet passed — so the fastest route to the authorization is often fixing the underlying gap and refiling rather than only contesting. Whether to petition, refile, or both is a judgment call to make with aviation counsel and your inspector.
How does FileFlo help with OpSpec amendments and added authorizations?
FileFlo does not file your amendment, decide whether you qualify, run your proving or validation tests, or get the authorization issued — that is the work of your management team, your aviation attorney where law is involved, and your FAA Flight Standards office. What FileFlo does is keep the documentation behind an amendment organized and provable: your current and superseded OpSpec pages, the amendment application and FAA correspondence, the proving/validation test records, the manual revisions and training records that supported the new authority, and the LOAs and authorizations (RVSM, Class II, EWINS, and the like) that often ride alongside a new operation — each with effective dates and expiration tracking. When an inspector asks to see the authority behind a flight, or which OpSpec version was in force on a given date, you can show it instead of digging. FileFlo is a compliance document intelligence platform; it does not provide legal, financial, or tax advice and does not claim SOC 2 certification.
Add the authority with the FAA — then prove it with records
Getting a new operation, area, or authorization onto your OpSpecs is work for your management team and your FAA Flight Standards office (and your aviation attorney where law is involved). The day-to-day job of proving every authorization you hold — showing the issued OpSpec, the amendment trail, the validation/proving records, and the LOAs that ride alongside — is a records problem, and that is what FileFlo solves. AI document classification. 600+ document types. One-click FAA-ready binder. Starter at $89/mo, Professional at $299/mo. No credit card required for the 5-day free trial. FileFlo does not give legal or tax advice, file your amendment, or get you certified — it organizes and proves your compliance documents.
5-day free trial · No credit card required · Cancel anytime
Continue your Part 135 certification & OpSpec reading
Reviewed by Chad Griffith, Founder, FileFlo — compliance document intelligence. Last reviewed June 15, 2026. The amendment procedure, the 90-day and 15-day filing windows, the FAA-initiated-amendment process, and the petition-for-reconsideration right are verified against 14 CFR §119.51; the definition of “kind of operation” against §110.2; the rule that operations specifications cover each kind of operation and each class and size of aircraft against §119.1(b)(2); and the proving-test and validation-test requirements against §135.145 — all via the Cornell Legal Information Institute. The common-carriage doctrine referenced elsewhere in our aviation library reflects FAA guidance in Advisory Circular 120-12A and longstanding FAA legal interpretation — guidance, not regulatory text. This article is a compliance-document perspective and is not legal, financial, or tax advice; whether and how to add a kind of operation, area, or authorization is a determination for your management team, your FAA Flight Standards office, and a qualified aviation attorney (and a tax advisor on tax questions). FileFlo does not file amendments, render legal opinions, or get operators certified.