The question of 'Basic Pilot Skills' is so irrelevant when the aircraft is so layered with synthetic computer programing and fly-by-wire-can't-turn-the-autopilot-off that it's a 300,000lb computer. We all know what computers do: They crash.
I think Doug is right-on with this.
There are brand new airplanes in service now, that at least one operator does not take the power off for overnight stops. Because maintenence has to spend over an hour clearing known nuisance software faults every time the ship powers up.
That situation even led to the discovery of an entirely new type of fault. This is where a particular system exhibited faults that caused erratic behavior when a unit remained powered for longer than 5 days.
The unit in question meets probably exceeds all current test specifications for that type of unit. In the past there were no requirements to ensure that a computerized black box operate continuously for so long. (I expect that to change.) That one really caught every one off guard. Significant pucker factor there.
Software is one of those things. When the complexity really scales up, 1000s of programmers, over decades, and millions of lines of code, multiple companies in different countries, code that outlives bankrupt companies, it's possible to have so many variables in the equation that it is impossible to generate error free code.
I don't want to sound entirely negative here. There are sucessful strategies for fault tolerant design. People work very hard at it. There is Level A software. Ref ->
http://en.wikipedia.org/wiki/DO-178B
It's gonna sound kind of stupid, but the folks that wrote Star Trek had it right. In the original version, they never had enough power, it was always the crystal thing. In the Next Generation, it was always the software. The SciFi folks pegged it there.