c/avionics-technicians

Am I the only one who remembers when a comms box swap was a half-day job?

About five years ago at my old hangar in Phoenix, pulling and replacing a standard comms unit was maybe four hours of work with the old wiring harnesses. Last week, I did the same job on a newer regional jet and it took me under ninety minutes from start to sign-off. The difference is those new quick-disconnect, slide-lock connectors they're using now. You don't have to fight with a dozen individual pins and that stiff conduit anymore. Has anyone else had a specific job time get cut in half because of a new part design?

The great coax crimper panic of '19

Five years back, I'd spend 20 minutes hand-twisting and taping BNC connectors on a bench in the hangar, praying they'd hold. Then a senior tech in Anchorage saw me and just tossed me his ratcheting crimper, saying 'Stop wasting your life.' I still keep that old tool in my box as a reminder. What's the one piece of gear that saved you the most time?

Had to pick between a $1200 used Fluke meter or a $400 new generic one for the shop. Went with the generic and it's been fine for 6 months, but I'm waiting for the other shoe to drop.

A trick for chasing down a phantom voltage drop I learned from an old guy at a hangar in Phoenix

I was stuck on a King Air with a weird nav light issue, showing 10.8 volts at the lamp when it should have been 14. I was about to start pulling panels when this retired guy, Frank, who was just hanging around, asked if I'd checked the cannon plug shell. He said, 'Kid, the airframe is the ground path, but corrosion loves to hide where the plug meets the metal.' I cleaned the plug shell mating surface with a scotch-brite pad, and the voltage jumped right up to 13.9. It's saved me hours since. What's your go-to method for finding a bad ground on older airframes?

The week we had to fix a 737's entire EFIS with a 1985 manual

It was maybe 8 years ago at a small shop in Wichita, and our whole digital library went down for three days. We had this old paper manual for the system, and it was full of handwritten notes from techs in the 90s. I mean, it was slow going, but figuring it out with just that book and a multimeter felt like real problem solving. Anyone else miss having to work with just the basics sometimes?

PSA: An old timer told me to always check the cannon plug before chasing a ghost signal

He said it back when I was working on a Citation's nav system in Wichita, and I brushed it off. Last week I spent two hours trying to find a weird glitch in a G1000 display, only to find a bent pin in the main connector. That guy saved me a whole afternoon of pointless work. Anyone else have a simple tip that turned out to be a huge time saver?

Can we talk about the difference in wiring diagrams from the old paper binders to the new digital manuals

I just spent two hours tracing a single wire on a 1998 Cessna 172 using the original paper manual, but the same job on a 2020 model with the digital manual took me 15 minutes because I could just search the part number.

Heads up on those new fiber optic testers from AeroTech

I was sure the 30% faster reading claim was just marketing, but after checking a suspect harness in a G650 last week, it caught a micro-fracture our old unit missed. Anyone else tried them on a tough fault yet?

Warning: a pilot in Tucson insisted I skip the full continuity check on a comms antenna

He said the plane was needed for a short hop and the static was intermittent. I refused and found a corroded connector at the base of the vertical stabilizer that would have failed completely. Has anyone else had to push back against pressure to cut a corner on a seemingly minor squawk?

Serious question, why do we skip digital diagnostics? My last radar job showed they find hidden faults.

Just nailed a pesky wiring fault that had everyone stumped!

It was a tiny break in the shielding that caused intermittent comms failure. Felt awesome to solve it with basic tools and patience!

Debating the detail in our repair logs: Where do you draw the line?

I'm split on our maintenance logging system. One side says full records are key for safety and checks, saying logs have helped spot repeat faults. The other side calls it a time drain, arguing we should focus on fixes, not forms. Like when I logged a simple wire splice that took twice as long to write up as to do. Is this level of detail really needed, or is it just extra work? I'd love to hear where you stand on this.

After a display error, I'm against rushed software patches

Most techs say updates are crucial, but this one caused a real problem. We should wait and test more to avoid new bugs.

Local trend: Aircraft owners delaying other maintenance for ADS-B compliance

At the airfield where I work, we've seen a clear pattern lately. Plane owners are prioritizing ADS-B upgrades over other needed avionics work. I think this is due to the FAA deadlines putting pressure on them. It means our shop is full of these installs, but other issues get pushed back. Just yesterday, a customer brought in a plane with a faulty transponder, but only wanted the ADS-B done. We had to explain the safety risks of ignoring the old problem. This shift is changing how we plan our jobs and talk with clients. I'm curious if other technicians are dealing with similar situations.

Noticed our avionics bench runs cooler with LED task lights.

Switching to LEDs cut our power use and the bulbs last way longer.

After a tricky antenna fix, I'm convinced we rely too much on diagnostic computers.

I mean, idk, maybe it's just me but I've seen this happen a lot lately. Like with that antenna issue, the system said it was fine, but signal was weak. I had to trace the cable and found a crack in the shielding. If we just go by what the computer says, we'd never catch these small things. It feels like we're losing the ability to troubleshoot without a screen. New techs seem to panic when the tools don't give a clear answer, and I worry that makes us less capable in the long run.

A buddy visiting my hangar nearly touched a hot bus bar

He was just curious, but one wrong move could have zapped him or shorted a whole system. I keep visitors behind a marked line now, no exceptions. It's not worth the risk, even for a quick look.