How one flight record files correctly with every authority

1

Capture

Block and airborne times in UTC. Departure and arrival aerodromes. Aircraft type and registration. The crew role you actually flew. Actual conditions, simulated conditions and time under IFR, kept apart.

2

Enrich

Sun and twilight timestamps are resolved for the position and date of the flight, and the greatest distance from departure is computed from the route. These are facts about the flight, not interpretations of it.

3

Compute at export

Choose an authority. Night, cross-country and command time are calculated against that authority's rules, into that authority's columns, at that moment.

The same record answers a second question. Those three steps produce your hours record. They also produce your flight-time-limitation position — duty, rest and the cumulative limits, run against the authority you fly under. One set of entries, two outputs.

Most logbooks stop at the first. Duty and rest end up in a separate system you do not control, which is why pilots so often know exactly what they have flown and not whether they can fly tomorrow.

Fly for anyone. Don’t see your operator’s rules? Send them — we’ll build the scheme, and it then works for everyone at your airline.

Version one computes your actual position from the record you already keep — no roster feed required. Forward projection comes after. Sojourn shows you where you stand. Figures are indicative — confirm against your Operations Manual. Not legal advice.

Flight-time limitations

Not a second app.
The same record.

Most logbooks stop at hours flown. Duty and rest end up in a system you do not control — which is why crew so often know exactly what they have flown, and not where they stand for tomorrow.

1

It runs on what you logged

Duty and flight times, the duty schedule, report and release, sectors, rest between them. Your own entries — not a roster we parsed weeks ago and assumed was still current.

A roster that changed is corrected by you, in place. Nothing is projected from stale data.

2

Verified rules. No guessing.

Every limit is read from the authority’s own legislation, versioned and dated — and where we hold your operator’s scheme, the company’s rule governs, because that is the one that reaches you.

A rule we have not confirmed against a primary source is marked unconfirmed rather than quietly applied.

3

Every figure shows its working

Not just the answer. Tap a number and the app shows the arithmetic, the table it read, the clause it came from, and whose rule it was — your operator’s, the authority’s, or your own override.

You stay in control of a judgement that stays yours, and you learn the rule while you use it.

The dashboard before a duty: next duty Dubai to London, an alcohol cut-off counting down in one hour thirty-five, report at 02:43 local against a scheduled departure of 04:08, the planned flight duty period drawn against the maximum with one hour ten of margin, and a week of coloured duties below. — **Before you go**The alcohol cut-off counting down, the report time 1:25 ahead of STD, and the planned duty against the maximum.

The dashboard during a duty: Dubai to Perth marked in progress, three hours six elapsed, the planned flight duty period of 12:45 against a maximum of 14:00 with one hour fifteen of margin, four crew with bunk rest. — **While you are on it**The duty in progress — elapsed against planned, and the margin still in hand.

The dashboard after a duty: London to Dubai marked resting, rest from 11:12 local against a required twelve hours, two hours one minute rested and nine hours fifty-nine until available, with the minimum noted as the authority’s. — **And afterwards**Rest taken against rest required, whose rule set it, and the hour you are available again.

A How this is worked out page: the operator’s own report pad of 1:25 taken off a scheduled departure of 11:30 to give a 10:05 report, badged to the airline; then the acclimatisation clock deciding which table applies and a long two-pilot sector factored to two sectors, both badged to the authority, each step showing its arithmetic and the clause it came from. — **How this is worked out**Each step with its arithmetic, its clause, and *whose* rule it is — the company’s own scheme sets the report time here, the authority sets the tables.

App screens over a fictional crew and operator; Sojourn Logbook™ is in beta testing. Figures are indicative — confirm them against your Operations Manual. Not legal advice. The app shows you where you stand and how it got there; deciding whether to accept a duty remains yours, which is exactly why it shows its working rather than handing you a verdict.

The rule behind it

What we refuse to store

Night, cross-country and command time are never written to the record as numbers. Not once. The moment you store “4.9 hours night” you have silently committed to one authority's definition, and the record becomes wrong everywhere else without ever looking wrong.

This is the single decision the whole app is built around, and it is the reason the same logbook can file correctly in Dubai and in Dublin.

Where the authorities disagree

Getting your history in

Import, without inventing anything

Roster import

Sojourn reads the rosters airlines actually publish. Where a source carries a field, we use it. Where it does not, we leave the field empty and tell you — we do not infer a registration or a crew name that the roster never contained.

Coming from another logbook

Imported totals are marked as imported. If a previous app stored a categorised night total under rules we cannot reconstruct, that total is preserved as a carried-forward figure rather than silently recomputed as though we knew how it was derived.

Honest provenance over silent inference. A logbook is a legal document, and a plausible guess in one is worse than a visible gap.

See one record become two documents

View the sample export

Capture once.Compute at export.