Picture yourself in the second week of a structural engineering course. The lights drop. Grainy footage fills the screen: a suspension bridge writhing in a 42-mph wind, its deck twisting in slow, nauseating spirals before the whole thing tears itself apart. Nobody died. The bridge had stood for four months. And yet for more than eighty years, that film reel has been threaded through projectors from Zurich to Seoul, dissected in textbooks, cited in papers on aeroelastic flutter, and invoked whenever an engineer needs shorthand for what happens when you ignore resonance. It is, by any measure, one of the most-taught disasters in the history of the built environment.
The Quebec Bridge, by contrast, collapsed twice: once in 1907, killing 75 workers, and again in 1916 during a repair attempt, killing 13 more. It is a footnote. Mentioned in specialist literature on compression failure and inadequate supervision, yes. But it doesn't have the cultural grip. It doesn't get the film reel.
The gap between those two cases is the thing worth understanding.
The accident that teaches versus the accident that disappears
Engineering failures don't become canonical because they are the worst. They become canonical because they are the most legible. The Tacoma Narrows collapse has a single, clean, visually demonstrable mechanism: the bridge entered a resonant oscillation driven by vortex shedding, and the deck's solid plate girders, chosen to save money over open trusses, made the structure act like a sail. You can show this in a wind tunnel. You can model it with a ruler and a fan. The lesson packages itself, almost like a toy that arrives pre-assembled.
Quebec's collapses were messier. The 1907 failure involved cascading errors: a chief engineer working mostly from his New York office, field supervisors overruled when they raised concerns, and a fatally optimistic recalculation of the bridge's own weight that was never properly checked. The structural mechanism was compression buckling in the lower chord, but the cause was an organizational and supervisory failure distributed across months of decisions. You can't film that. You can barely diagram it.
This is the first filter: photogenic clarity. A failure reducible to one diagram, one mechanism, one moment of visible drama has an enormous advantage in the competition for pedagogical attention.
The infrastructure of memory
Legibility alone doesn't explain everything. The other filter is institutional capture: which failures got written up first, by whom, and in which journals.
Take the Dee Bridge collapse of 1847 in England. Robert Stephenson's cast-iron girder design failed under a passing train, killing five people. It was investigated almost immediately by a Royal Commission, which produced a detailed public report. Stephenson himself testified. The failure entered the British engineering literature while the field was still young enough that a single well-documented case could shape practice for a generation. It got in early. Timing, in the formation of a professional canon, is almost everything.
Contrast that with dozens of industrial accidents from the same era that killed far more people but were never formally investigated at comparable depth, because the victims were workers in factories or mines rather than passengers on a train, and because no equivalent public institution existed to demand an account. Those failures produced no reports. No reports means no citations. No citations means no textbooks. The disaster that leaves no paper trail leaves no pedagogical legacy either.
This is worth stating plainly, without the usual softening: the canonical cases often reflect whose deaths were considered worth investigating, not whose deaths were most preventable. That is not a neutral curatorial outcome. It is a political one, and the profession has been slow to reckon with it.
Why the Challenger disaster crowded out the Columbia one
Both Space Shuttle disasters are taught. But Challenger, which broke apart 73 seconds after launch, gets substantially more classroom time than Columbia, which disintegrated on re-entry roughly seventeen years later. Ask an engineer what caused Challenger and most will answer immediately: O-ring failure in cold temperatures, compounded by organizational pressure to launch despite engineering objections. Ask about Columbia and you'll get a more hesitant answer, something about foam strike damage, something about institutional culture at NASA.
Both failures had identical organizational pathologies, as the Columbia Accident Investigation Board explicitly noted. Both involved engineers raising concerns that were dismissed by management. Both resulted from a culture that had normalized small warning signs until they were no longer seen as warnings at all. The Columbia report is, if anything, the more sophisticated document.
Yet Challenger has the stronger pedagogical grip. Partly this is sequencing: it came first, and first-mover advantage in case studies is real. Partly it's that the O-ring story has a villain structure that satisfies a narrative need. The Morton Thiokol engineers were right, management was wrong, and the wrongness is traceable to a specific pre-launch teleconference. Columbia's failure is more diffuse. The foam had struck the orbiter on many previous missions without catastrophic result. The normalization of that risk was gradual, institutional, almost invisible. That's a harder story to tell in fifty minutes.
The lesson that's easy to tell gets told. The harder lesson gets assigned as optional reading.
What people get wrong about the Tacoma Narrows
Since that bridge is doing so much work in engineering education, the standard classroom explanation deserves scrutiny, because its most famous lesson may be the wrong one.
For decades, the standard classroom explanation held that the bridge failed because of resonance: external driving forces matched the structure's natural frequency, and the energy built until the deck gave way. Clean. Teachable. The problem is that it's not quite accurate. The Tacoma Narrows failure was driven by aeroelastic flutter, a self-reinforcing feedback between the bridge's motion and the aerodynamic forces acting on it. Related to resonance, but distinct from it. A bridge failing because soldiers march in step is forced resonance. Tacoma Narrows was flutter: the structure was extracting energy from the wind and feeding it back into its own oscillation.
Engineers who specialize in bridge aerodynamics have been making this correction for decades. It filters slowly into general education because the simpler resonance story is already embedded in a thousand textbooks, and correcting it requires adding complexity to a lesson whose appeal was its simplicity.
This is the trap at the center of canonical teaching cases. The very process that makes a failure memorable, stripping it to one clean mechanism, also distorts it. The lesson that survives is not always the lesson that was there.
The forgetting is structural, not accidental
Consider two engineers: call them Ana and Ben. Both graduate in the same year, both work in structural design. Early in her career, Ana's firm encounters a near-miss: a connection detail on a parking structure shows unexpected fatigue cracking during inspection, caught before anyone is hurt. The incident is documented internally, shared quietly with a few peer firms, and Ana carries it as a formative lesson for thirty years. Ben never hears about it.
Now scale that up. The engineering profession's collective memory is built from what gets published, investigated, litigated, and legislated. Near-misses caught quietly, failures in contexts without regulatory oversight, disasters in countries without strong professional institutions, collapses that kill workers rather than passengers or residents: all of these are systematically underrepresented in the canonical record. The cases that get taught are not a representative sample of failure modes. They are a sample of failure modes that were visible, investigated, and happened to the kind of people whose deaths generated institutional responses.
The American Society of Civil Engineers established the Engineering Ethics Case Histories archive partly to address this. The Aviation Safety Reporting System, a confidential near-miss reporting mechanism for pilots and crew, was created explicitly because people knew that the accident record alone was missing most of the information. These are genuine attempts to widen the aperture. But they work against a strong current.
The case that's always missing from the syllabus
Pedagogical selection doesn't just determine what engineers learn. It shapes what the profession believes failure looks like.
If every canonical case involves a dramatic, visible, sudden collapse, engineers may underweight the slow failures: the corrosion that accumulates over decades, the maintenance culture that quietly degrades, the organizational drift that makes each small compromise seem reasonable. Ask yourself whether your own mental model of engineering failure is built around explosions and collapses, or around the slow grind of deferred maintenance and underfunded inspections. The answer probably tells you something about which cases your professors chose.
The Hyatt Regency walkway collapse in Kansas City killed 114 people and entered the canon, partly because the structural cause, a last-minute connection detail change that doubled the load on a rod, is diagrammable and the negligence trail is clear. The gradual deterioration of hundreds of bridges over the following decades, driven by deferred maintenance and funding shortfalls, kills people too, but in ones and twos over years. No case study. No film reel.
The profession's memory is biased toward drama and away from attrition. Toward the single bad decision and away from the thousand small ones. Toward the engineer who made a catastrophic error and away from the institution that made good engineering incrementally impossible.
What gets taught shapes what gets noticed. What doesn't get taught doesn't merely stay unknown: it stays unremedied, waiting for the next time conditions align and no one in the room recognizes the pattern, because the course that might have shown it to them ran short on time and stopped at the bridge that twisted in the wind.