Skip to content

Defer a grounding squawk

Ground-blocking squawks block all bookings on an asset until resolved. If the issue is understood and acceptable to continue operating with (for example, a known minor defect pending parts), you can defer the squawk until a stated date.

  • You must be an admin.
  • Only open grounding squawks can be deferred. Caution and info squawks have no ground effect and do not need deferral.
  • Deferral requires both a reason and an expiry date (Defer Until).
  1. Open the asset and tap the grounding squawk to open its detail screen.
  2. Under Admin Actions, tap Defer.
  3. Tap Select Date and choose the Defer Until date, the last day the deferral is in force.
  4. Enter a Reason: why the asset is safe to continue operating until that date.
  5. Tap Submit to confirm.

You see Squawk deferred. The squawk moves to deferred, the asset returns to service, and the bookings that the grounding had suspended are restored to confirmed. The squawk detail screen shows Deferred until: [date] and the reason.

The deferral is honoured through to the end of the date you set. The morning after it passes, the asset is grounded again automatically and the bookings spanning it suspend once more, unless you have resolved the squawk in the meantime. On the day the deferral expires, the syndicate’s admins get a Squawk Needs Closing reminder so the lapse does not catch anyone out.

  • “Reason is required”: enter a short explanation in the Reason field.
  • “Failed to defer”: check your connection and retry.
  • The Defer button is not shown: the squawk is not in open status, or not a grounding severity. Only open grounding squawks can be deferred.