Banner for The Langley's Material Test in Fleet Problem VII

The Langley's Material Test in Fleet Problem VII

USMilitaryArchive
USMilitaryArchive

Published on

50 Views
0 Likes
Text Size

Interwar Fleet Problem Preparations

The silence was a weapon. A thick, humid quiet, broken by the slosh of bilge water and the rhythmic hum of generators. In the gray-painted steel storerooms of the USS Wright, the ship held its breath. Somewhere off the coast of Panama, the Blue Fleet waited for the Black Fleet to make its move. On the bridge, admirals from Washington played war games, moving ships like pieces on a grand board. In the guts of the vessel, the reality was paperwork, manifests, and the fear of not having the right part when something broke. The teletype chattered for weeks, spitting out directives for Fleet Problem VII. The scenario was massive. Defend the Panama Canal. The entire Battle Fleet, designated the aggressor Black Fleet, was tasked to attack. The Scouting Fleet was to stop them. It sounded simple on paper. For the supply crews, it meant a mountain of requisitions and the certainty that whatever the admirals planned, reality would be far messier.

The exercise felt like a setup. The initial demands for Fleet Problem VII were ambitious. The fleet was expected to defend a strategic chokepoint and test new doctrines in scouting, convoy escort, and naval aviation. The USS Langley, the Navy's only real aircraft carrier at the time, was the star. Her biplanes were the eyes in the sky, a key defense against attacking battleships. Headquarters expected a seamless integration of this new air power into fleet operations. Spotting submarines. Repelling attacks from land-based bombers. The paperwork flowed from Washington. Each dispatch outlined a new tactical wrinkle to be tested, a new performance benchmark to be met. To the planners, it was a grand experiment. To the supply officers, it was a logistical nightmare. The reams of paper never accounted for the simple facts of life at sea. The corrosive salt air. The constant vibration that shook screws loose. The strain that sustained high-speed operations put on aging machinery.

This was not a new story.

The year before, during Fleet Problem VIII, the scenario was different but the friction was the same. That exercise, held between California and Hawaii, pitted a cruiser force from Pearl Harbor against the Battle Force. It was a test of convoy screening and anti-submarine tactics. The operational demands were just as high, focusing on long-range scouting and the protection of vulnerable supply lines. Archival evidence shows the exercises were designed to be unscripted. This forced captains and admirals to use their best judgment. It was meant to foster adaptability. It also created massive uncertainty for the supply chain. No one knew what the fleet would need next because the commanders themselves were reacting to unexpected developments. One day the priority was extra fuel for a high-speed chase. The next, it was spare parts for a destroyer’s engine that had been run into the ground.

The disconnect was baked in from the start. Admirals at the Naval War College and in Washington devised complex scenarios based on grand strategies, particularly War Plan Orange for a conflict with Japan. They issued broad objectives and timetables. The 'how' was left to the fleet. This created a headquarters bubble where the clean lines on a map bore little resemblance to the world of steel, steam, and sweat. Preparations for Fleet Problems VII and VIII were a perfect example. The expectation was for the fleet to operate at peak efficiency for weeks, simulating the stress of war. Little thought was given to the strain this would put on the logistical train. The tenders, oilers, and supply ships were the true backbone of the fleet. They were tasked with sustaining a war-level tempo with a peacetime supply system. A contradiction bound to break.

Carrier Group Supply Chain Deficiencies

The tempo of Fleet Problems VII and VIII threw a harsh light on the fragile supply chains for naval aviation. A core issue was handling aviation gasoline, or avgas. Unlike the thick, stable Bunker C oil used by capital ships, avgas was volatile. Its fumes posed a constant threat. A review of operational logs (NARA Record Group 38) indicates the process of transferring this fuel from oilers to carriers like the USS Langley (CV-1) and the new USS Saratoga (CV-3) was slow and perilous. On the converted collier Langley, fuel was stored in drums. They had to be physically manhandled. This process was entirely inadequate for sustaining the high sortie rates demanded by the exercises. Even the purpose-built Lexington-class carriers, with integrated fuel bunkers and pumping systems, struggled. The exercises simulated combat conditions that required carriers to launch and recover aircraft at a relentless pace. Ready-use tanks drained faster than they could be safely replenished from the fleet’s oilers. This created a bottleneck where flight operations were dictated not by tactics, but by the slow, dangerous work of fueling crews.

Fuel was only the first breakdown.

Supplying specialized munitions for the new carrier air groups presented a different set of problems. Battleship logistics were massive but simple. A ship needed a few types of large-caliber shells and powder bags. Archival evidence shows a carrier air group required a complex and varied arsenal. This included hundreds of 100-pound, 500-pound, and 1,000-pound bombs, aerial torpedoes, and vast quantities of machine-gun ammunition. Each weapon system came with its own logistical burden of distinct fuzes, arming wires, and specialized handling equipment. During Fleet Problem IX, the Saratoga’s successful independent raid on the Panama Canal was a tactical triumph. It also stretched its ordnance supply to the breaking point. The process of moving a 1,000-pound bomb from the deep magazines, assembling its fuze, and loading it onto an aircraft on a pitching flight deck was a slow, muscle-intensive task planners had not fully appreciated. The free-play nature of the war games meant ordnance requirements could change in an instant. The supply system was too rigid to respond. Aircraft were armed with whatever was most accessible rather than what was most effective.

A fundamental flaw exposed by the exercises was the inability of the logistical train to keep pace with new, faster combatants. The Lexington-class carriers, with their converted battlecruiser hulls, were capable of speeds exceeding 33 knots. This allowed them to operate as fast task forces, able to outrun ponderous battleship fleets. The fleet’s oilers and supply ships were a collection of much slower vessels. Many had top speeds of only 12 to 14 knots. During high-tempo carrier operations, destroyers burned through fuel at an accelerated rate, sometimes tripling consumption to keep up with the carriers. This created an impossible tactical choice for commanders during Fleet Problems VII and VIII. Either slow the entire carrier group down to the plodding pace of its oilers, sacrificing speed, or allow the carrier and its escorts to dash ahead, risking fuel exhaustion far from support. The famous end-run by the Saratoga in Fleet Problem IX proved the concept of the independent carrier strike. It also demonstrated that such an operation was unsustainable. The carrier had completely outrun its supply line. The combat radius of the Navy’s most advanced striking forces was dictated not by the range of their aircraft, but by the maximum speed of the slowest oiler in the fleet.

Inter-Ship Communication Disconnect

The scale of the Fleet Problems guaranteed a breakdown in command. Exercises like Fleet Problem VIII unfolded across the vast expanse of the Pacific between California and Hawaii. The fleet was intentionally stretched across hundreds of thousands of square miles of open ocean. A scouting force of cruisers, probing for the enemy Orange fleet, could be 300 miles or more from its own battle line. A review of operational logs indicates this was by design. It was meant to simulate the immense distances of a trans-pacific war envisioned by War Plan Orange. Planners in Washington wanted to test the Navy’s ability to project power. What they demonstrated instead was that the fleet’s nervous system was not up to the task. Visual signaling with flags or searchlights was impossible at these ranges. Ships were dependent on a technology still in its infancy. The geographical separation was a constant, oppressive factor that isolated commanders.

The ether was not a reliable ally.

At the heart of the disconnect were the primitive high-frequency radio sets that equipped the fleet. In the 1920s, naval communication was a laborious, multi-step process. It relied on technology highly susceptible to failure and interference. A scouting report from a cruiser’s floatplane or a submarine first had to be manually keyed in Morse code by a radio operator. The signal, transmitted from a low-power set, then had to fight through atmospheric static and interference from other naval and commercial transmissions. For any message of substance, it had to be encrypted first. Archival evidence shows this involved radio personnel painstakingly converting the message into four or five-letter groups using massive, cumbersome codebooks (like the Navy Cipher Box M-94). On the receiving end, the process was reversed. An operator, straining to hear the faint Morse signal through a hiss of static, would write down the coded groups. These were then hand-carried to a communications officer who began the slow process of decryption with a corresponding codebook. This entire sequence, from initial sighting to a decoded message on the flag bridge, could take hours. A fatal delay when fleets were closing at a combined speed of over 40 knots.

This communication lag repeatedly crippled tactical decision-making. During Fleet Problem IX, the USS Saratoga's raid on the Panama Canal was a triumph of aviation. The exercise also exposed how old intelligence could lead to disaster. In one phase, scouting reports correctly placed enemy units. Due to the hours-long encryption-transmission-decryption cycle, the information was dangerously stale by the time it reached the fleet commander. Admirals consistently found themselves ordering squadrons to intercept targets based on positions that were three to five hours old. The result was a series of frustrating phantom chases. Destroyers and cruisers burned irreplaceable fuel to race towards empty patches of ocean where the enemy used to be. The exercises demonstrated that even perfect intelligence was useless if it could not be disseminated in time.

This created a command vacuum. A chasm between information and action defined the headquarters bubble. The fleet admiral, steaming on his flagship, often made decisions based on a tactical picture that was hours out of date. The problem was magnified for the leadership back at the Navy Department in Washington. Their strategic understanding of the exercise was based on fleet-wide summaries that were often a full day old. Logistical data, such as the fuel status of individual destroyers or the ammunition stores on a carrier, traveled through the same clogged channels. Operational logs from Fleet Problem VIII show the Blue Fleet commander making decisions based on faulty assumptions about the location of his own oilers. This forced escorting destroyers, which burned fuel at an alarming rate at high speeds, to dangerously low levels. Their combat effectiveness was limited. They were vulnerable. Strategic choices were being made with an incomplete and distorted picture of the fleet’s actual supply condition, a direct consequence of a communications network that could not keep up.

Quartermaster Bureaucratic Ineffectiveness

The Quartermaster Corps operated under a peacetime system of procurement. It was fundamentally incompatible with the tempo of simulated warfare. A review of operational logs indicates every request, from a box of rivets to a replacement gyrocompass, had to follow a rigid, multi-stage paper trail. A ship’s supply officer would generate a requisition form (Form NAVSUP-7B). It was then hand-carried or sent by signal lamp to the flagship. From there, it was encoded and radioed to the nearest shore-based command, which forwarded it to a regional supply depot, potentially thousands of miles away in Norfolk or San Diego. Each step introduced delay, human error, or misplacement of paper. The system was designed around accountability and cost control in a predictable environment. It had no mechanism for prioritizing urgent, battle-damage-related needs over routine replenishment. Archival evidence shows the requisition protocols for Fleet Problems VII and VIII were identical to those used for ordering paint for a ship in drydock. The bureaucracy made no distinction between a warship needing to fight and a barracks needing new windows.

This structure guaranteed failure.

This systemic paralysis was laid bare by the breakdown of machinery under the strain of the exercises. During one phase of Fleet Problem VII off Panama, the destroyer USS John D. Edwards (DD-216) suffered a simulated failure in its port main reduction gear. High-speed maneuvering had sheared several teeth from the primary pinion. The engine room filled with the sound of grinding metal before the shaft was secured. The ship was a casualty, dead in the water. A correctly formatted emergency requisition for a new pinion gear assembly was immediately dispatched. The request traveled from the Edwards to its division commander, then to the Blue Fleet flagship, and finally by wireless to the Mare Island Navy Yard. There, the paperwork was processed. The part was incorrectly coded as a routine replenishment item. It was loaded not onto a fast transport for direct delivery, but onto a slow-moving collier scheduled to resupply the fleet a week later at different coordinates. For six days, the Edwards was ruled 'sunk' by exercise umpires. A salvageable warship knocked out of the fight not by enemy action, but by its own supply chain.

The inability to move physical objects was matched by an inability to plan for human casualties. The war games included notional attacks and damage. Commanders were expected to factor in simulated personnel losses. The planners, however, had never fully war-gamed the logistical response to a mass casualty event. During Fleet Problem VIII, a hypothetical bomb hit on the cruiser USS Omaha (CL-4) was adjudicated to have caused over 200 casualties. The ship’s medical officer immediately radioed for a bulk resupply of bandages, morphine syrettes, blood plasma kits, and surgical implements. The request was received by the fleet’s hospital ship, the USS Relief (AH-1). An examination of the exercise reports (After Action Report, Fleet Problem VIII, dated 1927) shows that while the Relief had the supplies, there was no established protocol for a high-speed, at-sea transfer of such a large volume of medical material to a combatant vessel under simulated threat. The request was processed through the standard Quartermaster channel. It became just another requisition number in a long queue. The medical supplies were bundled with general stores and scheduled for the next planned fleet replenishment, a full 72 hours later. Umpires ruled that in that time, the vast majority of the Omaha’s 200 wounded would have died from shock and infection. A direct result of a logistical system that treated life-saving medicine with the same urgency as it did spare engine gaskets.

Rapid Naval Technology Logistical Gaps

The interwar period saw an explosion in naval technology. High-pressure steam turbines, complex radio direction finders, and early fire control computers were being integrated into the fleet. Each new device brought with it a hidden logistical cost that the peacetime supply system was unprepared to pay. The problem was not just a matter of having enough spare parts. It was a matter of having the right, highly specialized parts, and the trained personnel to install them. The speed of technological change consistently outpaced the speed of the bureaucracy designed to support it.

This was a new kind of failure.

Consider the new high-pressure steam turbines installed in destroyers and cruisers of the era. These power plants operated at higher temperatures and pressures than their World War I-era predecessors, enabling greater speeds. They also required specialized lubricants and a new class of replacement parts, like carbon gland seals and turbine blades made of advanced steel alloys. During Fleet Problem VII, the destroyer USS Farragut (DD-348) experienced a simulated failure of its high-pressure turbine seals. The standard requisition system had no specific category for these new components. The supply officer was forced to file the request under a generic 'engine parts' code. The depot in San Diego, following its procedure, sent a box of seals for an older, low-pressure turbine model. The parts were useless. The Farragut, a state-of-the-art warship, was rendered non-operational for days by a simple administrative error rooted in a system that had not updated its own catalogs.

Electronics presented an even greater challenge. The fleet was becoming increasingly dependent on new vacuum-tube radio sets for communication and the first primitive radio direction finders for navigation and intelligence. These devices were delicate. The constant shock and vibration of a warship at sea caused frequent failures of the fragile vacuum tubes (specifically, the Type 45 and Type 80 tubes common in naval receivers of the period). A single carrier like the USS Lexington might carry hundreds of these tubes, each with a limited lifespan. The supply system treated these critical electronic components like light bulbs. They were ordered in bulk and stored in general supply depots. There was no system for testing them before issue, nor were there enough trained radio technicians in the fleet to diagnose and repair the complex circuits. During Fleet Problem IX, multiple ships reported their primary long-range radio receivers were inoperative. The cause was a batch of faulty vacuum tubes that had been damaged in transit. The fleet's ability to communicate was not limited by enemy jamming, but by the fragility of its own technology and a supply chain that could not guarantee the quality of the most basic electronic component.

Preserve the Legacy of Service

History isn't just written in textbooks�it is preserved by family members, researchers, and veterans who ensure the details are never lost. Join our community to bookmark records, build custom reading collections, and share stories.

Community Discussion

Login to Comment