A Beginner's Seven-Day Guide to Model Rocketry

India's rocket development, from early sounding rockets to today's launch vehicles, grew step by step, with each generation building on lessons proven by the one before it.

• Every generation of rocket answers a specific mission need, not just "build it bigger."
• Complexity is added only once earlier, simpler steps are proven reliable.
• Reliability and safety records earned on smaller vehicles justify moving on to more capable ones.
• Lessons from every test and flight — including failures — are documented and fed back into the next design.

Workshop connection: Inaugural keynote, 24 August 2026: Journey of Indian Rockets Development.

A model rocket is a small, purpose-built vehicle designed to fly straight up, coast, and return safely under a recovery device such as a parachute. Model rockets sit at the beginner end of a spectrum that also includes larger amateur (often high-power) and professional rockets used for research or orbital missions — the physics is shared, but scale, regulation and risk differ enormously.

• Thrust pushes the rocket, weight pulls it down, drag resists its motion through the air.
• For most of the flight, thrust and weight dominate the vertical picture; aerodynamic forces mainly keep the vehicle pointed the right way.
• Newton's third law explains thrust: the motor accelerates exhaust gas backward, and the rocket is pushed forward by the equal, opposite reaction.
• Main parts: fuselage (body tube), nose cone, fins, motor, and a recovery/deployment system.
• Flight has distinct phases — a rocket does not fly the same way from liftoff to landing.

Workshop connection: L1, Day 1 (25 August), 08:30–09:30.

Aerodynamics studies how air pushes and pulls on a moving object — nose shape, body diameter, surface smoothness and fin size all change a rocket's drag and stability. Structural analysis is the separate question of whether the airframe can survive flight loads without bending, cracking or coming apart.

• Centre of Gravity (CG) is where the vehicle's mass balances; Centre of Pressure (CP) is where aerodynamic force effectively acts.
• The general stability idea is that CG should sit ahead of CP by a workable margin — the exact acceptable margin comes from the official rulebook or a validated analysis, never a rule of thumb.
• A loaded (unfired-motor) rocket and a burnout rocket have different mass and CG, so both configurations need checking.
• Structural load paths — axial, bending, handling and recovery-shock loads — are traced from where a force is applied to where the structure resists it.
• A safety factor compares a material's allowable strength to the predicted load, giving a margin against uncertainty.
• Tools such as RASAero and FEAST predict aerodynamic and structural behaviour before a real test — they support engineering judgement, they do not replace it.

Workshop connection: L2, Day 1, 09:30–10:30.

"Avionics" (aviation electronics) is the set of onboard electronic systems that sense, decide, store and communicate. On a model rocket this usually means a flight computer, sensors, electrical power, data storage, a telemetry link, and outputs that trigger events such as parachute deployment.

• Sensors feed the flight computer with measurements (for example, altitude or acceleration).
• The flight computer runs basic flight-state logic — deciding, for instance, whether the vehicle has reached apogee.
• Power must reach the flight computer reliably throughout the flight, including through vibration and shock.
• Data storage keeps a record onboard even if the radio link is briefly lost.
• Deployment outputs are the signals the flight computer sends to trigger recovery events at the right moment.

Workshop connection: L3, Day 1, 11:00–12:00.

Validation is the structured process of proving an avionics system works before it flies: from checking individual components, to bench testing, to sensor calibration, to subsystem testing, to full integrated testing, and finally to an end-to-end mission rehearsal.

• Each test stage needs a defined expected input and output, and a clear pass/fail criterion.
• Calibration compares a sensor's output against a known reference input.
• Logging every test result creates an evidence trail that can be checked later.
• Power interruption and reset behaviour must be tested deliberately, not assumed.
• Fault handling — what the system does when something goes wrong — is tested, not just the "everything works" path.

Workshop connection: L4, Day 1, 12:00–13:00.

Sounding rockets carry instruments through the middle and upper atmosphere to measure conditions such as temperature, pressure, wind or radiation at altitudes aircraft and balloons cannot reach. The lecture introduces this context alongside a broader look at rocket aerodynamics.

• Sounding rockets are chosen because they can reach altitudes cheaper and faster than satellites for many short-duration measurements.
• A mission's target altitude, instrument requirements and recovery plan are decided together, not separately.
• Telemetry and recovery requirements both depend on how important it is to get the payload's data, or the payload itself, back.

Workshop connection: L5, Day 1, 14:00–15:00.

Across the week, students repeatedly sketch, refine and reason about their own rocket design in a guided hands-on practical block that runs on most afternoons.

• Start by identifying the mission objective and sketching a simple rocket with every subsystem labelled.
• List the assumptions behind the sketch explicitly, so they can be checked or corrected later.
• After each new lecture, return to the sketch and update it, noting what changed and why.
• Predict what could affect stability or recovery before those effects are actually tested.
• Record what was learned after each practical session — a design decision without a reason is hard to defend later.

Workshop connection: P1 (Day 1), P2–P3 (Day 2), P4–P5 (Day 3), P6–P7 (Day 4), P9 (Day 5) — Design and Fly Your Own Rocket.

Separation systems are the mechanisms that deliberately split a rocket into sections, or release a recovery device, at a planned point in the flight — most commonly to release a parachute near apogee.

• Every separation event needs a clear trigger, a mechanical restraint holding sections together until that trigger, an energy source that does the separating, and a clear path for the released section to move.
• Single-point failures — one part whose failure alone causes the whole event to fail — should be identified and, where practical, reduced with redundancy.
• Ground testing a separation system before flight is the only reliable way to know it works.

Workshop connection: L6, Day 2 (26 August), 08:30–09:30.

Mission design starts from the mission objective and Concept of Operations (ConOps) — what the rocket will do, in what sequence — and works backward to decide what needs to be measured and which sensors can measure it.

• Barometric pressure sensors estimate altitude from air-pressure changes.
• Accelerometers measure acceleration; gyroscopes measure rotation rate — together they form the core of an Inertial Measurement Unit (IMU).
• GNSS/NavIC (India's regional satellite navigation system) can provide position at a beginner level, with its own accuracy and update-rate limits.
• Temperature and voltage sensing protect the electronics and confirm the power system is healthy.
• Every sensor reading needs a sampling rate, a timestamp, a calibration and a defined unit to be useful.
• Sensing a value is not the same as making a flight decision from it — that step needs defined logic and a tested threshold.

Workshop connection: L7, Day 2, 09:30–10:30.

A launch rail is the mechanical guide that constrains a rocket's direction for the first part of its flight, before the fins can generate enough aerodynamic force to keep it stable on their own.

• Launch guides or rail buttons on the rocket slide along the rail, so their alignment and clearance must match precisely.
• "Usable rail length" is the travel available to the vehicle, not the rail's total physical length — these are not the same number.
• The rocket must leave the rail moving fast enough for its fins to take over stabilising duty; checking this needs verified mass and motor thrust data, not a guess.
• Pad angle, wind, and range-safety rules all influence a safe launch direction.

Workshop connection: L8, Day 2, 11:00–12:00.

This lecture extends L6 by looking at the different mechanical approaches used to achieve separation and the practical differences between them.

• Every separation event still needs precise timing, so it happens neither too early nor too late.
• Mechanical interfaces must be positively engaged before flight and reliably release on command.
• Design should actively prevent accidental separation from vibration, handling or aerodynamic loads.
• Clearance — the physical space the separating section needs to move freely — must be checked, not assumed.
• Verification always comes from a safe, controlled ground test, never from a first attempt in flight.

Workshop connection: L9, Day 3 (27 August), 08:30–09:30.

The power system supplies electrical energy to every avionics component — the flight computer, sensors and any radio — from a battery source, through wiring and connectors, sometimes via voltage regulators.

• Electrical power equals voltage multiplied by current (P = V × I, with P in watts, V in volts and I in amps) — this sets how much energy a component draws.
• Average load and peak load are different — a system must be sized for its peak demand, not just its typical demand.
• An energy and runtime budget checks whether the battery can supply the mission for as long as it needs to.
• Sensitive electronics should be isolated, where practical, from the higher-current loads of deployment devices to avoid interference or brownouts.
• Brownouts (a temporary voltage dip) and unwanted resets are real risks that need to be tested for, not assumed away.
• Batteries and wiring need secure mounting and visual inspection before every flight.

Workshop connection: L10, Day 3, 09:30–10:30.

Recovery systems bring the rocket, or its separated sections, back to the ground under control instead of free-falling. Common approaches include parachutes (main, and sometimes a smaller drogue for an initial descent), streamers and other descent-control devices.

• A drogue parachute, where used, provides a faster, more stable initial descent; a main parachute slows the final descent to landing.
• Streamers and winglet-style descent-control devices are alternative approaches described in the brochure — whether any specific device suits a given rocket depends on that rocket's own verified design.
• Descent mass and the recovery device's drag area together determine how fast the vehicle comes down.
• Harness and attachment points must be checked for the shock loads recovery events apply.
• Packing method and entanglement checks are verified on the ground before flight.
• Wind drift during descent affects where the vehicle lands, which matters for the recovery area and range safety.

Workshop connection: L11, Day 3, 11:00–12:00.

A static motor test fires a motor while it is securely mounted to an instrumented test stand rather than attached to a flying rocket, so its performance can be measured directly and safely.

• A thrust-time curve records how much force the motor produces at every moment of its burn.
• Peak thrust is the highest instantaneous force recorded; average thrust is the burn's overall force averaged over its duration.
• Burn time is how long the motor produces thrust; total impulse is the thrust integrated over the whole burn — a measure of the motor's total "push."
• Calibrated measurement equipment, remote operation and controlled access around the test stand are what make a static test safe and its results trustworthy.
• Test conditions and the motor's manufacturer documentation are both recorded so results can be compared meaningfully.

Workshop connection: L12, Day 3, 12:00–13:00.

Rocketry simulation software predicts how a rocket will fly before it is actually launched, using inputs such as geometry, mass, CG, the motor's thrust curve, drag, atmosphere and the planned recovery configuration.

• Typical outputs include predicted velocity, acceleration, altitude, stability margin and descent behaviour.
• A single "nominal" run is not enough — engineers also run worst-case and sensitivity cases to see how the prediction changes if an input is uncertain.
• Every simulation has limitations: it is only as accurate as its inputs and the physics it models.
• The model file, its exact input values, and its output plots should all be saved and version-labelled, so a result can be reproduced or checked later.

Workshop connection: P5, Day 3, 15:00–18:00.

These hands-on sessions walk through the practical steps of getting a rocket ready to fly: selecting an authorised launch site, checking weather conditions, assembling the rocket, packing recovery devices, and reviewing subsystem interfaces before integration.

• Site selection and weather review happen before any hardware is armed.
• Assembly follows a defined order and is checked against controlled drawings, not memory.
• Recovery devices are packed to a repeatable, tested procedure.
• Any late change to hardware or configuration must be re-checked, not assumed to still be fine.

Workshop connection: P4 (Day 3), P6–P7 (Day 4) — Preparing for Launch / integration practicals.

A solid rocket motor stores chemical energy in a solid propellant inside a casing. When ignited, the propellant burns in a combustion chamber, producing hot, high-pressure gas that accelerates out through a nozzle — the accelerating exhaust creates a reaction force (thrust) that pushes the rocket forward.

• The motor casing contains the propellant and combustion chamber and must withstand the pressure of burning.
• The nozzle shapes and accelerates the exhaust gas; its design affects how efficiently chemical energy becomes thrust.
• A thrust curve, burn time and total impulse describe a motor's performance over its whole burn (see L12 for how these are measured).
• Motors are grouped into classes at a high level based on total impulse — always sourced from certified, published data, never estimated.
• Motor retention — how the motor is mechanically held in the vehicle — is a structural interface, and motor mass materially shifts the vehicle's CG and performance.

Workshop connection: L13, Day 4 (28 August), 08:30–09:30.

Inertial systems measure motion directly, without needing an external reference like GPS satellites. The two core measurements are acceleration (from an accelerometer) and rotation rate (from a gyroscope); together they typically form an Inertial Measurement Unit (IMU).

• A reference frame is the fixed set of directions (e.g., up/down, forward/back) a measurement is described relative to.
• Bias is a small, steady offset error; noise is random fluctuation; drift is how an error grows over time — all three affect how trustworthy a raw sensor reading is.
• Sensor fusion means combining several imperfect measurements (e.g., accelerometer plus gyroscope) to get a better combined estimate — treated here conceptually, without advanced mathematics.
• How and where a sensor is mounted, and how carefully it is calibrated, directly affects the quality of its data.

Workshop connection: L14, Day 4, 09:30–10:30.

Quality assurance for rocket motors is the set of checks and records that confirm a motor meets its specification before it is trusted for use — this lecture covers the quality concepts, not manufacturing steps.

• Motors are sourced only from an approved supplier as a certified component.
• Traceability means being able to identify a motor's lot or batch, connecting it back to its manufacturing and test records.
• Visual inspection and dimensional/interface checks confirm a motor physically matches its specification before use.
• Storage and handling instructions from the manufacturer must be followed to keep a motor within its certified condition.
• Any deviation from specification is recorded as a non-conformance, and unresolved non-conformances are reviewed independently, not waved through by one person.

Workshop connection: L15, Day 4, 11:00–12:00.

This covers how a rocket sends measured flight data (telemetry) from an onboard transmitter through the air to a ground receiver, so a team can monitor the flight in real time and keep a record for later analysis.

• Antenna choice and placement affect how well a signal actually radiates and is received.
• Radio-frequency use is subject to regulatory permission — no frequency should be assumed to be automatically allowed.
• Data packets typically carry a timestamp, a sequence number, units for each value, and some form of integrity check so corrupted data can be detected.
• Range and orientation testing on the ground, and understanding line-of-sight limits, show what performance to expect in the field.
• Link loss (losing the radio connection) must have a defined, safe vehicle behaviour — the flight should not depend on the link staying up.
• Raw data is logged exactly as received, before any dashboard processing changes or interprets it.

Workshop connection: L16, Day 4, 12:00–13:00.

A launch checkout is a structured, ordered sequence of checks performed before a rocket is cleared to fly: configuration identity, mechanical inspection, recovery check, avionics power, sensor health, storage, telemetry, safe/arm confirmation, weather/site review, and a final go/no-go decision.

• Checklist discipline means following the written sequence exactly, not skipping ahead or reordering from memory.
• Critical items get two-person, independent verification, not a single person's word.
• Every check records who did it, when, and what the result was — this creates the evidence trail behind a go/no-go decision.
• If a check fails, the sequence stops there — later checks are not "worth doing anyway."
• Any hardware or configuration change after a check must trigger repeating the checks it could have affected.

Workshop connection: L17, Day 5 (29 August), 08:30–09:30.

This lecture covers how a rocket's physical configuration is controlled and verified end to end: the configuration drawing, how parts interface and fit, the order of assembly, fastener and cable-routing choices, mass distribution, tolerances, the Bill of Materials (BOM), inspection, and subsystem/integrated testing.

• A configuration drawing is the authoritative description of how the vehicle should be built — the physical vehicle should always match it.
• Assembly order and accessibility are planned in advance, not discovered mid-build.
• Cable routing and fastener choices must avoid interfering with other subsystems, including recovery deployment paths.
• A Bill of Materials (BOM) lists every part, so nothing is assembled from memory.
• "Configuration freeze" means stopping changes at an agreed point, so testing evidence still applies to the version that will actually fly; any needed change afterward goes through change control.

Workshop connection: L18, Day 5, 09:30–10:30.

ANSYS is a professional engineering analysis environment used here to demonstrate structural analysis (does the vehicle survive its loads?) and trajectory/mission analysis (how will it fly?) at a beginner-observer level — this is not a software tutorial.

• Every analysis needs defined inputs, assumptions and boundary conditions before it produces any output.
• A colourful, detailed-looking result plot is not, by itself, proof that the underlying model or inputs were correct.
• Mesh quality, for structural analysis, and other input checks are part of judging whether a result can be trusted.
• Reasonableness checks — does this output make physical sense? — and correlation against real test data are what actually build confidence in a simulation result.

Workshop connection: P8, Day 5, 11:00–13:00 — ANSYS team demonstration.

An ignition system is what starts a motor's burn on command, at the intended moment, under controlled conditions.

• Ignition is only ever performed with certified commercial igniters, used exactly per the motor manufacturer's instructions.
• A safe/arm separation keeps the ignition circuit disconnected from its power source until the last authorised moment before launch.
• Continuity checking — confirming the ignition circuit is electrically complete — is performed without energising the circuit, so the check itself cannot cause an accidental ignition.
• Controlled access around the pad, and authorised range supervision, govern every step from arming to firing.

Workshop connection: Threaded through L1, L12 and L13, and through the Safety and Quality Gate section of this page.

Technical project management is the discipline of organising a team's work so that a complex engineering effort — like building and flying a rocket — actually converges on a safe, working result on time.

• Team roles clarify who owns which subsystem and who makes which decisions.
• A work breakdown structure splits the project into manageable pieces; dependencies show which pieces must finish before others can start.
• A schedule turns the work breakdown into a timeline the team can actually track progress against.
• A risk register lists what could go wrong, how likely and severe each risk is, and what is being done about it.
• Action tracking, design reviews and configuration management keep decisions, changes and their justification recorded rather than lost in conversation.
• Evidence ownership means someone is responsible for each piece of verification evidence being complete and retrievable.

Workshop connection: Threaded through L15 (quality), L17–L18 (checkout and integration), and Day 6 competition preparation.

The final day covers preparing and delivering a technical presentation, following the official flight and range process to fly the rocket, and then comparing what was predicted against what was actually observed.

• A good technical presentation explains the mission objective, the system architecture and clear requirement-to-evidence traceability — not just a description of the finished hardware.
• Safety controls are presented honestly, including what was checked, what could not be fully verified, and why.
• The official flight and range process, and the authorised range officials' instructions, always take precedence over the team's own plan.
• After the flight, the vehicle is only approached and safed under authorised direction — never on the team's own initiative.
• Raw telemetry and photographs are preserved unedited, before any analysis or presentation touches them.
• Predicted and observed performance are compared explicitly; any difference is investigated, explained and turned into a corrective action, not dismissed.

Workshop connection: Day 6 (30 August): Competition Preparation, Presentation & Flight, Post-Launch Analysis, Valedictory Session.