Skip to content
Syndik8

Defer a maintenance limit

Defer a maintenance limit

Section titled “Defer a maintenance limit”

Move a maintenance check’s own due point out, with a recorded reason, instead of completing the work right now.

This is a different feature from deferring a grounding squawk. That one lets the asset keep flying past an open defect report. This one moves a scheduled check’s own limit — there is no defect and no squawk involved, just a check that would otherwise fall due, or has already, before the work is booked in. If you are here about a reported defect rather than a scheduled check, use Defer a grounding squawk instead.

Before you start

Section titled “Before you start”
  • You must be an admin.
  • The check must already have a limit to move: a due point recorded on at least one of its clocks. A completed item has nothing to defer, and neither does a check that has never been given one.
  • A reason is required, and is shown on the check to everyone who reads it.
  • Deferring moves the limit. It does not silence the warning and does not stop the asset grounding once the moved limit passes — see Airworthiness rules.
  • Syndik8 does not suggest how far to move a limit. Each field opens on where that limit falls due today, and you move it. How much tolerance a check may be given varies by check and by maintenance organisation, and that is your call to make and record, not the app’s.

Steps

Section titled “Steps”
  1. Open the asset: Syndicate → Assets → [asset].
  2. Open Maintenance on the asset.
  3. Tap the check whose limit you want to move.
  4. Tap Defer (or Change deferral, if the check is already deferred).
  5. Move the limit. The dialog shows one field for each limit the check actually has, each opening on where that limit falls due now:
    • New limit — an hours or cycles check’s own limit, in the units it counts. Type the new limit itself, not the amount you are adding.
    • Deferred until — a calendar limit. Tap it and pick the new date.
    • A check running on two limits (“50 hours or 4 months, whichever comes first”) shows both, and you may move either or both. A field you leave alone stays where it is.
    • You can only move a limit outwards, never in. A limit earlier than the one the check was originally set to would ground the asset sooner rather than later, which is not a deferral.
  6. Enter a Reason: why the check is safe to leave until the new limit.
  7. Tap Defer the limit to confirm.

You see Limit deferred. The check is now judged against the new limits — its status, and whether it grounds the asset, both follow the deferred limits rather than the original ones. The check’s screen and its card in the maintenance list both show each moved limit, who deferred it and when, and the reason. The check’s own screen additionally names the limit each one was deferred from; the list card leaves that out, because a card has room for what the aircraft is flying on rather than what it used to be.

Deferring again starts from where the limit already stands, not from the original, undeferred one — so a check already deferred to 1,210 hours opens on 1,210, and you move it on from there. You can also pull a deferral back part of the way: the earliest you may choose is the limit the check was originally set to.

To cancel a deferral outright, tap Put the limit back. The check goes straight back to the limits it was deferred from, which may take the asset out of service immediately. A deferral otherwise stays in force until you change it, or until the check is next signed off — completing the work clears every deferral on it automatically, because the new cycle starts fresh from that completion. See Log a maintenance task.

If it goes wrong

Section titled “If it goes wrong”
  • “Enter a valid figure greater than zero”: the figure entered is not a usable number.
  • “Can’t be earlier than … , the limit this check was set to”: the new limit is inside the original one. Deferring can only move a limit outwards.
  • “Move a limit out to defer this check”, with Defer the limit greyed out: every field still holds the limit the check was originally set to, so there is nothing to record. Move one of them — or, if you meant to cancel an existing deferral, use Put the limit back.
  • “Enter where this limit now falls due”: the field has been left empty. Every limit the check has must hold a figure before the deferral can be recorded, even the one you are not moving — confirming with a blank would wipe a limit you only cleared by accident. Put it back where it was and move the other.
  • Defer the limit stays greyed out: the Reason field is empty. Fill it in to enable the button.
  • “Couldn’t defer the limit”: the limit is unchanged. Check your connection and try again.
  • The Defer button is not shown: either you are not an admin, or the check has no limit to move — a completed item, or one with no due point recorded on any of its clocks.

See also

Section titled “See also”