Paper does not control the process

Most maintenance and continuing airworthiness management organisations in Poland have well-written procedures and people who know them. Even so, audits keep turning up the same things: a signature without a date, an open task in a closed work order, an AD deadline that passed in a spreadsheet nobody opened that day. Not because someone was at fault. Because paper does not control the process.

Procedures can be sound and staff properly trained. The problem starts when the course of the process depends solely on a manual record. Paper records what has been written. It does not check the order of actions, the completeness of the data or whether the conditions for moving on to the next stage have been met.

Yet that is exactly what the regulations require. Part-145 obliges an organisation to keep maintenance records detailed enough to establish what was done, by whom and on the basis of which data. Part-M requires the continuing airworthiness manager to keep a record system that shows the current status of the aircraft at any time. Neither regulation says the record has to be on paper. Both assume it is complete and reliable. Below are six places where paper does not guarantee that.

Release to service before all tasks are closed

In a traditional document flow, checking completeness depends on a person. An open task, a missing required confirmation or an incomplete entry may only be noticed during a later review of the records.

Yet a certificate of release to service (CRS) may only be issued once all the ordered maintenance has been properly carried out. On paper, nothing stands between the signature on the release and a task left open on another card. A digital system can track the status of the work as it happens and keep the process from closing until the required tasks have been carried out and properly documented.

The same mechanism works one level down: on a single signature.

A signature without the context of the work

A signature confirms a person's responsibility, but paper does not automatically record when, where and at which stage of the process it was made.

When records are filled in after the fact, it is hard to reconstruct the actual sequence of the work with certainty. A signature made at the aircraft and one made on Friday for the whole week look identical on the card. A digital audit trail links each record to a specific user, action and moment of execution.

Even if every signature is in place, the data it confirms rarely stays in one place.

The same data in several places

The mechanic records the work carried out. The data then goes into the technical records, the airworthiness management system, a spreadsheet or a report.

Every manual transcription increases the risk of discrepancies, omissions or errors. The more independent data sources there are, the harder it is to say which of them is current and authoritative.

The most common of these places is the spreadsheet.

A spreadsheet instead of a controlled process

Excel is an excellent calculation tool, but on its own it does not give you control over the airworthiness management process.

As the fleet grows, so does the number of deadlines, limitations, ADs, SBs, components, flight hours and the dependencies between them. Formulas, manually entered data and successive versions of the file all need constant checking.

The problem is not the spreadsheet itself. The problem is a situation in which an operational decision depends on a single cell, and the system does not automatically verify its source, whether it is up to date or how it affects the status of the aircraft. The regulations require the status of ADs, limitations and life-limited parts to be current in the records. The spreadsheet does not know whether it is.

The spreadsheet fails quietly. The journey log fails late.

Defect information arrives too late

A paper journey log passes information on only once someone reads it and forwards it.

If reporting a defect takes an extra phone call, a message or retyping the data, an information gap opens between finding the defect and the organisation's response. In the meantime, the next pilot may climb into the same aircraft.

In aviation, information about technical condition should reach the right people when it arises, not when the paperwork reaches the office.

All of these gaps have one thing in common: none of them is visible until someone asks. The auditor asks.

Compliance has to be not only ensured, but demonstrated

During an audit, it is not enough for a procedure or a form to exist. The organisation has to be able to show that the process was carried out in line with the requirements and remained under control.

With scattered documents, reconstructing the history means piecing together work cards, registers, spreadsheets, messages and signatures. Every such reconstruction recalls from memory what should have been recorded at the moment it happened.

What the system has to do

A well-designed system should leave a consistent audit trail of the process: from reporting and planning, through execution and verification, to closure and archiving.

It does not add procedures or change the way people work. Procedures live in the regulations and the manuals. They are what tell you how to work. The system does one thing: it makes the record come into being at the moment of execution, not after it, and it keeps the process from closing until it is complete.

That is how we designed Aeronite: from a defect reported in the journey log, through the work order and the work card in the hangar, to the release to service returning to the continuing airworthiness manager. If you want to see what that trail looks like in practice, sign up for early access.