You’ve probably stared at a product roadmap and realized everyone is just polishing the same tired ideas. We’ve been taught that good design is safe, stable, and predictable. But true innovation doesn’t play by those rules. Let me tell you about a plane built in the 1940s that looked like a UFO, flew like a nightmare, and was exactly what modern aviation needed.
Meet the Vought V-173, affectionately known as the ‘Flying Pancake.’ In the middle of WWII, the US Navy desperately needed fighter planes that could take off from the tiny decks of escort carriers without a catapult. Conventional wisdom said: build a smaller plane with a bigger engine. Engineer Charles Zimmerman said: flatten the entire aircraft into a giant disk.
If your new design doesn’t terrify the people testing it, you aren’t innovating. You’re just iterating.
Zimmerman went back to first principles. Why do we need long wings? For lift. But what if the entire fuselage was the wing? By using a symmetrical, all-lifting body with a massive chord, the V-173 generated unprecedented lift at near-stall speeds. It could take off in a space barely longer than a tennis court. It was a masterclass in radical trade-offs.
But there was a massive catch. The very physics that gave the Pancake its legendary low-speed lift also made it inherently unstable in pitch and roll. Pilots fought to keep it level. It was too complex for 1940s control systems. The Navy eventually passed, and history dismissed the V-173 as a quirky dead-end.
History is wrong.
Breakthroughs don’t come from optimizing the old model. They come from burning it down and dealing with the smoke.
Most aviation buffs look at the Flying Pancake as a weird anomaly. They miss the point entirely. Zimmerman’s core insight—that a symmetrical, all-lifting body could operate from tiny spaces—directly anticipated the modern blended-wing-body concepts and VTOL platforms like the MV-22 Osprey. The V-173 wasn’t a failure; it was just early. The aerodynamics were sound, but the computational power and fly-by-wire systems needed to manage that instability wouldn’t exist for another 40 years.
If you’re building anything right now—a product, a team, a company—this is the lesson you need to internalize. A step-change in performance almost always demands a trade-off in stability. You can’t get a 10x improvement by playing it safe. You have to embrace the complexity.
Stop trying to build the perfect, stable product. Start building the Pancake. Find the radical edge of what’s physically possible, accept the chaos that comes with it, and figure out how to manage it later.
FAQ
Q: Didn't the V-173 fail because it was too unstable to be useful?
A: Yes, it was unstable, but that wasn't a design flaw—it was a technology limitation. The aerodynamics were sound; they just lacked the 1980s fly-by-wire computers needed to manage the chaos. It didn't fail, it was just early.
Q: How does a 1940s plane help me build software or hardware today?
A: It tells you to stop optimizing the old model. If you want a 10x improvement in performance, you have to make a radical trade-off (like sacrificing stability for lift) and figure out how to manage the consequences later.
Q: Isn't embracing instability just a recipe for disaster?
A: Playing it safe is a recipe for irrelevance. The V-173's instability was the direct price of its breakthrough capability. If your product roadmap doesn't have at least one terrifyingly unstable bet, you're already falling behind.