How Afghanistan War soul-searching led to renaming of Navy expeditionary command

On October 1, Navy Expeditionary Combat Command became Commander, Navy Expeditionary Forces. The change was more than a new name. It moved the organization toward the Navy’s type-command structure, with responsibility for developing and overseeing a specific class of forces. This mattered because the Navy was preparing for future fights rather than continuing to organize around the last war.

The former command had handled many different jobs during the Global War on Terror. It supplied personnel and units to U.S. Central Command, trained sailors to fill temporary personnel gaps, supported specialized billets, and mobilized reservists. Its assets came from both active and reserve components with different reporting arrangements.

The rebranded organization will continue supporting expeditionary forces as key enablers that mobilize, sustain, and move the fleet forward. It will also work alongside efforts involving autonomous systems, including forces and tools designed for austere maritime environments.

A type command, or TYCOM, is a Navy organization responsible for a particular class of sailor or capability. Its main duties include providing training and overseeing maintenance and management for unique weapons systems. That focus helps build consistent readiness across forces with similar missions or equipment.

An ordinary command has a broader job. It can act as a wing of a military service and perform many functions, including deploying forces. Navy Expeditionary Combat Command operated in that wider way during the Global War on Terror. It gathered and provided forces, filled personnel gaps, trained sailors, and mobilized reservists.

Renaming the organization made its structure better match capabilities it had already developed. The Navy concluded that expeditionary forces would remain important in future combat. A type-command arrangement gives those forces a standing focus on training, equipping, maintenance, and management instead of organizing mainly around one war’s immediate demands.

The article does not provide a numerical count of the different personnel categories or capabilities the former command brought together. It does establish that the organization managed both active and reserve components. Those elements did not share one organizational structure, which made the command unusually broad.

Its work included providing individuals or units to U.S. Central Command that were not afloat, flying, or subsea. During the Global War on Terror, it trained sailors to plug temporary personnel shortages, filled billets requiring specialized skills, and mobilized reserve service members. It also helped ensure deployed forces met specific requirements.

That range explains why Andros described the command as a “Swiss-army knife.” The phrase captures variety, not a stated number. The later redesignation did not erase those capabilities. Instead, the Navy placed them within a type-command framework focused on preparing, sustaining, and managing expeditionary forces for future operations.

Navy Expeditionary Combat Command was formed in 2006 to bring together disparate Navy components. Its original task was to consolidate and manage forces spread across different command-and-control arrangements. These forces were expeditionary assets that did not fit neatly into the Navy’s afloat, flying, or subsea categories.

The organizational problem was significant. Some active and reserve units reported directly to U.S. Fleet Forces Command or U.S. Pacific Fleet. Others fell under type commands. Because the assets had different structures and reporting lines, the Navy needed an organization that could coordinate and manage them as a broader group.

The Global War on Terror then gave the command an expanded mission. The joint force needed specific capabilities for combat operations, and the Navy decided this command could provide them. It supplied forces to meet requirements from the U.S. Central Command commander, turning a consolidation effort into a flexible operational resource.

The wars’ broader military campaign created an urgent demand for specific forces supporting combat operations. The Navy decided its expeditionary command could provide people and units to U.S. Central Command. These forces were not afloat, flying, or subsea, but they had capabilities the CENTCOM commander specifically requested.

The command responded in several ways. It trained sailors who could temporarily plug personnel shortages. It filled billets that required specialized skills. It mobilized reserve service members and supplied units or individuals for deployed operations. These tasks made the organization a flexible source of force generation rather than a narrow administrative headquarters.

Andros compared the result to a “Swiss-army knife” because the command handled many different needs. That wartime flexibility also shaped the Navy’s later review. After the Afghanistan War ended, leaders examined whether those capabilities remained useful and concluded expeditionary forces would still help mobilize, sustain, and move the fleet forward.

The redesignation changes the command’s center of gravity. Instead of mainly assembling capabilities for the requirements of a particular war, Commander, Navy Expeditionary Forces will operate as a type command. Its work will emphasize training, maintenance, management, and preparing a specific class of expeditionary forces.

The shift builds on capabilities the command already proved during the Global War on Terror. It had coordinated active and reserve components, supplied specialized personnel, trained temporary replacements, and mobilized forces. Under the new structure, those functions can support a continuing readiness system rather than an improvised wartime response.

The Navy expects expeditionary forces to remain key enablers for mobilizing, sustaining, and moving the fleet forward. The command will also work with efforts to research and field autonomous weapons systems. The article does not specify every operational change, but it presents the new status as a closer match for future combat needs and emerging maritime technologies.

Unmanned systems are not simply placed in the fleet and left alone. People must man, train, and equip the forces or tools that operate them. Those systems may be inserted into austere maritime environments, where expeditionary forces are designed to mobilize capabilities and support operations away from established infrastructure.

The Navy’s Robotic and Autonomous Systems Warfighting Development Center is headquartered at Joint Expeditionary Base Little Creek-Fort Story. That is also where Navy Expeditionary Forces is based. The shared location supports a natural institutional connection between expeditionary force development and autonomous technologies.

Andros said the way robotic and autonomous systems are forming resembles expeditionary force generation more than the work of a ship or submarine. The partnership with Christopher Miller, the Portfolio Acquisition Executive for Robotic and Autonomous Systems, reflects that fit. The Navy also links expeditionary forces to expanding seabed and subsea warfare capabilities.