AirLog

AirLog turns messy aircraft records into clean, structured, and verifiable digital history — improving resale trust, compliance clarity, and aircraft value.

Built on PilotLog, the foundational flight logbook engine.

Dashboard

What It Does

AirLog ingests aircraft and pilot records and produces structured outputs that answer three questions a buyer or inspector actually cares about:

1. Is this aircraft airworthy? — compliance status on annual, transponder, pitot-static, ELT, and AD records
2. Can I trust these records? — a Trust Basis that shows what is verified, what is assumed, and what is missing
3. What is the complete history? — a buyer-facing sale packet with maintenance logs, flight history, component snapshot, and gap analysis

Running Locally

git clone https://github.com/hbrazier01/Pilotlog.git
cd Pilotlog
docker compose up

Open: http://localhost:8788

Or without Docker:

cd pilotlog-cli
node src/readApi.mjs

Key Endpoints

Endpoint	Description
GET /	Dashboard — flight totals, currency, compliance alerts
GET /verify/airworthy/html	Buyer-facing airworthiness check — pass/fail on 7 compliance items
GET /verify/airworthy	Same check as JSON
GET /export/sale-packet/html	Full sale packet — Trust Basis, maintenance history, compliance calendar, gap analysis
GET /export/sale-packet	Sale packet as JSON download
GET /export/trust-report/html	Trust report — risk score, provenance, integrity verification
GET /verify/hash/:hash	Hash verification — confirm record integrity

Outputs Explained

Trust Basis (in sale packet)

Shows exactly what AirLog can confirm vs. what it takes at face value vs. what is missing. Non-technical language intended for buyers.

Airworthiness Check

Pass/fail assessment across: annual inspection, transponder/ADS-B, pitot-static, ELT battery, maintenance records, AD compliance, and flight log presence. Includes plain-language disclaimer that this is record-based, not a legal determination.

Record Integrity Hash

Every record set produces a SHA-256 hash. Any change — even a single character — produces a different hash. Buyers can compare hashes to confirm they are reviewing unmodified records.

Gap Analysis

Flags missing or overdue items (maintenance chronology gaps >12 months, missing annual, missing engine TSOH) with severity ratings.

Data

Demo data for a 2018 Cirrus SR20 (N123AB) is included in data/ and pilotlog-cli/data/. The aircraft has:

• 4 flight log entries
• 5 maintenance records including 1 AD compliance record
• Annual inspection current through 2026-05-15
• Transponder and pitot-static current through 2027

To add a flight entry:

node scripts/add.mjs --from KAPA --to KADS --total 1.3 --pic 1.3

Architecture

data/
  aircraft.json     ← aircraft specs, compliance due dates
  entries.json      ← flight log entries
  maintenance.json  ← maintenance records, AD compliance, components
  profile.json      ← pilot profile, medical, endorsements

pilotlog-cli/src/readApi.mjs   ← Express API + all HTML pages
src/services/                  ← trust report, integrity, contract simulation
src/lib/                       ← hashing, canonicalization, airframe ID
compact/contracts/airlog/      ← Midnight Compact smart contract (compiled)
scripts/                       ← CLI utilities and Phase 2 readiness validator

Phase 2 — Midnight Blockchain

The Compact smart contract (compact/contracts/airlog/src/airlog.compact) is written and compiled. It supports:

• registerAirframe — owner registers aircraft on-chain by airframe ID
• authorizeIssuer — owner authorizes A&P/IA mechanics to add entries
• addEntry — authorized mechanic records a maintenance event on-chain
• transferAirframe — ownership transfer

Local circuit simulation works today. To validate readiness for live PreProd deployment:

node scripts/validate-phase2-readiness.mjs

One-Command PreProd Demo

Run the full deploy + addEntry flow from a clean state:

cd pilotlog-cli
npm run demo

Prerequisites:

Requirement	Detail
Node.js	v22 required (nvm use 22)
Proof server	Must be running at http://127.0.0.1:6300
tNight balance	Wallet must be funded on Midnight PreProd

The demo wallet address is printed on startup. Fund it at: https://faucet.preprod.midnight.network/

What it does:

1. Builds wallet from dev seed
2. Syncs with PreProd network
3. Bootstraps dust wallet if needed (registerNightUtxosForDustGeneration)
4. Deploys AirLog contract (or joins existing from deployment.json)
5. Calls registerAirframe (new deploy only)
6. Calls authorizeIssuer (new deploy only)
7. Calls addEntry — ANNUAL inspection for N12345

Expected output:

╔══════════════════════════════════════════════════╗
║      AirLog — Midnight PreProd Demo Flow         ║
╚══════════════════════════════════════════════════╝

[1] Build wallet
──────────────────────────────────────────────────
  ✓ Wallet ready
  Address (fund with tNight): midnight1q...

[2] Sync with PreProd
  ✓ Synced
  tNight balance: 1000000

...

[7] addEntry
  ✓ SUCCESS
  tx:    0xabc123...
  block: 4821012

╔══════════════════════════════════════════════════╗
║  DEMO COMPLETE                                   ║
╠══════════════════════════════════════════════════╣
║  Contract: midnight1contract...                  ║
║  addEntry: 0xabc123...                           ║
╚══════════════════════════════════════════════════╝

The contract address is saved to deployment.json after first deploy. Subsequent runs join the existing contract and only call addEntry.

Technology

• Node.js / ES Modules
• Express (read API + HTML pages)
• Midnight Compact (ZK smart contract language)
• @midnight-ntwrk/compact-runtime (local circuit simulation)
• Docker
• SHA-256 record hashing