Aircraft Maintenance Shift Handover: What Engineers Must Communicate

A maintenance shift handover is a safety-critical transfer of information. It ensures that the incoming team understands the aircraft’s technical status, the work completed and the tasks that remain outstanding.

A good handover prevents duplicated work, missed defects, unsafe configuration changes and incorrect assumptions about certification or release status. It also gives the incoming engineer a clear starting point for the next shift.

In the UK and Europe, a handover is not simply a local working preference. UK and EASA Part-145 organisations must have an effective process for communicating relevant information when maintenance tasks and shifts are handed over. The detailed procedure must be defined in the organisation’s Maintenance Organisation Exposition, or MOE.

Engineers must therefore follow the approved handover process used by their employer, whether it is paper-based, electronic or a controlled combination of both.

What a Maintenance Handover Must Achieve

A good handover allows the incoming engineer to answer five questions immediately:

• Which aircraft, component or work package is involved?
• What work has been completed?
• What remains open?
• What risks, limitations or precautions apply?
• What must happen next, and who is responsible?

The purpose is not to repeat every entry in the aircraft records. It is to provide a clear and attributable summary, supported by the relevant work cards, technical records and approved maintenance data.

A handover is incomplete if the incoming shift has to reconstruct the aircraft’s status from disconnected notes, verbal comments or assumptions. The principles of effective shift communication are also discussed in SKYbrary’s guidance on shift handovers.

1. Identify the Aircraft and Work Package

The handover should begin with an unambiguous identification of the work. Depending on the organisation’s procedure, this normally includes:

• Aircraft registration and, where required, aircraft type or MSN
• Component part number and serial number, if applicable
• Work order, package or task-card reference
• Hangar, stand, bay or work area
• Check or maintenance input being performed
• Current aircraft configuration relevant to the work
• Customer or operator instructions affecting the task

This prevents information being attributed to the wrong aircraft or work package, particularly where several aircraft of the same type are undergoing similar maintenance.

2. State Exactly What Has Been Completed

The outgoing engineer must distinguish between work that is fully complete and work that is only partially progressed.

The handover should identify:

• Maintenance tasks completed
• Inspections completed and their results
• Fault-finding already carried out
• Components removed, installed, tested or routed for repair
• Work cards or task steps signed by authorised personnel
• Independent inspections completed, where required
• Functional or operational tests performed
• Technical data used, including the applicable revision
• Findings that have been rectified and properly recorded

Work in progress is not sufficient as a description. The incoming shift needs to know the precise task step reached and whether the work is awaiting inspection, testing, parts, engineering advice or certification.

If a task is signed as complete, the records must support that status. If it is not complete, it must remain clearly open. Where an independent inspection is required, the handover should identify whether it has been completed and record the relevant sign-off. For more detail, read who can perform an independent inspection in aircraft maintenance.

3. List All Outstanding Work

Open items are the central part of a shift handover. They should be recorded individually rather than summarised as several defects remain.

For each outstanding item, communicate:

• The defect, task or inspection still open
• Its exact location or system reference
• The work already performed
• The next required action
• Applicable maintenance data or work instruction
• Any required inspection or authorisation
• Parts, tooling or equipment still needed
• Whether engineering, planning, quality or the operator must be consulted
• Any deadline, operational requirement or agreed priority

The incoming engineer should not have to infer whether an item is awaiting parts, awaiting a decision or simply forgotten.

Where a defect has been deferred, the handover must identify the approved deferral reference and any associated limitations, placards, inspections or expiry conditions. A deferred defect must not be presented as an ordinary outstanding task without its operational controls. Engineers should also understand how the operator’s MEL process affects defect control. See our guide to deferring aircraft defects using the MEL.

4. Communicate Defects and Abnormal Findings

Defects raised during the shift must be transferred accurately, including findings that appear minor or unrelated to the original task.

The handover should cover:

• Newly discovered defects
• Repetitive or recurring defects
• Unusual findings
• Evidence of damage, contamination, corrosion, overheating or fluid leakage
• Fault messages or maintenance-message history
• Troubleshooting results
• Defects closed during the shift
• Defects requiring further monitoring or engineering assessment

The description should be factual and traceable. For example, oil found in area is less useful than a recorded location, approximate quantity, condition, inspection performed and action taken.

If a defect has been closed, the handover should make clear how it was rectified and where the supporting record can be found. If it remains open, the reason and next action must be visible. Accurate fault history is particularly important when dealing with intermittent electrical or avionics faults. Related guidance is available in how to troubleshoot intermittent aircraft electrical faults.

5. Identify Parts, Materials and Tooling Issues

Parts availability can determine whether an aircraft is released on time. The incoming shift must know what has been fitted, removed, quarantined or ordered.

Relevant information includes:

• Parts installed and their traceability references
• Components removed and their storage or quarantine status
• Parts awaiting delivery
• Unserviceable or suspect components
• Consumables used or still required
• Shelf-life or batch-control concerns
• Tools or test equipment left connected or required
• Special tooling that has been reserved, transferred or returned
• Calibration or serviceability issues affecting equipment

A component must not be treated as available merely because it is physically present. Its paperwork, release documentation, status and compatibility must also be confirmed in accordance with the organisation’s procedures.

Where a component release document is relevant, the engineer should record the document reference and status clearly. Our guide to EASA Form 1 and CAA Form 1 requirements after Brexit explains the wider control considerations for UK organisations.

6. Highlight Safety and Configuration Controls

The handover must clearly identify anything that could create a hazard or cause damage if the next shift proceeds incorrectly.

This may include:

• Aircraft jacked, grounded or otherwise placed in a special condition
• Landing-gear safety pins or safety devices installed
• Access panels, cowlings or flight controls removed
• Electrical, hydraulic, pneumatic or fuel systems isolated
• Circuit breakers pulled or tagged
• Components supported, restrained or temporarily protected
• FOD-sensitive areas left open
• Fuel, oxygen or other hazardous materials involved
• Temporary blanks, covers or plugs installed
• Open panels or incomplete reassembly
• Special precautions for energising or testing a system

The outgoing engineer should explain both the physical condition of the aircraft and the controls recorded in the technical documentation. A verbal warning alone is not an adequate substitute for the required tag, work-card entry or isolation record.

Configuration status is especially important when panels, flight controls, landing gear systems or engine components have been disturbed. The incoming engineer should inspect the aircraft where necessary rather than relying solely on the written summary.

7. Confirm Maintenance Data and Engineering Instructions

Work must continue against current and approved maintenance data. The handover should therefore identify the reference being used and any technical decision affecting the next action.

This may include:

• Aircraft Maintenance Manual task references
• Structural repair or component maintenance instructions
• Service bulletins or approved modification data
• Engineering orders or technical instructions
• Approved repair data
• Non-routine task references
• Configuration or applicability information
• Engineering concessions or approved deviations
• Responses received from technical services or the operator

If the work has exposed a condition outside the published limits, the handover must state that an engineering disposition is required. Engineers should not pass on an assumption that a repair is acceptable when approval has not yet been obtained.

For a useful overview of the documents engineers may need during a handover, see Aircraft Maintenance Manuals Explained: AMM, IPC, SRM and Wiring Diagrams.

The EASA Easy Access Rules for Continuing Airworthiness provide the current European regulatory framework and associated guidance. UK organisations should also check the UK CAA Part-145 information and applicable requirements.

8. State the Certification and Release Status

One of the most important handover points is whether the work is certified, partially certified or awaiting certification.

The outgoing shift should identify:

• Tasks signed as complete
• Tasks awaiting inspection
• Tasks awaiting independent inspection
• Tasks awaiting functional testing
• Tasks awaiting authorised certification
• Any incomplete or incorrectly completed records
• Whether a Certificate of Release to Service can be issued
• Whether the aircraft or component remains unserviceable
• Any records still required before release

A handover must never imply that an aircraft is ready for return to service simply because the physical work appears complete. The technical records, required inspections and certification must also be complete.

Under the Part-145 framework, the release status is supported by the maintenance records and the applicable Certificate of Release to Service process. The incoming shift must be able to see what has and has not been certified. The organisation’s authorisation system must determine who may certify the work, not an informal assumption made during the handover.

9. Record the Handover Properly

The handover itself must be attributable and traceable. At a minimum, the organisation’s process should establish:

• Name or unique identity of the outgoing engineer
• Name or unique identity of the incoming engineer
• Date and time of handover
• Aircraft or work-package reference
• Summary of completed and outstanding work
• Safety-critical precautions
• Actions assigned to the incoming shift
• Confirmation that the information was received and understood

Where a face-to-face briefing takes place, it should be supported by the controlled record. Where a digital system is used, the entry should be time-stamped and protected against unauthorised alteration.

A maintenance handover system is useful only if it creates a reliable record of the transfer. It should not become a separate unofficial log that conflicts with the organisation’s work cards or MOE.

Paper, Digital and Verbal Handover Systems

A handover may use:

• Controlled paper forms
• Aircraft technical log entries
• Task cards and non-routine cards
• Electronic maintenance records
• Shift-handover software
• A structured verbal briefing supported by written or electronic records

The format is less important than control and consistency. A digital system should reflect the approved procedure rather than create a parallel process.

This is significant under 145.A.70, which requires the organisation to maintain an MOE describing its procedures. If the MOE describes one handover process but the software requires engineers to work around it, the organisation creates a compliance and safety risk.

Electronic records should include safeguards against unauthorised alteration, maintain a clear audit trail and support secure backup and retrieval. They should also allow an auditor to trace the handover back to the relevant work card, parts records, inspection entries and certification.

Handover Records and Audit Evidence

Part-145 record keeping is broader than retaining a final signature. The evidence should show an unbroken chain covering:

• The original work instruction
• Work completed and recorded
• Parts and materials used
• Required inspections
• Test results
• Defects and rectification
• Engineer and inspector identification
• Certificate of Release to Service, where applicable
• Handover information supporting continuation of the work

Point 145.A.55 establishes maintenance-record requirements, including protection and retention of records. The exact retention period must follow the current applicable regulation, the organisation’s approved procedures and any contract or continuing-airworthiness requirement. Engineers should rely on the current MOE and compliance guidance rather than an informal assumption about retention periods.

Records must be safely stored and retrievable. Computer backups, access controls and protection against unauthorised changes are part of the record system, not optional administrative features.

The organisation’s independent compliance-monitoring function may audit the handover process under the quality and safety arrangements required by Part-145, including the independence principles associated with 145.A.65(c). The people performing the maintenance should not be the only people deciding whether the handover records are complete and compliant.

Keep your maintenance experience and supporting records organised with Part 66 Logbook Analysis. Start your demo now and review your records with greater confidence.

The Incoming Engineer’s Responsibility

A handover is a two-way process. The incoming engineer must actively verify the information rather than accepting it passively.

The incoming shift should:

• Review the written or electronic handover.
• Inspect the aircraft or component where necessary.
• Confirm the status of open tasks and safety controls.
• Check the relevant work cards and maintenance data.
• Clarify ambiguous or conflicting information.
• Repeat back safety-critical instructions.
• Record any corrections or newly identified conditions.
• Accept responsibility only for work that is understood and properly transferred.

If the incoming engineer cannot determine the aircraft’s status, the handover has not been completed effectively. Work should pause until the uncertainty is resolved through the appropriate supervisor, planning, engineering or quality route.

A Practical Shift Handover Checklist

Before ending the shift, the outgoing engineer should confirm:

• Aircraft, component and work-package identity are correct.
• Completed work is clearly separated from incomplete work.
• All open defects and non-routine tasks are listed.
• Deferred defects and operational limitations are identified.
• Required parts, tools and test equipment are stated.
• Aircraft isolations, safety devices and temporary configurations are recorded.
• Current maintenance data and engineering instructions are referenced.
• Inspections, tests and certification still required are identified.
• The aircraft’s release or unserviceable status is clear.
• The incoming engineer has received and understood the information.
• The handover record is time-stamped, attributable and stored through the approved system.

The Essential Principle

A maintenance shift handover must communicate the aircraft’s actual status, not merely the work completed during one engineer’s shift.

Under UK and EASA Part-145, the organisation’s MOE defines how that information is transferred and recorded. Point 145.A.47(c) makes the communication requirement explicit, while the maintenance-record, quality-system and exposition requirements ensure that the process remains traceable and auditable.

The safest handover is precise, current and supported by records. It tells the next engineer what has happened, what remains, what could cause harm and what must be done before the aircraft or component can be released.

For more practical guidance on aircraft maintenance careers, licensing and compliance, visit the AeroTech Careers Blog.