LIVE · BRIEFING WIRE
FlightLogic Brief Daily aviation wire
Subscribe
← Reddit
● RDT COMM ·Quirky_Performer3991 ·May 13, 2026 ·00:26Z

Interesting night currency hypothetical

A pilot in Iceland identified a potential loophole in night currency regulations where the narrow window between sunset and civil twilight (approximately 40 minutes) would allow night landings to be logged for currency while remaining within day VFR requirements. The observation was verified by checking ForeFlight data showing sunset at 10:35 PM and civil twilight beginning at 12:10 AM, with even larger windows available in locations like Fairbanks, Alaska. The pilot noted this appears to be legitimate according to standard regulations, though acknowledging local variations may exist.
Detailed analysis

The regulatory gap between night currency and night flight time logging identified in this post is genuine and stems from two separate definitional frameworks embedded in the FARs. Under 14 CFR 61.57(b), night takeoffs and landings count toward currency when accomplished during the period beginning one hour after sunset and ending one hour before sunrise. Night flight time itself, however, is governed by the definition in 14 CFR 1.1, which ties night to the period between the end of evening civil twilight and the beginning of morning civil twilight. Civil twilight ends when the sun reaches six degrees below the horizon — a point that in high-latitude summer locations like Keflavík or Fairbanks can lag considerably behind sunset itself. The pilot's observation that these two thresholds create a usable window is correct under U.S. regulatory structure: there exists a period each evening that qualifies as "night" for currency purposes but remains "day" by logging definitions.

The practical math at Keflavík during the referenced period illustrates the phenomenon clearly. With sunset at 2235 local and civil twilight not ending until approximately 0010, the currency window opens at 2335 — only 35 minutes before night flight time would begin. A pilot flying U.S.-registered aircraft under FAA regulations could theoretically complete three full-stop landings in that 35-minute window, satisfy the recency-of-experience requirement under 61.57(b), and log zero night time for the flight. The same structural gap exists in Fairbanks during Alaskan summer, where the delta between sunset and civil twilight end can be considerably wider and where U.S. rules unambiguously apply — making the domestic version of the hypothetical operationally plausible rather than merely theoretical.

For working pilots, this observation carries more than academic interest. Flight departments operating under Part 135 or corporate Part 91 programs frequently manage pilot night currency tracking as part of their Operations Specifications or General Operations Manuals, and the regulatory distinction between "night" for currency versus "night" for logbook purposes is a genuine audit and compliance touchpoint. A pilot who has been flying early-evening departures in midsummer at high latitudes may be current by the clock standard of 61.57(b) while having accumulated little or no loggable night time — which matters separately for certificate requirements, insurance minimums set by underwriters, and company-imposed recency standards that often reference logged night hours rather than just currency events.

The broader context is that FAA definitions of night have historically been fragmented by purpose: one standard governs logging, another governs currency, another governs VFR flight rules and position light requirements, and SFAR or advisory circular guidance can introduce additional layers. The civil twilight and one-hour-offset standards were written at different times and for different regulatory purposes, and their interaction at extreme latitudes simply magnifies a seam that exists everywhere but goes unnoticed at lower latitudes where sunset and the end of civil twilight are separated by only ten to twenty minutes. As Part 91 and 135 operators continue to expand routes into higher-latitude markets — particularly with the growth of transatlantic and trans-polar business aviation in Greenland, Iceland, and northern Scandinavia — currency and flight time tracking protocols built around mid-latitude assumptions deserve scrutiny.

Operators and chief pilots should note that even if a pilot satisfies U.S. currency requirements through such a window, the analysis changes entirely under EASA or national regulations applicable in Iceland and most of Europe. EASA defines night differently, and currency requirements under EU-OPS and national implementing rules may not recognize the one-hour-offset framework at all. For any international operation, the applicable regulatory framework at the location of the flight governs, and pilots relying on U.S. currency logs to demonstrate recency for non-U.S. operations should verify equivalency with their operations manual and local competent authority guidance before treating FAA currency as dispositive.

Read original article