<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>space capsule &#8211; EFR Technology Group</title>
	<atom:link href="https://www.efrtechgroup.com/category/space-capsule/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.efrtechgroup.com</link>
	<description>We maintain technology so you don't have to!</description>
	<lastBuildDate>Fri, 07 Feb 2020 19:03:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://www.efrtechgroup.com/wp-content/uploads/2019/02/cropped-EFRTG-color-2-32x32.jpg</url>
	<title>space capsule &#8211; EFR Technology Group</title>
	<link>https://www.efrtechgroup.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>NASA wants to review Boeing’s Starliner work after setbacks</title>
		<link>https://www.efrtechgroup.com/tech/nasa-wants-to-review-boeings-starliner-work-after-setbacks/</link>
		
		<dc:creator><![CDATA[Randall]]></dc:creator>
		<pubDate>Fri, 07 Feb 2020 19:03:00 +0000</pubDate>
				<category><![CDATA[boeing]]></category>
		<category><![CDATA[boeing starliner]]></category>
		<category><![CDATA[cst-100]]></category>
		<category><![CDATA[iss]]></category>
		<category><![CDATA[Nasa]]></category>
		<category><![CDATA[Space]]></category>
		<category><![CDATA[space capsule]]></category>
		<category><![CDATA[spacecraft]]></category>
		<category><![CDATA[spaceflight]]></category>
		<category><![CDATA[starliner]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[tomorrow]]></category>
		<guid isPermaLink="false">https://www.efrtechgroup.com/nasa-wants-to-review-boeings-starliner-work-after-setbacks/</guid>

					<description><![CDATA[[ad_1] NASA and Boeing are still investigating the first software error &#8212; which caused the craft to fire some of its thrusters too late and burn too much fuel &#8212; and are now trying to better understand the second glitch. These multiple issues warrant a deeper review, according to Hill. &#8220;The panel has a larger [&#8230;]]]></description>
										<content:encoded><![CDATA[<p> [ad_1]<br />
</p>
<div>
<p>NASA and Boeing are still investigating the first software error &#8212; which caused the craft to fire some of its thrusters too late and burn too much fuel &#8212; and are now trying to better understand the second glitch. These multiple issues warrant a deeper review, according to Hill. &#8220;The panel has a larger concern with the rigor of Boeing&#8217;s verification processes. Further, with confidence at risk for a spacecraft that is intended to carry humans in space, the panel recommends an even broader Boeing assessment of, and corrective actions in, Boeing&#8217;s [systems engineering and integration] processes and verification testing.&#8221; Boeing says that it has accepted the suggestion and will coordinate with NASA, as well as take a $410 million charge against its earnings to help pay for a second unmanned test flight. The two organizations will decide on whether or not to actually conduct this second test by the end of February.</p>
<p>NASA was planning to use Boeing&#8217;s Starliner in a manned mission in December 2020, but it&#8217;s likely that the timeline has shifted in light of the pending review. It also wouldn&#8217;t be surprising if the ongoing concerns with the company&#8217;s 737 MAX impacted NASA&#8217;s decision to look deeper into the contractor&#8217;s practices. How these issues will affect Boeing as a company remain to be seen.</p>
</p></div>
<p>[ad_2]<br />
<br /><a href="https://www.engadget.com/2020/02/07/nasa-review-boeing-starliner-software/">Source link </a></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
