> For the complete documentation index, see [llms.txt](https://wiki.kscucf.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.kscucf.org/projects/tethered-satellite/t-sat-2/t-sat-2-project-b/timeline.md).

# Timeline

How TSat-2B went from kickoff in September 2025 to its flight on March 28, 2026.

This page records how TSat-2B actually went, from kickoff to launch, so future teams can plan their own schedules.

## At a glance

|                  | Planned          | Actual                                                 |
| ---------------- | ---------------- | ------------------------------------------------------ |
| Kickoff          | Early fall 2025  | First meeting September 16, 2025                       |
| Design reviews   | Fall 2025        | PDR started September 25; CDR started October 14, 2025 |
| Parts ordered    | October 2025     | October 30, 2025                                       |
| Ready for launch | End of fall 2025 | March 9, 2026                                          |
| Launch           | End of fall 2025 | March 28, 2026 (launched together with TSat-2A)        |

## Fall 2025: design

* **September 16, 2025:** first TSat-2B meeting. Goals for the week: introduce members, set a baseline for the project goals, and take input on what members wanted to build.
* **September 18, 2025:** work began on the Project Concept Proposal. OpenHD was suggested for live video because it could later be reused on a high-altitude balloon.
* **September 25, 2025:** Preliminary Design Review (PDR) document started. CAD of the housing began the next day.
* **October 7, 2025:** a code repository was set up for the telemetry software. It was moved into the club's GitHub organization on October 28.
* **October 13, 2025:** the team decided not to carry a parachute. TSat-2B stays tethered and is reeled back in, so a parachute would add nothing to its goals.
* **October 14, 2025:** Critical Design Review (CDR) document started. First version of the telemetry PCB schematic.
* **October 22–23, 2025:** first PCB layout. Live video hardware chosen: a Raspberry Pi Zero 2 W with ASUS USB-AC56 Wi-Fi adapters, a popular choice for OpenHD.
* **October 28, 2025:** the team weighed SDIO against SPI for the SD card. SPI is simpler and fast enough for telemetry without images.
* **October 30, 2025:** orders placed for both TSat-2 teams.
* **November 4, 2025:** breadboard test setups for the Wi-Fi adapters and sensors.
* **November 14, 2025:** live video working on the bench.
* **November 2025:** PCBs ordered. They arrived over winter break, so assembly waited until January.

## Spring 2026: build, test, and launch

* **January 21, 2026:** meetings resumed, three days a week.
* **January 30–February 6, 2026:** final parts printed and the satellite assembled, using M2 heat-set inserts. A telemetry SD card that wouldn't initialize worked again after reformatting.
* **February 11, 2026:** live video working again after an SD card problem on the air unit. A longer camera cable stopped the system from booting, so the team kept the short cable and changed the CAD to fit it.
* **February 20–23, 2026:** field tests on Memory Mall. Live video worked reliably to about 750 ft.
* **March 4, 2026:** battery life on the chosen power setting measured.
* **March 9, 2026:** all planned testing complete; ready for launch.
* **March 13, 2026:** the team was filmed for UCF's Charge On Air, which aired on March 31.
* **March 23 and 27, 2026:** launch site visit and dress rehearsal.
* **March 28, 2026:** TSat-2B flew first. Live video and live telemetry worked for the whole flight of about 30 minutes. The satellite spun a lot, possibly because it was tied to the line at only two points instead of four. See [Results](https://wiki.kscucf.org/projects/tethered-satellite/t-sat-2/t-sat-2-project-b/results.md).
* **April 2026:** flight data reviewed (spikes in the pressure data were likely wind gusts and jolts from the line), video posted, and documentation written.

## What slipped and why

* **PCB fabrication and shipping** pushed assembly past winter break. That turned a one-semester plan into a two-semester one.
* After that, TSat-2B was ready about three weeks before launch and waited for the shared launch date with TSat-2A.

## Advice for future teams

* Order PCBs early enough that they arrive before the end of the semester.
* Don't unplug fragile cables, such as camera ribbon cables, more than you need to.
* Do range and battery tests in the field before launch day; they took several sessions.
* Attach the satellite to the line at four points to reduce spin.
