The following article was written by Josh Rauch, Avionics Supervisor at Jungle Aviation and Relay Services (JAARS). It originally appeared in his monthly newsletter, and we are grateful to Josh for allowing us to share his insights here.
There are great deeds done in aviation maintenance that all can see.
Engines roar back to life. Radios crackle across the sky. Fresh avionics glow with the confidence of a sunrise over the panel. Aircraft roll out of the hangar ready for distant lands, and everyone understands that something important has happened.
And then there are the quieter labors.
The ones performed not with rivet guns, torque wrenches, or test flights, but with wiring diagrams, redlines, revision notes, and the slow, deliberate hunt through pages of tiny lines that seem to have been drawn by an electrical wizard during a thunderstorm.
This week in the avionics realm, we have been deep in that work: updating aircraft wiring diagrams.
It is not glamorous.
It is not fast.
It is, at times, the kind of work that makes a person stare into the distance and wonder if the coffee has been cursed by some ancient power to summon sudden-onset narcolepsy.
But it matters.
A wiring diagram is the map of an aircraft’s hidden kingdom. Behind the panels, beneath the floors, through cannon plugs, circuit breakers, relays, switches, antennas, and racks, the aircraft’s electrical system winds its way through places most passengers will never see and most pilots would rather not think about. When those maps are accurate, future troubleshooting becomes possible. Future modifications become safer. Future technicians can follow the trail without wandering into the Mines of “Who Installed This?”, sinking into the Swamps of “How Does This Even Work?”, or facing those dreaded beasts known throughout the hangar lands as “There’s Supposed to Be a Wire Here.”
Every wire has a purpose. Every shield ground has a reason. Every connector pin, circuit protection value, splice, and termination tells part of the aircraft’s story. When the diagram is wrong, incomplete, or outdated, that story becomes harder to read. A technician may still find the answer, but the path becomes longer, darker, and usually involves removing more panels than anyone originally hoped.
Or worse, consulting the ancient wizard of the sparks, who has spent so much time upside down beneath instrument panels that the excess blood flow to his brain has connected every wire, rumor, revision, and repair into one endless tale, where each simple question requires a ten-year journey through aviation history.
For too long, some of aviation’s most valuable technical knowledge has lived in the memory of an aging avionics technician who has smelled too much melted solder, stared too long into the back side of instrument panels, and can somehow remember that “the white wire with the blue stripe goes to the thing behind the thing, unless it was changed during that one project in aught-nine.”
That may work for a season.
It may even feel impressive.
But it is not a system.
Human memory is a noble but unreliable beast, especially hangar memory, seasoned by strange chemicals, ancient potions, and fumes of uncertain origin. It carries wisdom, scars, guesses, legends, and at least three versions of the same story. One day that technician retires, moves on, forgets, or simply looks at the aircraft and says, “I have no idea what was done there, or who might have done it.”
That is why updated wiring diagrams matter.
They take the knowledge out of one person’s head and preserve it in the annals of history through paper records, electronic files, revision logs, and drawings that can be opened by the next technician who inherits the quest. What was once tribal lore becomes usable information. What was once “ask Carman, the old steward of the avionics realm, he probably remembers what was done there” becomes “see drawing E-204, revision C.”
And that, in its own quiet way, is civilization.
In general aviation, the maps are not always easy to find. Some are incomplete. Some are outdated. Some appear to have been lost in the forgotten archives, buried beneath old manuals, faded logbook entries, and the quiet assumption that someone, somewhere, simply knows how the aircraft works.
In other realms of aviation, the recordkeeping is often more disciplined. The base aircraft may have its own Wiring Diagram Manual, telling the story of how it was originally built. Then each individual aircraft carries its own Supplemental Wiring Diagram Manual, a living chronicle of what has been added, changed, removed, repaired, rerouted, or otherwise persuaded into existence.
Most importantly, that chronicle is expected to stay current.
That is the kind of record we are trying to build. Not merely a drawing for today’s installation, and not merely enough information to survive the present quest, but a lasting map for those who will maintain the aircraft long after the original installer has wandered off into the mist, muttering about pinouts, shield grounds, and how “it made perfect sense at the time.”
There is also, hidden behind the ordinary glow of the office monitor, a mystical program known to the elders as Visual CAD.
In its day, Visual CAD served faithfully. Many diagrams were born there, lines and symbols arranged into the secret language of aircraft wiring. But time moves on, kingdoms change, and software that once seemed strong can become a lonely tower on a hill: still standing, still useful, but harder to defend with every passing year.
Access itself becomes part of the problem. When a program can no longer run on modern Windows, the drawings may still exist, but they are locked behind an aging gate. Opening them requires older machines, workarounds, borrowed keys, whispered incantations in languages long forgotten, and the hope that some dusty computer in a corner still remembers the old ways and is not too tired to boot.
So now begins the great translation.
The old files are being carried from Visual CAD into Wiring Planner, a newer and better companion for longevity, revision control, and future maintainability. This is not merely copying lines from one place to another. It is the careful preservation of technical history. It is taking the old maps, cleaning the ink, correcting the borders, and placing them into a system better suited for the long road ahead.
Wiring Planner gives these drawings a better future. Revisions can be managed more cleanly. Changes can be tracked more reliably. Files can live in a format that is easier to maintain, share, update, and protect from becoming digital archaeology.
Because while there is a certain romance in finding an old drawing file and whispering, “I wonder if anything can still open this,” that romance fades quickly when an aircraft is down, a system is not working, and the answer is sealed inside the sarcophagus of software older than most of the technicians.
So we update the maps.
And in the process, something else happens.
The technician doing the revisions is not merely moving lines around on a screen. He is learning the aircraft. He is tracing how power is distributed, how signals move, how boxes talk to other boxes, where grounds are gathered, where protections are installed, and how one system depends on another. To update the diagram correctly, you have to understand what you are looking at. You have to ask why the wire is there, what it serves, what changed, and what would happen if it failed.
That kind of work teaches the system in a way few other tasks can. It turns a drawing from a flat page into a living map. The more carefully it is studied and revised, the better the technician understands not only what was installed, but how the aircraft itself thinks electrically.
We compare what was installed to what was drawn. We verify wire numbers, connector locations, equipment interfaces, circuit breaker assignments, and system changes. We clean up old notes, add missing information, and make sure the next person who opens the drawing does not have to begin their quest by muttering, “Well, that can’t be right.”
This is the kind of work that does not usually get a photograph. Nobody gathers around a newly corrected diagram with misty eyes and says, “Look upon this revision and rejoice.”
But they should.
Because good documentation is a gift to the next technician. It is proof that the installer knew what they were doing when they performed their mystic art. It is a lantern left burning in the tunnel, lighting the way to proper functionality. It is a bridge over a troubleshooting swamp, sparing the next traveler days of wandering around it. It is the difference between “We found it” and “Where does this path actually lead?”
In mission aviation, that matters even more. These aircraft do not simply fly from one convenient airport to another where another ancient conjurer of electrons waits nearby with a meter, a soldering iron, and a half-remembered spell. They serve in places where parts, support, and technical help may be a great journey away. When an aircraft is overseas and something stops working, accurate wiring diagrams can help a technician identify the fault, repair the system, and return the aircraft to service faster.
The work may be boring.
Painfully boring.
Boring in the way only a person who has stared at a wiring diagram so long that all the wires have become one great tangled river of electrons can understand.
But it is also foundational. It is careful stewardship of the aircraft, the people who maintain it, and the mission it supports.
So this week, while no dragon was slain and no sword was reforged, the avionics team continued the noble and necessary work of making sure the aircraft’s hidden maps are true and brought into the light.
Somewhere down the road, perhaps months or years from now, another technician will open one of these drawings, follow the path, find the fault, and quietly say, “Well, that was actually helpful.”
And that, dear reader, is how legends are made.
With coffee.
With patience.
With old files rescued from the digital ruins.
And with wiring diagrams.
