-
#160
by
Chris Bergin
on 28 Feb, 2020 15:28
-
-
#161
by
FutureSpaceTourist
on 28 Feb, 2020 15:57
-
https://twitter.com/chrisg_nsf/status/1233423786847981568 "We had a lot of surprises were the systmes actually performed better than expected."
"We also had areas where we have work to do." -- John Mulholland.
#Boeing #Starliner
https://twitter.com/chrisg_nsf/status/1233423863603658752 John reiterates that #AtlasV performed flawlessly. #Boeing #Starliner
https://twitter.com/chrisg_nsf/status/1233425042303848450 Lots of things did go right on the Orbital Flight Test, and John is overviewing those, including power systems, star tracker, avionics cool, and life support. #Boeing #Starliner
https://twitter.com/chrisg_nsf/status/1233425401235546127 Thrusters... all but one (that they had to turn off after the Mission Elapsed Timer issue <-- this was known) functioned perfectly and more robust then predicted. #Boeing #Starliner
https://twitter.com/chrisg_nsf/status/1233425727434960899 Landing loads were benign, below predict and three times lower than required #Boeing #Starliner
https://twitter.com/chrisg_nsf/status/1233427503039025154 Interim Review Team still working on comm issue with forward link. Saw that issue 37 times in mission, 36 in same geographic area. Other one was false lock. Still working on that. Outbrief on that "later in March." #Boeing #Starliner
https://twitter.com/chrisg_nsf/status/1233429524496429058 John talking at length about how software issues were missed. 2nd one missed b/c hardware needed for testing was in New Mexico for Service Module hot fire when lab software qual was performed. Corrective actions in place to ensure that doesn't happen again. #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233429945369726976 First software issue missed because that qual run was stopped at Starliner sep from Atlas. Going forward, they will run qual run sims from launch to docking and then undocking to landing. #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233430211716358145 John says Boeing not ready to talk about when Starliner will be ready to fly again. Full action items and full "go forward plan" won't be in place until Interim Review Team is done with all investigation and Boeing's internal audit. #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233430388938334208 Firmer timeline in "next couple weeks" of when they'll get to audit phase. Then fixes need to be implemented. #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233430983703252992 If Boeing is ready, ULA can support pending spacecraft readiness. #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233433788073619456 John confirms it was Boeing that asked for the Independent Review Team and for NASA to partner on that. #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233433996165632002 The decision on whether the next Starliner mission will be crewed or uncrewed will be NASA's, not Boeing. #Beoing #Starliner
-
#162
by
FutureSpaceTourist
on 28 Feb, 2020 16:07
-
https://twitter.com/timfernholz/status/1233436763277758464 Boeing VP John Mulholland keeps getting asked why and how the company made Starliner test decisions that allowed multiple mistakes to slip through, and won't answer the question.
twitter.com/chrisg_nsf/status/1233437055415472128
Why didn't Boeing verify all the software before flight? Why only now?
John: Team developed what they thought would be adequate. testing. Hindsight proved different. "This team didn't take shortcuts. Abundance of testing. But we have gaps to fill." 1/2 #Beoing #Starliner
https://twitter.com/chrisg_nsf/status/1233437056430374912 2/2 "Committed to briefing other programs inside and outside of Boeing. This approach to verification isn't unique to Boeing. Others used it to. As we've discussed with them the issues we've found, they're making their process more robust." -- John Mulholland.
Edit to add:
https://twitter.com/emrekelly/status/1233434820090515461 Boeing: Doing audit of all #Starliner code, as well as audit of emulators. Want to make sure they accurately reflect what the spacecraft will see.
-
#163
by
FutureSpaceTourist
on 28 Feb, 2020 16:12
-
Makes more sense:
https://twitter.com/sciguyspace/status/1233432799073460224 Mulholland confirms report that a Russian-made avionics box is on board Starliner. It's not part of the the landing system, as reported by TASS, but rather would have been used for power conversion when docked to ISS.
Edit to add:
https://twitter.com/emrekelly/status/1233431907355983877 Boeing: "We do have one Russian avionics box (on #Starliner). It's actually a legacy system that's already flying on the International Space Station," Mulholland says. Not on the landing system; does power conversion while docked to ISS.
-
#164
by
FutureSpaceTourist
on 28 Feb, 2020 16:44
-
Important confirmation:
https://twitter.com/marinakoren/status/1233440862656507904 Wow: At beginning of presser, Mulholland said this Orlando Sentinel report "mischaracterized" Boeing's testing. But later, when pressed, he confirmed what @ChabeliH reported. Boeing didn't run this end-to-end test, but it will do it now, Mulholland says
Also, and inevitably with a broken process, they are finding other flight software issues:
twitter.com/marinakoren/status/1233436334976569349
Mulholland tells me that after audit of the flight software is done, they'll be able to say exactly how many issues they had (so far, there's a few). Says the NASA astronauts assigned to the first crewed mission are "supportive," have visited Boeing since the botched mission
-
#165
by
ChrisGebhardt
on 28 Feb, 2020 19:18
-
-
#166
by
FutureSpaceTourist
on 28 Feb, 2020 21:34
-
-
#167
by
FutureSpaceTourist
on 01 Mar, 2020 18:36
-
https://twitter.com/nasa/status/1234195453903851520 This week, experts will provide details about the outcome of the joint independent review team investigation of @BoeingSpace’s uncrewed Orbital Flight Test of the #Starliner spacecraft.
Tune in:
📅 Friday, March 6
🕚 11am ET
🔗 go.nasa.gov/38801sM
https://www.nasa.gov/press-release/nasa-boeing-to-provide-outcome-of-starliner-orbital-flight-test-reviews NASA and Boeing will host a media teleconference at 11 a.m. EST Friday, March 6, to discuss the outcome of the joint independent review team investigation into the primary issues detected during the company’s uncrewed Orbital Flight Test in December as part of NASA’s Commercial Crew Program.
Participants in the briefing will be:
Douglas Loverro, associate administrator of NASA’s Human Exploration and Operations Mission Directorate
Jim Chilton, senior vice president at Boeing Space and Launch
Kathy Lueders, manager of NASA’s Commercial Crew Program
John Mulholland, vice president and manager of Boeing’s CST-100 Starliner Program
Audio of the teleconference will stream live online at:
https://www.nasa.gov/live
To participate in the teleconference, media must contact Joshua Finch at [email protected] by 10 a.m. Friday for the dial-in information.
-end-
-
#168
by
PM3
on 05 Mar, 2020 18:36
-
-
#169
by
abaddon
on 06 Mar, 2020 14:33
-
-
#170
by
abaddon
on 06 Mar, 2020 15:03
-
Conference has started. Starting with Independent Review Team findings.
-
#171
by
abaddon
on 06 Mar, 2020 15:05
-
Doug Loverro: Using today to close out what we've been doing over the last several months since the OFT test in December. Thanking Boeing team. Team came out with about 60(?) corrective actions that will be worked through over the next several months.
-
#172
by
Chris Bergin
on 06 Mar, 2020 15:06
-
-
#173
by
abaddon
on 06 Mar, 2020 15:07
-
Loverro: Organization safety issue review will kick off shortly. Have decided with all evidence and hindsight since OST is issuing "High Visibility Close Call" - NASA will review and capture lessons learned. Will look at Boeing and NASA's organizational practices. To start after letter signed later today. Will assign team outside of HEO.
-
#174
by
abaddon
on 06 Mar, 2020 15:10
-
Kathy Leuders: reiterating thanks. Have listened to recommendations and taking concrete corrective steps to improve for the next mission. On NASA side adding focused software lead and embedding more software experts in the Boeing software process. Working to beef up insight into Boeing's integration activities. Continue to welcome feedback and will incorporate additional suggestions from the review team.
-
#175
by
abaddon
on 06 Mar, 2020 15:11
-
John(? maybe not) (Boeing): Thanks to NASA & review team for joint review team. Commending Boeing team for being clear & candid about mission data and review results. Result of IRT tracking about 61 actions, lots of good advice, tracking all of that. Planning on keeping IRT looped in moving forward. Embracing whatever testing to get back to best possible spacecraft.
-
#176
by
abaddon
on 06 Mar, 2020 15:15
-
John Mulholland: Moving forward with all recommendations e.g. first step an audit from software requirements to testing that was done to validate it. Looking for gaps in testing looking at high and medium complexity. 49 gaps in testing identified (not errors). Can now perform testing and look for additional fixes to code. Understanding additional problems to move forward and ensure good code. Organizationally making changes to ensure robust system and institutionalize learnings so it will remain in the team moving forward.
-
#177
by
abaddon
on 06 Mar, 2020 15:16
-
John Mulholland: Spacecraft refurbishment continuing in factory. Confident in RTF safely when IRT issues resolved.
Q&A to begin.
-
#178
by
abaddon
on 06 Mar, 2020 15:19
-
Steve Cowen (NASAWatch): 60+ problems in program given time and expense surprising. How can NASA and Boeing restore confidence? (Heavy paraphrase).
IRT 61 "recommendations" not "design issues or changes", all very actionable. Distributing learning as broadly as possible.
-
#179
by
abaddon
on 06 Mar, 2020 15:19
-
Sounds like the connection was hung up (busy signal) and now... dead air?