Vector bombsight

Bombing became a navigation problem the moment airplanes stopped throwing explosives over the side by guesswork. Early crews could see a target, but they could not solve the harder question: where should a moving aircraft release a bomb when wind is pushing the airplane sideways the whole way in? Harry Wimperis's 1917 vector bombsight, better known in British service as the Course Setting Bomb Sight, mattered because it turned that guess into a mechanical geometry problem.

The older `bombsight` was good enough only when aircraft flew low, slow, and roughly along the wind line. That was already inadequate by the middle of the First World War. Naval aircraft hunting submarines and ships over open water could not count on a neat straight run with the wind at their back. Wind drift changed the aircraft's track over the ground, which meant the target was no longer where a simple sight said it would be. A bomb aimer could try to patch the error with stopwatches, lookup tables, and mental arithmetic, but that was exactly the kind of work people fail at in a vibrating cockpit under fire.

Wimperis had already built a Drift Sight in 1916 that made wind measurement easier. The vector bombsight went further. It embedded the same vector triangle pilots used in dead reckoning directly into the sight itself. That is where the `slide-rule` connection becomes important. The machine was not a general calculator, but it borrowed the same culture of analog computation: align scales, set known variables, let the geometry produce the answer. By dialing in altitude, airspeed, wind speed, and wind direction, the bomb aimer could derive both the proper heading and the release angle without drawing triangles by hand. Bombing accuracy stopped depending entirely on improvised cockpit math.

That was a classic case of `path-dependence`. The vector bombsight did not appear from nowhere. It inherited the optical frame and release logic of the earlier `bombsight`, then fused it with air-navigation methods that aviators were already learning. Britain in 1917 was the right habitat for that fusion. The Royal Naval Air Service had an urgent anti-shipping and anti-submarine mission, British aircraft were spending more time over water where wind errors became obvious, and wartime procurement could move a good instrument from test to operational use quickly.

The result was practical almost immediately. Tests at the Scilly Isles in December 1917 reportedly produced two direct hits in eight bombing runs, with the other six close enough to count as near misses. Production followed fast, and by 1918 roughly 720 had been built. The Royal Flying Corps shifted to the new sight as supplies arrived and had broadly converted by April 1918. Those numbers matter because they show this was not an elegant prototype that historians later romanticized. It was a working wartime tool that crews accepted because it solved a real operational bottleneck.

Once installed, the sight triggered `niche-construction`. Air forces could now plan bombing runs around the assumption that crosswind correction was a standard part of the attack rather than an improvised skill owned by a few exceptional crews. Training, crew roles, and doctrine reorganized around that assumption. The bomb aimer became less of a guesser and more of an operator of an analog computer. That change outlived the First World War. A U.S. Mark III version was still important enough to be used in Billy Mitchell's 1921 bombing trials against the ex-German battleship *Ostfriesland*, and Wimperis-style course-setting sights stayed in RAF service into the early years of the Second World War.

Its longer legacy shows up in `trophic-cascades`. Once the vector bombsight proved that the bombing run could be treated as a continuous geometry problem, later designers pushed the same logic toward more automation, more stability, and more variables. The `tachometric-bombsight` took the next step by recomputing the answer continuously during the approach instead of relying on a setup that the bombardier periodically adjusted. In that sense, the vector bombsight sits in the same family as many early analog computers: it reduced a messy real-world problem to moving scales, gears, and disciplined inputs, then invited later engineers to mechanize more of the task.

Its limitations were obvious too. The device still depended on humans to measure the wind well, keep the aircraft steady enough, and feed the machine sane numbers. As bombers flew higher and faster, those demands became harsher. But that does not diminish the achievement. The vector bombsight was the first practical system to make crosswind bombing something air forces could do deliberately rather than hope for.

That is why the invention deserves attention. It made aerial bombing less like throwing a stone from a galloping horse and more like solving for trajectory inside a machine. It was a wartime instrument, but also an early act of analog computation. The important change was not only better aim. It was the new belief that navigation, wind, speed, altitude, and release timing could all be folded into a single cockpit device and trusted in combat. Later sights became more automatic, more secret, and more accurate. They were still living inside the niche that Wimperis's vector bombsight built first.