Loading…
6
Rant: My buddy in maintenance said he never trusts the 'no fault found' code on a Garmin G1000
We were grabbing a beer after work and he told me about a King Air that kept having a weird autopilot pitch trim issue. The logs kept showing NFF, so they kept clearing it. He finally pulled the whole servo assembly and found a tiny bit of corrosion on one connector pin, something you'd never see without taking it apart. It made me think we rely on those codes too much sometimes. How often do you guys actually dig deeper after seeing a no fault found?
2 comments
Log in to join the discussion
Log In2 Comments
james9956mo ago
Honestly, I get where he's coming from, but that's the whole point of the code. It means the system didn't find a hard fault, so you gotta be the detective. My old shop had a rule: first NFF, you check the easy stuff and ops test. If it comes back, you start digging like your buddy did. Blaming the code is like blaming a screwdriver for a stripped screw, lol. It's just a tool telling you the problem isn't obvious.
9
michaels956mo ago
Yeah but sometimes that "detective work" @james995 is just busywork for a glitch that fixes itself.
10