13.07.2015 Views

a methodology to repair or deorbit leo satellite constellations - AGI

a methodology to repair or deorbit leo satellite constellations - AGI

a methodology to repair or deorbit leo satellite constellations - AGI

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

vii3.20 Timeline f<strong>or</strong> Fourth Rendezvous ....................................................................... 693.21 Classical Orbital Elements of 5 th Firth Rendezvous ........................................... 703.22 Timeline f<strong>or</strong> Fifth Rendezvous ........................................................................... 713.23 Required Initial Velocities <strong>to</strong> Get in<strong>to</strong> De-<strong>or</strong>biting Trajec<strong>to</strong>ry .......................... 753.24 Required ∆V <strong>to</strong> Achieve Rendezvous ............................................................... 753.25 Required ∆V and Needed Propellant f<strong>or</strong> Missions ............................................. 773.26 Propellant Mass Flow Rates f<strong>or</strong> Various Astrium COTS Thrusters .................. 783.27 Burn Times f<strong>or</strong> the Mission f<strong>or</strong> Different Thrust Levels ................................... 793.28 Total Mission Payload Mass of Five Non-functional GlobalStar Set ................ 79


viiiLIST OF FIGURESFigurePage1.1 Size Ranges of Space Debris Types ..................................................................... 21.2 Comparison Space Debris between 1956 – 2011 ................................................. 31.3 Monthly Number of Objects in Earth‘s Orbit by Object Type ............................. 41.4 Debris Cloud His<strong>to</strong>ry After after The the Collision of a Non-functioningCosmos Satellite with a Functioning Iridium Communications Satellite ...................... 61.5 Spatial Density of Objects by Size as a Function of Altitude .............................. 71.6 Gokturk Reconnaissance Satellite ........................................................................ 81.7 Mass Penalty (in percent) f<strong>or</strong> Propulsive De-<strong>or</strong>bit (Circular Orbit) ................... 111.8 Average Number of Impacts on Representative Spacecraft over 10-YearMission ......................................................................................................................... 131.9 Collision Probabilities 24 Hours after Breakup .................................................. 141.10 Orbit Lifetime Guideline (Chao and Oltrogge 13) ................................................ 151.11 Variation of Estimate Satellite Lifetime with Initial Altitude (Chao andOltrogge 13 ) ................................................................................................................... 161.12 Recognition and Tracking Module Experiment ................................................. 181.13 ETS-VII Experiment .......................................................................................... 191.14 Thrust-I sp Range of All Types of Propulsion Systems ....................................... 231.15 Segments of GlobalStar Satellite Constellation ................................................. 241.16 GlobalStar Satellite Constellation ...................................................................... 251.17 GlobalStar Spacecraft Characteristics ................................................................ 262.1 Moving Frame Attached <strong>to</strong> Target S/C from which Chaser S/C Observed ....... 292.2 Relative Motion of Elliptically Orbiting Spacecraft B and Circularly OrbitingSpacecraft A ................................................................................................................. 312.3 Position Vec<strong>to</strong>r of Chase Vehicle Relative <strong>to</strong> Target Vehicle ........................... 322.4 Co-moving Clohessy-Wiltshire Frame ............................................................... 352.5 Rendezvous Trajec<strong>to</strong>ry of aof a Target Spacecraft in the Neighb<strong>or</strong>hood of ItsChase Spacecraft .......................................................................................................... 423.1 Non-functional GlobalStar Satellites Orbits ....................................................... 453.2 Sequence of of V Requirement Calculations f<strong>or</strong> The the Five GlobalStar Suite483.3 Sequence of of V Requirement Calculations f<strong>or</strong> The the Six GlobalStar Suite49


1CHAPTER 1INTRODUCTIONOn Oc<strong>to</strong>ber 4, 1957, Sputnik I, the Russian-made spacecraft was placed inEarth‘s <strong>or</strong>bit. It was the first man-made Earth <strong>satellite</strong> in his<strong>to</strong>ry. In just a few decades<strong>satellite</strong> technology has advanced <strong>to</strong> the point where it has become a critical elementin supp<strong>or</strong>ting international communications. The development and advancement of<strong>satellite</strong> technology has played an imp<strong>or</strong>tant and pivotal role in nearly every field ofmodern human life, including civil and military communication, navigation andobservation, remote sensing, broadcasting, scientific experiments, mapping, providingweather inf<strong>or</strong>mation, and so on. The utility and security f<strong>or</strong> all <strong>satellite</strong> applicationsdepends on three space environment related fac<strong>to</strong>rs: (1) secure access <strong>to</strong> an <strong>or</strong>bital slotf<strong>or</strong> each <strong>satellite</strong>; (2) secure access <strong>to</strong> a radio-frequency allocation <strong>to</strong> allowcommunication with each <strong>satellite</strong>; and (3) security against space debris with thecapability <strong>to</strong> damage <strong>or</strong> destroy the <strong>satellite</strong>. Reduction of the <strong>or</strong>bital debris threat <strong>to</strong>existing and future spacecraft is the focus of this thesis.1.1 Problem Motivation and Description1.1.1 Space Debris and RisksF<strong>or</strong>matted: Font: 12 ptEvery space launch creates space debris, just as every operating terrestrialvehicle creates pollution on the Earth‘s surface and in its atmosphere. Thedevelopment and utilization of space-derived infrastructure has huge advantages, butas the variety of space applications and the associated population of <strong>or</strong>biting platf<strong>or</strong>msgrows, the potential f<strong>or</strong> catastrophic collisions between <strong>or</strong>biting objects increasessimultaneously. Many countries have the capability of putting spacecraft in<strong>to</strong> <strong>or</strong>bit,and, depending on the <strong>or</strong>bit and the <strong>or</strong>bital insertion methods, a variety of man-madeobjects have become ―<strong>satellite</strong>s‖ even though they serve no useful function in space.Furtherm<strong>or</strong>e, depending on the <strong>or</strong>bital characteristics and <strong>or</strong>bital lifetime of eachobject, much of the population of man-made <strong>or</strong>biting material becomes space debris.Space debris can be divided in<strong>to</strong> two types: (1) natural space debris, consistingof small pieces of cometary and asteroidal material called mete<strong>or</strong>oids; and (2)artificial space debris (also known as space waste, <strong>or</strong>bital debris <strong>or</strong> space junk)


2consisting of all objects in Earth‘s <strong>or</strong>bit that were created by humans and that nolonger function as operational <strong>satellite</strong>s. Man-made space debris consists ofeverything that belongs <strong>to</strong> <strong>satellite</strong> systems, such as spent rocket bodies and stages,solid propellant slag, dust and liquids from rocket mo<strong>to</strong>rs, defunct <strong>or</strong> failed <strong>satellite</strong>s(dead <strong>satellite</strong>s), explosion and collision fragments and paint flakes.Man-made space debris is divided in<strong>to</strong> four main groups: spent rocket bodies(R/B‘s), mission related debris, break-up fragments, and non-functional spacecraft.These space debris populations have different size distributions, as shown inFigure 1.1 1 .Figure 1.1 Size Ranges of Space Debris Types.Spacecraft are particularly vulnerable <strong>to</strong> collisions with space debris.Beginning with the first launch in<strong>to</strong> <strong>or</strong>bital space, the accumulating population ofspace debris has increased every year. Since the launch of Sputnik in 1957, over36,761 man-made objects have been catalogued 2 ; many have since re-entered theatmosphere. Currently, the Space Surveillance Netw<strong>or</strong>k (SSN) tracks m<strong>or</strong>e than22,000 man-made objects <strong>or</strong>biting the Earth with characteristic dimensions of 10centimeters <strong>or</strong> larger. About five percent of the tracked objects are functioning


3payloads <strong>or</strong> <strong>satellite</strong>s; eight percent are rocket bodies; and about 87 percent arefragmentation objects and inactive <strong>satellite</strong>s 3 . However, the overwhelming maj<strong>or</strong>ity ofdebris in Low Earth Orbit (LEO) is smaller than 10 centimeters and is <strong>to</strong>o small <strong>to</strong> beverifiably tracked and catalogued 3 . There are tens of millions of objects withcharacteristic dimensions between 1 and 10 centimeters (i.e., larger than a marble),and perhaps trillions of pieces measuring less than one cm 3 . Even tiny fragments ofspace debris can harm operational spacecraft due <strong>to</strong> the high relative velocities thatcan occur during in-<strong>or</strong>bit collisions.1.1.2 Man-Made Orbital Object Population GrowthF<strong>or</strong>matted: Font: 11 ptA computer-generated image comparison of man-made objects in Earth‘s <strong>or</strong>bitin 1956 (none, on the left) with January 2011, is displayed Figure 1.2 4 .Figure 1.2 Comparison Space Debris between 1956 – 2011.The <strong>or</strong>bital debris dots are scaled acc<strong>or</strong>ding <strong>to</strong> the image size of the graphic, in <strong>or</strong>der<strong>to</strong> emphasize their locations and are theref<strong>or</strong>e not scaled properly. However, theseimages provide a good visualization of regions of greatest <strong>or</strong>bital debris density.The rate of increase in the population of <strong>or</strong>biting space debris with time 5 isrepresented in Figure 1.3. Space debris is a growing problem and threat <strong>to</strong> theapproximately one-thousand functional and operational <strong>satellite</strong>s belonging <strong>to</strong> m<strong>or</strong>ethan 40 countries at this time.


4Figure 1.3 Monthly Number of Objects in Earth‘s Orbit by Object Type.Space debris travels in a variety of <strong>or</strong>bits and is affected by variousperturbation f<strong>or</strong>ces, including the effects of the Earth's atmosphere, gravitationalperturbation effects, and solar radiation pressure. As <strong>or</strong>bital altitude increases, theinfluence of the atmosphere in accelerating <strong>or</strong>bital decay becomes small, andtypically, large objects in <strong>or</strong>bits higher than approximately 600 km can remain in <strong>or</strong>bitf<strong>or</strong> tens, hundreds, <strong>or</strong> even thousands of years 3 . Space debris has the potential <strong>to</strong>directly threaten space security since it increases risks associated with accessing andusing space. On average, colliding objects in low Low Earth <strong>or</strong>bit Orbits (LEO) haverelative velocities of about 10 kilometers per second (about 36,000 kilometers perhour). Thus, the impact from a 1 kilogram (10 centimeter diameter) object in LEOwith this relative velocity is equivalent <strong>to</strong> that of a 35,000 kilogram truck moving at190 kilometers per hour on earth. A collision with a debris fragment of this size couldtheref<strong>or</strong>e result in the catastrophic break-up of a 1,000 kilogram spacecraft (a typicalspacecraft bus weighs about 1,200 kilograms) 3 . All spacecraft routinely experiencecollisions with particles smaller than 1 millimeter in diameter, but with rareexceptions, such impacts do not have highly deleterious effects.


5As mentioned above, space debris risks are escalating at present and futuremanned and unmanned space missions will be inhave greater perilrisk involved. Table1.1 summarizes the significant known unintentional collisions between objects inspace. The term ―cataloged debris‖ generally refers <strong>to</strong> debris that is large enough <strong>to</strong> bedetected and tracked from the ground 6 .Table 1.1 Unintentional Collision Chronology between Significant Space Objects.YEARCOLLISION DESCRIPTION1991Inactive Cosmos 1934 <strong>satellite</strong> hit by cataloged debris from Cosmos296 <strong>satellite</strong>.1996Active French Cerise <strong>satellite</strong> hit by cataloged debris from Arianerocket stage.1997Inactive NOAA 7 <strong>satellite</strong> hit by uncataloged debris large enough <strong>to</strong>change its <strong>or</strong>bit and create additional debris.2002Inactive Cosmos 539 <strong>satellite</strong> hit by uncataloged debris large enough<strong>to</strong> change its <strong>or</strong>bit and create additional debris.2005 U.S. rocket body hit by cataloged debris from Chinese rocket stage.2007Active Meteosat 8 <strong>satellite</strong> hit by uncataloged debris large enough <strong>to</strong>change its <strong>or</strong>bit.2007Inactive NASA UARS <strong>satellite</strong> believed hit by uncataloged debrislarge enough <strong>to</strong> create additional debris.2009 Active Iridium <strong>satellite</strong> hit by inactive Cosmos 2251.After a collision, a debris cloud is created similar <strong>to</strong> that shown schematicallyin Figure 1.4 6 . There are two debris clouds in this case; one is associated with―<strong>satellite</strong> Satellite 1‖ and the other is associated with ―<strong>satellite</strong> Satellite 2‖. Figure 1.4shows how the two clouds follow the <strong>or</strong>bits of the <strong>or</strong>iginal <strong>satellite</strong>s. As depicted,when the two <strong>or</strong>bits are perpendicular <strong>to</strong> each other, the space debris from thecollision becomes a global problem threatening all <strong>satellite</strong>s that pass through similar<strong>or</strong>bital altitudes.


6Figure 1.4 Debris Cloud His<strong>to</strong>ry After after The the Collision of a Non-functioningCosmos Satellite with a Functioning Iridium Communications Satellite 6 .Medium Earth Orbits (MEOs) between 2,000 km and about 36,000 km areemerging as a new focus in space debris studies, since those <strong>or</strong>bital altitudes containthe navigation <strong>satellite</strong> <strong>constellations</strong>; f<strong>or</strong> example, the Global Positioning System(GPS) constellation, used <strong>to</strong> locate with high accuracy the position of a receiver onthe ground, operates at a nominal altitude of 20,200 km. The vital role that thisnavigation system has achieved f<strong>or</strong> air and terrestrial transp<strong>or</strong>tation traffic controlmakes these <strong>constellations</strong> and that the <strong>or</strong>bital altitude c<strong>or</strong>respondingly imp<strong>or</strong>tant. The


7growing space debris problem will affect these imp<strong>or</strong>tant <strong>satellite</strong> <strong>constellations</strong>. One<strong>or</strong>bit spatial density (objects per unit volume) represents the effective number ofspacecraft and other objects as a function of altitude. Spatial density with respect <strong>to</strong>altitude 7 f<strong>or</strong> three different size thresholds includes: objects with diameters larger than1 mm (<strong>to</strong>p red line), 1 cm (middle green line) and 10 cm (bot<strong>to</strong>m blue line) and isshown in Figure 1.5.On the <strong>or</strong>der of 1 mm1 mm <strong>to</strong> 10 cm10 cm <strong>or</strong> largerFigure 1.5 Spatial Density of Objects by Size as a Function of Altitude 7 .Obviously, the <strong>to</strong>tal space debris population above 2,000 km can threaten critical<strong>satellite</strong> <strong>constellations</strong>.1.2 Turkey’s Space Projects (GOKTURK)The development and advancement of <strong>satellite</strong> technology and its capabilitiesprovides m<strong>or</strong>e applications, not only f<strong>or</strong> civil purposes such as television and radiobroadcasting (TurkSat series), but also <strong>to</strong> supp<strong>or</strong>t military objectives such as <strong>satellite</strong>based communication, intelligence, observation missions and so on. Hence, theTurkish Armed F<strong>or</strong>ces has started the process of developing and deploying a veryhigh resolution Electro-Optical (EO) Reconnaissance and Surveillance Satellite that


8will serve both military and civilian purposes. After obtaining the necessaryassessment and approval by the Turkish Armed F<strong>or</strong>ces, the Under Secretariat of theDefense Industry, the project was named the Gokturk Project and was initiated in2005. The Turkish Armed F<strong>or</strong>ces assigned auth<strong>or</strong>ity over the project <strong>to</strong> the TurkishAir F<strong>or</strong>ce, and they are who is responsible f<strong>or</strong> determination of technicalspecifications f<strong>or</strong> the <strong>satellite</strong> and its associated supp<strong>or</strong>t systems. The Turkish AirF<strong>or</strong>ces and Under Secretariat of the Defense Industry signed an agreement with ItalianTelespazio and Thales Alenia Space Association on July 2009 8 . A rendition of theGokturk <strong>satellite</strong> is shown in Figure 1.6 9 .Figure 1.6 Gokturk Reconnaissance Satellite.The Gokturk <strong>satellite</strong> has the following characteristics: 9- Orbital The <strong>or</strong>bital period will be approximately 100 minutes (it willcomplete 14 <strong>or</strong>bits per day) and it will make observations all over thew<strong>or</strong>ld,- An electro-optical camera system with 4-band multispectral (col<strong>or</strong>) andpanchromatic (black and white) images,- Sun A sun synchronous low Low Earth <strong>or</strong>bit Orbit (650-700 km) f<strong>or</strong>proper target lighting, and- Ability The ability <strong>to</strong> operate in point, stereo, strip, and wide areaobservation modes.F<strong>or</strong>matted: Font: Bold


9-The general technical properties f<strong>or</strong> its ground station will be: 9F<strong>or</strong>matted: Indent: Left: 0.75", No bullets<strong>or</strong> numbering, Tab s<strong>to</strong>ps: Not at 1.09"- Satellite ground command and control systems,- Reconfiguration of <strong>satellite</strong> position and tasking, mission loading andimage downloading,- Image processing, assessments, sensing, and- Planning image requisitions, archive assessments and distribution ofimages.The general and primary objectives of the Gokturk project will be <strong>to</strong> providethe necessary supp<strong>or</strong>t f<strong>or</strong> the Turkish Armed F<strong>or</strong>ces. The <strong>satellite</strong> is expected <strong>to</strong>supp<strong>or</strong>t additional functions associated with preventing terr<strong>or</strong>ism while providingimaging and reconnaissance assistance <strong>to</strong> Turkey‘s allies. Gokturk is scheduled <strong>to</strong>enter its <strong>or</strong>bit in 2014 9 .While Turkey is just starting its space program, it has a progressive andcomprehensive plan f<strong>or</strong> developing space technology. As a space-faring nation,Turkey will need <strong>to</strong> be involved in space programs related <strong>to</strong> space debris mitigation,supp<strong>or</strong>ting such countries as the United States (National Aeronautics and SpaceAdministration), the European Union (European Space Agency, Agenzia SpazialeItaliana, German Aerospace Center), Japan (Japan Aerospace Expl<strong>or</strong>ation Agency)and the others members of the Inter-Agency Space Debris Co<strong>or</strong>dination Committee(IADC).1.3 Review of Previous Research on Debris MitigationIn this section, previous research related <strong>to</strong> characterizing and remediating thespace debris problem will be discussed. In addition, the possibility of <strong>or</strong>bitalrendezvous and <strong>repair</strong> of inactive spacecraft will be expl<strong>or</strong>ed, requiring a discussionof literature related <strong>to</strong> terminal rendezvous between two spacecraft and the associateddevelopment of spacecraft removal systems.1.3.1 Space Debris Hazards and MitigationF<strong>or</strong>matted: Font: 11 ptSpace access and the sustainability of space-related missions are veryimp<strong>or</strong>tant contemp<strong>or</strong>ary issues. Accelerating space technology developments


10continue, but those developments in space technology create additional constraints onfurther expansion. One of those constraints is the associated space debris problem. Inthis section three space debris hazard and mitigation studies will be reviewed; onestudy summarized techniques f<strong>or</strong> controlling the growing man-made debris populationin Earth‘s <strong>or</strong>bits 10 ; one study has produced an <strong>or</strong>bital debris hazard and environmentassessment f<strong>or</strong> the <strong>satellite</strong> <strong>constellations</strong> 11 and one study is an examination of andestimations of <strong>or</strong>bit lifetimes of man-made objects 12 .Petro 10 has discussed man-made <strong>or</strong>bital debris control and mitigation,concluding that it can be approached as a problem of c<strong>or</strong>rection <strong>or</strong> prevention.Spacecraft shielding, eff<strong>or</strong>ts <strong>to</strong> retrieve derelict spacecraft and sweeper devices <strong>to</strong>remove small debris are c<strong>or</strong>rective approaches f<strong>or</strong> reducing the <strong>or</strong>bital debrispopulation. Provisions f<strong>or</strong> self-removal of spacecraft and rocket stages and theincreased use of reusable space hardware are appropriate preventative approaches.Orbital debris studies of Petro‘s group have been examined by NASA Johnson SpaceCenter, approaching the problem using four general debris control techniques:1) Active active retrieval of large objects, 2) provisions f<strong>or</strong> self-disposal inc<strong>or</strong>p<strong>or</strong>atedin new spacecraft, 3) sweeper devices <strong>to</strong> remove small debris, and 4) increasing theuse of reusable space hardware.The approach f<strong>or</strong> active retrieval of large objects is <strong>to</strong> collect non-functional <strong>or</strong>useless defunct <strong>satellite</strong>s with an au<strong>to</strong>nomous <strong>or</strong> remotely controlled dexterousvehicle. That study handled the au<strong>to</strong>nomous <strong>or</strong> remotely controlled dexterous vehicleemploying two de-<strong>or</strong>biting options 10 after the dexterous vehicle had grabbed the target<strong>satellite</strong>. In the first option, it executed the de-<strong>or</strong>bit maneuver while linked with thetarget <strong>satellite</strong>, then separated from the target <strong>satellite</strong> and reinserted itself in<strong>to</strong> adifferent <strong>or</strong>bit, allowing the discarded object <strong>to</strong> re-enter the Earth‘s atmosphere.Alternatively, the target <strong>satellite</strong>s can be collected and maintained <strong>to</strong>gether in a safe<strong>or</strong>bit f<strong>or</strong> possible use as spare parts <strong>or</strong> raw materials. In the second option, thedexterous robot executes executed an au<strong>to</strong>nomous <strong>or</strong> remotely controlled rendezvouswith the target <strong>satellite</strong> then attaches attached a separate de-<strong>or</strong>bit device <strong>to</strong> the targe<strong>to</strong>bject. The attached device might be a de-<strong>or</strong>bit propulsion package <strong>or</strong> a passive dragdevice.Comment [KBS2]: What study? I‘d sayAuth<strong>or</strong>(s) (date) instead.


11Designing f<strong>or</strong> self-disposal in new spacecraft is a useful approach f<strong>or</strong> reducing<strong>or</strong>bital debris as part of an integrated process. The integrated de-<strong>or</strong>bit device could bea propulsion package, a drag-augmentation system, <strong>or</strong> a combination of the two 10 .Launched spacecraft can have self-disposal devices inc<strong>or</strong>p<strong>or</strong>ated as bus elements andrepresenting a small fraction of the <strong>to</strong>tal spacecraft mass. Three cases were examinedin terms of the mass penalty produced by the propulsive de-<strong>or</strong>biting device, assumingspecific impulse values of 250, 350, and 450 seconds and those results are shown inFigure 1.7 10 .Figure 1.7 Mass Penalty (in percent) f<strong>or</strong> Propulsive De-<strong>or</strong>bit (Circular Orbit).The mass fraction penalty increases with altitude, but the slope becomes relatively flatabove 10,000 km. F<strong>or</strong> circular <strong>or</strong>bits above 25,000 km, an escape from Earth‘s <strong>or</strong>bit isless costly than a de-<strong>or</strong>bit maneuver 10 .


12The use of sweeper devices <strong>to</strong> remove small objects is a concept f<strong>or</strong> clearingsmall size <strong>or</strong>bital debris. Large foam-filled balloons <strong>or</strong> large panels like the vanes of awindmill can be used as ―sweepers‖. However, these devices are effective only whenthey can sweep huge areas and launch, deployment, and maintenance of these verylarge systems would require an extremely large investment. Currently, these devicesare not considered <strong>to</strong> be feasible and need m<strong>or</strong>e research and development.Reusable space hardware is considered the best solution f<strong>or</strong> <strong>or</strong>bital spacedebris mitigation. Single use <strong>satellite</strong>s could be replaced by multipurpose spaceplatf<strong>or</strong>ms that can be <strong>repair</strong>ed and upgraded periodically. Reusable <strong>or</strong>bitalmaneuvering vehicles and <strong>or</strong>bital transfer vehicles could replace the expendable upperstages that litter the <strong>or</strong>bital environment 10 .Petro 10 showed that drag devices can be competitive with propulsion systemsas a means of self-disposal f<strong>or</strong> <strong>satellite</strong>s and upper stages. The fact that the dragdevices do not require active control makes them very attractive. Above 700 km,propulsive systems may be the only practical option, but above 25,000 km, a smaller∆V is required <strong>to</strong> simply boost dead defunct <strong>satellite</strong>s out of Earth‘s <strong>or</strong>bit rather than<strong>to</strong> de-<strong>or</strong>bit them.Spencer et al. 11 examined two categ<strong>or</strong>ies of environmental impacts f<strong>or</strong> <strong>satellite</strong><strong>constellations</strong>: (1) the effects of <strong>satellite</strong> <strong>constellations</strong> on the space debrisenvironment and (2) the effects of the environment on the <strong>satellite</strong> <strong>constellations</strong>.They developed a <strong>methodology</strong> <strong>to</strong> assess the risk posed <strong>to</strong> and by a large <strong>satellite</strong>constellation. In their computer simulation study, they assumed that a <strong>satellite</strong>constellation included 800 <strong>satellite</strong>s that were designed f<strong>or</strong> a 10-year useful life,starting in 2001. The constellation was <strong>to</strong> be distributed in 20 <strong>or</strong>bital planes with 40<strong>satellite</strong>s per plane. The <strong>or</strong>bits were circular and sun-synchronous at 700 km altitude.The ascending nodes of adjacent planes were spaced every 18 degrees around theequa<strong>to</strong>r 11 . They used several computer models and they categ<strong>or</strong>ized their results in<strong>to</strong>three risk components: 1) long-term hazard assessment, 2) sh<strong>or</strong>t-term hazardassessment, and 3) inter<strong>satellite</strong> collision hazard assessment.F<strong>or</strong>matted: Font: Not ItalicIn Spencer et al.‘stheir long-term assessments, they estimated the collisionprobabilities f<strong>or</strong> <strong>satellite</strong>s and components. Based on the results of the study, the


13number of impacts from debris impacts greater than 1 mm over a 10-year missionlifespan was divided in<strong>to</strong> upper and lower bound collision estimates f<strong>or</strong> various<strong>satellite</strong> element categ<strong>or</strong>ies and is displayed in Figure 1.8 11 .Figure 1.8 Average Number of Impacts on Representative Spacecraft over 10-YearMission.From the long term assessments, they found that this large constellation couldexpect a large number of impacts with smaller size debris. They suggested thatmanufacturers design these <strong>satellite</strong>s inc<strong>or</strong>p<strong>or</strong>ating shielded wires, cables, and othervulnerable parts in <strong>or</strong>der <strong>to</strong> protect them from probable impacts with millimeter-sizeddebris during their operational lives. The functionality of the <strong>satellite</strong>s can be assuredby proper hardening via shielding and redundancy 11 .Spencer et al.‘s 11 Their sh<strong>or</strong>t term study 11 examined collisions and breakupevents near an operational <strong>satellite</strong> and the cascading effects of these collisions andbreakup events f<strong>or</strong> a the nearest <strong>satellite</strong>. They The auth<strong>or</strong>s assumed two types ofcollision and breakup events. One case assumed that a collision occurred at the samealtitude (700 km) as the constellation <strong>satellite</strong> <strong>or</strong>bit and the other assumed that acollision occurred at a lower altitude (663 km). F<strong>or</strong> both breakup altitudes, thecollision probabilities f<strong>or</strong> 1- mm and larger fragments was plotted during the 24 hoursafter breakup and is shown in Figure 1.9.


14Figure 1.9 Collision Probabilities 24 Hours after Breakup.F<strong>or</strong>matted: Indent: First line: 0"


15The numbers refer <strong>to</strong> arbitrary <strong>satellite</strong> numbers in Figure 1.9. Spencer et al. 11 Theyfound from their IMPACT explosion models 11 that the impact probabilities f<strong>or</strong>impacts from debris with dimensions of 1 mm and larger increased by a fac<strong>to</strong>r of 60.Spencer et al.‘s 11 Their inter<strong>satellite</strong> collision hazard assessment utilized three<strong>satellite</strong> collision time frames: 1) N<strong>or</strong>mal operations, 2) Uncontrolled de-<strong>or</strong>bi<strong>to</strong>perations and3) Controlled de-<strong>or</strong>bit operations. They made simulationsemploying all three scenarios and the results of their simulation showed that duringthe controlled de-<strong>or</strong>bit of a <strong>satellite</strong> using low-thrust propulsion, the time duration ofthe de-<strong>or</strong>bit process could vary between 8 months and 5 years, depending on the phaseof the solar cycle. The time <strong>to</strong> descend through the constellation was estimated <strong>to</strong> beup <strong>to</strong> two years. Additional considerations such as variations in <strong>or</strong>bital spacing(altitude, inclination, and eccentricity) could be utilized <strong>to</strong> further reduce collisionopp<strong>or</strong>tunities and decrease the collision risk 11 .From the Spencer et al. 11 comprehensive <strong>satellite</strong> constellation space debrisassessment it is apparent that these events are an imp<strong>or</strong>tant consideration f<strong>or</strong>constellation <strong>satellite</strong> design and <strong>or</strong>bit management.F<strong>or</strong>matted: Font: Not ItalicFinkelman and Oltrogge 12 have examined the practical implications of the 25-year Low Earth Orbit post-mission lifetime guideline. Satellite <strong>or</strong>bit lifetimes varywith <strong>or</strong>bit characteristics, drag (ballistic) coefficient, and other characteristics, such asspacecraft <strong>or</strong>ientation. There are many ways <strong>to</strong> predict a <strong>satellite</strong> <strong>or</strong>bital lifetime, butunf<strong>or</strong>tunately all of the prediction methods must be based on accurate predictions ofthe long term spacecraft perf<strong>or</strong>mance and detailed knowledge of the long-termbehavi<strong>or</strong> of the Earth‘s atmosphere. Neither element can be predicted accurately andas a consequence, <strong>satellite</strong> lifetime predictions are extremely uncertain. The <strong>or</strong>bitlifetime prediction method developed by Chao and Oltrogge 13 has been recognized byinternational consensus as the most useful and their generic lifetime predictions interms of initial <strong>or</strong>bit inclination, perigee altitude and the characteristic ballisticcoefficient of the object is shown in Figure 1.10 12 . This figure illustrates thedependence of natural <strong>or</strong>bit lifetime with respect <strong>to</strong> the a 25 year guideline.


16Figure 1.10 Orbit Lifetime Guideline (Chao and Oltrogge 13 ).F<strong>or</strong>matted: Not Superscript/ SubscriptTheir results show that the <strong>or</strong>bital lifetime is extremely sensitive <strong>to</strong> <strong>or</strong>bitalaltitude. The influence of initial <strong>or</strong>bit altitude on estimated <strong>satellite</strong> lifetime is shownin Figure 1.11.Figure 1.11 Variation of Estimate Satellite Lifetime with Initial Altitude (Chao andOltrogge 13 ).


17Orbit altitude is the most significant property f<strong>or</strong> estimating the <strong>or</strong>bit lifetime.The slope of the Figure 1.11 shows the variation of estimated lifetime with the altitudef<strong>or</strong> <strong>satellite</strong>s in 28 degree inclination and the slope is approximately 0.1 years/km 12 .Sot This result can suggests that the <strong>satellite</strong> lifetime could be m<strong>or</strong>e than <strong>or</strong> less than 25years with an altitude change of just a few kilometers. This is probably most likelywithin the uncertainty of being able <strong>to</strong> maintain an <strong>or</strong>bit, and becomes w<strong>or</strong>se at higheraltitudes, but it does n't not matter as much from the perspective of the IADCguidelines, since objects in such <strong>or</strong>bits will require an active means of disposal 12 .The actual solar cycle strongly influences <strong>or</strong>bital decay. Finkelman andOltrogge 12 examined the solar cycle influences on predicted <strong>or</strong>bital lifetime. Theyassumed that the same <strong>satellite</strong> was inserted initially on the same <strong>or</strong>bit at in one yearintervals. The results were significantly different. Predicted <strong>satellite</strong> lifetimes werehalved when launched around 2016, compared with the same <strong>satellite</strong> launched in thesame <strong>or</strong>bit in 2013 <strong>or</strong> 2022 12 .They also considered the propellant mass necessary <strong>to</strong> lower the spacecraftaltitude in <strong>or</strong>der <strong>to</strong> reduce its lifetime <strong>to</strong> 25 years, at the completion of its mission. Itshould first be noted that the propellant mass required either <strong>to</strong> lower an <strong>or</strong>bit <strong>or</strong>maintain an <strong>or</strong>bit is relatively small. However, at an 800 km circular altitude, f<strong>or</strong>example, the propellant requirement f<strong>or</strong> <strong>or</strong>bit lowering in <strong>or</strong>der <strong>to</strong> comply with the 25-year lifetime is m<strong>or</strong>e than ten times the requirement f<strong>or</strong> remaining in the <strong>or</strong>iginal <strong>or</strong>bitf<strong>or</strong> another year. In other w<strong>or</strong>ds, an opera<strong>to</strong>r could buy 10 years m<strong>or</strong>e <strong>or</strong>bit lifetime byemploying the same propellant mass required <strong>to</strong> dispose of the <strong>satellite</strong> within 25years. Since the maj<strong>or</strong> reason f<strong>or</strong> end of mission is propellant depletion, this is atempting tradeoff 12 .A strong case can be made f<strong>or</strong> refurbishing inoperable communications<strong>satellite</strong>s in low Low Earth <strong>or</strong>bitOrbit, rather than de-<strong>or</strong>biting those <strong>satellite</strong>s.However, the risks associated with an unintended collision between an inactivecommunications <strong>satellite</strong> and a robotic <strong>repair</strong> spacecraft must be minimized. A greatdeal of research has been devoted <strong>to</strong> minimizing the risks associated with <strong>or</strong>bitalrendezvous and will be summarized in the next section.


181.3.2 Terminal Rendezvous between Two SpacecraftF<strong>or</strong>matted: Font: 12 ptOrbital rendezvous has been a subject of intense investigation since thebeginning of the space age. When astronauts controlled <strong>or</strong>bital rendezvous, theproblem was primarily one of accurate modeling, simulation and training. However,te<strong>leo</strong>perated <strong>or</strong> au<strong>to</strong>mated rendezvous operations are now feasible. New spacetechnologies and much better knowledge of the space environmental characteristicshave improved our ability <strong>to</strong> safely execute a rendezvous between two spacecraft. Inthis section two primary studies will be reviewed. One approach is based oncognitive-controlled vision systems f<strong>or</strong> rendezvous management 14 , and the other is anexamination of an unmanned experimental <strong>satellite</strong> that became the w<strong>or</strong>ld's first<strong>satellite</strong> <strong>to</strong> use a robot arm <strong>to</strong> manipulate another <strong>satellite</strong> 15 . However, the potentialf<strong>or</strong> a collision can threaten the survivalcontinued existence of the two spacecraft andthe possible release of debris can threaten other high-value objects as well.Qureshi, Terzopoulos, and Jasiobedzki 14 demonstrated a robotic arm whichwas controlled using a vision system that had the ability <strong>to</strong> capture a free-flying<strong>satellite</strong> au<strong>to</strong>nomously. They described an embodied, task-<strong>or</strong>iented vision systemwhich can combine object recognition and tracking with high-level symbolicreasoning. The au<strong>to</strong>nomous system under development can control target <strong>satellite</strong>approach, maneuver itself <strong>to</strong> get in<strong>to</strong> the desired docking position, and docking withthe target <strong>satellite</strong> using an on-board controller <strong>to</strong> estimate the position and track thetarget <strong>satellite</strong>. In this cognitive system, they demonstrated its ability <strong>to</strong> estimate thecurrent position and <strong>or</strong>ientation of the target <strong>satellite</strong> employing captured images, andbehavi<strong>or</strong>-based perception and mem<strong>or</strong>y units using contextual inf<strong>or</strong>mation <strong>to</strong>construct a symbolic description of the rendezvous scene. Ultimately, the cognitivemodule used knowledge of the encoded rendezvous scene dynamics and a type ofsituation calculus <strong>to</strong> construct a rendezvous scene interpretation. Finally, the cognitivemodule f<strong>or</strong>mulated a plan <strong>to</strong> achieve the current goal.The oObject recognition and tracking module has the ability <strong>to</strong> create imagesfrom a calibrated video camera-pair mounted on the end-effec<strong>to</strong>r of the roboticmanipula<strong>to</strong>r and compute subsequently its estimated relative position <strong>to</strong> the target<strong>satellite</strong>. Images created by the module during an experiment are shown in


19Figure 1.12 14 . The left image was taken from a distance of 5 m and the right imagewas taken from 0.2 m.Figure 1.12 Recognition and Tracking Module Experiment.The cognitive vision controller controls manipulates the image recognition andtracking module. It takes in<strong>to</strong> account several fac<strong>to</strong>rs such as current task, the currentstate of the environment, the advice from the symbolic reasoning module and thecharacteristics of the vision module. The cognitive vision control unit includes twosub-units, which are called the perception and mem<strong>or</strong>y units, in addition <strong>to</strong> thesymbolic reasoning unit. The perception unit receives the most current inf<strong>or</strong>mationfrom the active vision configuration and computes the estimated target <strong>satellite</strong>position. The symbolic reasoning unit plans the actions of the active rendezvouselement required <strong>to</strong> accomplish the task. They tested all of the equipment in asimulated virtual environment and in a physical lab<strong>or</strong>a<strong>to</strong>ry environment reproducingthe illumination conditions of a representative space environment such as a stronglight source, very low ambient light and harsh shadows. The demonstrationexperiment safely captured the simulated target <strong>satellite</strong> via vision-based sensing,meeting their perf<strong>or</strong>mance requirements.Kawano et al. 15 rep<strong>or</strong>ted on the first au<strong>to</strong>nomous rendezvous Rendezvous anddocking Docking Vehicle (RDV) of an Engineering Test Satellite-VII (ETS-VII) withan associated uninhabited spacecraft, which is shown schematically in Figure 1.13.The RDV technology demonstra<strong>to</strong>r successfully rendezvoused, then coupled twospacecraft. The ETS-VII experiment consisted of two <strong>satellite</strong>s, and the experimentwas conducted in two steps. First, the chaser <strong>satellite</strong> released the target <strong>satellite</strong>.Subsequently, the chaser <strong>satellite</strong> approached and then docked with the target <strong>satellite</strong>.F<strong>or</strong>matted: Font: Not Italic


20Figure 1.13 ETS-VII Experiment.The ETS-VII RDV system demonstrated the feasibility of three maj<strong>or</strong> au<strong>to</strong>nomousrendezvous functions: 1) au<strong>to</strong>nomous rendezvous and docking by an uninhabited<strong>satellite</strong>; 2) safe au<strong>to</strong>nomous rendezvous and docking; and 3) low-impact au<strong>to</strong>nomousdocking 15 .Uninhabited RDV systems can be categ<strong>or</strong>ized either as au<strong>to</strong>nomous RDVs <strong>or</strong>remotely piloted RDVs. Au<strong>to</strong>nomous RDV was chosen f<strong>or</strong> this demonstratedexperiment because of its utility and applicability <strong>to</strong> a variety of spacecraft types,while enabling them <strong>to</strong> demonstrate the feasibility of a fully au<strong>to</strong>nomous, highlyaccurate and reliable rendezvous system that was capable of executing rendezvousand docking even when the spacecraft pair was not in continuous communicationwith the ground station.The experiments were initiated when the chaser <strong>satellite</strong> ejected the target<strong>satellite</strong> with a departure speed of 1.8 cm/sec. In the first experiment, the chaser<strong>satellite</strong> started <strong>to</strong> control its relative attitude and position au<strong>to</strong>matically and separatedup <strong>to</strong> 2 m from the target, which was the holding point. The target and chaser<strong>satellite</strong>s flew in f<strong>or</strong>mation f<strong>or</strong> 15 min., utes, maintaining the separation distance of 2m. When the approach command was sent <strong>to</strong> the chaser <strong>satellite</strong>, it started <strong>to</strong>approachapproached the target <strong>satellite</strong> with a relative velocity of 1 cm/s, until itcaptured the target <strong>satellite</strong>. First The first experiment was successfully completedafter the chaser <strong>satellite</strong> au<strong>to</strong>matically docked <strong>to</strong> the target <strong>satellite</strong> au<strong>to</strong>matically.The second experiment (FP-2) was initiated in the same way as the first, butthe separation distance was substantially larger (2.5 km rather than 2 m). All of the


21command and control processes were the same as in the first experiment, but some ofthe chaser <strong>satellite</strong> thrusters did not fire c<strong>or</strong>rectly during the first attempt andc<strong>or</strong>recting that fault extended the mission. After modifying the RDV software, thetwo spacecraft were successfully docked, achieving the miles<strong>to</strong>ne of the firstsuccessful au<strong>to</strong>nomous rendezvous and docking demonstration.The ETS-VII experiment successfully demonstrated (1) relative approach, (2)final approach and (3) actual docking 15 .1.3.3 Development of Spacecraft Removal SystemsF<strong>or</strong>matted: Font: 12 ptSpacecraft removal systems are not a new idea. However, some constraintshave blocked their development. Challenges related <strong>to</strong> cost and scheduling resources,operational constraints, liability and political challenges have all represented barriers.These constraints are all related <strong>to</strong> removing objects from an <strong>or</strong>bit. In addition, it hasnot yet been widely accepted as being feasible using current technical capabilities.However, the previous and recent maj<strong>or</strong> breakup events that occurred in 2009between a functional <strong>satellite</strong> (Iridium 33) and a non-functional <strong>satellite</strong> (Cosmos2251), depicted in Figure 1.4, and tabulated in Table 1.1, and ongoing spaceenvironment modeling eff<strong>or</strong>ts have certainly reignited the interest in using spacecraftremoval systems <strong>to</strong> remediate the space environment. In this section, active removalsystems and their technical analysis will be reviewed 16 , along with an evaluation ofpropulsive system requirements f<strong>or</strong> de-<strong>or</strong>biting a <strong>satellite</strong> 17 .Karl 16 has analyzed the <strong>or</strong>bital debris problem and categ<strong>or</strong>ized <strong>or</strong>bital debrisby their sizes. He put f<strong>or</strong>ward several ideas f<strong>or</strong> effecting the active removal of <strong>or</strong>bitaldebris. Since the <strong>or</strong>bital debris population grows with every launch, <strong>satellite</strong>s must beprotected using passive systems such as shielding, <strong>or</strong> active collision prevention byusing small <strong>or</strong>bital maneuvers <strong>to</strong> avoid tracked <strong>or</strong>bital debris.F<strong>or</strong> <strong>or</strong>bital debris smaller than 1 cm, a sweeper spacecraft can be considered.If that type of spacecraft was covered with a special material such as foils <strong>or</strong> fibers 16 ,possessing material characteristics that provide high strength and low mass, it couldcollect (sweep) small size <strong>or</strong>bital debris objects by s<strong>to</strong>pping the high velocity particleswithout creating new <strong>or</strong>bital debris. After that type of spacecraft completed its sweepmission, it could be burned up re-entering the Earth‘s atmosphere.


23propulsion systems covered a range of thrusts and specific impulses (I sp ) as shown inFigure 1.14 17 . Figure 1.14a shows the thrust range of all propulsion systems, ,Figure 1.14b represents the specific impulse range of chemical propulsion systemsexamined and Figure 1.14c shows the specific impulse range of electrical propulsionsystems. Table 1.2 summarizes the advantages and disadvantages of the variouspropulsion systems 17 .F<strong>or</strong>matted: Font: 2 ptF<strong>or</strong>matted: Line spacing: single


25Figure 1.14 Thrust-I sp Range of All Types of Propulsion Systems.Table 1.2 Advantages and Disadvantages of Propulsion Systems.Type of Prop. Advantages Disadvantages Type of Prop. Advantages DisadvantagesSimple Extremely low Isp Simple, Reliable One thruster per burnCold GasLow system cost Moderate impulse capability Solid Low cost Total Impulse fixReliable Low density Propulsion High density Currently not qualifiedSafe High pressure Low structural index f<strong>or</strong> longterm spaceWide thrustModulableLow IspMono rangeHybrid SimpleNot qualifiedPropellant ModulablePropulsion ReliableLack of suitable(mostly) <strong>to</strong>xic fuelsProvenLow cos<strong>to</strong>xidizerWide thrust Complex Low thrustBi-Propellant range Costly ElectricalComplex(S<strong>to</strong>rable) Modulable Heavy Long maneuver timeProven Toxic Power consumptionPropulsion Very high Isp F<strong>or</strong>matted: Indent: First line: 0.5"Burkhart et al. 17 also discussed specific types of de-<strong>or</strong>biting options:1) uncontrolled de-<strong>or</strong>biting, 2) controlled de-<strong>or</strong>biting and 3) maneuvering thespacecraft in<strong>to</strong> disposal <strong>or</strong>bit regions. The uncontrolled de-<strong>or</strong>biting process starts withone <strong>or</strong> m<strong>or</strong>e deceleration maneuvers <strong>to</strong> reduce the object velocity and perigee altitude.This <strong>or</strong>bital change increases the aerodynamic drag and thus reduces the <strong>or</strong>bital lifetime of the object. Controlled de-<strong>or</strong>bit maneuvers are basically the same as theuncontrolled de-<strong>or</strong>biting maneuvers, but they inc<strong>or</strong>p<strong>or</strong>ate several propulsive retroburnand re-entry maneuvers in <strong>or</strong>der <strong>to</strong> produce a ∆V vs.versus a time profile thatfollows a trajec<strong>to</strong>ry with a predictable ground impact location. Maneuveringspacecraft in<strong>to</strong> disposal <strong>or</strong>bits (graveyard <strong>or</strong>bits) is an option but it was not discussedin the Burkhart et al. 17 study.F<strong>or</strong>matted: Font: Not ItalicF<strong>or</strong>matted: Font: Not Italic


261.4 Description of the GlobalStar ConstellationThe Globalstar communication system consists of a space segment, a usersegment, a ground segment, and four terrestrial netw<strong>or</strong>ks, as shown in Figure 1.15.Figure 1.15 Segments of GlobalStar Satellite Constellation.The space segment of the Globalstar constellation was planned initially <strong>to</strong> be52 <strong>satellite</strong>s (48 operational and 4 on-<strong>or</strong>bit spares). The <strong>satellite</strong>s are in a 48-8-1 18Walker constellation, in the Space Systems L<strong>or</strong>al "Big LEO" global mobilecommunications netw<strong>or</strong>k, offering global real time voice, data and fax. TheGlobalstar <strong>satellite</strong>s have beenwere launched from the Baikonur Cosmodrome usingSoyuz launch vehicles. The <strong>satellite</strong>s are 3-axis stabilized, employing magne<strong>to</strong>meterson deployable booms, sun sens<strong>or</strong>s, GPS attitude sens<strong>or</strong>s, and they carry twodeployable solar arrays, capable of delivering 1,100 W. The <strong>satellite</strong>s in the first-


27generation constellation were designed <strong>to</strong> operate at full perf<strong>or</strong>mance f<strong>or</strong> a minimumof 7.5 years. The <strong>satellite</strong> constellation is depicted in Figure 1.16 18 .Figure 1.16 GlobalStar Satellite Constellation.The <strong>satellite</strong>s in the GlobalStar system have been placed in<strong>to</strong> low Low earthEarth <strong>or</strong>bits Orbits in eight operational planes containing six <strong>satellite</strong>s each, <strong>or</strong>bitingat nearly constant 1,414 kilometer km altitudes, and inclined at 52°. Each <strong>satellite</strong> hasa nominal <strong>or</strong>bital period of 114 minutes and the overall constellation covers the globebetween 67° N<strong>or</strong>th and 67° South Latitudelatitude. The Globalstar system providescommunications from any point on the earth Earth‘s surface <strong>to</strong> any other point on theearth Earth‘s surface, exclusive of the polar regions. The <strong>satellite</strong>s utilize SS/L<strong>or</strong>alLS-400 platf<strong>or</strong>ms, with a trapezoidal body shape, along with the two deployable solarpanels. In that way, multiple <strong>satellite</strong>s can be carried on and be deployed from thesame launch vehicle. The <strong>satellite</strong> propulsion systems employ hydrazine, with aprimary function of station keeping. The mass of each <strong>satellite</strong> is 450 kg, and the drymass is 350 kg.The Globalstar <strong>satellite</strong> is a simple, low-cost <strong>satellite</strong> designed <strong>to</strong> minimizeboth <strong>satellite</strong> costs and launch costs. A pic<strong>to</strong>rial sketch of the <strong>satellite</strong> and some of themaj<strong>or</strong> characteristics are summarized in Figure 1.17 18 .


28Figure 1.17 GlobalStar Spacecraft Characteristics.1.5 Thesis OutlineVarious governmental agencies and international <strong>or</strong>ganizations are beginning<strong>to</strong> track space debris and also research possible mitigation solutions. One such debrismitigation <strong>or</strong>ganization is the Inter-Agency Debris Co<strong>or</strong>dinating Committee (IADC)of the United Nations. Guidelines developed by IADC are the current basis f<strong>or</strong> LEO<strong>satellite</strong> debris mitigation measures 19 . Quoting from that document:"A spacecraft <strong>or</strong> <strong>or</strong>bital stage should be left in an <strong>or</strong>bit in which, using anaccepted nominal projection f<strong>or</strong> solar activity, atmospheric drag will limit the<strong>or</strong>bital lifetime after completion of operations. A study on the effect of postmission <strong>or</strong>bital lifetime limitation on collision rate and debris populationgrowth has been perf<strong>or</strong>med by the IADC. This IADC and some other studiesand a number of existing national guidelines have found 25 years <strong>to</strong> be areasonable and appropriate lifetime limit."As a result of those studies and recommendations made by international<strong>or</strong>ganizations, countries with the ability <strong>to</strong> access space have begun <strong>to</strong> give attention


29<strong>to</strong> the management of space debris in <strong>or</strong>der <strong>to</strong> reduce the risks of collisions and thusaddress avoidable manned and unmanned mission failures.The objective of this thesis was is <strong>to</strong> investigate mitigation of space debris byexamining an approach f<strong>or</strong> recovery of a specific population of spent <strong>satellite</strong>s.Decommissioning a spacecraft is the final event associated with any space mission. Ithas theref<strong>or</strong>e become standard practice <strong>to</strong> remove non-functional <strong>satellite</strong>s from their<strong>or</strong>iginal <strong>or</strong>bits, placing many of them in higher <strong>or</strong>bits by using the residual propellantin the secondary propulsion system at the end of its useful life. This maneuver isfrequently and appropriately called a ‗graveyard burn‘. It is also becoming thepractice in LEO missions <strong>to</strong> provide controlled re-entry in<strong>to</strong> the Earth‘s atmosphere.The reason f<strong>or</strong> this controlled re-entry approach is that uncontrolled re-entry can lead<strong>to</strong> vehicle break up, providing a hazard on the ground and adding <strong>to</strong> the problem ofspace debris hazard.This study has examined the GlobalStar <strong>satellite</strong> constellation in <strong>or</strong>der <strong>to</strong>provide a specific example related <strong>to</strong> a large population of high-value <strong>satellite</strong>s tha<strong>to</strong>ccupy a low Low Earth <strong>or</strong>bit Orbit and have the potential of becoming <strong>or</strong>bital spacedebris. Since the <strong>or</strong>iginal GlobalStar <strong>satellite</strong>s were launched, starting in 1999, withplanned useful lives of 7.5 years, the first generation of these <strong>satellite</strong>s are nowbecoming <strong>or</strong>bital debris. Presently, at least 11 <strong>satellite</strong>s have ceased operation in theGlobalStar constellation <strong>or</strong>bits, and the GlobalStar Communication Company hasbegun replacing its <strong>or</strong>iginal constellation <strong>satellite</strong>s with new second generationGlobalStar <strong>satellite</strong>s. The new second generation of GlobalStar <strong>satellite</strong>s are iscurrently being launched, six-at-a-time, starting in Oc<strong>to</strong>ber, 2010 20 . As the newsecond generation <strong>satellite</strong>s have replaced the first generation <strong>satellite</strong>s, GlobalStarhas adjusted the <strong>or</strong>bits of their non-functioning first-generation <strong>satellite</strong>s, placingthem in 2,000 km graveyard <strong>or</strong>bits. The graveyard <strong>or</strong>bits have reduced the riskassociated with non-functioning <strong>satellite</strong>s occupying primary <strong>or</strong>bits, but those<strong>satellite</strong>s will need <strong>to</strong> eventually be removed eventually. This thesis has developed astrategy f<strong>or</strong> removing those <strong>satellite</strong>s.


30CHAPTER 2IMPULSIVE ORBIT TRANSFER STRATEGIESPropulsion systems are employed <strong>to</strong> effect controlled changes in the <strong>or</strong>bit of aspacecraft. Orbit transfer maneuvers use directed thrust <strong>to</strong> accelerate (<strong>or</strong> decelerate)an <strong>or</strong>biting object, changing its inertial velocity (direction and <strong>or</strong> magnitude) so that atthe end of the propulsive maneuver, a different <strong>or</strong>bit results. These propulsivemaneuvers are employed <strong>to</strong> transfer spacecraft from their launch-vehicle-controlledinitial <strong>or</strong>bits <strong>to</strong> a different <strong>or</strong>bit. They are also employed <strong>to</strong> change the <strong>or</strong>bital plane,<strong>to</strong> circularize an <strong>or</strong>bit <strong>or</strong> <strong>to</strong> synchronize the <strong>or</strong>bit of one spacecraft either with respect<strong>to</strong> a fixed location on the Earth‘s surface <strong>or</strong> with respect <strong>to</strong> another spacecraft. Mos<strong>to</strong>rbital transfer operations utilize chemical propellants in <strong>or</strong>der <strong>to</strong> better-control <strong>or</strong>bitaladjustments. It is the task of mission planners <strong>to</strong> determine spacecraft propellant massallowances required <strong>to</strong> attain and maintain planned <strong>or</strong>bital configurations over thelifetime of the spacecraft. Orbital rendezvous with a specified spacecraft is one of themost demanding classes of spacecraft maneuvers and it is necessary <strong>to</strong> properlyestimate the propellant required f<strong>or</strong> these operations.2.1 Relative Motion in OrbitA rendezvous maneuver consists of a target vehicle and a chaser vehicle. Thetarget vehicle is the passive, non-maneuvering vehicle, already in a specific <strong>or</strong>bit. Thechaser vehicle is the active vehicle, perf<strong>or</strong>ming the maneuvers required <strong>to</strong> achieve anappropriately synchronized target vehicle <strong>or</strong>bit, and subsequently <strong>to</strong> overtake andactually rendezvous with the target vehicle. The space shuttle is used regularly as achase vehicle, rendezvousing with the International Space Station (ISS) which is thetarget vehicle.In the geocentric equa<strong>to</strong>rial frame, the position vec<strong>to</strong>r of the target vehicle is ⃗and the moving <strong>or</strong> relative frame of reference has its <strong>or</strong>igin located at a specificreference point on the target vehicle, as shown in Figure 2.1. The x-axis is directedalong ⃗, the outward radial vec<strong>to</strong>r <strong>to</strong> the target. The y axis is perpendicular <strong>to</strong> ⃗ andpoints in the direction of the target <strong>satellite</strong>‘s local h<strong>or</strong>izon. The x and y axes theref<strong>or</strong>elie in the target‘s <strong>or</strong>bital plane, and the z axis is n<strong>or</strong>mal <strong>to</strong> that plane 21 .


31Figure 2.1 Moving Frame Attached <strong>to</strong> Target S/C from which Chaser S/C Observed.The angular velocity of the moving frame which contains the x,y z axes,attached <strong>to</strong> the target vehicle, is just the angular velocity of the position vec<strong>to</strong>r ⃗, andcan be written:⃗⃗ ⃗ ⃗ ( ) ̂ ( ) ̂ ⃗⃗ (2.1)Hence, the angular velocity vec<strong>to</strong>r from equation Equation (2.1) is:⃗⃗⃗ ⃗⃗(2.2)The angular acceleration of the co<strong>or</strong>dinate system is gotten achieved by taking thetime derivative of equation Equation (2.2):⃗⃗( ⃗ ̇ ⃗ ⃗ ⃗) ̇ ⃗( ̇ ⃗ ⃗) (2.3)but


32⃗ ̇ ⃗ ⃗ ⃗ (2.4)and the acceleration of the target vehicle is⃗⃗ ̇ ⃗. (2.5)In addition,⃗⃗ ̇ ⃗ . ⃗⃗/ ( ⃗⃗ ⃗⃗) (2.6)Finally, after manipulating equations Equations (2.2), (2.4), and (2.6), the angularacceleration can be represented as:⃗⃗( ⃗ ⃗⃗) ⃗⃗ (2.7)At first, it may be hard <strong>to</strong> visualize the motion of one spacecraft relative <strong>to</strong>another in <strong>or</strong>bit. Figure 2.2 21 can simplify that challenge. In Figure 2.2, two <strong>or</strong>bits areshown and <strong>or</strong>bit Orbit 1 is a circular <strong>or</strong>bit while <strong>or</strong>bit Orbit 2 is elliptical with aneccentricity of 0.125. The two <strong>or</strong>bits have the same semi-maj<strong>or</strong> axes (a) and f<strong>or</strong> thisreason their <strong>or</strong>bital periods are the same. A co-moving frame is shown attached <strong>to</strong>―observer Observer A‖ in the circular <strong>or</strong>bit (number 1). At epoch Epoch I, spacecraftSpacecraft B, in elliptical Elliptical <strong>or</strong>bit Orbit 2, is directly below the observerObserver A <strong>satellite</strong>. In other w<strong>or</strong>ds, A must draw an arrow in the negative x-direction<strong>to</strong> point at the position vec<strong>to</strong>r locating B in the lower <strong>or</strong>bit. Figure 2.2 shows eightdifferent epochs (I, II, III, . . .), equally spaced around the circular <strong>or</strong>bit, in <strong>or</strong>der <strong>to</strong>visualize the relative position of the two spacecraft with respect <strong>to</strong> each other. Ofcourse, A‘s observation frame is rotating, because the x-axis must always be directedaway from the earth. Observer A cannot sense this rotation and rec<strong>or</strong>ds the set ofobservations in their (<strong>to</strong> them) ―fixed‖ xy co<strong>or</strong>dinate system, as shown at the bot<strong>to</strong>mof the Figure 2.2. Coasting at a unif<strong>or</strong>m speed along the circular <strong>or</strong>bit, A sees the othervehicle <strong>or</strong>biting them clockwise in a s<strong>or</strong>t of bean-shaped path. The distance betweenthe two spacecraft, in this case, never becomes so great that the earth Earth intervenes.


33Figure 2.2 Relative Motion of Elliptically Orbiting Spacecraft B and CircularlyOrbiting Spacecraft A.2.2 Linearization of the Equations of Relative Motion in OrbitFigure 2.3 illustrates two <strong>satellite</strong>s in Earth‘s <strong>or</strong>bit trajec<strong>to</strong>ries. ⃗⃗⃗⃗ is theposition vec<strong>to</strong>r of the target vehicle and ⃗ is the position vec<strong>to</strong>r of the chase vehicle inthe inertial co<strong>or</strong>dinate frame.


34Figure 2.3 Position Vec<strong>to</strong>r of Chase Vehicle Relative <strong>to</strong> Target Vehicle.Also wWe can can also define the position vec<strong>to</strong>r of the chase vehicle relative <strong>to</strong> thetarget vehicle using ∆ ⃗, given by:⃗ ⃗⃗⃗⃗+∆ ⃗ (2.8)The chase vehicle acceleration can be written:⃗ ̈⃗(2.9)where r = ‖ ⃗‖. Substituting equation Equation (2.8) in<strong>to</strong> Eequation (2.9) yields theacceleration difference between the chase vehicle and the target vehicle:∆ ⃗ ̈⃗ ̈⃗∆ ⃗(2.10)


35The symbol ∆ is used <strong>to</strong> represent the relative position vec<strong>to</strong>r, and has a magnitudewhich is very small compared <strong>to</strong> the magnitude of the other position vec<strong>to</strong>rs which are⃗⃗⃗⃗ and ⃗, so that∆, (2.11)where ∆r = ‖∆ ⃗‖ and r 0 = ‖ ⃗ ‖.We can simplify equation Equation (2.10) by making use of the fact that ‖∆ ⃗‖ is verysmall,⃗ ⃗ ( ⃗⃗⃗⃗ ∆ ⃗) ( ⃗⃗⃗⃗ ∆ ⃗) ⃗⃗⃗⃗ ⃗⃗⃗⃗ ⃗⃗⃗⃗ ∆ ⃗ ∆ ⃗ ∆ ⃗Since ⃗⃗⃗⃗ ⃗⃗⃗⃗ and ∆ ⃗ ∆ ⃗ ∆ yields:6⃗⃗⃗⃗ ∆ ⃗( ∆ ) 7We can neglect the quadratic term in brackets by virtue of equation Equation (2.11):.⃗⃗⃗⃗⃗ ∆ ⃗/ (2.12)We will can neglect all higher <strong>or</strong>der powers of ∆ ⁄ . Since ( )⁄ :.⃗⃗⃗⃗⃗ ∆ ⃗/⁄(2.13)Using the binomial the<strong>or</strong>em and neglecting higher <strong>or</strong>der terms4⃗⃗⃗⃗ ∆ ⃗ 5⁄( ) 4 ⃗⃗⃗⃗ ∆ ⃗ 5After some manipulation:( ⃗⃗⃗⃗ ∆ ⃗)⁄which can be written:


36⃗⃗⃗⃗ ∆ ⃗ (2.14)Substituting equation Equation (2.14) in<strong>to</strong> the relative acceleration equation Equation(2.10), we get∆ ⃗ ̈⃗ ̈ ( ⃗⃗⃗⃗ ∆ ⃗) ( ⃗ ∆ ⃗)∆ ⃗ ̈⃗ ̈ ( ⃗ ∆ ⃗ ( ⃗⃗⃗⃗ ∆ ⃗)( ⃗ ∆ ⃗))Again neglecting higherneglecting higher <strong>or</strong>der terms, we get:∆ ⃗ ̈⃗ ̈ . ⃗ ∆ ⃗ ( ⃗⃗⃗⃗ ∆ ⃗) ⃗ / (2.15)But the acceleration vec<strong>to</strong>r f<strong>or</strong> the target vehicle is:⃗ ̈⃗Finally we get:∆ ⃗ ̈ .∆ ⃗ ( ⃗⃗⃗⃗ ∆ ⃗) ⃗ /. (2.16)Equation (2.16) is the linearized version of equation Equation (2.9), which governsthe motion of the chase vehicle with respect <strong>to</strong> the target vehicle. The expression islinear because ∆ ⃗ appears only in the numera<strong>to</strong>r and only first <strong>or</strong>der powers of ∆ havebeen included.2.3 Clohessy-Wiltshire EquationsFigure 2.4 illustrates an attached moving frame of reference xyz relative <strong>to</strong> thetarget spacecraft. This figure is similar <strong>to</strong> Figure 2.3, with the difference being that ∆ ⃗is restricted by the approximation (Eq. 2.11). The <strong>or</strong>igin of the moving system islocated on the target spacecraft. The x axes lies along ⃗⃗⃗⃗ and unit vec<strong>to</strong>r ̂, can bedefined:


̂37⃗⃗⃗⃗. (2.17)From Figure 2.4, the y axes is in the direction of the local h<strong>or</strong>izon, and the z axes isthe n<strong>or</strong>mal <strong>to</strong> the target spacecraft <strong>or</strong>bital plane described using the right hand rule,where ̂ ̂ ̂. The inertial angular velocity of the moving frame of reference is ⃗⃗,and the inertial angular acceleration is ⃗⃗ ̇ .Acc<strong>or</strong>ding <strong>to</strong> the relative acceleration f<strong>or</strong>mula, we have:⃗ ̈⃗⃗⃗⃗ ̈⃗⃗ ̇ ∆ ⃗ ⃗⃗ ( ⃗⃗ ∆ ⃗) ⃗⃗ ∆ ⃗ ∆ ⃗ (2.18)where the relative position, relative velocity and relative acceleration are given by,respectively:∆ ⃗ ∆ ̂ ∆ ̂ ∆ ̂ (2.19a)∆ ⃗ ∆ ̇ ̂ ∆ ̇ ̂ ∆ ̇ ̂ (2.19b)∆ ⃗ ∆ ̈ ̂ ∆ ̈ ̂ ∆ ̈ ̂ (2.19c)


38Figure 2.4 Co-moving Clohessy-Wiltshire Frame.F<strong>or</strong> simplicity, we assume that the <strong>or</strong>bit of the target spacecraft is circular (e=0) sothat the angular acceleration is equal <strong>to</strong> zero . ⃗⃗ ̇/. Using this restriction, <strong>to</strong>getherwith equation Equation (2.8), and substitution in<strong>to</strong> equation Equation (2.18) yields:∆ ⃗ ̈ ⃗⃗ ( ⃗⃗ ∆ ⃗) ⃗⃗ ∆ ⃗ ∆ ⃗ .Applying the vec<strong>to</strong>r triple cross product identity rule <strong>to</strong> the first term on the right handside of equation, yields:∆ ⃗ ̈ ⃗⃗( ⃗⃗ ∆ ⃗) ∆ ⃗⃗ ∆ ⃗ ∆ ⃗ . (2.20)Since the target spacecraft <strong>or</strong>bit is circular, we can write the angular velocity of thetarget spacecraft ( ⃗⃗) as:⃗⃗ ̂ (2.21)


39where n is the mean motion of target spacecraft, and is constant. Thus:⃗⃗ ∆ ⃗ ̂ (∆ ̂ ∆ ̂ ∆ ̂) ∆ (2.22)and⃗⃗ ∆ ⃗̂ (∆ ̇ ̂ ∆ ̇ ̂ ∆ ̇ ̂) ∆ ̇ ̂ ∆ ̇ ̂ (2.23)Substituting equations Equations (2.21), (2.22) and (2.23) along with eEquations(2.19), in<strong>to</strong> eEquation (2.20) yields:∆ ⃗ ̈ ̂( ∆ ) (∆ ̂ ∆ ̂ ∆ ̂) ( ∆ ̇ ̂ ∆ ̇ ̂) ∆ ̈ ̂ ∆ ̈ ̂ ∆ ̈ ̂Finally, collecting terms yields:∆ ⃗ ̈ ( ∆ ∆ ̇ ∆ ̈ ) ̂ ( ∆ ∆ ̇ ∆ ̈ ) ̂ ∆ ̈ ̂ (2.24)This expression gives the components of the chaser‘s absolute relative accelerationvec<strong>to</strong>r in terms of quantities that can be measured in the moving reference frame.Since the target spacecraft <strong>or</strong>bit is circular, the mean motion of the targetspacecraft is given by:√ √ ,and theref<strong>or</strong>e:. (2.25)Recalling equations Equations (2.17) and (2.19a), we also note that:⃗ ∆ ⃗ ( ̂) (∆ ̂ ∆ ̂ ∆ ̂) ∆ (2.26)Substituting equations Equations (2.19a), (2.25) and (2.26) in<strong>to</strong> the relativeacceleration eEquation (2.16) yields:∆ ⃗ ̈ 0∆ ̂ ∆ ̂ ∆ ̂ ( ̂)1 ∆ ̂ ∆ ̂ ∆ ̂ (2.27)


40Combining equations Equations (2.22) and (2.27), we obtain:( ∆ ∆ ̇ ∆ ̈) ̂ ( ∆ ∆ ̇ ∆ ̈) ̂ ∆ ̈ ̂ ∆ ̂ ∆ ̂ ∆ ̂Upon collecting terms on the left-side of the equation, we get:(∆ ̈ ∆ ∆ ̇ ) ̂ (∆ ̈ ∆ ̇ ) ̂ (∆ ̈ ∆ ) ̂That is:∆ ̈ ∆ ∆ ̇ (2.28a)∆ ̈ ∆ ̇ (2.28b)∆ ̈ ∆ (2.28c)F<strong>or</strong>matted: Font: 12 ptF<strong>or</strong>matted: Font: 14 ptF<strong>or</strong>matted: Font: 12 ptF<strong>or</strong>matted: Font: 14 ptF<strong>or</strong>matted: Font: 12 ptEquations (2.28a), (2.28b) and (2.28c) are the Clohessy-Wiltshire (CW) equations. Whenusing these equations, we will refer <strong>to</strong> the moving frame of reference in which they werederived as the Clohessy-Wiltshire frame. Equations The 2.28 equation(2.28) group is are aset of coupled, second <strong>or</strong>der differential equations with constant coefficients. The initialconditions are:At , ∆ ∆ ∆ ∆ ∆ ∆∆ ̇ ∆ ̇ ∆ ̇ ∆ ̇ ∆ ̇ ∆ ̇ (2.29)From equation Equation (2.28b):(∆ ̇ ∆ )which means:∆ ̇∆We find the constant by evaluating the left hand side of the equation at .Theref<strong>or</strong>e:F<strong>or</strong>matted: Font: 12 pt∆ ̇ ∆ ∆ ̇ ∆so that:


41∆ ̇ ∆ ̇ (∆ ∆ ) (2.30)Substituting this result in<strong>to</strong> equation Equation (2.28a) yields:∆ ̈ ∆ ,∆ ̇ (∆ ∆ )-which, upon rearrangement, becomes:F<strong>or</strong>matted: Font: 12 pt∆ ̈ ∆ ∆ ̇ ∆ (2.31)The solution of this differential equation is:∆ ∆ ̇ ∆ (2.32)Differentiating this equation once with respect <strong>to</strong> time, we obtain:∆ ̇ (2.33)Evaluating equation (2.32) atwe find:F<strong>or</strong>matted: Font: 12 pt∆ ∆ ̇ ∆ → ∆∆ ̇Evaluating equation (2.33) atwe find:F<strong>or</strong>matted: Font: 12 pt∆ ̇→∆ ̇Substituting these values f<strong>or</strong> A and B in<strong>to</strong>B in<strong>to</strong> equation Equation (2.32) leads <strong>to</strong>:∆∆ ̇( ∆∆ ̇ ) ∆ ̇ ∆which, upon combining terms, becomes:∆ ( )∆ ∆ ̇ ( )∆ ̇ (2.34)Theref<strong>or</strong>e,∆ ̇ ∆ ∆ ̇ ∆ ̇ (2.35)Substituting equation Equation (2.34) in<strong>to</strong> Eequation (2.30) yields:


42∆ ̇ ∆ ̇ [ ( )∆ ∆ ̇ ( )∆ ̇ ]which simplifies <strong>to</strong> become:∆ ̇ ( )∆ ∆ ̇ ( )∆ ̇ (2.36)Integrating this expression with respect <strong>to</strong> time, we find that:∆ . / ∆ ∆ ̇ . / ∆ ̇ (2.37)Evaluating ∆y atyields:F<strong>or</strong>matted: Font: 12 pt∆ ∆ ̇ → ∆ ∆ ̇Substituting this value f<strong>or</strong> C in<strong>to</strong> equation Equation (2.37), we get:∆ ( )∆ ∆ ( )∆ ̇ . / ∆ ̇ (2.38)Finally, the solution of equation Equation (2.28c) is:∆ (2.39)so that∆ ̇ (2.40)We evaluate the two expressions at<strong>to</strong> obtain the constants of integration:F<strong>or</strong>matted: Font: 12 pt∆∆ ̇Putting these values f<strong>or</strong> D and E back in<strong>to</strong> equation Equation (2.38) and Eequation(2.40) yields:∆ ∆ ∆ ̇ (2.41)∆ ̇ ∆ ∆ ̇ (2.42)


43Now that we have finished solving the Clohessy-Wiltshire equations, we change ournotation, denoting the x, y and z components of relative velocity in the moving frameas ∆ , ∆ and ∆ , respectively. That is:∆ ∆ ̇ ∆ ∆ ̇ ∆ ∆ ̇The initial conditions f<strong>or</strong> the relative velocity components are then written:∆ ∆ ̇ ∆ ∆ ̇ ∆ ∆ ̇Using this notation we write equations Equations (2.34), (2.35), (2.36), (2.38), (2.41)and (2.42) as∆ ( )∆ ∆ ( )∆ (2.43a)∆ ∆ ∆ ∆ (2.43b)∆ ( )∆ ∆ ( )∆ (2.43c)∆ ( )∆ ∆ ( )∆ . / ∆ (2.43d)∆ ∆ ∆ (2.43e)∆ ∆ ∆ (2.43f)Finally, introducing matrix notation <strong>to</strong> define the relative position and velocityvec<strong>to</strong>rs:*∆ ⃗( )+∆ ( ){ ∆ ( )} *∆ ⃗( )+∆ ( ){ ∆ ( )}∆ ( )∆ ( )and their initial values (at ):∆*∆ ⃗ + { ∆∆∆} *∆ ⃗ + { ∆∆}.


44Observe that we have dropped the subscript of relative (rel) introduced inequation Equation (2.19) because it is non-essential in rendezvous analysis. Equations(2.43) can be represented m<strong>or</strong>e compactly in matrix notation as:*∆ ⃗( )+ [ ⃗⃗ ( )]*∆ ⃗ + [ ⃗⃗ ( )]*∆ ⃗ + (2.44a)*∆ ⃗( )+ [ ⃗⃗ ( )]*∆ ⃗ + [ ⃗⃗ ( )]*∆ ⃗ + (2.44b)where the Clohessy-Wiltshire matrices are:[ ⃗⃗ ( )] [ ( ) ] (2.45a)( )[ ⃗⃗ ( )]( ) ( )(2.45b)[][ ⃗⃗ ( )] [ ( ) ] (2.45c)[ ⃗⃗ ( ) [ ]] (2.45d)2.4 Two-Impulse Rendezvous ManeuversThe typical rendezvous problem is shown in Figure 2.5. At time (theinstant preceding t=0), the position ∆ ⃗ and ∆ ⃗ of the chase spacecraft relative <strong>to</strong>the target are is known. At t=0 an impulsive maneuver instantaneously changes therelative velocity <strong>to</strong> ∆ ⃗ at t=0 + (the instant after t=0). The components of ∆ ⃗ areshown in Figure 2.5.


45Figure 2.5 Rendezvous Trajec<strong>to</strong>ry of a Target Spacecraft in the Neighb<strong>or</strong>hood of ItsChase Spacecraft.We must determine the values of ∆ , ∆ , ∆ , at the beginning of therendezvous trajec<strong>to</strong>ry, so that the chase spacecraft will arrive at the target in aspecified time t f . The delta-v (∆V) required <strong>to</strong> place the chase spacecraft on therendezvous trajec<strong>to</strong>ry is:*∆ + {∆ ⃗ } *∆ ⃗ + ∆{ ∆∆∆} { ∆∆} (2.46)At time t f ,, the chase spacecraft arrives at the target spacecraft (at the <strong>or</strong>igin of theco-moving frame), which means {∆ ⃗ } {∆ ⃗( )} * +. Evaluating equationEquation (2.44a) at t f , we find:


46* + [ ⃗⃗ ( )]*∆ ⃗ + [ ⃗⃗ ( )]*∆ ⃗ + (2.47)Solving this f<strong>or</strong> {∆ ⃗} yields:{∆ ⃗ } [ ⃗⃗ ( )] [ ⃗⃗ ( )]*∆ ⃗ + (2.48)where [ ⃗⃗ ( )] is the matrix inverse of [ ⃗⃗ ( )]. We know the velocity ∆ ⃗ atthe beginning of the rendezvous path; thus substituting equation (2.48) in<strong>to</strong>equation Equation (2.44b) we obtain the velocity ∆ ⃗ at which point the chasespacecraft arrives at target spacecraft, when :{∆ ⃗ } [ ⃗⃗ ( )]*∆ ⃗ + [ ⃗⃗ ( )]{∆ ⃗ }{∆ ⃗ } [ ⃗⃗ ( )]*∆ ⃗ + [ ⃗⃗ ( )] . [ ⃗⃗ ( )] [ ⃗⃗ ( )]*∆ ⃗ +/Simplifying, we get:{∆ ⃗ } .[ ⃗⃗ ( )] [ ⃗⃗ ( )][ ⃗⃗ ( )] [ ⃗⃗ ( )]/ *∆ ⃗ + (2.49)Obviously, an impulsive delta-v (∆V) maneuver is required at<strong>to</strong> bring the chasespacecraft <strong>to</strong> rest relative <strong>to</strong> target spacecraft (∆ ⃗ ):{∆ ⃗ } {∆ ⃗ } {∆ ⃗ } * + {∆ ⃗ } {∆ ⃗ } (2.50)In equations Equations (2.46) and (2.50) we have employed differences betweenrelative velocities <strong>to</strong> calculate delta-v (∆V), which is the difference in absolutevelocities. To show that this is valid,⃗ ⃗ ⃗⃗ ⃗ ⃗ (2.51a)⃗ ⃗ ⃗⃗ ⃗ ⃗ (2.51b)Since the target spacecraft is passive, the impulsive maneuver has no effect on itsstate of motion, which means ⃗ ⃗ and ⃗⃗ ⃗⃗ . Furtherm<strong>or</strong>e, by assumingimpulsive maneuvers, there is no change in the position, ( ⃗ ⃗ ). It followsfrom equations Equation (2.51) that:


⃗ ⃗ ⃗ ⃗ <strong>or</strong> ∆ ⃗ ∆ ⃗ (2.52)47


48CHAPTER 3DEVELOPMENT OF ∆V BUDGETS FOR REPAIRING ORREMOVING GLOBALSTAR SATELLITES3.1 Problem F<strong>or</strong>mulationCurrently, there are eleven non-functional <strong>satellite</strong>s in the GlobalStarconstellation. The <strong>or</strong>bital tracks of the eleven <strong>satellite</strong>s are depicted in Figure 3.1,where it is noted that all of the non-functional <strong>satellite</strong>s have semi-maj<strong>or</strong> axesbetween 8,132 and 8,521 km and right ascension of ascending nodes (RAAN (Ω))between 57 and 270 degrees. Their NORAD identifiers and <strong>or</strong>bital characteristics aresummarized in Table 3.1.Figure 3.1 Non-functional GlobalStar Satellites Orbits.


49Table 3.1 Orbital Characteristics of Non-functional GlobalStar Satellites.NORAD IDSEMI-MAJOR AXES(km)25164U 8232.5725964U 8167.0125874U 8132.0825853U 8334.18Ω(Degree)57.94266.04375.73681.12125306U 8221.30 90.959NORAD IDSEMI-MAJOR AXES(km)25872U 8372.1025885U 8343.9825771U 8475.2325886U 8405.3125851U 8521.6525308U 8156.13Ω(Degree)172.905179.299189.301195.848220.276270.261The primary goal of this study has been <strong>to</strong> develop specifications f<strong>or</strong> a set ofsmall dexterous servicing <strong>satellite</strong>s capable of refueling, <strong>repair</strong>ing <strong>or</strong> de-<strong>or</strong>bitingGlobalStar <strong>satellite</strong>s. This type of spacecraft has been examined in other studies 22,23 .F<strong>or</strong> the purposes of the present study, the spacecraft will be called Satellite Re-<strong>or</strong>biterSpacecraft (SRS) and the perf<strong>or</strong>mance requirements will be developed f<strong>or</strong> the SRSsystem in terms of optimal altitude and ephemeras characteristics, assuming that theSRS elements are carried in<strong>to</strong> <strong>or</strong>bit and deployed from a mother ship. In that way, itshould be possible <strong>to</strong> minimize overall SRS system size and operating costs f<strong>or</strong>servicing the 11 non-functional GlobalStar <strong>satellite</strong> example. In addition, goals of thisresearch include:1. Determination of SRS maneuvering requirements and acceptable err<strong>or</strong>allowances f<strong>or</strong> au<strong>to</strong>nomous rendezvous and docking with targeted GlobalStar<strong>satellite</strong>s,2. Capturing (attaching <strong>to</strong>) a non-functional GlobalStar <strong>satellite</strong> with SRS‘srobotic manipula<strong>to</strong>rs, and3. Determination of system requirements needed <strong>to</strong> propel a non-functionalGlobalStar <strong>satellite</strong> in<strong>to</strong> a predictable de-<strong>or</strong>bit trajec<strong>to</strong>ry.As shown in Table 3.1, the non-functional GlobalStar <strong>satellite</strong>s can be dividedroughly in<strong>to</strong> two separate <strong>or</strong>bital subsets, based on their right ascension of ascending


50nodes (RAAN <strong>or</strong> Ω)—five <strong>satellite</strong>s fall within 57° < < 91°, and six <strong>satellite</strong>s arewithin 172° < < 271°. Referring <strong>to</strong> Figure 3.1, it is apparent that the two <strong>or</strong>bital<strong>satellite</strong> groups may have evolved from their initial deployments. GlobalStar <strong>satellite</strong>s25164U, 25964U, 25874U, 25853U and 25306U (s between 57° and 90°) weredeployed from one multiple-<strong>satellite</strong> launch, and GlobalStar <strong>satellite</strong>s 25872U,25885U, 25771U, 25886U, 25851U and 25308U (s between 172° and 270°) appear<strong>to</strong> have been deployed from another multiple-<strong>satellite</strong> launch. A MatLab program hasbeenwas used <strong>to</strong> represent the NORAD <strong>or</strong>bits f<strong>or</strong> some aspects of the analysis thatfollows.In <strong>or</strong>der <strong>to</strong> bound this study, it has been assumed that the mother ship and itsassociated SRS fleet have been placed in <strong>or</strong>bit utilizing the same Soyuz launchvehicle system that has been employed f<strong>or</strong> the multiple-<strong>satellite</strong> GlobalStar launches.Thus, each SRS element will be a small <strong>satellite</strong>, deployed from the <strong>or</strong>biting mothership with overall mass and dimensional constraints derived from existing GlobalStarlaunch specifications. On that basis, an optimum number of SRS elements can beestablished in terms of effectingaffecting the largest number of rendezvous and<strong>repair</strong>/de-<strong>or</strong>bit s<strong>or</strong>ties with a minimum number of Earth launches. Obviously, thepropellant requirements, both f<strong>or</strong> <strong>or</strong>bital rendezvous and de-<strong>or</strong>bit, when necessary,represents the most imp<strong>or</strong>tant design driver. Since it is not possible <strong>to</strong> differentiate<strong>repair</strong>able GlobalStars from recoverable GlobalStars a pri<strong>or</strong>i, this study has assumedthat none of the non-functioning GlobalStars can be <strong>repair</strong>ed as a ―w<strong>or</strong>st case‖baseline. As a consequence, a main purpose of this study has been <strong>to</strong> determineoptimal propellant allowances <strong>to</strong> de-<strong>or</strong>bit the non-functional GlobalStar <strong>satellite</strong>s. Onthat basis, it was necessary <strong>to</strong> estimate the velocity increments required f<strong>or</strong> the entiresequence of operations, starting from deployment from the mother ship, thenproceeding through <strong>or</strong>bital rendezvous, <strong>satellite</strong> capture and subsequently de-<strong>or</strong>bitingnon-<strong>repair</strong>able GlobalStar <strong>satellite</strong>s.3.2 ∆V Calculations f<strong>or</strong> Rendezvous and De-<strong>or</strong>biting Maneuvers3.2.1 ∆V Rendezvous Maneuvers of SRS with Non-functional GlobalStarSatellite


51Assuming that there are two distinct groups of non-functional GlobalStar<strong>satellite</strong>s, rendezvous calculations have been made assuming that the mother ship wasplaced in an <strong>or</strong>bit that facilitated a minimum V propulsive requirement f<strong>or</strong> one SRSunit in each <strong>satellite</strong> subset. By being launched in<strong>to</strong> an optimal circular <strong>or</strong>bit relative<strong>to</strong> the desired rendezvous <strong>or</strong>bit f<strong>or</strong> the selected GlobalStar <strong>satellite</strong>, a minimumpropellant rendezvous can be executed. In <strong>or</strong>der <strong>to</strong> develop an optimal strategy, theanalysis has considered each of the non-functional GlobalStar <strong>satellite</strong>s in each subset<strong>to</strong> be the initial rendezvous candidate. In that way the optimum mother ship <strong>or</strong>bitcould can be selected on the basis of minimizing the <strong>to</strong>tal V requirements f<strong>or</strong> all ofthe remaining GlobalStar <strong>satellite</strong>s in that suite (subset).All of the GlobalStar <strong>satellite</strong> <strong>or</strong>bits are nearly circular. Furtherm<strong>or</strong>e, when themother ship is placed in its initial <strong>or</strong>bit, it is desirable <strong>to</strong> place the mother ship in aslightly different <strong>or</strong>bit than the initial target GlobalStar in <strong>or</strong>der <strong>to</strong> minimize risk. Byplacing the mother ship in a circular <strong>or</strong>bit sharing the <strong>or</strong>bital plane containing thetarget <strong>satellite</strong>, a low-V rendezvous can occur—provided that the mother ship‘s <strong>or</strong>bitis synchronized with the target <strong>satellite</strong> <strong>or</strong>bit. Furtherm<strong>or</strong>e, by deploying theremaining SRS vehicles from a circular mother ship <strong>or</strong>bit rather than the slightlyelliptic GlobalStar <strong>or</strong>bits, synchronization of the other SRS spacecraft with theremaining GlobalStar <strong>satellite</strong>s f<strong>or</strong> rendezvous can be controlled m<strong>or</strong>e easily. Thesemi-maj<strong>or</strong> axes of the subsequent SRS deployments can be controlled using the Vburn, and by waiting an appropriate number of (mother ship and target GlobalStar)<strong>or</strong>bits and determining the time when the propulsive kick is <strong>to</strong> be completed, it ispossible <strong>to</strong> place the SRSs in the desired rendezvous <strong>or</strong>bits with the desired separationdistances f<strong>or</strong> initiating rendezvous.Since all of the remaining SRS vehicles were <strong>to</strong> be deployed from the samemother ship <strong>or</strong>bit, it was only necessary <strong>to</strong> determine the V requirements f<strong>or</strong> each ofthe remaining SRS vehicles, starting from the selected mother ship <strong>or</strong>bit. The V setswere computed in the calculation <strong>or</strong>der, shown in Figures 3.2 and 3.3.


25164U25872U25885U25964U25771U25874U25886U25853U25851U25306U25308U52•25964U•25874U•25853U•25306U•25164U•25874U•25853U•25306U•25164U•25964U•25853U•25306U•25164U•25964U•25874U•25306U•25164U•25964U•25874U•25853UFigure 3.2 Sequence of V Requirement Calculations f<strong>or</strong> The the Five GlobalStarSuite.•25885U•25771U•25886U•25851U•25308U•25872U•25771U•25886U•25851U•25308U•25872U•25885U•25886U•25851U•25308U•25872U•25885U•25771U•25851U•25308U•25872U•25885U•25771U•25886U•25308U•25872U•25885U•25771U•25886U•25851UFigure 3.3 Sequence of V Requirement Calculations f<strong>or</strong> The the Six GlobalStarSuite.Non-functional GlobalStar <strong>satellite</strong> positions and classical <strong>or</strong>bital elements[semi-maj<strong>or</strong> axes (a), eccentricity (e), inclination angle (i), right ascension ofascending nodes (Ω), argument of periapsis (w) and true anomaly (θ) ] are knownfrom their NORAD data. The NORAD data f<strong>or</strong> each non-functional GlobalStar<strong>satellite</strong> are shown in Table 3.2. In an actual multiple <strong>satellite</strong> recovery and/<strong>or</strong> de<strong>or</strong>bitmission, after the mother ship carrying the SRS set was placed in<strong>to</strong> its optimal <strong>or</strong>bitand the first rendezvous and <strong>repair</strong> operation was completed, the <strong>or</strong>bital data f<strong>or</strong> theremaining GlobalStar targets would be updated in <strong>or</strong>der <strong>to</strong> set up the second SRSrendezvous and <strong>repair</strong> operation, and so on. In that way, the sequence of operationscan be adjusted <strong>to</strong> accommodate the various inspection, <strong>repair</strong> and/<strong>or</strong> de<strong>or</strong>bi<strong>to</strong>perations, minimizing ground station manpower and operational costs, whilerecognizing that the restricted two-body approach inc<strong>or</strong>p<strong>or</strong>ated in this optimizationprocess cannot predict actual <strong>or</strong>bits over extended periods of time. The actual


53optimization process can only be simulated in this study example by using NORAD<strong>or</strong>bital data spread over a period of time characterizing a complete SRS sequence.That approach allows realistic actual adjustments in <strong>or</strong>bits <strong>to</strong> occur.When this research <strong>to</strong>pic was selected, the public was unaware of GlobalStar‘sdecision <strong>to</strong> place their non-functioning <strong>satellite</strong>s in parking <strong>or</strong>bits where theyrepresented a minimum risk <strong>to</strong> their other functioning <strong>satellite</strong>s. As mentioned inChapter 1, every <strong>or</strong>biting object in the space environment can be hazardous <strong>to</strong>functional <strong>satellite</strong>s. These non-functional <strong>satellite</strong>s could trigger a nearly continuouschain reaction collision event in near-Earth <strong>or</strong>bital space. This effect is known as theKessler Syndrome, <strong>or</strong> effect, as proposed by NASA scientist Donald J. Kessler in1978. It is a scenario in which the density of objects in Low Earth Orbit (LEO) is highenough that collisions between objects could cause a cascade – each collisiongenerating debris which increases the likelihood of further collisions 24 . However, insupp<strong>or</strong>t of the present active removal research <strong>to</strong>pic, it was announced recently thatCanadian Robotics was expl<strong>or</strong>ing a rendezvous and <strong>repair</strong> partnership that wouldenable a commercial <strong>satellite</strong> opera<strong>to</strong>r <strong>to</strong> extend functional <strong>satellite</strong> lifetimes using anapproach similar <strong>to</strong> the type proposed here 25 . A robotic servicer <strong>satellite</strong> is beingdesigned <strong>to</strong> add in-<strong>or</strong>bit refueling and simple <strong>repair</strong>s <strong>to</strong> existing commercial <strong>satellite</strong>fleets. The robotic servicer <strong>satellite</strong> could add years of life <strong>to</strong> valuable spacecraft thatwould otherwise be decommissioned f<strong>or</strong> lack of fuel. The servicer also will be able <strong>to</strong>perf<strong>or</strong>m some <strong>repair</strong>s, possibly including releasing snagged solar arrays.As a result, this thesis should be considered as developing an appropriate<strong>methodology</strong> f<strong>or</strong> recovering <strong>or</strong> removing specific sets of non-functioning <strong>satellite</strong>sutilizing a minimum risk and minimum cost (based on launch mass requirements)<strong>methodology</strong>.Examination of the NORAD two-line ephemerus element data sets showedthat all 11 of the non-functional <strong>satellite</strong>s had been maneuvered out of their regularcommunications netw<strong>or</strong>k <strong>or</strong>bits. This presented a problem, since the <strong>methodology</strong>developed in this thesis is based on using efficient, low-overhead <strong>or</strong>bital rendezvoussynchronization timing schemes. The simple synchronization timing schemes basedon the restricted two-body model developed in Appendix A, are of limited accuracysince they do n‘t not include <strong>or</strong>bital perturbations resulting from gravity variations,


54aerodynamic drag, third-body perturbations, and solar pressure. However, as m<strong>or</strong>esophisticated simulations have shown (<strong>AGI</strong>‘s STK software package has been used inthis thesis), inclusion of all of the modeled <strong>or</strong>bital perturbation effects does notreplicate precisely the actual NORAD data f<strong>or</strong> long (several days <strong>or</strong> weeks) periods oftime. The low-overhead approach is most useful if the current NORAD data wereused in the actual SRS <strong>or</strong>bit change and rendezvous calculations. However, this thesiscan only simulate that process by using his<strong>to</strong>rical NORAD data <strong>to</strong> model theGlobalStar servicing and removal operations. Since the 11 th non-functional <strong>satellite</strong> inthe data set contained in Table 3.1 was maneuvered in<strong>to</strong> its present <strong>or</strong>bit in February,2011, his<strong>to</strong>rical data can only go back <strong>to</strong> that date in <strong>or</strong>der <strong>to</strong> model the overallapproach. On that basis, it has been assumed that the mother ship was launched in<strong>to</strong>its initial <strong>or</strong>bit on February 11, 2011. The reference NORAD data set f<strong>or</strong> 11 February2011, is contained in Table 3.4.NORAD data f<strong>or</strong> all non-functional GlobalStar <strong>satellite</strong>s between 11 February2011 and 11 April of 2011, have been used <strong>to</strong> represent the overall approach.Eccentricity (e), inclination angle (i), right ascension of ascending nodes (Ω) andargument of periapsis (w) can be read directly from the two-line ephemerus NORADdata, but semi-maj<strong>or</strong> axes (a) and true anomaly (θ) were needed in the rendezvouscalculations, and a MatLab program was written <strong>to</strong> utilize the NORAD data <strong>to</strong>determine all of the classical <strong>or</strong>bital elements * .* Also, the NORAD data contain the date and time when the data f<strong>or</strong> each GlobalStar <strong>satellite</strong> wasrec<strong>or</strong>ded. Table 3.4 represents the February 11 th ,11 th , 2011 data. The repeating ―11042‖ digital entriesin the first row of data f<strong>or</strong> each <strong>satellite</strong> indicate that the NORAD data were taken on the 42 th day of2011. The 42 th day of 2011 is 11 th February of 2011.


55Table 3.2 Orbital Characteristics of 11 Non-functional GlobalStar Satellites 26 .NORAD ID25164U25306U25308U25771U25851U25853U25872U25874U25885U25886U25964UTWO LINE ELEMENT SET1 25164U 98008C 11042.27601744 -.00000071 00000-0 10000-3 0 72962 25164 052.0023 057.3745 0000149 321.9325 038.1480 11.614272105752771 25306U 98023A 11042.09193041 -.00000072 00000-0 10000-3 0 72762 25306 051.9853 090.8838 0002023 116.3436 243.7593 11.653785385802231 25308U 98023C 11042.12384752 -.00000075 00000-0 10000-3 0 56342 25308 051.9886 270.0730 0002339 107.8269 252.2814 11.796717455901361 25771U 99031B 11042.56731775 -.00000062 00000-0 10000-3 0 50712 25771 051.9853 188.1960 0002651 092.8436 267.2664 11.120824545344901 25851U 99037A 11042.90107616 -.00000061 +00000-0 +10000-3 0 092142 25851 051.9987 218.4390 0014989 130.6948 229.5152 11.044834965173581 25853U 99037C 11042.57093445 -.00000068 +00000-0 +10000-3 0 042372 25853 051.9808 079.8836 0001553 041.9023 318.1907 11.421065055337021 25872U 99041A 11042.82911121 -.00000066 +00000-0 +10000-3 0 043852 25872 051.9400 171.1145 0001056 117.6764 242.4149 11.337395735305881 25874U 99041C 11042.56386101 -.00000075 00000-0 10000-3 0 44942 25874 051.9817 074.3992 0000554 357.9397 002.1440 11.833028505327981 25885U 99043C 11042.47178723 -.00000067 00000-0 10000-3 0 39922 25885 052.0122 178.3449 0005661 086.1141 274.0314 11.391359585222371 25886U 99043D 11042.88984758 -.00000065 +00000-0 +10000-3 0 044402 25886 051.9971 193.9635 0002805 148.7290 211.3681 11.275536645285411 25964U 99062D 11042.43323594 -.00000074 00000-0 10000-3 0 39602 25964 051.9800 065.0615 0006216 188.6931 171.3790 11.76690374504624Assuming that the mother ship is inserted in<strong>to</strong> an appropriate rendezvousposition (on 11 February 2011) f<strong>or</strong> deploying the initial SRS f<strong>or</strong> the final rendezvousphase with its designated <strong>satellite</strong>, every <strong>satellite</strong> in each suite was considered <strong>to</strong> bethe initial target. It was assumed that at least one day should be allowed f<strong>or</strong> engagingthe initial SRS with its target GlobalStar. Subsequently, the remaining targetGlobalStars were considered <strong>to</strong> be the next rendezvous target (four GlobalStars f<strong>or</strong> the57° < < 91° case and five GlobalStars f<strong>or</strong> the 172° < < 271° case). It wasassumed that each of the remaining SRS vehicles would only be released from themother ship when the mother shipits <strong>or</strong>bital position was optimal in terms of enablingthat SRS <strong>to</strong> change its <strong>or</strong>bit plane, completing its V plane-change maneuver so thatit was set up <strong>to</strong> proceed immediately in a close-proximity rendezvous. The time delayand <strong>or</strong>bital maneuvering ∆V requirements f<strong>or</strong> optimally changing the SRS inclinationand right ascension of ascending nodes were estimated f<strong>or</strong> all of the remaining<strong>satellite</strong>s in each GlobalStar suite. Using this ―optimal wait time f<strong>or</strong> rendezvous‖approach, it was only necessary <strong>to</strong> estimate the <strong>or</strong>bital plane change ∆V requirementsf<strong>or</strong> maneuvering the remaining SRS spacecraft from the mother ship‘s <strong>or</strong>bit in<strong>to</strong> their


56GlobalStar <strong>satellite</strong> target <strong>or</strong>bits. The optimal mother ship <strong>or</strong>bit f<strong>or</strong> each of the twoGlobalStar <strong>satellite</strong> suites could then be identified on the basis of the <strong>to</strong>tal <strong>or</strong>bitalplane change ∆V requirements f<strong>or</strong> that suite.Non-coplanar transfer calculations <strong>to</strong> change the SRS <strong>or</strong>bit inclinations andassociated right ascension of ascending nodes f<strong>or</strong> the five GlobalStar <strong>satellite</strong> suite inFigure 3.2 were calculated using:∆ (3.1)where , ( )- (3.2)Here, subscript G represents the target GlobalStar and subscript M represents themother ship <strong>or</strong>bit, whileV , MSCOnis the circular <strong>or</strong>bital velocity of the mother shipwhen it is located in the circular <strong>or</strong>bit associated with the nth GlobalStar <strong>satellite</strong>.Table 3.3 contains the <strong>or</strong>bital inf<strong>or</strong>mation f<strong>or</strong> the five-GlobalStar <strong>satellite</strong>suite. F<strong>or</strong> the purposes of demonstrating this method, the perigee velocity has beenused as the target circular velocity f<strong>or</strong> the mother ship when it is placed initially in the<strong>or</strong>bital plane of the specified GlobalStar.Table 3.3 Orbital Characteristics of Five Non-functional GlobalStar Satellites.Satellite Name (i) (Ω) (e) (T) (V perigee )GlobalStar 25164U 52.045° 57.942° 0.001048 7433.85 sec. 6.9656 km/secGlobalStar 25964U 52.043° 66.043° 0.000651 7345.24 sec. 6.9901 km/secGlobalStar 25874U 52.034° 75.736° 0.000641 7298.17 sec. 7.0056 km/secGlobalStar 25853U 52.057° 81.121° 0.001027 7571.92 sec. 6.9228 km/secGlobalStar 25306U 52.058° 90.959° 0.000617 7418.60 sec. 6.9673 km/sec


57Using these circular velocities given by:√ , (3.3)and the GlobalStar <strong>or</strong>bital data, it was possible <strong>to</strong> prescribe the mother ship circular<strong>or</strong>bit candidates, as given in Table 3.4. In addition, the plane change angularmaneuver requirements, using equation (3.2), f<strong>or</strong> the various combinations ofGlobalStar reference <strong>or</strong>bits are summarized in Table 3.5.Table 3.4 Orbital Inclination Angular Plane-Change Requirements between The theDifferent Combinations of Mother Sship and Non-functional GlobalStar SatelliteOrbits.MSCO GS(1) GS(2) GS(3) GS(4) GS(5)MSCO-1 -- 6.3855 14.0080 18.2304 25.8971MSCO-2 6.3855 -- 7.6387 11.8767 19.5884MSCO-3 14.0080 7.6387 -- 4.2455 11.9900MSCO-4 18.2304 11.8767 4.2455 -- 7.7549MSCO-5 25.8971 19.5884 11.9900 7.7549 --Table 3.5 Circular Velocities f<strong>or</strong> Every Option of Mother Sship Orbit with respect <strong>to</strong>the Five Non-functional GlobalStar Satellite Subset.Semi-maj<strong>or</strong> Axes (a) Circular velocity (V circular )GS-25164U - MSCO1 8232.57 km 6.9583 km/sec


58GS-25964U - MSCO2 8167.01 km 6.9861 km/secGS-25874U - MSCO3 8132.08 km 7.0011 km/secGS-25853U - MSCO4 8334.18 km 6.9157 km/secGS-25306U - MSCO5 8221.30 km 6.9630 km/secUsing equation Equation (3.1), the overall <strong>or</strong>bital plane change velocityincrements can be calculated f<strong>or</strong> every combination of the five non-functionalGlobalStar <strong>satellite</strong> <strong>or</strong>bits. The individual SRS velocity increments and overall <strong>to</strong>talvelocity increments required from each candidate mother ship <strong>or</strong>bit are summarized inTable 3.6.Table 3.6 Velocity Increments <strong>to</strong> Change Inclination and Right Ascension ofAscending Nodes f<strong>or</strong> Each Starting Point of Mother sShip.MSCOGS(1) GS(2) GS(3) GS(4) GS(5) Total V25164U 25964U 25874U 25853U 25306U (km/sec)MSCO-1 -- 0.7751 1.6970 2.2047 3.1184 7.7952MSCO-2 0.7782 -- 0.9307 1.4455 2.3768 5.5312MSCO-3 1.7074 0.9327 -- 0.5187 1.4624 4.6212MSCO-4 2.1912 1.4310 0.5123 -- 0.9353 5.0698MSCO-5 3.1205 2.3690 1.4545 0.9417 -- 7.8857As shown in Table 3.6, a mother ship circular <strong>or</strong>bit set up f<strong>or</strong> the initial SRSspacecraft <strong>to</strong> rendezvous with MSCO-3 (Non-functional GlobalStar <strong>satellite</strong> 25874U)has significant advantages over the other mother ship <strong>or</strong>bit candidates. That circular<strong>or</strong>bit minimizes the <strong>to</strong>tal ∆V requirements f<strong>or</strong> SRS <strong>or</strong>bital plane change maneuversand can be used as the starting point f<strong>or</strong> setting up the subsequent sequence of SRSdeployments based on the wait time required f<strong>or</strong> optimal <strong>or</strong>bital plane changemaneuvers.In <strong>or</strong>der <strong>to</strong> proceed, it is necessary <strong>to</strong> utilize universal time <strong>to</strong> locate themother ship in its <strong>or</strong>bit and all of the GlobalStars in the target suite, <strong>to</strong> start the


59rendezvous f<strong>or</strong> the first stack of non-functional GlobalStar <strong>satellite</strong>s. Also, we are able<strong>to</strong> use spherical trigonometry as shown in Figure 3.4 27 , <strong>to</strong> develop expressions f<strong>or</strong> ϑand i whenever a ∆V applies at the intersection of the target spacecraft and chasespacecraft <strong>or</strong>bits. We determine the location of the burn by using the cosine law and itenables us <strong>to</strong> avoid quadrant checks. Hence, f<strong>or</strong> the impulse argument of latitude onthe initial <strong>or</strong>bit, which is called u initial , is calculated from:.( ) (∆ ) ( ) ( )( ) ( )/ (3.4)and the impulsive argument of latitude on the final <strong>or</strong>bit, which is called u final , iscalculated from:.( ) ( ) ( ) ( ) (∆ )( )/ (3.5)


60Figure 3.4 Geometry f<strong>or</strong> Changes <strong>to</strong> Inclination and Right Ascension ofAscending Node.Calculated locations of impulsive burn completions are shown in Table 3.7.


61Table 3.7 Location of Burn <strong>to</strong> Change Inclination and Right Ascension of AscendingNode.MSCO-3GS(1)25164UGS(2)25964UGS(3)25874UGS(4)25853UGS(5)25306Uu i 95.4556°u f 84.4553°u i 94.5846°u f 85.1877°u i -u f -u i 91.3466°u f 88.0331°u i 92.9183°u f 86.9470°The same calculation and process can be employed f<strong>or</strong> the other six nonfunctionalGlobalStar <strong>satellite</strong>s whose <strong>or</strong>bital parameters are summarized in Table 3.8,while the calculated values f<strong>or</strong> ϑ if , mother ship circular velocities and velocityincrements required f<strong>or</strong> the <strong>or</strong>bital plane changes are provided in Tables 3.9, 3.10 and3.11.


62Table 3.8 Orbital Characteristics of Five Non-functional GlobalStar Satellites.Satellite Name (i) (Ω) (e) (T) (V perigee )GlobalStar25872UGlobalStar25885UGlobalStar25771UGlobalStar25886UGlobalStar25851UGlobalStar25308U51.952° 172.905° 0.000533 7623.65 sec.52.013° 179.299° 0.001089 7585.27 sec.51.966° 189.30° 0.001190 7764.94 sec.51.991° 195.848° 0.000689 7669.06 sec.51.969° 220.276° 0.002141 7828.83 sec.51.937° 270.261° 0.000913 7330.57 sec.6.9037km/sec6.9192km/sec6.8661km/sec6.8911km/sec6.8539km/sec6.9972km/secTable 3.9 ϑ if f<strong>or</strong> Non-functional Six GlobalStar Satellites.MSCOGS(1) GS(2) GS(3) GS(4) GS(5) GS(6)25872U 25885U 25771U 25886U 25851U 25308UMSCO-1 -- 5.0367 12.8962 18.0261 36.889 72.5066MSCO-2 5.0367 -- 7.8769 13.0239 32.0176 68.3434MSCO-3 12.8962 7.8769 -- 5.1566 24.2831 61.4908MSCO-4 18.0261 13.0239 5.1566 -- 19.1884 56.8839MSCO-5 36.889 32.0176 24.8231 19.1884 -- 38.868MSCO-6 72.5066 68.3434 61.4908 56.8839 38.868 --


63Table 3.10 Circular Velocities f<strong>or</strong> every Option of Mother Ship Orbit with respect <strong>to</strong>the Six Non-functional GlobalStar Satellite Subset.Semi-maj<strong>or</strong> Axes (a) Circular velocity (V circular )GS-25872U - MSCO1 8372.10 km 6.90 km/secGS-25885U - MSCO2 8343.98 km 6.9117 km/secGS-25771U - MSCO3 8475.23 km 6.8579 km/secGS-25886U - MSCO4 8405.31 km 6.8864 km/secGS-25851U - MSCO5 8521.65 km 6.8392 km/secGS-25308U - MSCO6 8156.13 km 6.9908 km/secAs can be seen in Table 3.11, MSCO-3 (Non-functional GlobalStar <strong>satellite</strong>25771U) is the logical <strong>or</strong>bit f<strong>or</strong> minimizing the overall ∆V requirements f<strong>or</strong> thesecond subset of non-functional GlobalStar <strong>satellite</strong>s.Table 3.11 Summary of Velocity Increments f<strong>or</strong> Plane Change and Right Ascensionof The the Ascending Node Adjustments f<strong>or</strong> SRS Units Departing from The theDifferent Candidate Mother Ship Orbits.MSCOGS(1) GS(2) GS(3) GS(4) GS(5) GS(6) Total V25872U 25885U 25771U 25886U 25851U 25308U (km/sec)MSCO-1 -- 0.6063 1.5498 2.1619 4.3661 8.1608 16.8449MSCO-2 0.6073 -- 0.9494 1.5677 3.8123 7.7642 14.7009MSCO-3 1.5403 0.9420 -- 0.617 2.8848 7.0119 12.996MSCO-4 2.1576 1.562 0.6195 -- 2.2955 6.5595 13.1941MSCO-5 4.3277 3.7723 2.9399 2.2798 -- 4.5511 17.8708MSCO-6 8.2681 7.8531 7.1477 6.659 4.652 -- 34.5799


64The six <strong>satellite</strong> subset demonstrates the challenge of rendezvous and de-<strong>or</strong>bitstrategies when an ‗outlier‘ <strong>satellite</strong> is present. From Figure 3.1, it can be seen thatnon-functional GlobalStar <strong>satellite</strong> 25308U is not in an <strong>or</strong>bit that is completely similar<strong>to</strong> the other five GlobalStars in the subset. That observation is m<strong>or</strong>e apparent in Table3.11, where the required ∆Vs f<strong>or</strong> the necessary plane-change maneuvers <strong>to</strong> departfrom one of the first five GlobalStar mother ship <strong>or</strong>bit candidates, setting up f<strong>or</strong>rendezvous with outlier MSCO-6, ranges between 4.55 and 8.16 km/s. Furtherm<strong>or</strong>e,the velocity increments required <strong>to</strong> maneuver the other five SRS units from theMSCO-6 <strong>or</strong>bit <strong>to</strong> set up f<strong>or</strong> rendezvous with the other GlobalStar <strong>or</strong>bits in this setranges from 4.65 <strong>to</strong> 8.26 km/s. Those velocity increments are comparable <strong>to</strong> thevelocity increment required <strong>to</strong> launch the mother ship in<strong>to</strong> its initial <strong>or</strong>bit.Consequently, it is not feasible <strong>to</strong> achieve the desired launch mass and cost savingsf<strong>or</strong> rendezvous with and de-<strong>or</strong>biting this six-<strong>satellite</strong> set.Possible efficiencies can be achieved with the second set of non-functionalGlobalStar <strong>satellite</strong>s only if the five <strong>satellite</strong>s with compatible <strong>or</strong>bits are considered.By eliminating non-functional GlobalStar <strong>satellite</strong> 25308U, the velocity incrementsrequired f<strong>or</strong> the plane change maneuvers f<strong>or</strong> the remaining four <strong>satellite</strong>s are tabulatedin Table 3.12. As in the <strong>or</strong>iginal five-<strong>satellite</strong> example, it can be seen here that bylaunching the mother ship in<strong>to</strong> the rendezvous <strong>or</strong>bit f<strong>or</strong> GlobalStar 25771U(MSCO-3), substantial propellant savings are possible.Table 3.12 demonstrates the similarity between this second <strong>satellite</strong> set and theexample set already presented. It is not necessary <strong>to</strong> repeat the mass estimation stepsf<strong>or</strong> this set, since they are so similar <strong>to</strong> the example already discussed.Table 3.12 Velocity Increments <strong>to</strong> Change Inclination and Right Ascension ofAscending Nodes f<strong>or</strong> Each Starting Point of Mother Sship after Eliminating GS(6)MSCO GS(1)25872UGS(2)25885UGS(3)25771UGS(4)25886UGS(5)25851UTotal V(km/sec)MSCO-1 -- 0.6063 1.5498 2.1619 4.3661 8.6841MSCO-2 0.6073 -- 0.9494 1.5677 3.8123 6.9367MSCO-3 1.5403 0.9420 -- 0.617 2.8848 5.9841


65MSCO-4 2.1576 1.562 0.6195 -- 2.2955 6.6346MSCO-5 4.3277 3.7723 2.9399 2.2798 -- 13.3197In this analysis, the perturbing f<strong>or</strong>ces such as Earth‘s gravitational field,atmospheric drag, solar radiation pressure, and other planetary gravitational f<strong>or</strong>ceshave been neglected. All <strong>or</strong>bit calculations were made using the restricted two-bodymodel, along with NORAD data. As mentioned in chapter Chapter twoTwo, thisanalysis has used two-impulse rendezvous, Clohessy–Wiltshire equations andHohmann transfer <strong>or</strong>bits in the calculations. MatLab-based programs have beenemployed f<strong>or</strong> the calculations and plots. In the calculations, the goal has been <strong>to</strong>minimize overall ∆V requirementsV requirements f<strong>or</strong> changing trajec<strong>to</strong>ries.Furtherm<strong>or</strong>e, it has been assumed that operational costs are sufficiently low thatrendezvous time intervals needed f<strong>or</strong> optimal ∆Vs can be quite long. Since <strong>or</strong>bitperturbations must be considered in identifying minimum energy <strong>or</strong>bital maneuveropp<strong>or</strong>tunities over periods of weeks <strong>or</strong> months, it was decided <strong>to</strong> restrict minimumenergy maneuver opp<strong>or</strong>tunities <strong>to</strong> the 24- hour period following a simulatedrendezvous. In that way, actual <strong>or</strong>bit variations should be small and the restricted twobodymodeling approach can be employed. Hence, minimum required ∆V optionswere found by choosing the best time, between 0 hour and 24 hours, <strong>to</strong> achieve therendezvous between the next assigned SRS and its non-functional GlobalStar <strong>satellite</strong>target. A required ∆V vs. maneuver completion time graph, as shown in Figure 3.5,was developed in <strong>or</strong>der <strong>to</strong> find the best time f<strong>or</strong> each rendezvous.The first SRS will be inserted <strong>to</strong> a circular <strong>or</strong>bit nearly 1.5 km in front of themother ship and the <strong>or</strong>bital elements f<strong>or</strong> the first rendezvous case (with <strong>satellite</strong>25874U) is shown in Table 3.13.Table 3.13 Classical Orbital Elements of 1 st First Rendezvous.


6625874U SRS-3a (km) 8132.08 8132.08e 0.000641 0i (deg) 52.034 52.034Ω (deg) 75.736 75.736w (deg) 65.071 0θ (deg) 140.746 205The two <strong>satellite</strong>s are so close <strong>to</strong> each other after the SRS-3 <strong>or</strong>bit insertionmaneuver that a minimal ∆V burn is required. The assumed <strong>or</strong>bital separationdistances during the coarse and fine rendezvous stages were based on the ETS-VIIau<strong>to</strong>nomous rendezvous experiment 15 . In the ETS-VII study, au<strong>to</strong>nomous rendezvouswas divided in<strong>to</strong> three elements based on separation distance: approach phase (from10 km <strong>to</strong> 500 m), final, final approach phase (500 m <strong>to</strong> 2 m) and docking phase(within 2 m). These distances were found <strong>to</strong> be appropriate in staging the <strong>or</strong>bitalrendezvous experiment.After completing the initial rendezvous and de-<strong>or</strong>bit operations on GlobalStar<strong>satellite</strong> 25874U, the mother ship could dispense the next SRS vehicle. In that way,potential collisions between the mother ship and a prematurely-deployed ―next‖ SRSvehicle with GlobalStar <strong>satellite</strong> 25874U could be avoided.First rendezvous parameters and plots:;


670.25258740.20.150.1Delta V0.0500 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24Figure 3.5 ∆V Requirements f<strong>or</strong> Rendezvous between Non-functional GlobalStarSatellite 25874U and SRS-3 in 24 Hours.As seen in Figure 3.5, the time-sequenced ∆V requirement is ―damped‖ <strong>to</strong> anearly constant minimum value, after 16 hours. We investigated bBoth minimum ∆Vrequirement and time delay were investigated. The Clohessy–Wiltshire equationsconsider time <strong>to</strong> find the best ∆V requirements. When the number of <strong>or</strong>bits pri<strong>or</strong> <strong>to</strong>rendezvous is increased, the flight time f<strong>or</strong> rendezvous is changed. In that way, therequired velocity increment can be reduced by waiting.Table 3.14 Timeline f<strong>or</strong> First Rendezvous.DATE TIME ACTION11 Feb 2011 00:00:00.000 Start of Mission11 Feb 2011 00:15:00.000 SRS-3 Release from Mother Sship11 Feb 2011 00:30:00.000 First Rendezvous Initial Location11 Feb 2011 13:30:00.000 End of First Rendezvous


68Figure 3.6 Rendezvous of SRS with GlobalStar 25874U.The best time <strong>to</strong> achieve rendezvous between the deployed SRS vehicle andGlobalStar 25874U was 13 hours f<strong>or</strong> minimum ∆V. The required ∆V was 0.0042km/sec.After completion of the initial SRS deployment and servicing <strong>or</strong> removal of25874U, the second rendezvous is initiated. In <strong>or</strong>der <strong>to</strong> minimize V requirements,each successive SRS deployment has attempted <strong>to</strong> exploit multiple <strong>or</strong>bit encountermaneuvers, thereby using time delays rather than larger Vs. Satellites in differen<strong>to</strong>rbits have different periods and simple Keplerian <strong>or</strong>bital mechanics can be employed<strong>to</strong> estimate optimal delay times. One day was allowed f<strong>or</strong> placing the mother ship inits desired <strong>or</strong>bit and accomplishing the first rendezvous and de-<strong>or</strong>bit operation. Whilethat is an aggressive assumption, the process being described f<strong>or</strong> multiple servicingdeployments can be adjusted somewhat arbitrarily after the first <strong>satellite</strong> has beenserviced <strong>or</strong> removed. F<strong>or</strong> this representative case, GlobalStar <strong>satellite</strong> 25164U was thesecond <strong>satellite</strong> and the second rendezvous was initiated with an SRS plane changemaneuver after its release. After SRS release, it was necessary <strong>to</strong> calculate the timerequired <strong>to</strong> complete the plane change maneuver, placing the second SRS in its


69approach phase position. Using that maneuver time and the Universal universal timewhen the SRS was <strong>to</strong> arrive at its rendezvous station, it was possible <strong>to</strong> estimate thetime when the SRS <strong>or</strong>bit maneuver should be initiated. The desired <strong>or</strong>bitalcharacteristics f<strong>or</strong> the second rendezvous (with 25164U) are summarized in Table3.15, followed by the graph showing the required <strong>or</strong>bital maneuver delta V as afunction of arrival time.Table 3.15 Classical Orbital Elements of 2 nd Second Rendezvous.25164U SRS-1a (km) 8232.57 8132.08e 0.001048 0i (deg) 52.045 52.045Ω (deg) 57.942 57.942w (deg) 100.522 0θ (deg) 66.5132 165.1816Second rendezvous parameters and plot:;


7010.90.80.70.60.50.40.30.20.10251640 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24Delta VFigure 3.7 ∆V Requirements f<strong>or</strong> Rendezvous between Non-functional GlobalStarSatellite 25164U and SRS-1 in 24 Hours.Table 3.16 Timeline f<strong>or</strong> Second Rendezvous.DATE TIME ACTION11 Feb 2011 13:45:00.000 SRS-1 Release from Mother Sship11 Feb 2011 14:04:26.400 Initial Location after the Plane Change f<strong>or</strong> SRS-113 Feb 2011 07:04:26.400 Second Rendezvous Initial Location13 Feb 2011 08:04:26.400 End of Second Rendezvous


71Figure 3.8 Rendezvous of SRS with GlobalStar 25164U.The best time f<strong>or</strong> the second rendezvous between the second SRS and itsGlobalStar <strong>satellite</strong> target (25164U), is 1 hour after completion of the first GlobalStarintercept and recovery operation. At that time, the required rendezvous velocityincrement was 0.0513 km/sec. Since that is such a sh<strong>or</strong>t time interval and since theactual completion time f<strong>or</strong> a real GlobalStar intercept and recovery operation could bevery different from the assumed conditions, it is imp<strong>or</strong>tant <strong>to</strong> note from Figure 3.7,that low velocity increment rendezvous insertion opp<strong>or</strong>tunities also occurapproximately 16 hours after the rendezvous opp<strong>or</strong>tunity window has been opened.After completion of the second rendezvous, the mother ship dispenses its thirdSRS. The third rendezvous (with GlobalStar <strong>satellite</strong> 25853U) <strong>or</strong>bital) <strong>or</strong>bitalparameters are summarized in Table 3.17, and the V requirements vs. on-stationarrival time are displayed in Figure 3.9.


72Table 3.17 Classical Orbital Elements of 3 rd Third Rendezvous.25853U SRS-4a (km) 8334.18 8132.08e 0.001027 0i (deg) 52.057 52.057Ω (deg) 81.121 81.121w (deg) 113.359 0θ (deg) 346.4246 97.07421425853121086Delta V4200 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24Figure 3.9 ∆V Requirements f<strong>or</strong> Rendezvous between Non-functional GlobalStarSatellite 25853U and SRS-4 in 24 Hours.


73Table 3.18 Timeline f<strong>or</strong> Third Rendezvous.DATE TIME ACTION13 Feb 2011 08:29:26.400 SRS-4 Release from Mother Sship13 Feb 2011 08:37:22.800 Initial Location after the Plane Change f<strong>or</strong> SRS-413 Feb 2011 16:46:58.800 Third Rendezvous Initial Location13 Feb 2011 17:46:58.800 End of Third RendezvousThird rendezvous parameters and plot;:Figure 3.10 Rendezvous of SRS with GlobalStar 25853U.SRS with GlobalStar <strong>satellite</strong> 25853U, rendezvous time is 1 hour and neededrendezvous velocity is 0.0999 km/s. After completing the third rendezvous, themother ship will release the fourth SRS from the mother shipits <strong>or</strong>bit. The fourthrendezvous will be with GlobalStar <strong>satellite</strong> 25306U and the <strong>or</strong>bit parameters f<strong>or</strong> thefourth rendezvous (25306U) are shown in Table 3.19.


74Table 3.19 Classical Orbital Elements of 4 th Fourth Rendezvous.25306U SRS-2a (km) 8221.30 8132.08e 0.000617 0i (deg) 52.058 52.058Ω (deg) 90.959 90.959w (deg) 72.992 0θ (deg) 273.5079 345.1021.22530610.80.60.4Delta V0.200 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24Figure 3.11 ∆V Requirements f<strong>or</strong> Rendezvous between Non-functional GlobalStarSatellite 25306U and SRS-2 in 24 Hours.


75Table 3.20 Timeline f<strong>or</strong> Fourth Rendezvous.DATE TIME ACTION13 Feb 2011 18:00:00.000 SRS-2 Release from Mother Sship13 Feb 2011 18:46:40.800 Initial Location after the Plane Change f<strong>or</strong> SRS-414 Feb 2011 06:22:40.800 Fourth Rendezvous Initial Location14 Feb 2011 07:22:40.800 End of Fourth RendezvousFourth rendezvous parameters and plot.:


76Figure 3.12 Rendezvous of SRS with GlobalStar 25306U.The optimal SRS time f<strong>or</strong> rendezvous with GlobalStar <strong>satellite</strong> 25306, is 1 hour andthe required rendezvous velocity is 0.0418 km/s. After completing the fourthrendezvous, the mother ship will release the fifth SRS f<strong>or</strong> deployment in<strong>to</strong> theGlobalStar 25964U <strong>or</strong>bit. The fifth rendezvous will be GlobalStar <strong>satellite</strong> 25964Uand <strong>or</strong>bit and values f<strong>or</strong> the fifth rendezvous (25964U) are given in Table 3.21.Table 3.21 Classical Orbital Elements of 5 th Fifth Rendezvous.25964U SRS-5a (km) 8167.01 8132.08e 0.000651 0i (deg) 52.043 52.043Ω (deg) 66.043 66.043w (deg) 148.004 0θ (deg) 43.4082 190.30180.80.70.60.50.40.30.20.10259640 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24Delta VFigure 3.13 ∆V Requirements f<strong>or</strong> Rendezvous between Non-functional GlobalStarSatellite 25964U and SRS-5 in 24 Hours.


78Table 3.22 Timeline f<strong>or</strong> Fifth Rendezvous.DATE TIME ACTION14 Feb 2011 08:00:00.000 SRS-5 Release from Mother Sship14 Feb 2011 08:57:36.000 Initial Location after the Plane Change f<strong>or</strong> SRS-518 Feb 2011 18:57:36.000 Fifth Rendezvous Initial Location18 Feb 2011 19:57:36.000 End of Fifth RendezvousFifth rendezvous parameters and plot;:Figure 3.14 Rendezvous of SRS with GlobalStar 25964U.Again, the optimal delay time f<strong>or</strong> SRS rendezvous with GlobalStar 25964, is 1 hourand the needed rendezvous velocity increment is 0.0386 km/s.


79In our the <strong>methodology</strong> development, we will not investigate the second subset ofnon-functional GlobalStar <strong>satellite</strong>s‘ will not be investigated using the same detailedrendezvous and de-<strong>or</strong>biting process just discussed, because it is the same process andcalculations as the first subset. Other than the outlier problem discussed previously,the subset analysis just presented can be considered representative of the secondsubset.3.2.2 ∆V Calculation f<strong>or</strong> SRS and Non-functional GlobalStar Satellite’sDe-<strong>or</strong>biting ManeuverThis analysis has assumed that the initial velocity increments were appliedinstantaneously at the apogee of the grabbed non-functional GlobalStar <strong>satellite</strong> withSRS <strong>or</strong>bit. The assumed Earth reference radius was 6,378 km, and the Earth‘sgravitational parameter was 398,600 km 3 s -2 . In addition, a re-entry (perigee) altitudeof 150 km has been used. The de-<strong>or</strong>biting sketch is shown in Figure 3.15.Figure 3.15 De-<strong>or</strong>bit Maneuver.


80The ∆V calculations proceeded as follows:1. Use NORAD two-line ephemeras data <strong>to</strong> characterize a specific GlobalStar target,2. Calculate the GlobalStar <strong>or</strong>bit period in seconds,(3.6)3. Use the <strong>or</strong>bit period <strong>to</strong> calculate the semi-maj<strong>or</strong> axis:√. / (3.7)4. Using the tabulated eccentricity, determine:( ) (3.8a)( ) (3.8b)5. Calculate the apogee and perigee velocities:(3.9)√ ( ) (3.10a)√ ( ) (3.10b)6. Determine the SRS transfer <strong>or</strong>bit specifications where:( ) (3.11a)( ) (3.11b)( ) ( )(3.11c)7. Determine the required transfer velocity:


81(3.12)( ) √ () (3.13)( )8. Calculate the transfer ∆V;∆ ( ) (3.14)The required initial transfer velocity increments f<strong>or</strong> each spent GlobalStar <strong>satellite</strong> setis summarized in Table 3.22.Table 3.23 Required Initial Velocities <strong>to</strong> Get in<strong>to</strong> De-<strong>or</strong>biting Trajec<strong>to</strong>ry.NORAD ID25164U25964U25874U25853U25306UREQUIRED ∆V0.41480.39960.39450.43260.4108All calculations were made sequentially. The mother ship released its SRSs SRS‘along its <strong>or</strong>bit, <strong>to</strong> enable the SRS <strong>to</strong> set up f<strong>or</strong> the specific rendezvous. As alreadydescribed, the various SRS rendezvous operations were sequenced f<strong>or</strong> minimum V


82and, allowing time f<strong>or</strong> actual rendezvous and latch-up, combined SRS-GlobalStar<strong>satellite</strong> elements resulted. If a GlobalStar could be <strong>repair</strong>ed, the SRS unit woulddisconnect from it and the SRS propulsion system would be used <strong>to</strong> propel the SRSon<strong>to</strong> an appropriate re-entry trajec<strong>to</strong>ry. The w<strong>or</strong>st case is when the GlobalStar cannotbe <strong>repair</strong>ed and the combined SRS-GlobalStar ―<strong>satellite</strong>‖ needs <strong>to</strong> be removed from<strong>or</strong>bit. SRS and non-functional GlobalStar <strong>satellite</strong> pairs got in<strong>to</strong> de-<strong>or</strong>biting trajec<strong>to</strong>ry.Also we added a 10% ∆V allowance was added f<strong>or</strong> all rendezvous maneuvers. Thecalculated required ∆V values are shown in Figure 3.24.Table 3.24 Required ∆V <strong>to</strong> Achieve Rendezvous.25164U25964U25874U25853USRSPLANECHANGE∆V (km/sec)1.70740.932700.5187SRSRENDEZVOUS∆V (km/sec)0.05130.03860.00420.0999REQUIRED ∆V∆VALLOWANCE(km/sec)0.0050.0040.00050.00925306U 1.4624 0.0418 0.005DE-ORBIT ∆V(km/sec)0.41480.39960.39450.43260.4108TOTAL ∆V(km/sec)2.17851.41090.39921.06021.9200We calculated aAll rendezvous were calculuated by using a restricted twobodyproblem analysis and frozen time. In real calculations, the NORAD data must beupdated as close <strong>to</strong> the actual rendezvous time as possible.3.2.3 Propellant mass and burn time calculations f<strong>or</strong> SRS and Non-functionalGlobalStar <strong>satellite</strong> de-<strong>or</strong>bit operationsExcept f<strong>or</strong> the close proximity maneuvers, <strong>or</strong>bital rendezvous propellant massand maneuver time allowances are required. The rocket equation can be employed <strong>to</strong>estimate the propellant required f<strong>or</strong> each distinct <strong>or</strong>bital maneuver tabulated in Tables3.6 and 3.11. That is,∆ ( ) . / (3.15a)where ( ) (3.15b)


83and the assumed specific impulse is seconds 28 (3.15c)The specific V requirements f<strong>or</strong> the three primary SRS-GlobalStarrendezvous and servicing maneuvers are summarized in Table 3.25. The propulsivemaneuvers must be analyzed in reverse in <strong>or</strong>der <strong>to</strong> determine the estimated initialmass of each SRS unit, and the associated maneuver initiation times. The de-<strong>or</strong>bitV-based propellant mass requirement has been labeled Prop 1; the propellant massrequired f<strong>or</strong> insertion of the SRS in<strong>to</strong> the rendezvous <strong>or</strong>bit has been labeled Prop 2;and the initial <strong>or</strong>bital plane change maneuver (from the mother ship <strong>or</strong>bit) propellantrequirement has been labeled Prop 3.


84Table 3.25 Required ∆V and Needed Propellant f<strong>or</strong> Missions.MISSION1MISSION2MISSION3MISSION4MISSION525164U25964U25874U25853U25306UREQUIRED∆V (m/sec)De-<strong>or</strong>bit GS1 414.8Two-impulsiveRendezvousPlane Change56.31707.4Initial SRS 1 -REQUIRED∆V (m/sec)De-<strong>or</strong>bit GS2 399.6Two-impulsiveRendezvous42.6Plane Change 932.7Initial SRS 2 -REQUIRED∆V (m/sec)De-<strong>or</strong>bit GS3 394.5Plane Change 5Initial SRS 3 -REQUIRED∆V (m/sec)De-<strong>or</strong>bit GS4 432.6Two-impulsiveRendezvous108.9Plane Change 518.7Initial SRS 4 -REQUIRED∆V (m/sec)De-<strong>or</strong>bit GS5 410.8Two-impulsiveRendezvous46.8Plane Change 1462.4Initial SRS 5 -TOTAL MASS (kg)SRS 1 GS 1 Descent Prop Prop 1150 450 10 129SRS 1150SRS 1150SRS 1150TOTAL MASS (kg)SRS 2 GS 2 Descent Prop Prop 1150 450 10 124SRS 2150SRS 2150SRS 2150TOTAL MASS (kg)SRS 3 GS 3 Descent Prop Prop 1150 450 10 122SRS 3150SRS 3150SRS 4 GS 4 Descent Prop Prop 1150 450 10 135SRS 4150SRS 4150SRS 4150TOTAL MASS (kg)TOTAL MASS (kg)SRS 5 GS 5 Descent Prop Prop 1150 450 10 128SRS 5150SRS 5150SRS 5150Prop 1 Prop 2129 8Prop 1 Prop 2 Prop 3129 8 358Total Prop495Prop 1 Prop 2124 6Prop 1 Prop 2 Prop 3124 6 157Total Prop287Prop 1 Prop 2122 1Total Prop123Prop 1 Prop 2135 16Prop 1 Prop 2 Prop 3135 16 83Total Prop234Prop 1 Prop 2128 7Prop 1 Prop 2 Prop 3128 7 287Total Prop422


̇̇85In <strong>or</strong>der <strong>to</strong> translate these incremental propellant requirements in<strong>to</strong> maneuverburn times, it is necessary <strong>to</strong> specify both the propellant and the thrusters. Since theGlobalStar <strong>satellite</strong>s employ hydrazine propellant, it will be the assumed propellantf<strong>or</strong> the SRS propulsion systems. EADS‘ subsidiary Astrium has a long his<strong>to</strong>ry ofproviding reliable space-qualified hydrazine thrusters f<strong>or</strong> all types of spacecraft.Commercially available off-the-shelf (COTS) hydrazine propulsion units can beobtained with thrust levels of 1N, 2N, 5N, 10N, 20N and 400N 29 . In <strong>or</strong>der <strong>to</strong> properlysize the SRS vehicles, it is necessary <strong>to</strong> select thrusters that are capable of perf<strong>or</strong>mingthe various V maneuvers in time intervals that are compatible with the GlobalStar<strong>or</strong>bital periods.Burn times can be calculated f<strong>or</strong> specific thrusters by using the equation thatdefines specific impulse <strong>to</strong> determine the mass flow rate f<strong>or</strong> the specified thruster andits stated specific impulse. That is, using:( ) , (3.16)the mass flow rates f<strong>or</strong> the various Astrium thruster sizes can be calculated and aresummarized in Table 3.25.Table 3.26 Propellant Mass Flow Rates f<strong>or</strong> Various Astrium COTS Thrusters.1N 2N 5N 10N 20N 400Nm Thrust (kg/sec) 4.635x10 -4 9.270x10 -4 2.317x10 -3 4.635x10 -3 9.270x10 -3 0.185Employing the five SRS mission scenarios from Table 3.24, 1N, 10N and 400Nthrusters were considered as SRS propulsion unit candidates. The associated burntimes required f<strong>or</strong> the different thruster and mission combinations are given inTable 3.27 where:(3.17)


86Table 3.27 Burn Times f<strong>or</strong> the Mission f<strong>or</strong> Different Thrust Levels.BURN TIME f<strong>or</strong>Prop 1 (sec)BURN TIME f<strong>or</strong>Prop 2 (sec)BURN TIME f<strong>or</strong>Prop 3 (sec)1N 10N 400N 1N 10N 400N 1N 10N 400NMission 1 278,964 27,896 697 16,504 1,650 41 773,031 77,303 1932Mission 2 267,788 26,778 669 12,211 1,221 30 338,101 33,810 845Mission 3 263,214 26,321 659 1,402 140 4 - - -Mission 4 292,125 29,212 730 33,009 3,300 83 178,640 17,864 446Mission 5 886,299 88,629 2215 13,613 1,361 34 618,381 61,838 1545Table 3.27 demonstrates that the 400N hydrazine thruster can be employed <strong>to</strong> yieldreasonable burn times. Table 3.28 is an estimated <strong>to</strong>tal mission payload f<strong>or</strong> thecomplete five-<strong>satellite</strong> subset mission, demonstrating that the <strong>to</strong>tal mass is within thecapabilities of the Soyuz launch system.Table 3.28 Total Mission Payload Mass of Five Non-functional GlobalStar SetMASSDESCENTPROPELLANT PROPELLANT TOTAL(kg) (kg) (kg) (kg)Mother Ship 750 20 250 1020SRS-1 150 10 495 655SRS-2 150 10 287 447SRS-3 150 10 123 283SRS-4 150 10 234 394SRS-5 150 10 422 582TOTAL 1500 70 1811 3381The Globalstar <strong>satellite</strong>s have beenwere launched from the Baikonur Cosmodromeusing Soyuz launch vehicles 18 , with launch payload masses of about 3,000 kg f<strong>or</strong> theirsix <strong>satellite</strong> clusters. The estimated mission payload summarized in Table 3.28 can belaunched using a Soyuz launch vehicle.


87CHAPTER 4CONCLUSIONS AND RECOMMENDATIONS FOR FUTUREWORKAnalytical Graphics, Inc., STK software and MatLab-based simulations wereemployed <strong>to</strong> develop a <strong>methodology</strong> f<strong>or</strong> systematically removing non-functioning(GlobalStar) <strong>satellite</strong>s from a large constellation. The <strong>methodology</strong> can be employedf<strong>or</strong> other <strong>constellations</strong> which have non-functional <strong>satellite</strong>s <strong>or</strong> f<strong>or</strong> a specific group ofnon-functional <strong>satellite</strong>s that threatens other functional <strong>satellite</strong>s. The proposed<strong>methodology</strong> employed a mother ship <strong>to</strong> carry a small set of servicing and <strong>repair</strong><strong>satellite</strong>s (SRSs) in<strong>to</strong> an optimal <strong>or</strong>bit from which they can be released and guided <strong>to</strong>specific target <strong>satellite</strong>s. The mini-<strong>satellite</strong>s were assumed <strong>to</strong> be capable ofau<strong>to</strong>nomous rendezvous with their target <strong>satellite</strong>s, inc<strong>or</strong>p<strong>or</strong>ating manipula<strong>to</strong>rs <strong>to</strong> grabthe target <strong>satellite</strong>, after the au<strong>to</strong>nomous rendezvous phase. After linking with thetarget <strong>satellite</strong>, the SRS spacecraft could either <strong>repair</strong> the non-functioning <strong>satellite</strong> andde-<strong>or</strong>bit itself <strong>or</strong> place the linked SRS-GlobalStar pair in a de-<strong>or</strong>bit trajec<strong>to</strong>ry whoseperigee altitude was 150 km, in <strong>or</strong>der <strong>to</strong> quickly re-enter the atmosphere and bedestroyed.The ∆V velocity increment requirements f<strong>or</strong> an overall mission wereestimated, considering each of the non-functioning <strong>satellite</strong> <strong>or</strong>bits <strong>to</strong> be candidatemother ship <strong>or</strong>bits, in a step-by-step process in <strong>or</strong>der <strong>to</strong> identify the minimum <strong>to</strong>tal∆V requirement and thus the best opp<strong>or</strong>tunity <strong>to</strong> execute a minimum-cost rendezvousand de-<strong>or</strong>biting mission. This analysis showed that it was possible <strong>to</strong> employ a mothership-SRS payload design with a nominal <strong>to</strong>tal mass similar <strong>to</strong> the <strong>to</strong>tal massassociated with second-generation, six-<strong>satellite</strong> GlobalStar <strong>satellite</strong> launch payloads.In the five-GlobalStar example, an optimal mother ship <strong>or</strong>bit was identified andoverall system estimates appeared <strong>to</strong> be reasonable.F<strong>or</strong> the remaining six non-functioning GlobalStar <strong>satellite</strong>s, this analysisshowed that one of the <strong>satellite</strong>s was an ―outlier‖ in the sense that its <strong>or</strong>bitalparameters were not compatible with the other five <strong>satellite</strong>s in the set. As a result, theestimated V requirements f<strong>or</strong> removing all six GlobalStars using SRS vehicles from


88a single mother ship was shown <strong>to</strong> be impractical because the V requirements f<strong>or</strong>many of the required rendezvous maneuvers were nearly the same as the Vrequirements f<strong>or</strong> launching the SRS vehicles from Earth. On the other hand, when theoutlier GlobalStar was excluded, the mother ship approach demonstrated potentialmass and associated cost savings that were similar <strong>to</strong> the detailed five GlobalStarexample.A m<strong>or</strong>e detailed study of this approach is warranted. Since the non-functioningGlobalStar <strong>satellite</strong>s have been placed in graveyard <strong>or</strong>bits, a different <strong>satellite</strong>constellation could be considered. The appropriate constellation should utilize<strong>satellite</strong>s that have sufficient design data <strong>to</strong> enable a m<strong>or</strong>e accurate characterization ofthe actual rendezvous and docking maneuvers, as well as permitting the developmen<strong>to</strong>f an SRS <strong>to</strong>ol kit and spare parts set that could be inc<strong>or</strong>p<strong>or</strong>ated in the SRS design <strong>to</strong><strong>repair</strong> solar arrays and other <strong>satellite</strong> components. Furtherm<strong>or</strong>e, a study should beconducted <strong>to</strong> determine the feasibility of refueling constellation <strong>satellite</strong>s withminimum risk of collisions <strong>or</strong> explosions. The mother ship <strong>methodology</strong> satisfies anacceptable risk threshold by using different parking <strong>or</strong>bit than the target <strong>satellite</strong>s‘<strong>or</strong>bits, but the <strong>methodology</strong> needs m<strong>or</strong>e accurate assessment of the risk associatedwith each SRS rendezvous. Orbit change maneuvers need m<strong>or</strong>e propellant thanexecuting a rendezvous maneuver. A m<strong>or</strong>e careful passive method strategy such asdrifting in right ascension of the ascending node, small changes in <strong>or</strong>bit that wouldcause the SRS vehicles <strong>to</strong> drift differently than the target <strong>satellite</strong> and low-thrustpropulsion f<strong>or</strong> the <strong>or</strong>bit change can be used <strong>to</strong> make the <strong>or</strong>bital plane change shouldalso be investigated.F<strong>or</strong>matted: Font: (Default) Times New Rom


89REFERENCES1. Rodriguez H.M., Liou J.C., ―Orbital Debris : Past, Present, and Future.‖,Proceedings of American Institute of Aeronautics and Astronautics (AIAA),Annual Technical Symposium, 9 May 2008, Hous<strong>to</strong>n (TX), Webster (TX).Available at http://www.aiaa-hous<strong>to</strong>n.<strong>or</strong>g/uploads/Documents/pres041.ppt.2. United States Strategic Command (STRATCOM), Space Control and SpaceSurveillance Factsheet. Available at http://www.au.af.mil/au/awc/awcgate/usspcfs/space.htm.3. National Research Council, ―Orbital Debris : A Technical Assessment‖,National Academy Press, 1995, Washing<strong>to</strong>n, D.C.. Available athttp://books.nap.edu/books/0309051258/html/index.html.4. A Computer-Generated Image Comparison of Man-Made Objects. Available athttp://<strong>or</strong>bitaldebris.jsc.nasa.gov/pho<strong>to</strong>gallery/pho<strong>to</strong>gallery.html.5. NASA Orbital Debris Quarterly News, Volume 15, Issue 1, January 2011.6. Wright D., ―Colliding Satellites: Consequences and Implications.‖,Union of Concerned Scientists, 26 February 2009. Available athttp://www.ucsusa.<strong>or</strong>g/assets/documents/nwgs/SatelliteCollision-2-12-09.pdf.7. Rossi A., ―Population Models of Space Debris‖, International AstronomicalUnion, 2005, DOIdoi: 10.1017/S1743921304008956.8. Press release, ―Gokturk Reconnaissance and Surveillance Satellite Project.‖Contract Signature Under Secretariat of the Defense Industries, July 2009,Ankara/TURKEY. Available at http://www.finmeccanica.it/EN/Common/files/Holding/C<strong>or</strong>p<strong>or</strong>ate/Sala_stampa/Comunicati_stampa/Anno_2009/SSM_Gokturk_16_07_09_inglese.pdf .9. Turkish Air F<strong>or</strong>ce Official Website about Future Projects. Available athttp://www.hvkk.tsk.tr/PageSub/Calismalarimiz/Projeler/GokturkProjesi.aspx.10. Petro A.J., ―Techniques f<strong>or</strong> Orbital Debris Control.‖, Journal Of Spacecraft andRockets, Vol. 29, No. 2, pp. 260, March-April 1992.11. Spencer D.B., Luu K.K., Campbell W.S., S<strong>or</strong>ge M.E., Jenkin A.B., ―OrbitalDebris Hazard Assessment Methodologies f<strong>or</strong> Satellite Constellations.‖, Journalof Spacecraft and Rockets, Vol. 38, No. 1, pp. 120-125, January–February 2001.


9012. Finkleman D., Oltrogge D., ―Twenty-five Years, M<strong>or</strong>e <strong>or</strong> Less?‖, AIAA/AASAstrodynamics Specialist Conference, 2-5 August 2010, T<strong>or</strong>on<strong>to</strong>, OntarioCanada, Reference Number : AIAA 2010-7822.13. Space Systems - Determining Orbit Lifetime, Doc.No. : ISO DIS 27852,International Organization f<strong>or</strong> Standardization, 2009, Geneva, Switzerland.Available at http://aiaa.kavi.com/apps/group_public/download.php/1009/ISO_CDC_27852_(E) %20(2).pdf.14. Qureshi F.Z., Terzopoulos D., Jasiobedzki P., ―Cognitive Vision f<strong>or</strong> Au<strong>to</strong>nomousSatellite Rendezvous and Docking.‖, 9 th IAPR Conference on Machine VisionApplications, May 2005, Tsukuba Science City, Japan. Available atwww.cs.ucla.edu/~dt/papers/mva05/mva05.pdf.15. Kawano I., Mokuno M., Kasai T., Suzuki T., ―Results of Au<strong>to</strong>nomousRendezvous Docking Experiment of Engineering Test Satellite-VII.‖, ActaAstronautica Vol:53, Issue 1, pp. 1-8, July 2003. Available athttp://www.sciencedirect.com/science/article/pii/S0094576502001959.16. Karl A., ―Active Removal of Space Debris – Discussing Technical andEconomical Issues‖, IAC-06-B6.4.04.17. Burkhardt H., Sippel M., Krulle G., Janovsky R., Kassebom M., Lubberstedt H.,Romberg O., Fristsche B., ―Evaluation of Propulsion Systems f<strong>or</strong> Satellite Endof-LifeDe-<strong>or</strong>biting.‖, 38 th AIAA/ASME/SAE/ASEE Joint Propulsion Conference& Exhibit, 7-10 July 2010, Indianapolis, Indiana. Reference Number : AIAA2002-4208.18. Description of the GlobalStar System Handbook, GS-TR-94-0001 Revision E,27, 27 December 2000. Available at http://gsproductsupp<strong>or</strong>t.files.w<strong>or</strong>dpress.com/2009/04/description-of-the-globalstar-system-gs-tr-94-0001-rev-e-2000-12-07.pdf.19. IADC Space Debris Mitigation Guidelines, Inter-Agency Debris Co<strong>or</strong>dinationCommittee, IAD-02-01, Rev. 1, September 2007.20. Press Release f<strong>or</strong> Launch of Second Generation GlobalStar Satellites,http://www.globalstar.com/en/index.php?cid=7010&pressId=633, 20 Oc<strong>to</strong>ber2010Oc<strong>to</strong>ber 2010, Coving<strong>to</strong>n, L.A.21. Curtis H., ―Orbital Mechanics f<strong>or</strong> Engineering Students‖, Elsevier AerospaceEngineering Series, 2005, ISBN : 0 7506 6169 0.


9122. Nishida S., Kawamo<strong>to</strong> S., Okawa Y., Terui F., Kitamura S., ―Space DebrisRemoval System Using a Small Satellite.‖, Acta Astronautica Vol.:. 65,pp. 95-102, 2009.23. Robinson E.Y., ―Spacecraft f<strong>or</strong> Removal of Space Orbital Debris.‖,Patent number : US 6,655,637 B1, Date of Patent : 2 December 2003.24. Kessler D.J., Cour-Palais B.G., ―Collision Frequency of Artificial Satellites: TheCreation of a Debris Belt.‖, Journal of Geophysical Research, Vol. :83, No.: A6,1 June 1978.25. M<strong>or</strong>ring F., ―Changing the Game.‖, Aviation Week and Space Technology,pp. 23-25, 21 March 2011.26. Two Line Element Set Data (TLE) f<strong>or</strong> Non-functional GlobalStar Satellites, .Available at http://www.space-track.<strong>or</strong>g/perl/id_query.pl. Access date 03 April2011.27. Vallado D.A., ―Fundamentals of Astrodynamics and Applications.‖, SpaceTechnology Library, ISBN:0-7923-6903-3, Microcosm, Inc., 21 May 2001.28. Properties of Hydrazine Thrusters. Available athttp://cs.astrium.eads.net/sp/brochures/hydrazine-thrusters.29. COTS Hydrazine Propulsion Units. Available athttp://www.astrium.eads.net/en/who-is-astrium.30. Prussing J.E., Conway B.A., ―Orbital Mechanics‖, Oxf<strong>or</strong>d University Press 1993,New Y<strong>or</strong>k, ISBN : 0-19-507834-9.31. Types of Conic Sections. Available at http://en.wikipedia.<strong>or</strong>g/wiki/Conic_section.32. Seifert H., ―Space Technology‖, John, John Wiley and Sons Inc., 1959, NewY<strong>or</strong>k.


92APPENDIX ABASIC ORBITAL MECHANICS FOR SATELLITE REMOVALThe basis of the analytical description of the motion of bodies in space is acombination of two of New<strong>to</strong>n‘s lawLaw: the second Second law Law of motionMotion and the law Law of gravitationGravitation.New<strong>to</strong>n‘s second Second law Law of motion Motion can be expressed as:⃗ ( ⃗⃗) (A.1)That is, the external f<strong>or</strong>ce applied <strong>to</strong> a body is equal <strong>to</strong> the time rate of change of thelinear momentum of the body.New<strong>to</strong>n‘s law Law of gravitation Gravitation may be expressed as:⃗ . ⃗ / (A.2)stating that the f<strong>or</strong>ce on body 1 is due <strong>to</strong> the attraction of body 2, varying directlywith the product of their masses, and inversely with the square of the separationdistance r, where the direction of the unit vec<strong>to</strong>r is given by ⃗ ⁄ , and ⃗ locates m 2 interms of m 1 . G is the Universal constant which has the value6.67259 x 10 -11 m 3 kg -1 s -2 .A.1 Equations of Motion f<strong>or</strong> the n-Body ProblemIn space, all celestial objects are interacting with each other. Astronomers andmathematicians want <strong>to</strong> solve a problem: Find find the positions and velocities of thebodies at any other time from given initial positions and velocities. It is clearly a verypractical problem <strong>to</strong> solve f<strong>or</strong> the attractional f<strong>or</strong>ce of the Sun, all the planets andmoons in the solar system acting on each other, and also including <strong>or</strong>biting spacecraft.If ⃗⃗⃗⃗ represents the position of a body, whose mass is , with respect <strong>to</strong> the <strong>or</strong>igin Oof an inertial reference frame, as shown in Figure A.1 30 , the position of the j th masswith respect <strong>to</strong> the i th mass can be designated ⃗ , where;


93⃗ ⃗ ⃗ , i, j =1,2,3,…,n (A.3)Figure A.1 Relative Position in an Inertial Frame.The attraction of the i th body is determined by the attraction of the n-1 other bodiesacting on it. Using equation Equation (A.1) and (A.2) and summing over the systemof masses yields:⃗ ̈ ⃗ ∑ ⃗ (A.4)Now, since ⃗in the system <strong>to</strong> yield:⃗ , equation Equation (A.4) can be summed over all of the bodies∑ ⃗ ̈(A.5)which can be summed over all of the bodies <strong>to</strong> yield:∑ ⃗ ̈ ⃗ , a constant vec<strong>to</strong>r, (A.6)then integrated <strong>to</strong> yield:


94∑ ⃗ ̇ ⃗ ⃗ (A.7)Defining the center of mass,⃗∑⃗⁄ ∑, (A.8)equation Equation (A.7) determines the motion of the system center of mass, which isrectilinear and from equation Equation (A.6) at constant velocity 30 . The linearmomentum of the system is thus conserved, which is expected since the system ofbodies is subject <strong>to</strong> no net external f<strong>or</strong>ce.A.2 The Two-Body ProblemWhile the general f<strong>or</strong>mulation would be the best approach, it is known thatsystems consisting of three objects <strong>or</strong> m<strong>or</strong>e do not yield closed-f<strong>or</strong>m solutions. Hence,it is necessary <strong>to</strong>, From from equation Equation (A.4),⃗ ̈⃗ ̈ ⃗̈ ⃗ ⃗ (A.9)Or<strong>or</strong>:⃗ ̈( )⃗ (A.10)<strong>or</strong>:⃗ ̈ ⃗ (A.11)where, μ≡G(m 1 +m 2 ) is the gravitational constant f<strong>or</strong> the particular two-body problemand the subscript notation is dropped because it is no longer necessary.Since μ completely characterizes the system, solutions can be developed <strong>to</strong>these two-body problems in terms of μ. In many applications the mass of the centralbody is much larger than the ―<strong>or</strong>biting mass‖ (m 1 ≫m 2 ), and in this case μ can beapproximated as Gm 1 . Thus each large celestial body has its own cataloged value of μ.


95equation Equation ( A.11), governing the position ⃗ of m 2 relative <strong>to</strong> m 1 isnonlinear, but several constant constraints on the motion exist. F<strong>or</strong> example, takingthe vec<strong>to</strong>r product;:⃗⃗ ̈ ⃗ ⃗ , (A.12)which can be integrated <strong>to</strong> give,⃗⃗ ̇ ⃗⃗ , a constant vec<strong>to</strong>r. (A.13)The vec<strong>to</strong>r ⃗ is then n<strong>or</strong>mal <strong>to</strong> the constant vec<strong>to</strong>r ⃗⃗. This implies that the relativemotion lies in a fixed plane in space called the <strong>or</strong>bit plane, with ⃗⃗ as its characteristicn<strong>or</strong>mal vec<strong>to</strong>r. Figure A.2 illustrates the position vec<strong>to</strong>r ( ⃗) and the velocity vec<strong>to</strong>r ( )are in the same plane and their cross product is perpendicular <strong>to</strong> that plane 30 .Figure A.2 Spacecraft Path around the Earth in Orbital Plane.


96Now, <strong>to</strong> solve equation Equation ( A.11), take the cross product with the constantvec<strong>to</strong>r ⃗⃗;⃗ ̈ ⃗⃗ ( ⃗ ⃗⃗) ⃗ ( ⃗ ⃗) ̇[ ⃗( ̇ ⃗ ⃗) ⃗( ⃗ ⃗)] ̇(A.14)<strong>or</strong>,⃗⃗ ̈ ⃗⃗ ( ̇ ⃗ ̇) (A.15)As shown in Figure A.3, the components of the velocity vec<strong>to</strong>r are ⃗ ̇ ̇ ̂ and⃗ ̇ ̇ ̂ , where ̂ and ̂ are the radial and tangential unit vec<strong>to</strong>rs respectively,and θ is the angular position of the radius vec<strong>to</strong>r. Substituting the components of thevelocity vec<strong>to</strong>r in<strong>to</strong> equation Equation (A.13) yields:⃗⃗ ̇ ⃗⃗ ( ⃗ ̂ ) ( ̇ ̂ ̇ ̂ ) ̇ ̂ (A.16)As we know ̂⃗⃗and from equation Equation (A.16) the magnitude of the specificangular momentumcan be written as;̇ (A.17)


Figure A.3 Spacecraft Velocity Components in Orbital Plane.97


98Figure A.4 Area Swept by Position Vec<strong>to</strong>r During during Time Interval t.Figure A.4 represents the area swept out by the position vec<strong>to</strong>r during aninfinitesimal time interval. The area of triangle OQS can be expressed ascan be written as; Aand it∆ ( ∆ ) ∆ ( ∆ ) ∆∆∆(A.18)Taking the limit of equation Equation (A.18) and substituting equation Equation(A.17), the rate at which area is swept is given by:(A.19)


99A vec<strong>to</strong>ral approach was used <strong>to</strong> integrate equation Equation (A.11) in <strong>or</strong>der <strong>to</strong>Robtain the <strong>or</strong>bit trajec<strong>to</strong>ry f<strong>or</strong>mula. Recall that ˆr , and taking the time derivativeRof the unit vec<strong>to</strong>r yields:̂⃗ ̇ ̇ ⃗ ⃗ ̇ ̇ ⃗ ( ⃗ ⃗) ⃗ ̇ ( ⃗ ⃗) ̇ ⃗(A.20)Now note that:. ⃗ /⃗ ̇⃗ ̇(A.21)Theref<strong>or</strong>e, equation Equation (2.15) becomes;⃗ ̈ ⃗⃗ . ⃗ / (A.22)which may be integrated directly <strong>to</strong> yield;⃗ ̇ ⃗⃗ . ⃗ ⃗/ (A.23)where ⃗ is a dimensionless vec<strong>to</strong>r constant of integration. Because ⃗ is n<strong>or</strong>mal <strong>to</strong> ⃗⃗, ⃗must lie in the <strong>or</strong>bit plane. Taking the dot product of ⃗ with equation Equation (A.23)yields a scalar equation:⃗ ( ⃗ ̇ ⃗⃗) ⃗ 2 . ⃗ ⃗/3 (A.24)<strong>or</strong>;( ⃗ ⃗) ̇ ⃗⃗ ( ( ⃗ )) ( ) (A.25)where the angle θ is defined as the angle between ⃗ and ⃗. Solving f<strong>or</strong> r yields;⁄(A.26)which is the equation of a conic section in polar co<strong>or</strong>dinates with the <strong>or</strong>igin of theco<strong>or</strong>dinate frame at the focus of the conic section. From equation Equation (A.26) we


100see that r will have its minimum value when θ=0, that is, the vec<strong>to</strong>r ⃗ represents thedirection of minimum separation distance.equation Equation (A.26) represents a conic section because it is exactly thesame equation which results from the f<strong>or</strong>mal definition of a conic section and types ofconic sections is shown on Figure A.5 31 .Figure A.5 Types of Conic Sections: (1) Parabola (2) Circle – Ellipse (3) Hyperbola.In mathematics, a conic section (<strong>or</strong> just a conic) is a curve obtained byintersecting a cone (m<strong>or</strong>e precisely, a right circular conical surface) with a plane. Inanalytic geometry, a conic may be defined as a plane algebraic curve of degree two. Itcan be defined as the locus of points whose distances are in a fixed ratio <strong>to</strong> somepoint, called a focus, and some line, called a directrix.Note that we have succeeded in obtaining a closed-f<strong>or</strong>m solution <strong>to</strong> thenonlinear equation of motion (A.11). However, the independent variable in thesolution is not time, but the polar angle θ, which is called true anomaly. F<strong>or</strong>tunately,we now have a geometrical description of the <strong>or</strong>bit; one can calculate r f<strong>or</strong> all valuesof θ if the constants μ, h and e (also called eccentricity) are given. However, we have


101lost track of where the <strong>or</strong>biting mass is at a specified time. The missing timeinf<strong>or</strong>mation is also evident in the fact that, although the solution <strong>to</strong> equation (A.11)requires six integration constants, our two vec<strong>to</strong>r constants ⃗⃗ and ⃗ provide only fiveindependent constants due <strong>to</strong> the fact that ⃗⃗ ⃗ .A.3 Elliptical OrbitsIn celestial mechanics an elliptic <strong>or</strong>bit is a Kepler <strong>or</strong>bit when the eccentricity isgreater than 0 and less than 1 (thus excluding the circular <strong>or</strong>bit). In a wider senseelliptic <strong>or</strong>bit is a Kepler <strong>or</strong>bit with negative energy. The equation governing the conicsection described using equation Equation (A.26) is:⁄(A.27)where r represents the magnitude of ⃗, e represents eccentricity and θ represents thetrue anomaly, as shown in Figure A.6. Also shown in the figure is the semi-maj<strong>or</strong> axisa, the semi-min<strong>or</strong> axes b represents , the semi-latus rectum p and the distance betweenthe two foci 2 c.


102Figure A.6 Elliptical Orbit Around around the Earth.Smallest ⃗ vec<strong>to</strong>r and so smallest magnitude of ⃗ vec<strong>to</strong>r have <strong>to</strong> at the periapsis point.At periapsis point true anomaly (θ) is equal <strong>to</strong> 0° so equation Equation (A.27) yields;:⁄ ⁄(A.28)Largest The largest ⃗ vec<strong>to</strong>r and so thus the largest magnitude of ⃗ vec<strong>to</strong>r have <strong>to</strong> atthe apoapsis point. At apoapsis point true anomaly (θ) is equal <strong>to</strong> 180° so equationEquation (A.27) yields;:Comment [KBS3]: Have <strong>to</strong> do what?⁄ ⁄(A.29)We can calculate eccentricity by dividing equation Equation (A.28) and eEquation(A.29);


103⁄⁄( ) ( )(A.30)Obviously we can see at Figure (A.6), adding length of periapsis and apoapsis <strong>to</strong> eachother, we have twice times of semi-maj<strong>or</strong> axes (2a). If we add equation Equation(A.28) <strong>to</strong> equation Equation (A.29) and divided by 2, we can calculate semi-maj<strong>or</strong>axes;⁄ ⁄(A.31)An alternative f<strong>or</strong>m of equation Equation (A.27) can be written by using the semimaj<strong>or</strong>axis definition.(A.32)Comparing equation Equation (A.27) and equation Equation (A.32) yields thespecific angular momentum, h, as a function of the masses and <strong>or</strong>bit geometry;√, ( )- (A.33)When true anomaly (θ) equals <strong>to</strong> 90°, equation Equation (A.32) yields;( ) (A.34)and as shown and defined at Figure (A.6), this distance is referred <strong>to</strong> as the semi-latusrectum (p). And from equation Equation (A.32),


104(A.35)comparing equation Equation (A.27) and Eequation (A.35); the specific angularmomentum (h)and the semi-latus rectum (p) are related by;:(A.36)Figure A.7 Unit Vec<strong>to</strong>r Definitions.With reference <strong>to</strong> Figure A.7, which illustrates the motion of m 2 and as seen anobserver on m 1, we see that⃗ ̇ ̇ ̂ ̇ ̂ (A.37)


̇105where the unit vec<strong>to</strong>rs rotate with the radius vec<strong>to</strong>r. Then, from equation Equation(A.27) we have⃗⃗ ⃗ ⃗ ̇ ( ̂) ( ̇ ̂ ̇ ̂ ) ̇ ̂ (A.38)However, that the differential element of area swept out by the radius vec<strong>to</strong>r as itrotates through an angle of dθ is, dA=(1/2)r 2 d . Theref<strong>or</strong>e, this implies that;= constant (A.39)That is, the rate at which the radius vec<strong>to</strong>r sweeps out area is a constant, and <strong>or</strong>bitalangular momentum is conserved. This verifies Kepler‘s second Second lawLaw.Besides, the time required f<strong>or</strong> one complete <strong>or</strong>bit, the <strong>or</strong>bital period T is;⁄(A.40)<strong>or</strong>;√( )(√ )√( )√ (A.41)A.4 The Orbit in SpaceSix constants are required <strong>to</strong> completely specify the <strong>or</strong>bit of a particular<strong>satellite</strong> with respect <strong>to</strong> the attracting center. In the most elementary f<strong>or</strong>m the sixcomponents of the state vec<strong>to</strong>rs ⃗ and ⃗⃗ at a specified time will serve this purpose.Unf<strong>or</strong>tunately, ⃗ and ⃗⃗ do not directly yield much inf<strong>or</strong>mation about <strong>or</strong>bit. F<strong>or</strong>example, they do not explicity tell us what type of conic the <strong>or</strong>bit present. So anotherset of six constants, the <strong>or</strong>bital elements, is much m<strong>or</strong>e descriptive of the <strong>or</strong>bit.


106ZSatelliteR e Perigeeh iInertialFrameYN XFigure A.8 Earth Centered Inertial Frame and Orbital Elements.In Figure A.8, <strong>or</strong>bital elements are shown which we did nothave not yet beendefined them bef<strong>or</strong>e. We can start <strong>to</strong> define inertial frame: Inertial frame, that iscommonly used, can be defined in terms of X, Y and Z. The X and Y axes lie in theEarth‘s equa<strong>to</strong>rial plane and the Earth spins around the Z axis. The X axis defined in adirection from the Earth <strong>to</strong> the Sun at the vernal Vernal equinox Equinox (21 March).This direction points <strong>to</strong> the constellation of Aries, it is called Aries direction. The Zaxis is in the n<strong>or</strong>therly direction and along the Earth‘s spin axes. It is at the angle of23°27ˈ 8ˈ ˈ <strong>to</strong> the n<strong>or</strong>mal of the ecliptic plane. The Y axes makes up a right handed<strong>or</strong>thogonal set with X and Z axes.Inclination (i) is the angle between the ⃗⃗ unit vec<strong>to</strong>r (Z axes) and the angularmomentum vec<strong>to</strong>r ( ⃗⃗).Longitude of the ascending node (Ω) is the angle, in the fundamental plane,between the ⃗ unit vec<strong>to</strong>r (X axes) and the point where the <strong>satellite</strong> crosses throughthe fundamental plane in n<strong>or</strong>therly direction measured counterclockwise when viewedfrom the n<strong>or</strong>th side of the fundamental plane.


107Argument of periapsis (ω) is the angle, in the plane of <strong>satellite</strong>‘s <strong>or</strong>bit,between the ascending node and the periapsis point, measured in the direction of the<strong>satellite</strong>‘s motion.A.5 Position in an Elliptical Orbit as a Function of TimeWe can calculate time of flight on the elliptical <strong>or</strong>bit with an auxiliary circlewhich is radius is equals <strong>to</strong> elliptical <strong>or</strong>bit‘s semi-maj<strong>or</strong> axes (a) which is shown inFigure A.9 32 . We can use geometric approaches and after some manipulations, wehave a relation between true anomaly (θ) and eccentric anomaly (E);√ (A.42)and√ (A.43)Figure A.9 Definition of Eccentric Anomaly.


108motion is;:The mean angular rate of the <strong>satellite</strong>, symbolized by n, and also called mean√(A.44)With the help of eccentric anomaly, time of flight of the <strong>satellite</strong> between twopoints can be defined as;:√ ( ) (A.45)Theref<strong>or</strong>e, we may define an auxiliary angle M=n t, called mean anomaly, whichrepresents physically the angular displacement of a fictitious <strong>satellite</strong> that travels atthe mean angular rate n as opposed <strong>to</strong> the rate ̇. In terms of mean anomaly can bewritten as;:√(√ ( )) (A.46)


109VITAGOKSEL GURGENBURANF<strong>or</strong>matted: Font: BoldDEGREESBachel<strong>or</strong> of Science : Electronic EngineeringTurkish Air F<strong>or</strong>ce Academy, Yesilkoy/Istanbul, August 2005August 2005PROFESSIONAL CHRONOLOGY Air Technical School Commands, Gaziemir/Izmir, Human Resources OfficerCourse, September 2006 - March 2007 3 rd Air Maintenance and Supply Center, Etimesgut/Ankara, Human ResourcesOfficer, May 2007-August 2009. Turkish Air F<strong>or</strong>ce Academy, Yesilkoy/Istanbul - Aerospace EngineeringDepartment, Old Dominion University, N<strong>or</strong>folk, Virginia, M.S. Student,September 2009-August 2011.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!