A two-line element set (TLE, or more rarely 2LE) or three-line element set (3LE) is a data format encoding a list of orbital elements of an Earth-orbiting object for a given point in time, the epoch. Using a suitable prediction formula, the state (position and velocity) at any point in the past or future can be estimated to some accuracy. The TLE data representation is specific to the simplified perturbations models (SGP, SGP4, SDP4, SGP8 and SDP8), so any algorithm using a TLE as a data source must implement one of the SGP models to correctly compute the state at a time of interest. TLEs can describe the trajectories only of Earth-orbiting objects. TLEs are widely used as input for projecting the future orbital tracks of space debris for purposes of characterizing "future debris events to support risk analysis, close approach analysis, collision avoidance maneuvering" and forensic analysis.[1][2]

The format was originally intended for punched cards, encoding a set of elements on two standard 80-column cards. This format was eventually replaced by text files as punch card systems became obsolete, with each set of elements written to two 69-column ASCII lines preceded by a title line. The United States Space Force tracks all detectable objects in Earth orbit, creating a corresponding TLE for each object, and makes publicly available TLEs for many of the space objects on the websites Space Track and Celestrak,[3][4] holding back or obfuscating data on many military or classified objects. The TLE format is a de facto standard for distribution of an Earth-orbiting object's orbital elements.

A TLE set may include a title line preceding the element data, so each listing may take up three lines in the file, in which case the TLE is referred to as a three-line element set (3LE), instead of a two-line element set (2LE). The title is not required, as each data line includes a unique object identifier code.

History edit

In the early 1960s, Max Lane developed mathematical models for predicting the locations of satellites based on a minimal set of data elements. His first paper on the topic, published in 1965, introduced the Analytical Drag Theory, which concerned itself primarily with the effects of drag caused by a spherically symmetric non-rotating atmosphere.[5] Joined by K. Cranford, the two published an improved model in 1969 that added various harmonic effects due to Earth-Moon-Sun interactions and various other inputs.[6]

Lane's models were widely used by the military and NASA starting in the late 1960s. The improved version became the standard model for NORAD in the early 1970s, which ultimately led to the creation of the TLE format. At the time there were two formats designed for punch cards, an "internal format" that used three cards encoding complete details for the satellite (including name and other data), and the two card "transmission format" that listed only those elements that were subject to change.[7] The latter saved on cards and produced smaller decks when updating the databases.

Cranford continued to work on the modelling, eventually leading Lane to publish Spacetrack Report #2 detailing the Air Force General Perturbation theory, or AFGP4. The paper also described two simplified versions of the system, IGP4 which used a simplified drag model, and SGP4 (Simplified General Perturbations) which used IGP4's drag model along with a simplified gravity model.[8] The differences between the three models were slight for most objects. One year later, Spacetrack Report #3 was released, included full FORTRAN source code for the SGP4 model.[9] This quickly became the de facto standard model, both in the industry as well as the astronomy field.

Shortly after the publication of Report #3, NASA began posting elements for a variety of visible and other well known objects in their periodic NASA Prediction Bulletins, which consisted of the transmission format data in printed form. After trying for some time to convince NASA to release these in electronic form, T.S. Kelso took matters into his own hands and began manually copying the listings into text files which he distributed through his CelesTrak bulletin board system. This revealed a problem in NASA's checksum system, which traced back to the lack of the plus character (+) on the teletype machines used at NASA, which ultimately turned out to be a problem from the punch card era that occurred when NORAD updated from the BCD to EBCDIC character set on the computer sending out the updates. This problem went away when Kelso began to receive data directly from NORAD in 1989.[10]

The SGP4 model was later extended with corrections for deep space objects, creating SDP4, which used the same TLE input data. Over the years a number of more advanced prediction models have been created, but these have not seen widespread use. This is due to the TLE not containing the additional information needed by some of these formats, which makes it difficult to find the elements needed to take advantages of the improved model. More subtly, the TLE data is massaged in a fashion to improve the results when used with the SGP series models, which may cause the predictions of other models to be less accurate than SGP when used with common TLEs. The only new model to see widespread use is SGP8/SDP8, which were designed to use the same data inputs and are relatively minor corrections to the SGP4 model.

Format edit

Originally there were two data formats used with the SGP models, one containing complete details on the object known as the "internal format", and a second known as the "transmission format" that was used to provide updates to that data.

The internal format used three 80-column punch cards. Each card started with a card number, 1, 2 or 3, and ended with the letter "G". For this reason, the system was often known as the "G-card format". In addition to the orbital elements, the G-card included various flags like the launching country and orbit type (geostationary, etc.), calculated values like the perigee altitude and visual magnitude, and a 38-character comments field.

The transmission format is essentially a cut-down version of the G-card format, removing any data that is not subject to change on a regular basis, or data that can be calculated using other values. For instance, the perigee altitude from the G-card is not included as this can be calculated from the other elements. What remains is the set of data needed to update the original G-card data as additional measurements are made. The data is fit into 69 columns and does not include a trailing character. TLEs are simply the transmission format data rendered as ASCII text.

An example TLE for the International Space Station:

1 25544U 98067A   08264.51782528 -.00002182  00000-0 -11606-4 0  2927
2 25544  51.6416 247.4627 0006703 130.5360 325.0288 15.72125391563537

The meaning of this data is as follows:[11]

Title line (optional) edit


Field Columns Content Example
1 01–24 Satellite name ISS (ZARYA)

If present, the TLE is a three-line element set (3LE).

If not, the TLE is a two-line element set (2LE).

Line 1 edit


Field Columns Content Example
1 01 Line number 1
2 03–07 Satellite catalog number 25544
3 08 Classification (U: unclassified, C: classified, S: secret) [12] U
4 10–11 International Designator (last two digits of launch year) 98
5 12–14 International Designator (launch number of the year) 067
6 15–17 International Designator (piece of the launch) A
7 19–20 Epoch year (last two digits of year) 08
8 21–32 Epoch (day of the year and fractional portion of the day) 264.51782528
9 34–43 First derivative of mean motion; the ballistic coefficient [13] -.00002182
10 45–52 Second derivative of mean motion (decimal point assumed) [13] 00000-0
11 54–61 B*, the drag term, or radiation pressure coefficient (decimal point assumed) [13] -11606-4
12 63–63 Ephemeris type (always zero; only used in undistributed TLE data) [14] 0
13 65–68 Element set number. Incremented when a new TLE is generated for this object.[13] 292
14 69 Checksum (modulo 10) 7

Line 2 edit


Field Columns Content Example
1 01 Line number 2
2 03–07 Satellite Catalog number 25544
3 09–16 Inclination (degrees) 51.6416
4 18–25 Right ascension of the ascending node (degrees) 247.4627
5 27–33 Eccentricity (decimal point assumed) 0006703
6 35–42 Argument of perigee (degrees) 130.5360
7 44–51 Mean anomaly (degrees) 325.0288
8 53–63 Mean motion (revolutions per day) 15.72125391
9 64–68 Revolution number at epoch (revolutions) 56353
10 69 Checksum (modulo 10) 7

Where decimal points are assumed, they are leading decimal points. The last two symbols in Fields 10 and 11 of the first line give powers of 10 to apply to the preceding decimal. Thus, for example, Field 11 (-11606-4) translates to −0.11606E−4 (−0.11606×10−4).

The checksums for each line are calculated by adding all numerical digits on that line, including the line number. One is added to the checksum for each negative sign (-) on that line. All other non-digit characters are ignored.

For a body in a typical low Earth orbit, the accuracy that can be obtained with the SGP4 orbit model is on the order of 1 km within a few days of the epoch of the element set.[15] The term "low orbit" may refer to either the altitude (minimal or global) or orbital period of the body. Historically, the SGP algorithms defines low orbit as an orbit of less than 225 minutes.

Two-digit Epoch Years from 57 to 99 correspond to 1957-1999 and those from 00 to 56 correspond to 2000–2056.[16]

The maximum number of Satellite Catalog Numbers that can be encoded in a TLE is rapidly being approached with the recent commercialization of space and several key break-up events that have created a massive number of debris objects. Future adaptations of the TLE have been imagined to extend the number of encodable Satellites within the TLE.[17]

References edit

  1. ^ Carrico, Timothy; Carrico, John; Policastri, Lisa; Loucks, Mike (2008). "Investigating Orbital Debris Events using Numerical Methods with Full Force Model Orbit Propagation" (PDF). American Institute of Aeronautics and Astronautics (AAS 08–126). Archived from the original (PDF) on 2014-12-04.
  2. ^ "Space-Track.org". www.space-track.org. Combined Force Space Component Command. Retrieved 7 November 2023.
  3. ^ "Introduction and sign in to Space-Track.Org". Space-track.org. Retrieved 28 November 2014.
  4. ^ "Celestrak homepage". Celestrak.com. Retrieved 28 November 2014.
  5. ^ Vallado, David; Crawford, Paul; Hujsak, Richard; Kelso, T.S. (2006). "Revisiting Spacetrack Report #3" (PDF). American Institute of Aeronautics and Astronautics.
  6. ^ Lane, Max; Cranford, Kenneth (1969). "An improved analytical drag theory for the artificial satellite problem". AIAA. OCLC 122930989.
  7. ^ ADCOM Form 2012 (PDF) (Technical report).
  8. ^ Lane, Max; Hoots, Felix (December 1979). General Perturbations Theories Derived from the 1965 Lane Drag Theory (PDF) (Technical report). Project Space Track, Aerospace Defense Command. Archived (PDF) from the original on July 9, 2015.
  9. ^ Hoots, Felix; Roehrich, Ronald (December 1980). Models for Propagation of NORAD Element Sets (PDF) (Technical report). Project Space Track, Aerospace Defense Command.
  10. ^ Kelso, Ted (January 1992). "Two-Line Element Set Checksum Controversy". CelesTrak.
  11. ^ "Space Track". Space-track.org. Retrieved 28 November 2014.
  12. ^ "Norad Two-Line Orbital Element Set File". ai-solutions.com. Retrieved 2019-09-03.
  13. ^ a b c d "NASA, Definition of Two-line Element Set Coordinate System". Spaceflight.nasa.gov. Archived from the original on 1 March 2000. Retrieved 28 November 2014.
  14. ^ "CelesTrak: "FAQs: Two-Line Element Set Format"". celestrak.com. Retrieved 2019-09-03.
  15. ^ Kelso, T.S. (29 January 2007). "Validation of SGP4 and IS-GPS-200D Against GPS Precision Ephemerides". Celestrak.com. Retrieved 28 November 2014. AAS paper 07-127, presented at the 17th AAS/AIAA Space Flight Mechanics Conference, Sedona, Arizona
  16. ^ "Frequently Asked Questions: Two-Line Element Set Format". CelesTrak.
  17. ^ "CelesTrak: A New Way to Obtain GP Data". celestrak.com. Retrieved 2020-07-29.