If you do NOT see the Table of Contents frame to the left of this page, then
Click here to open 'USArmyGermany' frameset

Command & Control
32nd AAA Brigade / Army Air Defense Command

Looking for more information from military/civilian personnel assigned to or associated with the U.S. Army in Germany from 1945 to 1989. If you have any stories or thoughts on the subject, please contact me.

AIRCENT Air Defense (1960s-70s)

4th ATAF C&C
Missile Control Centers

ADA Communications
BOC Commo Check

Related Links

10th AAA Gp/ADA Bde

69th AAA Gp/ADA Bde

94th AAA Gp/ADA Bde

108th ADA Bde

This page is still "under construction" and will undergo many changes and additions in the next few weeks.

However, comments, suggestions, and corrections are very much appreciated!!! This is a highly complex but very interesting topic, but with your help I feel we can put something together that is both accurate as well as informative. I am looking for a lot of help from any vets who were part of this elaborate air defense network.
AIRCENT Air Defense - 1960s and early 1970s
(Source: various sources)

AAFCE Emblem

  The integration of air defense capabilities within NATO was formalized in 1954 under "MC 54/1" (Directive of the NATO Military Committee on the Integrated NATO Air Defense System in Europe) and approved by the Military Committee (the highest military authority within NATO) in December 1955. The concept was based upon four air defense regions (ADRs) with coordinating authority given to SACEUR.

The Central Region (covering the area of the BENELUX countries, France - until they pulled out in 1966/67 - and the Federal Republic of Germany) fell under the operational command of CINCENT (Commander in Chief, Central Europe). AIRCENT (Allied Air Forces Central Europe), the air component responsible for the air defense mission in the Central Region, provided central direction and control for the air defenses through the co-ordination of two subordinate headquarters: Second Allied Tactical Air Force (2ATAF), based at Mönchengladbach, which covered the northern part of the region, and Fourth Allied Tactical Air Force (4ATAF), based at Ramstein Air Base, which was responsible for the southern area.

The air defense assets that made up the integrated air defense system (that would later evolve into the very extensive NATO Air Defense Ground Environment (NADGE)) consisted of:
- command and control systems (operations centers and communications networks)
- early warning and ground control intercept radar installations
- fighter interceptor aircraft
- surface-to-air (NIKE and HAWK) missile units.

(NOTE: At a later point, Boeing E-3A AWACS aircraft were added to the NATO Early Warning System.)

(Source: Die Luftwaffe 1950 bis 1970: Konzeption, Aufbau und Integration, 2006)

Air Defense Missile Belts
The establishment of a missile belt was the most important step in the implementation of the MC 54/1 decision document.

In June 1960, SACEUR approved the establishment of a second missile belt with 26 HAWK battalions. The second missile belt was to be deployed about 15-20 kilometers in front of (to the East of) the NIKE missle belt.

SHAPE defined in 1963 the air defense role of the NIKE and HAWK systems - the NIKE was responsible for the high and medium altitude air defense; HAWK for the low and medium altitude air defense.

Operated an Air Operation Centre

Operated an Air Operation Centre

2nd ATAF
In April 1960, the Belgian sector (SOC at Glons?) and Dutch sector (SOC at Nieuw-Milligen?) were reassigned to SOC Uedem and SOC Brockzetel, respectively, as sub-sectors.

Offensive Forces
2 TOCs (Tactical Operations Center) -- at Goch (belgian, british and german assets) and Sundern (dutch, british and german assets)

Defensive Forces
2nd ATAF established its ADOC (Air Defense Operations Center) at Uedem (in 1958?).

Air Defense Deputy of 2nd ATAF is commander of the ADOC. The ADOC is an element of the Joint Command Operations Centre, 2nd ATAF.

There are two Allied SOC's (Sector Operations Center) in 2nd ATAF: Brockzetel (Allied SOC-1) and Uedem (Allied SOC-2).

In early 1960s, the Early Warning Radar Station was at Auenhausen - it reported to SOC at Uedem.

In 1968, Allied SOC-I (Brockzetel) controls three NATO air bases: Wittmund, Germany (71st Jagdgeschwader - Fighter Wing, F-104G unit); Soesterberg, the Netherlands (32nd FIS, USAFE, F-102 unit); and Leeuwarden, the Netherlands (322 Sqn and 323 Sqd, both RNAF F-104G units).

Den Helder radar station with Elliott Firebrigade Mk 2 computerized control system is an important element of the NATO-wide control and reporting network
(Nieuw Milligen) radar station - non-computerized - callsign BANDBOX, is a stand-by operations center in eastern Holland

4th ATAF

Offensive Forces
3 TOCs -- at Kindsbach (17th AF USAFE); Metz (1st Air Div RCAF); and at Drachebronn, France (French assets)

Defensive Forces
Until (1960), 1st Air Div in Metz operated a SOC that was responsible for Sector 1 of 4th ATAF (Lorraine Region, France and Hessen, Germany)

The SOC at Drachenbronn was responsible for Sector 2 of 4th ATAF ( and Rhineland-Palatinate, Baden-Württemberg and Bavaria).

In early 1960s, the Early Warning Radar Station was at Burglengenfeld - it reported to ADOC at Kindsbach.

The SOC at Metz was replaced by a SOC (Allied SOC-3) at Langerkopf (1960 - 1963) and then the SOC (Allied SOC-3) in Boerfink (1963 - ).

The SOC in Drachenbronn (SOC-4) became a French national SOC when that country pulled out of the military command of NATO in 1966, leaving the AIRCENT Region with only three SOC's.


86th Air Division (Defense)
Gaggle Plaque


The 32d Antiaircraft Artillery Brigade was under the operational control of the 4th Allied Tactical Air Force and provided direct air defense support to Central Army Group units.

During the period in question, the Brigade consisted of the following units:
94th Arty Gp (NIKE)
10th Arty Gp (HAWK)
69th Arty Gp (HAWK)

NATO air defense forces were required to be on a high state of alert and readiness to respond, immediately and effectively, to a massive Warsaw Pact air attack. A major portion of the forward-deployed HAWK batteries were required to be ready to launch an air defense missile almost immediately, or in a few minutes. The more rearward-deployed Nike Hercules fire units were under only slightly longer "ready to fire" time requirements, but also only of a few minutes.

94th Artillery Group - AADCP

10th Artillery Group - AADCP (can anybody provide some detail on location and mission?)
69th Artillery Group - AADCP


4ATAF Patch

12th Air Force Patch

17th Air Force Patch

86th Air Div Patch

501st Tac Con Gp Patch

601st TCW Patch

601st AC&W Sqd Patch
602nd AC&W Sqd Patch

603rd AC&W Sqd

604th AC&W Sqd
606th AC&W Sqd Patch
615th AC&W Sqd

615th AC&W Sqd

616th AC&W Sqd Patch

616th AC&W Sqd Patch

152nd TCG NYANG Patch

101st AC&W Sqd MAANG Patch

123rd AC&W Sqd OHANG Patch

32nd FIS Patch (1)

496th FIS Patch

525th FIS Patch

526th FIS Patch
(1) courtesy www.slobberinwolfhounds.com (32nd TFS web site)

NIKE-HERC Command and Control
General Information
(Source: Wayne Scarpaci, HHB 69th ADA Gp, 1968-70)

10th Arty Gp Ernst Ludwig Kaserne, Darmstadt Cricket
? ADA Bn Cork  
? ADA Bn Chain  
? ADA Bn Caisson  
? ADA Bn ???  
69th Arty Gp Emery Bks, Würzburg Cocktail
AADCP Cocktail Forward
? ADA Bn Cat prob 6/52nd ADA
? ADA Bn Cheryl
? ADA Bn Challenge prob 4/57th ADA
? ADA Bn Charcoal
94th Arty Gp Kapaun Ksn, Kaiserslautern Cinnamon
AADCP Hill 479

(Source: 32nd AADCOM The News, Special Orientation Edition, October 1981)
'Invisible' units protect skies, an article on the MCC's at Boerfink and Lauda has been moved to the Missile Control Centers Page, Air Defense section.

AN/MSG-4 Missile Monitor
(Source: ROTCM 145-70, Branches of the Army, Oct 1963)
Fire Distribution System AN/MSG-4 (Missile Monitor)

The Missile Monitor is designed for employment with the field army to integrate the field army air defense with the air defense system operated by the Air Force. It is a fully mobile fire distribution system utilizing standard military vehicles.

Missile monitor provides facilities for an AADCP normally established at group level, and incorporates up to four battalion fire distribution systems. Designed for use with surface-to-air missile systems in the field army, it provides a rapid and accurate exchange of information between AIRCENT command elements and missile batteries. Information on the location and identity of aircraft is continuously collected, displayed at the AADCP, and disseminated to the integrated elements. Each fire unit transmits operational status to the AADCP, where it is displayed. Information is automatically exchanged with adjacent AADCP's and received from tactical air force units. The air defense commander observes the overall air defense situation, directs fire distribution, and supervises fire unit operations as required. Battalion fire distribution systems may be employed independently in small air defense areas.

The AADCP operations room contains display consoles used for surveillance, tracking, and tactical monitoring operations. Electronic computers update, store, and provide continuous target data to these consoles and to the integrated missile batteries. The electronic display includes the location and identity of all aerial objects in the defense area and those targets selected for attack by each fire unit.

(Source: US Army Air Defense School, Student Outline, March 1966)
(1) Purpose. A fire distribution system makes it possible to observe and influence the entire air battle scene from the widest viewpoint so separate actions of numerous batteries can be supervised and unified into an integrated defense. The purpose is to bring about a balanced and timely distribution of fire agains any raid, in a logical order of tactical priority, and thereby achieve an optimum kill with the given weapon's capability.

(2) General description of the AN/MSG-4 fire distribution system (Missile Monitor). The AN/MSG-4 is a mobile fire distribution system designed for the use with the field army to control the fire of Nike Hercules and Hawk guided missile systems.

The AN/MSG-4 is composed of two basic subsystems, the AN/MSQ-28 (AN/MSQ-56) subsystem located at group or brigade level, and the AN/MSQ-18 (AN/TSQ-38) subsystem located at battalion and battery levels.

(3) AN/MSQ-18 (AN/TSQ-38) subsystem.

(a) Operations central (OC). The OC is the tactical command post of the air defense battalion command. The OC is capable of either monitoring the engagement or actually making assignments of targets to its batteries.

(b) Coder-decoder group (CDG). The CDG is located at each of the batteries. Information between elements of the AN/MSG-4 is exchanged over an automatic data link (ADL) in a coded form (digital). The CDG decodes the digital data coming to the battery and changes the information to a form that can be used by the guided misslle system. Information being sent from the guided missile system is converted to coded form (digital) for transmission up to higher echelons (battalion and group).

(4) AN/MSQ-28 (AN/MSQ-56) subsystem.

(a) The major components of the AN/MSQ-28. The major components of the AN/MSQ-28 are the AN/MPS-23 frequency-scan radar, the radar data processing center (RDPC), and the weapon monitoring center (WMC). The two research and development systems are the only systems still carrying this nomenclature. All production models have had design improvements changing the nomenclature to either AN/MSQ-28B or AN/MSQ-56. These design improvements have included modification of the radar, changing its nomenclature to the AN/MPS-23A frequency-scan radar.

(b) AN/MPS-23 or AN/MPS-23A frequency-scan radar. The AN/MPS-23 provides the Missile Monitor with target detection. The radar is unique in that it provides not only range and azimuth, but also elevation angle. As the antenna rotates mechanically in azimuth, it scans electronically in elevation. The elevation capability of the AN/MPS-23 eliminates the need for a separate radar to determine height. Identification, friend or foe (IFF) equipment is also provided with the radar. An ECCM console in the radar enables the operator to determine which ECCM feature of the system is being the most effective during an ECM environment and enables the operator to transfer the best radar response to the RDPC.

(c) Radar Data Processing Center, the RDPC provides initial display of targets, a means of interrogation, and automatic tracking of targets. Tracking is accomplished at six detector-tracker (DT) consoles in the RDPC. Height data are observed on two range-height indicator (RHI) consoles. The position of the target in the X and Y coordinates, the identification, and the raid size are entered into a memory storage at the DT consoles. Height (H) is entered at the RHI consoles. Information entered is carried by ADL to
the WMC and entered into a second memory storage.

(d) Weapon Monitoring Center. The WMC provides the group commander with immediate presentation of the tactical situation at all times. All information entered into memory storage from the RDFC is available in symbolic or read-out form at the weapon monitoring consoles. Battery status to received from the batteries and entered into the memory storage. The WMC can accept data from remote sources for early warning purposes. The group commander can make assigments from the WMC to the batteries.

(5) Block organization and data flow.

(a) The AN/MSQ-28 is an integrated system providing the facility to the air defense commander to collect information on all targets in his area of defense, process and store the target information, disseminate information or target assignments to fire units, and to monitor the status of all fire units.

(b) Information in three dimensions is provided by the AN/MPS-23 radar over cable to the RDPC. Processed information is carried from the RDPC to the WMC over the ADL. Target assignments, reference messages, and battery status information are exchanged through each operations central to the fire unit over the ADL.

(c) The WMC can receive target information from remote sources, which could be from the tactical air force (TAC) or adjacent Missile Monitor systems.

(6) Methods of operation. Missile Monitor may be operated in six different switch-selected methods of operation. These are essentially different ways of channeling ADL information. Three of these methods of operation are used in the tactical employment of the system, two are used during system emplacement and for test purposes, and one method is used for emergency operation.

(a) Normal method (tactical). In the normal method of operation all commands originate at group level. The commands are transmitted aver the ADL through the battalion operations central (Bn OC) to the fire units at the battery. Status information of the fire units will be transmitted over the ADL through the Bn OC to the WMC at group level. Reference tracks may be received from the Bn OC over the ADL.

(b) Sector method (tactical). When a Bn OC is placed in the sector method of operation, all commands will originate at the Bn OC for all fire units integrated with it. Status information from these fire units will be transmitted over the ADL to the Bn OC and be passed on up to the WMC for monitoring purposes. The WMC at group can transmit reference information on tracks to the Bn OC and batteries while it is in the sector method of operation. The group commander can place a battalion in the sector method of operation
by changing switch positions. It is possible to have any number of Bn OC's operating to the sector method of operation while the remaining Bn OC's may be operating in the normal method of operation. The tactical situation will dictate the method of operation.

(c) Independent method (tactical). In the independent method of operation, there is no ADL between the AN/MSQ-28 at group and the AN/MSQ-18 or AN/TSQ-38. All commands will originate at the Bn OC, and all status information returning from the batteries over the ADL will terminate at the Bn OC.

(d) AADCP survey method (test). The AADCP survey method is a test method in which the WMC will transmit a message of target position continuously so all elements may check for accurate location with respect to the AADCP.

(e) Battery survey method (test). The battery survey method is a test method in which one of the batteries within the AN/MSG-4 system transmits target positional information continuously so all elements can correlate position.

(f) Emergency method (emergency use). This emergency method is used if certain components of the WMC become inoperational and the RDPC data are routed to the Bn OC's and batteries. The emergency method would permit the transmission of target information over the ADL and commands by voice communication to the OC's.

(7) Operating personnel and duties (officer and enlisted).

(a) The platoon leader is responsible to the Army air defense commander for all activities of the Army air defense command post. The platoon leader is normally a major.

(b) The operations officer, being senior on each shift, will perform duties of the Army air defense operations officer (AADOO), be the shift supervisor, and the tactical director of the air defense operations to the weapon monitoring center. He will monitor the actions of other operations personnel and perform additional duties prescribed by the platoon leader. There are normally four operations officers assigned, one for each shift. Rank: Captain.

(c) The tactical directors, working in shifts of four each, operate the four weapon monitoring consoles. Each console is associated with one of the four battalions normally assigned in a defense. Within the limits of SOP they will make specific action assignments and monitor fire unit action. There are normally sixteen tactical directors assigned, four for each shift. Rank: Lieutenant.

(d) The surveillance and entry (S&E) officer, being the senior officer on shift in the RDPC, is responsible to the operations officer for the RDPC operations. He operates a DT console and performs additional duties prescribed by the platoon leader. There are normally four S&E officers, one for each shift. Rank: Lieutenant.

(e) The section chief is the senior noncommissioned officer assigned to each shift and performs supervisory duties under the direction of the operations officer. He is directly responsible to the operations officer for march order and emplacement. He operates a DT console. There are normally four section chiefs assigned, one for each shift. Rank: E-6.

(f) The senior fire distribution operators operate the DT console in the RDPC and perform additonal duties prescribed by the section chief. There are normally four senior fire distribution operators, one for each shift. Rank: E-5.

(g) The fire distribution operators operate the DT console in the RDPC and perform additional duties prescribed by the section chief.

(h) Target trackers act as ECCM operators in the radar equipment trailer of the AN/MPS-23 radar. They also perform additional duties prescribed by the section chief. There are normally four assigned, one for each shift. Rank: E-4

(i) Plotter-tellers maintain a manual target plotting system to provide an alternate means of reporting air defense intelligence. They also operate system consoles and perform additional duties as prescribed by the section chief. There are normally three assigned. Rank: E-4.

(j) Height-finder operators operate the RHI console in the RDPC and perform additional duties as assigned by the section chief. There are normally eight assigned, two for each shift. Rank: E-5.

(8) Power requirements.

(a) Ten trailer-mounted generators are furnished for power to the AN/MSQ-28 equipment, but five of these generators serve as spares.

(b) The AN/MPS-23 radar requires a 60-cycle, 100-kilowatt generator.

(c) The RDPC and the WMC each require a 60-cycle, 45-kilowatt generator and a 400-cycle, 45-kilowatt generator.

(9) Trailer-mounted electronic shop AN/MSM-34. There are three electronic shop trailers with the AN/MSQ-28 equipment. Each major component of the AN/MSQ-28 has a trailer to house spare parts and test equipment for maintenance purposes.
WMC Console
D-T Console
RHI Console

(Source: US Army Air Defense School, Student Outline, March 1966)

Technical note:  ADL came in two varieties:  PCM (Pulse Coded Modulation) and FSM (Frequency Shift Modulation); these were (roughly) analogous to "pulse" and "tone" dialing modes on the telephone, respectively.... Also, remember that we (in the MSG-4 system) had "pushbutton phones" in the mid-1960s!  When did they come into common civilian use?)
AN/MSG-4 Cabling and Communications

(1) Basic types of communications.

(a) Automatic data link. ADL is used for the transmission of electronic messages throughout the fire distribution system. It can be transmitted by either radio or cable.

(b) Voice communications. Voice communications are used for the passage of tactical information such as equipment status and after action reports. Voice communications are also used as a backup to AOL.

1. Local and administrative lines. The local and administrative lines are used for administrative, maintenance, and supply purposes.

2. Hot loop nets. The hot loop nets are furnished on a full-time, high priority basis and are used for the exchange of tactical information such as condition of readiness, action status, and progress of mission. There are three hot loop nets available in the AN/MSG-4 system: group, battalion, and automatic.

a. Group hot loop. The group hot loop is used for the simultaneous exchange of information between the weapons monitoring center (WMC), radar data processing center (RDPC), and the four battalions.

b. Battalion hot loop. There are four battalion hot loop sets, each connecting one battalion to the WMC via the Army area communications system. The RDPC is not connected in the battalion hot loop.

c. Automatic hot loop. The automatic hot loop is automatically initiated during a RED air defense warning. It connects the operators telephone units at console No. 1 through No. 4 in the WMC to the four battalion hot leaps, respectively.

3. IRR nets. There are five IRR nets provided for use on a full-time, high-priority basis. They are used for the exchange of intelligence and radar reporting information such as weapon supply and early warning. The IRR nets avallable are the group IRR net and the battalion IRR net.

a. Group IRR net, The group IRR net is one in which the WMC, RDPC, and all four battalions are tied together to form an overall IRR net. The RDPC has priority over the WMC because it provides and uses the majority of information transmitted via the IRR nets.

b. Battalion IRR net. There are four individual battalion IRR nets, each connecting one battalion to the RDPC.

(2) Console communications facilities. The console communications facilities consist of telephone instruments, transmit control circuits, operator's telephone unit, and telephone connecting station.

(a) Telephone instruments. The telephone instruments (headset-handset) consist of a receiver, microphone, and hand-operated transmit control switch.

(b) Transmit control circuits. The transmit control circuits consist of a hand-operated or foot-operated switch used to energize the microphone.

(c) Operator's telephone unit. The operator's telephone unit amplifies all incoming speech signals, provides an audible indication of incoming calls, and connects the telephone instruments to the battalion hot loop during a RED air defense warning.

(d) Telephone connecting station. This is the connecting link between the controller's telephone unit and the voice communications lines.

1. Initiating a call.

2. Receiving a call.

(3) State-of-alert function. The state-of-alert circuits receive the audiofrequency signals indicating air defense warnings (RED, YELLOW, or WHITE) and provide visual indications. In addition, these circuits supply digital air defense warning data for transmission by ADL to the fire units,

(a) Audiofrequency air defense warning signals. These signals are sent out by the air defense artillery operations officer in the WMC.

(b) Digital air defense warning data. This information is supplied to the battalion ADL input-output buffer for transmission to all units in the AN/MSG-4 system.

(4) Army Area Communications System. Radio and wire systems may be used to provide communications circuits for voice and automatic data transmission.

(a) Radio. Multiplex radio facilities may be provided for simultaneous communication in two directions,

(b) Wire. The wire circuits used may be the standard WD-1 field wire or the Spiral-4 cable,

(Source: US Army Field Manual FM 44-95, AIR DEFENSE ARTILLERY EMPLOYMENT, NIKE HERCULES, April 1968)

5-1. General
FM 44-1 presents the detailed principles of command and control of theater air defense operations. A detailed listing of Army air defense officer functions, command relationships, and typical command arrangements are also included.
5-2. Field Army
Nike Hercules battalions and batteries required for defense of the field army are retained at field army level under the command of the field army ADA organization (normally an ADA brigade). Nike Hercules units are normally further assigned to an ADA group directly subordinate to the ADA brigade. Nike Hercules is not normally further assigned below field army level.
5-3. General
Key control elements include control of unit assignments, mission assignment, and control of fires. Control is exercised in accordance with theater air defense policies and procedures, and by provision of liaison and communications.

5-4. Control of Assignments
Assignments of Nike Hercules units are made in accordance with established priority lists for air defense. A commander receiving an assignment of these units may assign them as necessary to accomplish his mission. Any limitations placed on the receiving commander must be defined in the terms of attachment or assignment.

5-5. Mission Assignment
Nike Hercules unit assignment or attachment carries with it a mission to provide air defense, or for, the force, unless specified otherwise. A force receiving a Nike Hercules unit allocation further assigns missions of defense of
specified vital areas or force elements, subject only to limitations which may be included in the assignment or attachment order. Because the air defense means made available are generally limited, the force commander should prescribe priorities for air defense of his force units or installations.

5-6. Control of Nike Hercules Fires
a. Concepts.
(1) The right of self-defense against hostile air and ground attack is never denied. Commanders at all echelons have the responsibility to take whatever action is required to protect their forces and equipment against enemy air attack. Such action will be governed by rules and procedures established by the air defense commander. If emergency action deemed necessary is contrary to established rules, it should be carefully weighed for its effect on the operations and safety of other friendly forces, and, if taken, reported to the appropriate commander at the earliest practicable time.
(2) Nike Hercules units normally make air defense engagement decisions based on the rule that aircraft identified as hostile will be engaged. This rule may be changed by higher echelons to allow relatively unrestricted engagement or to impose increase fire restrictions. This concept for control of fires is dependent on provision of clear and detailed air defense rules covering the items discussed in b through f below, and communications to allow higher echelons to modify the air defense rules if the situation demands.

b. Conditions of Readiness and Air Defense Warning.
(1) Conditions of Readiness. Conditions of readiness are the means used by specified authorities to maintain air defense at a state of preparedness compatible with the real or apparent imminence of attack. The terms, defense readiness condition (DEFCON) and defense readiness posture (DEFREP), are frequently used in relation to conditions of readiness. In response to each condition of readiness, the Army ADA commander prescribes a required state of alert for each ADA unit under his command (appendix B).

(2) Air defense warning. Air defense warnings are normally issued after the air defenses have reached their highest conditions of readiness and represent the ADA commander's evaluation of the probability of air attack. The warnings are: RED, attack imminent or in progress; YELLOW, attack probable; and WHITE, attack not probable. The conditions of readiness ((1) above) and the air defense warnings serve as a basis for implementation of the air defense rules and procedures of the regional ADA commanders. These rules for engagement and procedures are established in operation orders or SOP (app B).

c. Rules for Engagement.
(1) Rules for engagement are promulgated by the area ADA commander to define, as a minimum, the responsibilities, procedures, and criteria for aircraft identification and engagement in consonance with the theater alert system.
(2) The following rules for engagement are considered typical for Nike Hercules operations:
(a) Conditions short of war -- engagements are conducted only in self-defense or as ordered by designated ADA commanders.
(b) Wartime -- engagements are conducted in accord with the prevailing weapon control status (d below) and the hostile criteria (f below).

(3) Implementation of the rules by Nike Hercules requires that determination be made of the friendly or hostile character of each aircraft; therefore, the rules are based on use of reliable identification criteria.

d. ADA Weapon Control Status. Each ADA weapon control status indicates the degree of air defense fire restriction imposed upon Nike Hercules units. A "normal" wartime status for Nike Hercules units should be specified in the rules of engagement. Authority to change ADA weapon control status, if any, should also be specified.

(1) Weapon free. Fire at any aircraft not identified as friendly. Under this status, "unknowns" may be engaged. An "unknown:" is an aircraft whose identity has not been established.

(2) Weapon tight. Fire only at aircraft positively identified as hostile. Theater rules for engagement will specify exact criteria for declaring an aircraft hostile when operating under this status. Examples of hostile criteria are presented in f below.

(3) Hold fire. Do not fire. This status may be used to impose restrictions on a defense as a whole. The status is normally transmitted as follows: "All units -- hold fire." Hold fire may also be given for certain indicated flights (e(1) below). BCO actions are identical in both cases.

e. Special Control Instructions. Other weapon control instruction pertaining to specific engagements or actions may be prescribed by the AD commander (who establishes rules for engagement) in controlling the Nike Hercules system. Typical terms are:
(1) Hold fire. Hold fire is used to protect friendly aircraft. This term, as defined in Army regulations, should not impose a blanket restriction on an entire area and all flights therein, but only on certain indicated flights. This status should only be invoked if safeguards over and above those inherent in the "normal" weapon tight status are required. The special control instructions are normally transmitted as in the following example: "Fire unit 68 -- hold fire -- track 97." When received by a BCO, it means --
If you have not fired:
• Do not fire.
• Cease tracking.
  If you have fired:
• Destroy missile immediately.
• Cease tracking.

(2) Cease fire. Cease fire is used to preclude simultaneous engagement of a target with both interceptors and SAM. When received by a BCO, it means:
If you have not fired:
• Do not fire.
• Continue tracking.
  If you have fired:
• Permit missile to continue to intercept.

(3) Cease engagement. This instruction is used to alert a unit already engaging a target to prepare to engage a target of higher priority. When received by a BCO, it means:
If you have not fired:
• Do not fire.
• Cease tracking.
  If you have fired:
• Permit missile to engage target, then transfer to new target.

f. Hostile Criteria. The theater rules for engagement will define criteria by which an aircraft may be designated hostile. For example, SOP may classify aircraft as hostile which are
(1) Attacking friendly elements.
(2) Improper response or no response to IFF challenge.
(3) Spraying smoke on friendly elements without prior coordination.
(4) Dropping flares at night over friendly territory without prior coordination.
(5) Discharging parachutists or unloading troops in numbers in excess of the normal aircraft crew without prior coordination.
(6) Engaging in mine-laying operations without prior coordination.

(7) Improper or unauthorized entry into an area designated as restricted.

(8) Use of ECM devices (e.g., chaff and reflectors) over friendly territory without prior coordination.

(9) Bearing the military insignia or having the configuration of am, aircraft employed by a known enemy nation.

(10) Operating at prohibited speeds„ altitudes, or directions.

g. Methods of Control.
(1) General. Theater rules or unit SOP may specify or imply the required Nike Hercules method of control.

(2) Centralized. Under this method of control an ADA commander may require that engagements be conducted only after receipt of permission from a designated higher ADA echelon. The higher echelon may also designate tentative targets, by electronic or voice command, when operating in this method. The right of unit self-defense is not denied. This method is not appropriate for Nike Hercules units during wartime.

(3) Decentralized. Under this method of control, engagement decisions are made at Nike Hercules battalion or battery level, based on the rules for engagement and subject to any temporary engagement restrictions imposed by higher echelons. This is the normal wartime control method for Nike Hercules fire units conducting air defense missions.

(4) Autonomous. When communications with higher headquarters have been lost, Nike Hercules batteries may continue to engage targets, based on the rules for autonomous operations prescribed by higher echelons. Battalions may also operate autonomously if they lose communications with the group, but the batteries may still be in centralized or decentralized method of control.
5-7. General
The Missile Monitor (AN/MSG-4) fire distribution system (FDS) is used for oversea-deployed Nike Hercules battalions (fig. 5-1). Missile Monitor is a mobile, electronic FDS designed for SAM systems that provides rapid and accurate exchanges of information from ADA command elements to fire units, and a rapid collection of data by command elements, to decrease the reaction time of the defense. It provides the ADA commander with a means of fire distribution and supervision that permits him to transmit commands directly to any fire unit in the defense or to provide data to the fire unit commander to allow selection of the best target for engagement. The methods of operation permit flexibility in varying tactical situations. The FDS is air-transportable and uses standard military vehicles for ground transportation.

5-8. Equipment Description
a. Radar Set AN/MPS-23A. This is a mobile, medium-range, frequency-scan radar. It furnished azimuth, elevation, and range data to the radar data processing center (RDPC). The frequency-scan feature provides target height information and range determination by electronic means and eliminates the need for height-finder radar. Azimuth is obtained by mechanical positioning according to the direction of the radar antenna.

b. Radar Data Processing Center. The RDPC is a mobile data processing center that obtains azimuth, elevation, range data, raid-size, and identity from the frequency-scan radar AN/ MPS-23A, displays these data at its consoles, and generates reference track data that are sent to the weapons monitoring center (WMC).

c. Weapons Monitoring Center. The WMC is the mobile tactical center of the Missile Monitor FOS. It is a processing center that receives data from the RDPC and fire units; it processes, displays, and correlates this data;

and it transmits data to the fire units. Data may also be exchanged with adjacent WMC's and Air Force agencies.

d. Battalion Operations Central AN/MSQ-18. The operations central AN/MSQ-18 at battalion headquarters is housed in a modified M109 van body mounted on a conventional 2
½-ton truck. The AN/MSQ-18 may coordinate up to eight Nike Hercules batteries, serves as a link between the defense acquisition radar (DAR) and the fire units, and is designed to be functionally associated with the WMC in the Missile Monitor system (fig. 5-1).

e. Battalion Operations Central AN/TSQ-38. The AN/TSQ-38 is the helicopter-transportable version of the AN/MSQ-18. It has the same or similar components as the AN/MSQ-18 and performs the same functions. One major difference is that the PPI's of the AN/MSQ-18 have a display range of 160 nautical miles (296 kilometers) while those of the AN/TSQ-38 have a display range of 320 nautical miles (593 kilometers).

f. Coder-Decoder Group AN/MSQ-18 and AN/TSQ-38. The coder-decoder group (CDG), the battery-level component of the AN/MSQ-18, is mounted in a modified M109 van body when used with the AN/MSQ-18 system and in a helicopter-transportable shelter when used with the AN/TSQ-38 system. The CDG functions as an automatic data link between the battery and the battalion.

g. Battery Terminal Equipment AN/GSA-77. The battery terminal equipment (BTE) is capable of integrating any ADA missile battery with any of the ADA FDS. The AN/GSA-77, which will replace the coder-decoder group, weighs less than 250 pounds, is small (2 feet x 2 feet x 1 foot), and requires a minimum amount of maintenance. When provided with communications a defense equipped with the BTE can operate in a battery data link mode without being integrated with any central FDS or netting station.

5-9. Organizations and Duties
General. Personnel and equipment to operate the Missile Monitor are provided by cellular teams by TOE 44-510. Personnel are organized in the ADA command post platoon consisting
of a command post headquarters section and a weapons monitoring and radar data processing section. Personnel are provided for continuous operation of the Missile Monitor on a four-shift basis.

(Source: Email from Ralph Dodds)
MSG4 Deployment to Germany, March 1960
I stumbled across your website doing a search on my name. I was really pleased to find your site.

I was the first operations officer of the MSG4 Det, and later one of the 3 shift leaders, until I was reassigned to the 94th Group S3 Office where I did Operational Readiness evaluations of the 24 Nike units. I was delayed in going back to the US due to the arrival of a baby girl in June 1963.

As Operations Officer, I was greatly involved in getting the 6 battalions and their 24 fire units electronically integrated with the WMC. I don`t remember the date when all 24 console lights were glowing and the data links worked reliably but all involved breathed a sigh of relief.

I have very fond memories of the outstanding military technical personnel at the hill, a selfless group. I think I can still remember the battalions under the 94th Group and their call signs.

When was the MSG4 Detachment formed? Was it in Germany or was it formed in the US and then transferred to Germany when the MSG4 equipment was shipped to the 94th?

I think Tom Legere mentions some of the answer in his text. The package was formed at a test site known as Site Monitor, a few miles from Ft
Bliss proper. Don`t know the start date.

I was the chief of the CDG (Coder Decoder Group) branch, Electronics Dept of the school. All of the branch personnel went to the Hughes school on the CDG and then we formed the branch to teach maintenance on the CDG, primarily to NATO personnel, but also some US Army soldiers. I was overdue for an overseas tour and jumped at the chance to go to Germany.

(Before the CDG branch, I attended the Martin FUIF school and then helped organize the FUIF branch, Electronics Dept. We taught maintenance on the FUIF equipment used in CONUS. My main job was going to the different defense areas in the US and orient the battalion personnel to fire control by electronic means. The FUIF was the equivalent of the CDG in the MSG4 setup.)

The MSG4 package was organized at Site Monitor and the word put out for volunteers to man and train with the MSG4 detachment and eventually go to Germany. The testing by the Arty board had been going on for some time when I joined and was completed just after I joined. The operations personnel consisted of several first Lts, about 16 second Lts and a detachment commander Capt Fitzgerald. The maintenance personnel as described by Tom made up the other part of the MSG4 detachment.

We trained for maybe 2 weeks or so and then received orders to leave for Germany. This was march 1960, I think. I was promoted en route and became the Ops officer of the detachment when we arrived in Kaiserslautern, Ger. The 32d Bde and 94th Arty Group were in different kasernes in Ktown.

Q: Can you tell me anything about the organization of the MSG4 Det? Were the personnel assigned to the det primarily used to man the scopes, or did the detachment also perform other responsibilities (communications, maintenance and repair, etc)?

The Detachment had a small Hqs, with the operations Pers. in one section and the maintenance pers in the maintenance section. The Det was under the Hqs, 94th Arty Group. There were Hughes Co pers to provide support, if needed.

The arty personnel were to man the WMC (Lts) and the EM the RPC and manual AADCP. The maint. personnel were on site to take care of the equipment and generators. All of the soldiers working on 479 were under the Det. CO. The maint personnel were Signal Corps.

Once operations were started we had 3 shifts of operations pers. Worked 3 days, 3 nights and off 2 days During exercises or actual alerts, the entire det. stayed on the hill. Had our own mess.

Obviously it was going to take some time to get our equipment ready as we had to electronically integrate the 24 batteries and their CDGs and the 6 Bn OCs. So all of the Lts were assigned to batteries to learn that side of the job. They were returned when we needed them to man the MSG4 equipment, some months later. That was a very good idea.

Q: I assume that the MSG4 equipment was mobile. Was it completely installed in trailers or was it moved into fixed structures on the hill (479)?

Yes the equipment was mobile and the equipment stayed in the trailers. A maintenance man stayed in the rear of the WMC van, monitoring the data links. When there was a big problem, the operations pers evacuated the van and the maintenance pers took over. At the opposite end of the WMC was the station for the ops officer. One of the Hughes personnel (ex army Communications) built a small switchboard for voice commo to the SOC, 24 fire units and 6 bn ops officers. All commands and authentication procedures went thru here. SOC to WMC to BNs/fire units.

The WMC was accessed thru the AADCP side door. The RPC and radar vans were nearby.

Was there any integration into the Air Force control system (412L) or any other NATO command and control system in operation at that time? If so, can you provide a brief description.

Sometime after we became operational, I think, the 412L system was installed at the SOC at Langerkopf and we had an electronics data link to the WMC. Army pers manned the consoles that we worked with. I`m not sure if the consoles were 412L or some equipment installed for just the Army use.

The WMC and the fire units could use the data (symbols) to designate targets to the batteries. The biggest problem we had was accurate symbology associated with an aircraft. The WMC/fire unit accuracy got to be pretty good. The SOC data wasn`t quite as good, as I remember.

Q: Can you provide the call signs in effect for that period?

The only one of the 6 bns I can remember today is that the 2d Bn, 56th Arty was Chrome.

(Source: CW-4 Emile (Tom) Legere, USA-Ret)

NOTE: For additional doctrinal and technical details, see Ed Thelen's wonderful Nike Missile web site)
AN/MSG-4 Weapons Monitoring Center

It was my honor to serve as Command and Control Officer in both the G-4 and G-3, Plans Sections, Hq. 32nd AADCOM, during the period 1975 - 1978. My primary duties involved the early fielding of the AN/TSQ-73 Command and Control System and the implementation of a Direct Support System for the AN/GSA - 77 Terminal Equipment (BTE). Additionally, I was also the Maintenance Officer for the first deployment of the AN/MSG-4 Weapons Monitoring Center with the 94th ADA Group in March 1960 to Hill 479, Bann, Germany.

I will be pleased to contribute to your efforts to compile a history of the 32nd AADCOM in Europe. I think that I know where many of the ghosts are buried and will try to help in keeping your facts straight. Since you have expressed a particular interest in the deployment of the MSG-4 to Germany in 1960, I will start there, and provide the AN/TSQ-73 deployment information with another message later on.

In late 1958, I was an enlisted (SFC) Radar Instructor with the USA Signal School at Ft. Monmouth, N.J. The School was tasked to assign an NCO, and, I was selected, to attend a 17 week AN/MSQ-28 Weapons Monitoring Center course at the Hughes Aircraft Company Facility, located at Fullerton, Ca. The assignment was TDY enroute to the USA Air Defense Board at Ft. Bliss, TX. As I recall (remember, this was 46 years ago), the WMC Course began at Fullerton on or about 1 Dec. 1958. My classmates were mostly all E-6 and E-7 NCO's drawn primarily from Signal Corps Radar and Communications assignments, a couple of Signal Corps Warrant Officers, and a couple of Signal Corps Lt's. There were also a couple of NCO's assigned by the USA Air Defense Board.

The class materiel was all Greek to the majority of us as we were introduced to strange things like BOOLEAN ALGEBRA, BINARY ARITHMETIC, AND and OR GATES, FLIP-FLOPS, and other things like MEMORY DRUMS, REMOTE STARTS and SEQUENCERS.

The Weapons Monitoring Center was, except for some display circuitry, completely transistorized, something that was completely new to the Army, and had a Memory Drum to store track and Fire Unit Data. What made this unique, was that for the first time, the Army would have a capability of maintaining automatic data updates on the location and speed of a large numbers of aircraft with minimal operator updating. The Memory Drum provided storage for up to 100 LOCAL Tracks (Aircraft Radar returns) detected by the Collocated AN/MPS-23 three-dimensional Radar (Another first for the Army) which sent Target range, azimuth, and height data to the Radar Data Processing Center (RDPC) for processing into digitized track data, which was then passed, by cable, to the WMC for possible assignment to up to 32 subordinate Hercules or Hawk Fire Units for action.

In addition to the 100 Local Tracks stored, the WMC could store up to 92 REMOTE Tracks provided by adjacent MSG-4 Units (this has special significance later, when the MSQ-28 was deployed to Europe), and up to 8 Battalion Tracks provided by up to 4 subordinate AN/MSQ-18 or AN/TSQ-38 Battalion Operation Centrals (BOC's), each of which was capable of semi-automatically generating 2 Battalion Tracks (1 per console - the BOC DID NOT have a Memory capability) based on radar video provided by it's collocated Defense Acquisition Radar (Usually an AN/GSS-1 Radar, the mobile version of the WWII AN/TPS-1D) - NOTE: The Defense Acquisition Radar (AN/GSS -1) was still the BOC Radar as late as 1978, and was maintained primarily with salvaged parts from cannibalized TPS-1 and GSS-1 radars stored and provided by the Lexington Army Depot, Kentucky.

Back to MSG-4 deployment: The WMC Course was 19 weeks in length rather than 17 weeks as stated above, although we did have a two week break during the 1958 Christmas and New Year period, when the Hughes Aircraft Facility closed down for those holidays. The Course was completed in April 1959, and we then reported for duty with the USA Air Defense Board, where we learned that we would participate in the Army Acceptance Tests of the prototype AN/MSQ 28 AADCP System (WMC, RDPC, and AN/MPS-23 Radar) to be conducted at SITE MONITOR, an Installation about 15 miles east of Fort Bliss, Tx.

Subordinate to the AADCP were four AN/MSQ-18 Battalion Operation Centers, and as I recall, a mixture of 16 Hercules and Hawk Fire Units (a Hercules Battery was 1 Fire Unit, and a Hawk Battery was 2 Fire Units, since a Hawk Battery, at that time was capable of two simultaneous engagements. Later (1975), with the fielding of the TRIAD configuration, a Hawk Battery was capable of three simultaneous engagements, with its three Firing Platoons). The TRIAD configuration had significant impact on Command and Control when the TSQ-73 was deployed, and especially when the GEADGE system was deployed. (I'll talk about that when I cover the AN/TSQ-73 deployment).

My primary duty was to integrate the subordinate BOC's and fire units prior to each individual test and to monitor equipment performance during the conduct of that test. Integration consisted of establishing communications with the subordinate units and to ensure that all Missile Battery Data Link (MBDL) information was transmitted and received between the WMC, the BOC's, and fire units correctly. (Following text inserted 5-18-2004) This was accomplished at one of four identical consoles, by the utilization of that console's Fire Unit Selection Push Buttons (one for each of 32 fire units), and the horizontal Command Panel which contained, going right to left, a Track Ball, up to ten Voice Communications Push Buttons, then separate push buttons for the following Commands:
ENGAGE A (Conventional Warhead - Used for either Hercules or Hawk Fire Units);
ENGAGE B (Low Yield Nuclear Warhead - Hercules ONLY);
ENGAGE C (High Yield Nuclear Warhead - Hercules ONLY);

There were also two REFERENCE Control Pushbuttons; TRANSMIT ONE, and TRANSMIT ALL (Use of these pushbuttons would cause either ONE selected LOCAL or Remote Track, or ALL Local and Remote Tracks to be transmitted to ALL BOC's and Fire Units interfaced with the WMC.)

An additional pushbutton was provided - The HOOK push button. The Console's Plan Position Indicator (PPI) provided digital display of detected targets by separate symbology For FRIEND, FOE, or UNKNOWN aircraft, and the geographical location of each fire unit, and the target pairing to that fire unit. If available, live targets would be used for integration, but in most instances, a SIMULATED TARGET representing a POINT IN SPACE was generated by Operation of the WMC SIMULATION PANEL.

The procedure was to HOOK a target by placing a HOOK Symbol over the selected target symbol by means of a Track Ball (Similar to the operation of a "Mouse" used with today's PC's), and depressing the HOOK pushbutton which caused the target symbol to expand in size. The pushbutton associated with the unit being integrated would be illuminated GREEN, indicating the Fire Unit was READY for assignment. Depressing (Selecting) the Unit's pushbutton would cause it to turn RED indicating that the unit was in the process of engagement. The WMC operator would then depress the appropriate ENGAGE Command pushbutton, causing a MBDL COMMAND MESSAGE to be transmitted to the selected Fire Unit.

Simultaneously, a blinking dashed pairing line would extend from the fire unit symbol to the assigned target symbol indicating that that target had been assigned to that fire unit. When the Battery Control Officer (Hercules) or the Tactical Control Officer (Hawk) correlated the assigned target symbology generated by the MBDL MISSILE BATTERY DATA LINK data received and processed by the Battery Coder-Decoder Group, with the video provided by his local acquisition radar (HIPAR or LOPAR for Hercules, or PAR or ICWAR for Hawk) on his tactical PPI display, he would then designate the target to the Target Tracking Radar (Hercules) or the Illuminator Radar (Hawk). Designation of the target to the Tracking/Illuminator Radar would automatically cause an ACKNOWLEDGE message to be transmitted to the BOC and WMC. The BCO/TCO could also manually acknowledge by pushing a button (Acknowledge ???) provided at his Console. When the Acknowledge message was received by the WMC, the blinking pairing line would cease to blink, but remain dashed, and the Acknowledge Message would also be displayed on the Battery Read-Out Panel. When the fire unit TTR/Illuminator LOCKED-ON to the target, it would cause the coordinates of the TTR/Illuminator acquired target to be transmitted to the BOC and WMC. This would cause the dashed pairing line to become solid, terminating at the point at which TTR/Illuminator was LOCKED-ON. If the BCO/TCO had acquired the assigned target video the pairing line would intersect with the assigned target symbology on the WMC PPI. If the BCO/TCO had designated the incorrect target video, the Pairing Line would terminate at the point designated by the BCO/TCO, telling the WMC Operator that the Fire Unit was engaging the wrong target, and he could then transmit the Appropriate command to the fire unit telling the BCO/TCO to terminate that engagement. When the Fire unit launched it's Missile (Hercules) or Missiles (Hawk), a firing message would automatically be transmitted to the BOC and WMC, causing that status to appear on the Battery Read-Out panel. After the completion of the engagement the BCO/TCO would evaluate the results of the engagement by determining if he still had target video. If no video remained, a KILL message would be transmitted, and if video remained a NO KILL message would be transmitted. This entire procedure could be performed silently without verbal exchange between the participants, for purposes of communications discipline.

Once the integration had been successfully completed with ALL of the units scheduled to participate in that particular test, the system would be turned over to the Officers responsible for the conduct of that test. Except for occasional operator errors, few equipment problems occurred during the conduct of these tests.

This testing phase provided excellent training vehicles for preparing us to field the system in that we learned to view the entire AN/MSG-4 Command and Control System as one entity with The AADCP, BOC's, Hercules or Hawk Fire Units, and ALL of the associated communications and Radars, as comprising the whole SYSTEM, as opposed to viewing the AADCP as a separate "BLACK BOX". In other words, a SYSTEMS ENGINEERING concept. Unfortunately, the training of future operator/maintenance courses (AN-MSG-4, AN/TSQ-51, and AN/TSQ-73) DID NOT stress this concept, but stressed the "BLACK BOX" approach to the detriment of successful employment of these systems in later years. The people associated with these future deployments had to learn the hard way, and, some, never learned at all. Case in point, of the five AN/MSG-4 Systems deployed (three in Germany, and two in Korea), only one became fully operational (94th ADA Group), and another partially operational (AADCP 2 at Inchon, Korea). The other three - the 10th and 69th Group Systems in Germany, and AADCP 1 at Camp Humphries in Korea NEVER BECAME OPERATIONAL. Sad, but true - I was there at both the 94th Group, and AADCP 2 in Korea.

One of the reasons for our success, was that our approach was that ARMY Air Defense NEEDED the AN/MSG-4 Systems, and that we had to make it work. If a malfunction occurred we worked right alongside the Hughes Tech Reps, to resolve the problems, and return the system to an operational configuration as soon as possible. This approach enhanced our understanding of the overall system, and expedited the successful completion of the Acceptance Testing of the system. Conversely, those responsible for testing the AN/TSQ-73 walked away from the system when a malfunction occurred and turned the system over to the Litton Reps, and returned ONLY when the system was returned to operational status, resulting - in my opinion - with unnecessary delay in fielding that system.

We did encounter a major catastrophe while testing the system. A generator operator while changing generators powering the RDPC, inadvertently. plugged the power cable so that the cable ground connector was connected to one of the three "Hot" phases effectively "grounding" that Phase. This resulted in a major power surge to the RDPC, and virtually incinerated a large number of circuit boards, resulting in eliminating the RDPC and AN/MPS-23 Radar from further test participation. Fortunately, when this incident occurred, those systems had already been successfully tested. We did, both RDPC and WMC Maint. People, expend many, many hours repairing RDPC circuit boards.

I don't remember precisely when, but we were given the opportunity to volunteer to become part of an AN/MSQ-28 Deployment Packet when the System was scheduled to be deployed to Germany. Since my wife was from Germany, and I had liked my prior duty there, I, of course, volunteered and was accepted as a member of the Deployment Packet.

The Signal Corps was planning to introduce a new Warrant Officer MOS - 4842 - Data Processing Maintenance Technician, and since the ADA Board was one of the only sources of personnel qualified in that field, the Board was requested to solicit those of us who were interested, to make application for appointment, so I did make an application, along with about eight others.

In addition to preparing for the deployment of the AADCP AN/MSQ-28 System to Germany, the ADA Board was still tasked to conduct cold weather testing of the system, as well as the follow-on testing of the Production AN/MSQ-28, prior to the deployment of those system to Germany and Korea. It was obvious that the number of qualified system repairmen available was inadequate to meet all of these needs. It was then necessary to train additional personnel to accompany those of us who had already been selected as part of the Deployment Package, and this requirement became the task of the Hughes Aircraft trained repairmen, as well as continue with the testing of the system.

This is good point to provide the roster of Deployment Packet. WMC Maintenance personnel trained at the ADA Board are indicated by (**) following their names.

AN/TSQ-28 AADCP Deployment packet roster:
Note: Approximately an estimated 20 to 30 (Perhaps more) 1st and 2nd Lieutenants were members of the packet as most of the WMC and RDPC Operator positions were to be manned by officers. That roster is not available to me, but a few of the names I do recall are:
  1. Capt. (Name-?) Fitzgerald Packet Commander
  2. Capt. Colin Bozeman
  3. Capt. Ralph Dodds
  4. 1st Lt. Johnnie Howorth
  5. 2nd Lt. Philip Pharese
  6. 2nd Lt. Thomas Franklyn
  7. 2nd Lt. Joe Thurston (Later - 1978, G3 of the 32nd AADCOM)
Roster of AADCP Maintenance and enlisted AADCP operations personnel:
  1. 1st Lt. Albert G. Stratton AADCP Maintenance OIC
  2. CWO W2 Frank B. Coombs AN/MPS-23
  3. CWO W2 Sydney B. Hunter WMC
  4. CWO W2 Richard W. Lee RDPC and AADCP Operations
  5. CWO W2 Harold A. Moulton AN/MPS-23
  6. CWO W2 Farrell E. Tew RDPC
  7. MSGT E7 Walter D. Blackwood WMC
  8. MSGT E7 William W. Barrow RDPC
  9. MSGT E7 Johnnie E. Grant RDPC
  10 SFC E7 Marshall N. Dana WMC
  11. SFC E7 Harry E. Leggans RDPC
  12. SFC E7 David A. Matthews RDPC
  13. SFC E6 Charles W. Adamek ?
  14. SFC E6 Harold D. Smalley ?
  15. SFC E6 Vernon W. Kidwell RDPC
  16. SFC E6 Emile T. Legere WMC
  17. SFC E6 James E. Roach WMC
  18. SFC E6 Edward J. Cewe AN/MPS-23
  19. SFC E6 Robert J. Cruz AN/MPS-23
  20. SFC E6 Manuel A. Bov ?
  21. SFC E6 Bobby D. Horne AADCP Operator
  22. SFC E6 Larry N. Takahashi RDPC
  23. SFC E5 Louis L. Duvernay WMC
  24. Sgt E5 Albert V. Bierman WMC **; Al had served with the 32nd Bde. in England
  25. Sgt E5 William D. Parrott AN/MPS-23
  26. Sgt E5 Claude F. McFarland AADCP Operations
  27. Sgt E5 Thomas D. Ray AADCP Operations
  28. Sgt E5 Louis M. Cotter ?
  29. Sgt E5 Walter R. Lucas WMC **
  30. Sgt E5 William E. Lucy RDPC
  31. Sgt E5 Samuel H. Beaty ?
  32. Sgt E5 Nicholas H. Meyerovich RDPC
  33. Sgt E5 Candido Suarez WMC **
  34. Sgt E5 Billy H. Walls WMC **
  35. Sgt E5 Jackie H. White AADCP Operator
  36. SP5 E5 Pasquale Garzone ?
  37. SP5 E5 Oswald L. Hughes RDPC
  38. SP5 E5 Roger W. Konrad WMC **
  39. SP5 E5 Robert E.Y. Lee RDPC
  40. SP5 E5 David W. Ziegler RDPC
  41. SP5 E5 Lester R. Elton ?
  42. SP5 E5 Hershel L. Duncan AADCP Operator
  43. SP5 E5 Lee R. Wheeler RDPC
  44. SP5 E5 Perley W. Wheeler WMC **
  45. SP4 E4 Thomas L. Becker RDPC
  46. SP4 E4 John C. Walker AADCP Operator
  47. SP4 E4 Charles A. Bell AADCP Operator
  48. SP4 E4 John P. HuiHui WMC **
  49. SP4 E4 John T. Pancake WMC **
  50. SP4 E4 Richard J. Poliquin WMC **
  51. SP4 E4 Albert H. Leong ?
  52. SP4 E4 Dayle C. Zorn AADCP Operator
  53. SP4 E4 David L. Wotawa AADCP Operator
  54. SP4 E4 Robert D. Crawford AADCP Operator
  55. PFC E3 Wilmer C. Holloman Jr. AADCP Operator
Roster of Hughes Aircraft Company Technical Representatives assigned to 94th ADA Group:
  1. John Langemak  
  2. Al Jensen  
  3. Ken Burke  
  4. Chester (?) Wilmot  
  5. Willy Henson  
  6. Bill Sargent  
  7. Johnny Ryan  
  8. Hank Varela  
  9. Ripp ?????  
NOTE: There were 4 or 5 others whose names I do not recall.
By early January 1960, acceptance testing, except for those tests which had earlier been aborted for one reason or another,and had to be conducted to complete the record, was in the process of winding down, and we were busy preparing to deploy to Germany. Orders were cut, household goods packed, and travel arrangements were made. By mid-February we were pretty much ready to go.

But then, we were told that there was one more major hurdle to overcome, before being allowed to proceed to Europe. Col. Schreiber, the ADA Board Chief of the Electronics Branch, who had final say on proceeding with the deployment, decreed that NO ONE WAS GOING ANYWHERE UNTIL ALL ELEMENTS OF THE TEST (AADCP, BOC'S, FIRE UNITS, RADARS, AND COMMUNICATIONS) WERE OPERATIONAL WITHOUT MALFUNCTIONS FOR A PERIOD OF 72 HOURS, at which time he wanted to see ALL units integrated. If that final test was successfully passed, then we would be permitted to proceed with deployment, otherwise, deployment would be delayed.

Needless to say, this was a very challenging requirement, and everyone, at all echelons, stacked the deck and the sharpest operators and maintenance personnel manned each item of equipment for the entire 72 hour period. At the end of the 72hours, Col. Schreiber monitored the conduct of each of the 16 Fire Units being integrated, which were conducted one at a time by the WMC Officer Operators. As these integrations were being conducted, SFC Dana and I were observing the operations, and we noticed that the Fire Unit Pushbuttons, were rapidly blinking from red to green, and back again, and looked like a pinball machine. This was a sure indication that the system was going to fail. We did'nt say anything, and if the Officer Operators were aware of what was happening, they did'nt let on. Finally, ALL of the integrations were successfully completed, and Col. Schreiber gave his authorization for the deployment to proceed as scheduled. He no sooner left the WMC Van, when the SYSTEM POWER SUPPLIES quit cold.

We did not take the time to repair the Power Supplies, but march-ordered the Van, as did the rest of the AADCP System Personnel with their Equipments (RDPC and AN/MPS-23 Radar). We corrected the problem as soon as the WMC was in place on Hill 479, Bann, Germany. And that was the way the first AN/MSG-4 AADCP was deployed to Germany, leaving Fort Bliss, Texas in mid-February, and arriving at Bann, Germany at the end of April 1960.

Once Col. Schreiber approved the movement of the AADCP Packet to Germany, it's members could then make requests for movement of dependents (wives and children of military personnel).

Due to the limited availability of Government Quarters within the Command, USAREUR policy was that military personnel assigned to duty with USAREUR units COULD NOT travel with dependents until Government Quarters became available, UNLESS an address on the German economy, at which those dependents could reside, was provided with the requests for movement of dependents. Since my wife was German, and could reside with her parents until quarters were available, my request for concurrent travel was approved.

Shortly after my request for concurrent travel was approved, I received a call from the Fort Bliss Transportation Office offering me the choice of air travel or TRAVEL BY FIRST CLASS ABOARD THE UNITED STATES LINES S.S. AMERICA!! - This was a no-brainer, so OF COURSE I requested the travel by the S.S. AMERICA even though we would have problems with clothing, and finances - this was the chance of a life-time. How many people have the opportunity to travel FIRST CLASS on an all-expense paid trip aboard one of the most historic passenger liners to cross the Atlantic Ocean? The reason this was possible was that the construction of the S.S. AMERICA, and her sister ship, the S.S. UNITED STATES, had been subsidized by the U.S. Government, and the United States Lines was obligated to provide X number of First Class accommodations for the use of Government civilian and military personnel for each voyage.

On 3 March 1960, I received a Port Call ordering me and my dependents to report to Pier 86 North River (Hudson), located at West 46th St, New York City on 18 March 1960 between 1300 and 1500 hours for travel aboard the SS America First Class accommodations sailing the same day. We learned that the SS America also had Dog Kennels on the upper deck, and that it would be possible for our Dachshund "Pepper" to travel along with us, although at our expense. The whole family could travel together!!!

We had 15 days to clear Post and travel by car to New York and ship the car to Germany so we really had to scramble, but we made it on time. When we boarded the ship, we were escorted to our assigned cabin on the First Class Deck. It was a very, very nice and comfortable cabin and fairly large, with a personal Steward to respond to our needs, which included midnight snacks if requested.

Once we had settled into our cabin, we hurried to the ships side to watch her back out from the pier as we set sail, and proceed down the Hudson River, and past the Statue of Liberty, which we were anxious to see. I was in my Class-A Green Uniform, and still wore the CONARC Patch (The ADA Board was a CONARC Unit hosted by Fort Bliss). As we were waiting to sail by the Statue of Liberty, a very Grubby, unshaven individual, in a very soiled raincoat, came up to me and introduced himself as John Woods. My reaction was cautious, and "Who Is This Guy?" As politely as possible, I explained to him that we were anxious to see the Statue of Liberty and requested that we delay our conversation until a later time. He graciously agreed, and left us to resume watching our progress through New York Harbor. When he left, my wife said "He's a General". I told her I didn¹t think so, as he sure didn¹t LOOK like a General to me !!. It developed that she had seen his name in the First Class Passenger List in our cabin, as we settled in, and by golly! - He was Major General John Woods from CONARC Headquarters in Virginia,and he had driven overnight in stormy weather in order to arrive in time for sailing. I later learned that he was General George Patton's Son-in-Law, who as a Lt. Col., had been captured at Kasserrine Pass in Tunisia. He became a controversial figure when Gen Patton ordered Task Force Baum to travel through German Lines in the vicinity of Frankfurt/Main and fight through to the Hammelburg POW Camp which was in the vicinity of Wurzburg and rescue the American POW's interned there. Lt.Col. John Woods was believed to be a prisoner at that Camp!!!

Later, Gen. Woods and I did have our conversation, and when he learned that I had participated in the Q-28 Tests, he asked many questions about the equipment performance, and asked me my opinion about it's potential. I responded that I thought the system would perform the mission for which it had been procured successfully. I think that he was reassured about the fielding of the AN/MSG-4.

Food aboard the America was fabulous and prepared by Gourmet Chefs, and served by our personal Dining Room Steward. There were a few hours available for each meal so that you did not have to rush in order to avoid missing a meal. There were only about a dozen Army personnel aboard, most of whom were General and Field Grade Officers. A Specialist-5 and his family were the only enlisted personnel aboard beside my family and I.

I had made two prior Atlantic crossings by Troopship during the month of March. The Atlantic seas are usually very rough in March, but I had not been sick during those passages. This time, on our second day out, as we were having breakfast, my 11 year old son, Thomas, said "Daddy, I'm going to be sick !". I hustled him out of the Dining Room, and he managed to hold on until we reached our cabin. You guessed it ! As he was being sick - I had the urge to keep him company - - and I did.

All in all, it was a very, very nice way to travel and we enjoyed ourselves very much. I do not recall exactly, but we arrived at our destination, the port of Bremerhaven, on or about the 24th of March . We had been told, prior to arrival, that the German Bundesbahn would have First Class cars waiting at dockside, and that we would debark from the ship directly into our assigned compartments. The train would then proceed to Frankfurt/Main, where we would transfer to other trains to out final destinations. We wired my In-Laws advising them of the arrival time in Frankfurt (They lived in Russelsheim/Main - between Mainz and Frankfurt, about 30 kilometers). When we arrived, we had a very joyous reunion with my wife's family.

Our reunion with my wife's family at the Frankfurt Bahnhof was great, BUT, I told them I was still obligated to continue on to Kaiserslautern and report for duty with the 32nd ADA Brigade. My Brother-in-Law, Leander, told me not to worry as he would drive me to K-town later in the evening so that I could report in before midnight (It is about 70 miles from Russelsheim to Kaiserslautern). With that understanding, we then went to my In-Laws house in Russelsheim, where my Sister-in-Law, Maria, prepared a typical German meal, which we consumed with gusto (Maria is a fantastic cook). At about 2130 hours, my wife, son,and I piled into Leander's car (an OPEL) to drive to K-town.

As anyone who has served in Germany will tell you, there is no SPEED LIMIT except in posted zones, and the Germans ALL drive as though they were driving at the Indianapolis Speedway. Leander was no exception, and he floored it all the way, and we arrived at Kapaun Barracks, Vogelweh, a little over an hour after leaving Russelsheim. I then reported to the surprised 32nd Brigade Duty Officer, who informed me that I was unexpected, and that I was the FIRST member of the MSG-4 Packet to arrive for duty. He then told me to take a few days before reporting in so we then drove, with Leander again flooring it all the way, back to Russelsheim, where we then had the time to get reacquainted with our relatives, who were overjoyed to have us there.

On, or about the 28th or 29th of March 1960, I reported for duty which would be the beginning of three of the most satisfying years of my 28 year career. No one else had arrived yet, so I had a lot of free time on my hands. I do not recall the circumstances, but someone suggested that I go take a look at HILL 479 where the Q-28 would be located when it arrived. I obtained transportation for the trip, and recall driving through the village of BANN (not to be confused with BONN), which consisted of twenty or thirty houses, with narrow, twisting cobblestone roads leading to 479. Coming out of the village was a narrow dirt farmers road, which had a fairly steep incline as it rose up towards the Hill, and then twisted around to the right, and after twisting around a couple of more times finally reached a relatively flat area, bordered by farmers (Potato-??) fields, and finally reached the AADCP site. IT WAS STILL BEING PREPARED BY A U.S. ARMY ENGINEER COMPANY !!!! The site was to the left of the road, and extended to where the terrain started to slope downward towards Landstuhl (No more than 100-150 yards). The Engineers had graded a gravel/dirt composition road running parallel to the farmers road, and had laid the concrete foundations for six (?) Butler Buildings, between their road and and the site fence. At the Southeastern corner of the site, a twenty or thirty foot Berm had been built for the AN/MPS-23 Antenna Trailer. The graded road then cornered to the left towards the North and about halfway down, the graded area was extended on the right side to provide a hardstand for the WMC, RDPC, and their Maintenance Vans. At the end of that section of road was the concrete foundation for another Butler Building, and before I forget, a Four (?) Hole Latrine Facility - We didn¹t have LADY soldiers assigned to the ADA Units in those days. The road then circled around to head South towards the Radar Berm, and a shed was constructed to shield the systems 12 Diesel Generators from the elements on the right side of the road. Another hardstand was provided at the Northeast corner of the site for emplacement of the Communications equipment shelters.

That was my first sight of the AADCP site on HILL 479, but not my last, because, my last sight of THE HILL (As we fondly, and sometimes, NOT TOO fondly - referred to it) was in 1978 as the first Group level AN/TSQ -73 was preparing to start operations there (108th ADA Group).

Within a couple of weeks after my arrival in Germany, the other members of the Packet began to arrive in twos and threes. The AADCP Maintenance Personnel were assigned to the 3815th Signal Support Unit at Kapaun Barracks, Vogelweh, and the AADCP Operations Personnel were assigned to the 32nd ADA Brigade, also at Kapaun Barracks. Since the AADCP Equipment had not yet arrived, the Signal Corps enlisted personnel were only required to report for the morning formation, after which we were pretty much left to our own devices. Almost immediately after our arrival, CWO Sydney Hunter (WMC) was reassigned to other duties, and Capt. Fitzgerald disappeared completely - I was only an enlisted member of the WMC Maintenance Section and not privy to the reasons for these reassignments.

Examination of the AADCP roster above reveals that the Packet was very rank heavy with E7 and E6 NCO's. The reason for this was that we were formed under a PROVISIONAL TABLE OF ORGANIZATION which provided for a number of E9, E8, and E7 slots, and thus an opportunity for promotion for most of us. This fact induced many of the Packet NCO's to volunteer for duty in Germany. Although I had an application for a Warrant Officer appointment pending, and I would have volunteered in any case, it didn¹t hurt my morale any to have the possibility I might be promoted to MSGT(E7). After all, I had been in grade since 1952, so if my Warrant Application was not approved, I would still be in pretty good shape.

We were soon advised that the PROVISIONAL Table of Organization HAD NOT BEEN APPROVED, and the AUTHORIZED Table of Organization provided only ONE SFC(E7) position for each of the three maintenance sections, The WMC, RDPC, and the AN/MPS-23. Thus, there resulted a MASS EXODUS of the M/SGT(E7) and some of the SFC(E6) personnel to other assignments within the 32nd ADA Brigade, and other USAREUR Units. This upheaval of Packet personnel DID NOT end the turmoil within our ranks, MORE was yet to come !!!

Again, I was not privy as to the reasons behind what occurred next, but a TURF WAR broke out when the area Signal Corps Officers including Capt. Stratton (promoted while in transit) and the majority of the Packet Warrant Officers, advocated that the Packet Maintenance Personnel be independent from the ADA and formed into a Signal Detachment and perform DIRECT SUPPORT to the ADA AADCP !!! In this instance the Signal Corps DID NOT prevail, but the future AN/MSG-4 deployments DID provide for the Maintenance Personnel being assigned to separate Signal Corps Detachments, which in my opinion, was the primary reason those deployments resulted in those systems NEVER achieving an OPERATIONAL status. While I was in Korea (1964-65), I WAS assigned to the 61st Signal Detachment in DIRECT SUPPORT of AADCP 2 at Inchon. Since it is not part of this narrative, I will not go into the history of the AN/MSG-4 Signal Detachments, but it will suffice to state that the WMC DID REQUIRE a 24 Hour a Day, ON SITE, maintenance presence - NOT TO REPAIR malfunctions, but to provide expertise in monitoring the status of the system data links which at times could become very marginal due to communications failures by operators, or signal levels. The result of the Signal Corps/ADA Turf War was that, except for CWO Farrell Tew, and CWO Richard Lee, Capt. Stratton and the other AADCP Warrant Officers were reassigned to other duties.

HILL 479
The personnel transactions just described, took place during the period April 1960 through November 1960. There was another significant transfer of AADCP Packet Personnel during this period, when a large (unknown) number of the AADCP Lieutenants (one of whom was 2nd Lt. Joe Thurston) and some RDPC Maintenance personnel were transferred to CRC LANGERKOPF to be trained to operate and maintain the Hughes Aircraft Company SRS-II System installed at that location. The SRS-II was the Developmental Version of the AN/MSQ-28 Radar Data Processing Center, in a "Breadboard" configuration, and functionally identical to the RDPC, and therefore, could emulate "The Adjacent AN/MSG-4 Track Data" mentioned earlier in my narrative. It's source of radar video was the CRC LANGERKOPF Surveillance Radar (type unknown), and provided CRC LANGERKOPF with a AUTOMATED capability to interface the U.S. Army Air Defense AN/MSG-4 System, which it DID NOT possess prior to installation of the SRS-II !!!!!

Emplacement of the SRS-II at CRC LANGERKOPF was to have profound impact on the utilization of the AADCP RDPC and AN/MPS-23 Radar located at Hill 479. I have NO INFORMATION as to how the decision by the ARMY to provide the SRS-II for Air Defense operations was arrived at, but having experienced a similar situation during the EARLY-FIELDING PHASE OF AN/TSQ-73, IT WAS A DIRECT RESULT - In My Opinion - OF THE "ROLLS AND MISSIONS" TURF WAR between CINCUSAFE and CINCUSAREUR which had transpired PRIOR to the deployment of the AN/MSG-4 System, which is described in the TWO Annual Historical Reports, HQs USAREUR-1958 and 1959). In developing this theme, I will quote selected portions of these two reports and identify the quotes by enclosing them with quotation marks. For a fuller understanding of USAF/US ARMY views of Air Defense in Europe, I refer the reader to the "ARMY AIR DEFENSE IN THE EUROPEAN THEATER" articles on the Overview Page of the web sites Air Defense section.

To understand what led to the emplacement of the SRS-II at CRC Langerkopf, and the eventual demise of the RDPC and AN/MPS-23 the historical record must be scrutinized. (I have NO PERSONAL KNOWLEDGE OF WHAT ACTUALLY TRANSPIRED, BUT HAVING BEEN THERE – AND DONE THAT [1975-1978], I BELIEVE THAT I CAN, BASED ON THE RECORD, OFFER A FAIRLY ACCURATE ESTIMATE OF WHAT HAPPENED).

“In September 1958, USAREUR was asked to concur in a draft USAFE letter concerning a special FY 1959 Military Assistance Program for the integrated air defense system. In an informal answer USAREUR pointed out that, since all requirements for Army equipment – NIKE, HAWK, and AN/MSG-4 – were in approved or recommended programs, there was no need for including such items in the USAFE program. “

“At a conference on the USAFE proposals held on 20 September 1958 a SHAPE representative asked THAT THE ARMY AN/MSG-4 SYSTEM, which had been approved by the Department of Defense, and was actually available, BE USED, TOGETHER WITH ITS RADAR, THE AN/MPS-23, AT SECTOR OPERATIONS CENTERS (SOC’S). IF A SOC HAD ITS OWN RADAR, THE REQUIREMENT FOR THE AN/MPS-23 WOULD BE ELIMINATED”.

“When the USAFE proposals were forwarded to the Secretary of Defense on 27 September 1958, CINCUSAREUR took exception to two points: THE PLAN TO LOCATE THE AN/MSG-4 SYSTEM IN THE SOC, AND THE POSSIBILITY THAT THE AN/MPS-23 MIGHT BE SEPARATED FROM THE AN/MSG-4 SYSTEM”.


“Engineer Testing of the AN/MSG-4 started in the Spring of 1959. And it was anticipated that an interim report, upon which the DEPARTMENT OF THE ARMY could base its decision on deployment, would be received in October 1959. If the evaluation was favorable, THE DEPARTMENT OF THE ARMY would make a PROTOTYPE (That was US !!!!) SET available to USAREUR by about January 1960”.

“In anticipation of the receipt of the AN/MSG-4 equipment by the 32nd Artillery Brigade, CINCUSAFE asked that planning for its installation be coordinated with his staff. The air defense of (southern) Germany would be conducted from three prime ground environment terminals – the Command and Reporting Centers (CRC’s) at LANGERKOPF, GIEBELSTADT, and FREISING that he supervised from the KINDSBACH CAVES”.




At this point, since these divergent views on AN/MSG-4 deployment had resulted in an impasse, A COMPROMISE was more than likely proposed, whereby the ARMY would deploy the SRS-II to CRC Langerkopf, and the AN/MSG-4 would be deployed as planned by the ARMY to Hill 479.


When the AN/TSQ-73 deployment is discussed in this narrative, it will be apparent that HISTORY REPEATED ITSELF !!!!

The AN/MSQ-28 AADCP equipments arrived in Germany at the end of April 1960 and were processed by one of the Kaiserslautern Depots, before being issued to the 32nd ADA Brigade. This was the start of a very busy period in the history of HILL 479, and much of it is very foggy in my mind as I try to recall as much of our activities as I can after all these years (Again; this was over 46 years ago). I do recall some incidents which occurred and which I will try to relate as they become appropriate.

I did not participate in the movement of the Q-28 AADCP equipment from the Depot to the HILL and I am not sure that any of us were DIRECTLY involved in that movement - I am not 100% certain, but I DO seem to recall that the actual movement was made by a local TRANSPORTATION TRUCKING UNIT, as we did not have organic Prime Movers. In all. There were the RADAR Antenna Van, the RADAR Equipment Van, The RADAR Maintenance Van, The RDPC Equipment Van, The RDPC Maintenance Van, The WMC Equipment Van, and the WMC Maintenance Trailer, as well as our 12 Diesel Generators which required movement. I DO know that negotiating some of the sharp left turns through the NARROW STREETS OF BANN did cause SOME difficulty, and that SOME damage was done to some of the buildings of the Village, for which the owners were presumably compensated - That was way above my Pay Grade !

The HILL became a "beehive" of activity once the equipments were in their allotted positions - a great deal had to be accomplished before the WMC could become OPERATIONAL - I can not speak for what the RADAR and RDPC Guys had to do, because THEY had to do THEIR THING - AND WE HAD TO DO OURS!

1. Provide Power to WMC
2. Compute Parallax for ALL INTERFACING UNITS
3. Establish Communications with ALL INTERFACING UNITS

1. Providing Power to the WMC entailed servicing (i.e. Fueling and Testing) the four (4) Diesel Generators assigned to the WMC - two each 45KW-60 cycle, and two each 45KW-400 cycle Generators. The 60 cycle Generators provided administrative power for the System Air Conditioners, Heaters and Lighting. The 400 cycle Generators provided the AC Input to be converted to the DC Voltages required by the System Circuits. One of each type were ON LINE 24 Hours per Day, 7 Days a Week, and were synchronized so that they could be switched from one to the other, without interrupting power to the WMC. Our Generators, as well as the other eight (8) Generators powering the RDPC and the AN/MPS-23 Radar, were maintained and operated by assigned Diesel Generator Operators who performed 1st and 2nd echelon maintenance under the supervision of CWO Tew. Generators requiring Direct Support Maintenance had to be evacuated from the HILL, and towed to the Direct Support Unit located in Kaiserslautern. Frequently, although a Generator had been repaired by the Direct Support Unit, by the time it had been towed back to the HILL, it was non-operational due to vibration which caused some components to shake loose during the trip back. Later, the Direct Support Unit would send a Contact Team to attempt repair on site, which reduced the number of evacuations required.

2. Computing Parallax

Webster defines Parallax as - the apparent displacement of an object as seen from two different points not on a straight line with the object.

Most, if not all, Ground Environment Command and Control Elements use the CARTESIAN COORDINATE Method of exchanging target and system location data. Although the Cartesian coordinate method is a LITTLE COMPLEX (to say the least) to implement, I will try to describe it as simply as possible, and if my description IS NOT TECHNICALLY ACCURATE, it should convey the CONCEPT of the methodology.

Before I get to the Cartesian Coordinate System, a few CONSTANTS have to be defined;

FIRST - it must be understood, that ALL participants in the exchange of Target and Location data, report that data based on the VIDEO or TRACKING returns from their COLLOCATED SEARCH or ACQUISITION/TRACKING RADAR, or based on the POSITION of THEIR PRIMARY SOURCE OF RADAR DATA.

THE RANGE OF A RADAR is most frequently described as being "160 miles" or some other "Range" which is, most of the time, translated to mean "STATUTE MILES', which IS NOT an accurate description. Mileage Scales are as follows;
Statute Mile = 1760 statute yards
Nautical Mile = 2023 statute yards
RADAR MILE = 2000 statute yards
DATA MILE = 2000 statute yards

Distance Scales on most Military Maps use the "Statute" Mile to determine the location of units with respect to each other. However, to be accurate in determining and reporting the POSITION of target returns, the RADAR MILE SCALE MUST be used, and therefore, a DATA MILE MUST equal a RADAR MILE ! - Since Military Maps are used to determine Ground Environment Unit Locations, a conversion from "STATUTE" to "DATA" miles must be performed, to ensure the accuracy of the data reported.

SECOND - Another requirement to ensure the accuracy of data exchange is that ALL PARTICIPATING RADARS MUST BE ORIENTED TO THE SAME POINT. Because the USAF ORIENTS it's GROUND RADARS to TRUE NORTH, it is necessary that ARMY ADA RADARS also be ORIENTED TO TRUE NORTH, (The DOD/NATO definition of TRUE NORTH is "the direction from an observer's position to the GEOGRAPHIC NORTH POLE).

CARTESIAN COORDINATES SIMPLY PUT - the Cartesian Coordinate system consists of a number of SQUARE BOXES superimposed over a portion of the earths surface, each SQUARE BOX representing a Participating Unit within, in this case, the Air defense Network.

The LARGEST BOX is known as the MASTER GRID, and the lower left corner of that Grid is known as the DATA LINK REFERENCE POINT (DLRP). THE PARTICIPATING UNIT BOXES ALL HAVE THEIR DATA REFERENCED TO THAT POINT. The Participating Units will have smaller boxes proportional in size to their areas of responsibility known as LOCAL GRIDS (i.e.; THE CRC LOCAL GRID will be larger than the AADCP LOCAL GRID, and the AADCP LOCAL GRID will be larger than ALL of it's subordinate Units, so that they are ALL contained within the AADCP LOCAL GRID.

THE HORIZONTAL area of each box is known as the X AXIS, while the VERTICAL area is known as the Y AXIS. There is also a HEIGHT(H) AXIS, but that will make this explanation overly complex to describe (Besides, I may really make a mess of this portion of my narrative - LET'S JUST SAY I DO NOT HAVE THE GUTS TO EVEN TRY TO EXPLAIN HOW THE HEIGHT(H) AXIS WORKS !!!!!!)

A participating unit IS LOCATED AT THE CENTER OF IT'S BOX. The dimensions of the Subordinate Units boxes are determined by the RADIUS of the MAXIMUM RANGE of it's collocated Radar. In the case of the 94th ADA Group, the subordinate Units were ALL Nike Hercules Batteries, and each had a High Power Acquisition Radar (HIPAR) with a Range of 160 DATA MILES - meaning that a Hercules Battery BOX was 320 DATA MILES in the X AXIS, and 320 DATA MILES in the Y AXIS, with the Unit at the CENTER of the BOX. When the BOX is divided in the X AXIS and the Y AXIS through the CENTER, FOUR (4) QUADRANTS are created. Going Clockwise,

the 1st Quadrant (upper right) data coordinates will be PLUS X and PLUS Y,
the 2nd Quadrant (lower right) data coordinates will be MINUS X and PLUS Y.
the 3rd Quadrant (lower left) data coordinates will be MINUS X and MINUS Y, and
the 4th Quadrant (upper left) data coordinates will be PLUS X and MINUS Y.

The PLUS or MINUS signs will govern the ADDITION or SUBTRACTION of the PARALLAX Data from an incoming data message.

A simple example describing the process, would be if two units are 100 Data Miles apart, along the X Axis. Label the unit on the LEFT - AADCP, and the unit on the RIGHT - Battery A. The AADCP detects a target aircraft 150 Data Miles from IT'S LOCATION. The 100 Data Mile distance between the AADCP and Battery A, becomes Battery A's PARALLAX WITH RESPECT TO THE AADCP. When the AADCP transmits the coordinate DATA of the target to Battery A, and it is received by Battery A, Battery A will compare the AADCP's coordinate Data to it's PARALLAX settings, and determine that the target is 50 DATA MILES to the right (East) of IT'S LOCATION, where the target data will be displayed on it's PPI.

This is a good point to describe the BIT VALUES of the X and Y COORDINATE DATA WORDS which are transmitted and received as a part of ALL POSITIONAL DATA exchanged between Participating Units. The BIT VALUE is the same for both the X and Y WORDS contained in exchanged messages (A BIT is a Binary value associated with EACH DATA SEGMENT of the exchanged messages - A Value of ONE (1) indicates DATA is present; a Zero (0) indicates NO DATA is present);

Bit 1 = 312.5 Yards
Bit 2 = 625 Yards
Bit 3 = 1250 Yards
Bit 4 = 2500 Yards
Bit 5 = 5000 Yards
Bit 6 = 10000 Yards = 5 Data Miles
Bit 7 = 10 Data Miles
Bit 8 = 20 Data Miles
Bit 9 = 40 Data Miles
Bit 10 = 80 Data Miles
Bit 11 = 160 Data Miles
Bit 12 = 320 Data Miles

To illustrate, if a target is at a range of 75 Data Miles, Bits 6, 7, 8, 9 would all contain a binary one (1) in their data segments, while ALL the other data segments would contain binary zeros (0)[NOTHING THERE] in their data segments.


The task of computing the Parallax settings of the 94th ADA Group Units was, more than likely, delegated to CWO RICHARD LEE, and he was probably aided by Hughes Aircraft's John Langemak. As indicated in the AADCP Roster above, Dick (also affectionately known as "TRICKY DICK") WAS TRAINED AS AN RDPC MAINTENANCE OFFICER, BUT NEVER served in that capacity. Instead, he functioned as a TECHNICAL/OPERATIONAL ADVISER to the AADCP and Group Commanders, ALL of whom, placed a VERY DESERVING HIGH VALUE on his aid and assistance, in their efforts to maximize the capabilities of the AN/MSG-4 and AN/MSQ-28 Systems.

HILL 479
94th Arty AADCP


1. AN/MSQ-28B AADCP on Hill 479

2. MSQ-28B RDPC interior

3. MSQ-28B WMC interior

4. Commo towers at another site as seen from Hill 479
Probably a communications site of some type. Site is located on a hill close to HILL 479.

Can anybody provide details on the USAF or Army unit operating this commo site in the mid 1960s and its mission?
(Email from Keith Fleisch)
It is only an uneducated guess, but the unidentified unit near hill 479 might have belonged to the 601st Tactical Control Group. The headquarters and CRC (M) operated from Sembach AB with 7-9 CRP's fanned out across Germany and an unknown number of forward detachments nearer the ADIZ. Also attached were some ground forward air control members and a special ops team. Elements of this unit were constantly deployed during this time period, almost always with US Army units. They were capable of setting up and operating a large variety of radar and communications equipment. I realize this is nothing concrete, but might open another channel to investigate.

(Source: Email from Lewis Wood, 32nd AADCP, 1961-62)
Q: Was the Army element at Langerkopf a detachment of the 32nd Arty Bde or the 94th Arty Gp? Was it an MCC (Missile Control Center)?

The Army element was definitely 32nd Artillery Brigade. The unit designation was 32nd AADCP. Our CO at Langerkopf was a Major Antonio J. Buldoc (spelling is as I remember it, but it could have been with 2 l's.).

The MCC functions were held by the 94th Group operating out of Hill 479 above beautiful Bann, Germany. (I was also stationed there, and I got to see a farmer plowing with a cow.)

Q: Was the Langerkopf site a CRC (command and reporting center) or SOC (sector operations center) or both? I have some information that indicates the SOC was moved from Langerkopf to Börfink but I don't know when.

Langerkopf was the SOC, and the Army unit AADCP was a liaison with the Air Force. The AF handled fighter interceptions and the Army handled assigning Hercules and other missiles to destroy in flight. The AF had a big manual plotting board at one end of the shed, and the Army had a computer to pass assignments on to the folks at (Hill) 479. They did the talking to -- assignments to -- the batteries.

AADCP and 479 were connected by a data line. I was in Maintenance at the AADCP, and we had a Hughes SRS II (also known as AN/MSQ-21) computer (built in the desert circa 1952/1953 and moved into the Langerkopf location strictly for the liaison mission.)

479 had a later generation computer -- built into a 35-or-so foot trailer for mobility -- also from Hughes Aircraft Company.

More on the SRS II -- many of the semi-conductors used had been experimental when the circuits were originally designed and built, and several of them had to be especially grown for us when we needed replacements for those which fried or aged out of their desired paradigms.

Q: Can you give me some details on the CRC, SOC, and/or MCC organizations?

At Langerkopf (SOC) the operators were all officers. As I said, I was an enlisted maintenance PFC. 18 of us went to an on-site computer repair school on the SRS II. The Army didn't want enlisted men controlling the launch of nukes -- go figure! The Army decided that they wanted to continue the Hughes contract for maintenance, so we who had graduated from electronics school were moved over to 497.

I pulled maintenance duty and parts supply technician duties on the WMC computer (Weapons Monitoring Center). Other divisions included Operations, Radar, and Support.

We were quartered with Hq&Hq Co of 94th Arty in Kleber Kaserne. The CO (who was an administrative type, neither Operations or Maintenance, more a chief typist) was a Captain. I didn't particularly care for the man -- I was a PFC working in an E-5 slot and he single-handedly kept me from getting E-4. 3 NCO's on the promotion board quit over that one. Anyway, rather than re-enlisting (What a waste of money -- the government paid nearly $60,000 for each of us who became electronic techs), I went back to college, BA, MA, and a dissertation away from a PhD and I paid for it all as an electronic technician.

(Source: Email from Dave Jungers)
I arrived in Germany around June 1959. After an overnite in Frankfurt I was transported to Dexheim. Spent the weekend there and on Monday morning was driven to the 32nd AAA Bde at Kapaun Barracks. I don't recall how long I was there but long enough to be put on "make work" details (typical Army BS).

One day I was driven to an Air Force site which was the 603rd AC&W Sq. I met the OIC who was a Major Kingston, later on replaced by a Captain Swann. The Air Force base commander was a LT COL Koszarek. I was assigned to Charlie Crew and began 14 months of 8-5 on days....24hr break......either 5-midnite swing or midnite-8 graveyard shifts. I loved it!!!

I was part of an Army Defense Command Post. All of our units used the Ajax missile. The Hercs hadn't been deployed yet. We communicated to the various units via telephone. Our call sign was COLLIE. The unit signs were CHAPTER, COSINE, CHEERFUL, COMPROMISE...there were 2 others but I forget their names.

The AF isn't as military as the Army as we had only one inspection in the 14 months I was there. Army MPs couldn't touch us if we were out after curfew. We had Air Force passes which allowed us to be absent when not required for duty.

In August 1960 I rotated back to CONUS. I was an Sp/4 (E-4) and was promised buck sgt stripes if I re-inlisted. I was willing to extend for a year but they wouldn't buy it. So on 8/2/60 I was transported by rail to Bremerhaven where I boarded the MAURICE ROSE for the 10 day trip to the Brooklyn Army Terminal (which we never saw) eventually boarding a plane for Oakland at Newark and discharge (8/12/60.)

Hopefully I have answered a few of your questions. I am now 67 and my European service seems like yesterday......the best time of my life.

At first we were in a tent-like structure where all missions were conducted. Operations was in a separate building. About 1-2 months before I left a new building was opened for all conducted missions. As far as I can remember,operations also was moved to this new building.

In 1983 I returned to the site and the buildings where I lived and worked no longer existed. In fact most of the AF personnel there were WAFs. Just my luck!

We used the same scopes as the Air Force used plus one man on Early Warning. In our crew the same man usually pulled early warning but I did it also as I recall.... There were approx 60-75 EM's divided equally in three crews... Alpha, Bravo, Charlie (I was in Charlie.)

We worked days 8-5, swing 5-midnite and midnite-8am. The swing/midnite shifts we rotated..... We had officers assigned to each crew. My crew had a Major (in charge), one or two Lts and two WO's. They did not live on post..... All three crews had their separate barracks.

We only had one inspection in the 14 months I was there.The barracks looked like buildings you would see in the movies "Stalag 17" and "The Great Escape". I had to paint one so I should know. Cement floors, coal burning stove, wood wall/foot lockers...primitive even in those days. German civilians came in from time to time to do needed maintenance or to bum cigarettes. One even gave me an authentic Nazi flag which I still have.

We had, between our midnite and day shifts three days off and we could go anywhere we wanted as we had Air Force passes, not restricted as to time as were the Army passes. We had fun with the MP's when we were stopped. They couldn't do anything to us except give us a lot of lip service/BS!

(Source: Email from Michael Dane, 94th ADA GOC, Bann Hill, 1979-81)
I arrived in Germany in September 1979 and was assigned the 94th as a 16H. I originally stayed at Kleber Kaserne in K Town and worked on Bann Hill at the Group Operation Center. We had brand new AN/TSQ-73 Missile Minders and shared the site with the 108th Hawk guys. There was also a Signal Battalion there keeping our communications going. I believe we replaced the MCC.

The AN/TSQ-73 was a Patriot comand and control system but we used it at that time for the NIKE's. I worked in the control van that monitored the status of the firing batteries and called up units to various states of readiness to insure that we could meet the state of alert. This included PAL and nuclear control orders. We had top secret security clearance for this.

Later we stayed at Landstuhl (GOC enlisted guys) on the hill behind the hospital near the movie house and liquor store. We had a major in charge of us and a bunch of captains to keep things working 24/7.

I worked out a deal to get TDY work at the AFRC in Garmisch for the winter of 80-81 as a ski patroler. And ETS'ed in May if 81 so I never got back to work on the hill after ski patrol ended.

I am thankful each day that I am no longer in the Army and pulling shift work is something I will never do again as long as I live. I just wanted to let you know that the GOC did exist and it was in Bann. All of our equipment was brand new in 1979 and the guys from Litton were there working out the bugs in the AN/TSQ-73. I remember watching all the air traffic over Western Europe on it's radar screens and how nice and cool it was in there in the summer. We also had USO shows sometimes as we were considerd a remote site although we were very close to K-Town and Ramstein AFB. I could see the AFB from my desk and remember watching the air show from the hill.
Michael W Dane

AN/TSQ-73 Missile Minder
(Source: Air Defense Trends, March 1972)
AN/TSQ-78 Named Missile Minder
The Army's latest command, control, and coordination system AN/TSQ-78, now under development with Litton Industries as the prime contractor, has been named Missile Minder. The AN/TSQ-78, which includes both brigade/group and battalion level systems, will replace the AN/MSG-4 (Missile Monitor) system currently deployed overseas.

(Shortly after this report, the name of the AN/TSQ-73 was changed to "command and control system." The same was the case for the MSG-4.)

Battalion Operations Center
(Source: ROTCM 145-70, Branches of the Army, Oct 1963)
NIKE Air Defense Artillery Battalion

The battalion is normally the basic administrative unit in air defense artillery organizations. It consists of a headquarters and headquarters battery and four missile batteries.

Air defense artillery battalions in the field army exercise tactical control over the assigned missile batteries through a battalion fire distribution system.
BOC Equipment
2/56th Arty (Hill 486)

1. IFC/BOC site overview

2. VHF Radio van

3. AN/GSS-1 Radar van

4. Commo room in the BOC bldg

5. Inside of MSQ-18 van

5. AN/MSQ-18 Operations Central van

7. VHF Commo at the site

8. VHF antenna mast

9. VHF radio antennas

10. UHF tower

11. Total view of BOC

12. IFC/BOC site

Integrated Fire Control
(Source: ROTCM 145-70, Branches of the Army, Oct 1963)
NIKE Operation
The same basic concept of operation and command guidance is used for NIKE-AJAX and NIKE-HERCULES. To understand how either NIKE works, only the major items of equipment need be considered -- a computer and three radars.

The acquisition radar detects a target, which is then designated to a target tracking radar (TTR). The TTR locks on the target; tracks it; and measures the range, azimuth, and elevation angle to the target; and continuously sends these data to the computer. A third radar, the missile tracking radar (MTR), locks on the missile and measures its range, azimuth, and elevation angle, and continuously sends this information to the computer. The electronic computer, knowing the location of the target and missile, continuously directs the missile to the target. When the missile nears the target, the computer commands the warhead to detonate.
IFC Equipment
2/56th Arty (Hill 486)

1. Partial view of IFC area

2. Partial view of IFC area

3. IFC

4. IFC

5. TTR and TRR

6. LOPAR and MTR

2-56th Arty

HILL 486 (Salzwoog)


1. Early view of VHF Radio Van

2. BOC's driveway area

3. HHB motor pool mechanics

80-foot UHF tower

BOC 2-56th Arty - Daily Commo Check

Commo Check List
  We used this check list at the BOC on a daily basis! 

"BOC," self-explanatory; "CBL," Cowboy Lima (32nd AADCOM MCC); "CINN," Cinnamon
(94th Group WMC) [or AADCP, as you may prefer!]; "05A - 05D," our firing batteries.... 

hand, I would say [guess!] that Tactical Operations was the "hot loop" (loudspeaker); IRR and Command were "normal" military phones; Administrative (Channel Two) was German commercial phone service; and, of course, ADL was the Automatic Data Link (non-voice).... ("LL" is Land Line, and "UHF" is ... duh! ... UHF radio....)  [Crews "changed shift" at 0800: hence, "our" commo checks for the day began then (rather than 0100 - 2400)....] 

I do not even remember how we filled this doggoned thing out!!  Maybe we just checked the
many different "connections" to our widespread "customers" randomly ... on a hourly basis?

On those rare occasions when there WAS "a commo problem," we found out about it PDQ!

(C) [FM] 44-13, U.S. Army Fire Direction System, AN/MSG-4 (Missile Monitor) (U);
(C) [TM] 11-5895-292-10, Operator's Manual: Antiaircraft Defense System AN/MSG-4 (U)"

The manuals themselves were classified (C); at least their titles were unclassified (U)

ADA Communications
ADA Communications Requirements in the Field Army
(Source: ST 44-183, Air Defense Artillery Communications, US Army Air Defense School, November 1966)

ST 44-183, Nov 1966
  Chapter 11, Pages 255 - 274.
Air defense artillery communications systems
General; Army Area Communications System
Army Area Communications System (cont'd)
Army Area Communications System (cont'd) + graphic; Communications Requirements
Communications Requirements (cont'd)
Graphic: ADA primary communications in the field army
Communications Requirements (cont'd)
Communications Requirements (cont'd); Army Air Defense Command Post
Graphic: Air defense artillery backup nets
Army Air Defense Command Post (cont'd)
Communications nets in Nike Hercules and HAWK units in the Field Army
Graphic: Nike Hercules battalion command and administrative net
Communications nets in Nike Hercules and HAWK units in the Field Army (cont'd)
Graphic: Nike Hercules tactical nets
Graphic: HAWK battalion command and administrative net
Communications nets in Nike Hercules and HAWK units in the Field Army (cont'd)
Communications nets in Nike Hercules and HAWK units in the Field Army (cont'd); Communications in air defense artillery AW (SP) units
Graphic: HAWK tactical net
Communications in air defense artillery AW (SP) units (cont'd); Proposed use of new radios
Proposed use of new radios (cont'd)
Table: ADA radio equipment in the field army


Related Links:
Association of Old Crows - Golden Gate Chapter - site for professionals engaged in the sciences of Information/Electronic Warfare; includes a very nice tutorial on radar in general and Early Warning Radar in particular.
Ed Thelen's Nike Missile Web Site - a superb web site that presents a vast amount of Nike Hercules historical, technical and operational information.
Kommandobunker - a very interesting German web site that highlights some of the efforts to turn the CRC bunkers at Boerfink, Freising and Lauda and the radar site on top of the Wasserkuppe into monuments/museums of the Cold War.