I was always nicking the center conductor on RG400 and just thought that was normal. One day a guy with 20 years experience walked by, grabbed my stripper, and showed me I was using the wrong depth setting for that cable. Anyone else have a basic task they thought they had down until someone called them out?
I was chasing an intermittent avionics bus fault on a 172. Multimeter showed 12 volts at the master relay when it was supposed to be dead. Took me 3 hours of pulling panels and checking grounds before I realized a tiny piece of metal shavings from a recent repair was bridging two pins on the back of the alternator control unit. Anyone else run into phantom shorts that drove you up a wall?
I was bench testing a brand new Garmin GNC 255 and it kept dropping power for no reason. Pulled the case, a pin on the backplane had a cold joint that barely touched the pad. Has anyone else found factory defects slipping through lately?
Now I back-probe every single pin before buttoning up a panel, even on fresh out of the box parts, because that one cracked shell cost me three hours of troubleshooting a ghost fault.
I was on a job last week at a small hangar in Boise, fixing an intermittent fault on a King KX 155 nav radio. The previous guy had used standard wire strippers on the coax, which crushed the dielectric and left little nicks in the center conductor. That caused a short that took me 45 minutes to trace with a multimeter. I swear, just buy a proper coax stripper for $30 and save yourself the headache. Has anyone else run into this kind of sloppy work on older GA planes?
I was looking through some old training manuals from the 80s I found in a bin at our hangar in Detroit, and it said the 737-200 had around 500 pounds less wiring than the NG models. That really surprised me, all that extra copper adds up fast. Has anyone else run into old specs that made you rethink how much things have changed?
I was working on a Citation 560 in a hangar in Wichita last night. The right nav light was flickering and the radio would cut out on the same side. Ran my continuity checks three times and everything looked fine but it kept acting up. Finally I just pulled the connector apart and saw a tiny bit of corrosion on one pin that I missed the first two looks. Cleaned it with a little contact cleaner and re-seated it, problem went away. Has anyone else spent way too long chasing a ground that was just a dirty pin?
I've been fixing avionics racks for 15 years and noticed the point-to-point wiring from the 80s lasts forever while these new pre-made harnesses start cracking after 5 years. The old stuff used thicker insulation and real solder joints instead of those crimp connectors. Anyone else see the same pattern on their bench?
Had a buddy from the Gulfstream shop keep telling me to buy a Fluke 1587 for troubleshooting. I thought my old Klein was fine and he was just wasting money. Last month I got a weird intermittent comm issue on a Global 6000 at my hangar in Phoenix. The insulation test caught a chafed wire that my regular meter missed completely because it only showed up under load. After 3 hours of chasing ghosts, that one tool found the problem in 5 minutes. Anyone else have a tool they were dead wrong about?
Worked on a Gulfstream GIV last month where the previous shop left out the bonding jumpers on three composite access panels, and I had to track down static discharge issues for two days straight. The difference in static buildup between those panels and the properly bonded ones was night and day, even just sitting on the ramp. How often do you guys actually see corrosion under those bonding tabs when they skip the prep work?
Yesterday I decided to swap a bad VOR indicator on a King Air. Thought it'd be a 20 minute job. Turned out the connector pins were corroded and one broke off, so I had to pull the whole nav panel to repin it. Took me 3 hours for something that should have been easy. Anyone else run into this kind of hidden damage on older birds?
That false reading almost made me swap a perfectly good generator control unit on a Friday afternoon, has anyone else had a budget meter burn them on a simple continuity check?
I swapped out the original RG-58 cable on a Cessna 172 last weekend because the GPS signal was dropping every 10 minutes. The before-and-after was night and day, with the new RG-400 giving me solid satellite locks even under heavy cloud cover. Has anyone else seen that big of a jump just from changing coax on an older panel?
I was helping a buddy troubleshoot a nav system fault last Thursday on a Harrier. Three other guys had already looked at it and swapped the box. Turned out someone had repaired a chafed wire in the harness but used the wrong gauge replacement. The resistance difference was small but enough to mess with the signal. Has anyone else run into issues from mismatched wire gauges in critical harness repairs?
I had a pitot static readout glitch last week on a 2006 King Air and went with the firmware flash instead of the full bench recalibration, and now I'm second guessing if the 0.5 knot offset I'm seeing is normal or a sign I made the wrong call, anyone run into this before?
The short was so intermittent that my meter kept showing open until I bypassed the broken ground lug with that clip. Makes me wonder if we rely too much on expensive test gear instead of old school troubleshooting tricks. Has anyone else rigged a janky workaround that ended up finding a fault faster?
Back in 2019 I bought this used DMM with waveform capability thinking it'd solve all my troubleshooting issues on old King radios. Turns out my basic Fluke does the same job 90% of the time and that extra feature set just sits in the case. Anyone else drop cash on a tool that sounded great but ended up being overkill for the bench work you actually do?
I was at a regional line maintenance shop in Boise last Thursday and saw three different units with corrosion hiding under the star washers - all because nobody bothered to torque them proper after the last panel swap. Has anyone else run into loose grounds causing intermittent failures that drive you nuts?
I was going through my logbook this afternoon and realized I just crossed 1,000 hours of bench testing since I started this job two years ago. Not one of those jobs came back for a rework. It caught me off guard because I still feel like a rookie sometimes. My lead told me that was a solid milestone for someone my experience level. I guess all those late nights double checking pinouts paid off. Has anyone else tracked a specific metric that surprised you when you looked back?
I was working a late shift at O'Hare in July 2019 when a big storm rolled in fast. We had a 737 on the ramp that took a direct hit to the static wick on the left wing. The surge went right through the bonding strap and fried the VOR receiver in the cockpit. The lead tech told me 'that strap is your best friend until it isn't.' After that night, I started double checking every ground cable connection before storms hit. I also make sure I use shielded grounding clamps now instead of the cheap ones we had back then. We replaced three avionics boxes on that bird and the bill was over 40 grand. Has anyone else seen a lightning hit take out something unexpected like a transponder or a radio?
He mentioned that a perfect comms check on his preflight made him feel more secure than any other system sign-off. I mean, I always knew comms were important, but hearing it framed as a primary safety feeling, not just a checklist item, hit different. Anyone else had a user's perspective change how you prioritize a routine task?
All those analog gauges and switches, miles of point-to-point wiring behind the panels. It really hit me how much we've traded physical troubleshooting for staring at a laptop screen. Anyone else miss the days when you could actually trace a circuit with your hands?
Last week at the hangar in Phoenix, I had to pull data from a 737's recorder after a maintenance check. The new software had been giving me trouble for months, but this time I followed the steps from the manual exactly and it worked on the first try. I got the full data set in about 20 minutes, which saved me a ton of time. Has anyone else had to learn this new system and found a good trick for it?
Had to troubleshoot a comms issue on a Gulfstream last month and pulling up the interactive schematic saved me at least two hours of flipping pages. The search function alone is worth the switch. Anyone else fully converted, or do you still keep the paper manuals around as backup?
Had a unit at our shop in Dallas that wouldn't accept the standard firmware load. The manual just said to send it back. Instead of boxing it up, I tried a full power cycle with the avionics master off for a full 10 minutes, then reloaded. It took the update perfectly. Has anyone else found a workaround that the official docs say not to do?