Rant: A new hire at the hangar said 'it's just a light' and it set me off

I was helping a guy fresh out of A&P school with a landing gear position light fault on a King Air. He found the bad bulb, swapped it, and when it still didn't work he shrugged and said, 'It's just a light, the MEL probably covers it.' I had to stop and explain that the 'just a light' tells the pilot if the gear is down and locked. We spent the next two hours tracing it back to a chafed wire in the wheel well that was three strands from shorting. That attitude is how small problems become big ones. If you don't respect every single circuit in this job, you shouldn't be signing off the work. It's not just about fixing what's broken, it's about understanding why it broke. How do you guys handle teaching that mindset to new techs who think some systems aren't critical?

3 comments

3 Comments

thomas_campbell1mo ago

Honestly, a buddy had a new guy dismiss a low oil pressure warning light as probably faulty. Turned out to be a real blockage, and they caught it just before a test run. That "just a light" mindset can literally cost an engine if nobody stops to ask why it's on.

garcia.miles3d ago

Man, I used to be that guy. I'd see a check engine light and my first thought was always a bad sensor, especially on older trucks. Then I had a coolant temp warning that I ignored. It wasn't the sensor, it was a stuck thermostat. By the time I finally checked, it had overheated and warped a head. That was a brutal, expensive lesson. Now any warning light gets the full check, no shortcuts.

joel2801mo ago

Yeah, that's the scary part. Like, what's the actual process for checking a warning light before you call it a false alarm? Do you just swap the sensor first, or is there a step-by-step check for pressure or flow? I've heard of guys just slapping in a new sender because it's faster, but then you miss the real problem.