HACS explained

High Angle Control System (HACS) was a British anti-aircraft fire-control system employed by the Royal Navy from 1931 and used widely during World War II. HACS calculated the necessary deflection required to place an explosive shell in the location of a target flying at a known height, bearing and speed.

Early history

The HACS was first proposed in the 1920s and began to appear on Royal Navy (RN) ships in January 1930, when HACS I went to sea in .[1] HACS I did not have any stabilization or power assist for director training. HACS III which appeared in 1935,[2] had provision for stabilization, was hydraulically driven, featured much improved data transmission and it introduced the HACS III Table.[3] The HACS III table (computer) had numerous improvements including raising maximum target speed to 350 knots, continuous automatic fuze prediction, improved geometry in the deflection Screen, and provisions for gyro inputs to provide stabilization of data received from the director.[4] The HACS was a control system and was made possible by an effective data transmission network between an external gun director, a below decks fire control computer, and the ship's medium calibre anti-aircraft (AA) guns.

Development

Operation

The bearing and altitude of the target was measured directly on the UD4 Height Finder/Range Finder, a coincidence rangefinder located in the High Angle Director Tower (HADT). The direction of travel was measured by aligning a binocular graticule with the target aircraft fuselage. The early versions of HACS, Mk. I through IV, did not measure target speed directly, but estimated this value based on the target type. All of these values were sent via selsyn to the HACS in the High Angle Calculating Position (HACP) located below decks.[5] The HACS used these values to calculate the range rate (often called rate along in RN parlance), which is the apparent target motion along the line of sight. This was also printed on a paper plot so that a range rate officer could assess its accuracy.[6]

This calculated range rate was fed back to the UD4 where it powered a motor to move prisms within the UD4. If all the measurements were correct, this movement would track the target, making it appear motionless in the sights.[7] [8] If the target had apparent movement, the UD4 operator would adjust the range and height, and in so doing would update the generated range rate, thereby creating a feedback loop which could establish an estimate of the target's true speed and direction.[9] [10] The HACS also displayed the predicted bearing and elevation of the target on indicators in the Director tower, or on later variants,[11] the HACS could move the entire Director through Remote Power Control so that it could continue to track the target if the target became obscured.[12]

The angle measured by the graticule also caused a metal wire to rotate around the face of a large circular display on one side of the HACS, known as the Deflection Display. The measured value of altitude and range, and estimated value of target speed, caused optics to focus a lamp onto a ground glass screen behind the wire, displaying an ellipse whose shape changed based on these measures. The deflection operator used two controls to move additional wire indicators so they lay on top of the intersection of the outer edge of the ellipse where it was crossed by the rotating metal wire.[13] The intersection of the ellipse and the target direction was used as a basis for calculating elevation and training of the guns. The ellipse method had the advantage of requiring very little in the way of mechanical computation and essentially modelled target position in real-time with a consequent rapid solution time.[14]

Information flow

The HADT provides target direction, range, speed, altitude and bearing data to the HACP, which transmits direction and fuse timing orders to the guns. The HACP transmits the computer generated range rate and generated bearing back to the HADT, creating a feedback loop between the HADT and HACP, so that the fire control solution generated by the computer becomes more accurate over time if the target maintains a straight line course. The HADT also observes the accuracy of the resulting shell bursts and uses these bursts to correct target speed and direction estimates, creating another feed back loop from the guns to the HADT and thence to the HACP, again increasing the accuracy of the solution, if the target maintains a straight line course.[15] Most guns controlled by the HACS had Fuze Setting Pedestals or Fuze Setting Trays where the correct fuze timing was set on a clockwork mechanism within the AA shell warhead, so that the shell would explode in the vicinity of the target aircraft.

Target drones

The HACS was the first Naval AA system to be used against radio controlled aircraft, and achieved the first AA kill against these targets in 1933.[16] In March 1936, six Queen Bee targets were destroyed by the RN Mediterranean Fleet during intensive AA practice at a time of extreme tension between the UK and Italy.[17] Target practice against target drones was carried out using special shells which were designed to minimize the possibility of destroying expensive targets.[18] [19] The RN allowed media coverage of AA target practice and a 1936 newsreel has footage of an actual shoot.[20] In 1935 the RN also began to practice HACS controlled shoots of target aircraft at night.[21]

Tachometric and radar additions

The RN moved quickly to add true tachometric target motion prediction and radar ranging to the HACS by mid 1941. The RN was the first navy to adopt dedicated FC AA radars. However the system, in common with all World War II-era mechanical AA fire control system still had severe limitations as even the highly advanced United States Navy (USN) Mk 37 system in 1944 needed an average of 1,000 rounds of 5adj=onNaNadj=on ammunition fired per kill.[22] In 1940 the Gyro Rate Unit (GRU) was added to the HACS system, an analogue computer capable of directly calculating target speed and direction,[23] converting the HACS into a tachymetric system.[24] [25] Also in 1940, radar ranging was added to the HACS.[26] The GRU and its associated computer, the "Gyro Rate Unit Box" (GRUB) no longer assumed straight and level flying on the part of the target. GRU/GRUB could generate target speed and position data at angular rates of up to 6 degrees per second, which was sufficient to track a 360kn crossing target at a range of .[27]

The Fuze Keeping Clock

See main article: Fuze Keeping Clock. RN destroyers were hampered by the lack of good dual-purpose weapons suitable for ships of destroyer size; for much of the war 40° was the maximum elevation of the 4.7adj=onNaNadj=on guns equipping such ships, which were consequently unable to engage directly attacking dive bombers, although they could provide "barrage" and "predicted fire" to protect other ships from such attacks.[28] Destroyers did not use HACS, but rather the Fuze Keeping Clock (FKC), a simplified version of HACS.[29] Starting in 1938 all new RN destroyers, from the onwards, were fitted with a FKC and continuous prediction fuse setting trays for each main armament gun.[30] WWII experience from all navies showed that dive bombers could not be engaged successfully by any remote computer-predictive AA system using mechanical fuzes[31] [32] due to the lag time in the computer and the minimum range of optical rangefinders.[33] In common with other contemporary navies, pre-war designed RN destroyers suffered from a lack of short-range, rapid-fire AA with which to engage dive bombers.

The Auto Barrage Unit

The Auto Barrage Unit or ABU, was a specialized gunnery computer and radar ranging system that used Type 283 radar. It was developed to provide computer prediction and radar anti-aircraft fire control to main and secondary armament guns that did not have inherent anti-aircraft capability. The ABU was designed to allow the guns to be pre-loaded with time fused ammunition, and it then tracked incoming enemy aircraft, aimed the guns continuously to track the aircraft, and then fired the guns automatically when the predicted aircraft position reached the preset fuse range of the previously loaded shells.[34] The ABU was also used with guns that were nominally controlled by the HACS to provide a limited blind fire capability.[35] [36]

Wartime experience

By May 1941, RN cruisers, such as, were engaging the Luftwaffe with stabilized HACS IV systems with GRU/GRUB and Type 279 radar with the Precision Ranging Panel, which gave +/- 25 yd accuracy out to 14,000 yds. HMS Fiji was sunk in the Battle of Crete after running out of AA ammunition but her HACS IV directed 4-inch AA gun battery fended off Luftwaffe attacks for many hours.[37]

Demonstrating the RN's rapid strides in naval AA gunnery, in May 1941, HMS Prince of Wales went to sea with HACS IVGB, with full radar ranging systems, and nine AA associated fire control radars: four Type 285 radar, one on each High Angle Director Tower (HADT) and four Type 282 radar, one on each Mk IV director for the QF 2 pdr (40mm) "pom pom" mounts, and a long range Type 281 radar Warning Air (WA) radar which also had precision ranging panels for aerial and surface targets.[38] This placed HMS Prince of Wales in the forefront of naval HA AA fire control systems at that time. In August and September 1941, HMS Prince of Wales demonstrated excellent long range radar directed AA fire during Operation Halberd.[39] Although the shortcomings of HACS are often blamed for the loss of Force Z, the scope of the Japanese attack far exceeded anything the HACS had been designed to handle in terms of aircraft numbers and performance. The failure of anti-aircraft gunnery to deter the Japanese bombers was also influenced by unique circumstances. The HACS was originally designed with Atlantic conditions in mind and Prince of Waless AA FC radars had become unserviceable in the extreme heat and humidity in Malayan waters and her 2-pdr ammunition had deteriorated badly as well.[40]

The RN made the following claims for ship borne anti-aircraft fire against enemy aircraft, from September 1939 up to 28 March 1941: :Certain kills: 234, Probable kills: 116, Damage claims: 134[41]

The RN made the following claims for ship borne anti-aircraft fire against enemy aircraft, from September 1939 up to 31 Dec 1942:[42]

Certain kills: 524

Probable kills: 183

Damage claims: 271

Certain kills: 216

Probable kills: 83

Damage claims: 177

Total kill claims: 740

Total probable claims: 266

Total damage claims: 448

Radar and the Mark VI Director

HACS used various director towers that were generally equipped with Type 285 as it became available. This metric wavelength system employed six yagi antennas that could take ranges of targets, and take accurate readings of bearing using a technique known as "lobe switching" but only crude estimates of altitude. It could not, therefore, "lock on" to aerial targets and was unable to provide true blindfire capabilities, which no other navy was able to do until the USN developed advanced radars in 1944 using technology transfers from the UK. This situation was not remedied until the introduction of the HACS Mark VI director in 1944 that was fitted with centimetric Type 275 radar. Another improvement was the addition of Remote Power Control (RPC), in which the anti-aircraft guns automatically trained with the director tower, with the necessary changes in bearing and elevation to allow for convergent fire. Previously the gun crews had to follow mechanical pointers that indicated where the director tower wanted the guns to train.[43]

HACS systems in use or planned in August 1940

HACS Directors fitted to ships in a document dated as "revised Aug 1940":[44]

HMS Ajax, Galatea, Arethusa, Coventry, HMAS Hobart, Sydney, Perth

HMS Penelope, Southampton, Newcastle, Malaya, Hood*, Australia*, Nelson*, Royal Sovereign*, Barham*, Resolution*, Cairo*, Excellent (gunnery training school)*, Revenge*, Calcutta*, Carlisle*, Curacoa*, Exeter*, Adventure*, Warspite*. Ships marked with * had roll stabilization for layer.

HMS Birmingham, Sheffield, Glasgow, Aurora, Liverpool, Manchester, Gloucester, Dido, and Fiji classes, Forth, Maidstone, Renown, Valiant, Illustrious, Formidable and Ark Royal.

and es.

HMS King George V and Prince of Wales, Dido and Fiji classes.

HMS Duke of York, Anson and Howe.

HMS Indomitable, Implacable and Indefatigable.

See also

External links

Notes and References

  1. Weapon Control in the Royal Navy 1935-45, Pout, from The Application of Radar and other Electronic Systems in the Royal Navy in WW2, p87 (Kingsley-editor)
  2. Appendix one, Classification of Director Instruments, see external links.
  3. Weapon Control in the Royal Navy 1935-45, Pout, from The Application of Radar and other Electronic Systems in the Royal Navy in WW2, p87,99 (ed Kingsley)
  4. HACS III Operating Manual Part 1, paragraph 2 (a-o)
  5. British Mechanical Gunnery Computers of World War II, Bromley, p19
  6. The Gunnery Pocket Book, B.R. 224/45, 1945, paragraphs 429-431. See external links
  7. HACS III Operating Manual Part 2, paragraph 300,301
  8. HACS III Operating Manual Part 1, paragraph 2 (a)
  9. Weapon Control in the Royal Navy 1935-45, Pout
  10. British Mechanical Gunnery Computers of World War II, Bromley, p22
  11. Naval Weapons of World War Two, Campbell, p. 30
  12. HACS III Operating Manual Part 2, paragraph 174 (a)
  13. The Gunnery Pocket Book, B.R. 224/45, 1945, paragraphs 424. See external links.
  14. British Mechanical Gunnery Computers of World War II, Bromley, p19, figure 18
  15. British Mechanical Gunnery Computers of World War II, Bromley
  16. Unmanned Aviation, Newcombe, p47
  17. The British Defense of Egypt, 1935-40, Morewood.P70-71
  18. UK Hansard, Queen Bee Aircraft (shooting practice).HC Debate07 June 1939 volume 348 column 427W:
  19. The Naval Review, A Misleading Success, July 1978, Jones, Basil, p254:
  20. https://www.youtube.com/watch?v=MSPmr-7MLrc HACS Target practice video
  21. ADM 186/339: Progress in naval gunnery, 1914-1936, p132. See external links
  22. Naval Weapons of WW2, Campbell, P106. This data in turn was based upon USN wartime AA kill claims, and so probably overstates the system's effectiveness.
  23. HACS III Operating Manual Part 1, paragraph 56,61
  24. Weapon Control in the Royal Navy 1935-45, Pout, p104, from The Application of Radar and other Electronic Systems in the Royal Navy in WW2 (Kingsley-editor)
  25. British Battleships of World War Two, Raven & Roberts, p378:
  26. Weapon Control in the Royal Navy 1935-45, Pout, p97
  27. Naval Weapons of WW2, Campbell, pp. 17–18
  28. Tribal Class Destroyers, Hodges, p27
  29. Naval Weapons of WW2, Campbell, p19
  30. Tribal Class Destroyers, Hodges, p27
  31. Summary of USN and RN gunnery reports. For example, the USS Enterprise reported her Mk 33 AAFC system as "ineffective" against dive bombers. USS ENTERPRISE CV6/A16-3/(10-My)
  32. US Destroyers-An Illustrated Design History, Friedman, p203:
  33. HACS III Operating Manual Part 2
  34. https://maritime.org/doc/br224/part4.htm#par446 The Gunnery Pocket Book, paragraph 448
  35. Campbell, Naval Weapons of World War Two, p16.
  36. Victor Humphries, HMS Renown WWII: "I was a radar RP3 rating on board HMS Renown during WW2. During which time I operated the ABU, which was very reliable; the set itself was not very big, the CRT being about 9 inches in diameter. The screen showed two green lines, the top one straight across the screen and the lower line had about a 1/4-inch step which was moved across the screen with a steering wheel situated below and to the left, which had a smaller steering wheel attached to it so that on moving the larger steering wheel to keep the step steady on the left side of the echo. Once I was satisfied that the aircraft was moving in at a steady speed, I could LOCK on with the small steering wheel and the stepped line would close in with the echo. There was an indicator on the screen at 5000 yards; when the aircraft was inside this range I could see by a green light that all guns were loaded, cocked, and ready to fire; all I then had to do was depress a foot pedal which fired ten 4.5-inch guns, either on the port or starboard sides. If the aircraft echo produced a downward echo every so many seconds (the number of seconds decided just before the operation) it would indicate IFF = identification friend or foe, which meant it was our own aircraft, if there was no IFF and the pilot did not break radio silence he could be shoot down. We also had long range aircraft warning Radar Type 281, which would warn of approaching enemy aircraft 150 miles away, and at WW2 aircraft speeds we had time to prepare. The types 273 & 284 are another story."
  37. The true experiences of Mr Leonard Charles Eades during the Second World War, from the HMS Fiji Association.
  38. The Development of Radar Equipments for the Royal Navy, Kingsley, p383.
  39. The Royal Navy and the Mediterranean Convoys. A Naval Staff History, p26
  40. Battleship: The Loss of the Prince of Wales and the Repulse, Middlebrook
  41. March, British Destroyers, p. 434.
  42. United States Navy, AntiAircraft Action Summary, July 1942 to Dec 1942 (Information Bulletin No. 22), pp. 281–282.
  43. Weapon Control in the Royal Navy 1935-45, Pout, pp. 105-106.
  44. Appendix one, Classification of Director Instruments.
  45. Uses FKC AAFC table according to Campbell.