Had a nav system start a reboot loop right after a pit stop in Denver

I was doing a quick post-flight check on a regional jet last Tuesday. The main flight management computer just kept cycling on and off, about every 45 seconds. It was a software hiccup from a recent update that didn't fully install. I had to pull the circuit breaker, do a full power reset on the whole avionics bay, and then reload the nav database from a fresh USB. It took almost two hours to get it stable. Has anyone else seen a reboot loop from a partial database load?

3 comments

3 Comments

dakota_murphy9017d ago

Two hours on the ground for a reboot? That's wild.

sullivan.abby9d ago

Reminds me of the time our whole terminal went dark for a software patch... they told us it would be twenty minutes. We were sitting there for almost three hours waiting on a single server. Sometimes these tech fixes just balloon out of control.

mary_kelly16d ago

Yeah, @dakota_murphy90, pulling the breaker for a full minute before the reload usually fixes that loop.