- 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>
- Photos show as 64px thumbnails (160px resized copies, made once with
libvips and kept; lazy-loaded) that open the in-app viewer, which has
Download; other files keep their name chip and download link
- image_processing gem and the vips variant processor (libvips was already
in the image)
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>
- 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>
- more_menu helper (menu / menu-item styles): each section keeps its main
action as a button; imports, exports, printing and tools move under More
(flights, logbook, logbook entry, documents, inspections, fleet)
- Aircraft header: More with status report and, for owners, access &
sharing, edit, .sam.zip and records package; Access & Sharing and Oil
Analysis tabs removed (oil analysis is under Oil & Fuel with a switch)
- Logbook: Print selected appears once an entry is ticked; filters apply on
change; dates use fmt_date (also AirTrail, notes, audits, About)
- Header shows the role on the aircraft and hides the usual Available badge;
no second Grounded badge on the Overview; AD DRS import listed once
- Flights: stat cards 2x2 on phones; By year opens visibly, only with more
than one year; duplicate + Log Flight removed
- Remove unused hello_controller.js; guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Delete methods nothing calls: BackupRun.last_good, EntrySignature#short_id,
Sso#issuer_origin, InspectionType#effect_label and #latest_record_for,
ApplicationHelper#airworthiness_dot, Airworthiness::Status#can_fly? and
FlightStats#shortest_flight (tests now check red? / longest_flight)
- Routes: sessions and passwords limited to the actions that exist
- Theme toggle: drop the unused button target
- Action Cable was never used (no broadcasts or streams): async adapter in
production, solid_cable gem, cable database and app/channels removed
- Empty system test setup removed with capybara and selenium-webdriver
- Compliance: one due_result helper for overdue / due soon; inspections use
next_due for the date, as ADs do
- applicable_to moved into SharedRecordHistory (was identical in ADs and
inspection types)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/guide/disclaimer.md, shown as Help -> Disclaimer: provided as is, not
FAA-approved, user verifies legal and suitable use (43.9/43.11/91.417,
AC 120-78B), status and AD matches don't replace the records or the PIC's
decision, no liability, host responsible for the instance
- README: notice at the top and a Disclaimer section
- Footer notice on every page (app and public layouts), notice on first-run
setup, link from Admin -> About and the guide's start page
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shown on Admin -> About, in the software history, records package, procedures
and sam:doctor; release notes in the app under Help.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tested against real Federal Register data:
- aircraft searched as make + model ("Cessna" "150L"), which drops the
transport-category ADs that merely contain the model string
- components also searched as maker + type ("Bendix" "magneto"): appliance
ADs usually name a series, not the exact model; "A/B" makers are split
- propellers also searched as maker + "propeller"
- custom terms add to the automatic searches (they used to replace them,
silently turning off engine/component searches); a bare aircraft model is
skipped since make + model covers it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Besides the aircraft and engine/propeller models (and families), each
in-use component is searched as maker + model designator and as
component type + designator (e.g. "Champion 4301", "Magneto 4301"),
so appliance ADs (magnetos, ELTs, radios, transponders) are found
- A match records the component; tracking it makes the AD apply to that
component instead of the airframe (ad_alerts.component_id)
- Page hint, guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The viewer compose uses the published image (from docker-compose.image.yml)
and a throwaway secret key, plain HTTP on localhost.
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>
- Insert suggested text for Hosting and network (HTTPS, sign-in mode,
password/lockout rules, Docker) and Additional procedures (common
Part 91 procedures; electronic-records date filled in), with
[bracketed] blanks for what only the owner knows
- A revision can't be adopted while a [blank] is left (Markdown links ok)
- Generated sections state HTTPS and the sign-in mode from the config
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 10 failed sign-ins in a row (password, authenticator code, or password
at signing) lock an account for 15 minutes from any address; the user
is emailed; admins can unlock. Same message as a wrong password.
- Passwords: at least 12 characters (max 72), refused if found in Have I
Been Pwned (k-anonymity range API; fails open; PWNED_PASSWORDS_CHECK=false)
- Optional TOTP (authenticator app) with 10 recovery codes for password
and emailed-link sign-in, and at signing (auth method password_totp);
codes accepted once; admins can reset; SSO sign-in unaffected
- Demo/test passwords updated; guide, README and procedures document
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>
- 16 Markdown pages covering every area for pilots, owners, mechanics
and admins, readable on GitHub
- /help renders them with a page list; links between pages work in both
places; only listed pages can be opened
- The electronic records instructions (AC 120-78B user instructions) are
now the guide's records page, also used as the procedures appendix
- Help link in the main menu
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Admin → Recordkeeping Procedures: generated procedures document
(2.2.11 / 3.2.8) from the system setup plus owner-entered details;
adopted as numbered, immutable revisions; included in the records package
- Admin → Records Audits: periodic QC checklist (3.2.8.5) combining app
checks with a restore test, sampled entries vs. source documents and a
user review; next due date on About and in admins' weekly reminder
- User instructions at /help/records, linked from the logbook and signing
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>
- Sign an entry: review exactly what's certified, choose a current
certificate (eligibility checked: pilot only for preventive maintenance,
inspections need their result and time), re-enter the password or sign
in again with SSO (prompt=login, within 5 minutes), and confirm the
"Certified by" statement (43.9 return to service, 43.11(a)(5) for
inspections, preventive maintenance for pilots)
- The signature stores signer, certificate, statement, UTC time, how they
authenticated, IP/browser, a SHA-256 fingerprint of the entry's content
and a readable snapshot; an HMAC seal covers the signature record. Status
shows Valid / Superseded / Altered since signing. The signer is emailed
- Signed entries (and their sub-components) can't be edited or deleted;
a correction entry, once signed, supersedes the original (kept)
- Owners invite an outside mechanic by email to sign one entry: one-time,
14-day link; they create or use their own account and certificate and
see only that entry
- Admins can disable accounts (signed out, can't sign in or sign; past
signatures kept); users with signatures can't be deleted
- Printouts show the electronic signature and fingerprint; archives carry
signatures (marked imported, with their origin) and corrections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Once a component is chosen, its sub-components are offered on the entry
form (and the squawk Resolve page); ticked ones are saved with their
total time and time since service, worked out from the airframe total
time like the component's (editable; blank before it was installed)
- Entry page and printed PDFs list each sub-component with its serial
number and times; parts without an overhaul type read "Since service"
- Archives carry them: the original format's list of components per entry
(first = the entry's component, the rest = sub-components)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Templates move to the database (Admin -> Logbook templates: add, edit,
delete, restore the built-in ones). The built-in preventive maintenance
set is added once on first use; deletions stick. A template can set the
entry type, logbook (picking the matching component) and certificate
- Template list shows "Name — Part 43 App. A (c)(6), (c)(23)" instead of
the doubled parentheses
- Component total time and time since overhaul are worked out from the
entry's airframe total time (current times shifted by the difference);
blank when the entry predates the overhaul; typing them stops the
automatic updates
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An entry can link a component (engine, propeller…) and records its total
time and time since overhaul at the entry; picking the engine or prop log
selects that component and fills its current times (editable). Squawk
fixes carry the squawk's component
- Components have an overhaul type (major, factory overhaul, factory new),
shown as SMOH / SFOH / SNEW
- Printouts: engine and propeller entries add the serial number, total
time and SMOH/SFOH (blanks when no component is linked); airframe total
time is labelled as such; full-page layouts draw a box around each entry
- Archives carry the entry's component and times (the original format's
components / component_hours), no longer dropped on import
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Print one entry or several (tick them on the logbook list) as a PDF:
Avery 5164/8164 or 5163/8163 adhesive labels (start at any label on a
partly used sheet), or half-letter / letter pages
- Each entry has the aircraft and serial, log, date, total time in
service, the work, the signer's name and certificate, and a blank line
to sign by hand; inspection entries with a recorded result get the
43.11(a)(5) statement unless the text already certifies
- Labels: long entries shrink to fit, then continue on the next label.
Pages: entries follow one another with their signature lines, numbered
- Generated with Prawn (built-in fonts; unsupported characters become ?)
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>
- Admin -> About: Email card (delivery, server, encryption, login name,
From; never the password) and a "Send test email" button that sends
immediately and shows the SMTP error if it fails
- SMTP: implicit TLS on port 465 (or SMTP_TLS=true), auth only with a
username, 10-15 s timeouts
- "Email me a sign-in link": single-use (spent by any later sign-in via a
monotonic users.last_signed_in_at), 15-minute expiry, confirm step so
mail scanners can't use it up, same answer for unknown addresses, rate
limited, off when PASSWORD_LOGIN=false
- Admin -> Users shows last sign-in
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- SSO via OmniAuth OpenID Connect (Authentik, Keycloak, …): link by stable
subject, by verified email, or from the profile; optional auto-create,
admin-group sync, and turning password sign-in off
- Current password required to change email or password; password changes
and resets sign out other sessions; idle sessions expire after 30 days;
"sign out everywhere else"; session reset on sign-in
- Rate-limit password resets; scope squawk components to the aircraft
- Strict Content Security Policy with nonces (inline handlers removed),
Permissions-Policy and COOP headers; file links expire after an hour
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>
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>
Flight import (owners, Flights tab → Import from spreadsheet):
- Upload .xlsx or .csv, preview, then confirm. Columns are matched by
header name (Date, From, To, Tach, Hobbs, Oil, Fuel, Flight Time).
- Each flight's time is derived from the previous row's meter reading;
rows are kept in file order so typos (tach going backwards) are
flagged and skipped while the next good row absorbs the time.
- Unchanged tach imports as a 0.0 hr entry so fuel/oil isn't lost;
"Full" fuel is warned about; re-imports skip existing rows.
- History only: component hours are untouched unless the owner opts in
to advancing the aircraft's meters to the last reading.
- Upload redirects to a GET preview (Turbo ignores 200 renders after a
form POST, which made the button appear to do nothing).
Consumption charts:
- Replace per-fill math (qty ÷ hours since last add), which spiked to
80 gal/hr on partial fills and top-offs, with a rolling rate (total
added ÷ hours over a trailing 10 h fuel / 25 h oil window).
- Headline shows recent (last ~50/100 hrs) and lifetime rates; straight
chart lines instead of splines.
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>