Bombardier Global 7500 task-card records review

When this review is needed

• A Global 7500 finished a check and the closed card set has to be verified before it clears the program status.
• A buyer's diligence team wants the last check's cards reconciled to the tasks they were meant to accomplish.
• Cards from a check performed away from the primary provider arrived in a batch and need matching to the program.
• A management handover left the closed card set filed separately from the program status it updated.

The problem

A check produces hundreds of cards, and a set can look complete while individual cards fail the details that matter: a missing inspection stamp, a reference to a superseded revision of the maintenance instruction, or a sign-off that does not cover the whole scope of the card. Matching each card to the program task it clears is tedious, so it is often skipped, and the program status is updated on the assumption that the cards behind it all hold. That assumption is what a careful reviewer or a buyer takes apart.

What gets reviewed

• Routine cards from the check matched to the program tasks they are meant to clear
• Sign-offs checked for the right authority and coverage of the full card scope
• Inspection stamps confirmed present where the card and the task require them
• The maintenance instruction each card references confirmed to be the correct revision
• Deferred or carried-forward items on cards tracked to where they landed
• The program status update reconciled against the cards that support it

What gets validated

• Each closed card maps to a program task and the status update it produced
• Sign-offs cover the full scope of the card, not only a portion of the work
• Required inspection stamps are present and legible on the cards that call for them
• The referenced maintenance instruction is the revision in effect at accomplishment
• Items deferred on a card are traceable to a non-routine or a later closure

Evidence normally required

• The closed task-card set from the check
• The program task list the cards are meant to satisfy
• The maintenance instruction references cited on the cards
• The program status output the check updated
• Any deferral or carry-forward register from the check

Common discrepancies

• A card closing a program task but referencing a superseded revision of the instruction
• A sign-off that covers part of a card's scope with the remainder unstamped
• A program task shown complete with no card in the set that clears it
• A deferral noted on a card that does not appear on any carry-forward register

What is at stake

A card that does not properly close leaves the program task it was meant to satisfy effectively open, which means the status overstates what has been done. A buyer who finds that pattern discounts the whole check package, and a receiving operator may have to re-accomplish tasks it thought were current. Reassembling a missing stamp or a correct reference long after the check is far harder than confirming it while the check paperwork is fresh.

How the work runs

What the buyer receives

• A supported exception list of cards that do not properly close their program task
• A source map from each program task to the card and evidence that clears it
• A closure plan naming the stamp, reference, or sign-off each open card needs

Who uses the output

• Records teams confirming a check package before it clears the program status
• Asset managers reading check-package integrity into the value of the tail
• Continuing-airworthiness leads verifying tasks are truly closed before an induction

How the work fits into the transaction or program

The task-card review is where the program status is proven at the card level, so a clean set confirms the program picture the maintenance-program review established. Cards that do not close feed the non-routine review when they raised findings, and the reconciled set becomes part of the check evidence a redelivery or sale relies on.

Aircraft-specific considerations

The Global 7500 carries an integrated cabin and avionics suite, so its task cards reference maintenance instructions that revise often, and a card built on a stale reference is a common miss on a young type. Because much of the fleet is managed rather than owner-operated, checks are performed at different facilities across the aircraft's life, and card format and sign-off convention vary between them. The review normalizes those differences enough to match every card to its program task.

Jurisdiction-specific considerations

A Global 7500 whose checks were performed under one authority and whose next operator sits under another may hold sign-offs and stamps in a form the receiving system reads differently. The review notes where card evidence will need supplementing for the receiving register, without asserting either authority accepts it.

Regulatory limits

The review confirms the cards close their program tasks and carry the sign-offs and references they require. It does not re-accomplish a task, sign off any card, or make an airworthiness determination on the aircraft.

What this review does not cover

• Re-accomplishing or signing any task card
• Physical inspection of the work the cards record
• Any airworthiness determination on the aircraft

Specific to this review

• A card can be signed and stamped and still not close its task, if it references a superseded revision of the instruction it was built from.
• Partial sign-offs are a frequent miss, because the card looks closed until you check that the stamp covers every step of its scope.
• A deferral written on a card but never carried onto a register is where an open item quietly disappears from the status.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits