[FPSPACE] correction/update

David Portree dsfportree at hotmail.com
Thu Jul 6 00:53:06 EDT 2017


For the sake of argument (and because I am a curmudgeon), I'm going to call this a partial success because of the delays. As long as the business model demands 40 or so launches a year, delays are set-backs.

Did they ever explain what went wrong the first two times and what they did to solve the problem? Was it a software fix (reset the values so the problem goes away) or something else?


David S. F. Portree


dsfportree at hotmail.com<mailto:dsfportree at hotmail.com>



From: FPSPACE <fpspace-bounces at mail.friends-partners.org> on behalf of Peter Pesavento <pjp961 at svol.net>
Sent: Wednesday, July 5, 2017 6:10 PM
To: FPSPACE at mail.friends-partners.org
Subject: [FPSPACE] correction/update

It is Intelsat 35e, not 45e.  And the second stage burn was good, and the spacecraft is set for deployment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.friends-partners.org/pipermail/fpspace/attachments/20170706/91b3f846/attachment.html>

More information about the FPSPACE mailing list