On February 1, 1943, a B-17 Flying Fortress named All American was heading away from a bombing mission over North Africa when a German fighter crossed into its path at exactly the wrong angle.
For an instant, the two aircraft were almost on top of each other.
The German fighter struck the bomber near the rear fuselage.
Metal folded.
Aluminum skin tore open.
Structural members snapped.
The impact ripped a deep wound across the B-17 just ahead of its tail assembly, leaving the rear portion of the aircraft attached to the rest of the bomber by what appeared to be an impossibly small amount of surviving structure.
Anyone looking at the damage afterward might reasonably assume that the airplane had broken apart in the air.
It had not.
The tail still hung behind the fuselage.
The horizontal stabilizers were still there.
The vertical fin was still there.
Some of the control system continued functioning.
And inside the bomber, a crew suddenly faced a problem no flight manual had been written to solve.
Their airplane was technically still flying.
The question was how long that would remain true.
The B-17 was far from home.
German fighters were still in the area.
The damaged aircraft could not maneuver normally.
Every vibration threatened to widen the tear.
Every change in airspeed altered the forces acting on the weakened fuselage.
A hard turn might finish what the collision had started.
A steep dive could increase airflow over the tail until the remaining structure failed.
Even ordinary turbulence could become dangerous.
The crew had no way to repair the damage in the air.
There was no metal brace long enough to reconnect the fuselage.
No technician could crawl outside and rebuild the aircraft several thousand feet above North Africa.
All they could do was keep the airplane within the narrow range of conditions its damaged structure might still tolerate.
They reduced violent control inputs.
They watched the tail.
They communicated continuously.
They moved carefully inside the aircraft.
And they began the long flight back toward friendly territory.
The most famous photograph taken that day shows the result.
The B-17 is still airborne.
Its wings appear intact.
Its four engines are running.
Then the eye reaches the rear fuselage.
A huge section has been torn away.
The entire tail seems to be connected by little more than a narrow strip of metal.
The image looks less like a damaged airplane than like a photograph taken one second before an airplane breaks in half.
Yet the B-17 did not break in half.
It continued.
That is why All American became one of the most famous examples of the B-17 Flying Fortress's ability to absorb catastrophic damage and remain airborne.
But the deeper story is not simply that the B-17 was strong.
Airplanes do not survive because of reputation.
They survive because enough specific structural members, control systems, engines, and human decisions continue functioning at the same time.
All American had lost far more than any crew would ever want to lose.
It had not lost everything.
And for the next part of the flight, survival depended on understanding the difference.
The B-17 Had Been Designed Around the Possibility of Damage
When Boeing developed the B-17 in the 1930s, the aircraft was intended to carry heavy bomb loads across long distances while operating at altitudes and ranges that placed enormous demands on both machine and crew.
The Flying Fortress was large by fighter standards.
It had four engines.
Multiple gun positions.
A crew spread through several compartments.
A substantial wing.
A long fuselage.
Its structure was built primarily from aluminum alloy, arranged through frames, longerons, stringers, skin, spars, and other components working together.
No single sheet of metal carried the entire airplane.
Loads were distributed.
That mattered.
An aircraft structure can survive some damage because the forces carried by one part can sometimes be transferred into neighboring parts.
Engineers call this redundancy in various forms.
Redundancy does not mean invulnerability.
Enough damage in the wrong place will still destroy an aircraft instantly.
A severed wing spar can remove a wing.
A fuel fire can consume the airplane.
Destroyed control cables can make flight impossible.
A broken fuselage can separate completely.
Yet the B-17 developed a reputation for returning with damage that looked astonishing.
Part of that came from its size.
Part came from the strength of its structure.
Part came from its four engines.
Part came from duplicated or distributed systems.
And part came from the simple fact that aircraft which returned could be photographed while aircraft that disintegrated never reached the camera.
That final point matters.
The photographs of damaged B-17s tell a true story about structural strength.
They do not prove every B-17 could survive every amount of damage.
The men flying them understood this better than anyone.
They had seen aircraft disappear.
They had watched bombers fall burning from formations.
They knew the phrase "Flying Fortress" was a name, not a guarantee.
On February 1, All American would test the difference between reputation and reality more severely than almost any crew could have imagined.
The Aircraft Was Fighting in North Africa, Not Over Germany
The famous image of B-17s usually brings to mind enormous formations crossing Europe later in the war.
Hundreds of bombers.
Contrails filling the sky.
German cities below.
Long-range escort fighters appearing beside them.
That was not yet the full shape of the American air war in early 1943.
All American was operating from North Africa as Allied forces fought Axis armies across Tunisia.
The campaign had begun after Operation Torch, the Allied landings in Morocco and Algeria in November 1942.