By: Daniel Clark

Daniel Clark — Wed, 24 Apr 2019 03:45:13 +0000

As a retired Air Force pilot (26 years) and software test engineer (10 years), I wholly agree that the main fault lies with the engine control software. I happened to be a passenger on the Viking Sky’s harrowing voyage, and have a personal interest in the results of the investigation. While the programmers might have been very good at coding software, it’s obvious that the software wasn’t adequately tested by personnel with relevant nautical experience, who could have asked the “what if”questions to prevent this type of situation. Mission critical software should never be given the authority to shut down the engines without requiring active concurrence by humans. In combat aircraft, engines can’t be shut down, weapons can’t be fired/released, and critical systems can’t be shut down without the aircrew’s concurrence. Is this a limiting factor? Possibly, but we haven’t had any autonomous aircraft engine shut downs yet.

By: Kem Kough

Kem Kough — Sun, 21 Apr 2019 04:43:14 +0000

This is the most incredible story. I support the captains decision to sail. Even if there were low oil warnings there was no reason for the computer to shut down the engines 100 meters from the coast. The engines were fine and could have saved the ship if the anchor slipped. Although there is the possibility that the crew was incompetent I believe that the computers prevented an expeditious restart of the engines at a potential loss of 1000+ lives . The ironic thing is that the captain saved the ship by throwing out the anchor which is what sailors have done to save there ships over the last 4000 years in storms. The men who should be held accountable in this investigation are the software programmers for the engine logic. Kem. Kough

Comments on: How Did It Happen? Norway Begins Viking Sky Investigation

By: Daniel Clark

By: Kem Kough