- "Swapping a tray-mounted nav/com unit" cited Part 43 Appendix A
(c)(32), which doesn't exist; the item is (c)(31). Its wording now
names that paragraph's conditions (self-contained, panel-mounted,
tray-mounted, manufacturer's instructions, operational check before
use).
- "Updating the navigation database" called itself preventive
maintenance under (c)(31). 14 CFR 43.3(k) says such an update isn't
maintenance: it's now an Other entry citing 43.3(k), with no
certificate type.
- Built-in templates now take their entry type from the YAML (it was
always Maintenance).
- A migration fixes copies already in the database where an admin
hasn't changed the text; edited ones are left alone.
- Test: every built-in template is valid and cites an existing
Appendix A paragraph.
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>