<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	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>Singapore Technologies Aerospace | George Hatcher's Air Flight Disaster</title>
	<atom:link href="https://airflightdisaster.com/tag/singapore-technologies-aerospace/feed/" rel="self" type="application/rss+xml" />
	<link>https://airflightdisaster.com</link>
	<description>Aviation News, Headlines &#38; Alerts</description>
	<lastBuildDate>Sat, 22 Jan 2011 00:01:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>ST Aerospace Responds to FAA&#8217;s Press Release on Proposed Civil Penalty Charge</title>
		<link>https://airflightdisaster.com/st-aerospace-responds-to-faas-press-release-on-proposed-civil-penalty-charge/</link>
		
		<dc:creator><![CDATA[GJHatcher]]></dc:creator>
		<pubDate>Sat, 22 Jan 2011 00:01:28 +0000</pubDate>
				<category><![CDATA[press release]]></category>
		<category><![CDATA[Singapore Technologies Aerospace]]></category>
		<guid isPermaLink="false">http://airflightdisaster.com/?p=14110</guid>

					<description><![CDATA[<p>SINGAPORE, Jan. 21, 2011 -USNewswire/ &#8212; We are disappointed with the Federal Aviation Administration (FAA)&#8217;s press release regarding a civil penalty proposal of US$1.025m against ST Aerospace&#8217;s U.S. facility ST Aerospace San Antonio, L.P. ST Aerospace takes our safety obligations seriously and has in fact addressed the issues raised by the FAA way back in...</p>
<p>The post <a href="https://airflightdisaster.com/st-aerospace-responds-to-faas-press-release-on-proposed-civil-penalty-charge/" data-wpel-link="internal" target="_self">ST Aerospace Responds to FAA’s Press Release on Proposed Civil Penalty Charge</a> first appeared on <a href="https://airflightdisaster.com" data-wpel-link="internal" target="_self">George Hatcher's Air Flight Disaster</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>SINGAPORE, Jan. 21, 2011  -USNewswire/ &#8212; We are disappointed with the Federal Aviation Administration (FAA)&#8217;s press release regarding a civil penalty proposal of US$1.025m against ST Aerospace&#8217;s U.S. facility ST Aerospace San Antonio, L.P. ST Aerospace takes our safety obligations seriously and has in fact addressed the issues raised by the FAA way back in 2008.</p>
<p>Although we are concerned about the FAA&#8217;s notice, we are also comfortable with the fact that we co-operated with the FAA years ago to resolve their concerns and to implement quality controls to ensure that we continue to comply with the FAA&#8217;s drug-testing standards.</p>
<p>We believe that the most important facts in this matter are:</p>
<ul>
<li>Every one of the employees referred to in the FAA&#8217;s press release has passed their drug tests.
<li>We have effective controls in place to ensure continued compliance with the drug testing standards found in the FAA&#8217;s regulations.
<li>There are no allegations of current compliance issues.
</ul>
<p>We intend to communicate with the FAA to explain why their informal allegations are incorrect. Nonetheless, we are treating this matter very seriously, and we will work closely with the FAA to resolve it.</p><p>The post <a href="https://airflightdisaster.com/st-aerospace-responds-to-faas-press-release-on-proposed-civil-penalty-charge/" data-wpel-link="internal" target="_self">ST Aerospace Responds to FAA’s Press Release on Proposed Civil Penalty Charge</a> first appeared on <a href="https://airflightdisaster.com" data-wpel-link="internal" target="_self">George Hatcher's Air Flight Disaster</a>.</p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
