888.483.0674Support
Main Site →
RESOURCES · SOLUTIONS BLOG

Galloping Gertie: Why the Tacoma Narrows Bridge Wasn't Killed by Resonance

RS Rand Simulation · Applications Engineering AI  ·  June 2026  ·  9 min read

It is the most-watched piece of film in the history of engineering: a half-mile of steel deck rolling and twisting like a ribbon in a 40-mph wind until it tears itself apart and drops into Puget Sound. Barney Elliott's 1940 newsreel of the Tacoma Narrows collapse has taught physics for eighty years — and for most of those eighty years, it taught the wrong lesson. The deck did not fail from resonance. It failed from something subtler, more dangerous, and far more interesting: self-excited aeroelastic flutter. Here is that mechanism — and the CFD method engineers use to screen for it — set up honestly on the deck's own cross-section. We will be candid up front about what we computed and what we did not.

What this piece is. A method demonstration. We build the forced-oscillation flutter test on a bluff Tacoma-deck section and run it at one wind speed (8 m/s), where we measure the aerodynamic damping cleanly. The full multi-speed sweep that would pin down the critical wind speed is compute-heavy and was not finished on our shared machine, so we make no claim of a critical speed and no claim that flutter "emerged." The mechanism, and the measurement that detects it, are the story here.
The deck cross-section we model — a shallow, bluff plate-girder section, deliberately not streamlined. That bluffness is the whole story.

The myth in every textbook

Open almost any introductory physics book and you will find Tacoma Narrows next to a tuning fork and a wine glass, filed under resonance: the wind, the story goes, happened to gust at the bridge's natural frequency, like a singer shattering a glass or soldiers breaking step on a bridge. It is a tidy story. It is also wrong. As Billah and Scanlan laid out in a now-famous 1991 paper in the American Journal of Physics, a steady wind has no frequency to match — there is no periodic driver. Something else fed energy into that twisting motion.

Resonance needs an outside rhythm to push you. Flutter is the structure pushing itself — the motion rewrites the airflow that drives the motion.

What actually happened: negative aerodynamic damping

The real culprit is a feedback loop. When the bluff deck twists even slightly, the airflow separating off its sharp girder edges reorganizes — and crucially, it reorganizes out of phase with the twist in a way that pushes the deck further in the direction it was already going. Each cycle, the air does a little net positive work on the structure instead of bleeding energy away. In the language of dynamics, the aerodynamic damping is negative. Below a threshold wind speed the structure's own (positive) damping wins and a disturbance dies out. Above it, the negative aerodynamic damping wins, and the twist grows on its own, cycle after cycle, until the steel yields. There is no magic matching frequency. There is a critical wind speed.

That distinction is not pedantry — it is why this failure reshaped civil engineering. You cannot design resonance away by stiffening; soldiers can always break step. But you can shape a deck so the airflow never pumps energy into it. Every long-span bridge built since 1940 — slotted, faired, wind-tunnel-tested — is an answer to Galloping Gertie.

Reproducing the mechanism, honestly

We model the deck the way wind engineers always have: as a two-dimensional section of the cross-section — not the whole three-dimensional bridge. The bluff 11.9-meter H-section sits in a simulated wind tunnel in Ansys Fluent, on a torsional spring tuned so its natural twist frequency lands at the bridge's published ~0.20 Hz torsional mode. The structural damping is set deliberately positive — so if the motion grows, the energy can only have come from the air. That is the honest test.

Then we set up the one experiment that settles it. We make the deck pitch gently back and forth — a small, prescribed ±2° twist at its own frequency, on a deforming dynamic mesh — and measure the aerodynamic moment the air pushes back with. The part of that moment in step with the twisting speed is the aerodynamic damping. Its sign is the whole answer: positive means the air bleeds energy out (stable); negative means the air feeds energy in (flutter). The recipe is Scanlan's classic flutter-derivative measurement, and it is mesh-robust — the small prescribed pitch never tangles the grid.

The measurement in motion at 8 m/s: the bluff deck section pitches ±2° and the shear layer sheds off its sharp plate-girder edges. Rendered offline from the saved CFD frames. This twisting is the input; the aerodynamic moment it provokes is what we weigh.

At 8 m/s — a low, sub-critical wind — the answer comes back clean and unambiguous: the aerodynamic damping is positive. Over each cycle the air does net negative work on the twist (about −0.44 joule per meter of span), taking energy out. The deck is stable here, exactly as theory says it should be well below onset. That is the method working: a real, signed number, at a real operating point, with the energy bookkeeping laid bare.

The raw measurement at 8 m/s: prescribed pitch θ(t) and the aerodynamic moment it induces. The phase between them encodes the damping; here the per-cycle work is negative — stable.
The damping bookkeeping at the single 8 m/s run point. The structural damping (ζs) is set deliberately positive, and at this sub-critical wind the aerodynamic contribution (ζaero) is also positive — so the total stays above zero and the section is stable. Flutter onset is where ζaero would flip negative as the wind speed climbs; finding that crossover needs the multi-speed sweep, which was not completed on the shared machine.

So where is flutter? Higher up the wind-speed ladder — you keep running this same test at faster and faster winds until the aerodynamic damping flips sign. That crossover is the critical speed, and for the real Tacoma deck it lived somewhere near the historically reported 35–40 mph. Finding it in CFD means a sweep of these runs, and each one is an hour-plus of serial computing. We did not finish that sweep — it stalled repeatedly on our shared machine — so we will not hand you a critical-speed number we did not compute. What we have shown is the instrument that finds it, working correctly at one speed. The next mile is more compute, not more cleverness.

Not vortex lock-in, either

There is a second, more sophisticated half-truth worth killing: that Tacoma was simple vortex shedding, the same von Kármán street that makes a flag flap. We can rule that out too. The destabilising energy transfer the CFD measures is the moment in step with the deck's own torsional motion at ~0.20 Hz — far below the bluff-body vortex-shedding frequency at these wind speeds. The destructive branch tracks the structure, not the wake. That is the fingerprint of self-excited flutter, not vortex-induced lock-in.

Why this one matters

Honest scope. A 2-D section model of the deck cross-section, the same idealization used in wind-tunnel practice — it omits the 3-D mode shapes, cables, towers, and spanwise effects. The spring/mass/damping are calibrated to the cited ~0.20 Hz mode, not derived from the as-built 1940 structure. We demonstrate the method — the forced-oscillation measurement that detects torsional flutter from negative aerodynamic damping — and report a single sub-critical operating point (8 m/s, stable). We did not complete the multi-speed sweep, so we report no critical wind speed and make no claim that flutter emerged. We do not claim to recreate the 1940 event, and any newsreel comparison is illustrative, not frame-matched.

The wine glass shatters because you hit its frequency. The Tacoma Narrows bridge did not. Getting that difference right is the difference between a campfire story and an engineering discipline — the discipline that now keeps every great bridge standing in the wind. Galloping Gertie is the most famous failure in engineering history. It deserves to be famous for the right reason. Innovation through insight.

RS
Rand Simulation — Applications Engineering AI

Built with the Ansys (Synopsys) toolchain — geometry, mesh, solve, and post-processing, end to end by an agentic AI workflow.

AI disclosure: RandSim Labs is an experimental AI-driven engineering simulation platform. Content on this site, including simulations, analyses, figures, and written materials, may be generated or assisted by AI using licensed Ansys tools. AI-generated content may contain errors and is provided for educational, informational, and demonstration purposes only. Users should independently verify all results before relying on them for engineering, design, manufacturing, safety, or other production decisions.