> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How to Verify Record Integrity
> Run integrity verification checks on regulatory records, interpret hash chain status, and export proof bundles for auditors using PlaneConnection's record integrity dashboard.
The Operations module must be enabled for your workspace. You also need the appropriate operations
permissions. Contact your workspace administrator if you cannot access these features.
Record integrity verification requires the **Admin**, **DOM** (Director of Maintenance), or
**Safety Manager** role. The Records module must be enabled for your workspace. If you cannot
access **Ops > Record Integrity**, contact your workspace administrator.
By the end of this guide, you will have navigated to the record integrity
dashboard, selected an aircraft, reviewed its hash chain status, run a
verification check, interpreted the results, and exported a proof bundle
suitable for an auditor or regulator.
The integrity dashboard covers all protected record types -- not just maintenance. Safety reports,
investigations, corrective actions, flight logs, dispatch releases, crew training records, and
other regulatory records all appear in the integrity dashboard alongside maintenance records. See
[Tamper-Evident Aviation Records](/en/explanation/record-integrity) for the full list of 19
protected record types.
For background on how the record integrity system works, see [Tamper-Evident
Aviation Records](/en/explanation/record-integrity).
## Navigate to the record integrity dashboard
### Step 1: Open the Record Integrity dashboard
From the main navigation, go to **Ops > Record Integrity**. The dashboard
displays a summary of integrity status across your fleet. Each aircraft is
listed with a status indicator, the date of the most recent verification, and
the number of records in its hash chain.
### Step 2: Review the fleet summary
The fleet summary uses three status indicators:
| Status indicator | Meaning |
| ---------------- | ----------------------------------------------------------------------------------- |
| **Green** | All records verified. Hash chain intact. All applicable anchors confirmed. |
| **Amber** | Verification has not run recently, or one or more anchor confirmations are pending. |
| **Red** | Hash chain break detected. One or more records may have been altered. |
A red status indicator requires immediate attention. Do not dismiss it without investigating the
affected records. Contact your PlaneConnection account team if you need assistance diagnosing
the cause of a hash chain break.
## Select an aircraft and view its hash chain
### Step 1: Select an aircraft
Click an aircraft's tail number on the dashboard to open its record integrity
detail view. The detail view shows:
* **Chain length:** total number of records in the hash chain.
* **Last verified:** timestamp of the most recent successful verification.
* **Anchor status:** confirmation status for RFC 3161, OpenTimestamps, and EVM
anchors, where applicable.
* **Recent records:** a paginated list of maintenance records in chain order,
each showing its record type, date, technician, and hash status.
### Step 2: Browse the hash chain
Scroll through the chain to review individual records. Each record shows:
| Field | Description |
| -------------- | ----------------------------------------------------------------- |
| Record type | Work order, inspection, safety report, flight log, training, etc. |
| Date | When the maintenance action was performed. |
| Technician | The user who created or signed off the record. |
| Hash status | Whether the record's hash matches its stored value. |
| Anchor status | Which external anchors have confirmed this record's hash. |
| Chain position | The record's position in the chain (useful for locating a break). |
Use the filter controls to narrow the chain view by date range, record type, or technician. This
is useful when you are looking for a specific record before generating a proof bundle for an
auditor.
## Run a verification check
### Step 1: Initiate a full verification
From the aircraft's record integrity detail view, click **Run Verification**.
The system will re-compute the hash for every record in the chain and compare
it to the stored value. This process typically takes a few seconds for chains
of up to a thousand records.
Verification runs in the background for very large chains. You will receive an in-app notification
when the check completes. You can navigate away from the page while it runs.
### Step 2: Wait for the verification to complete
The dashboard displays a progress indicator while the verification runs. When
complete, the status indicator updates and a summary report appears.
### Step 3: Review the verification summary
The summary report shows:
| Field | Description |
| ----------------- | -------------------------------------------------------------------------- |
| Records checked | Total number of records in the chain that were verified. |
| Records passed | Records whose hash matched the stored value. |
| Records failed | Records where a hash mismatch was detected. |
| Chain intact | Whether the entire chain from first to last record is unbroken. |
| Anchors confirmed | Count of records with at least one confirmed external anchor. |
| Anchors pending | Count of records awaiting anchor confirmation (normal for recent records). |
## Interpret verification results
### Green status: all records verified
Every record's hash matches its stored value and the chain is unbroken. All
RFC 3161 timestamps have been confirmed. OpenTimestamps anchors that have had
sufficient time to confirm (typically 10--60 minutes after creation) are
confirmed. No action is required.
### Amber status: pending anchors or stale verification
Amber most commonly appears for one of two reasons:
**Pending anchor confirmation.** Recently created records (within the last hour
or two) may show OpenTimestamps anchors as pending. This is normal -- the
Bitcoin anchoring process requires a block confirmation, which takes
approximately 10 minutes on average. The status will resolve to green
automatically as confirmations arrive.
**Stale verification.** If a full verification has not run in more than 30 days,
the dashboard flags the status as amber to prompt a fresh check. Run a new
verification as described above to resolve this.
### Red status: hash chain break detected
A red status means at least one record's hash does not match the value stored
at the time the record was created. This indicates one of the following:
* The record's content was modified after it was saved.
* A system error corrupted the record's data.
* The hash storage itself was modified.
The verification summary identifies the chain position of the first break.
Records before the break are unaffected. Records at and after the break position
require review.
Do not manually edit or delete records flagged by a red integrity status. Doing so may further
alter the chain and complicate investigation. Contact PlaneConnection support immediately. For
records that are critical to an ongoing regulatory audit, notify your Principal Operations
Inspector (POI) if the affected records cannot be confirmed within 24 hours.
## Export a proof bundle for auditors
### Step 1: Select the records to include
From the aircraft's record integrity detail view, use the date range picker or
check individual records to select those you want to include in the proof bundle.
For an audit covering a specific inspection period, select the relevant date
range. For a full airworthiness review, select all records.
### Step 2: Click Export Proof Bundle
Click the **Export Proof Bundle** button in the top-right of the detail view.
Choose your export format:
| Format | Contents | Use case |
| -------- | ------------------------------------------------------------------------------- | ------------------------------------------ |
| **PDF** | Human-readable records with embedded hash values and anchor proof summaries. | Regulatory submissions, inspector review. |
| **JSON** | Machine-readable bundle with full hash chain data and raw anchor proof objects. | External verification tools, legal review. |
| **Both** | PDF and JSON in a single ZIP archive. | Comprehensive audit packages. |
### Step 3: Verify the export
After download, verify that the proof bundle opened correctly and contains the
expected records and date range. Share the bundle with the auditor or inspector
directly -- no PlaneConnection account is required to read or verify a proof
bundle.
Auditors can verify RFC 3161 timestamp tokens using standard OpenSSL commands. OpenTimestamps
proofs can be verified at opentimestamps.org or using the open-source `ots` command-line tool.
Neither tool requires PlaneConnection access.
## Related
Understand the trust model behind hash chains and external anchoring.
Technical specifications for RFC 3161, OpenTimestamps, and EVM anchor types.
Creating maintenance work orders that feed the hash chain.
Full data export options for compliance and audit purposes.