- Components can't be made into a parent loop, and the parts tree walks
stop safely if one exists (logbook entry and squawk resolution pages
crashed).
- A rejected aircraft photo no longer breaks the edit page; empty photos
are refused; images that can't be read aren't resized, and a failed
resize sends the original instead of an error.
- Unsupported formats (/report.pdf…) answer 406; tampered upload
references, out-of-range numbers and constraint violations get a form
message instead of a 500; requests with null bytes are refused (400).
- Blank values in required columns with defaults take the default;
optional links to records that don't exist are validation errors.
- Imports (oil report, logbook scans, .sam.zip) accept only uploaded files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Refuse to start with a placeholder or short SECRET_KEY_BASE (under 32
characters); warn and fail sam:doctor under 64. .env.example no longer
ships a placeholder.
- First-run setup needs a one-time code printed only in the server log, so
only whoever runs the server can create the admin account.
- AirTrail: the server resolves the address and connects to exactly that;
never the server itself or link-local addresses (cloud metadata);
private-network addresses only for admins or hosts in
AIRTRAIL_ALLOWED_HOSTS.
- Host authorization when APP_HOST is set: APP_HOST, the APP_URL host,
ALLOWED_HOSTS, localhost and IP addresses; /up exempt. A blocked name
gets a short explanation instead of a blank 403.
- docker-compose.direct.yml: HTTPS without a proxy via Thruster's built-in
Let's Encrypt (TLS_DOMAIN).
- Notes' Markdown no longer allows the unused class attribute.
- README, .env.example and the user guide updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Aircraft photos get 192px and 960x432 copies made on upload; the header,
share page and Fleet cards use them (and the offline copies), instead of
the full original.
- Flight, engine data, component and major record details show one label
and value per row on phones (wide items no longer add grid columns).
- Profile re-records this device's push subscription on every visit, and
says why if it can't; Send test delivers now and lists each device's
result; Google's other push hosts are accepted; turning notifications on
shows the browser's actual error.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 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>
- 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>
- 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>
- Service worker keeps the Log Flight form when opened via Turbo, serves the offline page's script and icon, and treats 502/503/504 as offline; the offline page only links forms actually kept
- Serviced sub-components restart from the airframe time flown since the entry
- New logbook entries can complete inspections (recorded and linked to the entry)
- Components: replacement limit can count from installation (life limit)
- Component-level "Inspect every" / "Inspection critical" removed; a migration converts any unlinked settings into inspection types with a first record; component page lists its inspections
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>
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>
Shared records keep applicability in join tables, so linking to the
airframe or a component, unlinking, edits to the shared record and a
component's deletion are now appended to each affected aircraft's hash
chain. Owners can restore a removed link from Activity -> Record history.
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>
- Inlining CSS used String#sub with a replacement string, so "\&" in
escaped selectors became "</head>"; use block replacements
- Packaged status report and procedures omit the Back link, the print
button and the favicon link (they don't work outside the app)
- Status report: "On condition (Part 91)" as Tracked as, with remaining
hours shown for reference; on condition clears the hard-limit flag
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>
As POH moment-envelope charts and Garmin Pilot give it. Stored as CG
inches (moment x 1000 / weight), shown back as entered with the CG next
to each point; switching the units and saving re-reads the numbers.
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>
- 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>
- 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>
- Admin -> Settings: maximum upload size per file (1-1024 MB, default 50),
stored in a new settings table and read on each use, so a change applies
to every process at once
- Enforced by attachment validation and the direct-upload endpoint; upload
forms, bulk upload and Admin -> About show the current limit
- .sam.zip import accepts files up to 1 GB to match
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>
- Ruby 3.2.3 (end of life) -> 4.0.9 in the Docker image and .ruby-version
- config.load_defaults 8.1
- All gems at their newest compatible versions, including json 3.1,
roo 4.0, rubyzip 3.7 and solid_cable 4.1
- Admin -> About: running revision and build time, uptime, Ruby/Rails/
SQLite and key gem versions, which features are configured (never
secret values), storage and database sizes, background job health,
record counts. The image takes APP_REVISION and APP_BUILT_AT build args.
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>
Existing single attachments migrate to the new list. Photos open in a
full-screen viewer (swipe/arrow keys); every file has a download link.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New Oil Analysis tab: one record per oil sample with dates, hours, the lab's
verdict and comments, ppm results for 12 wear metals with the lab's averages,
and the report PDF. Shows wear-metal trends, a side-by-side history table,
and flags readings 1.5x or more above the lab average.
AvLab report PDFs can be imported: every sample on the report (current and
previous) is added unless already recorded, the engine is matched by serial
number, and reports for another tail number are refused. The parser reads
positioned text and drops the hidden color-code layer that overlaps results.
Adds the pdf-reader gem. Test fixture is a rebuilt report with a dummy header.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Attach a CGR-30 flight recording when logging a flight or later from the
flight page. The flight page shows engine run time, fuel burned, tach and
engine hours, peak RPM/EGT/CHT/oil/fuel flow, and charts per cylinder.
Unreadable files are rejected; recordings from another tail are flagged.
Also replace the real tail number in test data with N12345.
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>
Flights tab:
- Summary cards for the past 30 days, this year, past 12 months and
since the first flight (flight hours, flights, tach, fuel).
- Flight hours by month (last 24 months) with the past-year monthly
average, totals (flights, flight/tach time, average and longest
flight, fuel, gal/hr, airports visited, most visited) and a by-year
table.
- Flight time is Hobbs time where recorded, otherwise tach time.
Removed the per-aircraft DRS search link and its "Open in DRS" button:
each AD's DRS link already comes from the Excel import. A guarded
migration drops the column.
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>
- 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>