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>
- AD compliance "next due at tach reading" is prefilled from the AD's
hour recurrence (hours at compliance + interval), recalculates live as
the AD/date/hours change, keeps a typed-in override, and is filled
server-side when left blank.
- Live "Next due" preview on AD compliance and inspection record forms
(hours and/or end-of-month date, whichever comes first), mirroring
Compliance.next_due so preview and status agree.
- Reject an interval entered as the next-due reading (e.g. "100" for
"every 100 hours"), which made a complied AD show as overdue.
- ADs table shows hours remaining next to the due tach reading.
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>