On 1/25/21 3:43 PM, Roy Dean wrote:
I respectfully ask that AMSAT-NA Engineering and/or Operations publish a copy of the IOC (In Orbit Checklist), with any sensitive information redacted. I will also ask that the reasons for the redaction be provided. For example: "This sentence redacted as it relates to proprietary launch provider information." Or "This paragraph redacted as it relates to trade secret uplink transmission protocols."
I feel this information can greatly enhance the collective knowledge of AMSAT-NA by getting more eyes on the procedure, perhaps even leading to some hindsight that could lead to future design changes/improvements, etc.
Hello Roy,
I doubt this will happen, and here's why: Monday-morning quarterbacking isn't productive.
You'll have a small window on the project without any background information, and you'll load down volunteers with questions and speculation while they're trying to use their considerable knowledge of the project to recover the bird. Accusations will fly, and unrealistic or nigh-impossible solutions will be fielded. I can think of at least one 2020 board candidate who has already started down this war path.
You know the downlink frequency. The best thing you can do is listen for any peep out of it, and forward that data on, as requested, to AMSAT.
If you think you have something to contribute to the future missions, such as GOLF, please _volunteer_ and put in the time learning the system. You'll likely not be granted any special access to prior missions, but those volunteers who span missions will carry forward what worked and what didn't.
Making mistakes is how we learn, and failures happen even with the largest of budgets. As a reminder, here's a collection of SpaceX learning experiences, and they have a budget many orders of magnitude greater than AMSAT's.
https://www.youtube.com/watch?v=bvim4rsNHkQ
You've got to have a sense of humor to be an engineer.
(I am not speaking in any official capacity for AMSAT, nor am I empowered to do so on any occasion.)
--- Zach N0ZGO