12
A night shift in Anchorage made me stop trusting the book for every fault code
We had a 737 with a flickering nav light and the manual said to replace the whole unit, but I found a bad ground in the wing root after tracing the wire for two hours. Now I think we jump to the book fix too fast instead of doing the basic checks first. How many of you still start with the wiring diagram before you even open the book?
3 comments
Log in to join the discussion
Log In3 Comments
the_robert1mo ago
My buddy in Memphis chased a phantom avionics fault for a day, turned out to be a single pin backed out in a connector.
9
the_sage1mo ago
Ever think those weird electrical problems had to be something big? I used to assume it was always a fried board or bad wire. But after seeing a similar thing where a whole sensor was reading crazy because of one loose pin in the back, it totally changed how I look at it. Now I check the simple connections first. Makes you wonder how many "ghosts" are just something that didn't get pushed in all the way, right?
1
jadeg8125d ago
That "backed out pin" thing @the_robert mentioned is exactly what gets me - how often is it just something stupid simple like that? Did you guys end up finding anything else sketchy in that wing root or was it just that one bad ground?
7