c/avionics-technicians

Pro tip: double check those old wiring diagrams before you start cutting

I used to trust the wiring diagrams in our shop's old manuals without a second thought. Just last month, I was working on a Beechcraft King Air's autopilot system and the manual called for a specific wire gauge and splice point. I prepped everything, but something felt off. I decided to pull up the latest digital service bulletin from the manufacturer's portal, and sure enough, there was a revision from two years ago. The whole routing path had changed to avoid interference with a new radio install. If I had gone with the old book, I would have spent hours fixing a mistake and created a real safety issue. Now, I always cross-reference the physical aircraft log, the digital bulletins, and the manual before I touch a single wire. It adds maybe ten minutes to the job but saves a huge headache. How do you guys make sure you're working with the most current schematics?

Had a chat with a retired A&P at the airport diner yesterday that really got me thinking about how we test gear.

He was telling me about a time in the 90s when his whole shop spent two days trying to find a fault in a nav system. Turns out their test set was out of cal by a tiny bit, just enough to give false readings. He said, 'We were so sure the box was bad, we never thought to question the tester.' It hit different because I just spent a morning chasing a weird voltage drop on a comm radio, and my first thought was the LRU, not my multimeter. Made me realize I almost never send my personal tools out for calibration, just the shop's official stuff. How often do you guys actually check your own meters and testers? Got a schedule or just wait for something to feel off?

Had a weirdly smooth day on a G650 in Dallas after a software patch finally stuck

We'd been fighting with the same nav database update error for a week, but this time the whole system took it clean on the first try. Anyone else have a simple fix feel like a huge win after a string of headaches?

Rant: A bird in San Antonio built a nest entirely from wire strippings from my trash can

Found it last week when I went to toss some old coax, and the whole thing was a perfect, conductive little ball of 22 AWG scraps. Anyone ever had wildlife repurpose their shop waste into real estate?

Had to pick between a new wire tracer and fixing the old one

Last week, our shop's old wire tracer started giving a weak signal on a 737's main harness. The boss gave me a choice: order a new unit for about $800, or let me take a full day to try and fix the old one. I picked the fix, thinking I could save the budget and maybe learn something. Spent six hours opening it up, cleaning every contact, and re-soldering a cracked joint on the main board. It worked, but that was a whole shift gone on one tool. Now I'm not sure if saving the money was worth the time we lost on other jobs. Has anyone else had to make a call like that, where fixing old gear ate up more hours than you planned?

Finally got a stubborn LRU to pass after swapping the test adapter

This 737's flight management computer kept failing the BITE check for three days straight. Swapped out the standard test adapter for a calibrated one from the shop, and it passed instantly. Anyone else run into test gear giving you a false fail?

Had a weird intermittent fault on a G1000 system last month that only showed up above 10,000 feet.

The great torque wrench debate: do you really need to re-calibrate every year?

For five years straight, I just sent our shop's torque wrenches out for calibration on the schedule, no questions asked. Then, during a deep clean, I found the paper log for our Snap-on TechAngle wrench, serial number TA-3471. The last three calibration certs showed it was still within spec, every single time. It got me thinking, are we wasting about $85 per wrench annually on a service that might not be needed? Some guys say the schedule is sacred for a reason, especially with avionics. Others think if it passes a check, you're good. What's your shop's rule on this?

A guy at the Phoenix repair shop made me rethink my whole wire crimp process

I was rushing to finish a nav light harness on a Cessna 172 and he stopped me, pointed at my crimp, and said 'That'll vibrate loose before the next oil change.' He showed me his method of twisting the strands first, which I'd always skipped. How many of you do that extra step on every single crimp?

A bad day at Oshkosh made me rethink my whole approach to pre-flight checks

I was working static display support at AirVenture last year, and a pilot reported a weird intermittent comms failure on his panel. We traced it for two hours, checking every connection and module. Turned out a tiny piece of foil from a gum wrapper had fallen behind the audio panel and was shorting a pin. The pilot admitted he'd been snacking while doing his own checks. Now I visually inspect the entire cockpit floor and seat tracks for foreign objects before I even touch a multimeter. It adds maybe 90 seconds, but it has saved me from three wild goose chases since. How many of you have a specific FOD check step in your routine?

Am I the only one who had a 737's entire IFE system go dark right before pushback?

Just had this happen yesterday on a quick turn in Denver. The plane was loaded, doors closed, and the whole inflight entertainment screen array just died. No power, no status lights, nothing. The captain was already asking for the release. I had to jump into the E&E bay with a flashlight and my multimeter, sweating bullets. Traced it back to a single loose cannon plug on the main media server rack, connector C204. It must have vibrated loose on the inbound flight. Got it seated, powered up, and did a full reboot with the passengers staring at me from the jet bridge. Took 25 minutes and we went out late. How often do you guys see these big connectors work themselves free? Any trick to keep them locked besides the usual push and click?

Pro tip: keep a spare set of those tiny fiber optic cleaning tools in your kit

Last month, I was doing a pitot-static system check on a Citation in Dallas and dropped the only fiber optic connector cleaner I had. It rolled right into a drain. I was stuck for an hour waiting for the shop to open so I could buy another one. The job was a simple transceiver check, but that one missing tool killed my whole morning. Now I keep two of those little stick cleaners in a separate pocket. Has anyone else had a tiny tool cause a big delay like that?

Update: My logbook hit 1,000 autopilot system checks this morning.

One side says it's just a number, but the other side feels like a real mark of trust in keeping those systems safe, so what's a milestone that actually meant something to you guys?

Shoutout to the guy at the Phoenix MRO who helped me trace that intermittent fault

Spent two full days chasing a ghost in a G1000 autopilot, and he walked over with a different brand of breakout box that finally showed the glitch. Anyone have a go-to method for those random voltage drops?

Warning: That cheap fiber optic inspection scope from the online auction site cost me a whole day

I grabbed a used one for about $150 thinking it was a steal compared to the $2000+ units. The image was so fuzzy I couldn't tell a good connector from a scratched one. Ended up second-guessing myself on a perfectly good LRU, pulling it for no reason, and wasting hours. Had to borrow a proper scope from the hangar next door to finish the job. Anyone have a go-to brand for these that won't break the bank but actually works?

My hangar chief said I was crazy for using a heat gun on a stubborn connector

We had a 737's main radio connector that wouldn't budge after a salt spray cycle, and everyone said to just keep pulling. I gently warmed the housing for about 30 seconds on low, and it came right off without a single pin damaged. Has anyone else had to go against the book for a stuck component?

Showerthought: The new Collins Pro Line 21 trainer at our hangar in Phoenix has a comms issue that makes no sense.

It passed all the bench checks, but the second we put it back in the bird, the transmit audio cuts out above 10,000 feet. We've swapped the rack, the tray, and even the antenna coupler. Has anyone in a hot/dry climate run into something like this with a pressure-sensitive fault?

My old boss in Tampa told me to always trust the built-in test on the Garmin G1000

He said if the BIT passed, the box was good, no matter what the plane's logs said. I followed that for years until a King Air came in with a weird autopilot fault. The BIT was green, but a deeper check showed a bad roll servo channel. That advice cost us two days of downtime. How do you guys decide when to trust the built-in tests versus digging deeper?

I was sure my wire routing method was fine until a new guy pointed out the flaw

For months, I was bundling all the sensor wires for a nav system upgrade in one big loom, thinking it was neat. A tech who used to work on F-16s watched me for a minute and said, 'You're putting all your noise sources in one happy family.' He showed me how separating the power and signal lines by just a few inches on the tray cut the static by half on the bench test. Has anyone else had a simple routing fix solve a big interference headache?

A talk with a pilot at the Anchorage FBO made me check my assumptions

I was finishing up a G1000 software load on a Caravan, and the pilot asked me a simple question about the terrain database date. I gave my usual 'it's current' answer, but he pressed, saying he'd seen a new ridge line added on a chart that wasn't on his display last month. It hit different because he wasn't doubting my work, he was genuinely trying to connect the dots between our updates and his real world flying. Made me start double-checking the actual database version notes against the latest chart supplements before I sign off now. Anyone else had a user question that made you change a small part of your routine?

Warning: an old timer in Denver told me my wiring bundles were a mess

Honestly, I was working on a King Air 200 about six years ago, installing a new GPS unit. I thought my work was clean because everything was secure. This retired guy, who used to run a shop at Centennial Airport, came by to chat. He looked at my bundle and just said, 'Kid, you're making the next guy's fault isolation a nightmare.' He pointed out how I had power, data, and antenna lines all twisted together, no real separation. I argued it was fine, but he showed me his old manual where they color-coded ties for different systems. I changed my whole approach after that. Now I use different colored zip ties for different signal types and leave way more service loop. Has anyone else had a simple tip like that totally change their daily routine?

Shoutout to the inspector who called out my wire routing

He said my bundle looked neat but was too close to a hydraulic line, a real heat risk. I started leaving a full inch of clearance after that, which feels like a lot more space. Anyone else have a simple rule they follow for separation now?

Heard a pilot call a transponder a 'magic box that makes the plane show up'

I was grabbing coffee at the FBO in Tampa and overheard a new first officer ask the captain what the transponder actually does. The captain just said 'it's the magic box that makes the plane show up on the screen, don't worry about it.' I almost spit out my coffee lol. It made me think we should do a better job explaining our work to the flight crews in simple terms. Has anyone else had to give a really basic 'what does this black box do' talk?

Honestly, a pilot told me my comms checks were too fast and it made me rethink my whole process

This was on a King Air 350 last month. I was doing my usual quick 'radio check, one two three' and the captain stopped me. He said, 'Slow down. I need to hear each number clearly, not just a blur.' I realized I was just going through the motions to get it done. Now I pause a full second between each number and enunciate. It feels weirdly slow, but he was right. How do you guys handle comms checks on different aircraft? Do you adjust your pace?

A retired inspector told me my wire routing was 'too neat' for its own good.

I was showing off a panel I finished on a Citation XLS, and he pointed out that my tight, perfect bundles could actually cause heat spots and stress fractures over time. He said, 'Kid, you're building a plane, not a museum piece, leave some slack for vibration.' Has anyone else had a boss or inspector push back on work that looked too clean?