Night Time Tracker

Loggable night time runs from the end of evening civil twilight to the beginning of morning civil twilight (61.1) — note that's different from both sunset/sunrise and from the hour-offset window used for night landing currency under 61.57(b). Log time by the twilight definition and landings by the 61.57 window; keeping the two straight is most of the value of a dedicated night record.

You can — everyone does, once, the night before a deadline, and that's how transposition errors enter applications. Because night time has three different definitions (civil twilight, 61.57's hour-after-sunset, logging vs currency) that must not be blurred, the re-adding also involves judgement calls per entry, made hastily. This ledger moves those calls to logging time, when the flight is fresh, and reduces the deadline-night task to clicking Export.

Because the follow-up question to any lifetime total is always 'and recently?' Insurance renewals quote on 12-month night activity, checkout policies on 90-day recency, and interviewers read recent columns as current competence. The tiles recompute both windows on every page load, so the recency answer is as current as the lifetime one.

By design: career and currency records are sensitive, and the simplest privacy guarantee is never transmitting them. Local-only storage means zero servers, zero breach surface and zero subscription. If you fly from several devices, keep one as the master record and move snapshots between machines with the CSV export.

Always — the CSV export is a complete, lossless dump of your night record, generated locally in one click. Import it into commercial logbook software, archive it in your records folder, or post-process it in a spreadsheet. No lock-in is a deliberate design decision: data you can't take with you isn't really yours.