In early 2021 the U.S. Navy issued new sleep regulations meant to deal with the problems that caused three warship collisions in 2017. A combination of problems was responsible but inadequate sleep for the crew, especially those serving on the bridge was a key factor. Lack of sleep diminished alertness to possible problems, like collisions with other ships. In all three accidents the alertness of the bridge was compromised by chronic lack of sleep. The problem was that the existing regulations did not work in practice. In 2017 sailors were supposed to get seven hours of sleep every 24 hours. Because of the watch schedule sailors had four hours on watch (at work) followed by eight hours of rest or performing other duties. The old regs suggested that sailors get their seven hours of sleep in two increments; five hours plus a two-hour nap. Sailors often were lucky to get the five hours and they did not get it at the same time every day because the watch schedule ignored the difficulty in falling asleep if your work schedule was constantly changing. The new rules stipulate that sleep be at the same time of the day for each sailor and that conditions in the berthing (living quarters) for the crews take note of that and keep things quiet down there so sailors are able to get to sleep and not be jarred awake frequently.
The accidents that caused damage to three ships within an eight-month period led to the deaths of 17 sailors and it took some time for the 7th Fleet leadership to determine what was going on. The first accident, in January 2017, involved the cruiser Antietam running aground while leaving an anchorage in Tokyo Bay. The damage to the ship was not great and Antietam was repaired and back in service by the end of 2017. The captain was relieved and there was some mention of poor training for the crew members on the bridge, who were in charge of lifting anchor and heading maneuvering the ship out of the harbor to the open sea. Things got worse in June and August with two 7th Fleet destroyers colliding with commercial ships at sea. These two collisions left 17 sailors dead and all were apparently related to lower readiness levels, overwork and crew fatigue in these two ships. This was later found to be common throughout the 7th Fleet.
This time the result was two collisions involving Burke-class destroyers (the Fitzgerald and McCain) with one of them fatal. These two destroyers had some of the worst readiness and training ratings in the entire fleet. These ratings exist to spotlight ships and crews, that need the most attention from senior leadership, especially the fleet commander. That was not happening and since the new Secretary of Defense was a retired (in 2013) marine general with firsthand experience with what was going wrong in the navy, the admiral responsible was held accountable in the traditional way and within weeks of the August collision, was relieved as 7th Fleet commander. Note that while both the Marine Corps and the Navy are part of the Department of the Navy, the two organizations have evolved into separate services. The Marines have always been different and that meant marine generals could get away with being more traditional and hard-ass than current navy admirals.
Another factor was the adoption of touch screen controls for ship navigation. The current SCC (Ship’s Control Console) used two touch-screens on the Helm (the bridge, where a sailor physically mannered the direction the ship went in) and in the Lee Helm that controls the speed and direction (forward or reverse) of the engines. It was discovered that the crews involved had placed the SCC in “backup manual mode.” This turned off computer-assisted help so that there was more direct communication between steering and the SSC. This made it possible for someone at another station to take over steering operations. The problem was that when someone tried to regain control of the ship from more than one SCC there were additional delays in anyone having control of steering and speed. Worse, and typical of touch screen UI (User Interface), the procedures for quickly regaining control were complicated and none of the crew involved were able to quickly take control and avoid the collision. Further complicating the situation was the fact that the officers and sailors involved were suffering from lack of sleep and experience with emergency use of the SCC. As a result, the navy is converting back to the traditional manual controls, which are more intuitive and familiar. One can thank decades of movies and TV shows featuring the traditional manual controls.
The problems with leadership and training were rather obvious even before the three accidents. In 2017 it was no secret that these problems existed throughout the navy but were most acute in the 7th Fleet, which has been the busiest for over a decade because it has to deal with growing Chinese naval power and more frequent crises with North Korea. One could say the problem was navy-wide but most intense in the 7th Fleet. Not enough of the admirals were willing to speak up and admit to the politicians and voters what was going on and why it was not being addressed. One reason was that the politicians wanted admirals who would keep quiet. Those admirals who spoke out got forced into retirement and replaced by younger officers willing to play by the new rules. This is not unique in American history or military history in general. But this occurrence is another after-effect of the Cold War ending and attitudes changing with regard to responsibility and military readiness.
The immediate problem, in short, was that the navy has been getting smaller since the Cold War ended in 1991 and that process continued after 2001 because most increased defense spending went to the Army, SOCOM (Special Operations Command) and marine operations in Iraq and Afghanistan. The navy and air force had to get by on a lot less. For example, the number of ships in the navy went from 333 in 1998 to 277 in 2017. Yet the navy kept the same number of ships (about a hundred) deployed overseas despite there being 17 percent fewer ships. Worse the newer ships, and some of the older ones, were experimenting with smaller crews (and more automation). This is still a work in progress but meanwhile, lots of 7th Fleet ships were operating at a wartime tempo. This was wearing down the crews as well as the ships.
Although the navy knew this was going on, not a lot was done to deal with what was obviously a growing problem. For example, in the two years before the accidents the number of warships in the 7th fleet not certified as ready for combat increased five-fold (to 37 percent). The reasons why were no secret either. Many sailors were working over 100 hours a week when at sea, often more than the standard 70-81 hours a week. Ships were more frequently unable to go to sea because of deferred, by manpower shortages, maintenance. The most serious shortages were in training, which apparently contributed to the three serious accidents and many more events that could have gotten very ugly.
Further investigation of the crew performance and training issues uncovered the SCC UI problems which, it turned out, applied to a lot of new equipment that was using a touch screen UI. Problems with UI have become more of an issue as more ships, aircraft and ground vehicles employ them. There is also a lot more of these new UIs and the military had already learned the value of adopting UIs already existing in commercial products (like video games) that most sailors were already familiar with. One of the best examples is the widespread adoption of the Xbox game controller for many military systems. For more complex touch-screen UI a more thorough and intensive effort at developing and testing the UI is required. Military aircraft manufacturers are aware of this and the pilots who test UI designs are harsh critics of any UI ideas that will be less effective than older manual controls. The navy did not apply these UI development standards to the SCC, and many other UI systems. So now the navy has to reexamine the use of these UIs to ensure they are at least as effective and user proof in emergency situations.
In a gaming or business software situation a bad UI will cause a lot of customer dissatisfaction and lower sales. On ships with sailors suffering from chronic lack of sleep, bad UI meant groggy sailors were often not able to react quickly enough to deal with major problems.