Documentation

Please login to see this help content.
Please login to see this help content.
Why did you add period, apogee, perigee, and semi-major axis to the TLE and TLE_latest API classes and how do you calculate them?
We added semi-major axis, period, apogee, and perigee to the TLE and TLE_latest API classes so that users can filter their queries by these values, download only the data they need, and decrease the amount of the site's bandwidth that they use. Now, all the orbital elements in the satellite catalog (SATCAT) are available in the TLE class. However, the value of the same element (e.g. apogee) may not match exactly.

Every TLE already displays a value for the object's mean motion ("n") and eccentricity ("e"), so we derive these additional four values using the following calculations:

period = 1440/n
Using mu, the standard gravitational parameter for the earth (398600.4418),
semi-major axis "a" = (mu/(n*2*pi/(24*3600))^2)^(1/3)
Using semi-major axis "a", eccentricity "e", and the Earth's radius in km,
apogee = (a * (1 + e))- 6378.135
perigee = (a * (1 - e))- 6378.135

What is a TLE checksum?
A checksum is rudimentary means of detecting errors which may have been introduced during data transmission or storage. In TLEs and 3LEs, the last digit on line 1 and line 2 is a simple modulo-10 checksum. To calculate it, add the values of the numbers in the first 68 characters on each line—ignoring all letters, spaces, periods, and plus signs—and assign a value of 1 to all minus signs. The checksum is the last digit of that sum (the “ones” place) and is appended in the 69th character position.

Do all TLEs have checksums?
Yes, Space-Track.org has updated its code to include checksums for all current and historical TLEs/3LEs including over 8 Million TLEs/3LEs that did not previously include one. This provides users with better data integrity and rudimentary error checking.

Why do all TLEs/3LEs have a constant element number of 999?
To eliminate confusion caused by reusing element numbers after 999 has been reached. For example, object number 11 has used the same element numbers over 15 times throughout its life cycle.

What is a "well-tracked object" and how do I recognize it on Space-Track.org?
A "well-tracked object" is an object in orbit with uncertainty surrounding its origin. In order to better manage congestion caused by space debris and enhance spaceflight safety, USSTRATCOM catalogs and publishes a number of these objects on Space-Track.org. For these objects, Country Code & Launch Site values are both UNKN ("Unknown"); The International Designator format in the catalog is YYYY-000A and in TLEs is YY000A (year cataloged, '000' Launch #, & next alpha in sequence, e.g. 2014-000B, 2014-000C, etc.); The Launch Date is 1 January of the year that the object is cataloged.

What changed with Radar Cross Section (RCS) and why?
Did RCS values change?
USSTRATCOM has added scaling of RCS values to the SATCAT. Until 18 Aug 14, there was a dual-feed of both current values (RCSVALUE) & scaled values (RCS_SIZE). RCS_SIZE has 3 values: Small (< 0.1m2), Medium (0.1m2 – 1m2), & Large (>1m2). Space-Track began showing only scaled values on 18 August 2014 (with RCSVALUE showing a static value of 0 in satcat, satcat_debut, & decay classes). There is no change to CDM spaceflight safety notification info or procedures.

Why did USSTRATCOM revising radar cross section (RCS) information published on Space-Track.org?
USSTRATCOM simplified the process of reporting RCS information on space objects. The Conjunction Data Message (CDM) provides spaceflight safety information (including RCS) in a single product. Previously, users used two products, a Conjunction Summary Message (CSM) and the Satellite Catalog (SATCAT).

Will there be any change to current spaceflight safety information or procedures?
No. The Conjunction Data Message (CDM), which is sent to owner/operators to warn of a potential collision, contains the actual RCS to assist satellite owners/operators in spaceflight safety decision-making.

My organization was using RCS values. Is there a way to still receive that information?
Yes. Formal SSA sharing partners can receive additional information. Contact USSTRATCOM at stratcom.offutt.j51.mbx.j513@mail.mil for more information on SSA Sharing Agreements.

When did this change take effect?
The system switched to full-time scaled values on 18 Aug 14.

Do satellite owners/operators and other interested parties have opportunities to influence the implementation process?
USSTRATCOM and JFCC Space will accept feedback throughout the transition process. Contact admin@space-track.org to provide feedback on Space-Track.org, or stratcom.offutt.j51.mbx.j513@mail.mil for information about how to become a formal partner with USSTRATCOM.

What timezone is all date/time data in?
All date/time data is stored, delivered, and displayed in UTC.

What's new on the site?
Please engage us on our social media sites: facebook, Google+, or twitter.

Why is there a satellite catalog entry for object number [12345], but no orbital data for that object or TLEs for that object?
The answer from our data provider:
   "JFCC SPACE cannot post elsets for every man-made object orbiting the earth on www.Space-Track.org.

   Reasons include but are not limited to:
      - National security reasons
      - Some objects are too small for the sensors to consistently track
      - Some objects decay before the JSpOC can collect enough information to post a TLE
      - Gaps in sensor coverage

   Regardless whether an object's elset/TLE is posted on the website or not, JFCC SPACE screens all objects at least daily and notifies the operator if that object is predicted to approach another object."

What is the minimum size of objects that are maintained in the satellite catalog?
10 centimeter diameter or "softball size" is the typical minimum size object that current sensors can track and the JSpOC maintains in the catalog.

Why does the JSpOC switch elsets after a launch?
The answer from our data provider:
   "After a launch, the JSpOC has a time requirement to identify objects from the launch.

   For a multi-payload launch, typically the payloads are bunched together, making separation difficult, while the rocket body is generally drifting away and is easier to produce an elset. This elset is then used as a basis for the JSpOC and sensor network to track the other objects.

   Once all objects are catalogued, they will not be renamed until the JSpOC receives positive identification. At that point, once all payloads are known, the sensor network requires listing the payloads first before any rocket body or other launch debris.    The JSpOC recognizes this can be frustrating for users; however, the sensor network takes priority. The only way to solve this is to not send the elsets to the Space-Track.org website until after identification, which could take hours or possibly days after a launch."

Why have I not heard a response back from the JSpOC after reporting a mis-tagged object to jspoc.ssasharing@us.af.mil?
The answer from our data provider:
   "Positively identifying all objects after launch is challenging and may result in accidental misidentification of some objects.

   As years pass on, it becomes increasingly difficult to move historical data within the JSpOC system. The JSpOC has to validate all possible mis-tagging and receive clarification from multiple sources, i.e. signals, RCS data, etc. While the JSpOC may be aware of the error, multiple users of the official data would have to be notified, and on occasion, might have to initiate changes to their system to line-up with the JSpOC data before the JSpOC can initiate the change. Depending how much time has passed since launch, it may take a while to move all the appropriate data into the correct object.

   The JSpOC appreciates all notifications of possible mis-tagging, but please realize their primary focus is tracking objects for collision avoidance so the extra duty of cross checking mis-tagging reports can be placed at a lower priority at times."

How does the data provider come up with space object's common name?
Typically, the owner/operator reports the common name to our data provider. If our system already has a similar name, our data provider will adapt it.

If our data provider is not told what the common name is, he/she will get the name from either the launch team or open sources. Some common names may be abbreviated or truncated due to character limitations in that data field.

What criteria are used to determine whether an orbiting object should receive a catalogue number and International Designation?
There are three primary considerations when deciding to catalog an orbiting object:
We must be able to determine who it belongs to, what launch it correlates to, and the object must be able to to be maintained (tracked well).

I noticed a TLE with an epoch a few days in the future. Aren't TLEs supposed to be timing off the LAST ascending node pass prior to the current observations?
TLEs can contain future epochs.

About 20 satellites are categorized as "multi-day objects" because their period is so large. Consequently, our data provider propagates the epoch into the future based on perigee to enable better tracking by available sensors when the object finally comes back into view.

An example is Object 10370 with a 5683.23 minute period.
What is the JSpOC's reporting criteria for conjunction data messages (CDMs) in the following orbital regimes:
Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Highly Elliptical Orbit (HEO), and Deep Space (DS)?

For further information on orbital mechanics see: link

Apogee.
Point in the orbit where an Earth satellite is farthest from the Earth. Units are kilometers. link
Argument of Perigee (Degrees).
The angle between the ascending node and the orbit's point of closest approach to the earth (perigee). link
B* Drag Term.
Also called the radiation pressure coefficient. Units are earth radii^-1. The last two characters define an applicable power of 10. link
Catalog Change Report.
Report that details the changes (launches, additions, decays and updates) to the satellite catalog (SATCAT). Now parts 4 & 5 of the SSR
Catalog Number.
Sequential number assigned by US Air Force as objects are cataloged. Synonyms: Satellite Catalog Number, NORAD_CAT_ID, and OBJECT_NUMBER. link
Celestial Equator.
It is a projection of the terrestrial equator out into space. link
Checksum.
Sum of all of the characters in the data line, modulo 10. link
Common Name.
Also known as OBJECT_NAME, this is simply the name associated with the satellite. link
Complete Data Files.
See:link
Conjunction Assessment (CA).
The process of predicting and reporting the close approaches between Resident Space Object (RSOs) or between launch vehicles and RSOs. link
Conjunction Data Message (CDM)
CCSDS Recommended Standard message format for exchanging spacecraft conjunction information between originators of Conjunction Assessments (CAs) and satellite owner/operators and other authorized parties.
Conjunction Summary Message (CSM) - DEPRECATED.
The CSM is a fixed-format ASCII formatted message which contains information about a predicted conjunction between space objects.
Country.
The nation or group that has responsibility for an object
Current Catalog Files.
See:link
Debris.
Any object with the string 'DEB' or 'COOLANT' or 'SHROUD' or 'WESTFORD NEEDLES' in the SATCAT object common name. link
Decay.
The lessening of the eccentricity of the elliptical orbit of an artificial satellite. link
Decay Date.
Date object reentered the earth's atmosphere in YYYY-MM-DD format. link
Decay Message Types.
SATCAT - Historical.
Decay Entry - Historical.
TIP Message - Prediction.
60day Decay - Prediction.
Eccentricity.
A constant defining the shape of the orbit (0=circular, Less than 1=elliptical). link
Element Number.
The ELSET number is a running count of all TLEs generated by the JSpOC for this object. link
Element Set (ELSET).
See: Two Line Element set.
Element Set Epoch.
The first two digits ('13') indicate the year. Add 1900 for years >= 57, and 2000 for all others. The remainder of the field ('236.56031392') is the Julian day of the year.link
Epoch.
The specific time at which the position of a satellite is defined. link
First Derivative of the Mean Motion.
Is the daily rate of change in the number of revolutions the object completes each day, divided by 2. Units are revolutions/day. link
Geosynchronous Report.
Report generated using search parameters of satellite period between 1430-1450 minutes. link
International Designator.
Also known as COSPAR designation or NSSDC ID, this is one format for uniquely identifying an object. link
JFCC SPACE.
The Joint Functional Component Command for Space is a component of U.S. Strategic Command and is responsible for executing continuous, integrated space operations to deliver theater and global effects in support of national and combatant commander objectives. link
Latest Data.
Displays the latest TLE for the object. link
Latest ELSET.
Displays the last 5 TLEs for the object. link
Launch Date.
Date object was launched in YYYY-MM-DD format. See:link
Launch Site.
See:link
Laser Clearinghouse (LCH).
An organization within JFCC Space that supports safe and responsible laser activities consistent with the needs of national defense. See: LCH Acronyms
Mean Anomaly (degrees).
The angle, measured from perigee, of the satellite location in the orbit referenced to a circular orbit with radius equal to the semi-major axis. link
Mean Equinox.
The direction to the equinox at a particular epoch, with the effect of nutation subtracted. link
New Registered User Application.
On-line application submitted in order to obtain a user account on Space-Track.org link
Orbit Mean-Elements Message (OMM).
An approved international standard for a mathematical representation of a satellite’s mean orbit IAW CCSDS 502.0-B-2 Orbit Data Messages Blue Book .
Orbital Data Request (ODR).
The ODR is the form submitted by requesters asking for SSA services or information. link
Orbital Data Request Process.
The procedures used by Space-Track.org users to request Space Situational Awareness (SSA) advanced services support. link
Orbit Inclination (Degrees).
The angle between the equator and the orbit plane. link
Owner/Operator (O/O).
The designated control center or agency that is the focal point for operational control of a satellite payload, and/or vehicle, and/or ground site. The owner/operator interfaces with USSTRATCOM and/or JFCC SPACE and is generally the location where the operations center is located for a given space system.
Payload.
Any object not classified in the SATCAT as a rocket body or debris is considered a payload. link
Perigee.
Point in the orbit where an Earth satellite is closest to the Earth. Units are kilometers. link
Period.
The number of minutes an object takes to make one full orbit. link
Precedence.
In the Decay class, lower PRECEDENCE values indicate more recent data. link
Predicted Decay Location.
In the TIP class, LAT / LON values show the location above which an object is predicted to arrive at 10km altitude during its descent, not the predicted Earth impact location.
Predicted Decay Time.
The time that an object is predicted to reach its decay location. Format: GMT Date (YYYY-MM-DD, HH:MM:SS) +/- XX Hours.
Radar Cross Section (RCS).
A measure of how detectable an object is by radar, measured in square meters. link
Recent Satellite Decays.
A listing of recent satellite decays on Space-Track.org. link
Revolution Number at Epoch.
The number of orbits the object has completed at Epoch Time. link
Right Ascension of Ascending Node (degrees).
Is the angle of the ascending node measured EAST of the vernal equinox along the celestial equator. link
Rocket Body.
The propulsion unit(s) used to deploy satellites into orbit. These are cataloged differently from standard debris because they can have mechanisms or fuel on board that can affect the orbital behavior of the rocket body even after long periods of time. Rocket bodies are also constructed to endure high temperatures and stresses associated with launch so they have a greater probability of surviving reentry and require closer attention than most debris. Rocket Bodies are any object which contains the strings 'R/B' or 'AKM' (Apogee Kick Motor) or 'PKM' (Perigee Kick Motor) but not 'DEB' (Debris) in the SATCAT object common name. link
Satellite.
Any object in orbit around the Earth. Used interchangeably with 'resident space object'. However, commonly and mistakenly used to mean payload. Both a piece of debris and the moon are satellites.(SI 534-3)
Satellite Box Score.
Accounting of man-made objects that have been or are in orbit by country. (SI 534-3) link
Satellite Catalog Number.
Sequential number assigned by US Air Force as objects are cataloged. Synonyms: Catalog Number, NORAD_CAT_ID, and OBJECT_NUMBER. link
Satellite Catalog (SATCAT).
A catalog of satellite positional data maintained by the JSpOC.(SI 534-3) link
Satellite Situation Report.
Listing of those satellites (objects) currently in orbit and those which have previously orbited the Earth. Some objects are too small or too far from the Earth's surface to be detected; therefore, the Satellite Situation Report does not include all man-made objects orbiting the Earth. link
Second Derivative of the Mean Motion.
Measures the second time derivative in daily mean motion. link
SpaceDataSource.org.
A deactivated website. Its file sharing functionality was added to space-track.org in 2014.
Space-Track.org.
The website that provides unclassified SSA services and information. Space-Track.org is managed, maintained and administered by JFCC SPACE. link
Space.
The area above the lowest altitude that permits a vehicle to orbit the Earth without entering the earth's atmosphere. That altitude is approximately 100 kilometers (62 miles). link
Space Surveillance Data.
Data derived from the observation of space and activities occurring in space. link
Space Weather.
The conditions and phenomena in space and specifically in the near-Earth environment that may affect space assets or space operations.link
SI 534-3.
USSTRATCOM Strategic Instruction (SI) 534-3, Sharing Space Situational Awareness (SSA) Information, 18 January 2013. Establishes standard guidance for providing unclassified SSA information to United States Government (USG) agencies (including organizations supporting the USG under contract) and non-USG entities.
Tracking and Impact Prediction (TIP) Message.
Projected satellite reentry predictions for objects which have the potential for generating debris which could pose a hazard to people or property on Earth. link and link
Two Line Element set (TLE).
A mathematical representation of a satellite’s mean orbit. See:link
Three Line Format.
Same as a TLE except the first line contains the satellite common name. link
User Agreement.
The terms and conditions a potential user must agree to and abide by in order to obtain access to Space-Track.org. link
Vernal Equinox.
The point on the celestial sphere at which the Sun passes from south to north of the celestial equator each year. link
Acronyms
AKM Apogee Kick Motor
DD Day
DEB Debris
DoD Department of Defense
ELSET Element Set
GMT Greenwich Mean Time
HH Hour
JFCC SPACE Joint Functional Component Command for Space
MM Month or Minutes
PKM Perigee Kick Motor
RCS Radar Cross Section
SATCAT Satellite Catalog
SS Seconds
SSA Space Situational Awareness
TBA "To Be Announced" in the future.
TBD "To Be Determined" or unknown
TIP Tracking and Impact Prediction
TLE Two Line Element set
USG United States Government
USSTRATCOM United States Strategic Command
YYYY Year
ISS (ZARYA)
1 25544U 98067A   04236.56031392  .00020137  00000-0  16538-3 0  9993
2 25544  51.6335 344.7760 0007976 126.2523 325.9359 15.70406856328906
----------------------------------------------------------------------
1234567890123456789012345678901234567890123456789012345678901234567890   reference number line
         1         2         3         4         5         6         7


Line 0
ColumnsExampleDescription
1-24 ISS (ZARYA) The common name for the object based on information from the Satellite Catalog.
Line 1
Columns Example Description
1 1 Line Number
3-7 25544 Satellite Catalog Number
8 U Elset Classification
10-17 98067A International Designator
19-32 04236.56031392 Element Set Epoch (UTC) *Note: spaces are acceptable in columns 21 & 22
34-43 .00020137 1st Derivative of the Mean Motion with respect to Time
45-52 00000-0 2nd Derivative of the Mean Motion with respect to Time (decimal point assumed)
54-61 16538-3 B* Drag Term
63 0 Element Set Type
65-68 999 Element Number
69 3 Checksum
Line 2
Columns Example Description
1 2 Line Number
3-7 25544 Satellite Catalog Number
9-16 51.6335 Orbit Inclination (degrees)
18-25 344.7760 Right Ascension of Ascending Node (degrees)
27-33 0007976 Eccentricity (decimal point assumed)
35-42 126.2523 Argument of Perigee (degrees)
44-51 325.9359 Mean Anomaly (degrees)
53-63 15.70406856 Mean Motion (revolutions/day)
64-68 32890 Revolution Number at Epoch
69 6 Checksum


More Information

Satellite Catalog Number

25544

  • The catalog number assigned to the object by the US Air Force.
  • Numbers are assigned sequentially as objects are cataloged.
  • Object numbers less than 10000 are always aligned to the right, and padded with zeros or spaces to the left.


Classification

The security classification of the element set. All objects on this site will have a classification of
'U' (unclassified).

International Designator

98067A

This is another format for identifying an object.
  • The first two characters designate the launch year of the object.
  • The next 3 characters indicate the launch number, starting from the beginning of the year.
    This particular launch was the 67th launch of 1998.
  • The remainder of the field (1 to 3 characters) indicates the piece of the launch. Piece 'A' is usually the payload.


Element Set Epoch

04236.56031392

  • The first two digits ('04') indicate the year. Add 1900 for years >= 57, and 2000 for all others.
  • The remainder of the field ('236.56031392') is the day of the year.
  • Spaces or numbers are acceptable in day of the year. (e.g. '236' or '006' or ' 6').


1st Derivative of the Mean Motion

.00020137

  • "+" or "-" or space are acceptable in the 34th character position on Line 1, and indicate
    positive or negative value for 1st Derivative of the Mean Motion. A space implies a positive value.


Checksum

The checksum is the sum of all characters in the data line, modulo 10. In this formula, the following non-numeric
characters are assigned the indicated values:
  • Blanks, periods, letters, '+' signs -> 0
  • '-' signs -> 1

As the United States government agency responsible for space situational awareness (SSA) information, U.S. Strategic Command (USSTRATCOM), is committed to promoting a safe, stable, sustainable, and secure space environment through SSA information sharing. As more countries, companies, and non-governmental organizations field space capabilities and benefit from the use of space systems, it is in our collective interest to act responsibly and to enhance overall spaceflight safety. To achieve effective SSA, USSTRATCOM seeks to increase cooperation and collaboration with partners and space-faring entities through the exchange of SSA data and provision of SSA services.

The Joint Functional Component Command for Space (JFCC SPACE) provides SSA services through this website and their operations center, the Joint Space Operations Center (JSpOC), located at Vandenberg Air Force Base, in California. There are three levels of SSA services: basic, emergency, and advanced.



      Basic Services
      Basic SSA Information

USSTRATCOM provides space surveillance data to registered users through this public website, www.space-track.org. The JSpOC routinely updates the website with positional data on more than 16,000 satellites in orbit around the Earth. Users can build customized API queries to pull specific data from historical records, and automate the retrieval of new data.

Available JSpOC products: Required from customer:
      Redistribution of Basic SSA Information

Redistribution of basic SSA information retrieved from Space-Track.org requires an approved Orbital Data Request. Redistribution includes, but is not limited to, the use of Space-Track.org data to support public websites, web applications, software programs, written publications, and any other means of sharing Space-Track.org data with the general public.

Available JSpOC products:
  • Permission to redistribute data from Space-Track.org on a one-time, or annual basis
Required from customer:
      Emergency Services
The JSpOC provides emergency services to customers with specific needs, such those who operate satellites.
      Anomaly Resolution

Anomaly Resolution consists of actions taken by an owner/operator in response to a launch or on-orbit anomaly or non-nominal condition affecting a spacecraft bus, telemetry subsystem or communications payload, onboard sensor(s), or any other operating payload or subsystem.

Available JSpOC products:
  • State vectors, 1 every 8 hours, for 2 weeks or through the duration of anomaly resolution
  • Unclassified imagery analysis, if available and approved for release
Required from customer:
      Basic Emergency Conjunction Assessment (On-Orbit)

On-Orbit Conjuction Assessment (CA) is the process for determining the point and time of closest approach of two tracked orbiting objects. The JSpOC screens all active satellites against the satellite catalog several times per day to identify close approaches. If a close approach meets emergency reportable criteria the JSpOC will notify the satellite's owner/operator by email and through Space-Track.org's Operator Panel. This service is provided at no cost to promote spaceflight safety, and does not require an SSA Sharing Agreement or an ODR.

Available JSpOC products: Required from customer:
  • Contact jspoc.ssasharing@us.af.mil and provide:
    • Contact information: email addresses and phone number(s)
    • Space-Track.org usernames
    • The catalog number(s) and name(s) of the satellites you own or operate
      Basic Emergency Collision Avoidance (On-Orbit)

If an owner/operator receives a close approach notification email from the JSpOC, the owner/operator may submit their proposed maneuver plan and ephemeris for screening against the space catalog. Results that meet emergency reportable criteria will be provided. Collision avoidance is the responsibility of the owner/operator, but the JSpOC will support their collision avoidance efforts by screening their ephemeris and providing results through the predicted time of closest approach.

Available JSpOC products: Required from customer:
      Advanced Services
Advanced services are available to all entities who sign an SSA Sharing Agreement with USSTRATCOM.
      Launch Conjunction Assessment

Launch Conjunction Assessment (CA) identifies potential conjunctions that may result in a collision between launching objects and on-orbit objects. Using information provided by the customer prior to launch, via the Form 22 , the JSpOC screens the launch vehicle against the space catalog and provides conjunction information for each associated launch time. Screening begins at an altitude of 150km or greater and continues until either location uncertainty makes performing the screening no longer feasible or until the rocket body/sub-orbital components descend to 150km or less. The Launch CA Screening Results identify periods during the launch window which may put the rocket and payload at increased risk for collision.

Available JSpOC products:
  • Launch CA Screening Results: summary of predicted conjunction time windows, including:
    • Time of launch
    • Catalog number and common name of the conjuncting object
    • Mission Elapsed Time (MET) after liftoff (in seconds) of the predicted close approach
    • Predicted overall miss distance (in km) for the close approach at the MET
Required from customer:
      Launch Early Orbit Determination

Early Orbit Determination (EODET) is the process by which USSTRATCOM assets track a launch and/or separation of an object in order to generate element sets, catalog, and identify the object(s). In the event of launch anomalies (such as a booster failure, a launch failure, a satellite achieving the incorrect orbit, etc.), the JSpOC may provide anomaly resolution support.

Available JSpOC products:
  • Two-Line Element Sets
  • State vectors (after object(s) are identified in the catalog)
    • Nominal launch: 1 per day, for 2 weeks
    • Non-nominal: 1 every 8 hours, for 2 weeks or through the duration of anomaly resolution
Required from customer:
      Early Orbit Conjunction Assessment

Early Orbit Conjunction Assessment (CA) includes the screening of owner/operator-provided ephemeris against the satellite catalog to facilitate the safe maneuvering of a newly launched object into its final orbit. Expanded screening volumes and propagation are used to identify possible close approaches. Operators may provide more than one ephemeris file for each maneuver to allow analysis of multiple scenarios.

Available JSpOC products: Required from customer:
      Advanced Conjunction Assessment (On-Orbit)

Advanced On-Orbit CA uses expanded screening volumes and propagation to provide more results than Basic Emergency CA.

Available JSpOC products: Required from customer:
      Advanced Collision Avoidance (On-Orbit)

Advanced Collision Avoidance may be provided to assist owners/operators in relocating a satellite, or to avoid self-identified close approaches. Both situations allow an owner/operator to submit maneuver and non-maneuver ephemeris for expanded screening against the satellite catalog.

Available JSpOC products: Required from customer:
      Disposal/End-of-Life Support

Disposal/End-of-Life Support consists of planning for proper upper stage disposal and spacecraft end-of-life operations. If provided maneuver planning and on-orbit Information, the JSpOC may support a satellite owner/operator’s plans for disposing of an object by providing conjunction assessment and collision avoidance support using expanded screening volumes and propagation.

Available JSpOC products: Required from customer:
      Deorbit and Reentry Support

Deorbit and Reentry Support includes reentry assessment, reentry confirmation, and assistance in deorbit operations. Reentry assessments are predictions of the time and location where an uncontrolled object will reenter the atmosphere (not where the object will impact the ground). If a satellite owner/operator decides to perform the controlled deorbit of a satellite or rocket stage and provides relevant on-orbit information, the JSpOC will provide related conjunction assessment and collision avoidance support using expanded screening volumes and propagation, and confirmation of reentry after the owner/operator’s deorbit procedures are performed.

Available JSpOC products: Required from customer:
      SSA Sharing Agreement
USSTRATCOM/J513, Space Plans and Policy, negotiates SSA Sharing Agreements, which establish the parameters within which data will be exchanged by both signing parties to facilitate ongoing cooperation and advance spaceflight safety. All members of the space community, including satellite operators, launching agencies, commercial service providers, and research/academic institutions, are welcome to contact stratcom.offutt.j51.mbx.j513@mail.mil for more information on the agreement process. U.S. government (USG) organizations and their contractors have implied agreements and do not need to pursue additional documentation with USSTRATCOM.

      Orbital Data Request

All customers (non-U.S. government, commercial, and USG) should request advanced services using the Orbital Data Request (ODR) form. To submit an ODR, follow the directions on page 1 of the form and send it to odr@space-track.org.

The JSpOC’s SSA Sharing Cell processes all requests, which undergo security, legal, and resource assessments before the final JSpOC authority approves or disapproves the request. In the event of disapproval, the SSA Sharing Cell will work with the customer to revise their request for reconsideration. If a request is approved by the JSpOC, but the customer does not have an SSA Sharing Agreement, the request will be forwarded to USSTRATCOM for further review.

After approval, the SSA Sharing Cell will provide an estimate of when the data will be delivered, or when the ongoing service will be initiated. In some situations this will take more time than others, but the customer will be notified accordingly. ODRs are valid for one year from the date of approval.

Customers may request information not included in standard services, but this will lengthen the review process and the time required to deliver the data or service, if the request is approved.

      Register Your Satellite/Payload with the JSpOC

Whether you are putting your first satellite on orbit, or adding to an existing constellation, we encourage you to register your asset with the JSpOC so that we can plan for optimal tracking and identification, and provide you with conjunction assessment services as soon as possible. To register, please email jspoc.ssasharing@us.af.mil with the following information:

Required:
  • Satellite Common Name
  • Launch date and time window, launch location, and launching agency
  • Owning organization and operating organization (if different than owner)
  • Contact information for operations center (email and phone number)
Optional, but highly encouraged:
  • Launch plan and orbital parameters (please complete the R-15 form – this is necessary to expedite cataloging and identification of you satellite(s))
  • Mission description

As soon as you register, a member of the JSpOC will contact you to discuss the details of your mission and coordinate conjunction assessment and other required support.

      Communicating and Coordinating with the JSpOC

Due to the dynamic nature of space operations, the JSpOC relies on information from operators, launching agencies, and the overall space community to maintain space situational awareness. Even if you do not require direct support from the JSpOC, we welcome the following information:

Maintaining spaceflight safety and space situational awareness is a cooperative activity and responsibility. The information you provide advances these goals and ensures equal access to space for all global users. If you have questions about USSTRATCOM services or suggestions on how we can improve any aspect of our SSA Sharing process, we encourage you to contact the SSA Sharing Cell at jspoc.ssasharing@us.af.mil.

      U.S. Government Entities and Contractors

USG entities and their contractors may be eligible to receive additional data and services not listed above depending on their mission requirements and security clearance. For more information, please email jspoc.orbitaldatarequest@us.af.mil.

      Frequently Asked Questions
      What do you do with the information provided in the R-15 form?
The information in the R-15 form is the basis for the JSpOC’s launch planning. The Launch Team uses the launch sequence and orbital parameters to determine what sensors can track the launch and how soon the first elset(s) will be available. The spacecraft parameters help our Analysts decide how the objects will be maintained in the space catalog. The R-15 also informs how our Analysts will name the objects, and who the JSpOC will contact with conjunction assessment warnings.

      Can I submit the R-15 if I don’t have all of the information?
Yes. The JSpOC understands that different portions of a launch mission are managed by different entities, and appreciates any portion of the information you can provide to jspocssdlaunch@us.af.mil.

      If I don’t have an SSA Sharing Agreement can I submit an ODR?
Yes. We highly encourage you to sign an SSA Sharing Agreement, but if your agreement is in negotiations or delayed for any reason, you can submit an ODR, which will be sent to USSTRATCOM for final decision.

      How long does it take an ODR to be approved?
ODRs are usually approved in 2 weeks, but this can increase or decrease depending on the complexity and classification of the requested data.

      I’m a satellite operator who receives CDMs. Do I need to submit an ODR to share these with other organizations?
No. Each satellite organization may designate a Primary Representative who can manage access to CDMs for their constellation. For more information, contact jspoc.ssasharing@us.af.mil.

      My organization just launched a satellite, but it hasn’t been identified in the catalog. What can I do?
If you can correlate your satellite to an unnamed object in the catalog (e.g. Object A or Object B) send the identification to jspocssdlaunch@us.af.mil. If you receive telemetry from your satellite, please send a two-line element set or ephemeris to jspoc.ssasharing@us.af.mil.

      Key Contacts


JSpOC SSA Sharing Cell
Please direct all initial inquiries to the JSpOC SSA Sharing Cell. The SSA Sharing Team will respond to your inquiry, or put you in contact with the appropriate JSpOC personnel.
Email: jspoc.ssasharing@us.af.mil
Phone: +1-805-606-2675 or DSN 276-2675

JSpOC Spaceflight Safety Team
Please contact the JSpOC Spaceflight Safety Team for routine conjunction assessment support. They are manned 24 hours a day, 7 days a week.
Email: jspocspacecorrespondence@us.af.mil
Phone: +1-805-605-3533 or DSN 275-3533




Laser Clearinghouse (LCH)

"The Laser Clearinghouse mission is to provide the mission capabilities for supporting safe and responsible laser activities consistent with the needs of national defense"
- US Strategic Command Instruction 534-12

LCH Contact Information
    Documents for New Programs
Please read the following terms and conditions of the User Agreement carefully. This website permits access to U.S. Government space situational awareness information to approved users only. To obtain access, all users must abide by the following terms and conditions:

The User agrees not to transfer any data or technical information received from this website, or other U.S. Government source, including the analysis of data, to any other entity without prior express approval. See, 10 USC 2274(c)(2).

The User agrees to pay an amount that may be charged. The present U.S. Government policy is not to charge for website access. The website will provide notification should this policy change. See, 10 USC 2274(c)(1).

The User agrees to hold harmless the U.S. Government, any agencies and instrumentalities thereof, and any individuals, firms, corporations, and other persons acting for the United States. Such shall be immune from any suit in any court for any cause of action arising from the provision or receipt of space situational awareness services or information, whether or not provided in accordance with 10 USC 2274, or any related action or omission. See, 10 USC 2274 (g).

The User agrees he or she will only enter this site utilizing his or her own username and password. The User agrees not to share, assign or transfer his or her username or password to another. Each individual user or entity is required to obtain a separate account. See, 10 USC 2274(c)(3).

The User agrees to provide a valid and working email address at registration and for the duration of Account usage. This ensures effective communication with and delivery of services to the User. As part of the registration process, the User will be asked to provide and verify his/her email address.

The User agrees these terms and conditions shall be governed by and construed in accordance with U.S. Federal law.

Approved access must be renewed periodically. The U.S. Government may unilaterally terminate this agreement for any reason.

The agreed upon terms and conditions above do not alter in any way those of any other written agreement with the U.S. Government for space situational awareness services and information. The U.S. Government reserves the right to change or modify these terms and conditions at any time, and without prior notification.


WARNING!


TWO-LINE ELEMENT (TLE) SET IS THE MEAN KEPLERIAN ORBITAL ELEMENT AT A GIVEN POINT IN TIME FOR EACH SPACE OBJECT REPORTED. A TLE IS GENERATED USING THE SIMPLIFIED GENERAL PERTURBATIONS THEORY AND IS REASONABLY ACCURATE FOR LONG PERIODS OF TIME. A TLE AVAILABLE TO THE PUBLIC SHOULD NOT BE USED FOR CONJUNCTION ASSESSMENT PREDICTION. SATELLITE OPERATORS ARE DIRECTED TO CONTACT THE JOINT SPACE OPERATIONS CENTER AT 805-605-3533 FOR ACCESS TO APPROPRIATE DATA AND ANALYSIS TO SUPPORT OPERATIONAL SATELLITES.

THIS SITE MAY BE INACCESSIBLE FOR SHORT PERIODS OF TIME FOR ROUTINE MAINTENANCE AND UPDATES. THE U.S. GOVERNMENT RESERVES THE RIGHT TO LIMIT BOTH ACCESS DURATION AND DATA AMOUNTS FOR ANY USER.

U.S. GOVERNMENT DOES NOT WARRANT THE ACCURACY OR COMPLETENESS OF THIS WEBSITE OR THAT THE WEBSITE WILL BE UNINTERRUPTED, ERROR FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT THE WEBSITE OR SERVER WILL BE FREE OF VIRUSES, OR OTHER TECHNICAL PROBLEMS.

Current as of 13 March 2013.

Web Site Privacy and Security Notices, Web Site Disclaimer, and Accessibility Statement



Thank you for visiting this web site and reviewing its privacy and security notices.

Web Site Privacy Notice

Cookie technology may be used to enhance your experience while accessing this web site. At no time is private information you have provided – whether stored in cookies (persistent) or elsewhere – shared with third parties that have no right to that information. If you do not wish to have persistent cookies stored on your machine, you can turn them off in your browser. However, this may impact some of your functionality while visiting certain web sites.

Below are examples of what we do with your information when reading or downloading information from this Web site.

We may collect and store information for statistical purposes. For example, we may count the number of visitors to the different pages of our Web site to help make them more useful to visitors. This information does not identify you personally. We collect and store the following information about your visit automatically:

  • The Internet domain (for example, "xcompany.com" if you use a private Internet access account, or "yourschool.edu" if you connect from a university's domain) and IP address (an IP address is a number that is automatically assigned to your computer whenever you are surfing the Web) from which you access the web site;
  • The type of browser and operating system used to access our site;
  • The date and time you access our site;
  • The pages you visit; and
  • If you visited this web site from a link on another Web site, the address of that Web site.

Similar information is gathered for anonymous ftp, remote account login, or for other comparable types of connections.

The information that you provide to administrators of this web site will be used only for its intended purpose, except as required by law, or if pertinent to judicial or governmental investigations or proceedings.



When Sending Us E-Mail

By sending us an electronic mail (e-mail) message, you may be sending us personal information such as your name, address, and e-mail address. We may store your name, address, and e-mail address of the requester in order to respond to your request or otherwise resolve the subject matter of the e-mail. Under certain limited circumstances, we may be required by law to disclose the information you submit.

Remember that e-mail is not necessarily secure against interception. If your communication is sensitive, or includes personal information such as your Social Security number, you should consider sending it by postal mail instead.



When Registering

Information collected through questionnaires, feedback forms, or other means, enables us to determine visitors' interests, with the goal of providing better service to our visitors.

Regardless of the information being transmitted, we will protect all such information consistent with the principles of the Federal Records Act, the Privacy Act, and as applicable, the Freedom of Information Act.



Web Site Security

For site security purposes and to ensure that this web-based service remains available to all users, this computer system employs software programs that monitor network traffic to identify unauthorized attempts to upload or change information, or otherwise cause damage. Anyone using this system expressly consents to such monitoring and is advised that if such monitoring reveals evidence of possible abuse or criminal activity, such evidence may be provided to appropriate law enforcement officials. Unauthorized attempts to upload or change information are strictly prohibited and may be punishable by law, including the Computer Fraud and Abuse Act of 1986 and the National Information Infrastructure Protection Act of 1996.
For detailed questions regarding the satellite data, ephemeris, or decay information presented on this website, please email the data provider (Joint Space Operations Center) at jspoc.ssasharing@us.af.mil.

For permission to redistribute space-track data, information outside of what space-track provides, requests for launch support, and requests for Conjunction Assessment, please submit an Orbital Data Request.

For problems with Laser Clearinghouse procedures or documents, please contact the LCH team.

For problems with www.space-track.org website functionality, please email admin@space-track.org.