12-16U cubesat platforms
The 12-16U class sits at the point where cubesat form factor stops being a constraint and starts being a deliberate choice: real propulsion, X-band downlink, and payloads that produce operationally useful data.
Why this size class exists at all
The 6U form factor made commercial cubesats credible. It proved that standardised rails, rideshare deployers and COTS electronics could survive launch and operate in orbit. What it could not do was carry a payload of any real aperture, store meaningful data volumes, or deorbit itself. Those limits are not bugs in the 6U design; they are physics. A 6U chassis offers roughly 4 litres of usable payload volume and perhaps 20-30 W of average power. That is enough for AIS receivers, GNSS-RO and narrow-band communications. It is not enough for a 15 cm optical aperture or an experimental SAR antenna of any utility.
The 12-16U class addresses that gap without crossing into the microsatellite regime, where bespoke structures, longer integration schedules and higher launch costs begin to dominate. A 16U chassis, typically 226 mm × 226 mm × 366 mm in the ISIPOD or equivalent deployer standard, offers 10-12 litres of payload volume and a solar-panel area that can sustain 60-80 W average orbit-mean power. That is the threshold at which propulsion, X-band transmitters and moderately capable imagers all fit on the same platform simultaneously. The step change is real.
What the power and propulsion budgets actually allow
Published platforms in this class, including NanoAvionics' 16U bus and GomSpace's GOMX-5 heritage, carry electrospray or cold-gas propulsion systems providing 10-50 m/s of delta-V. That is not enough for large orbit changes. It is enough for station-keeping in a constellation, collision-avoidance manoeuvres, and controlled deorbit from 500 km within the 25-year rule. For a national programme that cannot afford the reputational or legal exposure of creating debris, onboard propulsion at this scale is not optional.
Power architecture in a 16U typically runs a 3.7 V lithium-ion battery stack of 80-150 Wh capacity, charged by deployable GaAs or silicon solar panels. Eclipse fraction at 500 km SSO is roughly 35 percent of the 95-minute orbit, which means average available power for payload duty cycles sits between 25 and 50 W depending on panel configuration and seasonal beta angle. Thermal management becomes non-trivial at this power level: passive radiators on the chassis panels are usually sufficient, but a payload with high instantaneous draw, such as an experimental SAR, will require duty-cycle discipline enforced at the mission-control level, not just the hardware level.
Optical and SAR payloads: what the aperture can and cannot do
A 12-16U bus can accommodate a pushbroom optical payload with an aperture of 10-15 cm. At 500 km altitude, the diffraction limit for a 12 cm aperture in the visible band is around 3 metres, but detector pitch and optical quality in COTS-adjacent designs typically yield ground sampling distances of 4-8 metres. That is mid-resolution: adequate for crop-area estimation, urban-growth monitoring, deforestation mapping and infrastructure change detection. It is not adequate for reading vehicle types or inspecting individual structures. Buyers expecting sub-2-metre imagery from a 16U will be disappointed; that performance requires a larger bus or a lower orbit with the attendant atmospheric drag penalties.
Experimental SAR at this scale is genuinely experimental. Organisations including ICEYE demonstrated early SAR capability in a ~3U-equivalent form factor, but useful coherent SAR imagery at 1-3 metre resolution in their operational constellation required platforms in the 85-100 kg class. A 16U SAR payload is more credibly a technology demonstrator or a ground-moving-target-indicator than a production imaging asset. The antenna aperture constrains resolution in the along-track dimension regardless of signal processing; there is no algorithmic substitute for physical aperture. A government programme should be honest with itself about whether a 16U SAR serves a learning objective or an operational one, because the answer changes the procurement logic entirely.
X-band downlink and the data-volume ceiling
Below 6U, VHF and UHF dominate because the antenna gain and power required for S-band or X-band are hard to fit. At 12-16U, X-band patch or horn antennas become practical, and published downlink rates for commercial platforms in this class run from 50 Mbps to 150 Mbps over a 10-minute ground-station pass. At 100 Mbps, a 10-minute pass delivers roughly 75 GB of raw throughput before coding overhead, which is enough to downlink a full orbit's worth of compressed multispectral imagery from a 4-8 metre GSD imager. It is not enough to downlink uncompressed hyperspectral data cubes from a high-duty-cycle payload without on-board processing or selective downlink logic.
On-board computing at this scale has improved substantially. Platforms now routinely carry ARM Cortex-A or FPGA-based processors capable of scene classification, cloud masking or change-detection inference before downlink. This matters for national programmes with limited ground-station access: transmitting only flagged scenes rather than full strips can multiply effective throughput by a factor of three to five, depending on cloud cover and scene content. The trade-off is that on-board processing introduces software dependency and update cycles that the operating organisation must be prepared to manage.
Where this class genuinely struggles
Pointing accuracy is the first honest limit. Reaction wheels sized for a 16U chassis typically achieve 0.01-0.05 degree pointing knowledge with a good star tracker, but settling time after a slew can consume a significant fraction of the imaging window over a target. For a constellation of identical platforms, this is a schedule and operations problem. For a single national asset with one chance per day over a priority target, it can mean a missed acquisition.
Radiation tolerance is the second. COTS components used to keep costs in the cubesat range are not radiation-hardened. At 500-600 km in a low-inclination orbit, total ionising dose accumulates slowly enough that a three-to-five year design life is achievable with selective shielding. At higher inclinations crossing the South Atlantic Anomaly frequently, or above 700 km where the Van Allen belts intensify, single-event upsets become a routine operations problem rather than an edge case. Mission architects should model the radiation environment for the intended orbit before committing to a COTS-heavy bill of materials.
Finally, the 12-16U class sits in an awkward commercial position. It is large enough that launch providers charge it at a per-kilogram rate approaching dedicated small-satellite pricing on some vehicles, yet small enough that it cannot share a dedicated launch economically without a constellation partner. Rideshare on Transporter-class missions resolves this, but rideshare orbits are fixed. A programme that needs a specific inclination or local-time-of-ascending-node for its imaging mission may find the orbital options constrained by what the rideshare aggregator is selling that quarter.
Where Satellize uses this class
The 12-16U platform is the natural starting point for a national programme that wants an operational data product, not just a heritage flight. It is large enough to carry a payload that produces commercially interpretable imagery or signals intelligence, small enough to procure, integrate and launch within a 24-to-36-month programme schedule, and cheap enough that a second unit as an on-orbit spare is a defensible budget line rather than a luxury.
Satellize's crop-estimation analytics programme for the Kingdom of Tonga draws on satellite data at resolutions consistent with this class, and the experience of building analytics pipelines around mid-resolution optical data informs how we specify payload and downlink requirements for programmes in this size range. The honest answer is that a 16U platform is a capable first satellite for a sovereign programme and a credible constellation building block, provided the mission requirement is written to match what the physics allow rather than what a brochure implies.
Engineering parameters
| Mass class (platform + payload) | 20-30 kg typical; varies by propulsion and payload complement |
| Chassis volume (payload) | 10-12 litres usable payload volume in 16U configuration |
| Average orbit-mean power | 40-80 W (GaAs deployable panels, SSO 500 km); duty-cycle constrained for high-draw payloads |
| Propulsion delta-V | 10-50 m/s (electrospray or cold-gas); sufficient for deorbit and station-keeping, not large orbit changes |
| Attitude pointing accuracy | 0.01-0.05 degree (3σ) with star tracker and reaction wheels |
| Downlink rate (X-band) | 50-150 Mbps; 10-minute pass yields ~45-110 GB before coding overhead |
| Optical GSD (at 500 km) | 4-8 m typical for 10-15 cm aperture; diffraction limit ~3 m at 12 cm |
| Design life | 3-5 years in low-inclination LEO with COTS components; radiation environment at higher inclinations shortens this |
| Launch compatibility | ISIPOD or equivalent 16U deployer; rideshare or dedicated small-launch vehicles |
| Integration and test lead time | 18-30 months from PDR to launch-ready, depending on payload complexity and heritage |
One contract, one accountable engineer
Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Request a 16U mission architecture review.