Authorities In development
We don’t guess.
Every rule, checked against the source.
Read from the authority’s own legislation, recorded with the clause it came from, versioned and dated — so you know exactly what you are filing, and when it was last confirmed.
Verification status
Where each one stands
We publish the verification state of every authority rather than a single coverage number, because “supported” means nothing on its own.
Verified means the logging rules were read from that authority’s own legislation and recorded with the clause they came from. Verifying means specific items still rest on secondary sources — and we name which ones.
Ten verified today. Fourteen mapped. The ones still being checked stay on this page while they are checked — taking them down until they were finished would make the list look better and mean less.
| Authority | Region | Rules verified | Night begins | Command model |
|---|---|---|---|---|
| FAA | United States | Verified | End of evening civil twilight | Sole manipulator |
| EASA | European Union | Verified | End of evening civil twilight | Designated command, with PICUS |
| UK CAA | United Kingdom | Verified | 30 minutes after sunset | Designated command, with PICUS |
| QCAA | Qatar | Verified | End of evening civil twilight | Designated command, with PICUS |
| GCAA | United Arab Emirates | Verified | End of evening civil twilight | Designated command, with PICUS |
| HKCAD | Hong Kong | Verified | 30 minutes after sunset | Designated command, with PICUS |
| TCCA | Canada | Verified | End of evening civil twilight | Position flown |
| CASA | Australia | Verified | End of evening civil twilight | Designated command, with ICUS |
| NZCAA | New Zealand | Verified | Sun’s centre 6° below horizon | Designated command, with PICUS |
| CAAS | Singapore | Verified | 20 minutes after sunset | Designated command, with PICUS |
| GACA | Saudi Arabia | Verifying | Civil twilight (unconfirmed) | Sole manipulator |
| DGCA | India | Verifying | 30 minutes after sunset (unconfirmed) | Position flown |
| CAAC | China | Verifying | 1 hour after sunset (unconfirmed) | Sole manipulator |
| JCAB | Japan | Verifying | Not yet confirmed | Experience-based |
A note on Singapore. Singapore’s night rule is not in the licensing standards where you would expect it — it sits in the Air Navigation Order, Part I paragraph 2: “the time between 20 minutes after sunset and 20 minutes before sunrise, sunset and sunrise being determined at surface level.” The surface-level qualifier matters at altitude, and it is the kind of detail that gets lost when a limit is copied from a screenshot rather than read from the source.
A note on Japan. JCAB has no statutory per-column personal-logbook mandate — its framework proves experience rather than prescribing a page. We will present JCAB output as an experience summary, not as a “statutorily compliant JCAB logbook”, because the second thing does not exist.
The process
How a rule gets into Sojourn
This is the part most logbooks skip entirely. It is also the part that decides whether the number on your export is right.
Read from the source
The rule is taken from the authority’s own legislation — not from a forum post, not from another app’s template, not from a screenshot. The clause it came from is recorded with it.
Versioned and dated
Every rule set carries a version and an effective date. Your export can say which version produced it, so a figure you filed last year stays explainable this year.
Re-checked on a schedule
Regulations are amended. Rule sets are re-checked against their sources on a monthly cycle, and the “last confirmed” date moves only when someone has actually looked.
Nothing ships as verified without sign-off
An unconfirmed item is marked unconfirmed — on this page and in the app. The same posture Sojourn Tax uses for its country rules.
Fly for anyone. Flight-time limitations are computed from operator schemes we build and version, not from limits you type in yourself. Don’t see your operator’s rules? Send them — we’ll build the scheme, verify it, and it then works for everyone at your airline.
Figures are indicative — confirm against your Operations Manual. Not legal advice.
Why this is hard
Four different nights
There is no single definition of a night hour. There are four rule families, and an hour logged under one is simply not the same quantity as an hour logged under another.
Civil twilight
FAA, EASA, TCCA, GCAA, QCAA, CASA. Night runs from the end of evening civil twilight to the beginning of morning civil twilight. New Zealand says the same thing more precisely — the sun’s centre 6° below the horizon.
Sunset ± 20 minutes
Singapore. Twenty minutes after sunset until twenty minutes before sunrise — with sunset and sunrise taken at surface level, which the Air Navigation Order is careful to specify.
Sunset ± 30 minutes
UK CAA and Hong Kong — both verified verbatim, Hong Kong’s at CAD 371 §7.16. A genuine divergence from EASA civil twilight. India is on the same reading, not yet confirmed.
Sunset ± 60 minutes
CAAC. A full hour either side.
One further trap: the FAA's sunset-plus-one-hour window exists, but it governs night-landing currency only — not the logging of night time. Conflating the two is a common and silent error.
Why this is hard
Two incompatible ideas of command
Sole manipulator
FAA · GACA · CAAC
You log command when you are sole manipulator of an aircraft you are rated for. Two people can log command for the same flight. There is no PICUS concept at all.
Designated command, with PICUS
EASA · UK CAA · GCAA · QCAA · CASA · NZCAA · CAAS · HKCAD
Command belongs to the designated commander alone. A pilot flying under supervision logs PICUS in a separate column, countersigned. A student on a dual flight logs no command time.
Canada and India use a third, position-based model. This is precisely why command time cannot be stored as a single number and carried between authorities. Exporting an EASA record to an FAA template means re-mapping PICUS deliberately — usually to co-pilot, and to command only where the pilot genuinely was sole manipulator. Copying it straight across would overstate command time on a legal document.
Why this is hard
Two more places the numbers diverge
Instrument time is two different quantities
The FAA family logs instrument time only when you are flying solely by reference to instruments — actual conditions or under the hood. Time on an IFR flight plan in clear air is not instrument time.
The EASA family carries an IFR operational-condition column, which is time conducted under IFR and can include IFR in visual conditions. Different question, different answer.
So actual conditions, simulated conditions and time under IFR are stored as three separate fields, and each authority's column is built from the right ones.
Cross-country has no shared threshold
The FAA is the outlier with a distance test — over 50 nautical miles for most credit, with 25 and 15 mile variants, and a 50-mile no-landing rule for the ATP.
EASA, the UK and the UAE define cross-country by pre-planned route and navigation, with no distance in the definition at all. New Zealand uses 25 miles, but measured from the departure aerodrome rather than the point of landing — a different test wearing similar clothes.
So the record stores the landing points and the greatest distance from departure, and each template applies its own threshold, or none.
See it done once
One flight record, exported to an FAA page and an EASA page side by side.