ARC

How to Choose an American Rocketry Challenge Coach (and Whether ARC Is Right for Your Student)

A parent's guide to evaluating ARC coaching: what good coaching actually looks like, the questions to ask, signs ARC fits your student, and honest reasons it might not.

Choosing a coach for the American Rocketry Challenge is not really about credentials on a wall. It is about choosing how your student will spend the next seven or eight months — how they will handle failure when a test flight doesn't hit the target, whether they will learn to reason from data or just follow instructions, and whether they will come out the other end with skills that transfer beyond rocketry. That is worth thinking through carefully before you commit.

This guide is for parents who are evaluating whether ARC is the right fit and, if so, what good coaching actually looks like. It is deliberately candid in places. Some students will read the fit signals below and decide this is not the right season for ARC. That is useful information.

Is ARC even right for your student?

ARC is structured as an open-ended engineering problem, not a kit build or a science fair presentation. Every season, teams receive a contest brief that specifies a target altitude and a flight duration window. Your rocket has to carry a raw egg, hit that altitude, stay aloft for the required time, and return the egg intact. The specific numbers change each year. No off-the-shelf design satisfies the brief — your team has to build something that actually works for that year's constraints.

That structure produces a specific kind of experience. Here are the signals that suggest a student will find it rewarding:

Genuine curiosity about how things work. Not performed enthusiasm for STEM, but actual interest in the question "why did that flight go 40 feet low?" Students who want to understand the mechanism tend to engage well with flight data and simulation. Students who just want to say they launched a rocket often check out by the third iteration.

Tolerance for a long feedback loop. ARC seasons run roughly September through April. A student who needs to feel successful within a few weeks will find the early design-and-simulation phase frustrating. A student who can stay curious across months of slow, incremental progress tends to thrive.

Willingness to be wrong and try again. The engineering loop in ARC is: simulate, build, test, measure, adjust. That loop runs multiple times in a season. Every test flight produces data that almost certainly shows something unexpected. Students who treat that as interesting learn a lot. Students who treat it as embarrassing tend to disengage from the data review and start guessing at fixes.

Openness to working through constraints, not around them. The altitude and duration targets pull against each other. A motor that gets you to the right altitude might bring you down too fast. A larger parachute that extends duration can also cause drift. There is no clever workaround — you have to engage with the trade-off. Students who want to find the one right answer quickly do not always enjoy this.

Now the anti-signals, which matter equally:

Wants fast, visible results. If a student's main motivation is having something impressive to show within a few weeks, ARC is probably not the right choice right now. The first several weeks involve simulation and design, not cutting and building. The first test flight often doesn't hit the target. Meaningful results take most of the season.

Over-scheduled. ARC competition teams need to meet regularly and consistently across a seven or eight month season. Design reviews, build sessions, test flights at a range, data review — these cannot be compressed into a burst of activity in March. If your student is already committed to activities that make consistent weekly engagement impossible, consider whether they can actually participate in the engineering loop or whether they will be showing up for parts of it.

No real interest in the engineering loop. Some students are interested in rockets but not in the iterative technical process of making them perform precisely. There is nothing wrong with that. A student who wants to launch rockets for fun without caring about simulation accuracy or flight data will probably find ARC frustrating. They might enjoy a recreational rocketry class instead.

One more honest note: first-season ARC teams frequently do not qualify. That is normal and not a failure — first seasons are how you learn the process. If your student needs to qualify in year one to feel the season was worthwhile, that expectation will need to be managed carefully.

What good ARC coaching actually looks like

The most common version of inadequate coaching is someone who knows the rules and makes sure students follow them. That is mentorship in the compliance sense, not coaching in the development sense. Here is what the distinction looks like in practice.

Real engineering or competition experience, not just subject knowledge. A physics teacher who has never run a simulation in OpenRocket and never stood at a range while a student's rocket underperformed by 80 feet does not have the right reference points to coach through ARC. The specific experiences that matter: running simulations and verifying them against actual flight data, diagnosing why a rocket didn't perform as predicted, making design decisions under time and budget constraints. A coach who has held a NAR certification and conducted their own qualification flights understands what happens between simulation and launch in a way a classroom teacher generally cannot.

Coaching the loop, not handing students a design. The fastest path to a working rocket is for a knowledgeable adult to hand students a proven design and tell them what to build. The contest rules prohibit this, and it also produces nothing educationally. Good coaches guide students through simulation setup, review their reasoning, ask questions that surface errors, and let the data from test flights drive design changes. The students should be making decisions, with the coach providing the framework for making them well.

Willingness to let students own the work. Related to the above, but distinct. Some coaches are uncomfortable watching students make decisions that will probably lead to a suboptimal first test flight. The instinct to step in and correct is natural, but it transfers ownership away from students. Good coaches let students fly the design they built even when it's imperfect, because the data from that imperfect flight is the most valuable teaching tool in the season.

Honest calibration about what a first season realistically achieves. A coach who tells a team of beginners they will definitely qualify is either uninformed or telling them what they want to hear. Most first-season teams spend more time understanding the engineering loop than they do approaching competitive scores. A coach who sets honest expectations and frames the season correctly keeps students motivated when results are slow.

Safety structure at the launch site. This is non-negotiable. Model rocketry is generally safe when protocols are followed. Coaches need to understand range safety procedures, RSO compliance, motor installation, and recovery system verification. A coach who waves safety steps as formalities creates real risk. A coach who treats every pre-flight check as genuinely important builds habits that will serve students across multiple seasons.

Questions to ask any ARC coach before you commit

These questions are designed to give you a clear picture of whether a coach meets the criteria above. A strong coach should have direct, specific answers to all of them.

"Who designs the rocket?" The answer should be: the students, with my guidance. If a coach says they provide a baseline design that students then build, ask how much the students deviate from it. If the answer is "not much," the engineering loop is not really happening.

"How do you use flight data?" You are looking for something like: we log every flight, compare the results to simulation predictions, identify the source of any significant discrepancy, and that drives the next design change. If the answer is vague — "we review what happened" — ask specifically what tool they use for data and how they interpret it with students.

"What does a typical session look like?" You want a concrete description, not a general philosophy. Does the coach have a prepared agenda? Is there a simulation review component, a build component, a debrief structure? Vague descriptions usually indicate sessions that lack structure.

"What safety setup do you have for test flights?" A serious answer involves familiarity with NAR/TRA range protocols, motor handling procedures, and RSO communication. It should include something about where students stand relative to the pad, how recovery is handled, and how launch-day go/no-go decisions get made.

"What do you consider a successful first season for a team with no prior experience?" This question surfaces expectations. An honest answer will be something like: understanding the simulation-to-flight feedback loop, completing at least three to four test flights, and arriving at qualifying with a characterized rocket they understand. A coach who says "qualifying at nationals" is either working with an unusually experienced team or setting unrealistic expectations.

"What's the format — group or individual coaching, and what does it cost?" In-person small-group coaching is typically more valuable for ARC than one-on-one, because team dynamics are part of what needs to develop. Competition team coaching is usually quoted separately from general preparation classes and reflects the additional time commitment of tracking a specific team's season. Make sure you understand what you are paying for.

"What does off-season support look like?" The gap between qualifying and nationals, or between one season and the next, is when teams that are serious about long-term improvement do their best work. Coaches who disengage outside the main competition window are less useful to teams trying to build multi-season capability.

How SEALS approaches it

SEALS Academy's ARC coaching is led by Eric Song, who holds a NAR Level 1 certification with a qualification flight at 1,500 feet apogee, serves as avionics compartment co-lead on a NASA Student Launch Initiative team, and founded an 80-plus-member Aviation and Aerospace Club at Portola High School. His background is in the technical and competition-facing aspects of rocketry — simulation, motor selection, avionics, and airframe construction — which means coaching sessions are grounded in the same tools and decisions students will actually face.

The coaching model follows the engineering loop: simulate, build, test, measure, adjust. That means sessions include time with OpenRocket and actual flight data review, not just build time. Students work through their own design decisions; Eric's role is to ask the questions that surface errors in reasoning before they show up as errors in flight data.

The format is in-person and small-group, which fits ARC well. Teams need to develop collective understanding of their rocket's behavior — it is not enough for the simulation lead to understand the model if the recovery lead does not understand how parachute size affects duration. Session work reflects that: all team members engage with all subsystems at the level needed to troubleshoot on launch day.

Coaching is offered as small-group preparation sessions, alongside competition team coaching — structured support across a full ARC season, including simulation setup, test flight review, and qualifying preparation. Pricing depends on format, team size, and session frequency; see the ARC classes page for current options and to request a quote.

One thing SEALS does not do: we don't fabricate a track record we don't have. SEALS Academy launched in 2025, so we don't yet have years of past qualifying teams to point to. The credibility here comes from Eric's actual engineering and competition experience, not from years of program history. If you need a program with a long list of past qualifying teams, SEALS may not be what you are looking for right now. If you want coaching from someone who has personally run the qualification flight, worked through the simulation-to-flight discrepancy loop, and understands what the data actually means — that is what we offer.

When to wait, or look elsewhere

ARC coaching is worth the investment when the conditions are right. It is probably not the right investment when:

Your student has never engaged with any building or making activity. ARC requires hands-on fabrication. Students who have no baseline comfort with tools, materials, and the iterative process of making something physical will spend their first season uncomfortable rather than learning. Starting with a shorter introductory rocketry or 3D printing class builds that foundation before competition prep begins.

The team isn't formed yet. ARC is a team activity. Coaching a single student who doesn't yet have teammates produces preparation without the context it applies to. Forming a team first — ideally before the coaching engagement starts — makes the coaching substantially more useful.

Your student wants to do ARC because their friend is doing it, not because they are actually interested. Social motivation can work, but only if the student develops real engagement with the content once the season starts. Parents can usually tell the difference. A student who is indifferent to the mechanics of why a rocket performed the way it did will not find six months of iterative engineering rewarding.

The schedule won't support consistent engagement. If the honest answer is that your student can participate in coaching sessions sporadically, you will spend money on coaching that cannot accumulate into genuine skill because the feedback loops get broken. Wait for a season when the schedule is actually clear.

Next steps

If the fit signals above describe your student reasonably well, and the coaching criteria give you a framework for what to look for, you have most of what you need to make a decision.

For more on what ARC actually involves before you go further, read getting started with the American Rocketry Challenge. If you are trying to understand the time commitment before committing, how to prepare for ARC season gives a week-by-week picture of what a focused preparation cycle looks like.

If SEALS Academy looks like the right fit for your student's team, you can review current coaching options and reach out at sealsacademy.com/arc/classes.

Share this guide:

Related guides

Getting Started

Getting Started with the American Rocketry Challenge

A complete beginner's guide to ARC — who can enter, how teams form, key dates, and what you need to build your first competition-ready rocket.

By SEALS AcademyRead guide →
Season Preparation

How to Prepare for ARC Season: A 12-Week Training Overview

A practical 12-week preparation roadmap for ARC teams — what to focus on each phase, from initial design through qualifying flights.

By SEALS AcademyRead guide →
Competition Strategy

ARC vs. Hobby Rocketry: What's Actually Different

Compare American Rocketry Challenge rockets with hobby rockets, and see how scoring constraints change design, testing, and team training.

By SEALS AcademyRead guide →

Want hands-on coaching?

Our coaches can help you apply what you've read.

Personalized ARC coaching for simulation, design review, flight data analysis, and qualifying preparation.