Airworthiness rules

What it is

The Airworthiness card shows booking availability calculated from the asset’s recorded squawks and maintenance items. When a recorded restriction applies, the app blocks new bookings and lists the reasons. The calculation depends on the information entered and available to the app; it does not certify that the aircraft is safe or legally airworthy. Pilots, owners, operators and maintenance organisations retain their responsibilities under the applicable rules.

The app shows no restriction from these checks when the asset has:

No active grounding squawks.
No overdue maintenance items.
No deferred grounding squawks past their deferral date.

The app restricts booking availability when any of those conditions fail. A clear indicator does not replace pre-flight checks, required maintenance or release-to-service documentation.

Who can use it

All members see the airworthiness card on the asset detail and receive blocks when trying to book an asset with a recorded restriction.
Admins can update the records: confirming, deferring, resolving, or dismissing squawks; logging maintenance completion. App permissions do not confer maintenance or certification privileges.

Where to find it

Asset detail, Airworthiness card.
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

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

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 this booking restriction until the deferral expires. Recording a lawful deferral restores booking availability and 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 do not affect this booking calculation. Their labels do not determine whether flight is lawful or safe.
Overdue maintenance grounds the asset. An item that has reached its limit on the measure it counts — flying hours, the engine meter, or landings — 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 booking restriction clears once the item is logged complete or deleted, provided nothing else still holds it down. Deleting a record does not fulfil a maintenance obligation. Admins get an advance warning before this happens — see Maintenance items: Behaviour rules.
A maintenance item’s own limits can be deferred, separately from squawk deferral. An admin can record a permitted extension of a check’s limits, with a reason, so the app judges the check against the recorded new limits. Not every maintenance limit may lawfully be extended; the admin must record the decision of an appropriately authorised person and its relevant basis/reference. A check running on two limits can have either moved or both, each in its own units. This is a different action from deferring a grounding squawk: it applies to a maintenance item’s own due points, not to a squawk, and it does not expire on its own — it stands until the item is next signed off, deferred again, or put back with Put the limit back. See Defer a maintenance limit.
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 recorded restrictions. The create-booking dialog calls this check and refuses to create the booking when a restriction applies, 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 member’s confirmed booking with a start time in the future on the affected asset to suspended and notifies each booking’s member. Maintenance bookings are never suspended — they are how the aircraft gets back into service. 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 recorded restrictions clear (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.
Grounding and its clearing are announced to the whole syndicate, not only to members with a suspended booking. Every member gets an Asset grounded notice naming the reason (a squawk, an overdue item, or both) when a recorded booking restriction starts, and an Asset restored notice once every cause has cleared. See Notification types.