Note: The above image is a real image from the MO Handover Suite Solution Software proposed and offered by Aviathrust.
Quick answer
Aircraft maintenance shift handover software is a digital tool that captures, records and preserves the information passed between outgoing and incoming maintenance personnel at every shift or task changeover. It exists because broken handovers cost lives: when work status is not communicated at shift change, aircraft have been released to service in an unairworthy condition. EASA Part-145 makes adequate handover a legal requirement under point 145.A.47(c), and your Maintenance Organisation Exposition (MOE) must document how you do it. The Aviathrust MO Suite delivers this as a cost-effective, deployment-ready handover log — designed by an aircraft engineer, for aircraft engineers — that small and medium MROs can adopt with minimal training.
Key takeaways
- A failed shift handover was central to the fatal crash of Continental Express Flight 2574 in 1991, which killed all 14 people on board.
- The FAA attributes roughly 80% of maintenance errors to human factors; “lack of communication” tops the industry’s “Dirty Dozen.”
- EASA Part-145 point 145.A.47(c) requires that information be “adequately communicated between outgoing and incoming personnel.”
- Your MOE must document handover aims, training, recording, the formal process and the responsible person (EASA MOE User Guide §2.26).
- Aviathrust MO Suite turns handover from fragile verbal memory into a permanent, searchable, exportable record.
When a Shift Handover Fails: The Continental Express Flight 2574 Disaster
On 11 September 1991, an Embraer EMB-120 Brasilia (registration N33701) broke up in flight near Eagle Lake, Texas. All 14 people on board died. The cause traced directly back to the hangar floor the night before.
During scheduled overnight maintenance, second-shift mechanics removed the 47 screws securing the upper surface of the left horizontal stabiliser’s de-ice boot leading edge. The work was not finished. At shift change, the second-shift supervisor did not solicit verbal end-of-shift reports from his mechanics and did not complete the required turnover documentation. The incoming third shift — and the inspectors — were never told the screws were missing. The aircraft was signed off and returned to service with the leading edge held by its lower fasteners only. In flight, it failed.
The US National Transportation Safety Board (NTSB) determined the probable cause was the failure of maintenance and inspection personnel to follow proper maintenance and quality-assurance procedures, with contributing failures by company management and FAA surveillance. Strip away the technical language and the lesson is brutally simple: information that lived in one tired person’s head at three in the morning never reached the people who needed it. A handover failed, and an aircraft fell out of the sky.
A Pattern, Not an Exception: British Airways Flight 5390
Continental Express 2574 is the textbook case, but it is not alone. On 10 June 1990, the left windscreen of British Airways Flight 5390 blew out at around 17,300 feet, partially ejecting the captain from the aircraft; cabin crew physically held onto him until the first officer landed safely.
The Air Accidents Investigation Branch (AAIB) found the windscreen had been replaced about 27 hours earlier using 84 bolts that were fractionally too small in diameter. A shift maintenance manager had fitted them on a like-for-like basis during a night shift, working alone, in poor light, without referring to the maintenance documentation and without independent verification of the critical task. Different aircraft, different failure — but the same DNA: a solo decision, made under time and fatigue pressure, that no formal process or second pair of eyes ever caught.
Why Handover, Communication and Coordination Decide Safety
Maintenance is the one place in aviation where a quiet, undramatic error can sit dormant for hours or days before it bites. The numbers explain why this matters so much:
- The FAA estimates that around 80% of maintenance errors involve human factors.
- Boeing has estimated that human error is a primary factor in more than 70% of commercial hull-loss accidents.
- In Gordon Dupont’s “Dirty Dozen” — the twelve most common human-factor causes of maintenance error — lack of communication sits at number one.
Shift and task handover is communication at its most fragile. Studies of verbal communication suggest as little as 30% of a spoken message is reliably received and understood. Now add a twelve-hour shift, fatigue, a noisy hangar, and a colleague who is mentally already on the drive home, and the gap between “what I meant” and “what you heard” becomes a safety hazard.
EASA’s own guidance frames effective handover around three elements: the outgoing person’s ability to communicate the important parts of the job, the incoming person’s ability to understand and assimilate them, and a formalised process — with a planned shift overlap and a place for the exchange to happen. Miss any one of the three and the chain breaks. Coordination across shifts, teams and even external working parties is not administrative overhead; it is the mechanism that stops half-finished work from being mistaken for finished work.
What EASA Part-145 Requires for Shift and Task Handover
Handover is not merely good practice — for an EASA-approved maintenance organisation it is a regulatory obligation. Point 145.A.47(c) of Annex II (Part-145) states:
“When it is required to hand over the continuation or completion of maintenance tasks for reasons of a shift or personnel changeover, relevant information shall be adequately communicated between outgoing and incoming personnel.”
The associated guidance, AMC 145.A.47(c), expands the primary objective — effective communication at the point of handover — into the three basic elements above: the outgoing person communicating clearly, the incoming person assimilating the information, and a formalised process with a planned shift overlap and a dedicated place for the exchange.
Handover does not sit in isolation. The same rule, 145.A.47(b), requires organisations to account for human performance limitations — including the threat of fatigue — when planning tasks and organising shifts, precisely the conditions under which handovers fail. And 145.A.48 (Performance of maintenance) requires an error-capturing method after any critical task and steps to minimise the risk of repeated errors. Robust handover is the connective tissue that ties planning, fatigue management and error capture together.
What Your MOE Must Document: Shift / Task Handover Procedures
Regulation sets the obligation; your Maintenance Organisation Exposition (MOE) has to show how you meet it. EASA’s MOE User Guide addresses this in section 2.26, “Shift / Task Handover Procedures” (referencing 145.A.47(c) and AMC 145.A.47(c)). A compliant procedure is expected to cover:
- The aims and objectives of the shift handover.
- Training of personnel in shift/task handover processes.
- Recording of the shift/task handover.
- A formalised shift handover process and the required information — including facility status, work status, manning status, outstanding issues, and any other relevant information.
- The person responsible for managing and completing the shift/task handover.
Two of those points — recording the handover, and a formalised process for the required information — are exactly where paper logbooks and informal verbal briefings let organisations down. A scribbled note can be illegible, lost, or never written at all. This is the gap that purpose-built software closes.
The Solution: Aviathrust MO Suite Handover Software
The Aviathrust MO Suite is a continuing-airworthiness and maintenance-management platform built around exactly this problem. Its Ground Handover Log replaces the fragile verbal-plus-paper handover with a structured digital record. For each handover, an engineer records the work order, jobcard and aircraft registration, then captures the handover itself in a rich-text entry that can include formatting, tables and images — enough to describe facility status, work status, outstanding issues and anything the next shift must know. Every entry is automatically stamped with its author and date and time, so there is never a question of who handed over what, or when.
Because the handover lives in a database rather than a folder, the entire history is instantly searchable and filterable by work order, jobcard, registration or date range. Any handover can be exported to a clean PDF with one click — ready for an audit file, a customer pack, or an investigation. Access is controlled: only authorised, approved users reach each module, and the system applies secure sessions with an automatic inactivity timeout suited to shared hangar terminals.
Handover is the lead module, but it sits inside a wider suite the same MRO can grow into: non-routine defect cards (with an aircraft register, work orders and stepped rectification records), deferred-defect / MEL management with automatic rectification-deadline tracking, and a controlled-document library with mandatory-read tracking and a compliance report showing who has read what. Across the suite, change logging records create, update and delete actions — who, when, and before versus after.
Built for Small and Medium Size MROs — By an Engineer, For Engineers
Most maintenance-management platforms are priced and built for large operators, with implementation projects and training budgets to match. The Aviathrust MO Suite takes the opposite approach. It is a cost-effective, deployment-ready solution aimed squarely at small and medium-sized maintenance organisations that need Part-145-aligned discipline without enterprise complexity or cost.
It was designed by a working aircraft engineer for aircraft engineers, so the workflows mirror how a hangar actually operates — which means minimal training to get a team productive. The interface is intuitive by intent: if you have run a shift, you already understand the handover log. There is no heavyweight rollout, no army of consultants, and no steep learning curve standing between your organisation and a defensible, auditable handover process.
How Aviathrust MO Suite Maps to Part-145 Handover Requirements
| EASA Part-145 / MOE §2.26 requirement | How Aviathrust MO Suite delivers |
|---|---|
| 145.A.47(c): adequate communication between outgoing and incoming personnel | A structured digital handover entry tied to work order, jobcard and aircraft registration |
| Recording of the shift/task handover | Every handover stored in a database with automatic author and timestamp |
| Formalised process and required information (work/facility status, outstanding issues) | Rich-text handover capturing status, outstanding issues, images and tables |
| Responsible person identified | Author captured automatically; access restricted to approved, authorised users |
| Evidence for audits and investigations | One-click PDF export plus a searchable, filterable handover history |
| Wider compliance (defects, MEL, documents) | Integrated NRC, deferred-defect/MEL and controlled-document modules with change logging |
Book a Demo of Aviathrust MO Suite
If your organisation still relies on verbal briefings and paper logbooks for shift and task handover, you are carrying a risk that regulators — and accident investigators — take very seriously. See how a purpose-built handover log closes that gap.
Contact Ing. George Spiteri for a demonstration and further details:
Email: george.spiteri@aviathrust.com
Ask for a walkthrough tailored to your maintenance organisation’s size and scope.
