- 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>
- Overview: "Coming due" (next 30 days or 10 hours) and "Last flight" (the
most recent day's legs, meters at the end, fuel and oil left).
- Component replace / TBO / inspect intervals, inspection types and ADs take
a number and a days / months / years choice (CalendarInterval). Components
gain month columns (years stored as 12 months; months land on the same
date); inspection types and ADs keep end-of-month. ADs now honour days.
- Due list: hours already run out count as overdue; a component covered by
an inspection type no longer gets its own "Inspect every" item.
- Loading calculator moved to a partial; no limit warnings until a load is
entered. Header buttons don't wrap on phones.
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>
- 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>
- 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>
- 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>
- Notes render GitHub-flavored Markdown (commonmarker, sanitized), with a
Write/Preview editor; overview shows a plain-text excerpt
- Phone header collapses into a menu; aircraft sections use a dropdown
- Tables stack into labelled cards under 640px (opt out with .table-keep)
- Fix horizontal overflow on overview and logbook; bigger touch targets;
16px inputs to stop iOS zoom
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dark mode:
- Theme toggle in the header (System → Light → Dark); "System" follows
the OS setting and its changes. The choice is kept per browser and
applied before first paint, so there's no light flash.
- Implemented by remapping the palette under :root[data-theme=dark]:
grays flip, color tints become translucent, dark colored text becomes
its light counterpart. Page, surface, header and accent colors are
semantic tokens. Native controls follow via color-scheme.
- Chart text and grid colors follow the theme.
- Public share pages get the toggle too.
- Contrast checked against WCAG 4.5:1 (primary button text and error
text adjusted for dark).
Tables:
- Shared table style no longer forces header text left, so right-aligned
numeric headers line up with their columns everywhere.
- Flight log: units in headers, muted dashes for empty cells, GPS marker
beside the route instead of its own column.
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>
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>