Had a guy come in last month at the hangar in Bakersfield, swore his comms were crystal clear. I pulled the unit and found a corroded pin that was barely hanging on. He watched me swap it and said quote "I guess you do know what you're doing." Made me laugh, but also wonder how many other pilots just ignore the crackling. Anyone else run into pilots who fight you on basic diagnostics?
I spent over a decade using a multimeter with just the beep function thinking it was fine for checking wire bundles. Then last Tuesday an old Gulfstream wiring diagram showed a specific resistance range, not just a dead short or open. Anybody else have a moment where you realized you were skipping a whole layer of test data?
Back in 2021 I dropped $2,800 on a brand new Tektronix scope for my home bench thinking I needed all those advanced features for troubleshooting autopilot systems. Fast forward to last month when I was working on a King KX-155 nav radio at my shop in Orlando and my old beat up analog scope caught a glitch the digital one missed completely. The new one has all these decoding menus and math functions that just slow me down when I'm trying to find a bad cap or a cold solder joint. My buddy Mike has been using the same 1980s B&K scope for 20 years and his repair time is half of mine. I'm honestly thinking about selling the Tektronix and putting that money into a good soldering station instead. Has anyone else found that simpler test gear actually works better for radio work?
Whoever routed those wire bundles through the aft equipment bay must have been in a hurry because they were snagged on two different support brackets and one was already chafed through the jacket, has anyone else found lazy routing on newer frames?
Last Tuesday I was swapping out a nav antenna coupler on a King Air and knocked a can of soda right into my open tool drawer. I left for lunch and came back to find a sticky mess of schematics and ferrules glued together. The before was neat organized chaos, the after looked like a toddler exploded a craft project. Has anyone else had a drink spill ruin their whole afternoon like that?
Last Monday I was tracing a faulty EFIS display on a Cessna 172, pulled the manual for the pinout, and spent 3 hours chasing a ground fault that turned out to be a misprint in the schematic. Then Wednesday, I'm swapping out a Garmin GNC 255 and the connector kit in the parts bin had the wrong pin crimps - no one labeled the old box. By Friday, I was ready to throw my multimeter across the hangar. Has anyone else had a week where it felt like the documentation was actively trying to mess with you?
It was a D-sub on a King Air that I've been swapping cards in and out of since 2018, and the pins still had proper retention force. Has anyone else kept close tabs on connector cycle life or am I just weird about it?
Used to poke around with a multimeter for hours chasing intermittent shorts. Got tired of the dance, bought a Flir for $350. Found a bad power supply module on a 737 in under 10 minutes. The heat signature just lit up the bad solder joint. Now I scan everything first before breaking out the probes. You guys use thermal tools or still stick to old school methods?
I pulled a bad nav receiver out of a 737, bench tested the replacement four times, then spent two hours chasing the same fault before a veteran tech pointed out my test harness had a bent pin, so now I check the gear before I ever blame the box again - has anyone else had a test adapter fool them like that?
I figured I'd save some cash on a older Tektronix for bench work, but it just showed a blank screen no matter what I did. Has anyone else had luck getting their money back from eBay on bad test gear?
I was using standard crimpers on some D-sub pins for a nav system swap on a King Air 350. The pins felt tight but the senior tech walked over and just looked at my work for like 10 seconds. He pointed out the insulation was slightly pinched near the barrel and said that causes intermittent failures after 500 hours of vibration. Turns out I needed a M22520/1-01 die set the whole time which I didnt even know existed. I had done maybe 50 installs that way without a single complaint. Anyone else have a basic skill they thought was fine but turned out to be completely backwards?
I was talking to a retired guy at my local shop last Saturday, and he mentioned he still uses a basic Fluke 77 meter from the 80s for everything. He said "these new digital scopes are nice, but they just eat batteries and crash when you need them most." It hit different because I had just spent $400 on a fancy handheld scope that glitches out in noisy hangars. Makes me wonder if I am overcomplicating my troubleshooting kit for no real gain. Anyone else go back to simpler tools after chasing the newest gear?
I had a 737 come in last Thursday with wiring that looked like a bird's nest from the factory. Took me three hours just to trace one circuit. The old timer who did the original install in '98 must have been in a hurry or something. Any of you run into a plane where the before and after is night and day after a proper rewire?
Been wiring planes for about 3 years now and I always thought continuity tests were just a waste of time. Old salt at the hangar in Nashville saw me chasing a ghost on a 737's nav light circuit and he just shook his head. Showed me how to actually use the damn thing in about 5 minutes. Turns out I was reading resistance instead of continuity and missing a broken wire in the harness. Fixed it in 20 minutes after that. Anyone else have a moment where you realized you'd been doing something basic the wrong way for way too long?
I was chasing a phantom voltage drop on a Garmin GNS 430 last Tuesday and my lead was reading negative where it should have been positive. My coworker Jeff just looked at me and said 'you got the red and black swapped, man' and walked away. Has anyone else done something this dumb for way too long?
Had this intermittent issue on a Gulfstream GIV where the VOR would freak out only at cruising altitude, and after weeks of guessing I bought a tiny Anritsu unit off eBay and traced it to a corroded connector behind the radio rack.
I was grabbing breakfast before a shift last Tuesday, and this retired guy who worked on F-14 avionics in the 80s sat down next to me. He asked what I was working on, and I told him about a persistent ghost signal issue on a King Air 200 that had me swapping out antenna cables for three weeks. He just laughed and said 'Check your bonding straps before you waste another hour.' Turns out he was right. I had overlooked a corroded strap on the stabilizer that was causing all the noise. Has anyone else had a simple ground fix solve something that seemed way more complicated?
I spent 4 hours tracing a intermittent autopilot disconnect in a 2008 model and found the shielding was rubbed raw behind a bulkhead clamp that looked fine from the front, has anyone else seen that specific issue on those clamps?
Been chasing a gremlin in an older Garmin GNS 430 for like 3 months, swapped every board twice before I found a cold solder joint on the backplane connector. Felt like winning the lottery watching all the self-tests go green in the shop at PDX this morning. Anybody else get weird fixes from bad solder instead of blown parts?
I spent an entire Saturday tracing a faulty ground wire on a Cessna 172 that turned out to be a corroded connector hidden behind a firewall blanket, and I still can't believe it took that long to spot.
I showed up at 6 AM to find 3 planes with nav light failures, all after a weekend storm. By 9 AM I had one fixed but the second one had a corroded connector hidden behind a panel I had never pulled before. Took me 4 hours just to trace the break with my Fluke meter. Then the third plane had a Garmin screen glitch that kept cycling through startup mode. I spent until 5 PM swapping LRUs and still had to sign off a deferral. The whole week was like that, one thing after another breaking. Has anyone else had a stretch where everything just seems to fail at once?
I was out at KPDX in Portland tracing a VOR reception issue on a CRJ-700 and swapped three antenna cables before I found the problem was just a loose BNC barrel. That little connector cost me 8 billable hours and had the plane sitting on the ramp. Any of you guys carry spare coax barrels in your kit for situations like this?
I was reading an old maintenance manual from 1985 for a Gulfstream I worked on last week. Turns out they used a Teflon coated wire that looks exactly like the modern stuff but it had a DIFFERENT insulation rating that could crack at 150 degrees instead of 200. Nearly swapped in the wrong replacement on a pitot tube harness because I assumed it was the same. Has anyone else run into this weird spec change on older airframes?
I was digging through the AIM last week after a weird glitch in the Garmin G1000 and stumbled on this one fact: if your navigation database expires while you're in the air, the system might not warn you until you try to load an approach. I've been doing this job for about 8 years now and never thought about it because I always check databases on the ground. But my buddy out of Denver had a close call last month where his 430W database went stale right before vectors to final. He said the unit just gave a 'no valid approach' message. So now I tell all the younger guys on my crew to always check the expiration date before every flight leg, not just at preflight. Has anyone else run into a situation where database timing caught you off guard?
Used to spend 20 minutes per panel fighting those wire nuts in tight spaces. Tried a Deutsch crimper last month on a King Air install and cut install time by half. Anyone else ditch the old methods for crimp connectors on pitot-static systems?