Latest 2,000 maximum · not a full-flight archive
LONG-DURATION FLIGHT / SMALL PAYLOAD. BIG WORLD.
Mission control
Solar-powered exploration, one packet at a time.
API connection is not a radio link
Viewed fixes only · excludes gaps
0 observation gaps >90m in view
Windows end at the latest loaded observation, not the current clock.
FLIGHT GEOGRAPHY
Last known position
The world is waiting.
The first valid GPS fix will place the balloon here.
THE FLIGHT, IN CROSS SECTION
Altitude & ground speed
Altitude, speed and coverage gaps will share this timeline.
Estimated ground speed averages successive valid fixes using onboard time. Blank across invalid fixes, boot changes, uncertain clocks and gaps over 90 minutes. Replay steps through received packets, not real elapsed time.
Energy
VNo readings in this window
Thermal
°CNo readings in this window
DETECTED FROM OBSERVATIONS
Mission events
Reception gaps, boot changes, GPS recovery and reported faults will appear here. This is not a launch-readiness checklist.
COMMUNITY GROUND NETWORK
Gateway reception
Each gateway’s packet count and mean signal levels appear here once an uplink arrives. Ocean silence is expected; it does not prove a failure.
Counts are unique packets per receiver in this window; one packet can reach several gateways. Signal averages use reported receptions.
EVERY RECEIVED OBSERVATION
Packet log
| Observed / UTC | Device · boot / seq | Altitude | Ground speed¹ | Supply | Outside | Fix / flags | Inspect |
|---|
Received packets will populate this log automatically. You can explore the full workspace with the demonstration flight.
How to read this mission · data limits & interpretation
Mission status comes from configuration, not an automatic inference that the balloon has launched. The API is polled every 30 seconds; this does not mean the radio transmits every 30 seconds. A last reception older than 90 minutes is labeled radio quiet, a display heuristic rather than a failure alarm.
The window contains at most the latest 2,000 observations, ordered by observation time. This is not the full archive. Network-received timestamps may describe buffered observations, so speed is omitted unless both observations have onboard timestamps. A valid fix can still contain GPS error; these plots are not navigation guidance.
Map lines connect successive valid fixes only, not a predicted trajectory. Distance excludes gaps over 90 minutes and invalid positions; it is neither total flight distance nor circumnavigation progress. Optional fields remain blank if not transmitted. Voltage is not state of charge.
Mission created: — UTC. Configured launch: Not set. Public, read-only telemetry. No flight commands are available here.