Loading…
18
My lead told me to ignore the intermittent fault code on a Garmin G1000, and it cost us a full day
He said it was just a sensor glitch on a Citation we were working on in Dallas, and to clear it and move on. Two days later, the plane came back with the same issue, and we spent eight hours tracing it to a bad connector pin that was causing a full avionics bus reset. What's the weirdest 'ignore it' advice you've gotten that turned out to be a major problem?
3 comments
Log in to join the discussion
Log In3 Comments
the_kim6mo ago
Ugh, classic "it's fine" that never is.
6
patricia3856mo ago
Why do leads always think a fault code is just the avionics having a bad day? That "ignore it" move is a sure way to get the plane back in your hangar for a full shift, just like @the_kim said. My old boss told me a rough-running engine was just "cold Texas fuel" and to send it, which led to a cracked cylinder head found on the next stop. It's like they forget we're fixing planes, not restarting a computer. What's the point of having the warning system if we're told to pretend it's lying?
3
seth_nguyen5mo ago
Look at it from the lead's side, sometimes those systems do throw false alarms and you have to make a quick call to keep things moving. I get why @the_kim is annoyed, but chasing every single ghost code would ground half the fleet.
0