///AMG
Well-Known Member
There are to many combinations and permutations of system issues that arise that the old adage of “count to ten, slew a piece of paper of the printer, write down the ECAM message” because chance are, the message cleared itself (done! don’t even wonder why it happened) or if it’s still there, follow prescribed procedure and read all the considerations. But when a person with self-ascribed “high systems knowledge” starts going off script, they’ll sometimes find themselves in a variant where none of that applies and then he’s compounded a minor annoyance into “why the deuce are we in alternate law?” with catlike swiftness.
This is interesting. So is there a "CTL ALT DEL" type procedure? I know in the FA-18, cycling both gens, or cycling both mission computers is often step one during mx assisted troubleshooting of any number of nuisance failures of systems. Everything is very interrelated, and momentary surges of trons during startup can cause stuff to happen that can be cleared this simply. The counterpoint to that, and the reason I frequently rolled my eyes at this "procedure" when I started to get more experienced in the jet, was that many times it would mess up other things that previously were fine. So that (generally safe for flight) TACAN problem you were working for example, suddenly becomes like 6 other unrelated failures and a flight control computer/functional degrade that are now downing gripes, and you spend the next hour trying to clear everything.