Written and maintained by CASRAI Editorial Board
Published
On this page
Space-Track.org is the U.S. Government’s website for unclassified space situational awareness (SSA) services and information, run by the 18th Space Defense Squadron (18 SDS) at Vandenberg Space Force Base. Researchers use it to pull current and historical orbital element sets, satellite catalog records, decay and reentry data, and, for approved operators, conjunction data messages. Basic access is free but needs a personal account, the API is rate-limited per query class, and data beyond the basic products requires an approved Orbital Data Request (ODR).
Definition and scope
Space-Track.org describes itself as a site that “provides unclassified space situational awareness (SSA) services and information”. Its glossary says the site is managed, maintained and administered by the 18 SDS, which NASA’s Conjunction Assessment Risk Analysis (CARA) team describes as a tactical squadron under United States Space Command. The website itself was developed by SAIC under contract. For a research group, the practical meaning is that Space-Track.org is a data-distribution service with its own terms of use, not an open data archive: access is granted to approved users only, and the government may change terms or end access.
It is worth separating the service from the formats it serves. The two-line element set (TLE) is one output format among several; the layout of a TLE is covered in the guide to two-line element sets. This page covers the service around those files: who gets an account, which data classes exist, how often each may be queried, what needs an ODR, and what the user agreement says about reuse.
How Space-Track.org is used in practice
Accounts and eligibility
Basic Services require a valid account. The user agreement asks that the registered email address be kept valid, that each individual user or entity hold a separate account, and that credentials are never shared or transferred. Approved access is renewed periodically. The site states that the present U.S. Government policy is not to charge for website access, while also reserving the right to terminate access for any reason and to change terms without notice. U.S. federal law governs the agreement. NASA’s CARA FAQ confirms the same basic point from the user side: access to Space-Track.org requires an account with login credentials.
A lab or project that depends on the data should therefore decide who owns the account, because the terms are written around the individual user or entity, and accounts cannot be pooled or handed on when a student or postdoc leaves.
The query pattern
Data is requested through a URL-based API. The documented pattern is /basicspacedata/query/class/[class]/[predicate]/[value]/format/[format]. The site’s own example requests the current element set for catalog number 25544 in TLE format with https://www.space-track.org/basicspacedata/query/class/gp/norad_cat_id/25544/format/tle, after signing in at the site’s login page. Value ranges use a double hyphen (for example NORAD_CAT_ID/100000--339999), and comma-delimited lists are allowed.
The general-perturbations classes (GP and GP_History) can be returned as OMM in XML, KVN, JSON, CSV or HTML. The documentation notes that TLE and 3LE formats lack support for numbers above 99,999, so a request for objects with catalog numbers of 100,000 or higher has to use an OMM format rather than TLE.
Rate limits
The documentation tells users to limit API queries to fewer than 30 requests per minute and 300 requests per hour, and forbids using multiple accounts to evade the limits. Accounts may be suspended for exceeding them. On top of that overall ceiling, each data class has its own frequency rule; these are compiled in the data table below. The practical consequence for research code is that polling loops are the wrong design: a script should request a class on its permitted schedule, store the result locally, and have analysis read from the local copy.
Data classes
The data table below compares the main query classes named in the Space-Track.org documentation, what each holds and how often it may be queried. Two details are easy to miss. First, GP_History is a once-per-object request: the documentation describes bulk history through yearly TLE zip files, and it counts the full historical set at over 138 million element sets. Second, the DECAY class limit applies once the history has been downloaded, so a new project should plan its initial pull of history before it sets up routine decay queries.
The satellite catalog (SATCAT) is a daily product, and the documentation asks users to query it once a day after 1700 UTC. It carries a radar cross-section size category: Small is under 0.1 m, Medium is 0.1 to 1 m, and Large is over 1 m. The documentation also records a change dated 28 May 2026: the RCSVALUE field now holds the median radar cross section in meters, and it is published as 0 for most users. A numeric radar cross section requires an ODR. Any analysis that used SATCAT radar cross-section values before that date should state which definition it relied on.
Where it matters for research and operations
Orbital Data Requests
The glossary defines the ODR as the form submitted by requesters asking for SSA services or information. Advanced services run through the ODR route rather than the basic account. The documentation says requests are usually approved in 30 days and that an approval is valid for one year, so a project that needs ODR-level data should build that lead time and the annual renewal into its schedule. The documentation gives the submission address for requests. NASA’s CARA FAQ adds that NASA’s own ODRs go through CARA review.
Conjunction data messages
Conjunction data messages (CDMs) are issued to satellite owners and operators, who analyze them to determine close-approach risk, according to NASA CARA. CARA performs risk analysis for the missions it supports and helps with maneuver planning. The Space-Track documentation sets separate frequency limits for CDMs: three requests a day to retrieve all constellation CDMs (the API tab words this as once every eight hours), or one request an hour for a specific conjunction event. CDMs are an operations product, so a research group without a satellite to operate should not assume it can obtain them with a basic account.
Citation and redistribution
The documentation says basic SSA data (TLE/OMM element sets, SATCAT and decay data) has express blanket approval for transfer and redistribution, conditioned on appropriate citation, and that other data needs an ODR. The user agreement separately requires prior express approval for transfers of data. Both statements appear in the same documentation, and a data-sharing plan should quote both rather than choosing the more permissive one. Researchers who publish derived datasets should cite Space-Track.org as the source, record the retrieval date and query, and follow the principles in the data citation principle. Where a dataset must be shared with collaborators outside the account holder’s organisation, the terms of a data use agreement are a different matter from the Space-Track terms and do not replace them.
Reproducibility
Because element sets for the same object change over time and the service limits repeated queries, a result built on a live query cannot be re-run later against the same data unless the input was saved. Archive the raw response, the full query URL, the class and format, and the retrieval time with the analysis, which supports the computational reproducibility of the work. This is an editorial recommendation for research practice, not a Space-Track requirement.
Common misunderstandings
“A public TLE is good enough for conjunction assessment”
The documentation warns in plain terms: “A TLE available to the public should not be used for conjunction assessment prediction.” The government also does not warrant the accuracy or completeness of the data. Public element sets suit tracking, visualization, teaching and many research tasks, but they are not a substitute for the operator-facing CDM service.
“Free means I can redistribute anything”
Free access is a policy statement that the government can change. Redistribution is a separate question, covered above: blanket approval applies to the basic products with citation, and everything else needs approval through an ODR.
“One account can serve the whole lab”
The terms require a separate account for each individual user or entity and prohibit sharing or transferring credentials. Splitting one workload across several accounts to avoid the rate limit is also prohibited.
“A TLE can describe any catalogued object”
TLE and 3LE formats cannot represent catalog numbers above 99,999. An OMM format in JSON, XML, KVN or CSV is the route for those objects.
“Space-Track.org is the same thing as the TLE format”
The site is a service with accounts, limits and terms; the TLE is one file format it offers. NASA’s CARA FAQ refers to Space-Track.org as providing TLEs of publicly cataloged objects, but the site also serves OMM, catalog, decay and reentry data.
Sources
- Space-Track.org documentation (glossary, FAQ, user agreement and API tabs; checked 2026-11-18).
- NASA Conjunction Assessment Risk Analysis (CARA), frequently asked questions (checked 2026-11-18).
- Space-Track.org account sign-in page, the entry point for the account and API requests described above.
- Space-Track.org documented example query (class gp, catalog number 25544, TLE format), which requires a signed-in session.
Data: Space-Track.org API query classes: content and frequency limits
Compiled from the Space-Track.org documentation: the main query classes, what each returns and the per-class query frequency limits that apply on top of the overall 30 per minute and 300 per hour ceiling.
Period covered: 2026.
| Query class | Content | Query limit | Notes |
|---|---|---|---|
| gp | Current element sets (TLE and OMM) for the unclassified catalog | 1 per hour | TLE/3LE only for catalog numbers below 100,000; OMM as XML, KVN, JSON, CSV or HTML |
| gp_history | Complete historical element sets, over 138 million | 1 per lifetime per object | Bulk history via yearly TLE zip files |
| satcat | Satellite catalog, a daily product | 1 per day, after 1700 UTC | RCS size Small (1 m); numeric RCS needs an ODR |
| decay | Decay records | 1 per day, once history is downloaded | Basic SSA data with blanket redistribution approval conditioned on citation |
| tip | Reentry predictions | 1 per hour | Class for reentry predictions |
| cdm | Conjunction data messages | 3 per day for all constellation CDMs, or 1 per hour for a specific conjunction event | Issued to owners/operators; the API tab words the first limit as once every 8 hours |
Sources
- Space-Track.org documentation (glossary, FAQ, user agreement, API) (accessed 2026-11-18)
- NASA CARA frequently asked questions (accessed 2026-11-18)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







