Raising non-routine work and shop findings

When a work package is in progress, you can create new tasks to identify logbook faults reported by the flight crew or on-board systems, and other non-routine, unplanned work that has to be done. In Maintenix, these tasks are called faults. If you detected a fault, and completed the work immediately, you can raise the fault in Maintenix and close it immediately to have a record of the problem that was addressed. If the fault has not been addressed, you can raise the fault and leave it open.

For logbook faults, you can raise faults from the work package, which assigns the faults to the work package, or you can raise the faults on the inventory of the aircraft. When you raise the fault on the inventory record, never select to leave the fault open because an open fault can ground the aircraft. If the fault has been addressed, raise and close it. Otherwise, select from the other options that are available: you can raise non-urgent faults and defer them so that they will be addressed later, or raise the fault and request parts for it immediately if it is more urgent.

For faults found during the inspection phase of heavy maintenance visits or during shop maintenance, you can raise a fault from the work package, or from the tasks that are in the work package—for example, the task you were working on when you found the issue—so that the fault is associated with the task during which it was detected.

When raising a fault that occurs frequently, you might be able to use a fault definition—a reusable template that contains many of the details of the faults and that can also include troubleshooting information and possible corrective actions. To use a fault definition, someone within your organization must have created it beforehand. Otherwise, you create what is called an ad hoc fault, one that is not based on a fault definition.