Releasing two balloons over Sector KD-T for Tiberdyne Aerospace this mission will take advantage of the orbiting Kerbin II to stay in communication & thus require less support to be taken along
![]() |
![]() |
Oct 16 2020
Releasing two balloons over Sector KD-T for Tiberdyne Aerospace this mission will take advantage of the orbiting Kerbin II to stay in communication & thus require less support to be taken along
![]() |
![]() |
Oct 06 2020
Oct 05 2020
Sep 29 2020
Hot on the heels of the first launch, the second mission was set to rectify several issues that ended up leading to a mission failure. Although the modifications needed for the rocket were made in time for an on-schedule launch the weather had other plans and forced a one day delay. Once the skies cleared up however all proceedings up to the terminal count were carried out with no additional issues.
With the service boom swung away and the rocket on internal power and radio-frequency comms, final preparations for launch were carried out mainly by the AFCS, now in control of the rocket. 5s before booster ignition the support arms holding the rocket steady against any sudden wind gusts were retracted to clear the way for ascent and at T-0 the 0.625m dual-segment SRB lit off to push the rocket off the engine support at 13:30:00.04 local time to begin its ascent.
With an initial TWR of 3 the rocket quickly gained enough speed in the first seconds for the guidance fins to have the authority to begin pitching the rocket downrange, heading the direction it was already facing – direct east. However instead the rocket went into a slight roll and actually ended up briefly pointing back west before correcting with another roll back towards 90° however upon reaching that head spun around again and continued to have trouble pointing itself in the proper direction to the consternation of controllers.
Sep 24 2020
Sep 13 2020
Hello everyone, this is going to be an entirely out-of-character annual update because I want to be candid about how this project could be affected by in-real-life events moving forward given my current circumstances.
The KSA is becoming a “mature” agency now and that helps because it doesn’t tweet or generate content nearly as much on a daily basis as it used to back in the earlier years, however at the same time the complexity of the operations has also increased. The pandemic these past few months and me being unable to do my “real job” coaching gymnastics and thus spending nearly all my time at home has also brought about a startling realization: this whole project is taking up a lot more time nowadays than it used to. In earlier years I would have at least 2-3 weeks of lead time, sometimes as much as 2-3 months and now I’m struggling to keep ahead by just a few days.
There is another consideration however – the whole pandemic situation has also brought me closer to friends online since regular in-person gatherings aren’t really a thing anymore lately. Ironically this has eaten up time as well because it’s easier to get together online to play games than it is to coordinate IRL meetups. So before Covid I was spending less time hanging with friends but getting more from the in-person interaction so I felt less compelled to connect to them online often, freeing up more time for me to work on KSA.
Now, if I free up more time from gaming with my friends online that will help me stay ahead when lead time grows short but another upcoming problem will be when financial assistance for unemployment related to Covid dries up over the next few months. If I return to the gym to coach or search out some other employment opportunity because I need the money to sustain myself then that is once again less time I have to spend on this project.
If time becomes an issue, as I have said before I will be forced to scale back the timeline and scope of this project in order to allow it to continue. Updates will become fewer, background story elements will fade away, crew will develop less character and time between launches will be extended so that I have more time to prepare.
A final consideration for how much time I have to work on KSA activities is contributions from Patreon. Obviously if I can make enough money through here that I don’t have to spend as much time coaching or traveling away to fireworks shows then that is more time I can spend on this project instead. Currently I’m making just enough to cover the monthly $10 payment I make to prolific KSP mod author LinuxGuruGamer, who in keeping various mods alive also helps keep the KSA project moving forward with new KSP versions.
While I of course hope my personal situation and the pandemic situation stabilizes in the near future, I also doubt it’s going to happen – especially considering this upcoming U.S. election. I remain committed however to not voluntarily giving up the project. I take a lot of enjoyment seeing people react to what the KSA is doing and I thank everyone who has reached out to me over the years with comments and suggestions or even attempted to take part in the role play. It does mean a lot.
I’m really looking forward to making it back to orbit over this coming year and continuing on this journey with you all. Thanks for following along and please don’t forget to help spread the word about the KSA’s existence!
Drew Kerman,
Founder, Operations Director
Sep 09 2020
Specialist Bob has had quite the long journey to get up into space. He was supposed to be the first to take the trip however the Monolith had other plans for our initial orbital attempt, which can be read about in more detail here. Nearly one year later his rotation finally came back around after first Bill then Val then Jeb all took turns flying up above the atmosphere. Always the one on the crew list with the most nerves, having 3 other kerbals return safely from space helped to put him at ease, although at the same time he couldn’t help but wonder if that meant he would be the one to not come back alive. Despite his anxiety, Bob got straight on board the rocket on launch day and retained his composure throughout the mission, despite the problems that were had.
With no issues in the countdown, the ignition sequence began at T-6s to fire up the main engine and check chamber pressures as it throttled to launch thrust of 1.2 TWR. Clamp release was approved as the AFCS confirmed launch thrust and the rocket began its ascent, holding throttle steady until it had climbed over the towers. The rocket began to roll from 45° to launch heading of 54° but at L+6s the guidance computer decided that it was also supposed to be holding a 45° pitch angle and kicked the rocket hard over while still less than 500 meters over the ground. Needless to say this caused quite the commotion in launch control!