A real estate pilot wraps up a dusk shoot of a lakefront property, watching the sky go from orange to deep blue as they fly. Nothing in their kit changes — same drone, same registration, same airspace — but at some point during that flight they cross from a period that needs no special equipment into one that legally requires an anti-collision light the aircraft doesn't have. Night flying isn't a separate activity that starts at a fixed clock time; it's a regulatory line most pilots don't notice until they're already on the wrong side of it, because the trigger is civil twilight, not "when it gets dark outside."
What actually changed in the rule
Night operations used to require a specific FAA waiver under Part 107, applied for in advance and often taking weeks to process. Since the Advanced Operations rule took effect, that waiver requirement is gone: a Remote Pilot Certificate holder can fly at night as a baseline privilege, provided they've completed the recurrent training that now specifically covers night operations — including the visual illusions and judgment errors that come with reduced light. The training requirement is the part pilots skip fastest, because it's easy to assume that removing the waiver meant removing the barrier entirely, when it really just moved the requirement from a paperwork approval to a knowledge standard.
The anti-collision light requirement is a specific number, not a vibe
Civil twilight — roughly 30 minutes before sunrise and 30 minutes after sunset — does not require anti-collision lighting under Part 107. True night operations do, and the rule is specific: the aircraft needs a light visible for at least 3 statute miles with a flash rate sufficient to alert other aircraft to a collision hazard. A blinking hobby-store LED strip that's visible from 200 feet is not compliance; it has to be bright enough that a manned aircraft pilot scanning the sky from three miles out has a real chance of seeing it in time to avoid a conflict. A pilot can reduce the light's intensity if the full brightness would itself create a hazard — for example, if it's bad enough to damage the remote pilot's own night vision at the control station — but cannot turn it off entirely to save battery or reduce visibility to bystanders.
Night flying is legal now; night vision problems didn't go away
The regulatory barrier dropping doesn't mean the human-factors risk did. Visual line of sight is still required using unaided eyes (corrective lenses are fine, night-vision goggles are not, absent a separate waiver), and the eye is measurably worse at judging distance, altitude, and closure rate in low light — peripheral vision picks up motion better than detail after dark, which is exactly backwards from what's needed to spot a fixed obstacle like a guy wire or a thin tower. A common mistake among newly night-current pilots is treating the drone's own lights as a reliable altitude reference; a light that looks stable and close can actually be drifting toward a rooftop or tree line the pilot simply can't resolve against a dark background until it's a very near miss.
Other restrictions don't pause at sunset
Every airspace and land-use rule that applies during the day still applies at night, and some matter more after dark: a LAANC authorization for controlled airspace often specifies whether it covers night operations at all, TFRs and national park bans are in force regardless of light level, and Remote ID broadcast is still required. Night flights also draw more noise complaints in residential areas, since a drone that's barely audible during the day can be the loudest thing in a quiet neighborhood at 9 p.m. — worth checking local ordinances even where FAA rules are fully satisfied.
Practical checklist
- Confirm your recurrent training actually covered night operations and visual illusions — an older certificate predating the rule change may need a refresher before flying after dark.
- Equip an anti-collision light visible from 3 statute miles with an adequate flash rate; a consumer LED strip usually isn't enough on its own.
- Know the exact civil twilight times for your location and date, not a rough guess — that boundary is when the lighting requirement kicks in.
- Don't rely on the drone's onboard lights as a substitute for genuinely judging altitude and distance against dark terrain.
- Re-check LAANC authorizations, TFRs, and land-use restrictions (like national parks) specifically for night coverage — daytime approval doesn't always carry over.
- This site's weather and airspace layers are planning references only; always verify current authorizations and restrictions directly with the FAA before a night flight.