I’m in IT and have worked with the guys that babysit the mainframe processing all night, calling us programmers when a job failed, etc.
When one guy leaves a shift, he passes on the notes from the previous shift, listing all activity for that shift. We did it that way in the 1980’s for crying out loud.
That crew should have had the same knowledge the crew before them had. This is a breakdown/flaw in that airline’s procedures.
It doesn’t mean Boeing is off the hook, but it looks like it really was a case of “pilot error” to some degree, if only because a different pilot had the same thing happen but the plane didn’t crash.
If the failure of a single sensor can send the aircraft into a dive toward the ground, it is not "pilot error" if the unfortunate pilot is unable to deduce the cause and determine the solution in time. The problem is that the aircraft dove toward the ground.
It would have been great if these pilots had been better trained, or had better documentation. But the fact is the aircraft crashed itself, because it was getting erroneous sensor information, and the system was not designed well enough to prevent a fatal response by the flight control computer.
We had those guys where I worked too. They were called “Console Operators”.