<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The first shoe to drop?</title>
	<atom:link href="http://tmfassociates.com/blog/2011/09/30/the-first-shoe-to-drop/feed/" rel="self" type="application/rss+xml" />
	<link>https://tmfassociates.com/blog/2011/09/30/the-first-shoe-to-drop/</link>
	<description>Satellites, spectrum and other stuff</description>
	<lastBuildDate>Tue, 03 Feb 2026 21:36:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TMF Associates MSS blog &#187; A watershed moment?</title>
		<link>https://tmfassociates.com/blog/2011/09/30/the-first-shoe-to-drop/comment-page-1/#comment-707</link>
		<dc:creator>TMF Associates MSS blog &#187; A watershed moment?</dc:creator>
		<pubDate>Thu, 10 Nov 2011 18:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://tmfassociates.com/blog/?p=2496#comment-707</guid>
		<description>[...] semi-annual progress report, filed with the FCC on October 31, the company confirmed that it is ignoring the FCC mandated timeline (from the January 2011 waiver) to make devices available by September 30, 2011 and now has [...]</description>
		<content:encoded><![CDATA[<p>[...] semi-annual progress report, filed with the FCC on October 31, the company confirmed that it is ignoring the FCC mandated timeline (from the January 2011 waiver) to make devices available by September 30, 2011 and now has [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ORBITRAX</title>
		<link>https://tmfassociates.com/blog/2011/09/30/the-first-shoe-to-drop/comment-page-1/#comment-680</link>
		<dc:creator>ORBITRAX</dc:creator>
		<pubDate>Fri, 30 Sep 2011 22:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://tmfassociates.com/blog/?p=2496#comment-680</guid>
		<description></description>
		<content:encoded><![CDATA[<p>I hope they don&#8217;t use the same excuses as Globalstar for failing to bring a dual mode High Speed MSS/ATC terminal as required by their authorization before or on July 1, 2011. </p>
<p>As the FCC noted&#8230;</p>
<p>¶Given the delay in second-generation deployment, Globalstar  contends it is &#8220;pointless&#8221; to meet the deadlines for distributing MSS/ATC terminals incorporating a high-speed, two-way MSS transceiver chipset, and for providing two-way MSS to customers with dual-mode MSS/ATC terminals.  Globalstar argues that requiring it to deploy such user terminals &#8220;far in advance of the [second generation] constellation (network)  availability.. would make no sense and would cause unnecessary expense for Globalstar when&#8230;. that equipment&#8217;s new, second-generation space capabilities (network) can not be used.  Consequently, Globalstar also asks for a 16-month extension of the dates by which its MSS/ATC terminals must come into compliance.</p>
<p>Our guess is&#8230;. A complete pass on the lack of mandated user terminals!!  After all.. They didn&#8217;t ask for one piece of paperwork to validate the launch delay of Skyterra 1.  </p>
<p>Boeing provided a letter stating that the Satellite was delayed due to an antenna problem.  That was the end of the investigation, even though we both know the storied funding path of Skyterra1 over the years.</p>
<p> Just as Thales provided a letter stating that the Thruster delay from RAFAEL was the main impetus for the delay in delivery of the Globalstar satellites for launch.</p>
<p>However the IB held court on Globalstar requesting hundreds of pages of justification for their launch delay </p>
<p>In it&#8217;s ruling, the IB stated:</p>
<p>¶33 &#8220;The record indicates&#8221; that the thrusters for the first batch of satellites were delivered to Thales more than [REDACTED] after the delivery date specified in the initial manufacturing contract.  However, the record NOWHERE INDICATES that late delivery of the thrusters impacted the deployment schedule of the second-generation satellites.&#8221;</p>
<p>The interesting point is that the [REDACTED] information in the Order was indeed, contrary to the FCC IB&#8217;s statements,  clearly available in &#8220;The Record&#8221; in Globalstara July 6, 2010 letter which Globalstar stated the first six thrusters were originally to be delivered by March 3, 2009.  Whereby Globalstar stated that actual delivery of the first Thrusters were not completed until June 1, 2010.  A delay of 15 MONTHS.  Globalstar provided complete documentation from RAFEL/Thales to support this fact.</p>
<p>But, Somehow the IB could not string together the concept that Thurster delivery delays from March 3, 2009 t June 1, 2010 could some how have delayed the first  satellite launch which took place 12 months late and shortly after the delivery of the first batch of Thrusters in June 2010.  After all the IB stated in the Order that&#8230;&#8221; The record NOWHERE INDICATES that late delivery of the thrusters impacted the deployment schedule of the second-generation satellites.&#8221;  Perhaps the IB didn&#8217;t understand that Satellites require Thruster installtion&#8230;. &#8220;BEFORE THEY ARE LAUNCHED&#8221;.</p>
<p>However, it is quite interesting that the IB intentionally REDACTED the publicly available thruster delay information from the Order that would have clearly contradicted their rational.   </p>
<p>ORBITRAX</p>
]]></content:encoded>
	</item>
</channel>
</rss>
