Space Situational Awareness (SSA) is the foundational knowledge of what objects are in Earth orbit - where they are, where they are going, and what they are doing. It is the "Sense" layer of Joint All-Domain Command and Control (JADC2) applied to the space environment, and it underpins everything from conjunction assessment and debris avoidance to counter-ISR planning, PNT resilience, and counter-narrative operations in the information domain.
For quick-reference answers on SSA concepts, see the SSA FAQ. For a deep dive into how the space domain impacts terrestrial operations - including recent examples from Operation Epic Fury - see How the Space Domain Impacts Your Operations.
What SSA covers
SSA is defined in Joint Publication 3-14 (Joint Space Operations) and codified in Space Domain Publication (SDP) 3-100 (Space Domain Awareness, November 2023) as "the requisite foundational, current, and predictive knowledge and characterization of space orbital objects and the space domain." The space environment, per SDP 3-100, includes the natural operating environment, space debris, threats, adversary use of space, and commercial space. SSA is the systematic effort to understand all of it.
In practice, SSA is a data engineering problem layered on top of well-established astrophysics. It spans orbital tracking of active satellites, defunct payloads, rocket bodies, and debris using the Space Surveillance Network (SSN) and commercial providers; orbit propagation using analytical models like SGP4 and SDP4 to compute future positions from Two-Line Element (TLE) data; space weather monitoring of solar activity, coronal mass ejections, geomagnetic storms, and ionospheric conditions that affect satellite operations, GPS accuracy, and RF propagation; debris cataloging and conjunction assessment to predict collision risk; and initial characterization of tracked objects by matching them to payload types, operators, mission purposes, and RF signatures using ITU filings, payload databases, and observation data.
All of this is "what is out there and where." SSA can tell you an object is at position X with orbital parameters Y. It cannot tell you what the payload is actually doing right now - the ITU filing may say "Earth observation," but the bird could be co-hosted with a SIGINT payload, re-tasked, or operating under a different controller than listed. It cannot tell you whether an observed maneuver was routine station-keeping or something with intent behind it, who actually controls the satellite at this moment, what a pattern of life means when overlaid against terrestrial events, or whether the catalog entry is accurate or the operator is deliberately running quiet. Every one of those questions requires the contextual layer above SSA: Space Domain Awareness.
The Space Surveillance Network and data sources
The Space Surveillance Network (SSN) is the US military's primary sensor network for detecting, tracking, and identifying resident space objects. It combines ground-based radars (including phased-array systems like the AN/FPS-85 at Eglin and the Space Fence on Kwajalein), ground-based optical telescopes, and space-based sensors into a network that maintains the authoritative US space catalog. The catalog tracks over 47,000 objects as of early 2026, though the actual number of debris fragments too small to track reliably is estimated in the hundreds of thousands.
SSA does not live solely inside the SSN. A useful operational picture requires data from multiple sources stitched together through careful data engineering. Space-Track and Celestrak provide TLEs from the NORAD catalog. The International Telecommunication Union (ITU) holds filed frequency allocations for satellites - critical for RF characterization, though ITU data is keyed by filing rather than NORAD ID, requiring non-trivial join logic. Commercial SSA providers like LeoLabs offer higher-cadence tracking on objects the public catalog is slow to update. Payload databases like the Union of Concerned Scientists (UCS) Satellite Database provide mission disposition and operator information. NOAA's Space Weather Prediction Center provides the environmental conditions that affect both the birds and the radio paths to and from them. SatNOGS, a community-driven network of ground stations, crowdsources observation of satellite transmissions. Each of these data sources has its own format, update cadence, coverage gaps, and quality problems - integrating them into a coherent picture is one of the harder data engineering challenges in the defense domain, and one of the foundational reasons Empyrean Defense was built.
TLEs and orbit propagation
The Two-Line Element (TLE) is the standardized data format that encodes everything an orbit propagation model needs to predict where a satellite will be and when. The name comes from the original format: two lines of data on 80-column punch cards. Modern TLEs are distributed in machine-consumable formats via Space-Track, Celestrak, and other providers, with the underlying mathematics available as open-source software packages in every major programming language.
A TLE encodes fields including the NORAD catalog ID, the epoch (year and fractional day the element set was generated), inclination (the angle between the orbital plane and the equator, which determines the latitude range the satellite's ground track covers), eccentricity (how circular or elliptical the orbit is), and mean motion (revolutions per day, from which you derive orbital period). The fields are column-delimited, not space-delimited - a common implementation gotcha that trips up first-time parsers.
The propagation models that consume TLEs are SGP4 (Simplified General Perturbations-4) for near-Earth objects and SDP4 (Simplified Deep Space Perturbations-4) for deep-space objects. Both account for Earth's oblateness (the J2 perturbation being the dominant term), atmospheric drag, and solar/lunar gravitational effects. Feed a TLE into SGP4 and you get position and velocity in a TEME (True Equator, Mean Equinox) reference frame, which you then convert to whatever coordinate frame you need - typically ECEF (Earth-Centered, Earth-Fixed) for plotting a ground track on a GIS map.
TLEs decay in accuracy. Expect roughly 1-3 km of positional drift per day from epoch. After about a week, the accumulated error can produce anomalies - impossible travel speeds, orbit regime violations - that will corrupt downstream analysis. Operational SSA requires fresh TLEs, ideally updated within 24-48 hours of epoch for objects of interest. For the International Space Station (NORAD 25544), which orbits at roughly 420 km altitude with an inclination of 51.64° and a mean motion of approximately 15.49 revolutions per day (~93 minutes per orbit), a fresh TLE lets you predict when it will be over any point on Earth between 52°N and 52°S latitude down to the second, and compute the footprint of Earth's surface visible from that altitude. All from two lines of text that look like someone passed out drunk on the keyboard. That is the power of SSA at its most basic: open-source data, well-established math, and a map.
From SSA to Space Domain Awareness
SSA is the catalog and physics. Space Domain Awareness (SDA) is the meaning. SDP 3-100 defines SDA as "the timely, relevant, and actionable understanding of the operational environment that allows military forces to plan, integrate, execute, and assess Space operations." If SSA is the "Sense" part of JADC2 for the space domain, SDA is the "Make Sense" part - characterization, behavioral analysis, intent inference, and the correlation of orbital activity with events in other domains.
Characterization
SDA begins with characterization: matching a tracked object to a payload type, a mission purpose, an operator, and a behavior profile. This is where ITU filings, commercial payload databases, RF signature analysis, and optical observation get fused into an identity that is more than a catalog number. It is the difference between knowing that NORAD catalog ID 40961 is at a specific position in orbit versus knowing that JILIN 1 is a Chinese commercial imagery satellite operated by Chang Guang Satellite Technology, downlinking on specific frequencies with a known revisit regime. Characterization is not a point-in-time lookup - it is a continuous process that must account for re-tasking, payload modifications, ownership transfers, leased capacity, and co-hosted foreign payloads.
Pattern-of-life and maneuver detection
Every satellite has a rhythm: station-keeping burns, attitude adjustments, seasonal drag compensation, and debris avoidance maneuvers. SGP4 projections drift against reality when a satellite maneuvers, and that drift is the tell. An anomalous maneuver - one that does not match the operator's historical pattern or the bird's stated mission - is a red flag that demands further investigation. Whether that maneuvering is overtly suspicious or malicious is what pattern-of-life analysis enables you to ascertain.
Maneuver detection and pattern-of-life go together but are solved differently. Maneuver detection is a physics problem: compare propagated position against observed position, flag significant residuals. Pattern-of-life is a behavioral analytics problem: build a baseline of normal activity over weeks or months, then detect deviations. A satellite reportedly carrying scientific payloads that starts elongating passes over a military base or critical infrastructure site - especially if electromagnetic activity on downlink increases in parallel - could denote a change in mission profile, dual-use technology, or outright deception in the original filing.
Rendezvous and Proximity Operations
Rendezvous and Proximity Operations (RPOs) are an observable class of maneuver that can be overtly malicious or overtly benign depending on context. When a satellite closes with another satellite, it could be for inspection, repair, or towing - as when Shijian-21 towed the defunct BeiDou-2 G2 into a graveyard orbit above GEO (~35,786 km altitude). The same mechanical capabilities that enable repair and towing also enable seizure, shielding damage, electronics interference, or the deployment of space-based effectors. RPO detection is a direct output of SSA (you need precise relative positioning), but interpreting RPO intent is pure SDA - it requires pattern-of-life, operator characterization, and cross-domain correlation to distinguish a benign servicing mission from something adversarial.
Counterspace threats
The space domain has its own threat taxonomy, ranging from reversible effects like dazzling and jamming through irreversible kinetic destruction.
Direct-Ascent Anti-Satellite (DA-ASAT) weapons are ground-launched or air-launched interceptors that physically destroy a satellite in orbit. The US, Russia, China, and India have all demonstrated DA-ASAT capability. The debris consequences are severe - China's 2007 test against Fengyun-1C alone generated over 3,500 pieces of trackable debris, much of which remains in orbit two decades later. Co-orbital weapons are satellites maneuvered into proximity with a target for inspection, interference, seizure, or kinetic engagement - the RPO threat described above. Directed Energy Weapons (DEW) include both space-based and ground-based systems. High-Energy Lasers (HELs) can cause material damage to satellites with significantly lower beam extinction rates in vacuum than through atmosphere. Even without destroying the satellite, overwhelming its optical sensors can cause outages lasting hours or days - a technique called dazzling. Russia's Peresvet ground-based HEL system is designed for exactly this mission. Electronic warfare targeting satellite uplinks, downlinks, or the signals they relay (particularly GPS) is the most commonly employed counterspace capability and does not require kinetic engagement. Cyber operations against ground segments - the stations that command and control satellites - are doctrinally part of the space domain even though the attack surface is terrestrial.
The CSIS Space Threat Assessment series, published annually, provides the most comprehensive unclassified survey of counterspace capabilities by country and type.
Space weather and environmental threats
Not all threats to the space domain come from adversaries. Coronal Mass Ejections (CMEs), geomagnetic storms, solar flares, and atmospheric drag variations are operationally significant threats that SSA must track alongside the adversarial picture. A strong CME can degrade GPS signals, induce single-event upsets in satellite electronics, and expand the upper atmosphere enough to change the drag profile of everything in LEO - which in turn invalidates TLE-based propagation until new element sets are generated. SDA must weigh space weather the same way a ground commander weighs terrestrial weather: it shapes the operating environment whether you account for it or not.
Space debris is the environmental threat with the longest tail. The Kessler Syndrome - the cascading collision scenario theorized by Donald J. Kessler and Burton Cour-Palais in their 1978 paper - describes a future in which debris from collisions generates fragments that cause further collisions, progressively polluting an orbital regime. While the timescale is decades or centuries rather than the minutes Hollywood depicts, the risk is operationally real and compounds with every ASAT test, accidental collision, and failed deorbit. The February 2009 collision between the defunct Russian Cosmos 2251 and the operational US Iridium 33 - which generated over 2,500 pieces of trackable debris - demonstrated that the Kessler dynamic is not purely theoretical. Debris in LEO is eventually dragged into the atmosphere and burns up; debris in higher orbits persists for centuries. Tracking it is as fundamental to SSA as tracking the satellites themselves.
Why SSA matters beyond space
Space is not a self-contained domain. Its effects cascade across electromagnetic, ground, maritime, air, and information domains in ways that are often invisible until something breaks.
Electromagnetic domain
Almost every satellite communicates via RF, transmitting on bands from UHF through Ka-band and beyond. Those downlink transmissions, while attenuated by inverse square law and atmospheric absorption over hundreds of kilometers, can raise the noise floor of sensitive ground-based receivers during a pass. A single satellite pass is usually negligible; a dense constellation with overlapping passes can create persistent low-level degradation that erodes detection sensitivity for EW receivers and DSP arrays without triggering any obvious alarm. SSA-informed correlation - knowing which satellite is overhead, on what frequency, at what time - turns unexplained noise floor elevation from a mystery into a cataloged and predictable event. Additionally, adversary SIGINT and ELINT payloads in orbit can collect on ground-based emitters. While the physics of inverse square law make space-based electronic attack (jamming from orbit) extremely difficult, space-based collection is well-established.
PNT degradation
GPS, GLONASS, Galileo, and BeiDou are all space assets transmitting relatively weak signals from Medium Earth Orbit or GEO. The civilian GPS frequencies (L1 at 1575.42 MHz, L2 at 1227.60 MHz, L5 at 1176.45 MHz) are well-known, sensitive to jamming and spoofing from the ground, and equally sensitive to space weather. Ionospheric scintillation from geomagnetic storms degrades PNT accuracy without any adversary spending a dime. The cascading effects of PNT degradation are severe: RF direction-finding arrays need to know their own position to compute a bearing; on-the-move sensors need continuous PNT to geolocate contacts; cooperative sensors like ADS-B and AIS inherit whatever position error their host platform has; unmanned systems from commercial SUAS to autonomous surface vessels often fail-safe to landing or return-to-home when GPS is lost; and guided munitions with GPS/INS guidance inherit PNT error directly into their terminal accuracy. A degraded sensor that thinks it is in the wrong position is in some cases worse than a sensor taken offline, because the operator does not know the data is wrong.
Information domain
Space-based ISR provides sensing you cannot consent to or prevent. Hundreds of commercial and military imagery satellites orbit Earth multiple times per day, and the baseline commercial capability is already sufficient to expose operational movements in near-real-time. During Operation Epic Fury, Chinese commercial imagery providers - including the 43-satellite Jilin constellation and MizarVision - published annotated photography of repositioned US THAAD and Patriot batteries, with damage assessments circulating on Telegram channels before reaching mainstream press. Simultaneously, US commercial providers like Planet Labs froze imagery availability from the conflict zone, creating a narrative vacuum that adversary information operations filled with a mix of genuine satellite imagery, AI-modified imagery, and outright AI-generated fabrications. The progression from "commercial satellite takes photo" to "AI-generated disinformation on TikTok" happened within an orbit cycle. SSA is the prerequisite for countering this: knowing which satellites are overhead, when they can observe, and whether a claimed image is physically consistent with the orbital geometry at the stated time is a counter-narrative technique grounded in physics rather than fact-check graphics.
For a detailed walkthrough of cross-domain space effects including the Epic Fury case study, see How the Space Domain Impacts Your Operations.
The edge deployment problem
Space data is global, but the operators who need it are often in exactly the environments where connectivity is degraded, denied, or contested. A forward-deployed unit that needs to know when adversary ISR satellites will be overhead cannot wait for a cloud query to return if SATCOM is being jammed. An air defense battery that needs to correlate noise floor anomalies with satellite passes needs that correlation computed locally. SSA tooling that depends on persistent connectivity to function will fail exactly when the space picture matters most - which is when the adversary is actively contesting the electromagnetic and information environments.
Edge-deployable SSA runs the full propagation, enrichment, and correlation stack on hardware that deploys with the unit. Connectivity enriches the picture with fresher TLEs and broader catalog updates when available; its absence does not destroy the operator's ability to propagate known objects, compute pass windows, and correlate against the local sensor picture.
Where Empyrean fits
Empyrean's Space Situational Awareness module ingests TLE data from Space-Track and other providers, propagates orbits via SGP4/SDP4, enriches the catalog with ITU RF allocations and payload characterization from multiple databases, and renders pass windows, ground tracks, and revisitation patterns on the Common Operational Picture. The catalog is searchable and filterable by orbit regime, country, mission type, and propagation status - operators can pull every Chinese imagery satellite in LEO in seconds and have their orbital parameters, RF characteristics, and epoch freshness in front of them.
The SSA module integrates with the EMSO workspace for space-to-ground RF correlation: when a noise floor anomaly coincides with a predicted satellite pass on a known downlink frequency, the correlation is automatic rather than manual. It feeds into the Fusion & Decision Engine for cross-domain track association, and into the Wargaming & Simulation Engine for scenario planning against space-dependent threats. Pass window predictions inform the Automation Policy engine, enabling automated EMCON enforcement, sensor mode changes, or alert escalations tied to specific satellite overflight schedules - all running at the edge without cloud dependency.
The entire stack is edge-deployable and air-gap capable. The same software runs in a SCIF, on a FOB, at a commercial airport, or in a backpack. Connectivity makes it better; disconnection does not make it stop.
Going deeper
- SSA FAQ - quick-reference answers on SSA, SDA, and orbital mechanics concepts
- How the Space Domain Impacts Your Operations - deep dive into cross-domain space effects with the Epic Fury case study
- Space Situational Awareness - Empyrean's SSA capability page
- What is Sensor Fusion? - the fusion layer that processes space data alongside other domains
- What is Counter-UAS? - where space-based ISR threats meet the C-UAS kill chain
- Why JADC2 Needs Sensor Fusion at the Edge - the architectural case for edge deployment
