Releasing an aircraft to service certifies airworthiness. This certification can be done when you are completing an aircraft work package.
You can initiate releasing an aircraft to service and then go on to release the aircraft to service by clicking Release Aircraft on the Aircraft Turn Details page when the work package is In Work.
Before you release the aircraft to service, in the Release Status section of the Aircraft Release page you can view if there are any issues that prevent the work package from being completed and the aircraft from being released to service. You can also view if any configuration warnings have been issued by the Configuration Management Service (CMS). The release status information categories are as follows:
| Release Status Information Category | Values | Impact on aircraft release |
| Configuration Warning |
A red Yes indicates that at least one configuration issue was identified via the CMS validation and a configuration warning was raised on a task or fault in the work package for the aircraft turn. A green No indicates no configuration warnings were identified. |
No impact. The warning is for information only. The technician may decide to release the aircraft to service or fix the problem according to the definitions of the airline. |
| Open Faults | A red Yes indicates that at least one fault is in the Open status on the aircraft. A green No indicates no open faults. | Must be assigned to the work package and closed or deferred to proceed. |
| Open Tasks | A red Yes indicates that at least one task is in the Active or In Work status on work package for the turn. A green No indicates no open tasks. | Must be completed to proceed. |
| Mandatory Components Missing | Missing mandatory
components refer to tracked and assembly parts which have not been
ere the configuration slot is mandatory. Missing mandatory components refer to tracked (TRK) and assembly (ASSY) parts that have been removed from the aircraft but have not yet been reinstalled. A green No indicates that there are no missing mandatory components in the aircraft. A yellow Yes indicates that there are missing mandatory components in the aircraft and the RELEASE_MISSING_COMPONENT parameter in Maintenix is set to WARN, with no hard stop in effect. A red Yes indicates that there are missing mandatory components in the aircraft and the RELEASE_MISSING_COMPONENT parameter in Maintenix is set to ERROR, with a hard stop in effect. |
To proceed with the
aircraft release, you must install the missing mandatory component. When the missing mandatory component field indicates Yes in red, only authorized users can override a hard stop. |
| Overdue Faults | A green No
indicates that there are no overdue faults in Maintenix for the
aircraft, for which the deadline has passed. A yellow Yes indicates that there are overdue faults in Maintenix for the aircraft, for which the deadline has passed, the same fault has not been closed in Line Maintenance Execution, and the RELEASE_OVERDUE_ FAULT parameter in Maintenix is set to WARN, with no hard stop in effect. A red Yes indicates that there are overdue faults in Maintenix for the aircraft, for which the deadline has passed, the same fault has not been completed in Line Maintenance Execution, and the RELEASE_OVERDUE_ FAULT parameter in Maintenix is set to ERROR, with a hard stop in effect. Note: Faults are considered overdue even when they are assigned to a work package. |
To proceed, you should
package the fault into a work package and then close it. If the
fault is already in your work package, you should close or defer it
or request a maintenance operations controller (MOC) to extend the
deadline. When the Overdue Faults field indicates Yes in red, only authorized users can override a hard stop. |
| Overdue Tasks | A green No
indicates that there are no overdue tasks in Maintenix for the
aircraft, for which the deadline has passed. A green Yes indicates that there are overdue tasks in Maintenix for the aircraft, for which the deadline has passed, the same task has not been completed in Line Maintenance Execution, and the RELEASE_OVERDUE_TASK parameter in Maintenix is set to OK. A yellow Yes indicates that there are overdue tasks in Maintenix for the aircraft, for which the deadline has passed, the same task has not been completed in Maintenance Execution, and the RELEASE_OVERDUE_TASK parameter in Maintenix is set to WARN, with no hard stop in effect. A red Yes indicates that there are overdue tasks in Maintenix for the aircraft, for which the deadline has passed, the same task has not been completed in Line Maintenance Execution, and the RELEASE_OVERDUE_TASK parameter in Maintenix is set to ERROR, with a hard stop in effect. |
To proceed, you should
package the task into a work package and then complete it. If the
task is already in your work package, you should request a
maintenance operations controller to extend the deadline. When the Overdue Tasks field indicates Yes in red, only authorized users can override a hard stop. |
| Near Due Faults | Near due faults are
faults that have due dates falling within the time interval defined
by the RELEASE_NOTIFY_INTERVAL parameter in Maintenix. A green No indicates that there are no near due faults for the aircraft in Maintenix. A yellow Yes indicates that there are near due faults for the aircraft in Maintenix. |
No impact. Note: You can release an aircraft with near due faults, even when the RELEASE_NEAR_DUE_FAULT parameter in Maintenix is set to ERROR, displaying only a warning. |
| Near Due Tasks | Near due tasks are tasks
that have due dates falling within the time interval defined by the
RELEASE_NOTIFY_INTERVAL parameter in Maintenix. A green No indicates that there are no near due tasks for the aircraft in Maintenix. A yellow Yes indicates that there are near due tasks for the aircraft in Maintenix. |
No impact. Note: You can release an aircraft with near due tasks, even when the RELEASE_NEAR_DUE_TASKS parameter in Maintenix is set to ERROR, displaying only a warning. |
To view a summary of any open, overdue, or near due faults or tasks or missing mandatory components, click Release Status Details.
If there are no indications or warnings preventing the release of the aircraft, you can proceed to record the release by clicking Record Release. On recording the release, you can add release remarks and a release number and then proceed to sign off.
If you are using an assigned YubiKey as part of the sign-off process for aircraft release, you can click Sign on the mobile or web applications and an immutable digital signature is created and stored against the aircraft turn. Note: If you are signing without YubiKey authentication, click Finish to sign off using the alternative sign-off process. This is the point at which a message is sent to Maintenix to complete all tasks in the work package and close all faults that originated from Maintenix, with actual end dates and a task reference with a hyperlink to the Task Details page of the completed tasks in Maintenance Execution. A second message is sent to Maintenix, with the actual start date and actual end date of the work package along with the work package ID to complete the work package in Maintenix. Note that skills, parts, tools, measurements, steps and actions within the task are not sent to Maintenix on work package completion.
Once the turn has been released, you can then view release details by clicking View Release on the Aircraft Turn Details page.
Note: If you are releasing an aircraft and signing off using a digital signature, follow through with recording the digital signature or cancel the procedure before the final step to avoid canceling at the final step and losing all task actions performed.