I watched a new guy spend 15 minutes today cranking each one down with a torque wrench to 30 inch-pounds, and I had to pull him aside and show him the service manual says 8-10 is plenty. Has anyone else seen this over-torque thing turn a simple panel removal into a stripped screw disaster?
I dropped $200 on a used Fluke cable tester off eBay and figured it was a waste until I hit a weird intermittent issue on a King Air 200. The autopilot was dropping out randomly but everything checked out visually and with the multimeter. Ran the cable through the tester and found a cracked pin inside a D-sub connector that was only making contact when the plane vibrated a certain way. Ended up saving me probably 10 hours of head scratching and the old mechanic I was working with finally stopped giving me crap about buying 'fancy toys.' Anyone else run into hidden wiring faults that basic tools just don't catch?
Was showing a kid how to pin out a harness for a G1000 retrofit and he said that after watching me fight a bad backshell for 20 minutes. Has anyone else dealt with trainees who think the troubleshooting is already done before they touch a wire?
I was helping a younger tech at the hangar in Wichita last Tuesday, and he kept fighting with a terminal strip on a 172. The newer Molex pins just slide out if you don't pinch them at a specific angle, and nobody writes that in the manual. I had to show him the old trick of twisting the wire a quarter turn before seating it. Has anyone else noticed the newer connectors are way less forgiving than the 1990s stuff?
I was struggling with a weird intermittent fault on a Garmin G1000 backup unit last Tuesday. Guy walked past, saw my multimeter leads everywhere, and told me to stop guessing and read the damn diagram. Has anyone else had that moment where a simple piece of advice saved you hours of troubleshooting?
Was looking up a part number for a 737-800 and stumbled on the price for a new DME antenna. $4,200 for a piece of plastic and some copper. Boss laughed when I asked about ordering one instead of repairing the old one. Has anyone else had to justify a repair vs replace on these things?
I was wiring up a new Garmin GPS in a Cessna 172 last month and kept second-guessing my torque on some hard-to-reach screws. Picked up a budget digital torque adapter from Aircraft Tool Supply for 75 bucks, and it let me check the torque on fasteners already tightened. Turned out I was under-torquing about 30% of them by a good 5 inch-pounds. That little adapter probably saved me from chasing down a loose screw later. Anyone else use one of these cheap adapters or do you stick with the nice click-type wrenches?
I used to think any old wiring setup was fine for testing. Then last month I spent 3 hours chasing a glitch in a Garmin G5 install that turned out to be a ground loop from running signal wires next to power cables on the test bench. A senior tech showed me how even 6 inches of parallel runs can cause noise issues. Now I always cross power and signal at 90 degrees and it's saved me at least two more headaches since. Has anyone else run into this and found a fix that works better?
I was up on a King Air 350 last Wednesday doing a routine check on the Collins Pro Line 4 system. Everything looked fine on the ground, but about 10 minutes after takeoff (I was riding along to verify a squawk), the whole navigation display just went black. No flickering, no warning flags, just nothing. The pilot had to switch to the standby instruments and we turned around. Got it back to the hangar and found a failed power supply board in the main display unit. Took me the better part of 3 hours to isolate it with the multimeter and find a replacement part from our supplier in Phoenix. Has anyone else had a Collins unit crap out like that with no warning signs beforehand?
Old timer named Rick at the hangar in Boise told me to check the coaxial cable ends on the transponder antenna instead of swapping boxes, and sure enough one had a loose center pin that was making intermittent contact - has anyone else had a weird issue traced back to a simple connector problem?
I saw a huge difference between my old king air with a century autopilot that I could fix with a multimeter and my buddy's new Garmin GFC 600 where the manual just says 'replace the entire computer' - has anyone else noticed this shift making us lose basic troubleshooting skills over the last 5 years?
I was troubleshooting an intermittent comm drop on a King Air 200 in Nashville last week. Pilot said the #2 radio would cut out after 20 minutes airborne. Started with the antenna coax, looked clean. Then I found a 2 volt difference between the airframe ground and the radio tray ground. Re-ran the ground strap and tightened every screw I could find. Two test flights later and no issues. Anyone else ever had a radio issue that turned out to be a lazy ground bond instead of a bad box?
Guy brought his plane in for an intermittent PFD flicker. Worked fine on the bench but kept losing data in flight. Checked connectors, swapped LRUs, even re-pinned the backshell. Turned out to be a corroded ground lug behind the instrument panel that looked clean but measured 12 ohms. Never again will I skip the continuity checks first. Anyone else waste a whole shift on something that simple?
Back in 2019 when I was setting up my home shop in Tucson, I had to choose between a beat up Tektronix 465 scope from a retiring tech for $200 or a brand new Fluke 87V meter. I went with the Tektronix because I figured a scope would help more with avionics troubleshooting. Now I kinda regret it since half the time I just end up borrowing my buddy's Fluke anyway when I need a solid reading on a nav box. Anyone else have a tool choice they second-guess years later?
Ngl, I grabbed it just to check continuity on a KX 155 and noticed the temp readout was showing 40 degrees higher than ambient. Turns out the fan relay in the cooling duct was stuck and the radio was about to cook itself. Anyone else use temp probes during routine avionics checks?
I was totally skeptical about the $40 Drok tester from Amazon, figured it was just garbage for home gamers. But last Tuesday I had a stubborn intermittent fault on a nav light circuit in a 172 at KAPA and that little thing narrowed it down to a broken pin in 15 minutes. Has anyone else had a cheap tool surprise them like this?
Picked up a fancy pinout tool from the AES booth in Oshkosh last summer, figured it would save me time tracing harnesses. Turns out it only works on specific connector types I rarely touch. Anyone else buy a specialized tool that ended up being a paperweight?
I was just doing a routine check on a Collins 900 something that's been flying charter out of McCarran for years and I realized I had rolled over 5,000 hours on this one unit without ever having to pull it for a bench repair. That felt like a big deal honestly because when I first started in the late 90s you were lucky to get 1,500 hours out of a nav box before something drifted. The old analog stuff just had so many more failure points and you'd be swapping cards every other month. Now with digital and solid state everything it's like these units just run and run until the airframe gives out. It's wild how much reliability has changed in just 20 years. Has anyone else noticed a specific part going way longer than you expected?
I always skipped bench testing power supplies before install. Just plug and pray type of guy. But I saw this place in San Antonio where they had multiple PSUs hooked up to a dummy load setup. The technician showed me how one unit was showing a steady voltage on a multimeter but dropped under load. That scared me straight. Now I run every single PSU through a quick load test before it goes in a panel. Super easy with a cheap resistor bank. Has anyone else had a PSU fail under load that tested fine at idle?
I've pulled three harnesses this month where someone just plugged in a new LRU after a fault code instead of checking pin continuity first. Turns out two of those had bent pins in the connector that just killed the new box too. How do you guys get rookies to actually respect the troubleshooting flow when they're in a rush?
Spent 2 hours ripping out a bad encoder box on a CRJ only to find the real problem was a chafed wire bundle the old guy overlooked, now I double-check every schematic before pulling anything have you ever had a senior guy steer you wrong on a quick fix?
He said half the time a scope just shows you noise you don't need, and it hit me different because I'd been overcomplicating every single diode check for the last 6 months since I got my Fluke 87V.
I was tracing a power issue on a Collins RTU-4200 last week and the manual just said 'check pin 14 for voltage.' Turned out pin 14 was the signal ground and the real offender was pin 22 that had a cold solder joint. Took me 3 hours with a multimeter and a prayer to figure it out. Has anyone else had a manual leave out that one critical detail that costs you half a shift?
I was chasing a phantom glitch in a Garmin GNS 430 for three days straight. Checked all the pins, reflowed solder joints, even swapped the whole unit out. Turned out my cheap oscilloscope ground clip was picking up noise from the shop lights. I clipped the ground wire direct to the airframe ground instead of the test bench lug and the waveform cleaned up instantly. Saved me from sending a good unit back to the shop for no reason. Has anyone else had a bad ground clip mess with their readings?
I used to be all about using those push-in connectors for everything. Figured they were faster and good enough. Then this guy named Dave, been doing avionics since the 80s, watched me splice some nav light wires and just said 'you trust a spring to hold a plane together?' He showed me how he does a proper Western Union splice and then solders it. Took maybe 2 extra minutes. Now I can't unsee the difference. Any of you guys still use the push-ins or did you learn the hard way too?