Unit 01 · Day 5
Plan the Paper Helicopter
Turn a question into a preregistered, safe, repeatable investigation plan before seeing the results. Today the quality of the design—not an exciting outcome—is the scientific product.
Learning objectives
By the end of this lesson, you should be able to:
- State a testable paper-helicopter question with one planned independent variable and an operationally defined dependent variable.
- Specify variable levels, controls, trial count, measurement method, and comparison logic before collecting data.
- Write a repeatable procedure precise enough for another learner to reproduce without guessing.
- Design a raw-data table before observing results.
- Identify safety hazards, stop conditions, confounders, and likely measurement limitations.
- Write a directional prediction with scientific reasoning while keeping prediction separate from evidence.
Materials
- Plain paper from one consistent source
- Metric ruler
- Pencil
- Scissors used normally and safely
- Paper clips, only if held constant across all tested designs
- Stopwatch/timer
- Science notebook or printed investigation sheet
- Science Studio tools for calculations or design review when appropriate
Use scissors only for normal paper cutting. Use a clear floor-level drop area with stable footing. Do not climb on chairs, tables, railings, stairs, counters, or other elevated surfaces to increase drop height. Keep people, pets, fans, open windows, fragile objects, liquids, flames, electrical equipment, and traffic paths away from the test area. If a safe repeatable drop height cannot be established from the floor, use a lower height rather than improvising.
1. Phenomenon and question
A paper helicopter converts gravitational potential energy into downward motion while its rotating paper surfaces interact with air. Small design changes can alter its motion, but several features can change at once unless the investigation is carefully controlled.
This question names a manipulable design feature and a measurable response. It does not assume in advance that longer rotors are “better.”
Underline the independent variable, circle the dependent variable, and identify the comparison condition. Then rewrite the question if your available materials require a safer or more measurable version.
2. Define the variables before testing
| Design element | Core plan | What must be documented |
|---|---|---|
| Independent variable | Rotor length | Exact lengths in cm and how each is measured |
| Dependent variable | Fall time | Timing start/stop rule and unit |
| Controls | Paper, body width/length, mass, folds, drop height, release, location | How each is kept sufficiently consistent |
| Possible confounders | Air currents, inconsistent release, damaged designs, different paper, timing differences | Prevention, monitoring, or limitation statement |
3. Choose defensible variable levels and trials
Foundation learners may compare two clearly separated rotor lengths. Core learners should compare at least three. Extended learners may use five or more levels and investigate whether the relationship appears linear or curved within the tested range.
Use at least five trials per rotor length. More trials can better reveal variation, but they do not repair a confounded or unsafe design.
List each rotor length in centimeters and explain why the values are different enough to create a meaningful comparison while still producing functional helicopters.
4. Operationalize the fall-time measurement
Your method must tell another investigator exactly when timing begins and ends. For example: “Start timing when the helicopter is released without a push; stop when the first part of the helicopter contacts the designated landing surface.” State the drop height and how it is measured.
Name your timer resolution. Identify one source of random timing variation and one possible systematic bias. State how repeated trials or a procedural check will address them.
5. Write the method as a reproducible protocol
- Describe how one standard helicopter is constructed and which dimension will vary.
- State every rotor-length level and the number of helicopters/design copies, if more than one is used.
- Define the fixed drop height and safe release location.
- Define the release technique without adding a push or spin unless that is intentionally standardized.
- Define timing start and stop rules.
- State the order of conditions. Consider alternating or randomizing condition order when practical so time-related changes do not always favor one design.
- State the minimum of five trials per condition.
- Record each raw trial immediately; never replace an inconvenient result merely because it looks unusual.
- Document any protocol deviation, damaged helicopter, interruption, or environmental change.
Give your written method to another person or the Science Mentor without explaining it aloud. What questions would they still need to ask? Revise until the important decisions are explicit.
6. Build the raw-data table before seeing results
Prebuilding the table protects against selectively recording only convenient observations.
| Rotor length (cm) | Trial 1 (s) | Trial 2 (s) | Trial 3 (s) | Trial 4 (s) | Trial 5 (s) | Notes / deviations |
|---|---|---|---|---|---|---|
| _____ | ||||||
| _____ | ||||||
| _____ |
Do not put calculated means in place of raw trials. Calculated summaries come later and should remain traceable to the original observations.
7. Prediction is not evidence
Write a directional prediction only after the design is specified. A useful hypothesis links the expected pattern to a plausible scientific mechanism but remains open to being unsupported by the data.
Use this structure if helpful: “If rotor length increases, then mean fall time will ______ within the tested range because ______.” Then identify one result that would fail to support your prediction.
8. Safety and stop-condition scan
Before approval, answer all of these:
- Is the drop area clear and reachable from stable floor-level footing?
- Can every cut be made with ordinary safe scissor use?
- Are people, animals, fans, open windows, fragile objects, liquids, heat, and electrical equipment clear?
- What will make you stop a trial—for example, someone entering the drop area, a damaged helicopter, unsafe footing, or a major environmental change?
- What will you do if the written method cannot be followed safely? Stop and redesign; do not improvise around the safety requirement.
9. Science Studio + Mentor design defense
Use the Science Studio investigation-design/evidence tools to review your variable map, raw-data structure, and calculation plan. Tools support the design; they do not decide whether your experiment is scientifically defensible.
Then bring the plan to the Science Mentor and be prepared to answer:
- Why are your chosen rotor lengths informative?
- Which uncontrolled factor is most likely to imitate an effect of rotor length?
- How will another investigator reproduce your release and timing method?
- What result would contradict your prediction?
- Which safety condition is non-negotiable?
Mentor review is a reasoning conference, not permission to bypass local adult/laboratory safety requirements.
10. Approval gate
Do not collect experimental data yet. Your plan is ready only when every item below is complete.
| Gate item | Ready? |
|---|---|
| Testable question and directional prediction are written separately | □ |
| Independent/dependent variables are operationally defined | □ |
| Controls and plausible confounders are documented | □ |
| Rotor levels and ≥5 trials per condition are specified | □ |
| Drop height, release, timing, and landing rules are explicit | □ |
| Raw-data table exists before results | □ |
| Instrument resolution/measurement limitation is noted | □ |
| Safety scan and stop conditions are complete | □ |
| Method is reproducible without hidden verbal instructions | □ |
11. Choose your pathway
| Pathway | Planning requirement |
|---|---|
| Foundation | Two rotor lengths, ≥5 trials each, complete variable/control map, raw-data table, safety scan, and repeatable timing method. |
| Core | At least three rotor lengths, ≥5 trials each, full confounder/measurement analysis, reproducible protocol, and design defense. |
| Extended | At least five levels where feasible; preregister how you will examine shape of the relationship, condition order, anomalous trials, and whether additional replication is warranted. |
12. Exit check
- Why must the raw-data table be created before data collection?
- Why do five trials not fix a confounded design?
- What makes an operational definition reproducible?
- What is the difference between a prediction and a conclusion?
- Name one reason to document a protocol deviation instead of silently deleting that trial.
Save the approved question, prediction, variable map, full protocol, data table, safety scan, measurement-quality statement, and design-defense revisions. Lesson completion does not replace the ≥80% Unit 01 mastery requirement.