How grounding squawks work

A squawk is a reported defect — the aviation word for “something is wrong with this asset”. Syndik8 takes every squawk seriously enough to record it, but only some squawks stop the asset being used. Three severities, a short lifecycle, and a deferral mechanism make the difference — and the reasons for each are worth knowing before you need them.

Why three severities and not two

A plain “can I fly it or not” boolean throws away too much information. Real operating experience has three kinds of finding:

Grounding — something that must be fixed before the asset is used again. Low oil pressure, a cracked exhaust, a tyre worn to the canvas.
Caution — something the next user needs to know about but can work around. An intermittent landing light, a broken chart-holder clip, a worn cowling fastener.
Info — a historical record the group wants on the asset. A small tear in the upholstery, a radio frequency programmed unusually.

Collapsing the middle and lower categories into “not a problem” is a false economy. A caution squawk carries forward to the next pilot’s pre-flight check; an info squawk builds the asset’s long-term record. Only grounding blocks availability — caution and info do nothing to the booking calendar. See Squawk severities for the exact behaviour of each.

Why grounding is binary at the asset level

The question “is the asset grounded right now?” has to have one answer. You cannot half-ground an aircraft — either a member can book it today or they can’t. Syndik8 computes a single airworthiness boolean per asset, visible on the asset detail and enforced by the booking dialog. A single open grounding squawk sets it to no; resolving or deferring that squawk sets it back to yes. See Airworthiness rules for everything that feeds that calculation.

The nuance lives inside the boolean. An asset is non-airworthy because of a specific squawk with a specific reason; the group sees that reason in plain text on the airworthiness card. The binary is cheap; the explanation behind it is rich.

The squawk lifecycle

A squawk moves through a short set of states: pending → open → (deferred or resolved or dismissed). Pending exists only when the syndicate requires admin confirmation of reports; it lets an admin weigh severity before the grounding effect kicks in. Open is active. Deferred, resolved, and dismissed are the three ways a squawk leaves active status. See Squawk statuses for the transitions and who can make them.

Nobody can reopen a resolved or dismissed squawk — if the same defect returns, the correct action is a fresh squawk, referencing the original if useful. Keeping the history immutable protects the audit trail.

Deferral is a controlled tool, not a workaround

The most common question about this model is: “what stops an admin from just deferring every grounding squawk so the asset keeps flying?” The answer is that deferral is engineered as a controlled operational tool.

Deferral requires a reason. The admin types it into the deferral form, and it is stored on the squawk.
Deferral requires an expiry date. The asset is ungrounded until that date, not indefinitely.
The date ticks. Once the deferral date is in the past, the asset re-grounds automatically. Nobody has to remember — the airworthiness rules include a check for deferred squawks past their date.
The deferral is on the record. It appears on the squawk, and the reason and date are visible to every member, not only admins.

The model reflects how small operators already work. Regulations in various jurisdictions let an operator fly on with a known minor unserviceability, provided the deferral is reasoned, recorded, and time-bounded. Syndik8 encodes that pattern rather than pretending every defect is either nothing or total grounding.

Why resolution is separate from dismissal

Resolving a squawk says the defect has been fixed. Dismissing a squawk says the defect wasn’t real — a mis-report, a duplicate, a misunderstanding. These are different statements and the group’s record should show which one happened. Dismissal requires a written reason, for the same audit-trail reason deferral does. See Squawk statuses for the exact rules on who can do each.