Files
simple-aircraft-manager-rails/docs/guide/inspections.md
T
rickyandClaude Opus 5.5 fe3fba1736 User guide in docs/guide, shown in the app under Help
- 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>
2026-11-07 13:40:09 -05:00

19 lines
1.2 KiB
Markdown

# Inspections
The **Inspections** tab shows each required inspection, when it was last done and when it's next due.
## Setting up
**Standard inspections** adds the recurring inspections and checks Part 91 calls for (annual, 100-hour, pitot-static and altimeter, transponder, ELT…). Pick the ones that apply to how the aircraft is flown; each comes with its interval and what being overdue means, and you can change them afterwards.
**+ Inspection Type** adds your own, for example a recurring inspection from an STC's instructions for continued airworthiness. Each type has:
- **Recurring** every so many hours, calendar months (due at the end of the month) and/or days.
- What overdue means: **grounds the aircraft**, **no IFR flight** (91.411), **transponder can't be used** (91.413), or **advisory only**.
- **Overrun allowance**: for the 100-hour, 10 hours. Done late within it, the next one counts from when it was due (91.409(b)).
- **Also counts as**: an annual also counts as the 100-hour.
## Recording an inspection
**Record** next to an inspection logs the date and hours it was done, optionally linking the logbook entry. The [logbook](logbook.md) entry is the signed record (14 CFR 43.11); write it too.