Why Do We Design for Collisions?
Every day, people ride in cars, wear bike helmets, and use phone cases. All of these involve collision-related designs — objects built to protect something during a crash. But how do engineers know if a design actually works? They test it against criteria and constraints. This idea has a long and interesting history.
Throughout history, people learned from real-world accidents. They asked: How can we reduce injury and damage during a collision? That question led to the engineering design process we use today. In this lesson, you will learn how to evaluate whether a collision-related design actually meets the goals it was built for.
Core Principles: Criteria, Constraints, and Forces in Collisions
Before you can evaluate a design, you need to understand three big ideas. First, what are criteria (the goals a design must achieve)? Second, what are constraints (the limits a design must stay within)? Third, how do forces work during a collision?
Design Criteria
Design Constraints
Force in Collisions
Energy Transfer
Evaluating a Design
Visualizing the Evaluation Process
Let's look at how engineers evaluate a collision-related design step by step. The diagram below shows the engineering design evaluation cycle. You start with a problem, create criteria and constraints, build a solution, test it, and then evaluate the results.
The key step for this lesson is Step 5 — evaluation. This is where you compare your test data to the criteria. Did the design reduce force enough? Did it stay within budget? If the answer is yes to all criteria and constraints, the design passes. If not, it is time to redesign.
The Math Behind Collision Forces
To evaluate a collision design, you often need to understand the forces involved. Two important ideas help us do the math: Newton's second law and the relationship between force and stopping time.
Here is the big idea for collision design: if you increase the time it takes for an object to stop, the force on the object goes down. Think about it — would you rather stop suddenly by hitting a brick wall, or slowly by landing on a mattress?
How Engineers Evaluate Collision Designs
Engineers use several methods to evaluate collision designs. Let's look at a common classroom example: the egg drop challenge. In this challenge, you build a container that protects an egg when dropped from a height. The diagram below shows how you might organize your evaluation.
Notice something important: a design can fail for different reasons. Design B actually protected the egg, but it went over budget and over the weight limit. A true evaluation checks every criterion and every constraint, not just the most obvious one.
Worked Example: Evaluating a Bumper Design
Let's walk through a full evaluation. Imagine your class is designing bumpers for a small toy car. The car (mass = 0.5 kg) rolls down a ramp and hits a wall at 4 m/s. You need to design a bumper that reduces the collision force.
Strengths, Limitations, and Tradeoffs in Collision Design
In the real world, no design is perfect. Engineers must make tradeoffs (giving up something in one area to gain something in another). For example, adding more padding might make a helmet safer but also heavier and more expensive.
| Design Feature | Strength | Limitation |
|---|---|---|
| Thick foam padding | Absorbs a lot of energy; greatly reduces force on the object | Adds weight and bulk; may exceed size or mass constraints |
| Crumple zone (crushable material) | Increases collision time, lowering the peak force significantly | Can only be used once; must be replaced after each collision |
| Hard outer shell | Spreads force over a larger area; protects against punctures | Does not absorb much energy on its own; can be expensive |
| Airbag | Inflates quickly to cushion impact; very effective in cars | Complex technology; higher cost; single-use |
| Rubber bumper | Bounces back after impact; reusable and inexpensive | Less effective at absorbing energy compared to foam or crumple zones |
Connecting to Advanced Physics and Engineering
The ideas you are learning now connect directly to advanced topics in high school and college. The concept of evaluating designs against criteria is central to engineering design in every field, from building bridges to designing spacecraft.
| What You Learn Now | What Comes Next |
|---|---|
| Force = mass × acceleration (F = m × a) | Impulse-momentum theorem: Force × time = change in momentum (F × Δt = m × Δv) |
| Kinetic energy is transferred during collisions | Conservation of energy and momentum in elastic vs. inelastic collisions |
| Increasing collision time reduces force | Calculating impulse and analyzing force-vs-time graphs in detail |
| Evaluating designs against criteria and constraints | Formal engineering design process with optimization and failure analysis |
In high school physics, you will study momentum (mass × velocity) and learn that it is always conserved in collisions. You will also learn to read force-versus-time graphs to understand exactly how forces change during a crash. For now, the most important skill is being able to evaluate designs using evidence and clear reasoning.
Practice Problems
Test your understanding with these five problems. They start simple and get more challenging. Read each one carefully and think about criteria, constraints, and the math of collisions.
Lesson Summary
In this lesson, you learned how to evaluate collision-related designs by comparing test results to criteria (the goals a design must achieve) and constraints (the limits a design must stay within). You explored how Newton's second law (F = m × a) and the formula F = (m × Δv) ÷ Δt help you calculate the average force during a collision. Designs that increase the collision time reduce the force on the object being protected.
You also learned about tradeoffs — every design feature has strengths and limitations. A successful evaluation checks every criterion and every constraint, not just one. The crosscutting concept of cause and effect helps you connect design features to their outcomes. If a design fails, engineers use the redesign loop — they go back, make changes, and test again until the design meets all requirements.