Astro-Coord-ECI-TLE-Iridium
view release on metacpan or search on metacpan
xt/author/iridium_status.t view on Meta::CPAN
remained in the 605km * 625km insertion orbit.</p>
<p>The first Iridium Next launch (2017-003) took place on 14
January 2017, lifting the first ten Iridium Next satellites to
Orbital Plane 6.<br>
Initially all 10 Iridium Next satellites were in a 605km * 625km
insertion orbit.<br>
On 22 January 2017, Iridium 106 (2017-003A) was the first to have
its orbit raised by about 10km, presumably following a successful
initial check-out.<br>
On 24 January 2017, Iridium 103 (2017-003B) had its orbit raised
by about 10km.<br>
On 25 January 2017, Iridium 106 (2017-003A) was raised
significantly to a 700km * 705km storage orbit.<br>
By 28 January 2017, Iridium 103 (2017-003B) and Iridium 109
(2017-003C) had also been raised to the 700km * 705km storage
orbit., and Iridium 102 (2017-003D) was in the process of being
raised.<br>
Over the next few days, Iridium 102 (2017-003D), Iridium 104
(2017-003F), and Iridium 114 (2017-003G) were also raised to the
700km * 705km storage orbit.</p>
<p>It initially seemed unlikely that any of the Iridium Next
satellites launched to Oribital Plane 6 would be moved to other
orbital planes, as any gaps in those planes caould be filled more
quickly by the launches direct to those planes that are expected
to take place in the coming months.</p>
<p><strong>The status of the Iridium constellation </strong><strong><u>immediately
prior to the first Iridium Next launch</u></strong><strong>
appears to have been as follows:</strong></p>
<p>(At this time, it was reported that 64 of the original Iridium
satellites still remained operational)</p>
<pre>Orbital <-------------- Operational satellites --------------> Spares
Plane
Plane 1: <a href="iridium74and21.htm">21</a> 72 75 70 62 14 64 65 66 67 68 <a
href="iridium74and21.htm">74</a> (note: Iridium 74 is probably a partial failure)
Plane 2: 22 <a href="iridium94.htm">94</a> 76 25 23 46 47 20 49 <a
href="iridium11and26.htm">11</a> 3 (note: Iridium 23 is probably a partial failure)
Plane 3: 55 <a href="iridium28and95.htm">95</a> 45 <a
href="iridium30and31.htm">31</a> <a href="iridium30and31.htm">30</a> 32 <a
href="iridium33collision.htm">91</a> <em> </em> 58 59 60
Plane 4: 19 34 35 <a href="iridium36and97.htm">97</a> <a
href="iridium5and51.htm">5</a> 6/51 <a
href="iridium7and51.htm">7</a> 8 96 37 61 (note: Iridiums 6, 7 and 51 are probably partial failures)
Plane 5: 50 56 52 53 <a href="iridium9and84.htm">84</a> 10 54 12 13 83 <a
href="iridium16and86.htm">86</a> <a href="iridium91.htm">90 (launched to plane 3, but has been migrated to plane 5)</a>
Plane 6: 18 98 40 15 80 <a href="iridium17and77.htm">77</a> 81 <a
href="iridium38and82.htm">82</a> 41 43 <strong>
</strong></pre>
<pre>Original <----- Failed -----> <- Failed -> <em>Note that some of the failed</em> <em>satellites have drifted from the original orbital planes</em>
Orbital (but still in orbit) (decayed)
Plane <em> </em>
Plane 1: 73t 63
Plane 2: 69t 24t 71t <a href="iridium11and26.htm">26</a> 48d
Plane 3: <a href="iridium28and95.htm">28</a> 29<font
color="#FF0000"> </font><a href="iridium33collision.htm"><font
color="#FF0000">33</font></a>t 57 27d <em>Iridium 33 was fragmented by the collison with Cosmos 2251 on February 10, 2009</em>
Plane 4: 4 <a href="iridium36and97.htm">36</a>t
Plane 5: 2t 914t 911t <a href="iridium16and86.htm">16</a>t 85d <a
href="iridium9and84.htm">9</a>d <em>Iridium 2 has drifted far from</em> <em>its original launch plane, and continues to drift</em>
Plane 6: 920t 921t 44t <a href="iridium38and82.htm">38</a>t <a
href="iridium17and77.htm">17</a>t 42t 39 79d </pre>
<p>t indicates satellites that have been reported as tumbling out
of control. </p>
<p>In their quarterly report dated 30 June, 2016, Iridium
Satellite LLC acknowledged the failure of two satellites in the
preceding quarter year.</p>
<p>In June 2016, Iridium 15 (24869, 1997-034A) was moved from
Plane 6, Slot 7 to Plane 6, Slot 4, replacing Iridium 39 (25042,
1997-069D). The intention may have been to swap over the two
satellites but, in any case problems were experienced with with
Iridium 39, which was then removed from the operational
constellation, leaving a gap at Plane 6, Slot 7. No spare was
available to replace it.</p>
<p>In May 2016, Iridium 57 (25273, 1998-019B) began to drift away
slowly from its nominal position (Plane 3, Slot 8) and has
presumably failed. See<a
href="http://www.satobs.org/seesat/May-2016/0069.html"> Iridium
57 looks to have a bad attitude</a>.</p>
<p>In the middle of 2015, Iridium 45 (25104, 1997-082A) which had
been migrating from orbital plane 2 towards orbital plane 3 for
about 14 months, arrived in oribital plane 3. It appears to have
already been in operational use as part of orbital plane 3 for
some months previously, even though it was not in its final
orbital location (Plane 3, Slot 3).</p>
<p>In early December 2014, Space-Track catalogued four items of
debris (40324-40327, 2002-05G to 2002-05K) associated wth the
2002-05 launch .These are labelled by Space-Track as
"IRIDIUM 91 DEB", and seem to be associated with
Iridium 91 (27372, 2002-005A) which appears, however, to remain
fully operational.</p>
<p>In early October 2014, <a href="iridium7and51.htm">Iridium 51
(25262, 1998-018A)</a>, which had been paired wth <a
href="iridium7and51.htm">Iridium 7 (24793, 1997-020B)</a> was
moved within orbital plane 4 to be paired with Iridium 6 (24794.
1997-020C).</p>
<p>At the end of August 2014, Iridium 14 (25777, 1999-032A) ,
whch had been spare in orbital plane 1 since launch, was raised
to operational altitude to replace Iridium 63 (25286. 1998-021B),
which had presumably failed.</p>
<p>At the end of August 2014, Iridium 98 (27451, 2002-301B) ,
whch had been spare in orbital plane 6 since migrating from plane
4, was raised to operational altitude a few seconds behind
Iridium 42 (25077. 1977-077) which had presumably failed. Iridium
42 has since been reported to be flashing.</p>
<p>By early 2014, Iridium 45 (25104, 1997-082A) was no longer
maintaining its place in orbital plane 2, and was evidently
( run in 1.418 second using v1.01-cache-2.11-cpan-b16cb0d3907 )