BRENNEN

Industries / Transport and vehicles / Aerospace and defense

Space launch and satellites

This is the work of designing, building and testing rockets and their engines, and the crewed spacecraft and satellites that rockets carry to orbit.

7

Milestones achieved, from 1926 to 2019.

3

To watch for: announced, not yet confirmed outside.

3

Open deliverables. Nobody has shipped them.

In depth

The same ground is charted in more depth, as an industry of its own.

The road

AchievedWatch forOpen

Achieved

  1. 1926

    First liquid-fuel rocket

    Robert Goddard launched a rocket that burned liquid fuel from a farm in Auburn, Massachusetts, on 16 March 1926. NASA calls it the world's first. It climbed 41 feet (about 12 m) and landed 184 feet (about 56 m) away, and NASA says the flight laid the foundation for rocket technology.

    nasa.gov

    Credit

    Robert H. Goddard

  2. 1957

    First artificial satellite

    On 4 October 1957 the Soviet Union put Sputnik 1 into orbit. NASA calls it the world's first artificial satellite. It was a ball 58 cm across that weighed 83.6 kg, launched on an R-7 rocket from Sergei Korolev's design bureau.

    nasa.govnasa.gov

    Credit

    Sergei Korolev and his design bureau, Soviet Union

  3. 1961

    First person in orbit

    On 12 April 1961 an improved R-7 rocket launched Yuri Gagarin in the Vostok 1 capsule, on a flight NASA gives as 108 minutes. Gagarin ejected at 20,000 feet (about 6 km) and came down by parachute, which Soviet officials did not disclose at the time; the Smithsonian says he still "remains indisputably the first person in space."

    esa.intairandspace.si.edu

    Credit

    Korolev's design bureau; cosmonaut Yuri Gagarin

  4. 1986

    Challenger and a known flaw

    On 28 January 1986 the Space Shuttle Challenger was destroyed 73 seconds after launch. The presidential commission traced the loss to failed seals in a joint of the right solid rocket motor, and found that NASA and the contractor, Morton Thiokol, had seen seal damage on earlier flights and in the end "treated it as an acceptable flight risk." In 2003 Columbia and its seven crew were lost after a piece of foam from the external tank broke through the wing's leading edge at launch, and the investigation board found that NASA had classed foam shedding as an "accepted risk" and that the causes behind Challenger "have not been fixed."

    LessonDamage that keeps showing up on flights that return safely is a warning, not proof that the design is safe.

    nasa.govnasa.gov

    Credit

    Rogers Commission (1986); Columbia Accident Investigation Board (2003)

  5. 2003

    A standard small satellite

    In 1999 Jordi Puig-Suari of Cal Poly and Bob Twiggs of Stanford had students build satellites in standard sizes, with a basic unit about 10 cm on a side that became known as the CubeSat. A standard satellite fits any rocket with spare room, so it can be built first and then wait for a ride. The first six CubeSats, built by universities in Japan, Canada, Denmark and the US, launched together on 30 June 2003 from Plesetsk, Russia. Cal Poly's specification, now Revision 14.1 (2022), still sets the sizes, a typical maximum mass of 2.00 kg per unit, and the checks each CubeSat must pass.

    science.nasa.goveoportal.org

    Credit

    Jordi Puig-Suari (Cal Poly) and Bob Twiggs (Stanford)

  6. 2017

    Boosters that fly again

    On 30 March 2017 SpaceX launched the SES-10 communications satellite on a Falcon 9 first stage that had flown before, then landed that stage again on a ship at sea. The first stage is the lower part of a rocket, which fires first and drops away. In 2021 NASA flew astronauts on a reused booster for the first time, and by August 2026 Spaceflight Now counted 614 launches on reflown boosters.

    collectspace.comnasa.govspaceflightnow.com

    Credit

    SpaceX

  7. 2019

    Satellites made by thousands

    SpaceX began launching its Starlink internet satellites in 2019, starting with a batch of 60 in low Earth orbit, the band of orbits up to about 2,000 km above the ground. The independent tracker Jonathan McDowell counted 13,122 Starlink satellites launched by 16 November 2026, with 11,199 working, and 1,554 deliberately lowered so they burned up. Others are following: McDowell lists 660 OneWeb satellites and 276 of China's Qianfan constellation in orbit.

    planet4589.orgplanet4589.org

    Credit

    SpaceX; counts by Jonathan McDowell

Watch for

  1. Catching an orbital upper stage

    On 14 November 2026, at the end of Starship's 15th flight test, SpaceX caught the Starship upper stage, the part that carries the payload the rest of the way to orbit, in the arms of its launch tower after about 14 orbits. The catch was reported by the press. Reuse has not yet been shown: no caught Starship upper stage has flown again, and every one of the 716 Falcon launches to date used a disposable upper stage, by Aviation Week's count. The booster on the same flight called off its own tower landing and came down in the Gulf of Mexico.

    Achieved whena recovered Starship upper stage launches to orbit again, as logged by an independent tracker.

    aviationweek.comspaceq.ca

    Claimed by

    SpaceX, November 2026

  2. China's first reusable boosters

    On 10 July 2026 a recovery ship off Hainan caught the first stage of the state-owned CASC's Long March 10B in a net of cables, and the team says it aims to fly that stage again by the end of 2026. On 19 August 2026 the company LandSpace landed its Zhuque-3 first stage on legs in Gansu, but the stage fell over a few hours later. In late October NASASpaceFlight reported the Long March 10B stage being readied for a mission; no reflight had been reported by 17 November 2026.

    Achieved whena recovered Chinese first stage flies a second orbital mission, confirmed by an independent tracker.

    news.cgtn.comspaceflightnow.comnasaspaceflight.com

    Claimed by

    CASC, July 2026; LandSpace, August 2026

  3. A robot fitting satellite jetpacks

    On 21 July 2026 a Falcon 9 launched Northrop Grumman's Mission Robotic Vehicle with three Mission Extension Pods, small engine packs that let satellites running low on fuel keep working. Its two robot arms, built by the US Naval Research Laboratory, are meant to attach the pods to client satellites in geosynchronous orbit, the high orbit where a satellite goes around once a day and seems to stay over one spot. The trip there takes about a year, and the named clients include Optus and SES.

    Achieved whena client operator confirms that the robot attached a pod and the satellite is running on it.

    news.northropgrumman.comspaceflightnow.com

    Claimed by

    Northrop Grumman, July 2026

Open

  1. 01

    Checklist from the CAD file

    A free program that reads a CubeSat's 3D design file (STEP format) and fills in the measurement lines of Cal Poly's CubeSat acceptance checklist: rail-to-rail width at the top, middle and bottom (100.0 ± 0.1 mm), rail lengths, the contact area at each rail end, the clearance from each rail edge to the first protruding part, how far any part sticks out from a face, and mass and centre of gravity from a mass table. It marks each line pass or fail against specification Revision 14.1 and highlights failures on the model.

    The brief
    Credit · unclaimed
  2. 02

    Telling commands from faults

    A fault detector for satellite telemetry, the stream of sensor readings a satellite sends home, that also reads the log of commands sent to the satellite. A jump caused by a command the operators sent is not raised as a fault; an unexpected jump still is.

    The brief
    Credit · unclaimed
  3. 03

    Inhibit count from the schematic

    A checker that reads a CubeSat's KiCad schematic and lists every route by which battery power could reach the radio transmitter or a deployable part, counting for each route the independent inhibits: physical switches in the power path, each controlled separately. It outputs the table and diagram that go into the team's electrical report.

    The brief
    Credit · unclaimed

Open 01 · the brief

Checklist from the CAD file

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A free program that reads a CubeSat's 3D design file (STEP format) and fills in the measurement lines of Cal Poly's CubeSat acceptance checklist: rail-to-rail width at the top, middle and bottom (100.0 ± 0.1 mm), rail lengths, the contact area at each rail end, the clearance from each rail edge to the first protruding part, how far any part sticks out from a face, and mass and centre of gravity from a mass table. It marks each line pass or fail against specification Revision 14.1 and highlights failures on the model.

Why it is still open

The checklist is a paper form, and Cal Poly's inspection procedure has a person zero the calipers, measure each item by hand and write it down. A 2025 study in Scientific Reports says "most CubeSat integration and acceptance testing relies on manual instruments such as Vernier calipers" and that there is no standard method for dimensional checks; that study tested a commercial 3D scanner on built parts, not the design file. A search found no tool that checks the design file.

cubesat.orgdoi.org

Built with what exists

CadQuery or FreeCAD (both built on the open OpenCascade geometry kernel); Python; the open cubesat-specs package on GitHub, which holds the specification's limits as data; OreSat's public STEP files for 1U, 1.5U and 3U frames as test cases. AI coding models can now write geometry scripts against an open CAD kernel.

  1. First step

    Download the OreSat 1U frame STEP files and write a CadQuery script that prints the rail-to-rail width at the top, middle and bottom.

  2. Done looks like

    On the three OreSat frames, every line matches a hand measurement in CAD to within 0.02 mm. On 20 altered copies, each with one planted violation (for example a 7 mm protrusion), it flags 20 of 20, with no false failures on the unaltered frames, and it outputs a filled checklist.

Open 02 · the brief

Telling commands from faults

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A fault detector for satellite telemetry, the stream of sensor readings a satellite sends home, that also reads the log of commands sent to the satellite. A jump caused by a command the operators sent is not raised as a fault; an unexpected jump still is.

Why it is still open

The European Space Agency's anomaly-detection benchmark paper says that beyond simple limit alarms, anomalies "are usually detected manually." For one mission it found that "no algorithm was able to accurately identify 9 actual anomalies" among rare but normal events, and it names telling these apart as "one of the important future works." A 2026 University of Maryland study found that precision "remains fundamentally bounded" by command-driven normal events.

arxiv.orgdrum.lib.umd.edu

Built with what exists

The benchmark's code (ESA-ADB, MIT licence, on GitHub) and its dataset on Zenodo; Python and PyTorch; open time-series forecasting models such as Amazon Chronos and Google TimesFM.

  1. First step

    Download the Mission 2 data, run the repository's baseline detector, and list which of the 9 anomalies it misses and which commanded events it raises alarms on.

  2. Done looks like

    Run with the benchmark's unchanged scoring code on its Mission 2 test set, the detector flags at least 8 of the 9 annotated anomalies with no more than one false alarm per real one, and a second person reproduces the numbers from the published code and weights.

Open 03 · the brief

Inhibit count from the schematic

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A checker that reads a CubeSat's KiCad schematic and lists every route by which battery power could reach the radio transmitter or a deployable part, counting for each route the independent inhibits: physical switches in the power path, each controlled separately. It outputs the table and diagram that go into the team's electrical report.

Why it is still open

The CubeSat Design Specification requires at least three independent inhibits each for radio transmission and for deployables. NASA's CubeSat 101 guide says compliance is shown in an electrical report, where the team marks the inhibits on a diagram by hand and explains "the number of inhibits and how they function." A search found no tool that works out the inhibit count from a schematic.

cubesat.orgnasa.gov

Built with what exists

KiCad 8 or later (its command-line tool exports a netlist); Python and networkx for path analysis; the OreSat battery card, whose repository includes the team's own inhibit diagram, and the PyCubed mainboard as test designs. AI models can now draw and check circuit boards, which the Note "Three working devices" covers.

  1. First step

    Export the OreSat battery card netlist with KiCad's command-line tool and print every path from the battery terminals to the main power bus.

  2. Done looks like

    On the OreSat battery card the inhibit list matches the team's diagram, and on PyCubed it matches a count made by hand by a second person. On 20 altered copies (one inhibit bypassed, or two inhibits sharing one control line) it flags 20 of 20 and flags nothing on the originals.