Top / EN / SpaceDebris / OrbitalAnalysis


_ Numerical Analysis of Orbital Motion

_ Space Debris Environment (in A.D. 2000)

This picture shows approximately 9,000 catalogued objects.
Blue: Operational Satellites
CYAN: Abandoned Satellites
YELLOW: Spent Rocket Bodies
RED: Space Debris

fileView the larger image
filePlay the animation (2 hours, 600x speed)

_ Motion of Objects in LEO (Low Earth Orbit)

filePlay the animation (10 minutes, 30x speed)

_ Motion of Geosynchronous Objects

Abandoned geosynchronous objects tend to have orbital inclination bacause of gravitational accelerations from the sun and the moon, after they lose orbital control. As a consequence, it is warned that debris may hit a operational satellite in GEO, when they cross the equatorial plane twice in a day.

GEO_thumb.png *1
fileGeocentricí╩2 hour, 1500x speed)
fileGeographic (1 day, 18000x speed)

_ Hazard Analysis after Break-up Event

_ Fragment Cloud Evolution after a Hypothetical Collision

If a geosynchronous satellite breaks up (explosion or collision), it causes huge number of debris as we call "Debris Cloud". The debris cloud will spread all over the GEO, and will remain forever around GEO.

FragCldEvo-s.giffileAnimated GIF (715KB)

_ Debris from Chinese ASAT Test

China tested ASAT (Anti-SATellite weapon) at 22:28 UTC Jan. 11, 2007. They launched an ASAT missile to hit a Chinese old weather satellite Feng Yun 1C (FY-1C). FY-1C was broken into a huge numbers of orbital debris.

Pictures below show debris environment after the ASAT test (Jan. 29). Approximately 500 debris from FY-1C are tracked thier orbit.

All debris in LEO after ASAT test
fileHigh Resolution Picture

Debris from Feng Yun 1C
&ref(): File not found: "fengyun_1c_070129-s.png" at page "SpaceDebris/OrbitalAnalysis";
fileHigh Resolution Picture

_ IRIDIUM33 - COSMOS2251 Collision

2009/02/10 16:56(UTC)
Above Siberia, Estimated Altitude: 788km

  • Now, the estimated number of fragments and the future orbit evolution are being investigated by using LEODEEM and NASA Standard Breakup Model.

&ref(): File not found: "SatelliteCollision_090211_STA.jpg" at page "SpaceDebris/OrbitalAnalysis";
Animation (Youtube)

  • Ground track before collision (Simulation with Orbitron)
    &ref(): File not found: "SatelliteCollision_090211_s.png" at page "SpaceDebris/OrbitalAnalysis";
    &ref(): File not found: "SatelliteCollision_090211.gif" at page "SpaceDebris/OrbitalAnalysis";
  • TLE
1 22675U 93036A   09041.75659016 -.00000010  00000-0  60222-5 0  7421
2 22675 074.0357 017.1729 0016015 095.9865 264.3113 14.31135598817592
1 24946U 97051C   09041.76123952  .00000148  00000-0  45664-4 0  4757
2 24946 086.3989 121.2960 0002253 089.6115 270.5342 14.34220263597475
  • Estimated Info. from TLE Data
    SatelliteIRIDIUM 33COSMOS 2251
    Time2009/02/10 16:56:00 UTC
    LongitudeE 97.8855 degE 97.8924 deg
    LatitudeN 72.5175 degN 72.4987 deg
    Altitude788.686 km788.588 km
    Velocity (Speed)7.467 km/s7.472 km/s
    Velocity (Azimuth)13 deg117 deg
  • Relative Velocity at Collision Point
    &ref(): File not found: "Figure_RelativeVelocity_090211.jpg" at page "SpaceDebris/OrbitalAnalysis";

Red dots in this picture are not real catalogued objects but represent theoretical distribution of fragments from Titan IIIC transtage which exploded in 1992.

Link: EN/Activities(525d) EN/SpaceDebris(582d)
Last-modified: 2009-02-18 (Wed) 16:34:04 (3138d)