Skip to content
N-1 · In buildN-1 build book
N-1 · Launch day · first flight

Launch day, from first email to the flight log.

Everything for getting N-1 to a club launch and back with its data: what to ask the club, what to pack, the exact switch-on sequence on the pad, recovery and what to do if something goes wrong. Tick things off as you go. Ticks are saved in this browser only. Print a copy for the field, where there may be no signal.

Non-negotiables. Certified commercial motors only, at a UKRA club launch, under the Range Safety Officer. An adult or the club buys, stores and fits the motor. A misfire is handled by the RSO's procedure: never approach early. Never make motors or propellant. Never go near power lines or climb trees to get a rocket back.

01 · Getting there

Find a club and ask first

N-1 flies only at a UK Rocketry Association (UKRA) club launch, with the Range Safety Officer (RSO) in charge. UKRA keeps a list of UK rocketry clubs with their websites and known flying dates. It asks you to check with each club directly before travelling, because launches get cancelled for weather. Pick the nearest club and get in touch well before the day you want to fly.

Safety codeThe UKRA Safety Code and the Model Rocket Safety Code. The RSO has the final say on how it applies.
MembershipUKRA membership is yearly (January to December) and has a junior category for under-18s. The page says flight insurance is mandatory and comes from the BMFA.
Under 18The Safety Code says children must be accompanied by a responsible adult. Bring one to every launch.

Ask the club before the day

These are questions, not answers. Write down what the club tells you.

02 · Weeks before

Test, weigh, check, practise

Everything here is done at home, with plenty of time to fix what fails.

03 · Range box

Packing list

Pack the range box the day before. The motor is not on your list: an adult or the club buys, stores and brings it.

The rocket

Recovery spares

Tools and repairs

Electronics and laptop

Paperwork

For you

04 · Night before

Charge, pack, rehearse

05 · At the field

Check in and prepare

  1. Check in with the RSO or club organiser. Say it is a first flight, show your membership and insurance details if asked, and find out where the prep tables, pads and the area for fliers and spectators are. Ask how they run the range today.
  2. Set up a prep table out of the way. Lay the rocket, tools and laptop out so nothing gets lost in the grass.
  3. Ground station. Antenna on the ground station board first, then plug it into the laptop. Double-click n1/mission/NOVTAR Mission Control.bat (it opens http://127.0.0.1:8770). Choose Ground station, pick its port, press Connect. The events list should say the radio is ok and that it is recording to a live_ file.
  4. Prepare the rocket. Check the recovery packing, fit the nose section and its two screws, and make sure the switch is off and reachable through the payload tube.
  5. Motor. The responsible adult or the club fits the motor, following the motor maker's instructions, and tightens the motor clips. You don't handle the motor.
  6. Flight card and inspection. Fill in the card, take the rocket to the RSO for inspection, and do what they ask.
  7. GO / NO-GO in Mission Control. The three top items tick themselves once the rocket is on and sending. Tick the other five yourself, honestly. Mission Control's GO is only your own check: the RSO's approval is what lets N-1 fly.

Mission Control's GO / NO-GO list

06 · On the pad

Switch-on sequence

This is what the N-1 firmware does when you switch it on, step by step. Do it on the pad, because the board measures the ground pressure at switch-on and calls that height zero.

  1. Rocket onto the rod or rail where the RSO or pad manager tells you. The club deals with the igniter and the launch controller, using their procedure.
  2. Antenna fitted? Never switch on without it. Sending without an antenna can damage the radio.
  3. Switch on. The board checks the barometer, accelerometer, log file and radio. 3 short beeps all four ok2 long beeps something failed: switch off, take it off the pad, don't fly
  4. Hold still for about two seconds. Straight after the beeps it averages 60 pressure readings for the ground level. It is then logging 10 times a second and sending 2 packets a second.
  5. Check Mission Control (best if a helper watches the laptop): phase PAD, BARO, IMU and LOG green, altitude close to 0 m, packets counting up, signal bars showing. The three automatic GO / NO-GO items should be ticked.
  6. If it isn't PAD (a hard knock can look like a launch: over 2.5 g three samples in a row), switch off, wait a moment and switch on again. Each switch-on starts a new log file, which is fine.
  7. Write down the time you switched on, and roughly how many times you have switched on today. The last log file is normally the flight.
  8. Walk back to the fliers' area. Don't run, and leave nothing on the pad.
  9. The RSO runs the countdown, out loud. Watch the rocket, not the screen. Your helper calls out what Mission Control shows.

The flight computer only measures. It has no firing or pyro output at all. The motor's own ejection charge pushes the parachute out. The radio uplink has only two commands, Ping and Locate, and the rocket ignores both unless it is in PAD or LANDED.

07 · After launch

Track, find, recover, download

  1. Watch it all the way down. Mission Control's phases go BOOST (motor burning), COAST (climbing), DESCENT (under the parachute), then LANDED. Keep your eyes on the parachute and pick a landmark in line with where it comes down (a tree, a gate, a pylon).
  2. Note where it landed before you set off: the direction, the landmark and the time. Mission Control keeps recording the whole time.
  3. Wait for LANDED and the RSO's go-ahead before you walk out. The UKRA Safety Code says recovery must not start until the descent is fully over. LANDED means the altitude has stayed steady, within 15 m of the pad height, for 5 seconds. From then the rocket chirps twice a second on its own.
  4. Locate. Once the rocket is LANDED, press Locate · beep in Mission Control. The rocket chirps four times a second for 10 seconds. Press it again as you get closer. If it lands somewhere more than 15 m above the pad (on a hill or up a tree) it may never say LANDED, and then it ignores Locate.
  5. Recover safely. Stay out of growing crops and away from livestock unless the club says it's fine. Never cross a road to chase a rocket. Never go near power lines, and never climb a tree: tell the RSO and leave it. The Safety Code says no one may approach a power line to recover a rocket, and no attempt may be made to recover rockets that land in dangerous places.
  6. Switch off only after LANDED. The board saves its log in blocks, and it saves everything when it decides it has landed.
  7. Download the flight back at the table. Either way works:
    • Mission Control: Rocket USB mode, connect, List flights, type the newest flight number and press Download flight. It is saved in n1/mission/flights/ and opens as a replay.
    • Command line, from n1/: python tools/download_flight.py lists the flights, then python tools/download_flight.py 3 saves flights/flight_003.csv and a chart, and prints the peak, top speed and highest g.
    Don't press Delete all logs until the flight is downloaded and copied somewhere else.
08 · If something goes wrong

Misfire, no signal, lost, damaged

Misfire (nothing happens)

Stay where you are. The RSO handles it using the club's procedure, and nobody goes near the pad until the RSO says so. Don't approach early, even if it looks dead. How long to wait and what happens next is the RSO's call: check the UKRA Safety Code and ask your club's RSO.

No telemetry

Don't hold the launch up for the radio unless you want to. The rocket logs to its own memory whether or not the ground hears it, so the flight is still recorded. Check the ground station antenna, the USB cable and the port, then reconnect. Afterwards, download the log over USB as normal.

Lost rocket

Note the last state and altitude Mission Control showed, and the direction it went. Walk the line from the pad towards the landmark, pressing Locate every so often and listening (it only answers in LANDED). N-1 has no GPS: that is planned for the next flight computer. Tell the RSO and the club, since your name and number are on the rocket. Never go onto land you're not allowed on.

No LANDED, or two long beeps

If it is down and still but still shows DESCENT, wait a minute and switch off. At most the last second or so of data is lost. Two long beeps at switch-on means a sensor, the log or the radio failed: don't fly it that day.

Damaged rocket

Don't fly it again until it has been checked at home: fins and fillets, motor mount and clips, shock cord and its anchors, parachute and blanket for burns, nose and bulkhead. Run the build book's bench tests again before the next flight.

09 · After the day

Log it and learn for N-2

Flight record

Date and site
Club and RSO
Motor and delay
Mass on the pad (g)
Weather and wind (as given by the club)
OpenRocket predicted peak (m)
Logged peak (m)
Log file name
Parachute out near the top?
Damage
Notes

Notes for N-2

What worked, what didn't, what was hard on the day, and what to change. Write it in the notebook or here once printed.