Night VFR Weather Minimums and Margins

Night doesn’t create weather that isn’t already in the forecast. It takes away your ability to see the weather coming. A cloud deck you would have dodged in daylight becomes a wall you fly into without warning, and the fog forming over the river at your destination is invisible until your landing light finds it on short final.

That single fact drives everything else, including the regulations. At night in Class G airspace below 1,200 feet above the surface, the basic VFR minimum jumps from 1 statute mile and clear of clouds in the day to 3 statute miles with 500 feet below, 1,000 above, and 2,000 horizontal from the clouds (14 CFR 91.155). The rule is stricter after dark for the same reason your personal minimums should be: you have lost your primary sensor. Everything below is US-centric, written against the 14 CFR the FAA enforces.

Why night changes the weather problem, not just the lighting

In daylight you fly a continuous see-and-avoid loop against the weather. You watch a scud layer lowering ahead and turn before it reaches you, or see the rain shaft under a cell and give it room. None of that requires an instrument. It requires eyes and a horizon.

Take the horizon away and the loop breaks. On a dark night over unlit terrain you cannot tell VMC from IMC by looking, because both look like nothing. Pilots have flown into clouds, into rising ground, and into the water without ever seeing the thing they hit. The weather was in the briefing. The margin that would have caught it in daylight was gone.

So the honest way to think about night flying weather is not “the same flight, darker.” It is a flight where your best tool for catching a bad forecast has been switched off, and you rely instead on the briefing and your instruments. That is why the go/no-go for a night flight starts from a tighter baseline than the same route by day. Our working framework for the go/no-go decision treats night as its own input, not a footnote.

The three “nights” in the FARs

A snag that trips up more certificated pilots than it should: the FAA does not use one definition of night. It uses three, for three different purposes, and they do not start and end together.

Sunset to sunrise: aircraft lights (14 CFR 91.209). Position lights are required from sunset to sunrise. This is the earliest of the three to trigger in the evening. The sun goes down, your nav lights go on, and you are legally in “night” for the purpose of lighting the airplane, even though the sky is still bright enough to read a chart.

Civil twilight: logging night time (14 CFR 61.51, via the definition in 14 CFR 1.1). For logging night flight time and building the night experience your certificate required, “night” means the time between the end of evening civil twilight and the beginning of morning civil twilight, as published in the Air Almanac and converted to local time. Civil twilight ends when the geometric center of the sun sits 6 degrees below the horizon, usually 20 to 30 minutes after sunset at mid-latitudes. So every evening there is a window when your lights must be on but the clock does not yet count toward night currency or your night logbook column.

One hour after sunset to one hour before sunrise: passenger currency (14 CFR 61.57(b)). To carry passengers during the period beginning one hour after sunset and ending one hour before sunrise, you need three takeoffs and three landings to a full stop within the preceding 90 days, flown during that same window, as sole manipulator, in the same category and class (and type, if a type rating applies). This is the latest window to open in the evening and the one people forget: touch-and-goes do not count, and daylight landings do not count.

The reason all three matter on a weather flight: sunset itself means very little, and the useful boundaries sit before and after it. Our civil twilight and sunrise/sunset tool gives you the three boundaries side by side for tonight at your airport, so you can see which “night” you are planning into.

Legal VFR minimums at night

Class G is where night rewrites the numbers. Everywhere else the VFR minimums are the same day or night, so the trap is the airspace most GA pilots treat as the freest.

Class G airspace	Day	Night
1,200 ft or less above the surface	1 SM, clear of clouds	3 SM; 500 below, 1,000 above, 2,000 horizontal
More than 1,200 ft AGL but below 10,000 ft MSL	1 SM; 500 below, 1,000 above, 2,000 horizontal	3 SM; 500 below, 1,000 above, 2,000 horizontal
More than 1,200 ft AGL and at or above 10,000 ft MSL	5 SM; 1,000 below, 1,000 above, 1 SM horizontal	5 SM; 1,000 below, 1,000 above, 1 SM horizontal

Two things to read off that table. The generous daytime Class G allowance of 1 mile and clear of clouds disappears at night in both low tiers, replaced by 3 miles and the standard cloud clearances. And Class E stays at 3 miles and 500/1,000/2,000 below 10,000 feet MSL around the clock, so if your route lives in Class E, night does not change the legal floor, only your ability to hold it visually.

There is one narrow night relief in 91.155(b): an airplane operating in an airport traffic pattern within one-half mile of the runway may go clear of clouds when visibility is less than 3 but not less than 1 statute mile. It exists for the pattern, not the cross-country, and flying to legal minimums at night is a separate question from flying to safe ones.

The radiation fog trap after sunset

The most common way a legal-at-departure night flight turns dangerous in the air is radiation fog forming under you while you fly. On a clear, calm night the ground radiates its heat to space, the surface air cools toward its dew point, and when the two meet, fog forms. Sunset starts that clock. A field reporting 8 miles and a 4-degree temperature/dew-point spread at your 2100Z departure can be a quarter mile in fog by the time you reach the arrival, the spread closed to zero exactly when you needed the runway.

The temperature/dew-point spread is the single number to watch on a night briefing, and a tightening spread in the TAF is a night no-go signal long before the visibility line changes. Our guide to the fog types and when they burn off covers radiation fog’s overnight timing in detail. At night you will not see it forming. The spread is your only forecast of it.

Black-hole approaches and false horizons

Even in legally clear air, night removes the visual references your eyes assume are there, and your brain invents replacements. The AIM catalogs these under illusions in flight (AIM 8-1-5); two of them bite on night arrivals.

A false horizon happens when a sloping cloud deck, a shoreline, or a scattering of ground lights blending into stars gives you a horizon that is not level. Follow it and you bank to match a line that was never true. The black-hole approach is the classic: a runway reached over water or unlit terrain, its lights the only thing in the windscreen, no surrounding features to judge height or angle against. The runway can look like it is sloping, and pilots consistently fly too low and land short. Neither is a weather phenomenon, but both are made worse by any weather that further thins your visual cues, and both are answered the same way. Trust the instruments. On a black-hole arrival, fly the glidepath the panel and the approach lighting give you, not the picture your eyes are painting.

Raising personal minimums for night

With the daytime safety valve of see-and-avoid gone, night personal minimums should be visibly higher than your daytime numbers, not the same numbers held more carefully. A few that pilots who fly a lot of night settle on:

• Higher ceilings and visibility than the legal minimum. If your daytime personal minimum is a 2,500-foot ceiling and 6 miles, night might be 4,000 and 8. The point is room to see terrain and cloud before you reach them.
• More fuel, held firmer. Alternates are farther apart at night, fewer fields have fuel and lighting when you arrive unplanned, and a diversion eats more of your reserve. The night reserve should beat the legal 45 minutes and be a hard floor.
• An instrument-capable out. Continued VFR into instrument conditions is the accident that ends night VFR flights, and it happens fastest when the pilot has no instrument plan and no currency to fall back on. If you are not instrument-current, your night route needs a guaranteed visual escape at every point. The mechanism by which a legal night departure becomes a fatal one is worth studying directly; see how VFR flights end up in IMC.

Go/no-go inputs that matter more at night

Some factors barely register in a daytime go/no-go and move to the top of the list after dark. None of these is a rule. They are the honest questions a night flight asks that a day flight does not.

• The moon. A full moon high in a clear sky gives you a usable horizon and lit terrain, close to a bright day for orientation. A new moon under an overcast gives you nothing, and the black-hole and false-horizon risks climb accordingly. Moon phase and its time above the horizon are real planning inputs for a night VFR flight.
• Terrain. Rising ground you would see and clear easily by day is invisible at night. The minimum safe altitude that feels conservative in daylight is what keeps you alive after dark. Know the highest obstacle and the grid MORAs along the route, and fly them.
• What is under you. A single engine over lit, landable ground at night is a different proposition from the same engine over forest, water, or open desert with no cultural lighting. That is a personal call, not a regulation, and no one else can make it for you. It belongs in the night go/no-go honestly, without a sermon attached.

Night flying is some of the smoothest, quietest flying there is, and none of this argues against it. It argues for treating the darkness as the loss of a sensor and buying the margin back deliberately, in the briefing and in the numbers, because you cannot buy it back in the air.

Common questions

How many definitions of night are there in the FARs?

Three, and they do not start together. Position lights are required from sunset to sunrise under 91.209. Night flight time is logged between the end of evening civil twilight and the beginning of morning civil twilight, per the definition in 14 CFR 1.1. Passenger-carrying currency under 61.57(b) runs from one hour after sunset to one hour before sunrise.

Do VFR weather minimums change at night everywhere?

No. Class G is where night rewrites the numbers, which is the trap, because it is the airspace most GA pilots treat as the freest. In every other class the VFR minimums are the same day or night. The change is concentrated exactly where pilots expect the fewest restrictions.

What should night personal minimums look like?

Visibly higher than your daytime numbers, not the same numbers held more carefully. If your daytime minimum is a 2,500 ft ceiling and 6 miles, night might be 4,000 and 8. Carry more fuel and treat the reserve as a hard floor, since alternates are farther apart and fewer fields have fuel and lighting when you arrive unplanned.