L
21

Does anyone else refuse to trust a software update unless the plane has flown 50 hours first?

Back in 2018 I was at a maintenance hangar in Tucson and we loaded a fresh avionics software load into a King Air. The vendor swore it was tested. Three days later the MFD started dropping airspeed data on approach. Pilot caught it, but it got me thinking. Some guys at my shop treat software updates like gospel, others won't touch one until it's been proven in the field for weeks. Where do you draw the line? Is it on the manufacturer to prove it, or on us to be the guinea pigs?
1 comments

Log in to join the discussion

Log In
1 Comment
henry_hernandez
Treat it like any new part, flight test it yourself before you trust it... I always keep the old software load handy until I'm sure the new one ain't gonna bite me.
4