Treat night waiver knowledge as a boundary-drawing skill. First, classify each planned flight against §107.29: night or civil twilight operations with the required anti-collision lighting and all other Part 107 rules met need no waiver, while the same operations without that lighting do. Second, for any waiver you actually need, write the safety explanation as named hazards paired with specific, checkable mitigations, and keep airspace permission in a separate lane. Practice that classification before you practice anything else, because it determines whether you apply at all.
Drawing the Line: Night Flights §107.29 Allows Without a Waiver
Part 107 permits night and civil twilight operations when the aircraft has the required anti-collision lighting. A §107.29 waiver is needed only when you cannot meet that published rule, so classify every planned flight before applying.
The FAA's waiver table lists one specific condition for §107.29: flying a small UAS at night or during civil twilight without anti-collision lighting. That phrasing is the boundary. If your aircraft carries the required lighting and you meet every other Part 107 rule — visual line of sight, operating limits, airspace requirements — you are operating under the regulation as published, and the FAA states plainly that no waiver is needed when you comply with all Part 107 regulations.
A waiver becomes necessary only for the version of the flight you cannot make compliant: night or twilight operations where anti-collision lighting is absent, or where another listed rule cannot be met. The FAA adds a warning specific to this request: if you apply to operate during civil twilight or at night, you must include details for mitigating the additional risk, or the approval may restrict you to daylight operations only. Build your application around that mitigation expectation from the start.
| Planned flight condition | What applies | Where it is handled |
|---|---|---|
| Night or civil twilight with required anti-collision lighting, all other rules met | No waiver; comply with §107.29 as published | No application required |
| Night without anti-collision lighting | Waiver from §107.29 with added risk mitigation details | Aviation Safety Hub |
| Civil twilight without anti-collision lighting | Waiver from §107.29 with added risk mitigation details | Aviation Safety Hub |
| Night or twilight flight in Class B, C, D, or surface E airspace | §107.29 waiver plus separate §107.41 airspace authorization | Aviation Safety Hub and FAADroneZone |
Filling the Waiver Safety Explanation Fields for a §107.29 Request
The Waiver Safety Explanation should describe the proposed operation and pair every identified risk with a mitigation. The FAA states that applications lacking hazards and mitigations cannot receive a complete safety analysis and will be disapproved.
Start with the operational details the FAA's guidance asks for: where you plan to operate, ideally with latitude and longitude and a detailed map; maximum altitude above ground level; whether controlled airspace is involved; what other kinds of airspace lie within five miles; and the character of the area — rural, sparsely populated, congested, a neighborhood, or a restricted access site. Then describe the aircraft: type, power source, maximum flight time, range, speed, dimensions, containment method such as geo-fencing or a tether, any termination system, flying weight, and how any load is secured.
Next cover personnel. State the minimum experience the Remote PIC must have, the minimum crew needed, and what training visual observers and other personnel receive before flying under the waiver. Explain how the responsible person verifies competence, what testing is performed and documented, and how knowledge is maintained through recurrent training or testing. Keep the whole explanation scoped: the FAA directs you to include only information applicable to the regulation you are waiving, so everything here should serve the §107.29 case.
Choosing Mitigations a Reviewer Can Actually Evaluate
The FAA's stated concerns are how you keep the operation safe at all times, including unusual circumstances, and which circumstances could arise. Write hazards as specific nighttime events and mitigations as specific, checkable controls.
Translate darkness into concrete circumstances: an obstacle you cannot see at distance after sunset; a person entering the flight area when ground detail is hard to judge; a lost control link when visual references are poor; or a lighting failure that removes your key safety equipment. For each circumstance, the FAA expects you to describe what you will do — a lighted pre-flight site survey, a visual observer with assigned scanning duties, geo-fencing with defined containment boundaries, or an immediate flight termination switch.
Anchor your mitigations to the categories the FAA names: operating limitations, technology, additional training, equipment, personnel, and restricted access areas. Generic assurances that the pilot is experienced and careful give a reviewer nothing to analyze. An operating limitation such as a reduced maximum altitude, or equipment such as a backup light source carried in the crew kit, can be verified against your described operation. Pair every hazard you name with at least one mitigation from those categories, and address what happens in unusual circumstances, not just the nominal flight.
Why a Night Waiver Cannot Substitute for Airspace Authorization
A §107.29 waiver removes only the night and civil twilight limitation. Operations in Class B, C, D, or surface Class E airspace still require authorization under §107.41 through a separate FAA process and decision.
The FAA's own guidance splits these into different lanes: waiver applications are submitted through the Aviation Safety Hub, while the airspace authorization process for §107.41 remains in FAADroneZone. The waiver application itself prompts you about controlled airspace and points night and twilight applicants toward §107.41 and the FAA's guidance on flying near airports. Treat the two approvals as independent: the waiver addresses when you may fly, and the authorization addresses where.
Sequencing matters because each decision moves on its own schedule. The FAA aims to review waiver requests within about 90 days, with timing varying by complexity and completeness, and it may issue a request for information with a response deadline. Submit the airspace request in parallel rather than waiting for waiver approval, and check whether LAANC or UAS Facility Maps cover your planned location. An application that answers the controlled-airspace question but never acts on it leaves the flight grounded regardless of the waiver's status.
Scenario: The Twilight Shoot That Never Needed a Waiver
A videographer booked a dusk exterior and applied for a night waiver by habit. Checking the flight conditions against §107.29 first would have shown the aircraft's anti-collision lighting made the flight legal as planned.
The setup: exterior property photos starting at civil twilight, flown by a current Part 107 pilot with a multi-rotor carrying the required anti-collision lighting. The mistake: assuming any flight touching darkness requires a waiver, the pilot filed an application with a generic safety explanation. The job then waited behind a review cycle for an approval that changed nothing — the FAA states directly that you do not need a waiver when complying with all Part 107 regulations, and that approval may even restrict the operation to daylight unless night risks are mitigated.
The better decision: classify the operation before applying. Lighting present, all other rules met — so fly under §107.29 as published. Reserve the waiver path for the genuinely non-compliant variant, such as the same twilight shoot if the aircraft cannot carry adequate lighting. Why it matters: the distinction separates a job that starts on schedule from one stalled in review, and an approved waiver brings binding terms you must then adhere to, since failing to follow waiver terms can constitute a violation of the regulation being waived.
Scenario: Night Waiver Approved, Class D Airspace Still Blocked
A riverfront inspection team secured a §107.29 waiver but discovered during planning that the site sat in Class D airspace. The waiver never covered that question; a separate §107.41 authorization was still required.
Setup: a municipality wants night inspections over a riverfront inside a Class D surface area. Mistake: the planner treated the approved waiver as blanket permission and scheduled the first flight. The airspace gap only surfaced when someone walked through a pre-flight checklist. The irony is that the waiver application had already asked about controlled airspace and other airspace within five miles of the flight area — the team answered those questions but never acted on the answers, so the paperwork they filed flagged the exact problem they later hit.
The better decision: map the airspace early, then submit the waiver through the Aviation Safety Hub and the §107.41 authorization through FAADroneZone in parallel, aligning both timelines before promising a start date. Why it matters: the two decisions arrive through different systems on different schedules, and only both together make the flight possible. A waiver approval does not move your first flight date if the airspace permission is missing, and a planner who sequences the applications sequentially instead of concurrently builds that delay into the project.
Practice Exercise, Self-Check Rubric, and Study Sequence
Draft a one-page safety explanation for a hypothetical night industrial-yard inspection, then score it against a five-dimension rubric. Redraft any dimension that falls short, and finish with the readiness checks below.
Exercise: you must inspect fencing and perimeter lighting at a fenced industrial yard on the edge of a small town, flying after civil twilight in an aircraft without anti-collision lighting. Write the explanation the way the FAA field expects: name §107.29 and the exact condition being waived, describe the location and area type, state maximum altitude and your containment and termination methods, then list at least three hazards specific to darkness, each paired with a mitigation drawn from the FAA's categories.
Expected observations: a strong draft reads like a checklist a reviewer could verify — specific places, specific controls, no promises of general carefulness. A weak draft describes the pilot's experience, leaves hazards unnamed, or answers one hazard with vague proper planning. Run the sequence in the bullets over about a week, adjusting the pace to your schedule: classification first, drafting second, self-attack third, boundary drills fourth, rescoring last. The order matters because drafting before you can classify tends to produce applications for flights that never needed one.
- Rubric dimension 1: names §107.29 and the precise waivable condition — night or civil twilight without anti-collision lighting.
- Rubric dimension 2: describes location, area type, maximum altitude, containment method, and termination system.
- Rubric dimension 3: lists at least three hazards specific to darkness rather than generic aviation risks.
- Rubric dimension 4: pairs every hazard with a mitigation from operating limitations, technology, training, equipment, personnel, or restricted access areas.
- Rubric dimension 5: documents personnel roles, training plans, and how competence is tested and documented.
- Adaptable sequence: Day 1 — classify five sample flights against §107.29 and the waiver table; Day 2 — draft the safety explanation; Day 3 — write your own request-for-information questions and answer them; Day 4 — run three flight plans across the waiver/airspace boundary; Day 5 — rescore against the rubric.
- Readiness check: you can explain without notes which night flights need no waiver, why a daylight-only restriction can appear, and why one approval cannot stand in for the other.
- Readiness check: given any practice flight plan, you can name the correct submission path and the regulation involved without looking.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.