MARINE AIR CONTROL SQUADRON-4 (MACS-4): From Moonman to Vicesquad *– the Marine Corps’ deployment of the first internet-like command and control system in modern warfare.
*Tactical call signs used during the Vietnam War.
A Navy ship departed San Diego on 13 May 1967, for Da Nang, Vietnam. On board was a squadron of Marines from Marine Air Control Squadron-4 (MACS-4) with a singular cargo. They were embarking on a seminal event in modern warfare history for both the Marine Corps and the U.S. military. They were to establish a tactical air operations center (TAOC), and deploy in combat the first tactical data system for air command and control, which would allow the Navy and Air Force air control systems to connect with each other automatically. The strategic and tactical consequences of this were enormous. For the first time, combat pilots from the Marine Corps, Navy, and Air Force would have instant control and communications with minimal-to-no voice commands. The results were increased security and safety, efficient de-confliction of airspace, enhanced identification of friends from foes, and real-time feedback for senior air decision makers. It was a conversion from the grease pencil command and control to the digital world of near real time. Modern command and control warfare was spawned by these initiatives. Air planning, execution, surveillance, and airspace management took on dimensions never dreamed of before.
The site chosen for the TAOC was Monkey Mountain, overlooking Danang airfield, in the northern sector (I Corps) of the Vietnamese theatre. On this site already were semiautomated Air Force command and reporting post (CRP) and a Marine Corps Hawk Battery. It was felt that this site provided optimum radar coverage far into North Vietnam and had a reasonable zone of security for the exposed radar and communication systems. The major concern was attacks from Russian MIGs and other Vietnamese aircraft. In addition, with all the air sorties and ground operations, coordination of the airspace was an imperative.
The team assembled by the Marine Corps was among the best and brightest in the community and exceeded the normal manning for its predecessor manual unit. The Marine Corps had a great investment in this enterprise and a lot riding on its success. The challenge for this unit was that there was no written handbook or concept of operations on how to use these automated systems. In addition, the Air Force was the senior air command and control system and had misgivings about the Marines. It seemed likely that the Marines would be relegated to a watch/listening post; and that was that.
The Marines had a manual air command and control system in the south, at Chu Lai Air Base (Moonman). They basically tracked and kept inventory of Marine air missions in I Corps and North Vietnam. All planning, coordination and prime tactical air direction was with the Air Force CRP on Monkey Mountain. It was in this subordinate role that MACS-4 entered the picture.
After a few weeks on the air, the Air Force personnel visited the site to see the new equipment and make good neighbors. They quickly realized the incredible capabilities of both the controllers and the new system. Of major consequence also was the capability to integrate/automate the Navy Air C2 (Navy Tactical Data System) system with theirs. Consequently, all three services now had near-real-time access to a common picture of the air space. This was revolutionary.
We started operations at a measured pace: First, picking up tracking of Marine air from Chu Lai, and monitoring the other air operations of our Air Force and Navy air centers. As more senior commanders from the other services visited our site we were not only given a more active role, but also began to rewrite the book on joint air operations in combat. We easily impressed the Air Force, who needed our support due to increased air tempo.
By August 1967, we were in the driver’s seat, with full-speed ahead. We never hesitated, and the grit of our controllers and operators became a surety for all who entered our sphere of control. We were assigned combat air patrol missions, which were the prize for an air controller: the dream of engaging a MIG. We coordinated with the air support squadrons and their radar bombing operations. We worked with air traffic control to facilitate the take-off and landings at all times of the day and night; under some of the most severe weather conditions. We calibrated all potential hostile contacts with our HAWK missile battery. We constantly update the Tactical Air Command Center with relevant, critical mission data. Our newly assigned tactical name—Vicesquad—became a favorite go-to for pilots and other agencies. Any helicopter, plane, jet, gunship, tanker, bomber—we built it and they came. They knew we had their backs and that we were true professionals who knew our business. We had the keenest of eyes and ears. Even Hanoi Hannah, the North Vietnamese broadcaster with her sultry voice, mentioned us on the air.
MTDS proved its worth, and then some. The Marine Corps had an advantage of it being developed years after the Air Force and Navy systems. We took advantage of the latest technologies and shortcomings, and went beyond. The best analogy I could use is we went directly to the Iphone from a clam shell. We had the internet, phone, and computer all in one. The Marine Corps finally arrived at the forefront of tactical data systems. The dawn of the modern battlefield was upon us. However, the first chapter was written by MACS-4 and all the pioneers who went to Vietnam on that early May morning in 1967. Their names are many, but live on in the Marines of today who develop and operate our new systems.
MTACCS: From Requirements to Reality
The success of MTDS encouraged the Marine Corps to proceed with the development and deployment of the other systems of MTACCS. As noted, MTACCS was a concept whereby all the combat functions of the MAGTF would be automated and integrated. Battlefield automation was tested, proven, and here to stay. Requirements and system attributes were developed for the other combat areas as rapidly as possible. The Marine Corps saw the need to establish organizations that could do this. One principal one was the Marine Corps Tactical System Support Activity (MCTSSA). It started out supporting the system maintenance and upgrades to MTDS. It also became an assembly point for officers, enlisted, and civilian contractors who had expertise in both computer-based technologies and relevant operational expertise in the various combat arms.
Initially, a test bed was set up to evaluate requirements and technologies for automated field artillery fire support. This brought together the ground and air Marines for the first time for tactical data system development. The Marine Corps also established liaison with the other services for joint development. The Marine Air Ground Intelligence System (MAGIS) was a major joint effort, with the Air Force as lead program office and the Navy another participant. While this system was never put into operations, it did provide valuable insights into systems’ development and operational issues. [The author was assigned to this office for three years.] Other developments were underway to automate the tactical air command center, the Marine air support squadron, and Marine air traffic control.
Perhaps the most significant event occurred when the Marine Corps Research and Development Command (MCRDAC) was formed in the late 1980s. This brought together the various itinerant MTACSS developments. A MAGTF command and control office was established to coordinate and leverage the various activities. In addition, the Marine Corps Combat Development Command (MCCDC) was established to harmonize combat command and control requirements. This tandem team facilitated the development and fielding of MTACCS. The architects of MCRDAC used this reorganizational opportunity to push for common hardware and software. Software was the driving force in system costs. We created an agreement with the Army, Navy, and Air Force to adopt a common technical architecture for C2 systems. This was possible because of the advances in open software architectures. This effort later was branded the Department of Defense Information Infrastructure Common Operating Environment (DII COE), and was administered by the Defense Information Systems Agency. All future C2 systems were mandated to use this for their development; and current systems tried to modify their current software to these specifications. The Marine Corps was the godfather of this initiative, which was both initiated and brought to fruition with a lot of political engineering and luck.
Two other seminal events were when we joined the Army in developing and fielding a common laptop computer for the battlefield; and when we initiated a short development cycle, called the Field Development System. This latter process enabled us to have a short cut to purchase off-the-shelf hardware and software, and test it with operational forces during select annual exercises.
This history ends in April, 1992 (the author’s retirement). I am not up to speed on what happened afterwards, and will leave that part of the history to those who were there: trusting others will continue the narration of the Marine Corps pioneering role in this vital arena.
I started my career as a participant in pioneering tactical data systems, and had the privilege of ending it as one. I witnessed first-hand the evolution and maturation of automation and its significant impact on our missions. I had the honor to work with some of the best and brightest in all the services, and have the confidence that our Marine Corps will always be at the forefront of innovation. Subsequent developments will be written by the best and brightest Marines. Semper Fi!
