Earthquake-Resistant Design

For ages 9–11, treat earthquake-resistant design as a full engineering-design cycle, not a single fact: children define the problem with explicit criteria (keep occupants safe, keep the building standing) and constraints (budget, materials, height), then generate multiple building and community solutions, test each under the same shaking, compare them against shared criteria, and iterate. The honest ceiling is that engineering REDUCES and delays impact and buys escape time — it does not make a building or town hazard-proof. Attach a physical mechanism to every feature (inertia for base isolation, low centre of mass for a wide base, triangulation for cross-bracing, counter-sway for a roof damper) and widen beyond the building to the detect→warn→act system of warning sirens, marked evacuation routes and practised drills.

• 'You can build a totally earthquake-proof building.' — Engineering reduces and delays damage; the goal is protecting people and buying escape time, not invincibility.
• 'A stronger/heavier/more rigid building is always safer.' — Rigidity can be worse; flexible frames and base isolation that let a building sway or decouple from the ground often outperform brute stiffness.
• 'Base isolation means the building is fixed harder to the ground.' — It is the opposite: bearings DECOUPLE the building so the ground can move without dragging the building with it.
• 'Bigger earthquake magnitude is the only thing that determines damage.' — Distance, ground type, building design and preparedness all shape the actual impact; design targets the impact side.
• 'Only the building matters.' — Warning systems, evacuation routes and practised drills reduce human impact as much as structural features; mitigation is a system, not just a stronger wall.
• 'Drills are a waste of time / the plan is obvious.' — Rehearsed evacuation is itself an engineered solution; it measurably cuts casualties when seconds count (esp. tsunamis).

• Shake-table test bench: a base that oscillates while a built structure is scored for staying upright — the canonical earthquake-engineering model.
• Before/after failure pair: an un-braced frame racking into a parallelogram vs a triangulated/braced frame holding its shape.
• Base-isolation cutaway: building on rollers/bearings while the ground slides underneath — arrow showing ground moves, building lags (inertia).
• Solution-comparison grid: rows = candidate designs, columns = criteria (survives strong shake? cost? height kept?), so the trade-off is legible at a glance.
• Tsunami evacuation map: detection buoy → siren → marked route → high ground / vertical-evacuation tower, showing the detect-warn-act chain.

• Run it as a full engineering-design cycle: define the problem with explicit criteria (occupants safe, building stands) and constraints (budget, materials, height), then generate MULTIPLE solutions, test, compare, and iterate — do not let it collapse into 'build one tower'.
• Make the failure visible and safe: children must SEE a poorly-braced structure rack and topple under shaking so the need for each feature is felt, not told.
• Attach a physical mechanism to every feature (inertia for base isolation, low centre of mass for wide base, triangulation for cross-bracing) so features are understood, not memorised as a checklist.
• Insist on fair testing: same shake, one change at a time, so a comparison actually isolates what the feature did — this is the science-fair 'control variables' habit.
• Frame the honest ceiling: engineering REDUCES impact and buys time; it does not make a building or town earthquake-proof — connect to real trade-offs of cost vs safety.
• Widen beyond the building: pair structural design with warning systems and evacuation drills so children see 'reduce impact' as a system (detect → warn → act), matching real hazard mitigation.