For This B-24 Bomber, the Trip Home Was as Dangerous as the Mission
Fortunately, the aircraft was flying well and we were climbing at a positive — if unknown — rate.
Here's What You Need to Remember: Adding even more to the degree of difficulty was the fact that the spare B‑24 had several major differences from our H-model, including the cockpit layout, flight controls. defensive weaponry and the bomb sight. But there was one particular difference between it and our normal aircraft that was about to bite us in the keester. The two birds had different locations for the pitot-static system which provide the pilots with airspeed, altitude and rate of climb/descent.
On April 22, 1944, 26 B-24 bombers from the U.S. Army Air Corps’ 453rd Bombardment Group took off from Old Buckenham Airfield in England. Their target — a railway marshaling yard in Hamm, Germany.
The pilot of the lead B-24 was Bill Norris, my father and a future Air Force test pilot. Norris, then in his early 20s, was not happy. The group had decided to surprise the Germans by launching the planes in the daytime — a departure from standard procedure.
It was a tactic the bombardment group would not repeat.
The problem was, departing when the sun was up meant returning when the sun was down. “Another example of masterful mission variation planning and execution,” Norris joked decades later.
“The penetration into Germany and bombing were nearly normal,” Norris explained. The 453rd Bombardment Group’s official history seconds Norris’ account. “Bombing results were excellent,” the history notes.
The problem occurred on the flight back to England. “The return was a real nightmare,” Norris said.
“German night-fighters followed us home until we were told to turn on navigation lights for penetration separation and recovery,” Norris said. “In just a couple minutes, the black night was well-illuminated by flaming B-24s in the sky over southeast England.”
“I directed the squadron to shut off their lights and pick any airfield they could find. I found Old Buck and approached to land. A Ju-88 was firing at us on final approach and the gunners were returning fire ’til we touched down. We sustained several 20-millimeter [cannon] hits in the wings and tail, but no one was injured.”
“Many aircraft had encounters with intruders,” the official history comments unironically.
“Needless to say,” Norris quipped, “we did not do that again.”
On a separate mission that same spring, Norris and his crew had to contend with an equally dangerous screw-up — one that required some mid-flight engineering on a malfunctioning plane.
“We were alerted for a mission and the usual procedure was for the crew to pre-flight the B‑24 and munitions-load prior to mission preparation and briefing,” Norris recalled. “As squadron lead, our navigator and bombardier prepared the route and target folders while I worked with operations on the departure, formation and in‑flight procedures.”
Our group of 26 B-24s — each loaded with four 2,000-pound bombs — was to join hundreds of other bombers and fighters from the 8th Air Force on the mission. Our aircraft’s load included a couple of 100-pound smoke bombs because, as lead, our formation dropped on our release and the smoke bombs acted as a marker.
All was well until our crew chief found an engine problem that couldn’t be fixed in time for take‑off. Therefore, we had to use a backup aircraft. Time was moving rapidly toward mission take‑off time and we had a new bird to pre-flight. We immediately encountered a problem in that the spare’s bomb load wasn’t correct and had to be downloaded and replaced in the dark and rain well before sunrise.
Adding even more to the degree of difficulty was the fact that the spare B‑24 had several major differences from our H-model, including the cockpit layout, flight controls. defensive weaponry and the bomb sight. But there was one particular difference between it and our normal aircraft that was about to bite us in the keester. The two birds had different locations for the pitot-static system which provide the pilots with airspeed, altitude and rate of climb/descent.
The download/upload of bombs took darn near every bit of the time remaining and we were pressed to man-up, crank up the four engines and get to the runway to lead the takeoff sequence.
As usual, the weather was lousy. A ragged 600 foot ceiling, moderate rain and solid clouds from 1,800 to 20,000 feet. We had specified climb corridors and routes since there were several nearby bomber and fighter groups executing similar departures.
The plan was for each of the 25 B-24s following us from Old Buck to penetrate the clouds individually and — once on top — rendezvous with us via the Buncher 6 radio beacon. We would then join with other groups to form the Division as we departed the English coast for Germany.
By that time it would be daylight and we knew German flak would begin right away — prior to crossing the coast inland — from flak barges and would continue in varying intensity and accuracy until we re-crossed the Channel on the way home.
For example, one battery at Abbeville always scored hits, while others could not seem to hit anything. When not in the midst of flak, we’d be under attack by Luftwaffe fighters. The boys out of Abbeville earned a reputation for being especially deadly.
We took the runway with the deputy-lead on the right wing. I applied power and we rolled slowly down the runway, heavy with full fuel and the bomb load. I eased the B‑24 off the ground and called for the gear retraction. Checking the instruments, I found — with some trepidation — that we had no airspeed, erratic rate of climb and questionable altitude. There was no choice but to proceed and soon we were mired in thick cloud and rain.
Fortunately, the aircraft was flying well and we were climbing at a positive — if unknown — rate. Without the gauges we rely upon in zero visibility, I had no choice but to fly the aircraft by attitude, power and the seat of my pants. We needed to unscrew this ASAP, so I called for Chris, our flight engineer, to make his way up to the cockpit and explained the situation.
Given that our pitot-static system was totally defunct, we ran through the possibilities and quickly diagnosed the problem. In our hasty departure, the protective covers had to have been left on the tubes shutting off both the ram and static air sources needed by our gauges.
Problem was — even though we understood what went wrong — we still had to solve it because we needed both airspeed and altitude for bombing, to say nothing about normal flying and recovery, assuming we got home in one piece.
Running out of the proverbial airspeed, altitude and ideas, our solution was a bit drastic, but none other came to mind. As I kept us climbing wings level, Chris got his tool box, went up to the bombardier’s compartment and chiseled out a sizable hole in the side of the fuselage just ahead of where he knew the left-hand pitot tube to be.
He then reached out and pulled the cover off the pitot tube and — like magic — we had airspeed, altitude and rate of climb for the rest of the mission.
The hole was easily explained as battle damage since we had collected multiple holes from heavy flack and German fighters. But, to my knowledge, this specific bit of mission information never made it into the debriefing folder.
An unintentional oversight, I’m sure.
This first appeared in WarIsBoring here.
Image: Wikicommons