AC 120-78B chapter 3:
- Every change to logbook entries, sub-components, signatures, inspection
records, AD compliance, major records, W&B, components, squawks and
documents is kept as a RecordVersion (who, IP, when, field changes),
hash-chained per aircraft; versions can't be edited or deleted. Shown on
each logbook entry and in Activity -> Record history
- Nightly job: SQLite online-backup copy to storage/backups, verified
(integrity_check + record counts), pruned to the configured number; then
an integrity check of the history chains and every signature's seal and
fingerprint. Results on Admin -> About ("Back up and check now"); admins
are emailed on failure
- Software versions recorded (first/last seen) on Admin -> About
- Records package (Access & Sharing): logbook entries PDF with signatures,
signatures.csv, record-history.csv, self-contained status report HTML,
the .sam.zip, and a README, for the FAA/NTSB or a buyer
- Legacy (paper) records: documents can be marked as legacy records;
aircraft have an "electronic records since" date (status report, package)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Inspection types say what overdue means: grounds the aircraft, no IFR
(91.411), no transponder (91.413) or advisory. Overdue limitations show
as a new LIMITED status ("VFR only", "No transponder") and don't block
flights under airworthiness enforcement
- "Also counts as": an annual satisfies the 100-hour (91.409(b))
- Overrun allowance: a 100-hour done within 10 hrs of due counts the next
one from when it was due; done early, from when it was done
- Per-aircraft maintenance clock (tach or Hobbs) for time in service; new
records default to it (fixes the tach-offset mismatch)
- Status labels Current / Due soon / limitation / Grounded, with the
91.7 pilot-in-command note
- Migration converts existing types by name; archives carry the new fields
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Existing single attachments migrate to the new list. Photos open in a
full-screen viewer (swipe/arrow keys); every file has a download link.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AirTrail (https://github.com/johanohly/AirTrail):
- File export (Flights → Export for AirTrail) in AirTrail's import
format, validated against its schema; same-day repeat legs get leg
numbers so AirTrail's de-duplication doesn't merge them.
- Automatic sync through AirTrail's REST API (Profile → AirTrail sync):
per-user connection with an encrypted API key and scope check; flights
are created/updated/deleted in background jobs; a full sync first
links flights already in AirTrail (e.g. from a file import) instead of
duplicating them; airports are resolved and cached, with manual
mapping for unknown codes.
- GPS tracks: GPX, KML and CSV track logs are converted to AirTrail's
track format for both sync and export; the flight page shows a summary.
- Aircraft ICAO type (e.g. C150) for AirTrail's aircraft type.
Airport database (OurAirports, the source AirTrail uses):
- Managed like AirTrail: downloaded in the background on first start,
updated in place from Admin → Airports (adds, changes, removes; ids
stable), with admin-managed custom airports that updates never touch.
- Each airport carries AirTrail's code, so logged codes translate to
AirTrail's exactly (1B9 → K1B9, 4MB → K5M3).
- From/To autocomplete on new flights (airports this aircraft has used
rank first); From is pre-filled with the last flight's destination;
codes are normalized to uppercase.
- Flights → Standardize airport codes: rewrite logged codes to the
standard code, and fix codes not in the database (typos such as 0R8 →
08R are suggested).
Also: admin pages grouped under an Admin dropdown menu.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Flights tab:
- Summary cards for the past 30 days, this year, past 12 months and
since the first flight (flight hours, flights, tach, fuel).
- Flight hours by month (last 24 months) with the past-year monthly
average, totals (flights, flight/tach time, average and longest
flight, fuel, gal/hr, airports visited, most visited) and a by-year
table.
- Flight time is Hobbs time where recorded, otherwise tach time.
Removed the per-aircraft DRS search link and its "Open in DRS" button:
each AD's DRS link already comes from the Excel import. A guarded
migration drops the column.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AD import (owners, ADs tab → Import from FAA DRS):
- Upload a DRS export (.xlsx recommended, .csv works), preview, confirm.
- Per AD: track, not applicable, or skip, with suggestions and flags for
superseded/non-current ADs, model mismatches, appliance and STC-only
ADs, repetitive actions, and older ADs this one supersedes.
- ADs are matched by number; re-importing updates existing ADs from the
FAA data (preview lists what will change) without touching compliance
records, recurrence or applicability. Superseded tracked ADs are
updated and flagged rather than skipped.
- DRS's Excel export hyperlinks each AD number to its DRS page; those
links are kept (http(s) only). DRS ids aren't derivable from the AD
number, so no links are guessed.
Also:
- Per-aircraft "not applicable" AD determinations (N/A badge, quick
action, excluded from airworthiness).
- AD numbers link to their DRS document in the AD list, compliance
history (now with description, logbook/inspection links) and share page.
- Saved DRS search link per aircraft with an "Open in DRS" button.
- Upload storage extracted to a StoredUpload concern shared with the
flight import.
- document_url / drs_search_url added in their own guarded migration
(they were briefly in an already-applied migration).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rails 8.1 + SQLite rewrite of marbindrakon/simple-aircraft-manager,
designed to self-host as a single container (Solid Queue/Cache/Cable,
Active Storage on disk, Hotwire + importmap, Tailwind).
- Airworthiness engine ported from health/services.py (ADs, grounding
squawks, inspection recurrency, component replacement)
- Hours updates and flight logs cascading to in-service components,
optional airworthiness enforcement
- Components, squawks, ADs, inspections, logbook, documents, major
records, oil/fuel consumption stats and charts, activity log
- Admin/owner/pilot RBAC and public share links (status/maintenance)
- Docker Compose and Kamal deployment, env-driven production config
- Service and integration tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>