Night FPV is a different sport. Your depth perception shifts from visual reference to instrument reference — the OSD becomes your horizon. You navigate by lights, not landmarks. And a failsafe at night has a recovery rate near zero because finding a dark quad in a dark field is needle-in-haystack territory.
I’ve been flying night sessions for four years across open fields, abandoned industrial sites, and mountain ridgelines. This is the equipment and the protocol that keeps the quad coming back.
Camera Selection: IR Sensitivity Is Everything
Standard FPV cameras with IR-block filters (almost all stock cameras ship with one) are blind below twilight. Removing the IR filter — or starting with a camera designed for night use — transforms the sensor’s sensitivity.
Camera Comparison for Night Flying
| Camera | IR Filter | Minimum Lux | Night Usable | Latency | Notes |
|---|---|---|---|---|---|
| Runcam Night Eagle 3 | None (dedicated night) | 0.00001 | Yes — full darkness | 18-22ms | Best night performance, low resolution (800TVL) |
| Foxeer Cat 3 | None (dedicated night) | 0.00001 | Yes — full darkness | 15-18ms | Slightly sharper than Night Eagle, narrower FOV |
| Caddx Ratel 2 | Removable | 0.001 | Yes — starlight+ | 8-12ms | Best daytime+night hybrid; pop filter out for night |
| Runcam Phoenix 2 | Removable | 0.005 | Marginal — needs moonlight or LEDs | 8-12ms | Good hybrid, struggles in true darkness |
| DJI O3 (night mode) | Software IR cut removal | 0.01 | No — needs illumination | 28-35ms | Night mode helps but sensor still 2-3 stops short |
The dedicated night cameras (Night Eagle 3, Cat 3) are in a different league. At 0.00001 lux, they can see by starlight alone — no IR illuminator needed. The trade is resolution: 800TVL is roughly equivalent to 480p. In the dark, you’re flying by shapes and contrast, not detail, so the resolution penalty is acceptable.
The hybrid approach (Caddx Ratel 2 with removable IR filter) is what I recommend for 90% of pilots. Flip the filter out for a night session, pop it back in for daytime. The 0.001 lux sensitivity with the filter removed is enough for moonlight or ambient city light. In true pitch-black conditions, you’ll want supplemental illumination.
IR Illuminator (Active Illumination)
If you’re flying in zero-ambient-light conditions (deep rural, over water at night, inside unlit structures), an onboard IR illuminator is mandatory. A 3W 850nm IR LED module weighs 8g and illuminates 30-50 meters. Mount it on a small TPU bracket pointing forward, powered from a spare 5V or 12V pad on the FC.
One thing nobody tells you: the IR spotlight creates a visible red glow at the LED source (850nm is at the edge of human vision). If you’re flying somewhere you’d rather not draw attention, use 940nm IR LEDs — they’re completely invisible but about 40% less efficient. The Runcam IR-block filter removal mod doesn’t pass 940nm as well as 850nm, so test before committing.
Navigation and Orientation Lighting
Without a horizon, you orient by lights. The standard configuration every night pilot converges on:
- Front: Two white LEDs (5mm, wide-angle, 50-100mA each). Mount on the front arms or camera cage, angled slightly outward (15°) to be visible in the peripheral FOV during banking turns.
- Rear: Two red LEDs (5mm, wide-angle). Rear arms or top-plate rear edge. These are your primary orientation reference — if you see red, you’re looking at the back of the quad.
- Arm tip: Colored LEDs (addressable WS2812 strips). Left arms green, right arms red (aviation standard). At distance, the color block tells you the quad’s heading in the camera frame.
- Top/Bottom: Different colors if you fly inverted. White on top, red on bottom, or any high-contrast pair. In a power loop at night, the top/bottom light flip is your only clue that you’ve gone past vertical.
Wire the LEDs to a switch on your radio (assign to a spare channel in Betaflight LED tab). You want the ability to kill all lights instantly — for those moments when you need to go dark, or when the LEDs are reflecting off fog/mist and creating a glare visible in the camera.
LED Power and Wiring
Addressable LEDs (WS2812B) draw 60mA at full white per LED. A strip of 8 LEDs is 480mA — significant on a 5V BEC that’s also powering the FC and receiver. Use a dedicated 5V BEC (Pololu 5V 1A step-down, 2g) wired directly to the battery lead for LED-only power. This isolates LED current noise from the FC’s 5V rail and prevents the dreaded “LED flicker correlated with motor RPM” issue.
Flight Protocol and Safety Rules
Pre-Flight Walk
Before the first night flight at a location, walk the entire flying area in daylight. Mark obstacles mentally — the single tree in the middle of the field, the power line at the far edge, the fence along the property line. At night through an FPV camera, none of these will be visible until you’re 10 meters away. Your flight path should avoid every obstacle by at least 30 meters.
Launch and Landing
Launch and land with a flashlight illuminating the takeoff/landing zone. The quad’s own LEDs aren’t enough to see the ground texture for a precise landing. A headlamp on your head or a flashlight propped on the ground pointing at the LZ works. Land in angle mode if you normally fly acro — depth perception through a night camera is unreliable for the last meter of descent.
Altitude Discipline
Fly at least 10 meters higher than your daylight altitude floor. At night, the ground rises without visual warning — a gentle slope that you’d see easily in daylight is invisible through an IR-sensitive camera. Your barometer (if you have one) or GPS altitude in the OSD is your primary altitude reference, not the image.
Battery Voltage Monitoring
Voltage sag is more dangerous at night. A pack that sags to 3.3V/cell during a punch-out in daylight is a minor concern — you back off the throttle and the voltage rebounds. At night, that sag might happen during an orientation recovery maneuver where you need the power, and a brownout-induced failsafe in the dark is a total loss. Land at 3.5V/cell resting — give yourself a wider safety margin than daytime.
Spotter Requirement
Never fly night FPV alone. A visual observer with a flashlight who can track the quad’s position in the sky is your insurance against a video system failure. If your camera dies mid-flight (rare but possible — water, impact damage, connector wiggle), the spotter’s visual contact on the navigation LEDs is the only way to guide the quad back. The spotter should stand behind you and call out the quad’s position relative to obstacles: “You’re 50m out, 30° to the right, clear air in all directions.”
Common Mistakes & What Most Night Pilots Get Wrong
1. Using a standard FPV camera without removing the IR filter. You’ll see a black screen with faint shapes that look like ghosts. The IR filter on a daylight camera blocks exactly the wavelengths that your LEDs and ambient IR light are putting out. Remove it or buy a camera designed for night use. YouTube tutorials exist for IR filter removal on specific camera models — it’s a 5-minute mod but permanently changes the camera’s daytime color balance.
2. Making the LEDs too bright. Overly bright LEDs (especially white front LEDs) bloom in the camera sensor and wash out the surrounding image. Run white LEDs at 30-50% brightness via the Betaflight LED tab. At full blast, what looks like helpful illumination to your naked eye is lens flare in the camera.
3. Flying an unfamiliar location at night for the first time. Scouting in daylight is non-negotiable. The branch that hangs at 15 feet from the ground is invisible to an IR camera until it’s in frame — by which point you’ve already hit it. Fly a location at least 3 times in daylight before attempting it at night.
4. Forgetting that LiPo performance drops in cold night air. A LiPo at 5°C has roughly 20% less usable capacity and sags harder under load than at 25°C. If you’re flying a cold night session, keep packs in an inside jacket pocket until you’re ready to fly. A warm pack installed in a cold quad still loses heat faster than in daytime — your 5-minute flight time might be 4 minutes. Land at 3.6V/cell instead of the usual 3.5V.
5. No redundancy for orientation lights. A single LED failure at night turns a fully controllable quad into a disoriented mess. If your lone rear red LED shorts out mid-flight, everything behind the camera is suddenly black and you have no idea which direction “forward” is. Run redundant LEDs — two white front, two red rear, minimum. Addressable strips give you per-LED redundancy; a single failed LED doesn’t kill the whole strip.
⚠️ Regulatory Notice: Night UAS operations are subject to additional restrictions in most jurisdictions. In the US, the FAA’s 2026 regulations require anti-collision lighting visible from 3 statute miles for nighttime recreational flights. The EU’s EASA open category requires a lighting system for night operations. Many countries prohibit night flights entirely for non-certified pilots. Always verify your local 2026 regulations for night UAS operations before flying. Operation near airports or in controlled airspace at night carries significantly higher penalties than daytime violations.
The LED configuration and Betaflight setup principles pair well with our FPV LED Strip Configuration Guide. For the electronics behind clean LED power, our FPV Capacitor Installation Guide has the power filtering setup that prevents LED flicker. And if you’re flying at night in less-than-ideal weather, our Conformal Coating Guide covers the waterproofing that keeps dew and moisture out of your night rig’s exposed electronics.
A night rig needs a dedicated LED power rail that won’t sag when the motors pull current. The GEPRC GEP-F722-45A AIO’s independent 5V and 9V BEC outputs mean you can run your LEDs on one rail and your camera/VTX on the other — zero crosstalk, zero flicker. The F722 processor’s extra UARTs give you a dedicated LED strip pin without sacrificing GPS or receiver ports, which is exactly what a night build needs.