Paper Airplane Flight Lab
The same lift-and-drag tradeoffs behind real aircraft design, tested with a single sheet of paper.
Related field: Aerospace Engineering
Mission Briefing
Objective
Design a paper airplane optimized for either maximum distance or maximum hang time (pick one goal), then test and refine it.
Constraints
- One sheet of paper only, no tape or glue
- Must be thrown by hand, not launched with any device
- Pick distance or hang time as your single goal before you start — you're optimizing for one, not both
Concept You're Testing
Lift and drag — how wing shape and weight distribution change how a plane behaves in the air, the same basic tradeoff real aircraft designers work with at a much larger scale.
What You'll Need
- Several sheets of paper (for multiple attempts)
- A tape measure or a way to count paces for distance
- A stopwatch or phone timer, if testing for hang time
Instructions
- 1Decide your goal: distance or hang time. This changes what you're optimizing for.
- 2Fold a basic paper airplane design as your starting point.
- 3Throw it 3 times with a consistent, similar-strength throw, and record the distance or flight time each time.
- 4Change one thing about the design — wing shape, nose weight (like a paperclip or folded tip), or wing angle.
- 5Test the new design the same way, 3 throws, same throwing technique.
- 6Compare the average of your first design against the average of your second.
- 7Make one more change based on what you learned, and test a third time.
How to Measure Results
Record the average distance (or hang time) across 3 throws for each design version, and compare them directly — a single throw isn't reliable data, but an average of 3 is a fair comparison.
Skills You'll Practice
- Why engineers test multiple trials instead of trusting a single result
- How small design changes (weight, angle, shape) measurably change performance
- Isolating one variable at a time so you know what actually caused a change
- The real tradeoff between stability and speed in flight design
If It Doesn't Work the First Time
That's normal — this challenge follows the same design process real engineers use. A failed test just tells you where to go back and improve.
Figure out what problem you're actually solving, and what would even count as success. Skip this step and jump straight to building, and a lot of bad designs happen right here.