Two Major Satellite Breakups Near End of 2001 Two Major Satellite Breakups, the Worst in for Each

Two Major Satellite Breakups Near End of 2001 Two Major Satellite Breakups, the Worst in for Each

A publication of The Orbital Debris Program Office NASA Johnson Space Center Houston, Texas 77058 January 2002 Volume 7, Issue 1. NEWS Two Major Satellite Breakups Near End of 2001 Two major satellite breakups, the worst in for each. Throughout Thanksgiving and the remained in orbit for a few more revolutions 20 months, occurred just four weeks apart in the following weekend, NASA and Naval Space before falling back to Earth. fourth quarter of 2001, both producing in excess Command personnel worked to gain a better On 19 December the eighth breakup of the of 300 large fragments. Two other lesser insight into the extent of the newly created de- year resulted in a severe fragmentation of an breakup events brought the total number of sat- bris cloud. Indian PSLV fourth stage (2001-049D, US Sat. ellite fragmentations to nine for the year, a rate The STS-108 mission, then planned for No. 26960), which had been in orbit for only not matched since 1998. launch on 29 November, raised new safety is- two months. Within two days of the event ap- On 21 November a Russian satellite, Cos- sues. The Space Shuttle is not as well protected proximately 200 debris with orbits stretching mos 2367 (International Designator 1999-072A, from small debris impacts as ISS. Specific con- from 200 to 1100 km had been identified. By US Sat. No. 26040), experienced a significant cerns were STS-108 overall mission risks, EVA 27 December the number of tracked debris sur- fragmentation while in an orbit just 30 km risks, risks associated with boosting ISS during passed 300. The event marked the first breakup above the International Space Station (ISS), i.e., the mission, and risks associated with special of an Indian satellite. 411 km mean altitude for Cosmos 2367 and 382 Space Shuttle attitudes planned during inde- This was the sixth flight of the PSLV km for ISS. Approximately 200 debris were pendent flight. Fortunately, these new risks (Polar Satellite Launch Vehicle) which had suc- detected by normal US Space Surveillance Net- were assessed to be within NASA guidelines. cessfully inserted the main payload, the Indian work (SSN) operations, while special sensor Cosmos 2367 was the latest in the Cosmos TES (Technology Experiment Satellite) space- observations several days after the event indi- 699 series of 3-metric-ton spacecraft which be- craft, into a sun-synchronous orbit along with a cated that another 100 or more smaller debris gan in 1974. To date 20 of these spacecraft small German satellite called BIRD. A second were also in orbit. These debris were concen- have undergone one or more fragmentation epi- piggyback satellite from Belgium, PROBA, was trated in the orbital regime of 200-500 km, but sodes with the number of debris generated usu- placed into a slightly elliptical orbit after the some were thrown into orbits with apogees ally on the order of 100 or more. Most of the deployment of TES and BIRD. The 900 kg above 1000 km. events have occurred at relatively low altitudes, stage was in an orbit of 550 km by 675 km with Approximately 40% of the debris were resulting in relatively rapid decay of the debris. an inclination of 97.9 deg at the time of the immediately thrown into orbits which crossed In the case of Cosmos 2367 some of the debris event. the orbit of ISS. Immediately upon notification should remain in orbit for many months. The cause of the PSLV breakup is under of the breakup, the Orbital Debris Program Of- About three weeks after the Cosmos 2367 investigation. A potential energy source for the fice undertook an effort to characterize the breakup, the 12-year-old Molniya 3-35 space- fragmentation may be residual hypergolic pro- probable debris cloud and to assess the risks craft (International Designator 1989-043A, US pellants. The release of all residual propellants posed by it not only to the ISS but also to the Sat. No. 20052) fragmented during catastrophic and compressed fluids at the end of launch ve- imminent STS-108 mission. Naval Space Com- orbital decay on 14 December while passing hicle stage and spacecraft operations is highly mand, headquartered in Dahlgren, Virginia, over the Southern Hemisphere. About two recommended by US Government agencies as spearheaded the effort to identify the individual dozen pieces were detected with most reenter- well as many space-faring nations around the debris and to develop initial orbital parameters ing immediately. Some debris appear to have (Continued on page 2) Inside... The 2001 Leonid Observations at JSC ......................................................................................2 New Report on Hubble Space Telescope Impact Damage .................................................... 4 Orbital Evolution of Cloud Particles from an Explosion in Near-GEO ................................6 Doppler Inclination Estimates from Haystack Measurements of the Debris Environment 9 1 The Orbital Debris Quarterly News NEWS Two Major Satellite Breakups Near End of 2001, Cont’d (Continued from page 1) to have occurred late on 24 December when a on 29 October 1991. The orbit of the stage at world. To date no satellite which has been suc- 10-year-old Ariane 4 orbital stage generated the time of the event was 230 km by 28,505 km cessfully passivated in this manner is known to several pieces of debris. The stage (1991-075B, with an inclination of 7.2 deg. The extent of the have suffered a breakup. US Sat. No. 21766) had placed the Intelsat 601 fragmentation was still being evaluated at the Y The final fragmentation of the year appears spacecraft into a geosynchronous transfer orbit close of 2001. Anomalous Events in 2001 Anomalous events are defined as the un- event occurred early in the year, perhaps in Seasat (1978-064A, US Sat. No. 10967), planned separation, usually at low velocity, of April, when an object separated from the Ariane which also has been linked to several anoma- one or more detectable objects from a satellite 40 launch vehicle (1991-050F, US Sat. No. lous events since 1983, was the third source of which remains essentially intact. The principal 21610) which had launched the ERS-1 space- new debris identified by analysts of 1CACS. causes of anomalous events are assessed to be craft. The object, eventually cataloged as US The new fragment (US Sat. No. 26963) ap- impacts by very small natural or artificial parti- Sat. No. 26925, experienced considerably peared in early July with a very high rate of cles or to be the result of environmental stresses higher orbital decay than its parent, which was decay, falling from an altitude of more than 750 leading to satellite surface degradations. in a nearly circular orbit with a mean altitude of km to reentry in only five months. Many of the Anomalous events are historically more diffi- about 770 km. Reentry is expected to occur in previous Seasat anomalous event debris also cult to identify than the more intense and pro- 2002. exhibited high area-to-mass ratios which re- lific satellite breakups. The latest edition of The second anomalous event involved the sulted in rapid orbital decay. “History of On-Orbit Satellite Fragmenta- 35-year-old Nimbus 2 spacecraft (1966-040A, The orbital lifetimes of two of these three tions” (JSC-29517, July 2001) lists 35 satellites US Sat. No. 02173), which has been the subject debris were sufficiently short, thereby posing no which have suffered one or more anomalous of multiple anomalous events since 1997. The long-term collision risk to other resident space events. newly detected event is assessed to have oc- objects. This is typical of a large number of The 1st Command and Control Squadron curred about the start of May 2001. A single anomalous debris and is a clue to their charac- (1CACS) of Air Force Space Command has object was released and later cataloged as US ter. The Orbital Debris Program Office will be found evidence for anomalous events with at Sat. No. 26962. This object also is decaying releasing the results of a new study on anoma- least three satellites during 2001. Each event more rapidly than Nimbus 2 from its original lous events and their potential importance next produced a single new piece of debris. The first 1093 km by 1177 km orbit. year. Y The 2001 Leonid Observations at JSC J. Pawlowski mock in my back yard starting about 3:30. I did Clear Lake, Texas, considers this the greatest The JSC Leonid Observers were out and have to deal with the runway lights which meteor shower he’s ever seen. “In a one-hour about in the wee hours of Sunday morning, No- ended up being brighter than I would have period I observed eight meteors. From Hous- vember 18, 2001. imagined. I saw a meteor about once every 10 ton, that’s the best I’ve ever seen. It was almost Mark Mulrooney and Anna Scott observed seconds for the first hour or so. After that, sleep worth getting up at that ungodly hour to see it!” at the JSC Observatory near Cloudcroft, New and fog took their toll and the rate dropped con- Kandy Jarvis reported, “The view of the Mexico. Observing about 1/6th of the sky, Anna siderably by 5:00 a.m.” Leonids from Las Vegas (~45 min drive North counted a peak of 700 between 1000 and 1100 Jim Pawlowski was not as fortunate. He of downtown) wasn't bad, though a brisk wind UT. Mark wrote, “Having viewed showers for was visiting his daughter, Amber, in La Jolla made it a bit teeth chattering. Humidity was 25 years, I’ve never seen anything like it”.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    14 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us