Mark XIV bomb sight

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:Mk. XIV sighting head.jpg
The Mk. XIVA sighting head, which would be mounted in the front of the aircraft and connected to the computor by the cables coiled up on the left. This example is found in the RAF Museum's reserve collection.
File:Mk. XIV computor.jpg
The Mk. XIVA computor, normally mounted on the left side of the forward fuselage. The wind speed and direction are set on the blue dials, the bomb's terminal velocity and the target altitude on the green dials.

The Mark XIV Computing Bomb Sight[lower-alpha 1] was a vector bombsight developed and used by the Royal Air Force's Bomber Command during the Second World War. The bombsight was also known as the Blackett sight after its primary inventor, P.M.S. Blackett. Production of a slightly modified version was also undertaken in the United States as the Sperry T-1, which was interchangeable with UK-built version.

Developed in 1939, the Mk. XIV started replacing the First World War-era Course Setting Bomb Sight in 1942. The Mk. XIV was essentially an automated version of the Course Setting sight, using a mechanical computer to update the sights in real-time as conditions changed. The Mk. XIV required only 10 seconds of straight flight before the drop, and could account for shallow climbs and dives as well. More importantly, the Mk. XIV sighting unit was much smaller than the Course Setting sight, which allowed it to be mounted on a gyro stabilization platform. This kept the sight pointed at the target even as the bomber manoeuvred, dramatically increasing its accuracy and ease of sighting.

The Mk. XIV was theoretically less accurate than the contemporary Norden bombsight, but was smaller, easier to use, much more quick-acting, and better suited to night bombing. It equipped the majority of the RAF's bomber fleet; some Stabilized Automatic Bomb Sights and Nordens were used in specialist roles. In spite of being much simpler than tachometric designs, or because of that, the Mark XIV remained in use long after the war, including in the V Bomber fleet.

History

Course setting sights

A problem with early bombsights was that they could only correct for the effects of wind in a simple way, and required the bomber to fly directly up- or down-wind from the target to minimise the complexity of the required calculations. This made it difficult to attack moving targets, and allowed anti-aircraft artillery to pre-sight their weapons along the wind line.[1]

In 1917 Harry Wimperis introduced the Course Setting Bomb Sight (CSBS), which replaced the tables and timings with a simple mechanical calculator capable of solving the sideways drift due to wind. As the bomb aimer turned a wind direction knob, the main portion of the sight was pushed to the left or right, indicating the required angle to fly. The CSBS was the first bombsight that allowed the bomber to approach the target from any direction, which offered greatly increased tactical freedom.[2]

The downside to the CSBS was that the settings, made through four main input dials, were useful for only a single given operational setup – a given altitude, heading, etc. If the aircraft manoeuvred, the entire system had to be re-set. Also, the direction indicated by the system was not the direction of the nose of the aircraft, but the angle to fly compared to the ground. Checking to see if the aircraft was flying along the correct heading required a time consuming process of trial and error, sighting through thin metal wires against a suitable object below. As the sight was not stabilized, any manoeuvres to correct for mis-alignment interfered with the ability to measure the heading, so these corrections further extended the required bomb run. The CSBS generally required the bomber to fly straight and level for a lengthy time.[3]

Although the need for an improved CSBS was known in the 1930s, little work on developing such a sight was carried out. That was because an entirely new class of bombsights were being developed, the tachometric designs, which offered dramatically improved accuracy while at the same time automating much of the setup. The RAF was working on the Automatic Bomb Sight along these lines, but development was slow and it had not been accepted for use when the war started. Additionally, the Air Ministry had been in extensive negotiations with the US Navy in an effort to gain a licence for the similar Norden bombsight. The Navy constantly refused these requests, based on arguments about secrecy and various political issues.[4]

As the war started, therefore, updated versions of the CSBS, the Mk. VII and Mk. IX, remained universal. A more significant upgrade, the Mk. X, was in widespread production and being readied for service entry.[5]

A pressing need

On 18 December 1939, Vickers Wellington bombers carried out a raid on German shipping in what would become known as the Air Battle of the Heligoland Bight. Detected on radar and attacked en route to their targets, the CSBS' demand that they fly straight and level made the bombers easy targets for both fighters and anti-aircraft gunners. Over half the attacking force was destroyed or damaged beyond repair.[3]

On 22 December 1939, at a pre-arranged meeting on bombsight policy, Air Chief Marshal Sir Edgar Ludlow-Hewitt of RAF Bomber Command stated flatly that the CSBS did not meet RAF requirements and asked for a bombsight that would allow the bomber to take any sort of evasive action throughout the bomb run. This, in effect, demanded the use of stabilization in order to allow the bomb aimer to continue making adjustments while the bomber manoeuvred.[3]

The existing CSBS was clearly not sufficient, nor was the upgraded version, the Mk. X. Both would be difficult to stabilize due to their large size. Due to details of its construction, the Automatic Bomb Sight could be modified to include stabilization, but it was estimated that it would be some time before it could be modified and brought into production. The Norden did offer stabilization, but it also required relatively long setup times and was still not available for purchase.[3]

Another solution to the vulnerability of the RAF bombers was to fly at night, which was taken up as the primary goal of Bomber Command from this point on. In this case, the existing sights displayed a number of other problems as well. The Mk. X proved to be very difficult to read at night, and bombers that had received it were quickly re-fit with the earlier Mk. VII or Mk. IX's.[5] The Norden was unable to work at night at all; the bomb aimer had to locate the target long in advance of the drop point using a built-in telescope, at ranges that could not be seen in low-light situations.[6]

What was needed was a new bombsight, one that could be very quickly set up, had useful illumination of the crosshairs so it could be used at night, and was stabilized so the bomb aimer could watch the approach even as the bomber was manoeuvring.[3] An early attempt was the Mk. XI, which mounted a cut-down CSBS on the front of a gyro unit taken from a Sperry Gyroscope artificial horizon to provide stabilization in the horizontal plane, useful for aiding drift measurements and corrections. However, this also required the range angle to be hand-calculated on the manual Course and Speed Calculator, by no means an easy task. Although introduced in 1941, only a small number were produced.[7][lower-alpha 2]

Blackett's solution

The request for a new bombsight was quickly passed on to the Royal Aircraft Establishment, where Patrick Blackett of the Aeronautical Research Committee volunteered to lead the effort.[5][lower-alpha 3] His solution to the problem was a dramatically updated version of the CSBS concept.[lower-alpha 4]

The key advance to the Blackett design was the way the sighting head was aimed. Instead of dialling the parameters into the sight directly, as in the CSBS, these inputs were dialled into a separate console. The console was equipped with repeaters for each of the aircraft instruments needed to operate the sight, like altitude and airspeed. The operator simply turned the dials on the console so their indicator arrows matched the readings on the instruments displayed in the same location, known as laying needle on needle. This eliminated the possibility the numbers would not be updated as the bomber manoeuvred, but required so much manual working that a new crew member, the bomb-aimer's mate, was introduced to operate the console.[9]

The inputs operated by the bomb-aimer's mate drove a mechanical calculator inside the console, or computor, as it was then spelled.[9] The output of the calculator drove flexible shafts that rotated the sight head to the proper angles in azimuth and altitude,[8] representing the wind drift and range angle. The sight head itself replaced the older wire crosshairs with a modern reflector sight that was easy to see at night. The sight could be rotated manually to sight on objects well in front of the aircraft, allowing the bomb aimer to select a wider variety of objects to use for drift measurements.[9]

In the CSBS the sighting system and calculator were one and the same, which required the bombsight to be fairly large. With this restriction removed, the sight head was much smaller and lighter than the older versions. This greatly reduced size meant that the sight head was easy to mount on a stabilizer system, adapted from the same Sperry gyroscope as earlier experiments. With the sight head stabilized, the bomb aimer could continue to measure drift even as he indicated turns to the pilot, eliminating the need to correct, re-measure, correct again, etc. Moreover, the remote console and second operator eliminated the need for the bomb aimer to look away from the sights to make adjustments while on the bomb run. As a result of these changes, short aiming periods of a few seconds would be enough for an accurate drop.[9]

The resulting Mk. XII bombsight was first tested in September and October 1940, and by the end of October, 20 examples had been constructed.[10] A slightly improved version, the Mk. XIII, was also designed, but not put into production.[9]

Mk. XIV

File:Royal Air Force Bomber Command, 1942-1945. CH12283.jpg
Bomb aimer on an Avro Lancaster demonstrating use of the Mark XIV.

The need for the second crewman was an obvious problem with the Mk. XII, especially as few bombers of the era had enough room for the operator.[10] Working with Henry Braddick, Blackett developed a new version of the calculator that included the necessary aircraft instruments inside the computor, and performed all the measurements and calculations automatically.[9][11] After the initial design was complete, Blackett moved onto other issues with Coastal Command, where he continued development of his theories of operational research.[lower-alpha 5]

The new design reduced the bomb aimer's setup workload to dialling in four settings, two of which could be pre-set before the mission. The two pre-set values were the altitude of the target over sea level, and the bomb's terminal velocity, a function of its design. The only settings adjusted in-flight were the measured wind direction and speed. The altitude, airspeed and course were all measured by the internal instruments, and presented to the user in windows on the side of the computor case. Once set, the computor could be left alone and automatically updated the aim point, and displayed this as the bombing angle through another window. The computor could even account for steady changes in altitude, allowing the bomb run to take place in a shallow climb of up to 5 degrees, or dive of up to 20 degrees. The later was especially useful in tactical bombing situations.[12]

The resulting Mk. XIV was first tested in June 1941.[13] It was the first modern bombsight that allowed for accurate bombing immediately after radical manoeuvring, with a settling time as little as 10 seconds. The fast settling time was invaluable during night bombing missions, as it allowed the bomber to fly a helical path, both climbing and turning, and then level out immediately before the drop. Even slow turns made it difficult for night fighters to track the bombers within the limited view of their radar systems, and continually changing altitude is an effective way to avoid anti-aircraft fire.[12]

Although the Mk. XIV was not as accurate as the Norden at altitudes over 20,000 feet, for typical night bombing altitudes between 12 and 16,000 feet, any differences in accuracy were minor. When the need for more accuracy for use with the Tallboy bombs arose in 1943, the Stabilized Automatic Bomb Sight (SABS), a development of the ABS, was introduced in limited numbers.[14]

Production and use

File:T-1 computer.jpg
The T-1A computer, a US-built version of the Mk. XIVA computor. This example retains the scales in the reading windows and a blank levelling card.

Although existing sources do not record when the Mk. XIV went into production in the UK, they do record that operational testing started in January 1942 and production examples started reaching squadrons in March. It was manufactured by small machine shops and instrument makers, such as the Aron Meter Company, and production was simply too slow to meet the demand. Between July and October, less than one hundred a month were being delivered. As the design was finalized, automated production was undertaken; by mid-1943, 900 a month were available. This was enough to equip the heavy bombers as they arrived from the production lines, and by late 1942 the Handley Page Halifax was being delivered with the sight head already installed.[12]

To fill demand for other aircraft, and especially smaller ones like the de Havilland Mosquito, the Air Ministry began looking at US manufacturers to supply the bombsight. Frederic Blin Vose of Sperry Gyroscope expressed an interest in the design, and felt he could adapt the Mk. XIV to US production methods and have it in mass production rapidly.[3]

Sperry arranged for AC Spark Plug to take over manufacture, initially on a sub-contract basis, and later for direct sales to the UK. The two companies then worked in some basic changes to the design in order to make it easier to produce, and a final design was ready in May 1942. The Sperry T-1 was fully compatible with UK-built versions, and a T-1 computer could be used with a Mk. XIV sight head, or vice versa. T-1s started arriving in March 1943, they were sent to light bombers like the Wellington, while UK-built versions were sent to the heavy bombers.[3]

Full production of the T-1 commenced at A.C.'s Flint, MI plant in November 1942. In August 1943, George Mann of A.C. Spark Plug visited the UK for a period of about a year, liaising with RAE Farnborough, Boscombe Down, and the Ministry of Aircraft Production.[3]

Later versions

File:462 Squadron RAAF Halifax bombsight AWM P01523.007.jpg
Mk. XIVa in a Handley Page Halifax in its stowed position with the collimator handle rotated forward and the metal plate over the glass sight.

In May 1943, Arthur Travers Harris requested that the maximum bombing altitude be increased from 20 to 30,000 feet, as the Avro Lancaster units were now carrying out missions as high as 22,000 feet. The Air Ministry responded with a compromise improvement of 25,000 feet and a more accurate angle mechanism.[9] These changes produced the Mk. XIVA which arrived in December 1944.[15] The A model also introduced the ability for the minor differences in instrument readings for indicated and true air speed between aircraft to be corrected simply by replacing a cam.[9]

The Mk. XIVB and T-1B replaced the suction-powered gyros in the stabilizer with electrical ones, reducing wiring.[9] This was introduced with the 18,000th T-1 on the A.C. production line.[16]

The Mk. XV was a version designed for the Royal Navy and Coastal Command for attacking submarines. As these operations took place at low altitudes, even small changes of altitude air pressure could lead to large errors in the calculations. The Mk. XV allowed the altitude input to be taken directly from a radar altimeter, eliminating these inaccuracies and any instrument lag.[9] The Mk. XVII was a Mk. XV modified for the very high speeds of the Naval Mosquito, allowing attack speeds of more than 400 mph. As the Naval Mosquito did not have a bomb aimer's position, the sight head was unstabilized and mounted in front of the pilot.[9]

In the post-war era, the UK produced derivatives of the design based on the T-1, as opposed to the original Mk. XIV. These T-2 and T-4 designs had much higher altitudes, airspeed and wind speed settings, suitable for high altitude bombing in the jet stream.[3] These could also be used with the Green Satin radar, which provided real-time measurements of the wind direction and speed, further automating the process. However, most wartime optical sights like the Mk. XIV proved almost useless for operations in jet aircraft, as the limited distances visible through the sight from high altitudes made it almost impossible to aim before the aircraft had already passed the drop point. Optical bombing quickly gave way to radar bombing, although the Mk. XIV remained in RAF service until 1965.[17]

Description

Basic mechanism

The Mk. XIV consisted of two independent parts, the sighting head and the computor.[18] The sighting head was located in the bomb aimer's window at the front of the aircraft. The separate computor cabinet was assembled with the operating knobs positioned on the right side of the case, so it had to be placed on the left side of the fuselage. The two were connected via two flexible cable drives.[19]

The computor cabinet included only four main controls. On the left side of the chassis, from top to bottom, were dials that set the wind direction, wind speed, target altitude and the bomb's terminal velocity. All of these inputs were set by reading their value in a small window on the left side of the dials. Additional windows provided output values for the indicated airspeed, course, and the bombing angle (or range angle).[20] Clips in the upper right held a card with levelling data, as well as notes about the sight or the bombs being dropped. The computor was also connected to several external sources. Compressed air was supplied from the engines to drive the mechanism, and an exhaust allowed the less dense used air to escape. Tubes were also connected to the pitot tube and static air source, which allowed the accurate measurement of airspeed. A separate electrical connection input the direction measured on the distant reading compass, using a selsyn.[19]

The sight head was mounted on top of a square platform, with screw adjustments that could be used to level the platform. A spirit level on the sight allowed it to be checked. The normally periodic and minor changes to level that the sighting head required could be accomplished by removing the cover over the spirit level and then turning a small adjusting screw on the mount. Pressing the release lever unlocked the sighting head from the mounting shaft on the left of the platform, allowing the sight to be removed and then re-attached simply by sliding it back onto the shaft, maintaining the level setting between missions.[21]

Above the mounting platform was the stabilization gyro, which rotated the entire upper section of the system from side to side in relation to the mounting platform below. As the sights worked by reflecting light off a mirror in the center, motion of the mirror would result in twice the motion of the aim point. To address this, the gyro was attached through levers with a 2-to-1 reduction.[8][22] The reflector sight mechanism was mounted in front of the gyro, slightly to the left. A metal flap protected the half-mirror from damage when stowed, which was rotated rearward during use and thereby covered the spirit level instead. The collimator was mounted on a prominent arm that projected in above and front of the sight when in use, and folded forward when stored. Electrical power was provided to light the collimator as well as the drift scale, which indicated the angle to fly to correct for the wind drift.[21]

Operation

The main design feature of the Mk. XIV was that it gave the bomb aimer more time to work on the problem of bringing the aircraft to the proper location to drop the bombs. As the calculations of this location were being carried out automatically, he could concentrate solely on the sight throughout the bomb run. The sight projected a crosshairs into space so it appeared to be projected on the ground, allowing the user to focus on the target throughout.[23]

The vertical line on the sight was relatively short, and could not be used directly to measure drift – unlike the long drift wires of the CSBS it replaced. To address this, the collimator handle could be used to manually rotate the sighting assembly forward, allowing the bomb aimer to point the sight further in front of the aircraft's location. This allowed the bomb aimer to select any convenient object on the ground for drift measurements, including the target itself, long before the aircraft reached it. Through periodic movements of the handle, the bomb aimer could ensure the drift line continued to pass through the target. When the handle was returned to the resting position and released, the shaft to the computor automatically re-engaged and started tracking the proper range angle again.[24] The handle was also used to rotate the collimator forward for storage.

Many of the figures used in the calculation of the bomb's trajectory were based on fixed values, and were entered before the mission started. In particular, the terminal velocity is based on the type of bomb being dropped and will not change during the mission. This is used to calculate how steep the path of the bomb will be when dropped from high altitudes; at lower altitudes and airspeeds, the bomb did not reach terminal velocity and followed a more parabolic path. Other measures were entered only once as the aircraft approached the target.[25]

Measuring wind

The only major measurement that could not be made automatically or before the mission was the determination of the windspeed and direction. These change over time, and also due to changes in location or altitude (see thermal wind). This demanded an accurate determination of the wind in the general area of the target, and would normally be highly inaccurate if dialled in at the mission start. Taking this measurement while nearing the target was an important procedure on the CSBS, who's manual included a number of methods of determining the wind.[26] In the case of the Mk. XIV, the manual describes only one method of determining the wind, equivalent to the most complex of the procedures from the CSBS model.[27]

Prior to the bomb run the pilot is directed to fly the aircraft in several different directions in sequence, preferably about 120 degrees apart. On each leg, the bomb aimer uses the reticle to measure the drift angle, either by rotating the wind direction dial on the computor so it rotated the sight head to the right angle, or by unlocking the azimuth control from the computor and turning the sight manually.[28] The drift angle is whatever angle the sight head is pointing when objects on the ground can be seen to be moving along the line on the sight. Once measured, the angle of the aircraft and the angle of the drift (measured either from the dial on the computor or the scale on the sight) are recorded. Using the Mk. III Navigation Computor, the RAF's version of the modern E6B, the three sets of angles are entered onto the wind calculator face. This normally results in a small triangular area forming where the three lines come close to meeting, and the center of this triangle reveals the wind speed and direction. This value is then entered onto the computor.[27]

Other details

As the Mk. XIV included the ability to calculate the effects of a shallow climb or dive (or glide as it is referred to in bombing), the computor included its own levelling mechanism. This was added to the range angle calculated by the computor in order to move the sight head. Levelling the system required adjustment of both the computor and the sight head. Since these were in a fixed relationship to each other, levelling could be carried out on the ground and then left alone. Any adjustments required were recorded on a card fixed to the front of the computor.[29]

As the computor held the level line and was sending angle commands to the sight, this eliminated the need for a two-axis gyro in the sighting head itself. The gyro on the sight head only adjusted for rotation of the aircraft around its roll axis.[30]

The bomb sight was also supplied with the Emergency Computor, a simple circular slide rule for use when the main computor stopped working.[12] In this case the bomb aimer would dial in the same basic parameters on the various disks, and read out the proper sighting angle at the bottom.[lower-alpha 6] Wind had to be estimated and calculated by hand. The angles were then entered manually into the sight; the drive cables were clutched out, the aiming angle entered using the operating handle, and the drift angle set by a small locking screw.[31]

A separate switchbox was used to control the brightness of the lamps driving the drift scale and reticle.[31]

See also

Notes

  1. The British military at that time used Roman numerals to denote the sequence of models (i.e. progressive versions) of military equipment. Hence this was the fourteenth model of bombsight in a line starting with the original CSBS Mk. I.
  2. An image of the Mk. XI is available at this page.
  3. Hore suggests that Blackett had already taken up development of the new bombsight of his own accord.[8]
  4. It is not clear from existing sources whether or not Blackett was also responsible for the Mk. XI. The only source to mention the Mk. XI is SD719, but it fails to note its origins.
  5. Although it is not mentioned specifically, sources suggest that Braddick led development of the Mk. XIV.[10]
  6. See image here.

References

Citations

  1. Goulter 1995, p. 28.
  2. Goulter 1995, p. 27.
  3. 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 Black 2001b.
  4. Zimmerman 1996, pp. 34–60.
  5. 5.0 5.1 5.2 Black 2001a.
  6. Torrey 1945, p. 71.
  7. SD719 1952, p. 283.
  8. 8.0 8.1 8.2 Hore 2004, p. 89.
  9. 9.00 9.01 9.02 9.03 9.04 9.05 9.06 9.07 9.08 9.09 9.10 SD719 1952, p. 284.
  10. 10.0 10.1 10.2 Hore 2004, p. 90.
  11. Hore 2004, pp. 90–91.
  12. 12.0 12.1 12.2 12.3 Harris 1995, p. 100.
  13. Hore 2004, p. 91.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Harris 1995, p. 101.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Kirby 2004, p. 91.
  18. AP1730 1943, Chapter 9 §6.
  19. 19.0 19.1 AP1730 1943, Chapter 9 Figure 5.
  20. AP1730 1943, Chapter 9 Figure 4.
  21. 21.0 21.1 AP1730 1943, Chapter 9 Figure 6.
  22. AP1730 1943, Chapter 9 §11.
  23. AP1730 1943, Chapter 9 §7.
  24. AP1730 1943, Chapter 9 §9.
  25. AP1730 1943, §8.
  26. AP1730 1943, Chapter 4 §65–94.
  27. 27.0 27.1 AP1730 1943, Chapter 9 §44.
  28. AP1730 1943, Chapter 9 §43.
  29. AP1730 1943, Chapter 9 §iii.
  30. AP1730 1943, Chapter 9 Figure 9.
  31. 31.0 31.1 AP1730 1943, Chapter 4 §13.

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.