CubeSat Database-Nerfed

Baby, We're Back!

It took a minute, but the site is now retooled to take advantage of my new data partnership with Seradata's SpaceTrak.

Who knew that merging thousands of data entries would take so long?

Welcome!

This page contains my working list analyses of all CubeSats that have flown. I do not keep track of upcoming launches, as (a) launch dates and published manifests change up to the last minute, including after launch, and (b) I have a day job.

Speaking of day jobs, you won't find the list of CubeSats anymore; keeping track of an average of 1 new CubeSat every day was too much for any one person to manage. I now use Seradata's SpaceTrak service, augmented with my own work and the other references.

Click on the links below to jump to a section, or keep scrolling to see everything.

[Source: XKCD. Click on the image to visit the site, but be prepared to lose the next hour or so scrolling through the comics...]

Definitions

    • CubeSat. When we talk about "CubeSats", we're really talking about "containerized spacecraft"; so many CubeSats have flown because it is (comparatively) easy to qualify the containers for launch. Why? The container decouples the spacecraft from the launch vehicle; more so than any other launch system, the CubeSat restrictions and the container protect the launch vehicle from the secondary spacecraft. (And vice versa, but that's of lesser concern to the launch vehicle). So, as far as I'm concerned, a CubeSat-class spacecraft is any situation where the spacecraft is launched in a standardized container - or is compatible with such containers. Example containers:

      • The Opal ejector system. Opal is where the CubeSat idea was conceived and first executed.

      • The Space Shuttle Picosat Launcher (SSPL).

      • Any of the ejectors that are (mostly) compatible with the Cal Poly CubeSat Design Specification:

      • [please contact me to add your dispenser to this list!]

    • Mission Status. We have defined levels of mission success, based on what fraction (if any) of the mission objectives have been achieved. Mission status is distinct from spacecraft functional status; mission status is only concerned with how much of the primary mission has been achieved. An otherwise-functional spacecraft with a broken primary payload would be stuck at Level 3. A spacecraft that cannot downlink its mission data, for whatever reasons, would be stuck at whatever Level it achieved at the point of failure. A spacecraft that achieved its mission success and then died is still at Level 5.

      • 0 (Manifested): A launch date has been published. We don't keep track of missions until a launch date has been published. (And even then, we usually don't include them on the public database, below. Too much variability in launch dates/mission definitions before launch.)

      • 1 (Launched): The rocket began liftoff. (Launch failures usually stop at Mission Status 1.)

      • 2 (Deployed): The spacecraft is confirmed to have released from the launch vehicle.

      • 3 (Commissioning): The spacecraft has had at least one uplink and downlink.

      • 4 (Primary operations): The spacecraft is taking actions that achieve primary mission success (i.e., receiving commands, downlinking mission data)

      • 5 (Mission success): Primary mission objectives have been met. The spacecraft may continue to operate, run secondary missions, etc.

    • Mission Type. Missions are categorized as follows:

      • B (Passive): The spacecraft has no active functions, but there was still a good (?) reason it was launched. Examples include: a passive target (retroreflectors, etc) for an instrument on another spacecraft/ground system and the various companies that will fly your knickknacks (or ashes) into orbit.

      • C (Communications): The primary mission is to relay communications between two points. Amateur radio service and AIS tracking are common examples.

      • E (Educational): The primary mission is the education/professional training of the participants in the spacecraft design lifecycle. To be and E-class mission any science returns or technology demonstrations must be of secondary value to the education. Typically, E-class missions have no science or technology value, except to the mission developers themselves. E-class missions are also called "Beepsats", as they don't do anything but "beep" health & status data back to the ground.

      • I (Earth Imaging): The mission is to return images of the Earth for commercial and/or research purposes. Planet Labs' Dove constellation is the primary example.

      • M (Military): The mission has military relevance that does not properly fit in the other categories.

      • P (Proximity Operations/Servicing): The primary mission is to move this spacecraft to the region near another, for inspection and/or servicing tasks.

      • S (Science): The mission collects data for scientific research, including Earth science, atmospheric science, space weather, etc. To be S-class, there must be a clear connection between the data collected and end-user researchers; a spacecraft that measures the Earth's magnetic field and publishes the data on the web, hoping that some scientist will find the data useful, is not an S-class mission. (It's probably an E-class mission.)

      • T (Technology Demonstration): The mission involves the first flight of a new technology or capability, such that it is advanced one or more Technology Readiness Levels (or equivalent indicator). As with S-class missions, it is not enough to simply try out some new technology in space; there must be a clear, obvious process by which the behaviors of this new technology in orbit are validated.

      • V (Cargo Vehicle): The spacecraft is carrying other spacecraft and will release them on-orbit.

    • Class. The spacecraft class is the type of organization responsible for the design/construction/operation.

      • Civil (civ). Civilian government organization (e.g., NASA, JAXA, ESA).

      • Commercial (com). A private organization. If a contractor builds the spacecraft for another organization, then the satellite is classified as civil/military. And though Amateur satellites are by definition not commercial, AMSAT missions are classified here. (Sorry for the confusion.)

      • Military (mil). A government military/defense organization (e.g., the US Air Force).

      • University (uni). A university or other educational institution (including high schools). To be considered university-class, student education must be part of the core mission. Otherwise, if the university is contracted to build the spacecraft as if it were a professional organization, it will be classified under that organization.

    • Builder Type. Not all CubeSats are created equal, and you will get things very wrong if you assume that all CubeSats are the same. I have found it useful to subdivide the CubeSats by the characteristics of the builder. Mission types and success rates are VERY different across builder types.

      • Industrialists. Large, traditional space contractors who build high-performance spacecraft using standard practices. Industrialists are characterized by building high cost, long development time, high reliability spacecraft. In other words, you get what you pay for.

      • Hobbyists. Universities, secondary schools and others for whom this is an exciting opportunity to learn. Hobbyists are characterized by having low resources, a strong willingness to try risky approaches and -this should come as a surprise to no one - high failure rates.

      • Crafters. Also called “NewSpace” or “Smallsat”, crafters exist in the middle ground between hobbyists and industrialists. They have enough experience and capabilities to understand how to build & test space vehicles, but they are more accepting of risk than industrialists. Crafters are known for having well-performing spacecraft, relatively short development times and an aggressive risk posture.

      • Constellations. These builders have a very different objective; rather than trying to get one spacecraft to achieve a mission, they are trying to provide a continuous and/or distributed data service using many (dozens) of spacecraft. Because of this, the performance of one spacecraft has little bearing on the overall mission result. Planet and Spire are the most visible CubeSat constellations, but they are by no means the only ones.

References

Part 1: Sources of Data These are some of the key places where I gather spacecraft data. (Not counting personal communications/web scouring, of course.)

Part 2: Other Databases I don't draw my data from these sites, but that says nothing about the quality of their work. [Hint: It's high-quality work.]

    • Erik Kulu's Nanosat Database. Erik's public-facing page covers more than just CubeSats.

    • The Small Satellite Systems Virtual Institute (S3VI). Among many other elements, they are building a parts database.

Part 3: Student Collaborators. Many students have contributed to the management of this database

  • Marie Kendrick (2013)

  • Clay Jayne (2015-2017)

  • Spring 2019 team

    • Samantha Carlowicz, Scott Elliott, Connor Highlander, Andie Kaess, Tinevimbo Ndlovu, Cody Powers, Patrick Sullivan, Adam Walker, Sean Walsh

Part 4: My work My own papers/presentations on the subject. These papers cover not just CubeSats, but also secondary spacecraft and university-class spacecraft. They are listed with the most recent, first.