- Edit on a flight: owners can correct any flight; a pilot, the flights
they logged (the same rule as its engine data).
- Date, airports, route, notes, oil and fuel (its oil and fuel records
follow) and the attached files can always be changed.
- The meter readings only on the latest flight, while its tach in is
still the aircraft's tach: the aircraft and installed components move
by the difference, and with both readings the duration is worked out
from them. On earlier flights they're locked (later flights started
from them), pointing to Update Hours; the server ignores them too.
- Each correction is in the activity log with what changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With a signal so weak requests hang, the phone still says it's online, so
nothing fell back: Log Flight waited minutes with no feedback, and pages
never reached the offline page.
- Log Flight and Report Squawk say "Sending…" and, after 10 seconds
without an answer (60 with photos), keep the entry on the device as
with no signal. When the top bar is already red they keep it right
away. If it got through after all, the copy sent later is dropped
(same client_key).
- What's kept on the device isn't sent while the top bar is red, gives
up after 15 seconds, and goes again as soon as the server answers.
- Every page of the app falls back to its kept copy or the offline page:
after 10 seconds, then 3 while requests keep failing, and at once right
after a failure. Downloads made while you wait (.sam.zip, records
package, PDFs) have no time limit.
Checked on an Android 14 emulator with a connection that accepts
requests and never answers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Setup checklist on a new aircraft's Overview (owners): components,
standard inspections, DRS AD import, registration/airworthiness
certificate, weight and balance; hideable per device
- Log Flight: "Save and log next leg" reopens the form on the same date,
starting where the leg ended
- Component form: limits in two collapsible groups (replacement and expiry;
overhaul and TBO), open when in use
- Squawk form warns what "Ground Aircraft" does
- Logbook entry form: inspection result only for inspection entries
(show-when controller); document names default from the file
- Dates in pickers, the activity log, airworthiness lines, search, audits
and transcription notes use the app format
- No duplicate Report Squawk button on Squawks; "Record service" label
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>
- 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>
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>
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>