- Views use lazy t(".key") lookups; sentences with values or links stay
whole (interpolation, _html keys); counts use one/other plurals
- Stored-value labels (statuses, types, priorities...) are LabelSets read
from labels: in the current locale; field names and validation messages
under activerecord:; flash and activity text under flash:
- Services, models, helpers, mailer subjects, the logbook PDF, procedures
templates, records package README and transcription warnings localized;
the PDF reuses LogbookEntry#certification_statement instead of a copy
- Scripts read js: strings from a JSON tag via app/javascript/i18n.js
- Dates through I18n.l (app, weekday, month_year, long formats); html lang
follows the locale
- APP_LOCALE picks the language (falls back to English); missing
translations raise in development and tests
- README: Translating section and APP_LOCALE
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- sam:doctor: health report (secret key, address, HTTPS, SMTP and SSO
reachable, Google Drive, migrations, disk, jobs, backup/check/off-site/
procedures/audit recency); exits 1 on a failure
- records:check: backup now + history and signature check; exits 1 on a problem
- backups:list / backups:restore[file]: checks the copy (nightly or Drive
.gz), refuses while the server runs, moves the current DB aside, asks
(CONFIRM=yes to skip)
- users:sign_out_all, sam:records_package[tail], email:test[address],
offsite:backup, offsite:restore_test
- Admin guide: maintenance commands table, restore steps use backups:restore
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Admin → Off-site Backup: connect a Google account with your own OAuth
client (drive.file scope; refresh token and secret encrypted)
- Nightly after the verified database backup: upload the gzipped snapshot
(newest N kept, Settings) and every uploaded file not yet copied
- Restore test downloads the newest copy, opens and checks it, and checks
sampled files against their checksums; failures emailed to admins
- About, procedures document, policy completeness and audits use it
- offsite:restore_files rake task; restore steps in the admin guide
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>
- Users add their FAA certificates (kind, number, optional expiry) on
their profile; admins see them on the Users list
- "Sign as" on new/edited logbook entries and the squawk Resolve page
fills the signer's name, kind of certificate and number (expired
certificates aren't offered); deferrals default to mechanic for users
with a mechanic certificate
- Weekly reminder lists certificates expiring within 60 days (or lapsed
in the last 30), even when nothing else is due
- Preventive maintenance templates keep a certificate already chosen
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>
- Logbook entries record the signer's kind of certificate and number and
an inspection's result; maintenance and inspection entries list what
43.9 / 43.11 needs that's missing (flagged, not enforced). Transcription
reads the certificate details too
- AD compliance records the method (inspection, terminating action, AMOC,
not applicable) and the AD revision complied with, filled in from the AD
when blank; the method sets the permanent / N/A flags
- Maintenance status report (91.417(a)(2)): total times, life-limited
parts, time since overhaul, inspection and AD status, major alterations,
open discrepancies; print or save as PDF; on maintenance share links too
- Archives carry the new fields
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Oil analysis: Blackstone PDF import (20 elements, oil properties, universal
averages), results stored per element, oil type, "leave out of trends",
the original app's statuses; AvLab fixes (multi-line comments, unrelated
labels no longer steal values). Existing records migrate.
- Aircraft archives in the original app's .sam.zip format (schema v2): export
from Access & Sharing, background import from the Fleet page, rake tasks.
Archives move both ways between this app and the original.
- Scanned logbook pages (images or PDFs) upload as a document; with
ANTHROPIC_API_KEY set, Claude transcribes them into logbook entries.
- Fix: deleting a component or aircraft failed when AD compliances or
inspection records pointed at a component.
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>
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>