Raise Fault
Explanation
In aircraft maintenance, a fault is raised when a problem is discovered.
A fault is sometimes referred to as a non-routine maintenance, finding, or
discrepancy. Faults are found and raised by the flight crew during flights,
inspections, and by technicians while performing maintenance work. After
assessing a fault, it can then be fixed or deferred.
You can only raise and edit faults when the device is online.
You can raise a fault in two ways:
-
From the Technician Lobby: When raising a
fault from the Technician Lobby, select the
aircraft on which the fault was found. If you do not select a flight for
the Found During Flight field, the technician can
either the defer the fault or work on it once the fault is published
from CAMO. If you do not select a flight for the Found During
Flight field, you cannot specify skill requirements.
-
From the Aircraft Turn Details page: When
raising a fault from the Aircraft Turn Details
page, the fault is assigned to the aircraft of the selected
turn and the Found During Flight field is set to the
last arrival flight for the aircraft. When raising a fault from the
Aircraft Turn Details page, you can also add
labor requirements and scheduled hours.
Once a fault has been created, you can update information about the fault
from the Task
Details or Fault Details page
before the fault is deferred or closed.
You can raise and close a historic fault by selecting Raise and close, then specifying the corrective action and other details.
Prerequisites
- Aircraft configuration and flight information must be available
within Line Maintenance Execution.
- Company and Site must be
defined under the resource group.
- Skill certificates must be set up.
System Effects
- If the found during flight was specified during the raise fault
process, a task is created with the Active status, and
a fault record is created with the Open status.
- If the found during flight was not specified, only a fault is
created with the Open status.
- If you raise a fault from the Aircraft Turn Details page or if you specify a flight during which the
fault was found
when raising a fault from the Raise Fault page, the fault is
automatically packaged to the existing work package. If a work package does not
exist, the fault is packaged into a newly created work package.
- A new fault is created in CAMO.
- A fault raised from the My Aircraft Turns
page is assigned to an existing work package if one exists. If not,
the fault is packaged into a newly created work package.
- A fault raised from the Technician Lobby
is not assigned to a work package until it is published from CAMO.
- A fault raised by a pilot through the eLogbook application is
packaged into an IN WORK work package at the flight's arrival airport.
If a work package doesn't exist, the fault is packaged into a newly
created work package.
- If specified, skill requirements and assignments for the executor,
certifier, and inspector roles are added to the Task Details
and Fault Details pages.
- If specified, skill requirements, assignments and scheduled hours
for the Executor role are synchronized to CAMO.
- If the Flight Safety Impact or ETOPS Significant toggles are enabled, two sign-off lines are added to the task: Task Certifier and Inspector (RII). If not, only the Task Certifier sign-off line is added.