When Requesting a Waiver the Required Documents Should Be Presented to the FAA at Least How Many Calendar Days Prior to the Planned Operation: The 60-Day Rule Explained

The answer is 60 calendar days. Under the FAA's waiver framework in 14 CFR Part 107, an operator requesting a certificate of waiver must submit the application — with all required supporting documents — at least 60 calendar days before the planned operation. That figure is the statutory minimum review window, not a processing guarantee: the FAA can and does take longer, and the regulation states plainly that a waiver will not be granted if the application is received after that 60-day threshold has passed.

What 14 CFR 107.200 Actually Says About the Filing Window

Section 107.200 is short, and that brevity is exactly why people misread it. It directs the Administrator to issue a certificate of waiver when the FAA finds the proposed operation can safely be conducted under the waiver's terms and conditions, and it caps the waiver term at two years. Buried in the same section is the procedural gate: no waiver will be granted if the application is received by the FAA less than 60 calendar days before the proposed operation's start date.

Two words in that language do the heavy lifting. "Received" means the date the FAA accepts a complete application, not the date you hit submit on a portal or drop an envelope in a mailbox. "Calendar days" means every day counts, including weekends and federal holidays — there is no business-day grace period to lean on.

The 60-day window attaches to the proposed operation's date, so a waiver application written around a single event must name that event and clear the gap. If you're seeking a broader waiver covering recurring operations, the agency's guidance treats the requested effective date as the relevant anchor, which is why operators who want coverage "as soon as possible" still have to pick a start date at least two months out.

There's a second deadline hiding in the same rule that catches almost nobody: a waiver request must be submitted at least 90 calendar days before the proposed operation expires if you're asking to extend or amend an existing waiver. Two different clocks, two different numbers, and mixing them up is one of the most common filing errors in the entire Part 107 system.

Why the FAA Built in a Two-Month Buffer

The 60-day figure isn't arbitrary bureaucracy. Part 107 was finalized in June 2016, and the waiver process it created was designed to handle requests that fall outside the operating rules — night operations before those became routine, flights over people, beyond visual line of sight, operations from a moving vehicle. Each of those requires the FAA to evaluate a safety case, not just check a box.

The review isn't a single reviewer reading a PDF. Depending on the waiver type, an application can route through aviation safety inspectors, air traffic personnel if controlled airspace is involved, and policy staff who check the proposed mitigations against precedent. The 60 days gives the agency room to ask follow-up questions and still issue a decision before your operation date — provided you filed a complete package.

Knowing why the buffer exists changes how you use it. The 60 days is a floor for the FAA's review clock, so treating it as your preparation deadline rather than your filing deadline is the practical move. Operators who need a waiver for a date-certain event should be assembling documentation 90 to 120 days out so the application goes in with room to spare.

The clock also runs differently depending on how you file. The FAA's online waiver portal issues an automatic acknowledgment, but that acknowledgment is not the "received" date that matters — the received date is when the package is accepted as complete. A missing attachment can reset your timeline without any notification that it happened.

The Documents That Must Ride Along With the Application

The regulation itself doesn't publish a numbered checklist; the required contents live in the application instructions and the FAA's waiver guidance, and they scale with the complexity of what you're asking for. At minimum, a complete package includes the operator's identity and certificate information, the specific regulation or regulations you want waived, a description of the proposed operation including location and timing, and the safety justification — the mitigations that make the operation as safe as the rule you're departing from.

For anything beyond a simple daylight waiver, expect to attach supporting material: crew qualifications and currency, aircraft specifications, a concept of operations, and evidence that your proposed mitigation has a track record. The FAA's guidance has repeatedly emphasized that waiver requests supported by existing standards, consensus safety cases, or prior FAA-accepted mitigations move faster than novel proposals — a point worth internalizing before you write a 40-page justification from scratch.

Administrative completeness matters as much as the safety case. An application missing the operator's registration details, the correct regulation citation, or a coherent description of the operation gets returned, and the return eats days you may not have. The received-date rule means a returned-and-resubmitted package restarts the 60-day measurement at the resubmission.

If your operation touches controlled airspace, a separate authorization under Part 107's airspace provisions may be needed alongside the waiver, and those two processes run on different tracks. Filing them together without understanding that they're distinct is a common source of confusion — the waiver covers the operating rule, the airspace authorization covers the location.

A Worked Timeline From Today to an Approved Waiver

Here's how the calendar math actually plays out for an operator planning a date-certain operation. Assume a planned operation on a Saturday in mid-March. Counting back 60 calendar days lands the filing deadline in mid-January — and because weekends count, a Friday filing in mid-January is the real-world target.

That middle row is where timelines die. An FAA follow-up question that sits in an inbox for a week effectively shortens your buffer, because the agency can't finish review until it hears back. Assign one person to monitor the application and respond same-day.

The 90-day amendment clock deserves its own line in your planning. If you already hold a waiver and want to extend it or change its terms, the request must arrive at least 90 calendar days before the current waiver expires — 30 days earlier than a fresh application. Operators who discover this late sometimes let a waiver lapse and refile from scratch, which costs them the full 60-day window again.

Run the math backward for recurring operations, too. A waiver lasts at most two years under 107.200, so a renewal filed on the last permissible day gives you a decision roughly two months before expiry if everything goes smoothly. Anything less than smooth and you're flying on an expired waiver, which is the same as flying without one.

The Failure Case: What Happens When You File Late

Filing inside the 60-day window doesn't produce a denial with an explanation of the safety merits. It produces a procedural rejection: the regulation says the FAA will not grant a waiver when the application arrives too late, full stop. Your safety case never gets evaluated, and the operation can't legally proceed under the waiver you wanted.

The downstream cost is the part operators underestimate. A missed waiver doesn't just cancel one flight. If the operation was a commercial contract — a inspection, a mapping job, a film shoot — the operator either cancels, flies outside the rules and accepts enforcement exposure, or scrambles for a different operational approach that may not satisfy the client. None of those is cheap.

There's an edge scenario worth flagging: the application that arrives on day 60. Because the rule measures calendar days prior to the operation, a package received exactly 60 days out satisfies the threshold on its face. But "received" is the FAA's determination, and a submission timestamped late in the evening on day 60 may be logged the following day. File at least a few days early to absorb that ambiguity.

Denials for incompleteness behave similarly. The FAA may close an application that doesn't contain enough information to evaluate rather than parking it indefinitely, and a closed application is not a pending one. If you learn nothing else from this article, learn that a complete package filed 75 days out beats a thin package filed 61 days out every time.

Waivers Versus Airspace Authorizations: Different Documents, Different Clocks

People routinely conflate the Part 107 waiver with the airspace authorization process, and the confusion creates real scheduling errors. A waiver under 107.200 changes how you may operate — the rule you're departing from. An airspace authorization under the Part 107 operating rules grants permission to fly in a location where flight is otherwise restricted. They're separate submissions with separate review paths.

The timescales aren't identical either. Airspace authorizations through the FAA's online system have historically been processed on a different cadence than waivers, and the agency has pushed operators toward its LAANC system for many routine airspace requests precisely because it returns near-instant decisions in participating areas. A waiver request gets you nothing on the airspace question, and an airspace authorization gets you nothing on the operating-rule question.

Where this bites is the operator who assumes a single submission covers both. A night-operation waiver for a site inside controlled airspace needs both approvals in hand before the flight, and each has its own clock. Build both into your timeline rather than treating one as a formality behind the other.

One more distinction: waivers under 107.200 are specific to the operator and the operation described. They don't transfer to a different pilot or a materially different operation without an amendment, and amendments carry that 90-day expiry-adjacent filing requirement. Read your granted waiver's terms before assuming it covers the next job.

What a Strong Safety Case Looks Like Inside the 60-Day Package

The FAA has been explicit across its waiver guidance that applications grounded in existing consensus standards and previously accepted mitigations get faster, more predictable review. That's not a secret handshake — it's a signal about how to write the safety justification. If your proposed mitigation mirrors one the agency has already accepted for a similar operation, say so and describe the match.

Specificity is the currency. "Our pilot is experienced" means nothing; "the pilot in command holds a remote pilot certificate and has logged 150 hours in the proposed aircraft type, with 40 hours in the preceding 90 days" is evaluable. The same applies to equipment, procedures, and the description of the operating area. A reviewer who has to guess at your intent will ask questions, and questions cost days.

Attach the operational description as a coherent document rather than a pile of fragments. State what the operation is, where it happens, when it happens, who flies it, what aircraft is used, and how each mitigation addresses the specific risk that the waived regulation was written to manage. That structure lets a reviewer reach a finding without a scavenger hunt.

Leave the boilerplate out. Language copied from a sample waiver found online is recognizable, contributes nothing to the safety case, and sometimes describes an operation that isn't yours. Every paragraph should answer a question the reviewer will actually ask about this operation.

Common Mistakes That Burn the Calendar Days

The single most expensive mistake is discovering the 60-day rule after planning the operation. Operators who learn about the filing window when they sit down to apply are already behind, and there's no expedited lane for a date they've already promised a client.

Second is the business-day assumption. Sixty calendar days is roughly 43 business days in a typical stretch, and anyone mentally substituting the smaller number files about two and a half weeks late without realizing it. Put the deadline on a calendar in calendar days and count weekends in.

Third is treating the portal acknowledgment as the received date. The acknowledgment confirms transmission. The received date is when the FAA has a complete package, and the difference between those two can be a week or more if something's missing.

Fourth is forgetting the amendment clock. Operators who hold a waiver and want to widen it sometimes file at the 60-day mark out of habit, only to find the rule requires 90 days for extensions and amendments of an existing waiver. The two numbers look similar enough that the mistake is easy and the consequence is a lapsed waiver.

How Long Approval Actually Takes Once You've Filed

The 60-day figure is a minimum, not a service-level commitment, and the FAA has never guaranteed a decision date. In practice, straightforward waivers supported by established safety cases have come back within the window, while novel or complex proposals — particularly those involving operations beyond the agency's existing precedent — have taken longer. The variance is the reason to file early rather than at the threshold.

Withdraw-and-refile is a real option if an operation date moves. If your planned operation slips by several months, the original 60-day calculation no longer matches reality, and the FAA may need an updated description of the operation. Coordinating that change early keeps the application live rather than letting it close.

Track the waiver's two-year maximum term from the grant date. A waiver granted in March of one year expires in March two years later, and the renewal clock starts months before that. Operators with multiple waivers should keep a single register of grant dates, expiry dates, and the 90-day amendment deadlines so nothing lapses by inattention.

Denials are appealable through the FAA's processes, but an appeal consumes time you likely don't have for a date-certain operation. The productive move after a denial is to read the stated reason, address it directly in a new application, and file with the 60-day window intact from the new operation date.

FAQ

Does the 60-day clock start when I submit or when the FAA acknowledges?

It starts when the FAA receives a complete application, not when the portal confirms transmission. An acknowledgment email is proof of submission only. If the agency later determines the package was incomplete, the received date resets to the resubmission, which can push you past the 60-day threshold without any warning.

Can I get a waiver approved faster than 60 days?

No — the regulation bars granting a waiver when the application arrives less than 60 calendar days before the operation. There is no published expedite lane for Part 107 waivers. The practical speed lever is a complete, precedent-aligned package filed well ahead of the threshold, not a request for priority handling.

Is the 60-day rule the same as the 90-day rule I've heard about?

They govern different filings. The 60-calendar-day minimum applies to a new waiver request measured against the proposed operation date. The 90-calendar-day requirement applies to requests to extend or amend an existing waiver, measured against the current waiver's expiration — a longer window that catches experienced operators off guard.

What happens if my planned operation date changes after I file?

The filed application describes a specific operation and timing, so a material change may require an updated submission. Contact the FAA early rather than assuming the original filing still applies. A shifted date can also mean your original 60-day calculation no longer reflects the operation you'll actually conduct.

Do I need a waiver and an airspace authorization for the same flight?

Possibly, and they're separate approvals on separate clocks. A waiver changes the operating rule; an airspace authorization permits flight in a restricted location. A night waiver at a site inside controlled airspace requires both in hand before launch, and each must clear its own review timeline.

Does the waiver cover any pilot on my team?

No. A Part 107 waiver is issued to the operator for the operation described, and it doesn't automatically extend to a different pilot or a materially different operation. Check the grant's named parties and terms before assigning the flight, and file an amendment if the scope needs to widen.

What's the maximum term of a Part 107 waiver?

Two years from the grant date, per 14 CFR 107.200. The expiry date drives the 90-day amendment and extension clock, so a waiver granted in a given month expires in that same month two years later — put the renewal deadline on the calendar at grant, not at expiry.

Can I operate while my waiver application is pending?

No. The underlying regulation still applies until a waiver is granted, so operating in reliance on a pending application is operating outside the rules. Enforcement exposure attaches to the flight, not the paperwork, and a pending status provides no defense.

This article is general educational information about the FAA's Part 107 waiver framework and is not legal advice or an aviation regulatory determination. Waiver requirements, review timelines, and portal procedures can change, so confirm current filing instructions with the FAA directly and consult a qualified aviation attorney or regulatory consultant for advice specific to your operation. If an operation involves immediate safety risk, contact the appropriate aviation authorities or emergency services.