Anti-Collision Lighting Requirements
Anti-collision lighting is the equipment half of the night-operations rule: without it, an aircraft cannot legally fly at night or during civil twilight, no matter how well trained the remote pilot is. This lesson goes deep on exactly what 14 CFR 107.29's lighting requirement demands, why the standard is written the way it is, and the reduce-but-never-extinguish rule that gives a remote pilot some judgment while still guaranteeing the aircraft stays visible to others.
The 3-statute-mile visibility standard
Both 107.29(a)(2), which governs full night, and 107.29(b), which governs civil twilight, use identical language: the aircraft must have lighted anti-collision lighting visible for at least 3 statute miles. This is the same fundamental concept used for manned aircraft anti-collision lighting: the lighting needs to be bright and positioned well enough that another aircraft or a person on the ground, under clear conditions, could reasonably spot it from three statute miles away. A remote pilot is not expected to literally measure this distance before every flight; rather, the aircraft's anti-collision lighting equipment needs to be genuinely rated and designed to meet this visibility standard, the same way a manufacturer designs and rates any other piece of required safety equipment.
The flash-rate requirement: a functional standard, not a fixed number
107.29 requires a flash rate "sufficient to avoid a collision" — notice that the regulation does not specify an exact number of flashes per minute. This is a functional, performance-based standard rather than a precise numeric one: the lighting must flash at a rate that would genuinely help another aircraft or observer notice and avoid the drone, but the FAA leaves the specific engineering number to reasonable equipment design rather than mandating one fixed figure in the text of 107.29 itself. This differs from some manned-aircraft lighting standards that do specify numeric flash-rate ranges; a remote pilot should not assume Part 107 borrows an exact number from those other rules unless they have specifically verified it in the current regulation text.
The lighting requirement applies identically in civil twilight and full night
As covered in Lesson A, the training/testing condition of 107.29(a)(1) applies only to full night, not civil twilight. The lighting condition works differently: it is required, in the exact same form, during both periods. There is no lighter-touch version of the lighting standard for civil twilight — the same 3-statute-mile visibility and sufficient flash rate apply whether the aircraft is flying at 11:00 PM or during the 30 minutes right after official sunset.
Reducing intensity without extinguishing the lighting
Both 107.29(a) and (b) give the remote pilot in command a specific, limited authority: the pilot may reduce the intensity of the anti-collision lighting, but may not extinguish it entirely, if the pilot determines that doing so is in the interest of safety given the operating conditions. In practice, this authority exists for situations where full-intensity lighting could actually work against the pilot's own ability to maintain visual line of sight — for example, extremely bright lighting reflecting back at the pilot in certain conditions, or causing enough glare to make it harder, not easier, to track the aircraft visually. This is a narrow safety-judgment exception, not a general option to dim the lights whenever convenient, and it never permits turning the lighting off completely.
- Permitted: Reducing intensity when the pilot determines it is in the interest of safety.
- Never permitted: Extinguishing the anti-collision lighting entirely, for any reason, during night or civil twilight operations.
How this plays out with real equipment
Many aircraft designed for commercial use come with factory-installed anti-collision lighting, often a strobe or pulsing LED module built into the airframe and positioned for maximum visibility from multiple angles. Some remote pilots instead add an aftermarket anti-collision light to an aircraft that did not ship with adequate built-in lighting. Either way, the equipment needs to actually be rated for the 3-statute-mile visibility and sufficient flash-rate standard — a general-purpose position light or a dim accent LED intended purely for aesthetics is not automatically sufficient just because it is technically a light on the aircraft.
The anti-collision lighting standard: 3-statute-mile visibility, a sufficient flash rate, and the reduce-not-extinguish rule.
View LargerScenario: inspecting a communications tower at night for thermal anomalies
A remote pilot is hired to fly a thermal-camera inspection of a communications tower after dark, when temperature differentials are easiest to detect. The aircraft is equipped with a factory-rated anti-collision strobe confirmed to meet the 3-statute-mile visibility standard, and the pilot has already completed the training condition required for full night operations. During the flight, the pilot notices the strobe's reflection off the tower's metal structure is creating enough glare to make it briefly harder to track the aircraft visually against the tower. The pilot reduces the strobe's intensity setting to cut the glare, while confirming the lighting remains clearly visible and active, rather than turning it off — a legal and appropriate use of the reduce-but-not-extinguish authority under 107.29(a).
Confirming anti-collision lighting compliance before a night or twilight flight
Do this as part of every preflight check when any portion of the flight will occur during civil twilight or full night.
Confirm the aircraft's anti-collision lighting is rated for the required standard
Verify the lighting, whether factory-installed or aftermarket, is designed and rated to be visible for at least 3 statute miles with a flash rate sufficient to avoid a collision, not just a general-purpose light.
Test the lighting is functional and set to normal intensity before takeoff
Confirm the lighting activates and flashes normally, at full intensity as the default state, before launching into civil twilight or night conditions.
Monitor throughout the flight and reduce intensity only if genuinely needed for safety
If a specific safety condition arises, such as glare interfering with visual tracking, reduce the intensity as needed — but never disable the lighting entirely.
Document the equipment check for commercial jobs
Keep a simple record confirming the lighting was checked and functional for the specific flight, particularly useful for client-facing commercial work.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Assuming lighting is only required during full night, not civil twilight | Civil twilight has a lighter-touch rule for the training condition, which invites assuming lighting is also relaxed | The exact same lighting standard, 3 statute miles visibility and a sufficient flash rate, applies during both civil twilight and full night | 14 CFR 107.29(a)(2); 14 CFR 107.29(b) |
| Believing there is a specific, fixed flash-rate number required, such as a certain number of flashes per minute | Some other aviation lighting standards do specify exact numeric flash rates, and it is easy to assume Part 107 does the same | 107.29 uses a functional standard, "a flash rate sufficient to avoid a collision," without specifying an exact number in the regulation text itself | 14 CFR 107.29(a)(2) |
| Thinking any onboard LED or accent light satisfies the anti-collision lighting requirement | The aircraft may already have decorative or general-purpose lighting that looks similar to a strobe | The lighting must actually be designed and rated to meet the 3-statute-mile visibility standard, not just be any light present on the aircraft | 14 CFR 107.29(a)(2) |
| Believing "reduce intensity for safety" means the pilot can turn the lighting off whenever it seems more discreet or convenient | The rule does grant real discretion to the pilot, which can be over-read as broad permission | The reduction authority is tied specifically to the pilot's safety judgment about operating conditions, and the lighting may never be extinguished entirely for any reason | 14 CFR 107.29(a); 14 CFR 107.29(b) |
Does my drone's normal navigation or status lights count as anti-collision lighting?
Only if that lighting is actually designed and rated to meet the 3-statute-mile visibility and sufficient flash-rate standard of 107.29. A general-purpose status LED or aesthetic light is not automatically sufficient just because it is present on the aircraft.
Is there an exact required flash rate, like a specific number of flashes per minute?
No. 14 CFR 107.29 uses a functional standard, requiring a flash rate "sufficient to avoid a collision," without specifying an exact numeric figure in the regulation text.
Do I need anti-collision lighting during the day?
No. The anti-collision lighting requirement of 107.29 applies specifically to operations during civil twilight and full night, not to daytime operations.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.