CubeSat Database
Plots are Down; Will Return c. May 15th
This is a scheduled interruption in service. Plots will return.
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:
Cal Poly's P-POD.
The ISIPOD and QuadPack
JAXA's ejector for the International Space Station (J-SSOD), brokered by NanoRacks.
NanoRacks has its own dispenser, the lengthily-named NanoRacks CubeSat Deployer (NRCSD).
The Pico Satellite launcher (PSL), by Astro- und Feinwerktechnik, which comes in Single, Double and Triple variants; all variants will be labeled as PSL in the database.
NASA's NLAS.
Planetary System Corp.'s Canisterized Satellite Dispenser.
Tyvak's RailPOD.
[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.
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.
Orbit Status. Indicates where the spacecraft currently resides
D (Deorbited): The spacecraft orbit has decayed, and it has re-entered the Earth's atmosphere.
O (On-orbit): The spacecraft has been deployed and is free-flying in orbit.
S (Stowed): The spacecraft has launched into orbit, but is still stowed inside its launch container. (ISS CubeSats can sit on station for months.)
L (Launch Failure): The spacecraft was lost to a launch failure.
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.
The Database
Apologies; since I no longer keep track of this information myself, I'm no longer publishing the list of Cubesats. If you have questions or have suggestions for making new/better plots, please contact me (mswartwo@slu.edu). I love looking at this data, and would gladly spend more time talking about it than you want me to.
References
Part 1: Sponsors. This work has been supported, strongly, by the NASA Parts and Packaging Program (NEPP) through grants 80NSSC20K1230, NNX15AV50G, NNX17AJ46G, and 80NSSC18K0637.
Part 2: Data Partner. Though I consider myself to be very much the junior partner, I am partnering with Seradata to generate the analyses shown here. I continue to augment their data with my own work.
Part 3: Sources of Data. These are some of the key places where I gather spacecraft data. (Not counting personal communications/web scouring, of course.)
Gunter's Space Page. The gold standard, by my reckoning.
The many communications surveys compiled by Bryan Klofas.
Mike Rupprecht's (DK3WN) SatBlog gives daily updates on a lot of active Amateur spacecraft.
AGI's SpaceBook.
SatNOGS mission database.
The online proceedings of the Conference on Small Satellites.
Part 4: 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 5: 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 6: 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.
2019
L. Berthoud, M. Swartwout, J. Cutler, D. Klumpar, J.A. Larsen, J.D. Nielsen, "University CubeSat Project Management for Success", presented at the 33rd AIAA/USU Conference on Small Satellites, Logan, UT, 3 August 2019; paper SSC19-WKIII-07.
M. A. Swartwout, "CubeSats: Toys, Tools or Debris Cloud?", presented as part of the Science in St. Louis series, St. Louis, MO, 29 April 2019.
M. A. Swartwout, "CubeSat Mission Success: Are We Getting Better?", presented at the 2019 CubeSat Developers Workshop, San Luis Obispo, CA, 23 April 2019. Thanks to Cal Poly, you can watch the presentation here.
2018
M. A. Swartwout, "Reliving 24 Years in the next 12 Minutes: A Statistical and Personal History of University-Class Satellites", presented at the 32nd AIAA/USU Conference on Small Satellites, Logan, UT, 5 August 2018; paper SSC18-WKVIII-3. See also a page with all the plots/tables here.
M. A. Swartwout, "All CubeSats are Not Created Equal: How Mission Success Rates (and Risks) Change with the Builder and Mission Type", presented at the 2018 NASA-ESA-JAXA Trilateral Mission Assurance Conference, Cape Canaveral, FL, 4 June 2018.
M. A. Swartwout, "Small Satellite Reliability: .Updates through 2017", presented at the Small Satellite Reliability Initiative TIM-3, San Luis Obispo, CA, 3 May 2018.
M. A. Swartwout, "You Say 'Picosat', I Say ''CubeSat':.Developing a Better Taxonomy for Secondary Spacecraft", presented at the 2018 IEEE Aerospace Conference, Big Sky, MT, 7 March 2018. https://doi.org/10.1109/AERO.2018.8396755.
2017
M. A. Swartwout, "CubeSats and Mission Success: 2017 Update", presented at the 2017 Electronic Technology Workshop, NASA Electronic Parts and Packaging Program (NEPP), NASA Goddard Space Flight Center, 27 June 2017.
2016
M. A. Swartwout and W. C. Jayne, "University-Class Spacecraft by the Numbers: Success, Failure, Debris. (But Mostly Success.)", presented at the 30th AIAA/USU Conference on Small Satellites, Logan, UT, 11 August 2016. See also this page with the plots/tables and presentation.
M. A. Swartwout, "CubeSats and Mission Success: 2016 Update", presented at the 2016 Electronic Technology Workshop, NASA Electronic Parts and Packaging Program (NEPP), NASA Goddard Space Flight Center, 14 June 2016.
M. A. Swartwout, "CubeSats and Mission Success: A Look at the Numbers", presented at the 2016 CubeSat Developers Workshop, San Luis Obispo, April 2016.
2014
M. A. Swartwout, "CubeSats: Toys, Tools or Debris Cloud?", invited talk at the 2014 St. Louis Space Frontier Gateway to Space Conference, 8 November 2014. (Note that this talk borrows heavily from the Goddard presentation, below. The new material is at the end, with the discussion of debris.)
M. A. Swartwout, "The First 100 200 272 CubeSats", invited talk at the EEE Parts for Small Missions 2014 Workshop, NASA Electronic Parts and Packaging Program (NEPP), NASA Goddard Space Flight Center, 11 September 2014.
M. A. Swartwout, "Secondary Payloads in 2014: Assessing the Numbers", 2014 IEEE Aerospace Conference, Big Sky, MT, 1-8 March 2014, doi:10.1109/AERO.2014.6836390
2013
M. A. Swartwout, "The First One Hundred CubeSats: A Statistical Look", Journal of Small Satellites (2):2, 2013, pp. 213-233.
M. A. Swartwout, "The long-threatened flood of university-class spacecraft (and CubeSats) has come: Analyzing the numbers", Proceedings of the 27th Annual AIAA/USU Conference on Small Satellites, Logan, UT, 12-15 August, 2013, Paper SSC13-IX-1.
M. A. Swartwout, "Cheaper by the dozen: The avalanche of rideshares in the 21st century", 2013 IEEE Aerospace Conference, Big Sky, MT, 2-9 March 2013, doi: 10.1109/AERO.2013.6497182
2011
M. A. Swartwout, "Attack of the CubeSats: A Statistical Look", Proceedings of the 25th Annual AIAA/USU Conference on Small Satellites, Logan, UT, August 2011, Paper SSC11-VI-04.