Photo Info

Focus on maintenance: Learning from mistakes

By John Carinha | August 12, 2026

Estimated reading time 4 minutes, 45 seconds.

Oftentimes, the average work day can be mundane — especially if one is working on a long-term project where work spans weeks and months. Lately, our shop has been seeing a steady flow of these types of projects, and an uptick in the number of short-term jobs. These usually last no more than a week and involve a faster approach to the planning and execution. When you’re rolling several of these, no amount of policy is going to capture every last detail. Every so often, the shoe falls — and you regroup, learn and move on.

Much of what we do in avionics is based on data of some sort. Whether approved, acceptable or specified, at some level the design integration of systems involves one or more of these data types. This usually culminates in a formal schematical drawing drafted on some form of computer-aided design software. As this involves a high level of focus and consideration, it can get mentally “busy” to process all the ins and outs of a system design. And, as a result, a multi-level revision process usually plays out during the length of the project.

As some systems repeat from project to project, often subtle changes are done to pre-existing drawings. This would involve cutting and pasting portions of one drawing into another in order to save time. Sometimes, one aircraft will have the same GPS navigator interfaced to a different transponder or audio panel. As a result, one would retain the specifics of the GPS navigator drawing and cut out that of the system(s) to which it interfaces. Often, all it takes is a couple of mouse clicks — but the engineer can easily create a miscue in the design if they are not careful. The consequence to this type of oversight is sometimes not detectable until the job is near completion — and typically only during the system checkout phase.

On a recent project, we were asked to provide a wire harness and drawing to a client for a used radio altimeter system they recently acquired. They had experienced and trained staff but not the capabilities to produce the parts and wiring. Late one afternoon, a call came in expressing frustration with the equipment — they were getting errors during the calibration procedure. I reviewed the two fault codes and could not make sense of their connection or resolution. I contacted the equipment OEM, and based on the codes, they concluded that it was a hardware issue and that the units should be returned to them for repair. This was very much a setback in both time and cost. In the hustle of managing multiple projects, it also seemed like the fastest resolve to a problem (we would soon find out) was self-inflicted.

Upon producing the OEM manuals for the system in question, and cross-checking them against the drawing provided, it was found that a two-wire data wire was connected to the wrong contact locations at the radio altimeter indicator. All other connections were correct except these two. Upon confirming the correct unit part numbers and pinouts, the wiring was configured to what it should have been to begin with, and the calibration procedure was conducted and deemed successful.

To say I was a little red-faced would be an understatement. We never aim to make mistakes, and we also know we are not flawless. In the end, a lesson was learned, and the important thing is how one responds to this type of challenging situation. The client had been loyal to us for many years and understood the oversight. Everyone moved forward that much more knowledgeable and equally cautious.

Being reactive to this situation wasn’t a choice — it is what brought about a solution. Being proactive moving forward, one hopes, will prevent this sort of error from happening again, and allow us to stay ahead of any future problems or issues.

Leave a comment

Your email address will not be published. Required fields are marked *

ASU’s Dan Meyer on the latest in night vision goggles

Notice a spelling mistake or typo?

Click on the button below to send an email to our team and we will get to it as soon as possible.

Report an error or typo

Have a story idea you would like to suggest?

Click on the button below to send an email to our team and we will get to it as soon as possible.

Suggest a story