Students see rockets, drones, aircraft, and spacecraft and mistake the object for the research question. But a competitive aerospace project isn’t defined by what you build. It is defined by the research tradition you enter, and aerospace punishes poor scoping more severely than most fields. Regulatory, safety, and testing constraints can become hard limits only after months of work have already gone into a project.
Reviewed byDr. Richard McKee
Mentor for Aerospace and Robotics.Last reviewed July 2026.
Aerospace has a scoping problem that most STEM fields don’t.
Interest in aerospace has surged in recent times. Artemis II has brought crewed lunar exploration back into public conversation at a scale not seen in decades, and student interest in aerospace is rising with it. But converting that excitement into serious research requires more than choosing an aerospace topic. It requires knowing where the field actually allows a student to investigate, experiment, and contribute.
That is the breakdown we use at Future Forward Labs before a student touches a wind tunnel, a motor, or a flight controller.
Our Aerospace mentor, Dr. Richard McKee, has mapped the research landscape for middle and high school students, from viable research traditions and project directions to the regulatory and safety constraints that can shape what is possible. The goal is simple: know the boundaries before you build within them.
The Research Traditions Inside Aerospace
Aerospace engineering isn’t one discipline wearing a trench coat, it’s several, and a strong project lives clearly inside one of them.
Aerodynamics and fluid dynamics studies how air moves over a surface and how that surface should be shaped in response, airfoil design, drag reduction, boundary layer behavior. A real project here produces lift and drag coefficients. Most student attempts don’t. They test three wing shapes, note which one “flew farther,” and call it done, without ever quantifying the airflow that actually caused the difference.
Propulsion research lives in combustion efficiency, specific impulse, and nozzle geometry, how a fuel and a motor turn into thrust, and how efficiently. It’s also the category where a student’s age matters more than their equipment. Motor class caps what’s legally available to fly, long before it caps what’s scientifically interesting, which makes propulsion the one tradition where the regulatory ceiling has to be checked before the research question is finalized.
Structures and materials work asks how something holds together under stress, load-bearing capacity, fatigue over repeated cycles, how a composite layup behaves when it fails. Students underrate this category because it sounds like the least “aerospace” one on the list. In practice, it’s one of the most accessible: stress-strain testing and thermal cycling don’t require a launch site, a motor, or a certification of any kind. It’s also one of the fastest-moving: advances in thermal tolerance and ductility keep expanding what’s structurally possible in aerospace design, which means a student testing a new layup or coating today is closer to the field’s actual frontier than the “least aerospace” reputation suggests.
Astrodynamics and orbital mechanics, trajectory design, transfer orbit efficiency, launch window optimization, happens entirely on a laptop. No lab, no field, no motor to purchase. A student with a solid grip on calculus and Python can run genuinely rigorous orbital mechanics work using open tools like Poliastro or GMAT, and never leave their desk to do it. It’s about as close to “hands-on” as this field gets without actually going to space, the software lets students visualize orbital complexity in a way that’s genuinely rigorous, not just theoretical.
Avionics, guidance, and control systems cover how a flight vehicle senses its own state and corrects course, sensor fusion, stabilization algorithms, and autonomous navigation. Commercial flight controller hardware has gotten cheap enough in the last few years that this has quietly become one of the most original categories in student aerospace work, because the barrier to experimenting with real control systems dropped faster than most mentors’ advice caught up to it. It’s also one of the clearest bridges between aerospace and mechanical engineering, since the same sensor fusion and control-loop principles that stabilize a flight vehicle show up directly in robotics and mechanical systems work.
Uncrewed aerial systems (UAS) research uses the drone as an instrument, not as the subject, agricultural imaging, environmental mapping, search-pattern optimization. That distinction matters: “I built a drone” is an engineering demonstration, while “I used a drone to answer a data question” is a research project. Drones lend themselves to this range of applications precisely because they combine easy access to almost any location with a strong sense of their environment and a control system simple enough that the vehicle itself stays out of the way of the actual research question. It’s also the category most likely to run into the FAA before it runs into a science fair judge.
Human factors and life support research covers cabin environment design, radiation shielding, and physiological response to acceleration or microgravity, territory that’s gotten a lot more relevant since Artemis II put crewed lunar missions back in the news. No student has access to an actual microgravity chamber, so this work is almost entirely literature-and-design-based, which makes it one of the strongest no-equipment entry points on this list.
Systems engineering and space policy trade one prototype for one spreadsheet: mission architecture trade studies, launch system cost-benefit analysis, space debris mitigation strategy. It’s the category students skip because it doesn’t produce anything to hold up at a poster session. It’s also exactly what the Conrad Challenge scores on, since that competition rewards feasibility and systems thinking over a working build.
Two of these, astrodynamics and systems engineering, deserve more attention than they usually get, for the same reason bioinformatics deserves more attention in microbiology: they require no lab, no launch site, and no certification, and they’re taken increasingly seriously at the competition level.
The Rules Every High School Aerospace Researcher Needs to Know
Aerospace research has a regulatory layer that many high school researchers don’t encounter until much later: the rules governing what can be built, tested, launched, operated, or transmitted into the air. Depending on the project, that can involve FAA requirements, airspace restrictions, launch regulations, radio-frequency rules, export controls, and local or institutional safety requirements — many of which vary by state, municipality, or even the specific site a student is testing at. The challenge is not that every student needs to become a regulatory expert. It is knowing which rules apply before an experiment moves from a research question into a physical test, and where.
Model rocketry (A–G motors) has no certification requirement — but it’s not unregulated. Any student can fly A through G motors without NAR or Tripoli certification. This is where the overwhelming majority of viable student rocketry projects should live: motor comparison, recovery system design, altitude/apogee prediction modeling, staging efficiency. It still requires following NAR/Tripoli safety codes and, depending on size, may require flying at a sanctioned launch site.
High-power rocketry (H motors and above) has a hard age wall. Full NAR and Tripoli Level 1–3 certification is only available to members 18 and older. Students 14–17 aren’t locked out entirely, NAR’s HPR Participation Program and Tripoli’s Mentoring Program allow supervised flights under a certified adult, but an independent student research project cannot legally involve a minor holding their own H-motor-or-above certification. If a project concept requires impulse beyond G power, the realistic path is partnering with a certified adult mentor or a university rocketry club, not attempting it solo. This is worth knowing before a student designs a project around a motor class they can’t legally purchase.
Drone research has a clean line at “commercial or non-recreational purposes.” The FAA’s Part 107 Remote Pilot Certificate requires the pilot to be at least 16. A science fair or competition project is generally treated as a non-recreational purpose, which triggers Part 107 territory, meaning a 14-year-old with a data-collection drone project needs either to wait, or to fly under the direct supervision of a certified adult acting as pilot-in-command. This is the single most common compliance gap I see in student UAS proposals: the research question is sound, but nobody checked who’s legally allowed to fly.
High-altitude balloon projects trigger FAA notification requirements above certain thresholds. Unmanned free balloons are regulated under 14 CFR Part 101, with rules that scale by payload weight and balloon size, small “pico” balloon payloads typically fall under the regulatory floor, but anything approaching a standard high-altitude weather-balloon payload usually requires advance coordination with the FAA and air traffic control. This is a project category where the paperwork should be settled before a launch date is picked, not after.
Wind tunnel and CFD work has no regulatory ceiling at all, which is exactly why it’s underused. A student with access to a small subsonic wind tunnel, or none at all and only a laptop running open-source CFD (OpenFOAM, SimScale’s free tier, even simplified panel-method tools), can generate genuinely rigorous aerodynamic data with zero age restriction, zero certification, and zero FAA involvement. Most students haven’t yet learned to tune mesh sizes carefully, so their simulation results often drift from what an actual wind tunnel would show — but that gap is itself the lesson: it’s one of the clearest ways to learn the difference between a theoretical model and real-world performance, a distinction that shows up constantly once a student starts comparing results across projects. This is the aerospace equivalent of bioinformatics: the most accessible serious path, and the most overlooked one.
Competition rules layer on top of federal rules, and they’re not always the same thing. ISEF has a dedicated Aerospace and Aeronautical Engineering category, and Regeneron ISEF’s safety review process still requires documentation for projects involving combustion, pressurized systems, or anything flight-related, independent of whether FAA rules apply. The Conrad Challenge’s Aerospace & Aviation track, by contrast, doesn’t require a working prototype at all, it evaluates a design and business case, which is exactly why systems-engineering-style projects fit it so well.
What Separates a Real Project From a Demonstration
Learning this well is harder at the high school level precisely because there’s rarely a class for it, most students are piecing together astrodynamics, CFD, or control theory on their own, outside any curriculum, which is part of what makes the category demanding. But the same test applies here as anywhere else in student research: could a judge ask “so what’s the variable, and how did you isolate it?” and get a real answer.
“I compared three fin shapes and one flew highest” is a demonstration, no control for launch conditions, no repeated trials, no quantified aerodynamic explanation for why one performed differently.
“I modeled how fin cant angle affects spin-induced drag across three motor classes, validated the model against five trials per configuration, and quantified the trade-off between stability and altitude loss” is a research project, it has an isolated variable, a mechanism, repeated trials, and a quantified result.
The gap between those two sentences is almost never about access to better equipment. It’s about whether the student started from a specific, mechanistic question or from a topic. That’s true whether the topic is fin shape, orbital transfer efficiency, or drone flight-path optimization, and it’s the first thing worth nailing down before any motor, drone, or CFD simulation gets involved.
None of this should be read as a list of reasons not to pursue an aerospace project, quite the opposite. Artemis II just put a crewed lunar mission back in the public conversation for the first time in fifty years, and interest is real. The students who turn that interest into something competitive are the ones who pick a research tradition on purpose, understand which regulatory tier it lives in before they commit to it, and design a question a judge can actually interrogate. A mentor’s job is to help make that match before the building starts, not after.
