How AeroLarke keeps an audit trail DGCA can verify
Every change is recorded with who, what, when, where, the source and the reason, and chained so that any alteration shows. How the audit trail and the integrity check work.
CAR 7-J-III para 17.7 and CAR 7-J-IV para 18.4 ask for a computerised FDTL system with an "audit trail … tracked down to its source". A record that can be edited quietly does not meet that, however carefully it is kept. This is how AeroLarke’s audit trail works, and how an inspector can check it rather than take it on trust.
Every change, with its context
Each change in AeroLarke is saved together with its audit entry, in one step: the change cannot be saved without the entry. The entry records:
| Recorded | |
|---|---|
| Who | The person, by name and designation |
| What | The record and field, with the old value and the new value |
| When | Server time, in UTC |
| Where | The device and network address |
| Source | The screen, import file, API or document reference the change came from |
| Why | A reason, required for changes to verified data, overrides and adjustments |
Nothing is deleted or overwritten. A correction is an amendment that keeps the original, and removing a record is a void with a reason. The history of a duty, a crew record or a Scheme value can always be read back to its first entry.
Chained, so a change shows
An audit trail in a database could still be edited by someone with access to the database. AeroLarke makes that visible.
- Each entry is chained to the one before. An entry’s hash is computed from its own contents and the previous entry’s hash. Altering or removing any entry breaks every link after it.
- The chain head is anchored every day. Each day the latest hash is written to write-once storage, kept apart from the database. Even if someone rewrote the whole chain and recomputed every hash, it would no longer match the anchors.
- Anyone authorised can verify it. Verify integrity recomputes the chain over a period and compares it with the daily anchors. The result says whether every entry is intact, or where the chain breaks.
Each operator has its own chain, so one operator’s verification never depends on another’s data.
What an inspector sees
- Read-only access. A designated officer grants a DGCA inspector a time-limited, read-only login. Every page the inspector opens is logged.
- The reasoning behind each result. Every legality result shows the limit, the actual value, the margin and the CAR paragraph, so an inspector can follow why a duty was legal or not.
- The check itself. A designated officer can run Verify integrity with the inspector watching, over whatever period the inspector asks for.
Who can change what
The audit trail records changes; access control decides who can make them. Every change is made from a named, personal account. FDTL-critical actions, such as approving an override, verifying actual times or approving a Scheme change, also need a current designated-officer appointment, and the person who asks for an approval can never give it.
The compliance page shows the integrity check working on a demo operator.