<!DOCTYPE html> <html lang="en-US" > <head > <title >Space-Track.org</title > <meta charset="utf-8" > <meta http-equiv="X-UA-Compatible" content="IE=edge" > <meta name="viewport" content="width=device-width, initial-scale=1.0" > <meta name="description" content="Space-Track.Org" > <meta name="keywords" content="Space, TLE, orbit, satellites, space objects" > <meta name="author" content="SAIC admin@space-track.org" > <link rel="apple-touch-icon" sizes="180x180" href="https://www.space-track.org/assets/ico/prod/apple-touch-icon.png"> <link rel="icon" type="image/png" sizes="32x32" href="https://www.space-track.org/assets/ico/prod/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="16x16" href="https://www.space-track.org/assets/ico/prod/favicon-16x16.png"> <link rel="icon" type="image/png" sizes="192x192" href="https://www.space-track.org/assets/ico/prod/android-chrome-192x192.png"> <link rel="manifest" href="https://www.space-track.org/assets/ico/prod/manifest.json"> <link rel="mask-icon" href="https://www.space-track.org/assets/ico/prod/safari-pinned-tab.svg" color="#2b5797"> <link rel="shortcut icon" href="https://www.space-track.org/assets/ico/prod/favicon.ico?v=m2l0MBPYLl" type="image/ico"> <meta name="apple-mobile-web-app-title" content="Space-Track"> <meta name="application-name" content="Space-Track"> <meta name="theme-color" content="#ffffff"> <script src="https://www.space-track.org/assets/js/jquery-2.1.4.min.js"></script> <script src="https://www.space-track.org/assets/js/bootstrap.min.js"></script> <script src="https://www.space-track.org/assets/js/bootstrap-toggle.min.js"></script> <script src="https://www.space-track.org/assets/js/st-custom.js"></script> <script> $.ajaxPrefilter(function(options, originalOptions, jqXHR){ if (options.type.toLowerCase() === "post") { // initialize `data` to empty string if it does not exist options.data = options.data || ""; // add leading ampersand if `data` is non-empty options.data += options.data?"&":""; // add token entry options.data += "spacetrack_csrf_token=23172255e379d0a9587dfac815c7beae"; } }); </script> <link href="https://www.space-track.org/assets/css/bootstrap.min.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/jquery.datatables.v1.10.16.min.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/theme/st-slate/bootstrap-theme.min.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/jquery.datetimepicker.min.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/st-custom.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/theme/st-slate/st-custom.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/bootstrap-toggle.css" rel="stylesheet"> <link href="https://www.space-track.org/assets/css/jquery.datatables.select.1.3.1.min.css" rel="stylesheet"></head> <body data-spy="scroll" data-target=".subnav" data-offset="50" onload="loadDoc()">  <div class="container" > <nav class="navbar navbar-default navbar-fixed-top" role="navigation" > <div class="container-fluid col-md-12" id="top-navbar" > <div class="navbar-left pull-left" id="top-navbar-logo" > <a href="/" style="float:left;margin-right:3px;height:30px" > <img src="https://www.space-track.org/assets/img/spacetrack-logo-lg.png" alt="Space-Track Logo" class="img-responsive" /> </a > <a href="/" class="navbar-brand navPopunder" style="vertical-align: center;">Space-Track.org</a > </div > <ul class="nav navbar-nav pull-right" id="top-navbar-right"> </ul> </div> <div class="container-fluid" id="top-navbar-2">  <button type="button" data-toggle="collapse" data-target=".navbar-collapse2" class="navbar-toggle collapsed"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button>  <div class="navbar-left collapse navbar-collapse"> <ul id="mainNav" class="nav navbar-nav"> <li><a href="https://www.space-track.org/"><i class="glyphicon glyphicon-log-in"></i> LOGIN</a></li> <li class="dropdown dropdown-toggle"> <a href="https://www.space-track.org/documentation" nav-id="https://www.space-track.org/documentation"> HELP <b class="caret"></b> </a> <ul class="dropdown-menu"> <li><a href="https://www.space-track.org/documentation#/api" class="font-size-14">API</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/howto" class="font-size-14">How To</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/faq" class="font-size-14">FAQ</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/legend" class="font-size-14">Legend</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/tle" class="font-size-14">TLE Format</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/odr" class="font-size-14">Data Requests</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/lch" class="font-size-14">Laser Clearinghouse</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/user_agree" class="font-size-14">User Agreement</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/privacy" class="font-size-14">Privacy</a></li><li class="divider divider-thin"></li><li><a href="https://www.space-track.org/documentation#/contact" class="font-size-14">Contact Us</a></li> </ul> </li> </ul > </div > <div class="nav navbar-nav pull-right st-clock-text" style="padding: 0 10px;" > <div class="" style="font-family: Arial, sans-serif;" > <div style="display: flex; flex-direction: row" > <div class="" id="clockContainer" > <p class="" style="margin: 0px;" ><strong class="" >Current Time (UTC) </strong ></p > <p class="text" style="margin: 0px;" id="timeValue" >2025-02-26 03:06:44</p > </div > </div > <script type="text/javascript" > let time; let incrementVal = 1; let enabled = true; async function asyncGetTime() { const response = await fetch( "https://www.space-track.org/time/getTime" ); return await response.json(); } function formatDate( isoDate ) { let returnDate = isoDate; const dotIndex = isoDate.indexOf( '.' ); if ( dotIndex !== -1 ) { returnDate = isoDate.substring( 0, dotIndex ); } return returnDate.replace( 'T', ' ' ); } function incrementLocalClock() { if ( enabled ) { let date = new Date( time ); date.setSeconds( date.getSeconds() + incrementVal ); setLocalClock( date.toISOString() ) } } function setLocalClock( updatedTime ) { time = updatedTime; const formattedTime = formatDate( time ); updateClockDisplay( formattedTime ); } function updateClockDisplay( formattedTime ) { $( "#timeValue" ).text( formattedTime ); } function getTime() { /********************************************************************* * Per PT - https://www.pivotaltracker.com/story/show/186967042 * * We are eliminating repeated calls to the webserver to 'refresh' the * time and instead allowing the local JS to keep the clock updated. * * This reduces/eliminates the excessive calls from the web clients *********************************************************************/ // const response = asyncGetTime(); // response.then( data => { // setLocalClock( data['time'] ); // } ); localTimeUTC = new Date().toISOString(); setLocalClock( localTimeUTC ); } $( document ).ready( function () { getTime(); /********************************************************************* * Per PT - https://www.pivotaltracker.com/story/show/186967042 * * We are eliminating repeated calls to the webserver to 'refresh' the * time and instead allowing the local JS to keep the clock updated. * * This reduces/eliminates the excessive calls from the web clients *********************************************************************/ // Refresh the clock every 15 seconds with new data setInterval( getTime, 15000 ); // Increment the local clock every second setInterval( incrementLocalClock, 1000 ); } ); </script > </div > </div >  <div class="navbar-left collapse navbar-collapse2" > <ul id="verticalNav" class="nav navbar-nav" > <li ><a href="https://www.space-track.org/" ><i class="glyphicon glyphicon-log-in" ></i > LOGIN</a ></li > </ul > </div > </div > </nav > </div > <script> $(document).ready(function() { $('.navPopunder').popover({ placement: 'bottom', trigger: "hover focus" }); $('[rel=popover]').popover({ placement: 'bottom', trigger: "click", html : true, content: function() { return $('#popover_content_wrapper').html(); } }); $('.docTooltip').tooltip(); $('.docTooltipL').tooltip({ placement: 'left' }); // highlight the top-level menu item $('#mainNav .dropdown-menu>li>a').on("click", function(){ $('#mainNav li.dropdown-toggle').find('.active').removeClass('active'); $(this).parent().parent().parent().addClass("active"); }); $('#mainNav .dropdown-menu').hover( // mouse enter handler function(){ // $('#mainNav li.dropdown-toggle').find('.active').removeClass('active'); $(this).parent().addClass("top-nav-opened"); }, // mouse leave handler function(){ $(this).parent().removeClass("top-nav-opened"); } ); // On page load get current URL path and assign 'active' class to correct top level menu item var pathname = window.location.pathname; if (pathname === '/'){ pathname += 'home'; } $('#mainNav > li > a[nav-id*="'+pathname+'"]').parent().addClass('active'); }); </script> <div class="container" id="help-container"> <header id="overview"> <h1>Help Documentation</h1> </header>  <ul id="tab" class="nav nav-tabs"> <li class='active'><a href="#api" data-toggle="tab">API</a></li> <li><a href="#howto" data-toggle="tab">How To</a></li> <li><a href="#faq" data-toggle="tab">FAQ</a></li> <li><a href="#legend" data-toggle="tab">Legend</a></li> <li><a href="#tle" data-toggle="tab">TLE Format</a></li> <li><a href="#odr" data-toggle="tab">Data Requests</a></li> <li><a href="#lch" data-toggle="tab">Laser Clearinghouse</a></li> <li><a href="#user_agree" data-toggle="tab">User Agreement</a></li> <li><a href="#privacy" data-toggle="tab">Privacy</a></li> <li><a href="#contact" data-toggle="tab">Contact Us</a></li> </ul> <div id="myTabContent" class="tab-content container" style="padding:0;margin-left:0;"> <div class="tab-pane in active" id="api"> <section id="help-api" role="document" > <div class="page-header" > <h2 >Introduction to the API</h2 > </div > <div id="pageSubNav" class="subnav top-spacer-sm" > <ul class="nav nav-pills" > <li ><a href="#api-Overview" >Overview</a ></li > <li ><a href="#api-use-guidelines" >Usage</a ></li > </ul > </div > <br /> <section id="api-Overview" class="anchor" > <div class="panel panel-default panel-st-help" > <div class="panel-heading" >Overview</div > <div class="panel-body" > Space-Track.org's <a target="_blank" href="http://en.wikipedia.org/wiki/Application_programming_interface" > Application Programming Interface </a > (API) allows users to access data on this site programmatically using custom, stable URLs with configurable parameters. This API conforms to the general principles of a design called <a target="_blank" href="http://en.wikipedia.org/wiki/Representational_state_transfer" > Representational State Transfer </a > or "REST" and is identical to the data returned in the site's Graphical User Interface (GUI). <div class="alert alert-info bold margin-top-10" style="margin-bottom:0;" > If you are going to develop scripts that query our API and believe that developing/testing them could violate our API guidelines, please <a href="https://www.space-track.org/documentation#contact" >Contact Us</a > to request access to our test server. This will enable you to develop your scripts against the same API without affecting the production server. </div > </div > </div > </section > <section id="api-use-guidelines" class="anchor" > <div class="panel panel-default panel-st-help panel-warning" > <div class="panel-heading" >API Use Guidelines</div > <div class="panel-body" > <strong >API Throttling:</strong > <p > Space-track throttles API use in order to maintain consistent performance for all users. To avoid error messages, please limit your query frequency. </p > <div class="alert alert-danger bold" >Limit API queries to less than 30 requests per 1 minute(s) / 300 requests per 1 hour(s) </div > <strong >To prevent excess bandwidth costs, please do not exceed the following data retrieval rates for your automated scripts:</strong > <table class="table table-condensed table-bordered table-striped" > <thead > <tr > <th >Type</th > <th >Frequency</th > <th >Details</th > </tr > </thead > <tbody > <tr > <td >CDM</td > <td > 3 / day</td > <td >Once every 8 hours for all constellation Conjunction Data Messages (CDM)</td > </tr > <tr > <td >CDM</td > <td > 1 / hour</td > <td >Once every hour for a specific conjunction event (Note: The 18 SDS will continue to send Close Approach (CA) emails to satellite owners/operators) </td > </tr > <tr > <td >TLE</td > <td > 1 / hour</td > <td >Once every hour for TLEs. Please randomly choose a minute for this query that is not at the top or bottom of the hour. </td > </tr > <tr > <td >SATCAT</td > <td > 1 / day</td > <td >Once per day after 1700 (UTC) for SATCAT data</td > </tr > <tr > <td >BOXSCORE</td > <td > 1 / day</td > <td >Once per day after 1700 (UTC) for Box Score data</td > </tr > <tr > <td >60-DAY DECAY</td > <td > 1 / week</td > <td >Once per week, on Wednesdays after 1700 (UTC), for 60-Day Decay data</td > </tr > </tbody > </table > <p > <strong >With great power comes great responsibility...</strong ><br /> The API Query Builder tool allows users a great amount of power and flexibility in creating queries. Your space-track account may be suspended if you violate the usage policy by querying data too often or by running queries that negatively impact the performance of the website. Repeat offenders may have their account suspended permanently. </p > <p > If your account has been suspended you should receive instructions from us on what you need to do in order to have your account re-instated. </p > <p > <strong >We're here to help...</strong ><br /> We realize that it can sometimes be challenging to use our API to craft an efficient query to retrieve the data that you're looking for. Rest assured that we're here to help you! If you <a href="https://www.space-track.org/documentation#contact" >Contact Us</a > and tell us what you are trying to accomplish, we can help you customize your queries to meet your needs. </p > </div > </div > </section > <br/><br/><div class="alert alert-info">Please <a href="https://www.space-track.org/auth/login?redirectFromURL=https://www.space-track.org/documentation&redirectFromTab=api">login</a> to view this content.</div></section > </div> <div class="tab-pane" id="howto"> <br/><br/><div class="alert alert-info">Please <a href="https://www.space-track.org/auth/login?redirectFromURL=https://www.space-track.org/documentation&redirectFromTab=howto">login</a> to view this content.</div> </div> <div class="tab-pane" id="faq">  <section id="help-faq" role="document"> <div class="page-header"> <h2>Frequently Asked Questions (FAQ)</h2> </div> <div id="faqDiv" class="anchor"> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What is Alpha-5?</div> <div class="panel-body"> Alpha-5 is an object numbering schema that alters the Two-line Element Set (TLE) format to replace the 1st digit of the 5-digit object number with an alphanumeric character, making it possible to represent 240,000 more numbers without widening the fixed-width format. It is a stop-gap measure that enables continued use of the TLE format for objects with an object_number of up to 339,999 for certain legacy systems. In order to achieve this, the Alpha-5 format replaces the first character of an object number over 99,999 with a letter. A is 10, B is 11, C is 12, and so on. For clarity, the “I” and “O” characters are not used in Alpha-5. <br /> More information about Alpha-5 can be found on the TLE page here: <a href="https://www.space-track.org/documentation#/tle-alpha5" target="_blank">https://www.space-track.org/documentation#/tle-alpha5</a> <br/> <br/> <i><strong>Note: </strong>Space-track.org encourages all users to use extensible formats, such as JSON, XML, or CSV. These formats are capable of handling 9-digit numbers, and will not use the Alpha-5 numbering schema. </i> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">How can I get Alpha-5 from Space-track?</div> <div class="panel-body"> To get just Alpha-5 formatted TLE’s from space-track, request ephemerides using the TLE format for objects with a number between 100,000 and 339,999 using the <a href="https://www.space-track.org/basicspacedata/modeldef/class/gp/format/html" target="_blank">GP</a> and <a href="https://www.space-track.org/basicspacedata/modeldef/class/gp_history/format/html" target="_blank">GP_History</a> API classes. <br /> Example: <a href="https://www.space-track.org/basicspacedata/query/class/gp/NORAD_CAT_ID/100000--339999/format/tle/emptyresult/show" target="_blank"> https://www.space-track.org/basicspacedata/query/class/gp/NORAD_CAT_ID/100000--339999/format/tle/emptyresult/show </a> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">How can I avoid breaking my software that doesn't support Alpha-5?</div> <div class="panel-body"> If your software cannot process alphabetical characters in the catalog number section of the TLE, you can eliminate the Alpha-5 range from your query by adding /NORAD_CAT_ID/<100000/ to filter them out like in this example: <br /> <a href="https://www.space-track.org/basicspacedata/query/class/gp/NORAD_CAT_ID/%3C100000/decay_date/null-val/epoch/%3Enow-30/orderby/norad_cat_id/format/tle" target="_blank"> https://www.space-track.org/basicspacedata/query/class/gp/NORAD_CAT_ID/%3C100000/decay_date/null-val/epoch/%3Enow-30/orderby/norad_cat_id/format/tle </a> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Can I get Alpha-5 values for other formats?</div> <div class="panel-body"> Alpha-5 is designed as a TLE-specific format for the GP and GP_History API classes. Only the TLE and 3LE formats will show this Alpha-5 designator in lines 1 and 2. All other formats are capable of handling object numbers up to 999,999,999. Users can only query the API using numbers in NORAD_CAT_ID. Even though TLE/3LE will support Alpha-5 format on output in lines 1 and 2, users need to specify NORAD_CAT_ID integer values to return specific objects. The API will not support filtering on Alpha-5 values or ranges like /NORAD_CAT_ID/T0000--V9999/ We encourage users to switch to formats other than the legacy fixed width TLE/3LE that are highly extensible (XML, KVN, JSON). </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Why will the tle, tle_latest, and tle_publish API classes be deprecated?</div> <div class="panel-body"> We found that the conflating API classes of data with the names of the various formats for the same data was confusing. With 9-digit catalog numbers on the horizon, we need new API classes that will efficiently handle all General Perturbations elsets: they are GP and GP_History.<br/> <br/> The new GP classes are designed to accommodate the expanded satellite catalog’s 9-digit identifiers. Users can return ephemerides for any publicly available object in the catalog using the CCSDS's flexible Orbit Mean-Elements Message (OMM) format in canonical XML/KVN, JSON, CSV, or HTML. All 5 of these formats use the same keywords and definitions for OMM as provided in the Orbit Data Messages (ODM) <a target="_blank" href="https://public.ccsds.org/Pubs/502x0b3e1.pdf" >CCSDS Recommended Standard 502.0-B-3</a >.<br /> <br/> The general perturbations (GP) class is an efficient listing of the newest SGP4 keplerian element set for each man-made earth-orbiting object tracked by the 18th Space Defense Squadron so users can propagate the most up-to-date orbit. GP_History has the complete set of historical ephemerides, totaling over 138 Million elsets.<br/> <br/> We will deprecate the OMM and TLE API classes at some point in the future, but not the OMM and TLE formats. Ephemerides for all objects will continue to be available with GP and GP_History classes in the following formats: OMM Standard XML, OMM Standard KVN, JSON, CSV, and HTML. Only currently available catalog number ranges below 100,000 will continue to be available in the legacy fixed-width TLE or 3LE format because TLE/3LE formats lack support for numbers above 99,999. We also plan to support any future Space Force formats that the 18th Space Defense Squadron may send us.<br/> <br/> For example, the newest elset for the International Space station will be available in TLE format using this API query:<br/> <ul> <li> <a target="_blank" href="https://www.space-track.org/basicspacedata/query/class/gp/norad_cat_id/25544/format/tle"> https://www.space-track.org/basicspacedata/query/class/gp/norad_cat_id/25544/format/tle </a> </li> </ul> (note that objects > 99,999 are not available in TLE/3LE format)<br/> <br/> The newest elsets for the ISS, NAVSTAR 77, and NAVSTAR 78 in OMM (KVN) format are:<br> <ul> <li> <a target="_blank" href="https://www.space-track.org/basicspacedata/query/class/gp/norad_cat_id/25544,43873,44506/format/kvn"> https://www.space-track.org/basicspacedata/query/class/gp/norad_cat_id/25544,43873,44506/format/kvn </a> </li> </ul> The last 30 days of elsets for the ISS in OMM (XML) format is:<br/> <ul> <li> <a target="_blank" href="https://www.space-track.org/basicspacedata/query/class/gp_history/norad_cat_id/25544/CREATION_DATE/>now-30/format/xml"> https://www.space-track.org/basicspacedata/query/class/gp_history/norad_cat_id/25544/CREATION_DATE/>now-30/format/xml </a> </li> </ul> We encourage you to review all the options and new metadata fields for querying the gp and gp_history classes on our API help page:<br/> <ul> <li> <a target="_blank" href="https://www.space-track.org/documentation#api-restRules"> https://www.space-track.org/documentation#api-restRules <a/> </li> </ul> <a href="https://www.space-track.org/">Space-Track.org</a> and <a target="_blank" href="http://www.celestrak.org">Celestrak.org</a> recommend that developers migrate their software to use the OMM standard (displayed in /class/gp/ as the /format/xml/) for all GP ephemerides because, again, legacy fixed-width TLE or 3LE format lacks support for numbers above 99,999. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What will replace the tle, tle_latest, and tle_publish classes?</div> <div class="panel-body"> The use case for tle_latest is fulfilled by the GP class, an efficient listing of the newest element set for each object tracked by 18 SDS. Over 75% of space-track users queried tle_latest and specified /ORDINAL/1/, so we simplified the gp class to deliver just the newest elset.<br/> <br/> The use case for the omm and tle classes will change to gp_history class which uses the very same elements or "predicates" as the GP class and provides access to our database of over 138 million historical elsets.<br/> <br/> The use case for the tle_publish class will be the same gp_history class and use the CREATION_DATE field (also currently in GP class) to differentiate when the ephemerides was published to <a href="https://www.space-track.org/">Space-Track.org</a>. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What are analyst objects?</div> <div class="panel-body"> Analyst objects are on-orbit objects that are tracked by the U.S. Space Surveillance Network (SSN) with insufficient fidelity for publication in the public satellite catalog (SATCAT). The lack of fidelity may be due to infrequent tracking, cross-tagging (observation association with closely-spaced objects), or inability to associate the object with a known launch. For current statistics on the total number of objects tracked by the SSN, to include the number of active payloads, analyst objects and debris, visit <a href="https://www.space-track.org/auth/login">Space-Track's login page.</a> <br/><br/> The 18th Space Defense Squadron (18 SDS) is responsible for analyzing tracking data from the SSN to maintain the SATCAT, and creating and updating analyst objects as new satellites launch and new objects are found. The analyst range, which is denoted by a satellite number from 80,000-89,999, is used like an analytical sandbox, where Orbital Analysts (OA) can create, change, and update objects until they have sufficient data and information to transition them to the public SATCAT. Consequently, analyst numbers can be constantly reused for different objects. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What are well-tracked analyst objects of unknown origin?</div> <div class="panel-body"> A "well-tracked analyst" object is an object in orbit with uncertain origin. Historically, USSPACECOM has not published these in the SATCAT due to the absence of critical data points such as launch date or launch country. In order to better manage congestion caused by space debris to enhance spaceflight safety, USSPACECOM now shares positional data (in the form of ELSETs) for these well-tracked analyst objects with registered Space-Track users. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What is the criteria for well-tracked?</div> <div class="panel-body"> Well-tracked objects are generally objects that have been consistently tracked by the SSN for longer than six months that don't frequently cross-tag with other objects. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Why is USSPACECOM releasing this data?</div> <div class="panel-body"> Publishing information on objects of unknown origin will help enhance spaceflight safety, prevent potentially catastrophic orbital collisions, and increase international cooperation in space. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Will this list be updated?</div> <div class="panel-body"> Yes, this list will be periodically updated as more analyst objects that meet well-tracked criteria are identified. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">How will I know if an object moves from the analyst object range to the SATCAT?</div> <div class="panel-body"> USSPACECOM will not typically announce movement of objects from the analyst object range to the SATCAT; newly cataloged objects may or may not have been objects tracked in the analyst range. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">How do I know if the analyst object is a payload, rocket body (R/B) or piece of debris?</div> <div class="panel-body"> Analyst objects that meet well-tracked criteria are generally debris objects, as is the majority of the space catalog. If the object type is known, it will be provided when and if the object is entered into the space catalog. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">How will the international designator be formatted in the TLEs for well-tracked analyst objects if you don't know what launch they are associated with?</div> <div class="panel-body"> The international designator may be blank, replaced with the digit zero, or in some cases, there may be a partial international designator. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">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?</div> <div class="panel-body"> 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. <br/><br/> Every ELSET 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: <br/><br/> <ul> <li><strong>period</strong> = 1440/n</li> <li>Using mu, the standard gravitational parameter for the earth (398600.4418),<br/> <strong>semi-major axis</strong> "a" = (mu/(n*2*pi/(24*3600))^2)^(1/3) </li> <li>Using semi-major axis "a", eccentricity "e", and the Earth's radius in km,<br/> <strong>apogee</strong> = (a * (1 + e))- 6378.135<br/> <strong>perigee</strong> = (a * (1 - e))- 6378.135 </li> </ul> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What is a TLE checksum?</div> <div class="panel-body"> 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. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Do all ELSETs have checksums?</div> <div class="panel-body"> Yes, Space-Track.org has updated its code to include checksums for all current and historical ELSETs including over 8 Million ELSETs that did not previously include one. This provides users with better data integrity and rudimentary error checking. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Why do all ELSETs have a constant element number of 999?</div> <div class="panel-body"> 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. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What is a "well-tracked object" and how do I recognize it on Space-Track.org?</div> <div class="panel-body"> 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, USSPACECOM 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 ELSETs 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. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">RCS - What changed with Radar Cross Section (RCS) and why? Did RCS values change?</div> <div class="panel-body"> USSPACECOM 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.1m<sup>2</sup>), Medium (0.1m<sup>2</sup> – 1m<sup>2</sup>), & Large (>1m<sup>2</sup>). 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. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">RCS - Why did USSPACECOM revise the RCS information published on Space-Track.org?</div> <div class="panel-body"> USSPACECOM 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). </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">RCS - Will there be any change to current spaceflight safety information or procedures?</div> <div class="panel-body"> 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. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">RCS - My organization was using RCS values. Is there a way to still receive that information?</div> <div class="panel-body"> Yes. Formal SSA sharing partners can receive additional information. Contact USSPACECOM at <a href="mailto:SPOC.SPACE.CustomerService@spaceforce.mil">SPOC.SPACE.CustomerService@spaceforce.mil</a> for more information on SSA Sharing Agreements. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">RCS - When did this change take effect?</div> <div class="panel-body"> The system switched to full-time scaled values on 18 Aug 14. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What timezone is all date/time data in?</div> <div class="panel-body"> All date/time data is stored, delivered, and displayed in <a href="http://en.wikipedia.org/wiki/Coordinated_Universal_Time">UTC</a>. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What's new on the site?</div> <div class="panel-body"> Please engage us on our social media sites: <a target="_blank" href="https://www.facebook.com/SpaceTrack">facebook</a> or <a target="_blank" href="https://twitter.com/spacetrackorg">twitter</a>. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Why is there a satellite catalog entry for object number [12345], but no (or less timely) orbital data or ELSETs for that object?</div> <div class="panel-body"> The answer from our data provider:<br/> <i>"S4S will provide periodic updates which may not include elsets and timely orbital data for every man-made object orbiting the earth on www.Space-Track.org.<br/><br/> Reasons include but are not limited to:<br/> - National security reasons<br/> - Some objects are too small for the sensors to consistently track<br/> - Some objects decay before S4S can collect enough information to post a <a href="https://www.space-track.org/documentation#/tle">TLE</a><br/> - Gaps in sensor coverage<br/><br/> Regardless of whether or not an object's ELSET and orbital data are posted on the website, S4S screens all objects at least daily and notifies the operator if that object is predicted to approach another object."</i> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What is the minimum size of objects that are maintained in the satellite catalog?</div> <div class="panel-body"> 10 centimeter diameter or "softball size" is the typical minimum size object that current sensors can track and 18 SDS maintains in the catalog.<br/> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Why does 18 SDS switch ELSets after a launch?</div> <div class="panel-body"> The answer from our data provider:<br/> <i>"After a launch, 18 SDS has a time requirement to identify objects from the launch.<br/><br/> 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 18 SDS and sensor network to track the other objects.<br/><br/> Once all objects are catalogued, they will not be renamed until the 18 SDS 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. 18 SDS 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."</i> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Why have I not heard a response back from 18 SDS after reporting a mis-tagged object to <a href="mailto:"></a>?</div> <div class="panel-body"> The answer from our data provider:<br/> <i>"Positively identifying all objects after launch is challenging and may result in accidental mis-identification of some objects.<br/><br/> As years pass on, it becomes increasingly difficult to move historical data within the 18 SDS system. 18 SDS has to validate all possible mis-tagging and receive clarification from multiple sources, i.e. signals, RCS data, etc. While 18 SDS 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 18 SDS data before 18 SDS 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.<br/><br/> 18 SDS 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."</i> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">How does the data provider come up with a space object's common name?</div> <div class="panel-body"> 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.<br/><br/> 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. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">What criteria are used to determine whether an orbiting object should receive a catalogue number and International Designation?</div> <div class="panel-body"> There are three primary considerations when deciding to catalog an orbiting object:<br/> 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). </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">I noticed a ELSET with an epoch a few days in the future. Aren't ELSETs supposed to be timing off the LAST ascending node pass prior to the current observations?</div> <div class="panel-body"> ELSETs can contain future epochs.<br/><br/> 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.<br/><br/> An example is Object 10370 with a 5683.23 minute period. </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading" id="screening">What is 18 SDS's reporting criteria for conjunction data messages (CDMs) in the following orbital regimes: <br /> Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Highly Elliptical Orbit (HEO), and Deep Space (DS)? </div> <div class="panel-body"> See the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf">Spaceflight Safety Handbook for Operators</a> for the most current information. </div> </div> </section> </section> </div> <div class="tab-pane" id="legend"> <section id="help-legend" role="document" > <div class="page-header"> <h2>Legend/Glossary/Definition of Terms & Products</h2> </div> <div class="panel panel-default" > <div class="panel-body" > <p >For further information on orbital mechanics see: <a href="http://www.braeunig.us/space/orbmech.htm" >link</a > </p > <br /> <dl > <dt >Apogee</dt > <dd >Point in the orbit where an Earth satellite is farthest from the Earth. Units are kilometers. <a href="https://en.wikipedia.org/wiki/Apogee" >link</a ></dd > <dt >Argument of Perigee (Degrees)</dt > <dd >The angle between the ascending node and the orbit's point of closest approach to the earth (perigee). <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >B* Drag Term</dt > <dd >Also called the radiation pressure coefficient. Units are earth radii^-1. The last two characters define an applicable power of 10. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Catalog Change Report</dt > <dd >Report that details the changes (launches, additions, decays and updates) to the satellite catalog (SATCAT). Now parts 4 & 5 of the <a href="https://www.space-track.org/#/ssr" >SSR</a > </dd >  <dt >Catalog Number</dt > <dd >Sequential number assigned by the US Space Force as objects are cataloged. Synonyms: Satellite Catalog Number, NORAD_CAT_ID, and OBJECT_NUMBER. <a href="https://www.space-track.org/documentation#/tle" >link</a ></dd > <dt >Celestial Equator</dt > <dd >It is a projection of the terrestrial equator out into space. <a href="http://www.newworldencyclopedia.org/entry/Equator" >link</a ></dd > <dt >Checksum</dt > <dd >Sum of all of the characters in the data line, modulo 10. <a href="https://www.space-track.org/documentation#/tle" >link</a ></dd > <dt >Common Name</dt > <dd >Also known as OBJECT_NAME, this is simply the name associated with the satellite. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Complete Data Files</dt > <dd >See: <a href="https://www.space-track.org/#/recent" >link</a ></dd > <dt >Conjunction Assessment (CA)</dt > <dd >The process of predicting and reporting the close approaches between Resident Space Object (RSOs) or between launch vehicles and RSOs. <a href="https://satellitesafety.gsfc.nasa.gov/CARA.html" >link</a ></dd > <dt >Conjunction Data Message (CDM)</dt > <dd ><a href="https://public.ccsds.org/Pubs/508x0b1e2c2.pdf" >CCSDS Recommended Standard</a > message format for exchanging spacecraft conjunction information between originators of Conjunction Assessments (CAs) and satellite owner/operators and other authorized parties. </dd > <dt >Conjunction Summary Message (CSM) - DEPRECATED</dt > <dd >The CSM is a fixed-format ASCII formatted message which contains information about a predicted conjunction between space objects. </dd > <dt >Country</dt > <dd >The nation or group that has responsibility for an object</dd > <dt >Current Catalog Files</dt > <dd >See: <a href="https://www.space-track.org/#/recent" >link</a ></dd > <dt >Debris</dt > <dd >Any object with the string 'DEB' or 'COOLANT' or 'SHROUD' or 'WESTFORD NEEDLES' in the SATCAT object common name. <a href="https://orbitaldebris.jsc.nasa.gov/faq.html" >link</a ></dd > <dt >Decay</dt > <dd >The lessening of the eccentricity of the elliptical orbit of an artificial satellite. <a href="https://en.wikipedia.org/wiki/Orbital_decay" >link</a ></dd > <dt >Decay Date</dt > <dd >Date object reentered the earth's atmosphere in YYYY-MM-DD format. <a href="https://www.space-track.org/#/decay" >link</a ></dd > <dt >Decay Message Types</dt > <dd >SATCAT - Historical.</dd > <dd >Decay Entry - Historical.</dd > <dd >TIP Message - Prediction.</dd > <dd >60day Decay - Prediction.</dd > <dt >Eccentricity</dt > <dd >A constant defining the shape of the orbit (0=circular, Less than 1=elliptical). <a href="http://en.wikipedia.org/wiki/Eccentricity_(orbit)" >link</a ></dd > <dt >Element Number</dt > <dd >The ELSET number is a running count of all ELSETs generated by 18 SDS for this object. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Element Set (ELSET)</dt > <dd >See: Two Line Element set.</dd > <dt >Element Set Epoch</dt > <dd >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. <a href="https://www.space-track.org/documentation#/tle" >link</a ></dd > <dt >Epoch</dt > <dd >The specific time at which the position of a satellite is defined. <a href="https://en.wikipedia.org/wiki/Epoch_(astronomy)" >link</a ></dd > <dt >File</dt > <dd >The unique identifying number of the source file for a particular object's data - higher numbers are more recent uploads. </dd > <dt >First Derivative of the Mean Motion</dt > <dd >Is the daily rate of change in the number of revolutions the object completes each day, divided by 2. Units are revolutions/day. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Geosynchronous Report</dt > <dd >Report generated using search parameters of satellite period between 1430-1450 minutes. <a href="https://www.space-track.org/basicspacedata/query/class/satcat/PERIOD/1430--1450/CURRENT/Y/DECAY/null-val/orderby/NORAD_CAT_ID/format/html" target="_blank" >link</a ></dd > <dt >Inclination - Orbital Inclination (Degrees)</dt > <dd >The angle between the equator and the orbit plane.</dd > <dt >INTLDES - International Designator</dt > <dd >Also known as COSPAR designation or NSSDC ID, this is one format for uniquely identifying an object. <a href="https://www.space-track.org/documentation#/tle" >link</a ></dd > <dt >Latest Data</dt > <dd >Displays the latest ELSET for the object. <a href="https://www.space-track.org/#/recent" >link</a ></dd > <dt >Latest ELSET</dt > <dd >Displays the last 5 ELSETs for the object. <a href="https://www.space-track.org/#/recent" >link</a ></dd > <dt >Launch Date</dt > <dd >Date object was launched in YYYY-MM-DD format. See: <a href="https://www.space-track.org/#/catalog" >link</a ></dd > <dt >Launch Number</dt > <dd >A three-letter code representing the sequential identifier of a piece in a launch.</dd > <dt >Launch Site</dt > <dd >See: <a href="https://www.space-track.org/basicspacedata/query/class/launch_site/format/html" target="_blank" >link</a ></dd > <dt >Laser Clearinghouse (LCH)</dt > <dd >An organization within S4S that supports safe and responsible laser activities consistent with the needs of national defense. See: <a href="https://www.space-track.org/documentation#/lch" >link</a ></dd > <dt >Mean Anomaly (degrees)</dt > <dd >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. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Mean Equinox</dt > <dd >The direction to the equinox at a particular epoch, with the effect of nutation subtracted. <a href="http://en.wikipedia.org/wiki/Equinox_(celestial_coordinates)" target="_blank" >link</a > </dd > <dt >Message Epoch</dt > <dd >The UTC time that 18 SDS generated a message.</dd > <dt >New Registered User Application</dt > <dd >On-line application submitted in order to obtain a user account on Space-Track.org <a href="https://www.space-track.org/auth/createAccount" >link</a ></dd > <dt >Object ID</dt > <dd >The CCSDS's name for International Designator.</dd > <dt >Object Number - Catalog Number</dt > <dd >Synonyms: Satellite Catalog Number, NORAD_CAT_ID, Object Number</dd > <dt >Orbit Mean-Elements Message (OMM)</dt > <dd >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. </dd > <dt >Orbital Data Request (ODR)</dt > <dd >The ODR is the form submitted by requesters asking for SSA services or information. <a href="https://www.space-track.org/documentation#/odr" >link</a ></dd > <dt >Orbital Data Request Process</dt > <dd >The procedures used by Space-Track.org users to request Space Situational Awareness (SSA) advanced services support. <a href="https://www.space-track.org/documentation#/odr" >link</a ></dd > <dt >Orbit Inclination (Degrees)</dt > <dd >The angle between the equator and the orbit plane. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Owner/Operator (O/O)</dt > 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 USSPACECOM and/or S4S and is generally the location where the operations center is located for a given space system. <dt >Payload</dt > <dd >Any object not classified in the SATCAT as a rocket body or debris is considered a payload. <a href="https://www.space-track.org/#/boxscore" >link</a ></dd > <dt >Perigee</dt > <dd >Point in the orbit where an Earth satellite is closest to the Earth. Units are kilometers. <a href="https://en.wikipedia.org/wiki/Perigee" >link</a ></dd > <dt >Period</dt > <dd >The number of minutes an object takes to make one full orbit. <a href="http://en.wikipedia.org/wiki/Orbital_period" >link</a ></dd > <dt >Precedence</dt > <dd >In the Decay class, lower PRECEDENCE values indicate more recent data. <a href="https://www.space-track.org/basicspacedata/modeldef/class/decay/format/html" target="_blank" >link</a ></dd > <dt >Predicted Decay Location</dt > <dd >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. </dd > <dt >Predicted Decay Time</dt > <dd >The time that an object is predicted to reach its decay location. Format: GMT Date (YYYY-MM-DD, HH:MM:SS) +/- XX Hours. </dd > <dt >Radar Cross Section (RCS)</dt > <dd >A measure of how detectable an object is by radar, measured in square meters. We do not provide numeric RCS values unless you have a valid requirement to see them. If you have a requirement for these values, please submit an Orbital Data Request (ODR) to get permission for RCS values. See our help page at <a href="https://www.space-track.org//documentation#/odr" target="_blank" >https://www.space-track.org//documentation#/odr</a >. <a href="http://en.wikipedia.org/wiki/Radar_cross-section" >link</a ></dd > <dt >Recent Satellite Decays</dt > <dd >A listing of recent satellite decays on Space-Track.org. <a href="https://www.space-track.org/#/decay" >link</a ></dd > <dt >Revolution Number at Epoch</dt > <dd >The number of orbits the object has completed at Epoch Time. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >Right Ascension (or Longitude) of Ascending Node (degrees)</dt > <dd >Is the angle of the ascending node measured EAST of the vernal equinox along the celestial equator. <a href="https://en.wikipedia.org/wiki/Longitude_of_the_ascending_node" >link</a ></dd > <dt >Rocket Body</dt > <dd >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. <a href="https://www.space-track.org/#/boxscore" >link</a ></dd > <dt>S4S - CJFSCC</dt> <dd>The <em >Space Forces - Space</em > is the Space Force Service component to United States Space Command and is responsible for executing continuous, integrated space operations to deliver theater and global effects in support of national and combatant commander objectives. Additionally, the S4S commander conducts joint space operations on behalf of USSPACECOM commander through Combined Joint Force Space Component Commander (CJFSCC) authorities. <a href="https://www.vandenberg.spaceforce.mil/Units/CFSCC/" target="_blank" >link</a > | <a href="https://www.spaceforces-space.mil/About-Us/" target="_blank">link</a> </dd> <dt >Satellite</dt > <dd >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-03) </dd > <dt >Satellite Box Score</dt > <dd >Accounting of man-made objects that have been or are in orbit by country. (SI 534-03) <a href="https://www.space-track.org/#/boxscore" >link</a ></dd > <dt >Satellite Catalog Number</dt > <dd >Sequential number assigned by the US Space Force as objects are cataloged. Synonyms: Catalog Number, NORAD_CAT_ID, and OBJECT_NUMBER. <a href="https://www.space-track.org/#/catalog" >link</a ></dd > <dt >Satellite Catalog (SATCAT)</dt > <dd >A catalog of satellite positional data maintained by 18 SDS.(SI 534-03) <a href="https://www.space-track.org/#/catalog" >link</a ></dd > <dt >Satellite Situation Report</dt > <dd >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. <a href="https://www.space-track.org/#/ssr" >link</a ></dd > <dt >Second Derivative of the Mean Motion</dt > <dd >Measures the second time derivative in daily mean motion. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >SpaceDataSource.org</dt > <dd >A deactivated website. Its file sharing functionality was added to space-track.org in 2014. <dt >Space-Track.org <dd >The website that provides unclassified SSA services and information. Space-Track.org is managed, maintained and administered by S4S. <a href="https://www.space-track.org/" >link</a ></dd > <dt >Space</dt > <dd >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). <a href="https://en.wikipedia.org/wiki/Outer_space" >link</a ></dd > <dt >Space Surveillance Data</dt > <dd >Data derived from the observation of space and activities occurring in space. <a href="http://www.dtic.mil/doctrine/new_pubs/jp3_14.pdf" >link</a ></dd > <dt >Space Weather</dt > <dd >The conditions and phenomena in space and specifically in the near-Earth environment that may affect space assets or space operations. <a href="https://www.swpc.noaa.gov/about-space-weather" target="_blank" >link</a ></dd > <dt >SI 534-03</dt > <dd >USSTRATCOM Strategic Instruction (SI) 534-03, 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. </dd > <dt >Tracking and Impact Prediction (TIP) Message</dt > <dd >Projected satellite reentry predictions for objects which have the potential for generating debris which could pose a hazard to people or property on Earth. <a href="http://orbitaldebris.jsc.nasa.gov/newsletter/pdfs/ODQNv12i3.pdf" >link</a > and <a href="https://www.space-track.org/#/decay" >link</a ></dd > <dt >Two Line Element set (TLE)</dt > <dd >A mathematical representation of a satellite’s mean orbit. See: <a href="https://www.space-track.org/documentation#/tle" >link</a ></dd > <dt >Three Line Format</dt > <dd >Same as a TLE except the first line contains the satellite common name. <a href="http://spaceflight.nasa.gov/realdata/sightings/SSapplications/Post/JavaSSOP/SSOP_Help/tle_def.html" >link</a ></dd > <dt >User Agreement</dt > <dd >The terms and conditions a potential user must agree to and abide by in order to obtain access to Space-Track.org. <a href="https://www.space-track.org/documentation#/user_agree" >link</a ></dd > <dt >Vernal Equinox</dt > <dd >The point on the celestial sphere at which the Sun passes from south to north of the celestial equator each year. <a href="http://www.encyclopedia.com/topic/vernal_equinox.aspx" >link</a ></dd > </dl > <table class="table table-striped table-bordered" > <thead> <tr> <th colspan="2">Acronyms</th> </tr> </thead> <tbody> <tr> <td>AKM</td> <td>Apogee Kick Motor</td> </tr> <tr> <td>DD</td> <td>Day</td> </tr> <tr> <td>DEB</td> <td>Debris</td> </tr> <tr> <td>DoD</td> <td>Department of Defense</td> </tr> <tr> <td>ELSET</td> <td>Element Set</td> </tr> <tr> <td>GMT</td> <td>Greenwich Mean Time</td> </tr> <tr> <td>HH</td> <td>Hour</td> </tr> <tr> <td>S4S</td> <td>Space Forces - Space</td> </tr> <tr> <td>MM</td> <td>Month or Minutes</td> </tr> <tr> <td>PKM</td> <td>Perigee Kick Motor</td> </tr> <tr> <td>RCS</td> <td>Radar Cross Section</td> </tr> <tr> <td>SATCAT</td> <td>Satellite Catalog</td> </tr> <tr> <td>SS</td> <td>Seconds</td> </tr> <tr> <td>SSA</td> <td>Space Situational Awareness</td> </tr> <tr> <td>TBA</td> <td>"To Be Announced" in the future.</td> </tr> <tr> <td>TBD</td> <td>"To Be Determined" or unknown</td> </tr> <tr> <td>TIP</td> <td>Tracking and Impact Prediction</td> </tr> <tr> <td>TLE</td> <td>Two Line Element set</td> </tr> <tr> <td>USG</td> <td>United States Government</td> </tr> <tr> <td>USSTRATCOM</td> <td>United States Strategic Command</td> </tr> <tr> <td>USSPACECOM</td> <td>United States Space Command</td> </tr> <tr> <td>YYYY</td> <td>Year</td> </tr> </tbody> </table> </div > </div > </section > </div> <div class="tab-pane" id="tle"> <section id="help-tle" role="document"> <div class="page-header"> <h2>Basic Description of the Two Line Element (TLE) Format</h2> </div> <div id="pageSubNavTle" class="subnav top-spacer-sm"> <ul class="nav nav-pills"> <li><a href="#tle-basic">Basic Info</a></li> <li><a href="#tle-addlInfo">Additional Info</a></li> <li><a href="#tle-alpha5">Alpha 5</a></li> </ul> </div> <section id="tle-basic" class="anchor"> <div class="page-header"> <h2>Basic Info</h2> </div> <pre><a class=docPopunder data-content="Columns 1-24 The common name for the object based on information from the Satellite Catalog." title="Common Name">ISS (ZARYA)</a> <a class=docPopunder data-content="Column 1" title="Line Number">1</a> <a class=docPopunder data-content="Column 3-7" title="Satellite Catalog Number">25544</a><a class=docPopunder data-content="Column 8 Elset Classification" title="Classification">U</a> <a class=docPopunder data-content="Column 10-11 Launch Year" title="International Designator">98</a><a class=docPopunder data-content="Column 12-14 Launch Number" title="International Designator">067</a><a class=docPopunder data-content="Column 15-17 Launch Piece" title="International Designator">A</a> <a class=docPopunder data-content="Column 19-20 Year" title="Element Set Epoch">04</a><a class=docPopunder data-content="Column 21-23 Day" title="Element Set Epoch">236</a><a class=docPopunder data-content="Column 24-32 Fractional portion of day " title="Element Set Epoch">.56031392</a> <a class=docPopunder data-content="Column 34-43" title="1st Time Derivative of the Mean Motion">.00020137</a> <a class=docPopunder data-content="Column 45-52" title="2nd Time Derivative of the Mean Motion">00000-0</a> <a class=docPopunder data-content="Column 54-61" title="B* Drag Term">16538-3</a> <a class=docPopunder data-content="Column 63" title="Element Set Type">0</a> <a class=docPopunder data-content="Column 65-68" title="Element Number">999</a><a class=docPopunder data-content="Column 69" title="Checksum">3</a> <a class=docPopunder data-content="Column 1" title="Line Number">2</a> <a class=docPopunder data-content="Column 3-7" title="Satellite Catalog Number">25544</a> <a class=docPopunder data-content="Column 9-16 Degrees" title="Orbit Inclination">51.6335</a> <a class=docPopunder data-content="Column 18-25 Degrees" title="Right Ascension of Ascending Node">344.7760</a> <a class=docPopunder data-content="Column 27-33" title="Eccentricity">0007976</a> <a class=docPopunder data-content="Column 35-42 Degrees" title="Argument of Perigee">126.2523</a> <a class=docPopunder data-content="Column 44-51 Degrees" title="Mean Anomaly">325.9359</a> <a class=docPopunder data-content="Column 53-63 Revolutions/day" title="Mean Motion">15.70406856</a><a class=docPopunder data-content="Column 64-68" title="Revolution Number at Epoch">32890</a><a class=docPopunder data-content="Column 69" title="Checksum">6</a> ---------------------------------------------------------------------- 1234567890123456789012345678901234567890123456789012345678901234567890 reference number line 1 2 3 4 5 6 7</pre> <br /> <div class="centered"> <table class="table table-striped table-bordered"> <thead> <tr> <th colspan="3" class="left">Line 0</th> </tr> <tr> <th class="tle-sub-header">Columns</th> <th class="tle-sub-header">Example</th> <th class="tle-sub-header" width="50%">Description</th> </tr> </thead> <tbody> <tr> <td class="centered">1-24</td> <td class="centered">ISS (ZARYA)</td> <td>The common name for the object based on information from the Satellite Catalog.</td> </tr> </tbody> <thead> <tr> <th colspan="3" class="left">Line 1</th> </tr> <tr> <th class="tle-sub-header">Columns</th> <th class="tle-sub-header">Example</th> <th class="tle-sub-header">Description</th> </tr> </thead> <tbody> <tr> <td class="centered">1</td> <td class="centered">1</td> <td>Line Number</td> </tr> <tr> <td class="centered">3-7</td> <td class="centered">25544</td> <td>Satellite Catalog Number</td> </tr> <tr> <td class="centered">8</td> <td class="centered">U</td> <td>Elset Classification</td> </tr> <tr> <td class="centered">10-17</td> <td class="centered">98067A</td> <td>International Designator</td> </tr> <tr> <td class="centered">19-32</td> <td class="centered">04236.56031392</td> <td>Element Set Epoch (UTC) *Note: spaces are acceptable in columns 21 & 22</td> </tr> <tr> <td class="centered">34-43</td> <td class="centered">.00020137</td> <td>1st Derivative of the Mean Motion with respect to Time</td> </tr> <tr> <td class="centered">45-52</td> <td class="centered">00000-0</td> <td>2nd Derivative of the Mean Motion with respect to Time (decimal point assumed)</td> </tr> <tr> <td class="centered">54-61</td> <td class="centered">16538-3</td> <td>B* Drag Term</td> </tr> <tr> <td class="centered">63</td> <td class="centered">0</td> <td>Element Set Type</td> </tr> <tr> <td class="centered">65-68</td> <td class="centered">999</td> <td>Element Number</td> </tr> <tr> <td class="centered">69</td> <td class="centered">3</td> <td>Checksum</td> </tr> </tbody> <thead> <tr> <th colspan="3" class="left">Line 2</th> </tr> <tr> <th class="tle-sub-header">Columns</th> <th class="tle-sub-header">Example</th> <th class="tle-sub-header">Description</th> </tr> </thead> <tbody> <tr> <td class="centered">1</td> <td class="centered">2</td> <td>Line Number</td> </tr> <tr> <td class="centered">3-7</td> <td class="centered">25544</td> <td>Satellite Catalog Number</td> </tr> <tr> <td class="centered">9-16</td> <td class="centered">51.6335</td> <td>Orbit Inclination (degrees)</td> </tr> <tr> <td class="centered">18-25</td> <td class="centered">344.7760</td> <td>Right Ascension of Ascending Node (degrees)</td> </tr> <tr> <td class="centered">27-33</td> <td class="centered">0007976</td> <td>Eccentricity (decimal point assumed)</td> </tr> <tr> <td class="centered">35-42</td> <td class="centered">126.2523</td> <td>Argument of Perigee (degrees)</td> </tr> <tr> <td class="centered">44-51</td> <td class="centered">325.9359</td> <td>Mean Anomaly (degrees)</td> </tr> <tr> <td class="centered">53-63</td> <td class="centered">15.70406856</td> <td>Mean Motion (revolutions/day)</td> </tr> <tr> <td class="centered">64-68</td> <td class="centered">32890</td> <td>Revolution Number at Epoch</td> </tr> <tr> <td class="centered">69</td> <td class="centered">6</td> <td>Checksum</td> </tr> </tbody> </table> </div> </section> <a href="#"><i class="glyphicon glyphicon-arrow-up"></i> Back to top</a> <section id="tle-addlInfo" class="anchor"> <div class="page-header"> <h2>Additional Information</h2> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Satellite Catalog Number</div> <div class="panel-body"> <p><em>example:</em> 25544</p> <ul> <li>The catalog number assigned to the object by the US Space Force.</li> <li>Numbers are assigned sequentially as objects are cataloged.</li> <li>Object numbers less than 10000 are always aligned to the right, and padded with zeros or spaces to the left.</li> </ul> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Classification</div> <div class="panel-body"> <p>The security classification of the element set. All objects on this site will have a classification of 'U' (unclassified).</p> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">International Designator</div> <div class="panel-body"> <p><em>example:</em> 98067A</p> <p>This is another format for identifying an object.</p> <ul> <li>The first two characters designate the launch year of the object.</li> <li>The next 3 characters indicate the launch number, starting from the beginning of the year.<br />This particular launch was the 67th launch of 1998.</li> <li>The remainder of the field (1 to 3 characters) indicates the piece of the launch. Piece 'A' is usually the payload.</li> </ul> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Element Set Epoch</div> <div class="panel-body"> <p><em>example:</em> 04236.56031392</p> <ul> <li>The first two digits ('04') indicate the year. Add 1900 for years >= 57, and 2000 for all others.</li> <li>The remainder of the field ('236.56031392') is the day of the year.</li> <li>Spaces or numbers are acceptable in day of the year. (e.g. '236' or '006' or ' 6').</li> </ul> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">1st Derivative of the Mean Motion</div> <div class="panel-body"> <p><em>example:</em> .00020137</p> <p>"+", "-" 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.</p> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Checksum</div> <div class="panel-body"> <p>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:</p> <ul> <li>Blanks, periods, letters, '+' signs -> 0</li> <li>'-' signs -> 1</li> </ul> </div> </div> </section> <a href="#"><i class="glyphicon glyphicon-arrow-up"></i> Back to top</a> <section id="tle-alpha5" class="anchor"> <div class="page-header"> <h2>Alpha 5</h2> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading"> Alpha-5 </div> <div class="panel-body"> <p> Alpha-5 is a stopgap object numbering schema from the United States Space Force that increases the satellite catalog’s capacity to display up to 339,999 objects in the GP/GP_History API classes using legacy fixed-width Two and Three Line Element Set (TLE/3LE) formats. </p> <p> Replacing the 1st digit of the 5-digit object number with an alphanumeric character makes it possible to represent 240,000 more numbers. Objects less than 100,000 are unaffected by Alpha-5, as are users who download elsets from the GP and GP_History API classes in other formats like XML, JSON, KVN, and CSV. In order to preserve legacy operations that depend on 5-digit integers, our legacy API Classes tle, tle_latest, and tle_publish will not change to Alpha-5. </p> <p> Only capital letters and numbers are used in Alpha-5. The letters “I” and “O” are omitted to avoid confusion with the numbers “1” and “0”. </p> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Examples</div> <div class="panel-body"> <p>Some example object numbers in Alpha-5 format, as they would be seen in the TLE:</p> <table class="table table-striped table-bordered"> <thead /> <tbody> <tr> <td>100000 => A0000</td> <td>148493 => E8493</td> </tr> <tr> <td>182931 => J2931</td> <td>234018 => P4018</td> </tr> <tr> <td>301928 => W1928</td> <td>339999 => Z9999</td> </tr> </tbody> </table> <p> Even though TLE/3LE will support Alpha-5 format on output in lines 1 and 2, users need to specify NORAD_CAT_ID integer values to return specific objects. The API will not support filtering on Alpha-5 values or ranges like /NORAD_CAT_ID/T0000--V9999/. </p> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Alpha-5 Propagator</div> <div class="panel-body"> <p> If your propagation software cannot process alphabetical characters in the catalog number section of the TLE, you can eliminate the Alpha-5 range from your query by adding /NORAD_CAT_ID/<100000/ to filter them out as displayed in this example: <a href="https://www.space-track.org/basicspacedata/query/class/gp/NORAD_CAT_ID/%3C100000/decay_date/null-val/epoch/%3Enow-30/orderby/norad_cat_id/format/tle" target="_blank">https://www.space-track.org/basicspacedata/query/class/gp/NORAD_CAT_ID/%3C100000/decay_date/null-val/epoch/%3Enow-30/orderby/norad_cat_id/format/tle</a> </p> <p> The latest SGP4 propagator, Version 8.0, is compatible with the new Alpha-5 format shown in this graphic and is available at <a href="https://www.space-track.org/documentation#/sgp4" target="_blank">https://www.space-track.org/documentation#/sgp4</a>: </p> <img src="https://www.space-track.org/assets/img/help/alpha5/alpha5_tle_graphic.png" alt="Alpha 5 TLE Graphic" /> </div> </div> <div class="panel panel-st-secondary"> <div class="panel-heading">Full Alpha-5 Numbering</div> <div class="panel-body"> <table class="table table-striped table-bordered"> <tbody> <tr> <td>A => 10</td> <td>J => 18</td> <td>S => 26</td> </tr> <tr> <td>B => 11</td> <td>K => 19</td> <td>T => 27</td> </tr> <tr> <td>C => 12</td> <td>L => 20</td> <td>U => 28</td> </tr> <tr> <td>D => 13</td> <td>M => 21</td> <td>V => 29</td> </tr> <tr> <td>E => 14</td> <td>N => 22</td> <td>W => 30</td> </tr> <tr> <td>F => 15</td> <td>P => 23</td> <td>X => 31</td> </tr> <tr> <td>G => 16</td> <td>Q => 24</td> <td>Y => 32</td> </tr> <tr> <td>H => 17</td> <td>R => 25</td> <td>Z => 33</td> </tr> </tbody> </table> </div> </div> <div class="panel panel-default panel-st-help"> <div class="panel-heading">Future Use</div> <div class="panel-body"> While this schema extends the usability of the TLE format, space-track.org encourages users to switch to a more extensible format, such as XML, KVN, or JSON. These formats handle the ever-increasing size of the catalog, regardless of object number size. </div> </div> </section> <a href="#"><i class="glyphicon glyphicon-arrow-up"></i> Back to top</a> </section> </div> <div class="tab-pane" id="odr" > <div class="page-header"> <h2>SSA Sharing & Orbital Data Requests (ODR)</h2> </div> <div id="pageSubNavOdr" class="subnav top-spacer-sm"> <ul class="nav nav-pills"> <li><a href="#odr-ssa_odr" data-toggle="tab">SSA Sharing & Orbital Data Requests</a></li> <li><a href="#odr-examples_forms" data-toggle="tab">Data Examples & Forms</a></li> </ul> </div> <br /> <div id="odrPageContent" class="tab-content container"> <div class="tab-pane active in" id="odr-ssa_odr"> <section id="help-ssaSharing" role="document"> <div> <p> As the United States government agency responsible for Space Situational Awareness (SSA) information, United States Space Command (USSPACECOM), 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, USSPACECOM seeks to increase cooperation and collaboration with partners and space-faring entities through the exchange of SSA data and provision of SSA services. </p> <p> The Space Forces - Space (S4S) - Combined Joint Force Space Component Commander (CJFSCC) provides SSA services through this website and the <a href="https://www.peterson.af.mil/About/Fact-Sheets/Display/Article/2356622/18th-space-control-squadron/" target="_blank">18th Space Defense Squadron (18 SDS)</a>, located at Vandenberg Space Force Base, California. There are three levels of SSA services: basic, emergency, and advanced. </p> </div> <br /> <div id="odr_Body" class="in collapse panel panel-default" style="padding: 15px;"> <br/> <div id="odr_basicServices" class="expandable_text" data-toggle="collapse" data-target="#odr_basicServicesDetails" aria-controls="#odr_basicServicesDetails"> <i class="glyphicon glyphicon-chevron-down" style="margin-left:1em;"></i>  Basic Services<br/> </div> <div id="odr_basicServicesDetails" class="collapse in section_indent"> <div id="odr_basicSSAInfo" class="expandable_text" data-toggle="collapse" data-target="#odr_basicSSAInfoDetails" aria-controls="#odr_basicSSAInfoDetails"> <i class="glyphicon glyphicon-chevron-right"></i>  Basic SSA Information<br/> </div> <div id="odr_basicSSAInfoDetails" class="collapse section_indent"> <p> USSPACECOM provides space surveillance data to registered users through this public website, www.space-track.org. 18 SDS routinely updates the website with positional data on more than 16,000 satellites in orbit around the Earth. Users can build customized <a href="https://www.space-track.org/#/queryBuilder">API queries</a> to pull specific data from historical records, and automate the retrieval of new data. </p> Available products: <ul> <li><a href="https://www.space-track.org/#/catalog">Satellite Catalog (SATCAT)</a> information</li> <li>General Perturbation (GP) positional data for the unclassified space catalog <a href="https://www.space-track.org/#/tle">(two line element sets)</a></li> <li><a href="https://www.space-track.org/#/decay">Satellite decay and reentry</a> predictions</li> </ul> Required from customer: <ul> <li>Valid Space-Track.org <a href="https://www.space-track.org/auth/createAccount">user account</a></li> </ul> </div> <div id="odr_redistBasicSSAInfo" class="expandable_text" data-toggle="collapse" data-target="#odr_redistBasicSSAInfoDetails" aria-controls="#odr_redistBasicSSAInfoDetails"> <i class="glyphicon glyphicon-chevron-right"></i>  Redistribution of Basic SSA Information<br/> </div> <div id="odr_redistBasicSSAInfoDetails" class="collapse section_indent"> <p> USSPACECOM has provided express blanket approval for transfer/redistribution of basic SSA data and services accessed via www.Space-Track.org conditioned on appropriate citation. Publications of analysis based on USSPACECOM data also require appropriate citations. </p> <p> Basic SSA data are Two-Line Elements (TLEs) and Orbital Mean-element Messages (OMMs); SATCAT; and Satellite Decay and Reentry Data. </p> <p> Basic SSA data can be found on the <a href="https://www.space-track.org/"> Home panel</a>: </p> <ul> <li><a href="https://www.space-track.org/#/gp">ELSET Search</a></li> <li><a href="https://www.space-track.org/#catalog">SATCAT</a></li> <li><a href="https://www.space-track.org/#decay">Decay/Reentry</a></li> </ul> </div> </div> <div id="odr_emergencyServices" class="expandable_text" data-toggle="collapse" data-target="#odr_emergencyServicesDetails" aria-controls="#odr_emergencyServicesDetails"> <i class="glyphicon glyphicon-chevron-down"></i>  Emergency Services<br/> </div> <div id="odr_emergencyServicesDetails" class="in collapse section_indent"> 18 SDS provides emergency services to customers with specific needs, such those who operate satellites. <div id="odr_anomalyResolution" class="expandable_text" data-toggle="collapse" data-target="#odr_anomalyResolutionDetails" aria-controls="#odr_anomalyResolutionDetails"> <i class="glyphicon glyphicon-chevron-right"></i>  Anomaly Resolution<br/> </div> <div id="odr_anomalyResolutionDetails" class="collapse section_indent"> <p>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. </p> Available products: <ul> <li>Special Perturbation (SP) <a target="_blank" href="https://www.space-track.org/documents/State%20Vector%20Example.docx">state vectors</a> </li> <li>Unclassified imagery analysis, if available and approved for release</li> </ul> Required from customer: <ul> <li>Immediately contact <a href="mailto:19SDS.orbital.safety@spaceforce.mil">19SDS.orbital.safety@spaceforce.mil</a> with the following: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Details of spacecraft status (e.g., attitude determination, spacecraft configuration, communication status) </li> </ul> </li> </ul> </div> <div id="odr_basicEmergencyCAOnOrbit" class="expandable_text" data-toggle="collapse" data-target="#odr_basicEmergencyCAOnOrbitDetails" aria-controls="#odr_basicEmergencyCAOnOrbitDetails"> <i class="glyphicon glyphicon-chevron-right"></i>  Basic Emergency Conjunction Assessment (On-Orbit)<br/> </div> <div id="odr_basicEmergencyCAOnOrbitDetails" class="collapse section_indent"> <p> On-Orbit Conjunction Assessment (CA) is the process for determining the point and time of closest approach of two tracked orbiting objects. 18 SDS screens all active satellites against the satellite catalog several times per day to identify close approaches. If a close approach meets <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> emergency reportable criteria</a>, 18 SDS 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. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> </li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> on Space-Track.org </li> </ul> Required from customer: <ul> <li>Contact <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a> and provide: <ul> <li>Contact information: email addresses and phone number(s)</li> <li>Space-Track.org usernames</li> <li>The catalog number(s) and name(s) of the satellites you own or operate</li> </ul> </li> </ul> </div> <div id="odr_basicEmergencyCAvoidanceOnOrbit" class="expandable_text" data-toggle="collapse" data-target="#odr_basicEmergencyCAvoidanceOnOrbitDetails" aria-controls="#odr_basicEmergencyCAvoidanceOnOrbitDetails"> <i class="glyphicon glyphicon-chevron-right"></i>  Basic Emergency Collision Avoidance (On-Orbit)<br/> </div> <div id="odr_basicEmergencyCAvoidanceOnOrbitDetails" class="collapse section_indent"> <p> If a satellite owner/operator receives a close approach notification email from 18 SDS, the owner/operator may submit their proposed maneuver plan and ephemeris for screening against the space catalog. Results that meet <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> emergency reportable criteria</a> will be provided. Collision avoidance is the responsibility of the satellite owner/operator, but 18 SDS will support their collision avoidance efforts by screening their predictive ephemeris and providing results in the Conjunction Data Message (CDM) format. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a></li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> on Space-Track.org</li> </ul> Required from customer: <ul> <li>Predictive ephemeris formatted and named in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li> Notification of any planned, confirmed, or cancelled maneuvers, in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> </ul> </div> </div> <div id="odr_advancedServices" class="expandable_text" data-toggle="collapse" data-target="#odr_advancedServicesDetails" aria-controls="#odr_advancedServicesDetails"> <i class="glyphicon glyphicon-chevron-down"></i><strong>  Advanced Services</strong><br/> </div> <div id="odr_advancedServicesDetails" class="in collapse section_indent"> Advanced services are available to all entities who sign an SSA Sharing Agreement with USSPACECOM. <div id="odr_launchConjunctionAssessment" class="expandable_text" data-toggle="collapse" data-target="#odr_launchConjunctionAssessmentDetails" aria-controls="#odr_launchConjunctionAssessmentDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Launch Conjunction Assessment</strong><br/> </div> <div id="odr_launchConjunctionAssessmentDetails" class="collapse section_indent"> <p> 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 <a target="_blank" href="https://www.space-track.org/documents/LCA_Form_22.docx">Form 22</a> , 18 SDS 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 through the duration of the <a target="_blank" href="https://www.space-track.org/documents/LCA_Trajectory_Formats.docx">launch trajectory</a> provided by customer. The Launch CA screening results identify periods during the launch window which may put the rocket and payload at increased risk for collision. </p> Available products: <ul> <li>Launch CA screening results: summary of predicted conjunction time windows, including: <ul> <li>Time of launch</li> <li>Catalog number and common name of the conjuncting object</li> <li>Mission Elapsed Time (MET) after liftoff (in seconds) of the predicted close approach</li> <li>Predicted overall miss distance (in km) for the close approach at the MET</li> </ul> </li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/LCA_Form_22.docx">Form 22</a></li> <li>Properly formatted <a target="_blank" href="https://www.space-track.org/documents/LCA_Trajectory_Formats.docx"> launch trajectory data in EFG coordinate system</a> </li> </ul> </div> <div id="odr_launchEarlyOrbitDet" class="expandable_text" data-toggle="collapse" data-target="#odr_launchEarlyOrbitDetDetails" aria-controls="#odr_launchEarlyOrbitDetDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Launch Early Orbit Determination</strong><br/> </div> <div id="odr_launchEarlyOrbitDetDetails" class="collapse section_indent"> <p> Early Orbit Determination (EODET) is the process by which the Space Surveillance Network (SSN) tracks a launch and/or separation of an object and sends observation data to 18 SDS for the calculation of initial orbit(s), entry into the space catalog, identification and naming of the object(s), and continual generation of element sets. 18 SDS uses information provided by the launch entity or satellite owner/operator to inform the tracking, cataloging, and identification process. </p> Available products/services: <ul> <li><a href="https://www.space-track.org/#/recent">Two-Line Element Sets</a></li> <li>Satellite naming (for satellite owners/operators</li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Launch sequence and orbital parameters</li> <li><a target="_blank" href="https://www.space-track.org/documents/R-15%20Form.docx">R-15 form</a> (preferably 30 days prior to launch)</li> <li><a href="#odr_RegisterSatellite" class="linkToSatReg">Satellite registration</a> by satellite owners/operators</li> </ul> </div> <div id="odr_earlyOrbitConjAss" class="expandable_text" data-toggle="collapse" data-target="#odr_earlyOrbitConjAssDetails" aria-controls="#odr_earlyOrbitConjAssDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Early Orbit Conjunction Assessment</strong><br/> </div> <div id="odr_earlyOrbitConjAssDetails" class="collapse section_indent"> <p> 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. <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Expanded screening volumes and propagation</a> are used to identify possible close approaches. Operators may provide more than one ephemeris file for each maneuver to allow analysis of multiple scenarios. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> for conjunctions that meet emergency reportable criteria </li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> for all results within screening volumes </li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Predictive ephemeris formatted and named in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf">Spaceflight Safety Handbook for Operators</a> </li> <li>Space-Track.org usernames</li> <li><a target="_blank" href="https://www.space-track.org/documents/R-15%20Form.docx">R-15 form</a> (optional, but highly encouraged)</li> </ul> </div> <div id="odr_advancedConjAss" class="expandable_text" data-toggle="collapse" data-target="#odr_advancedConjAssDetails" aria-controls="#odr_advancedConjAssDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Advanced Conjunction Assessment (On-Orbit)</strong><br/> </div> <div id="odr_advancedConjAssDetails" class="collapse section_indent"> <p>Advanced On-Orbit CA uses <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> expanded screening volumes and propagation</a> to provide more results than Basic Emergency CA. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> for conjunctions that meet emergency reportable criteria </li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> on Space-Track.org for all results within screening volumes </li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Predictive ephemeris formatted and named in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> (optional, but highly encouraged) </li> <li>Space-Track.org usernames</li> </ul> </div> <div id="odr_advancedColAvoid" class="expandable_text" data-toggle="collapse" data-target="#odr_advancedColAvoidDetails" aria-controls="#odr_advancedColAvoidDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Advanced Collision Avoidance (On-Orbit)</strong><br/> </div> <div id="odr_advancedColAvoidDetails" class="collapse section_indent"> <p> 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 <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> expanded screening</a> against the satellite catalog. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> for conjunctions that meet emergency reportable criteria </li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> for all results within screening volumes </li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Maneuver plan formatted in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Predictive ephemeris formatted and named in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Space-Track.org usernames</li> </ul> </div> <div id="odr_disposalEOL" class="expandable_text" data-toggle="collapse" data-target="#odr_disposalEOLDetails" aria-controls="#odr_disposalEOLDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Disposal/End-of-Life Support</strong><br/> </div> <div id="odr_disposalEOLDetails" class="collapse section_indent"> <p> 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, 18 SDS may support a satellite owner/operator’s plans for disposing of an object by providing conjunction assessment and collision avoidance using <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> expanded screening volumes and propagation</a>. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> for conjunctions that meet emergency reportable criteria </li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> for all results within screening volumes </li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Maneuver plan formatted in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Predictive ephemeris formatted and named in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Space-Track.org usernames</li> </ul> </div> <div id="odr_deorbitReentry" class="expandable_text" data-toggle="collapse" data-target="#odr_deorbitReentryDetails" aria-controls="#odr_deorbitReentryDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Deorbit and Reentry Support</strong><br/> </div> <div id="odr_deorbitReentryDetails" class="collapse section_indent"> <p> 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, 18 SDS will provide related conjunction assessment and collision avoidance support using <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> expanded screening volumes</a> and propagation, and confirmation of reentry after the owner/operator’s deorbit procedures are performed. </p> Available products: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> for conjunctions that meet emergency reportable criteria </li> <li><a href="https://www.space-track.org/documentation#odr-examples_forms"> Conjunction Data Messages (CDMs)</a> for all results within screening volumes </li> <li><a target="_blank" href="https://www.space-track.org/documents/State%20Vector%20Example.docx"> State vectors</a> <ul> <li>1 per day for controlled deorbit/reentry</li> <li>1 per 8 hours for uncontrolled reentry</li> </ul> </li> <li><a target="_blank" href="https://www.space-track.org/documents/TIP%20message%20example.pdf"> Tracking and Impact Prediction</a> (TIP) messages via Space-Track.org </li> <li>Reentry confirmation via Space-Track.org, or by email/phone</li> </ul> Required from customer: <ul> <li><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a></li> <li>Maneuver plan formatted in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Predictive ephemeris formatted and named in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Space-Track.org usernames</li> </ul> </div> </div> <div id="odr_ssaSharingAgreement" class="expandable_text" data-toggle="collapse" data-target="#odr_ssaSharingAgreementDetails" aria-controls="#odr_ssaSharingAgreementDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  SSA Sharing Agreement</strong><br/> </div> <div id="odr_ssaSharingAgreementDetails" class="collapse section_indent"> USSPACECOM/J5 Strategy, Plans, and Policy negotiates SSA Sharing Agreements. The SSA Sharing Agreement establishes 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 <a href="mailto:SPOC.SPACE.CustomerService@spaceforce.mil">SPOC.SPACE.CustomerService@spaceforce.mil</a> 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 USSPACECOM.<br/><br/> </div> <div id="odr_orbitalDataRequest" class="expandable_text" data-toggle="collapse" data-target="#odr_orbitalDataRequestDetails" aria-controls="#odr_orbitalDataRequestDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Orbital Data Request</strong><br/> </div> <div id="odr_orbitalDataRequestDetails" class="collapse section_indent"> <p> All customers (non-U.S. government, commercial, and USG) should request advanced services using the <a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">Orbital Data Request</a> (ODR) form. To submit an ODR, follow the directions on page 1 of the form and send it to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a>. </p> <p> 18 SDS’s SSA Sharing Team processes all requests, which undergo security, legal, and resource assessments before the final 18 SDS authority approves or disapproves the request. In the event of disapproval, the SSA Sharing Team will work with the customer to revise their request for reconsideration. If a request is approved by 18 SDS, but the customer is non-USG and does not have an SSA Sharing Agreement, the request will be forwarded to USSPACECOM for further review. </p> <p> After approval, the SSA Sharing Team 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. </p> <p> 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. </p> </div> <div id="odr_RegisterSatellite" class="expandable_text" data-toggle="collapse" data-target="#odr_RegisterSatelliteDetails" aria-controls="#odr_RegisterSatelliteDetails"> <i class="glyphicon glyphicon-chevron-right"></i><span style="font-weight:bold; color:red">  Register Your Satellite/Payload with Delta 2 SPACE Office</span><br/> </div> <div id="odr_RegisterSatelliteDetails" class="collapse section_indent"> <p> Whether you are putting your first satellite on orbit, or adding to an existing constellation, we encourage you to <a href="https://www.space-track.org/documents/New_Satellite_Registration_Form.docx">register</a> your asset with 18 SDS so that we can plan for optimal tracking and identification, and provide you with conjunction assessment services as soon as possible. As soon as you register, a member of 18 SDS will contact you to discuss the details of your mission and coordinate conjunction assessment and other required support. </p> </div>   <?//=base_url()?>    <div id="odr_commWithOpsCenter" class="expandable_text" data-toggle="collapse" data-target="#odr_commWithOpsCenterDetails" aria-controls="#odr_commWithOpsCenterDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Communicating and Coordinating with 18 SDS</strong><br/> </div> <div id="odr_commWithOpsCenterDetails" class="collapse section_indent"> <p> Due to the dynamic nature of space operations, 18 SDS 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 18 SDS, we welcome the following information: </p> <ul> <li>Launch information in the <a target="_blank" href="https://www.space-track.org/documents/R-15%20Form.docx">R-15 form</a> <ul> <li>Complete to the fullest extent possible and email to <a href="mailto:18SPCS.doo.launch@us.af.mil">18SPCS.doo.launch@us.af.mil</a> </li> </ul> </li> <li>Updates on satellite health and status <ul> <li>Satellite breakups, malfunctions, loss of communications, shedding, change of operational status, decommissioning, etc. Email updates to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a></li> <li>If there is an emergency situation, requiring anomaly support, please email <a href="mailto:19SDS.orbital.safety@spaceforce.mil">19SDS.orbital.safety@spaceforce.mil</a></li> </ul> </li> <li>Satellite identification <ul> <li>Send identifications and supporting information to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a></li> </ul> </li> <li>Notification of any planned, confirmed, or cancelled maneuvers, in accordance with guidance in the <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> </li> <li>Positional corrections for satellites as element sets or ephemeris <ul> <li>Send TLEs and/or ephemeris to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a></li> </ul> </li> <li>Catalog corrections <ul> <li>Send the correction and supporting information to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a></li> <li>18 SDS will investigate suggested corrections, but cannot guarantee that changes will be made</li> </ul> </li> </ul> <p> 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 USSPACECOM services or suggestions on how we can improve any aspect of our SSA Sharing process, we encourage you to contact the 18 SDS SSA Sharing Team at <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a>. </p> </div> <div id="odr_govEntitiesContractors" class="expandable_text" data-toggle="collapse" data-target="#odr_govEntitiesContractorsDetails" aria-controls="#odr_govEntitiesContractorsDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  U.S. Government Entities and Contractors</strong><br/> </div> <div id="odr_govEntitiesContractorsDetails" class="collapse section_indent"> <p> 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 <a href="mailto:SPOC.SPACE.OrbitalDataRequest@spaceforce.mil">SPOC.SPACE.OrbitalDataRequest@spaceforce.mil</a>. </p> </div> <div id="odr_faq" class="expandable_text" data-toggle="collapse" data-target="#odr_faqDetails" aria-controls="#odr_faqDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Frequently Asked Questions</strong><br/> </div> <div id="odr_faqDetails" class="collapse section_indent"> <div id="odr_faq1" class="expandable_text" data-toggle="collapse" data-target="#odr_faq1Details" aria-controls="#odr_faq1Details"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  What do you do with the information provided in the R-15 form?</strong><br/> </div> <div id="odr_faq1Details" class="collapse section_indent"> The information in the <a target="_blank" href="https://www.space-track.org/documents/R-15%20Form.docx">R-15 form</a> is the basis for 18 SDS’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 element set(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 18 SDS will contact with conjunction assessment warnings. <br /><br /> </div> <div id="odr_faq2" class="expandable_text" data-toggle="collapse" data-target="#odr_faq2Details" aria-controls="#odr_faq2Details"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Can I submit the R-15 if I don’t have all of the information?</strong><br/> </div> <div id="odr_faq2Details" class="collapse section_indent"> Yes. 18 SDS understands that different portions of a launch mission are managed by different entities, and appreciates any portion of the information you can provide to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a>.<br /><br /> </div> <div id="odr_faq3" class="expandable_text" data-toggle="collapse" data-target="#odr_faq3Details" aria-controls="#odr_faq3Details"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  If I don’t have an SSA Sharing Agreement can I submit an ODR?</strong><br/> </div> <div id="odr_faq3Details" class="collapse section_indent"> 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 <a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">ODR</a>, which will be sent to USSPACECOM for final decision.<br /><br /> </div> <div id="odr_faq4" class="expandable_text" data-toggle="collapse" data-target="#odr_faq4Details" aria-controls="#odr_faq4Details"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  How long does it take an ODR to be approved?</strong><br/> </div> <div id="odr_faq4Details" class="collapse section_indent"> <a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">ODRs</a> are usually approved in 30 days, but this can increase or decrease depending on the complexity and classification of the requested data.<br /><br /> </div> <div id="odr_faq5" class="expandable_text" data-toggle="collapse" data-target="#odr_faq5Details" aria-controls="#odr_faq5Details"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  I’m a satellite operator who receives CDMs. Do I need to submit an ODR to share these with other organizations?</strong><br/> </div> <div id="odr_faq5Details" class="collapse section_indent"> No. Each satellite organization may designate a Primary Representative who can manage access to CDMs for their constellation. For more information, contact <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a>.<br /><br /> </div> <div id="odr_faq6" class="expandable_text" data-toggle="collapse" data-target="#odr_faq6Details" aria-controls="#odr_faq6Details"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  My organization just launched a satellite, but it hasn’t been identified in the catalog. What can I do?</strong><br/> </div> <div id="odr_faq6Details" class="collapse section_indent"> If you can correlate your satellite to an unnamed object in the catalog (e.g. Object A or Object B) send the identification to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a>. If you receive telemetry from your satellite, please send a two-line element set or <a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> ephemeris</a> to <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a>. <br /><br /> </div> </div> <div id="odr_keyContacts" class="expandable_text" data-toggle="collapse" data-target="#odr_keyContactsDetails" aria-controls="#odr_keyContactsDetails"> <i class="glyphicon glyphicon-chevron-right"></i><strong>  Key Contacts</strong><br/> </div> <div id="odr_keyContactsDetails" class="collapse section_indent"> <p><br/> <strong>Delta 2 SSA Sharing Team</strong><br /> The SSA Sharing Team will respond to your inquiry, or put you in contact with the appropriate 18 SDS personnel.<br /> Email: <a href="mailto:SPOC.SPACE.DataSharing@spaceforce.mil">SPOC.SPACE.DataSharing@spaceforce.mil</a> <br /> Phone: +1-805-606-2675 or DSN 276-2675 </p> <p> <strong>19 SDS Orbital Safety Team</strong><br /> Please contact 19 SDS Orbital Safety Team for routine conjunction assessment support. They are manned 24 hours a day, 7 days a week.<br /> Email: <a href="mailto:19SDS.orbital.safety@spaceforce.mil">19SDS.orbital.safety@spaceforce.mil</a><br /> Phone: +1-540-284-3999 or DSN 284-3999 </p> </div> </div> </section> </div> <div class="tab-pane" id="odr-examples_forms"> <section id="help-odrExamples" role="document"> <div id="odr_DataExamples" class="expandable_text" data-toggle="collapse" data-target="#odr_DataExamplesDetails" aria-controls="#odr_DataExamplesDetails"> <i class="glyphicon glyphicon-chevron-down"></i>  Data Examples<br/> </div> <div id="odr_DataExamplesDetails" class="in collapse section_indent"> <ul> <li><a target="_blank" href="https://www.space-track.org/documents/State%20Vector%20Example.docx"> State vector</a> </li> <li><a target="_blank" href="https://www.space-track.org/documents/TIP%20message%20example.pdf"> Tracking and Impact Prediction (TIP) message</a> </li> <li><a target="_blank" href="https://www.space-track.org/documents/SP_Ephem_Format_5Feb19.pdf"> Propagated SP Ephemeris</a> </li> <li><a target="_blank" href="https://www.space-track.org/documents/CAN_Example.pdf"> Close Approach Notification email</a> </li> <li>Conjunction Data Message (CDM) (Effective March 23, 2020):<br/> <em>Note that some examples contain the optional comment fields and some do not</em> <ul> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_CSV_example.csv">Example: Near Earth CSV</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_HTML_example_NearEarth.html">Example: Near Earth HTML</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_JSON_example_NearEarth.txt">Example: Near Earth JSON</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_KVN_example_NearEarth.txt">Example: Near Earth KVN</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_XML_example_NearEarth.xml">Example: Near Earth XML</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_HTML_example_DeepSpace.html">Example: Deep Space HTML</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_JSON_example_DeepSpace.txt">Example: Deep Space JSON</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_KVN_example_DeepSpace.txt">Example: Deep Space KVN</a></li> <li><a target="_blank" href="https://www.space-track.org/documents/New_CDM_format_XML_example_DeepSpace.xml">Example: Deep Space XML</a></li> </ul> </li> <li><a target="_blank" href="https://www.space-track.org/documents/SFS_Handbook_For_Operators_V1.7.pdf"> Spaceflight Safety Handbook for Operators</a> includes: <ul> <li>Ephemeris formats</li> <li>File name guidance</li> <li>Maneuver notification format</li> </ul> </li> <li><a target="_blank" href="https://nodis3.gsfc.nasa.gov/OCE_docs/OCE_51.pdf">NASA Spacecraft Conjunction Assessment and Collision Avoidance Best Practices Handbook</li> <li><a target="_blank" href="https://www.space-track.org/documents/ASampleOrganization_5383_COLA_170075848.OPM"> Example Maneuver Notification - minimum information</a> </li> <li><a target="_blank" href="https://www.space-track.org/documents/ASampleOrganization_5383_6SK.OPM"> Example Maneuver Notification - expanded information</a> </li> <li><a target="_blank" href="https://www.space-track.org/documents/LCA_Handbook.pdf"> Launch Conjunction Assessment Handbook</a> includes: <ul> <li>Trajectory Formats</li> <li>File name guidance</li> <li>Results Formats</li> </ul> </li> </ul> </div> <br/> <div class="row"> <div class="span12"> <table class="table table-striped table-bordered"> <thead> <tr> <th style="width:200px">Form</th> <th>Use to:</th> <th style="width:100px">Format</th> </tr> </thead> <tbody> <tr> <td>Satellite Registration Form</td> <td> Register your asset with 18 SDS for optimal identification, tracking, and conjunction assessment services. </td> <td><a href="https://www.space-track.org/documents/New_Satellite_Registration_Form.docx">docx</a></td> </tr> <tr> <td>Orbital Data Request</td> <td>Request all advanced services</td> <td><a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.docx">docx</a>    <a target="_blank" href="https://www.space-track.org/documents/USSPACECOM_ODR.pdf">pdf</a> </td> </tr> <tr> <td>Form 22</td> <td>Provide detailed parameters on launch collision avoidance requirements</td> <td><a target="_blank" href="https://www.space-track.org/documents/LCA_Form_22.docx">docx</a></td> </tr> <tr> <td>R-15 Form</td> <td>Provide detailed parameters on an upcoming launch and/or satellites to achieve orbit</td> <td><a target="_blank" href="https://www.space-track.org/documents/R-15%20Form.docx">docx</a></td> </tr> </tbody> </table> </div> </div> </section> </div> </div> <script> $(document).ready(function() { // Toggle the arrow for the collapsible section clicked $('.expandable_text').on('click', function() { if ($(this).children('i').hasClass('glyphicon-chevron-down')) { $(this).children('i').removeClass('glyphicon-chevron-down'); $(this).children('i').addClass('glyphicon-chevron-right'); } else { $(this).children('i').removeClass('glyphicon-chevron-right'); $(this).children('i').addClass('glyphicon-chevron-down'); } }); // Show and scroll to the Register Satellite section when link is clicked $('.linkToSatReg').on('click', function(e) { e.preventDefault(); var chevronContentRef = $('#odr_RegisterSatelliteDetails'); chevronContentRef.collapse('show'); chevronContentRef.attr({'value':'open'}); // Change "Details" DIV value to 'open' $('#odr_RegisterSatellite').children("i").attr({'class':'glyphicon glyphicon-chevron-down'}); // Change chevron icon to open (points down) $('html, body').animate({ scrollTop: chevronContentRef.offset().top }, 500, 'linear'); }); }); </script> </div > <div class="tab-pane" id="lch" > <section id="help-lch" role="document"> <div class="page-header"> <h2>Laser Clearinghouse (LCH)</h2> </div> <div class="well well-lg"> <span style="font-size:18px"><em> "The Laser Clearinghouse mission is to provide the mission capabilities for supporting safe and responsible laser activities consistent with the needs of national defense"</em> </span> <br/> <div class="pull-right">- United States Strategic Command Instruction 534-12</div> <br/> </div> <div class="row"> <div class="col-md-12"> <img src="https://www.space-track.org/assets/img/lch-contact-info.png" alt="LCH Contact Information" style="margin-bottom:18px;" /> </div> </div> <div class="panel panel-default panel-st"> <div class="panel-heading" style="cursor:pointer;" data-toggle="collapse" data-target="#lch_laser_registration_docs"> <i class="glyphicon glyphicon-list-alt"></i> Laser Registration </div> <div id="lch_laser_registration_docs" class="panel-body in"> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=31723759">2. Laser Registration Form V8</a><br/> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=31723303">LCH Laser Registration FAQ</a><br/> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=31723683">Notification Of Laser Categorization CAT I - Template V2</a><br/> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=31723724">Notification Of Laser Categorization CAT III - Template V2</a><br/> </div> </div> <div class="panel panel-default panel-st"> <div class="panel-heading" style="cursor:pointer;" data-toggle="collapse" data-target="#lch_predictive_avoidance_docs"> <i class="glyphicon glyphicon-list-alt"></i> Predictive Avoidance </div> <div id="lch_predictive_avoidance_docs" class="panel-body in"> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=30123092">LCH MTOS Input Form 2025</a><br/> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=31722987">Laser Registration Form V8</a><br/> <i class="glyphicon glyphicon-file"></i> <a href="https://www.space-track.org/documentation/download?fileID=31722910">LCH Reports Handbook Change 9</a><br/> </div> </div> </section> <script> /** * folderAction() * * Switches the icons and values for the folders involved to indicate open * and closed status */ function folderAction(folderID, folderContentID) { // Set folderRef variable var folderRef = $('#'+folderID); var folderContentRef = $('#'+folderContentID); if (folderContentRef.attr('value') === 'closed') { // Change folder value to 'open' folderContentRef.attr({'value':'closed', 'value':'open'}); // Change folder icon to open folderRef.children("i.icon-folder-close").attr({'class':'icon-folder-close', 'class':'icon-folder-open'}); } else { // Change folder value to 'open' folderContentRef.attr({'value':'open', 'value':'closed'}); // Change folder icon to open folderRef.children("i.icon-folder-open").attr({'class':'icon-folder-open', 'class':'icon-folder-close'}); } } // END folderAction() </script> </div >   <div class="tab-pane" id="user_agree"> <section id="agree" role="document"> <div class="page-header" > <h2 >User Agreement</h2 > </div > <div class="panel panel-default" > <div class="panel-body" > <p ><strong >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.</strong > To obtain access, all users must abide by the following terms and conditions:</p > <p >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).</p > <p >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).</p > <p >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).</p > <p >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).</p > <p >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.</p > <p >The User agrees these terms and conditions shall be governed by and construed in accordance with U.S. Federal law.</p > <p >Approved access must be renewed periodically. The U.S. Government may unilaterally terminate this agreement for any reason.</p > <p >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.</p > <br /> <p class="lead" >WARNING!</p > <p >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 18TH SPACE DEFENSE SQUADRON AT SPOC.SPACE.CustomerService@spaceforce.mil FOR ACCESS TO APPROPRIATE DATA AND ANALYSIS TO SUPPORT OPERATIONAL SATELLITES.</p> <p >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.</p > <p >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.</p > <p ><em >Current as of 1 August 2019.</em ></p > </div > </div > </section> </div> <div class="tab-pane" id="privacy"> <section id="help-privacy" role="document"> <div class="page-header" > <h2 >Space-Track.Org Web Site Privacy Statement</h2 > </div > <div class="panel panel-default" > <div class="panel-body" > <h3 >Web Site Privacy and Security Notices, Web Site Disclaimer, and Accessibility Statement</h3 > <p >Thank you for visiting this web site and reviewing its privacy and security notices.</p > <h3 >Web Site Privacy Notice</h3 > <p >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.</p > <p >Below are examples of what we do with your information when reading or downloading information from this Web site.</p > <p >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:</p > <ul > <li > 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; </li > <li > The type of browser and operating system used to access our site; </li > <li > The date and time you access our site; </li > <li > The pages you visit; and </li > <li > If you visited this web site from a link on another Web site, the address of that Web site. </li > </ul > <p >Similar information is gathered for anonymous ftp, remote account login, or for other comparable types of connections.</p > <p >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.</p > <h3 >When Sending Us E-Mail</h3 > <p >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.</p > <p >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.</p > <h3 >When Registering</h3 > <p >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.</p > <p >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.</p > <h3 >Web Site Security</h3 > <p >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.</p > </div > </div > </section> </div> <div class="tab-pane" id="contact">  <section id="help-contact" role="document"> <div class="page-header"> <h2>Contact Us </h2> </div> <div class="panel panel-default" > <div class="panel-body" > <p >For detailed questions regarding the satellite data, ephemeris, or decay information presented on this website, please email the data provider (Delta 2 SPACE Office) at <a href="mailto:SPOC.SPACE.CustomerService@spaceforce.mil" > SPOC.SPACE.CustomerService@spaceforce.mil</a >.</p > <p >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 <a href="https://www.space-track.org/documentation#/odr" >Orbital Data Request</a >. </p > <p >For problems with Laser Clearinghouse procedures or documents, please <a href="https://www.space-track.org/documentation#/lch" >contact the LCH team.</a ></p > <p >For problems with www.space-track.org website functionality, please email <a href="mailto:admin@space-track.org" >admin@space-track.org</a >.</p > </div > </div > </section> </div> </div>  <script> !function($){ $('.docPopover').popover({ placement: 'top', trigger: "hover" }); $('.docPopunder').popover({ placement: 'bottom', trigger: "hover" }); $('.docTooltip').tooltip(); $('.docTooltipL').tooltip({ placement: 'left' }); $('.docTooltipR').tooltip({ placement: 'right' }); var pageSubNav = $('#pageSubNav'); // cache jQuery selectors var mainSubNav = $('#mainSubNav'); // fix sub nav on scroll var $win = $(window) , $pageNav = pageSubNav , $navGuts = $pageNav.find('.nav') , navTop = pageSubNav.length && pageSubNav.offset().top - 40 , isFixed = 0; if($win.scrollTop()>0){ processScroll(); } $win.on('scroll', processScroll); function processScroll() { var scrollTop = $win.scrollTop(); if (scrollTop >= navTop && !isFixed) { isFixed = 1; ////$pageNav.addClass('subnav-fixed') $navGuts.remove(); if(mainSubNav.length>0){ mainSubNav.append($navGuts); }else{ $pageNav.addClass("subnav-fixed").append($navGuts); } } else if (scrollTop <= navTop && isFixed) { isFixed = 0; if(mainSubNav.length>0){ mainSubNav.append($navGuts); }else{ $pageNav.removeClass("subnav-fixed"); } $navGuts.remove(); $pageNav.append($navGuts); } } }(window.jQuery); /** * Custom function that fires from the body onload event and parses * the URL to discover and navigate to all tabs but also sub tabs * inside tabs. */ function loadDoc() { // Retrieve the current URL current_url = location.href; // Check if the current URL even has a tab/anchor ref if (current_url.indexOf('#') !== -1) { // Splitting on the # var url_parts = current_url.split('#'); // Get the last entry in the array, should be our ID to 'activate' var last_segment = url_parts[url_parts.length - 1]; // Check if there is a '/' at the end and remove it // because not all URLs will come in the form /# if (last_segment.charAt(0) === '/') last_segment = last_segment.substring(1); var subTabIndex = last_segment.indexOf('-'); var mainTab = ''; var subTab = ''; //--- NO SUBTAB LINKING DETECTED!!! if (subTabIndex === -1) { mainTab = last_segment; } //--- SUBTAB LINKING DETECTED!!! else { // Go through and remove all classes that have 'active' set $('.active').removeClass('in active'); // Set the mainTab and subTab values mainTab = last_segment.substring(0, subTabIndex); subTab = last_segment; } // Set the tab header to be 'on' and its tabcontent to be 'on' $('a[href="#' + mainTab + '"]').parent().addClass('active'); var tabContentRef = $('#'+mainTab); tabContentRef.addClass('active in'); //--- WE HAVE A SUBTAB!!! if (subTab !== '') { // Set the subtab header and its tabcontent to be 'on' $('a[href="#'+subTab+'"]').parent().addClass('active'); var subTabContentRef = $('#' + subTab); subTabContentRef.addClass('active in'); } } // END if -- check for # existence in the URL } </script> <div class="push" ></div > <footer class="footer navbar-fixed-bottom" > <div style="display: flex; justify-content: space-between;" > <p> <a href="https://www.facebook.com/SpaceTrack" target="_blank" ><img src="https://www.space-track.org/assets/ico/facebooklogo.png" class="social-media-icon" alt="Facebook" ></a > <a href="https://twitter.com/spacetrackorg" target="_blank" ><img src="https://www.space-track.org/assets/ico/twitterlogo.png" class="social-media-icon" alt="Twitter" ></a >    Developed by <a href="http://www.saic.com" target='_blank' >SAIC</a > under contract to S4S-CJFSCC. <a href="https://www.space-track.org/documentation#/contact" >Contact Us</a > </p>     <p style="align-self: flex-end" ><a href="#" ><i class="glyphicon glyphicon-arrow-up" ></i > Back to top</a ></p > </div > </footer > </div> </body> </html>

CINXE.COM