> 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-mission-a/flight-results.md).

# Flight Results

Launch configuration, flight, and recovery results from the March 28, 2026 flight of TSat-2A.

<figure><img src="https://1394776253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPuVVtRVX2TItLnaqjW8A%2Fuploads%2F4QeryXjDkQT2eeY0vyRs%2FTSAT-A.JPG?alt=media&amp;token=8eff68a7-398b-4b04-9098-f96e8b6a4016" alt="" width="563"><figcaption></figcaption></figure>

#### Launch Configuration

Final assembly integrated the mechanical housing, PCBs, batteries, cameras, sensors, radio, servo mechanism, parachute, and external launch equipment. A servo panel was replaced shortly before launch, and additional printed material was present near the separation system.

These late modifications reduced the time available for complete end-to-end testing and final configuration inspection.

#### Important Final Assembly Issues

The final configuration required additional verification of the replacement servo panel, battery output, electrical connections, and parachute exit path. Printed material near the servo and parachute path may have interfered with parachute deployment, although this was not conclusively confirmed.

Future teams should freeze the final configuration early enough to test all replacement parts and modifications as part of the complete system. The parachute should be installed during final deployment testing, and the entire exit path should be inspected for potential interference. External launch equipment, including the rope-reeling system, should also be tested before flight.

### Launch Operations

#### Ascent

The launch system experienced an issue with the rope-reeling equipment, requiring manual intervention during operations. The payload reached an altitude of approximately 450 ft before the separation sequence was completed.

The launch demonstrated the importance of testing external support equipment and preparing contingency procedures before flight.

<figure><img src="https://1394776253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPuVVtRVX2TItLnaqjW8A%2Fuploads%2FgAcTH1GJgtqYpXrGnbPS%2Fcam2_pic103.jpg?alt=media&amp;token=6be7b87c-7978-422d-a518-9c7649b41bbe" alt="" width="375"><figcaption><p>Image Captured by TSat-2A</p></figcaption></figure>

#### Separation

The separation command was successfully received, but the servo did not initially cut the fishing wire. After intervention, the CubeSat eventually separated from the balloon assembly.

The separation system therefore demonstrated partial success: communication and command processing operated as intended, but the initial mechanical deployment did not occur as planned.

<figure><img src="https://1394776253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPuVVtRVX2TItLnaqjW8A%2Fuploads%2FpNoOWEMHWdKsdPPeUxvU%2FTethered%20Satellite%202A%20Altitude%20Graph.png?alt=media&amp;token=4cebc920-fcba-48a2-84ba-dbefe59fba6a" alt="" width="563"><figcaption><p>Post-Processed TSat-2A Altitude Data</p></figcaption></figure>

### Recovery and Mission Results

#### Parachute Deployment

The parachute did not deploy correctly and remained partially inside the housing. The suspected interference from printed material highlights the need to inspect the complete parachute exit path, including the parachute itself, after all components have been installed in their final flight configuration.

The deployment system should be tested using the final hardware, parachute packing method, component alignment, and mounting configuration.

#### Recovery

The recovered housing sustained significant damage during the flight and landing sequence. However, both cameras remained undamaged, the two PCBs appeared intact, and the SD card was recovered with image and altitude data. Some components had become disconnected, while the Project A.L.E.X. panel remained undamaged.

The recovered hardware and data provided useful information for evaluating the performance of the mechanical structure, avionics, imaging system, and data storage system.

<figure><img src="https://1394776253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPuVVtRVX2TItLnaqjW8A%2Fuploads%2FJhrPAeBHSaReYrENnaor%2FIMG_4055.jpg?alt=media&amp;token=8c72260a-8f50-42ad-a53b-27236e1c2518" alt="" width="375"><figcaption><p>Images After the TSat-2A Crash</p></figcaption></figure>

<figure><img src="https://1394776253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPuVVtRVX2TItLnaqjW8A%2Fuploads%2FNqZ3q8bztglBTe0AaMaF%2FIMG_4981.JPG?alt=media&amp;token=66f2b2ac-319c-4b2e-8034-ba3fa92ffa72" alt="" width="375"><figcaption></figcaption></figure>

#### Lessons Learned

TSat-2A demonstrated the importance of complete system-level testing and final configuration control. Future teams should prioritize the following:

* Perform end-to-end separation and parachute deployment testing using final flight hardware.
* Inspect the entire parachute exit path with the parachute installed.
* Verify all replacement parts, printed features, and mechanical clearances before launch.
* Freeze the final design early enough to allow sufficient testing.
* Test external launch equipment and prepare contingency procedures.
* Use physical or sensor-based verification for critical actions instead of relying only on software acknowledgements.
* Secure and inspect electrical connections following final assembly and vibration or handling tests.

#### Conclusion

TSat-2A established a foundation for future TSat development by demonstrating the integration of a modular 2U housing, onboard avionics, imaging, altitude sensing, data storage, wireless communication, and a remotely controlled separation system. Although the parachute deployment and initial separation attempt were unsuccessful, the recovery of mission data and several functional components provided valuable engineering feedback.

Future missions can build on this work by improving final configuration control, performing more complete deployment testing, strengthening mechanical interfaces, and adding verification methods for critical flight actions. The lessons from TSat-2A should be used to improve reliability while maintaining the modular and repeatable design approach established during development.

<figure><img src="https://1394776253-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPuVVtRVX2TItLnaqjW8A%2Fuploads%2Fg7gHLfI0SELbzwVpNi9d%2FIMG_4959.JPG?alt=media&amp;token=6f1c7ff6-e089-4ef2-8f8a-3c6ffce5ba61" alt="" width="188"><figcaption><p>TSat-2A During Flight</p></figcaption></figure>
