mirror of
https://github.com/rickbarrette/simple-aircraft-manager-rails.git
synced 2026-11-17 15:50:36 -05:00
Docs: maintenance pages follow roles, adding aircraft
The guide pages written before roles said "owners" for work Mechanics now do too (logbook entries, corrections, asking someone to sign, components, resolving squawks, reminders), and the Fleet page didn't say who can add aircraft. The index lists roles, invitations and the new setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c360edfce0
commit
9adbc3d0a8
11 files changed
+15
-15
No files matched your search
+1
-1
@@ -20,6 +20,6 @@ The app searches the Federal Register weekly for new ADs mentioning the aircraft
|
||||
|
||||
**Comply** records the date, aircraft hours, the component, the logbook entry, the method (inspection, terminating action, AMOC) and the AD revision complied with, with details of what was done. **N/A** records that an AD doesn't apply, and why (for example, serial number outside the affected range). Recurring ADs then show when they're next due.
|
||||
|
||||
Applying an AD to the aircraft or a component, removing it, and changes to it are kept in **Activity → Record history**, with who and when. An owner can **Restore** an AD that was removed by mistake from there.
|
||||
Applying an AD to the aircraft or a component, removing it, and changes to it are kept in **Activity → Record history**, with who and when. Someone with the **Restore from history** permission (Owners) can **Restore** an AD that was removed by mistake from there.
|
||||
|
||||
Make the logbook entry for the work as well; the status report lists each AD with its method and revision (91.417(a)(2)(v)).
|
||||
Reference in new issue
Block a user