Many aviation authorities require that records in a digital logbook cannot be changed without a trace, and that pilots can show this on request. FLYLOG.io helps you meet these requirements with two features: Lock Flight Records and Audit Log. You can find both in Settings, in the section Prevent altering of flight records.
Regulatory background
EASA requires pilots to keep a reliable record of all flights (FCL.050) and allows the logbook to be kept electronically if it follows the required format (AMC1 FCL.050). In the US, pilot logbook requirements are set by 14 CFR 61.51, and the FAA’s guidance on electronic records and signatures is AC 120-78B. Some authorities, such as the Swiss FOCA, also require that every change in a digital logbook is traceable and included in printouts. Lock Flight Records and the Audit Log are designed to help you meet these requirements.
How it works
Lock Flight Records stops changes: flights older than 24 hours can no longer be edited.
Audit Log records changes: every time a flight is created or edited, the change is saved with the date, the time, and the old and new values.
Digital signatures protect signed flights: a signed flight cannot be edited. If you unlock it to make changes, the signature is removed and this is recorded in the Audit Log.
Lock Flight Records
When enabled, each flight is locked 24 hours after it is created and can no longer be edited. Locked flights are marked with a lock icon. To change a locked flight, contact our support team.
⚠️ Important: Once enabled, only our support team can disable this feature. If you need help, contact us at support@flylog.io.
Audit Log
The Audit Log shows when your flights were created or changed, newest first, grouped by day. For each change you can see:
Date and time of the change, to the second
Type of change: Created or Edited
Flight details: route, registration, flight date and flight time
Which fields changed, with the old value (crossed out) and the new value
Open an entry to see all details. Tap Open flight to go to the flight record.
Example: you change your role on a flight from SIC to PICUS. The Audit Log shows the changed fields (Role: SIC → PICUS, PICUS: 0.0 → 9.8, SIC: 9.8 → 0.0) together with the exact time of the change.
Signed flights
A flight with a digital signature (for example from an instructor or examiner) is protected and cannot be edited. This keeps the signature valid for exactly the data that was signed.
If you need to change a signed flight:
Open the flight record.
Tap Signed.
Tap Unlock. FLYLOG.io warns you that unlocking removes the signature.
Confirm with Yes. The signature is removed and the flight can be edited.
Removing a signature cannot be undone, and reverting the flight to an earlier version does not bring the signature back. The Audit Log records the removal as a change to the flight’s files, so it is always visible when a signature was removed. If the flight needs to be signed again, request a new signature. See Digital Signatures.
Restore an earlier version
Revert (next to a day): returns your logbook to how it was on that day.
Revert all changes after this (inside an entry): undoes all changes made after the selected moment.
Removed signatures are not restored by reverting.
Showing your records to an authority
You can export the Audit Log as a PDF and share it with an authority on request, together with your logbook export.
Open the Audit Log.
Tap the PDF icon (top right).
Choose All changes or a Date range.
Good to know
The Audit Log is available on web and mobile.
Included in both Basic and Premium plans.
Still need help?
Send us an email and our support team will help you.
Contact support
