Spent three hours chasing a phantom voltage drop on a G1000 system

I was sure the issue was a bad ground in the tail section of a Cessna 172. I had my Fluke meter on the ground stud and was getting a solid 0.2 volts, which seemed way too high. My lead finally came over, watched me for a minute, and asked why I was testing with the avionics master off. I had the whole system powered down, so of course the reading was meaningless. I felt like an idiot. Who else has made a simple mistake that wasted half a day?

4 comments

4 Comments

jennybailey1mo ago

Oh man, that's a classic one lol. Been there chasing ghosts with the power off. The real kicker is when you finally turn the master on and that voltage disappears, proving you just fought your own shadow for hours. Always start with the basic power state check now, it saves so much pain. Live and learn, right? At least your lead caught it before you started tearing into the airframe.

kim_mason551mo ago

Right? The worst feeling is that slow burn when you realize you checked everything but the main breaker. My old crew chief used to call it "chasing the dark." Makes you feel real smart for a solid twenty minutes.

anthonyrivera19d ago

Classic case of skipping step one.

kim_mason551mo ago

Saw a maintenance manual once that had "verify power state" as the first step for every single trouble tree, bolded and in a red box. Thought it was overkill until I spent a morning checking continuity on a dead bus. Turns out the hangar power cart was just unplugged. Those checklist writers know what they're doing.