Airworthiness rules
What it is
Section titled “What it is”Airworthiness in Syndik8 is a per-asset, always-current answer to: “can this asset be booked right now?” The answer is computed from the asset’s squawks and its maintenance items; it is not a flag a human sets. When the answer is no, the app blocks new bookings and the asset detail displays a banner listing the reasons.
An asset is airworthy when it has:
- No active grounding squawks.
- No overdue maintenance items.
- No deferred grounding squawks past their deferral date.
An asset is not airworthy when any of those conditions fail.
Who can use it
Section titled “Who can use it”- All members see the airworthiness card on the asset detail and receive blocks when trying to book a non-airworthy asset.
- Admins can resolve the underlying issues: confirming, deferring, resolving, or dismissing squawks; logging maintenance completion.
Where to find it
Section titled “Where to find it”- Asset detail, Airworthiness card (heading labelled “Airworthiness”).
- When creating a booking: the booking dialog runs an airworthiness check and shows a warning when the asset is grounded.
- Route:
/syndicates/:syndicateId/assets/:assetId.
Fields / options
Section titled “Fields / options”The airworthiness card shows a boolean status and a list of issues. Each issue has a type and a human-readable message:
| Issue type | Triggered by |
|---|---|
| Grounding squawk | An open grounding squawk (not pending, deferred, or resolved). |
| Overdue maintenance | A maintenance item with calculated status overdue. |
| Overdue deferred | A deferred squawk whose deferral date is in the past. |
Behaviour rules
Section titled “Behaviour rules”- An open grounding squawk grounds the asset. By default a reported grounding squawk opens, and grounds, immediately; where the syndicate requires confirmation a member’s squawk stays pending and does not ground until an admin confirms it. See Squawk statuses.
- Deferral clears the ground effect until the deferral expires. Deferring returns the asset to service and restores its suspended bookings, unless another grounding cause still holds it down (a second open grounding squawk or an overdue maintenance item) or the booking still overlaps an active maintenance window. Once the deferral date is in the past, the squawk grounds the asset again automatically and re-suspends those bookings, with no further admin action required.
- Caution and info squawks never ground. They are visible but carry no airworthiness impact.
- Overdue maintenance grounds the asset. An item whose engine hours have reached its limit, or whose calendar due date has passed, grounds the asset exactly like an open grounding squawk: new bookings are blocked and the future confirmed bookings that span the asset are suspended. A live or past booking is left alone, so a flight already under way stays loggable. The asset returns to service once the item is logged complete or deleted, provided nothing else still holds it down.
- Multiple issues accumulate. If the asset has both an open grounding squawk and an overdue maintenance item, both appear as separate issues in the list.
- Booking creation respects airworthiness. The create-booking dialog calls the airworthiness check and refuses to create the booking when the asset is not airworthy, showing the list of reasons.
- Future confirmed bookings are auto-suspended when the asset grounds. Whether the cause is an open grounding squawk or an overdue maintenance item, the server flips every confirmed booking with a start time in the future on the affected asset to suspended and notifies each booking’s member. In-progress bookings (already started) and past bookings are left as-is, so their usage stays loggable. The suspended bookings flip back to confirmed, with a “booking restored” notification, only when the asset returns to service (no open grounding squawk and no overdue item) and the booking no longer overlaps an active maintenance booking. Bookings still inside a maintenance window stay suspended until that maintenance booking is removed, shrunk, or cancelled. If a deferral later expires, the asset is grounded again and those bookings suspend once more.