mirror of
https://github.com/rickbarrette/simple-aircraft-manager-rails.git
synced 2026-11-17 23:50:36 -05:00
2026.11.1: offline flight logging fixed, inspections from logbook entries, life limits from installation, component inspections moved to inspection types
- 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>
This commit is contained in:
1 parent
7552e4a8a3
commit
352a38c7fb
28 files changed
+289
-69
No files matched your search
@@ -12,7 +12,9 @@ The **Components** tab is a tree of the aircraft's parts: engine, propeller, mag
|
||||
- **Replace every** hours and/or a calendar interval in days, months or years (whichever comes first); **Replacement critical** makes overdue replacement ground the aircraft (oil, filters, ELT battery…).
|
||||
- **Expires on**: a date marked on the part, such as an ELT battery's.
|
||||
- **TBO** hours and/or a calendar interval. Under Part 91 TBO is usually a recommendation; tick **Treat TBO as a hard limit** only when an AD or the airworthiness limitations make it one, or **On condition** to show it without warnings.
|
||||
- **Inspect every** hours and/or a calendar interval, counted from the component's last service. For an inspection with its own records (an oil change, a magneto inspection, the ELT check), set it up on the **Inspections** tab and apply it to the component instead: the inspection then governs and the component's own interval is ignored.
|
||||
- **Replacement counts from**: *Last service* (the default), or *Installation (life limit)* for a part that's cleaned and reused but has a life limit, such as a reusable oil filter: its limit then counts from its total time and in-service date, and only a replacement restarts it.
|
||||
|
||||
**Inspections** of a part (a magneto's 500-hour inspection, an oil change, the ELT check) are inspection types applied to the component: use **+ Inspection** on the component's page, or set one up on the **Inspections** tab. The component's page lists them with when they were last done and are next due; they're tracked from their records, count toward airworthiness, and can be completed from a logbook entry.
|
||||
|
||||
Logged hours are added to every component that's in service.
|
||||
|
||||
|
||||
@@ -9,6 +9,8 @@ The **Logbook** tab holds the maintenance record entries. Owners write and edit
|
||||
1. Choose a **Template** to start the wording if one fits, and fill in its blanks (`__`). The built-in ones are for a pilot doing preventive maintenance on an aircraft they own or operate (14 CFR 43.3(g)); admins can add their own.
|
||||
2. Fill in the date, the **logbook** (aircraft, engine, propeller or other), the **entry type** (usually maintenance or inspection) and the **airframe total time**.
|
||||
3. For an engine or propeller entry, pick the component: its total time and time since overhaul at the entry fill in from the airframe time. Tick any **sub-components** included in the work (an oil filter on the engine) to record their times as well. On a new entry, set a sub-component to **Serviced** or **Replaced** to record that on the Components tab at the same time (an oil and filter change resets their time since service), dated to the entry.
|
||||
Its time since service then counts from the airframe time on the entry.
|
||||
Under **Inspections completed**, tick any inspection the work completes (an Oil Change): it's recorded as done on the Inspections tab at the entry's date and airframe time, linked to the entry.
|
||||
4. Write the **entry text**: what was done, with reference to the data used.
|
||||
5. The sign-off fields (who, certificate kind and number, location) are filled in when the entry is signed electronically. Fill them in yourself for an entry copied from a paper logbook.
|
||||
6. For an inspection, record the **inspection result** (approved for return to service, or a list of discrepancies given to the owner).
|
||||
|
||||
Reference in new issue
Block a user