- Requests run in the viewer's zone: Profile -> Time zone, else their
device's (a tz cookie set from the browser), else the installation's;
times show in it and "today" is the local date (a new flight's date)
- Docker's TZ sets the installation zone (default UTC): scheduled jobs run
on its clock (recurring.yml), and it's used before a device's zone is known
- The weekly reminder email is worked out in the recipient's zone
- Signatures, record history and exports keep exact UTC timestamps
- users.time_zone; README, .env.example and guide updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Offline
- Flights and squawks saved offline are tagged with their user and only sent
while that user is signed in; storage is made persistent; Background Sync
sends them with the app closed (Chromium); unsent count on the app badge
- Report Squawk works offline (photos included, one-time key like flights)
- The Fleet page and, for each of your aircraft, the Overview, W&B, Log
Flight and Report Squawk pages and photo are saved ahead of time, so the
app opens and works without signal; copies say when they were saved
- Sign-out clears saved forms, pages and photos (asks first if items wait)
- Offline page rendered by Rails (localized, follows the theme, no inline
script); service worker version follows the build
Install and notify
- Web Push (web-push gem, VAPID keys from env or storage/vapid_keys.json):
grounding squawks, newly overdue items (daily, once each), signing
requests; per-device on/off and test in Profile -> This device; only
browser push service endpoints accepted
- Manifest shortcuts (Log Flight, Report Squawk via /go/...), lang and
localized description; install help on Profile; reload notice after a
release
Also
- Dockerfile: libssl-dev in the build stage (openssl gem); lockfile checksums
- Leftover English and %{_} interpolation names from the localization pass
- Guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
- Entries transcribed by Claude are unverified (with Claude's confidence)
until an owner checks them against the scan: badge, filter, "mark
verified" stepping through the rest
- Preventive maintenance templates on new logbook entries, keyed to Part 43
Appendix A(c), setting the entry type and pilot certificate (43.3(g))
- An STC's ICA can become a tracked recurring inspection, linked from its
major record
- Weight & balance: history of empty weight/CG (linked to the 337 that
changed them), loading stations and CG envelope from the POH, and a live
calculator for takeoff and landing weight/CG; shown on the status report
- New ADs: weekly Federal Register search per aircraft (aircraft, engine
and propeller models, or custom terms); track or dismiss each; included
in the weekly reminder
- Archives carry the new records; brakeman: explicit params, reviewed
About-page links
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Squawks: defer an inoperative item under 91.213(d) once each condition
is confirmed (pilots may too); deferred items stop grounding and are
listed for awareness. Resolving can record the fix as a logbook entry
(43.9 fields) or link an existing one
- Expiration dates on components (ELT battery, 91.207(c)) and documents;
new document types (registration, airworthiness certificate, insurance,
radio license). Expired replacement-critical parts and an expired
registration (91.203) ground; others warn; registration warns 90 days out
- Standard inspections: one click adds annual, 100-hour, 91.411, 91.413,
ELT (91.207(d)) and VOR (91.171) checks with the right rules, skipping
ones already tracked and linking annual to 100-hour
- Weekly Monday reminder email to owners when something needs attention;
profile opt-out; admin "send me this week's reminder"
- README feature table updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Bulk Upload page: pick many files or a folder; each file becomes a
document named after it, and files sharing a name become one multi-page
document. Files go up as direct uploads with per-file progress.
- Direct uploads require a signed-in user and check type/size up front;
only fresh, unattached blobs can be attached; abandoned uploads are
purged nightly.
- DedupDisk storage service: each distinct file is stored once under its
SHA-256 and blobs hard-link to it; nightly sweep (and storage:dedupe)
links pre-existing duplicates and drops unused objects.
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>