Ok so “doesn’t exist” may be a slight overstatement. A better way of phrasing it might be “operator error is often used as a way of warding off close examination of how systems fail.”
You read about airlines accidents attributed to pilot error, and almost universally you find overworked, overtired people who have to deal with inadequate training, and poorly maintained equipment. Often investigations uncover a pattern of management ignoring problems that pilots regularly have to deal with. Out-of-date terrain data, false sensor readings, confusing systems presentation, fatigue.
The cargo airline industry fights to keep its pilots exempt from crew rest requirements and a fatigued crew crashes a mile short of the runway. Only the two crew on board die, so really it’s no big deal, right?
Amtrak builds a new bypass to cut 10 minutes off the travel time from Portland to Seattle but doesn’t give the engineers enough training to prepare them for it, nor installs adequate signage to warn of a 30mph curve, so on the inaugural run the engineer hits the curve at 80 mph.
Construction on a nuclear power plant runs into trouble and so to make a key pressure-bearing component fit, they install an S-bend around a pipe, which causes falsely water level readings. Operators open a valve to reduce what they think is excessively high pressure in the reactor and it melts down.
And all of these get simplified, either initially, or in perpetuity, as operator error. Because operators are cheap and easy to replace. Firing someone and laying the blame on them is cheaper than reassessing and restructuring a management culture built on passing the buck.
