This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Two-Line Element set | |
|---|---|
| Name | Two-Line Element set |
| Type | Orbital data format |
| Introduced | 1960s |
| Authors | North American Aerospace Defense Command, United States Space Surveillance Network |
Two-Line Element set.
A compact, text-based orbital element representation used to describe near-Earth and deep-space object orbits in a form suitable for propagation and cataloging. Widely distributed by organizations such as North American Aerospace Defense Command, United States Space Force, and private entities like SpaceX, the format underpins operational tracking by agencies including NASA, European Space Agency, and academic groups at institutions such as Massachusetts Institute of Technology and California Institute of Technology. Two-Line Element sets are integral to conjunction analysis for satellites like International Space Station and missions by Roscosmos, China National Space Administration, and commercial operators including OneWeb and Planet Labs.
The schema provides a terse syntax historically produced by United States Air Force systems and later maintained by Joint Space Operations Center and Combined Space Operations Center nodes. Civilian consumers ranging from hobbyist observers affiliated with American Association of Variable Star Observers to professional observatories like Mt. Wilson Observatory use the data for predictions of passes over locations such as Cape Canaveral, Baikonur Cosmodrome, and Vandenberg Space Force Base. National programs including Indian Space Research Organisation and Japan Aerospace Exploration Agency rely on Two-Line Element-derived ephemerides for planning and debris assessment alongside catalog services like Celestrak and Space-Track.
A standard set consists of two fixed-width ASCII lines with catalog metadata often prefixed by a title line naming payloads such as Hubble Space Telescope or GOES-16. Lines encode identifiers linked to lists maintained by United States Naval Observatory and numbering systems like the International Designator. Fields include epoch timestamps synchronized to scales used by International Earth Rotation and Reference Systems Service and modeled with parameters adopted from standards such as those of Consultative Committee for Space Data Systems and International Astronomical Union. Additional fields reference perturbation coefficients informed by data from facilities like Goldstone Deep Space Communications Complex and Haystack Radar.
Key parameters provided include inclination values relevant to launches from Kennedy Space Center or Plesetsk Cosmodrome, right ascension of ascending node tied to celestial reference frames used by Jet Propulsion Laboratory and European Southern Observatory, and eccentricity measures affecting mission planners at Lockheed Martin and Northrop Grumman. The mean motion and mean anomaly entries are exploited in conjunction with simplifications like the SGP4/SDP4 propagators developed at Massachusetts Institute of Technology and implemented by groups including NorduGrid contributors and software repositories affiliated with GitHub. Analysts from Defense Advanced Research Projects Agency and researchers at Stanford University interpret these to estimate perigee and apogee altitudes and nodal regressions for spacecraft operated by Arianespace and United Launch Alliance.
Primary production originates from sensor networks operated by United States Space Surveillance Network, Space Surveillance Squadron 18, and partner nodes in Royal Air Force and French Space Command. Supplemental inputs derive from radar installations at Eglin Air Force Base, optical telescopes at Palomar Observatory, and space-based assets like Geostationary Operational Environmental Satellite. Commercial aggregators such as LeoLabs and academic groups at University of Colorado Boulder ingest tracks from observation campaigns including those led by International Astronomical Union commissions and data-sharing initiatives between European Space Agency and National Aeronautics and Space Administration.
Precision depends on observation arc lengths from facilities like Arecibo Observatory before its collapse and instrumentation status at Svalbard Satellite Station. Limitations arise from simplified force models compared with high-fidelity dynamics used by Jet Propulsion Laboratory's Horizons system and perturbations such as atmospheric drag modeled using standards from National Oceanic and Atmospheric Administration. Updates are issued following maneuvers by operators including Iridium Communications and anomaly events cataloged by Space-Track, with epoch corrections synchronized to time standards maintained by Bureau International des Poids et Mesures.
Operational uses span collision avoidance for assets like GPS Block III and Galileo satellites, mission planning for probes similar to Voyager 1 and Mars Reconnaissance Orbiter, and public visualization by projects such as Heavens-Above and Stellarium. Scientific communities at Harvard-Smithsonian Center for Astrophysics and Max Planck Institute for Solar System Research employ Two-Line Element-derived trajectories in conjunction with data from observatories like Keck Observatory and instruments on missions by European Space Agency and JAXA. Commercial sectors, from insurers working with Lloyd's of London to launch providers like Blue Origin, incorporate TLE-based analyses into risk assessments.
Origins trace to mid-20th-century tracking initiatives by Ballistic Missile Early Warning System and cataloging efforts by North American Aerospace Defense Command during the Space Race. Evolution involved formalization through military commands such as Air Force Space Command and coordination with scientific bodies like International Astronomical Union and Consultative Committee for Space Data Systems. Software implementations and community tooling emerged from collaborations among institutions including Massachusetts Institute of Technology, Cornell University, and open-source contributors distributed via platforms used by European Space Agency and National Aeronautics and Space Administration mission teams.