Skip to content

Reports, inspector access and a record you can verify

The reports your regulator and your Head of Operations ask for, a read-only login for inspectors, and a history of every change that an integrity check can verify.

Who, what, when, where, source and why

Nothing is deleted or overwritten. Every change keeps who made it, the old and new value, the time, the device, the source and the reason, and each entry is chained to the one before.

History, DM 211–21416-Nov-2026, times in UTC
  1. P. Menon, FDTL officer

    Verified and locked the actual times for DM 211–214Locked
  2. R. Iyer, Operations controller

    Actual on-blocks, DM 214: from 12:40 to 12:52

    Source: journey log photo. Reason: block time corrected from the journey log.

  3. A. Okafor, Captain, crew app

    Acknowledged the roster for 16-Nov-2026

Integrity check passed. Every entry matches the hash chain; none altered or removed.

What it does

Compliance reports
Quarterly fatigue and extension reports, crew FDTL statements, the exceedance register, cumulative limits and document expiry.
Operations reports
Daily duty log, crew monthly schedule, duty by type, sector summary, monthly flying report, and the warnings and violations register.
Excel export
Rosters and dashboards export to Excel for your own analysis.
Amendments, not edits
A correction keeps the original beside it; removing a record is a void with a reason.
Integrity check
Entries are hash-chained, and a daily chain head goes to write-once storage. Verify integrity recomputes the chain and compares it.
Inspector access
A time-limited, read-only login, granted by a designated officer, with every visit logged.
Crew see their own
Each crew member sees their own FDTL statement and records, and nobody else’s.

See it working on a demo operator

We show you the screens with demo data, then talk through your own Scheme, fleet and bases.