Space Intelligence (SPACEINT): Intelligence Discipline Guide

Orbits are deterministic and observable. A satellite cannot hide its manoeuvres from anyone willing to do the arithmetic, and much of the arithmetic is done for you in public.

What Space Intelligence is as a discipline

Space intelligence covers orbital activity, space asset characterisation, launch and deployment tracking, and counterspace risk. It rests on the fact that objects in orbit obey publicly modellable mechanics and are tracked by both government and amateur networks. Practitioners work with orbital element sets to propagate positions, detect manoeuvres by observing element discontinuities, catalogue newly launched objects, characterise payloads from orbit selection and behaviour, and monitor rendezvous and proximity operations where one object deliberately approaches another.

Sub-methods include catalogue correlation and object identification, manoeuvre and station-keeping analysis, conjunction and re-entry assessment, launch cadence and deployment pattern analysis, ground segment mapping, and downlink and licensing research. In the cycle it provides both indications and warning, through launch and manoeuvre detection, and targeting support for other disciplines by predicting overhead access windows for imaging or observation.

Why it matters

Only space intelligence answers when a given satellite was overhead a location, which is decisive for judging what an actor could have observed. It answers whether an object has manoeuvred and therefore has propulsion and active control, whether a launch deployed more payloads than declared, which objects are conducting proximity operations near others, and where the ground stations that command a constellation are located. It also determines whether a claimed capability is orbitally plausible at all.

What analysts actually look for

These are the concrete, observable signals that carry weight in this area of work:

Two-line element set changes indicating manoeuvres, orbit raising, station-keeping cadence and end-of-life disposal burns
Orbit selection: inclination, altitude and repeat ground track revealing mission type such as reconnaissance, communications or navigation
Launch manifests versus catalogued objects, exposing undeclared payloads, rideshares and deployed subsatellites
Rendezvous and proximity operations where objects close to unusually short separations and maintain relative position
Overhead access windows and lighting conditions determining what a given imaging satellite could realistically have collected
Radio frequency licensing and filing records for satellite downlinks, revealing operators, bands and intended coverage
Ground station locations and antenna infrastructure that link an on-orbit asset to a terrestrial operator and jurisdiction
Re-entry and decay predictions, plus debris-generating events that indicate collisions, breakups or destructive tests

Where the data comes from

Authoritative and openly available collection points. Always confirm licensing and terms before operational or commercial use:

CelesTrak — Free curated element sets, satellite catalogues, SupGP data and analysis tools maintained by a long-standing authority
Space-Track.org — Official US catalogue with element sets, decay and conjunction messages; free registration required and terms apply
n2yo — Free browser-based tracking, pass prediction and live position display, convenient for quick overhead access checks
ESA DISCOS and Space Debris Office reports — Object database and annual environment reports covering debris population, launch traffic and disposal compliance
UNOOSA Register of Objects Launched into Outer Space — Treaty-mandated state declarations of launched objects, useful for comparing declared against catalogued reality
Jonathan McDowell's Space Report and GCAT — Independently maintained launch and object catalogue with corrections and detailed historical context
SeeSat-L and amateur optical observation networks — Volunteer observations that recover objects not present in public catalogues and confirm manoeuvres
ITU space network filings and national licence records — Frequency and orbital slot filings identifying operators, bands and planned constellations before launch

A working method

A repeatable sequence beats ad-hoc searching. This is a practical starting workflow:

Frame the orbital question — Decide whether you need access windows, manoeuvre detection, object identification or operator attribution, since each drives a different data product.
Pull and correlate catalogues — Retrieve element sets from at least two sources and correlate catalogue numbers, international designators and names to a single object identity.
Propagate carefully — Use an appropriate propagator with fresh elements, respecting the accuracy limits and rapid staleness of general perturbations data.
Detect manoeuvres — Track element history over time and flag discontinuities in semi-major axis or inclination that no natural perturbation explains.
Characterise the mission — Infer likely function from orbit, launch vehicle, operator filings and downlink licensing, stating the inference chain explicitly.
Map the ground segment — Identify associated ground stations and licensing jurisdictions to connect the on-orbit asset to responsible terrestrial entities.
Report access, not certainty — Deliver overhead windows and behavioural findings with error bounds, distinguishing what an asset could have done from what it did.

How this connects across the intelligence taxonomy

Intelligence work does not respect neat boundaries. The mission domain you are working, the disciplines you practise, and the data points you pivot on are one connected system. These are the direct relationships for this entry — every link is also a tag, so you can follow any thread across the whole library.

Applied in these mission domains

Operates on these data points

GPS Coordinates — Precise latitude/longitude coordinates identifying an exact point on Earth — the atomic unit of GEOINT analysi
Radio Callsign — A licensed radio identifier for a station, vessel, aircraft, or operator.
Event / Incident — A discrete real-world occurrence — protest, strike, breach, seizure — with time, place, and actors.
Facility / Site — A physical installation — plant, base, port, data centre — with a fixed footprint and function.
Satellite Imagery — Overhead imagery of an area of interest, used for change detection and site analysis.

Related disciplines

Measurement & Signature Intel — Signatures, Measurements, and Physical Phenomena
Radio Frequency Intelligence — The Electromagnetic Spectrum as an Intelligence Source
Signals Intelligence — Intelligence from Intercepted Communications and Emissions

Inside the platform: where Space Intelligence lives

The Quantus platform is 204 pages behind a 147-item sidebar organised into six working groups: Command (24 items), Dashboards (15), Threat Theaters (14), Intelligence Domains (15), Investigate (34), and Administration (45). This entry is not a page in isolation — it is a thread running through several of them.

The modules that matter most here:

discipline.php?d=SPACEINT — Discipline hub
source-catalog.php?disc=SPACEINT — Source catalogue filtered to this discipline
search.php — Advanced search, filter and pivot
correlate.php — Correlation graph
cases.php — Case management

Each dashboard is local-first: it renders from the platform’s own database rather than depending on a live third-party call, so it still works when an upstream API is unreachable or rate-limited. Heavy aggregates are cached with a hard query time cap and degrade to the last good value instead of hanging the page.

Automation, playbooks and AI skills

Analysis that only happens when someone remembers to run it is not a capability. The platform ships a 30-step automation pipeline (cron.php) that collects, ingests, resolves, enriches, correlates and scores on a schedule — 25 seeders, 11 resolvers and 7 enrichment runners, all idempotent and cursor-based so a run can be interrupted and resumed without duplicating or losing work.

AI skills that apply

The 16 one-click operations in ai-skills.php are deterministic jobs, not free-text generation. The ones that matter here:

Score Country Risk
Sync Intel Domains
Resolve Everything
Summarise (Copilot)
Generate Report

Alerting closes the loop: rules in alerts.php fire on new indicators matching a saved query, so a first sighting in this area raises a notification rather than waiting to be noticed at the next review.

Feeds, data sources and the API

The collection layer runs a feed registry of free, machine-readable sources — bulk blocklists and trackers (Maltrail, IPsum, FireHOL, the full abuse.ch corpora, phishing databases, Emerging Threats, Spamhaus, DigitalSide, ThreatView), authoritative government feeds (CISA KEV, OFAC, UN and EU sanctions lists), and reference datasets (RIR allocations, ip-to-ASN and geolocation tables, MITRE ATT&CK, EPSS). collect.php pulls them server-side on a schedule; feeds.php and source-catalog.php show what is registered, what it covers and when it last ran.

Anything the platform holds is reachable programmatically. The REST API in api.php exposes 11 endpoints — status, stats, search, lookup, recent, export, bulk_check, top_threats, by_category, categories, check — and export.php streams 18 formats in bounded chunks, so a million-row export neither exhausts memory nor times out:

STIX 2.1, MISP, OpenIOC 1.1, CEF (ArcSight), LEEF 2.0 (QRadar), Zeek/Bro intel, Snort/Suricata rules, Palo Alto EDL, BIND RPZ, hosts blackhole, iptables, CSV, JSON, NDJSON/JSONL, XML.

That covers the CTI standards (STIX 2.1, MISP, OpenIOC), SIEM ingestion (CEF, LEEF, Zeek), detection engines (Snort/Suricata), and direct enforcement (Palo Alto EDL, BIND RPZ, hosts, iptables) — so intelligence developed here can be actioned in the tools you already run, without a manual reformatting step. A TAXII 2.1 server and a MISP/RSS feed are also served for pull-based sharing.

Use cases

Three ways this entry earns its keep in day-to-day work:

Triage under time pressure. An artifact or report lands and you need a defensible read in minutes, not days. Frame the orbital question is the first move; the platform pre-computes the enrichment so the analyst spends the time on judgement rather than lookups.
Building the picture. A single indicator is rarely the story. Propagate carefully turns one artifact into a network — shared infrastructure, repeated selectors, the same operator behind different names — via the correlation graph and the cross-entity link engine.
Producing something actionable. Analysis that ends in a document nobody can use is wasted. Report access, not certainty feeds the case file, the detection rule, the block list or the referral — with sourcing attached so the recipient can verify it.

Case management (cases.php), watchlists, saved searches and scheduled reports mean the work persists between sessions and survives an analyst leaving the team.

How each sector uses Space Intelligence

The same entry is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The underlying artifacts are shared — the constraints, outputs and thresholds are not.

🎖 Military and defence

Space intelligence supports overhead access prediction, which drives camouflage, concealment and deception timing, force protection and operations security. Analysts determine when adversary imaging or signals satellites are overhead a location, whether an object has manoeuvred and therefore has active control, and where the ground segment commanding a constellation sits. Products feed IPB, electromagnetic and visual signature management plans, and targeting support in the sense of understanding what an adversary could have observed. Constraints include the accuracy limits of public element sets, terms of use on catalogue data, and export control on space situational awareness data and some propagation software.

🕵 National intelligence

National intelligence uses orbital analysis as an indications and warning source: launch cadence changes, unexpected deployments, rendezvous and proximity operations and manoeuvres that indicate a change of mission. Requirements often concern whether a launch delivered what was declared and which operator actually controls an object. Because public catalogues underpin much of this work, unclassified assessments can be shared with partners and industry, while classified sensors resolve the residual ambiguity. Registration and licensing filings under treaty obligations provide a documentary layer, and the gap between what is registered and what is observed is itself a reportable finding.

👮 Law enforcement

Law enforcement rarely tasks orbital analysis directly, but it appears in export control and sanctions cases involving satellite technology, in fraud cases where claimed constellations do not exist, and in investigations of unauthorised transmissions to or from satellites. Element sets and catalogue records support timeline evidence about when an asset was overhead a location, which can corroborate or refute imagery provenance claims. Evidentially, catalogue data needs to be obtained and preserved with source and retrieval timestamps, and an expert is required to explain propagation error, because a predicted position is a model output rather than an observation.

🔍 Private investigation and corporate security

Corporate teams use space intelligence for competitor constellation tracking, due diligence on satellite ventures, insurance and claims analysis after an anomaly, and verification that a customer's imagery provenance claims are plausible. Public catalogues, launch records and regulatory filings answer most questions. Private actors must respect catalogue terms of use, particularly redistribution restrictions, and must not treat licensed space situational awareness data as freely shareable. Where analysis touches satellite technical data it may be export controlled, so sharing detailed assessments with foreign colleagues can require a licence even inside a multinational firm.

📰 Journalism and OSINT media

Journalists use orbital data to verify whether a satellite could have imaged a location at a claimed time, to document launches that governments do not announce, and to report on constellation growth and debris risk. Verification standards require using fresh element sets, stating the propagation software and the error bounds, and having an orbital analyst review conclusions, because propagated positions degrade quickly and confident errors are easy to make. Attribute the catalogue source and its terms. Be careful publishing precise tracking of sensitive assets, which in some jurisdictions raises national security concerns and can endanger amateur observers.

🌍 NGO, humanitarian and human rights

Humanitarian and human rights organisations use overhead access analysis to plan imagery tasking for documentation of atrocities, displacement and infrastructure destruction, and to understand what commercial imagery could exist for a given date and place. This makes evidence collection systematic rather than opportunistic. Do no harm applies to publishing imagery that identifies individuals or reveals the location of vulnerable communities. Duty of care includes recognising that adversaries also read overhead schedules, so publicising the timing of collection can endanger the people being documented.

🎓 University and research

Researchers in astrodynamics, space policy and space situational awareness work with public catalogues, optical observation networks and orbital determination methods. Methodology requires stating the element set epoch, the propagator, the force model and the resulting position uncertainty, since general perturbations data carries kilometre-scale errors that grow rapidly with propagation time. Data-sharing terms on catalogues restrict redistribution, so publish derived results and code rather than raw element sets where required. Ethics review is rarely engaged, but export control advice is prudent when work touches conjunction assessment or manoeuvre detection methods.

Playbook: working Space Intelligence end to end

A repeatable sequence, from the moment the requirement lands to the moment a product is delivered and the case is closed out. Each phase states what you are trying to establish, not merely what to click — the point is a defensible chain of reasoning, not a checklist.

Phase 1 — Frame the orbital question

Decide precisely which of four questions you are answering: overhead access windows, manoeuvre detection, object identification, or operator attribution. Each needs different data, different freshness and different error handling, and conflating them produces confident nonsense. A good output is a question statement naming the object or region, the time window and the required accuracy. Stop when you can state what accuracy the answer must have, because that determines whether public element sets suffice at all.

Phase 2 — Establish object identity across catalogues

Resolve the object to its catalogue number and international designator, and reconcile the names used by different sources, which frequently disagree, particularly for classified or recently launched objects. Record the launch, the deploying vehicle and any co-deployed objects. A good output is an identity record with cross-catalogue references and known naming disputes noted. Stop when identity is fixed or explicitly reported as ambiguous, since analysis of the wrong object is the most common and most embarrassing failure.

Phase 3 — Retrieve fresh element sets

Pull the most recent element sets available and record their epoch. Two-line element accuracy degrades from roughly a kilometre near epoch to tens of kilometres within days, and manoeuvring objects invalidate elements immediately. A good output is an element set archive with epochs, sources and retrieval timestamps preserved. Stop and refresh rather than propagating an old element set forward, and never mix element sets from different sources in a single propagation without reconciling their reference frames.

Phase 4 — Propagate with an appropriate model

Use the propagator the data was generated for, which for two-line elements means the SGP4 family, and do not feed those elements into a high-fidelity numerical propagator expecting better answers. Carry the uncertainty forward explicitly. A good output is a predicted position with a time and cross-track error estimate. Stop before quoting a position to a precision the model cannot support, which is the single most common misuse of public orbital data.

Phase 5 — Compute access windows

For an overhead access question, compute rise, culmination and set times with elevation, range and lighting conditions for the target location, and state the sensor's plausible field of regard rather than assuming nadir-only imaging. Agile satellites can image well off track. A good output is a window table with elevation, slant range, solar illumination and a stated assumption about pointing. Stop before concluding that a satellite did image a site; you can establish only that it could have.

Phase 6 — Detect manoeuvres from element history

Track element history over time and look for discontinuities in semi-major axis, eccentricity, inclination or mean motion that natural perturbations cannot explain. Distinguish routine station-keeping from significant plane or altitude changes. A good output is a manoeuvre timeline with the changed element, the magnitude and the inferred delta-v. Stop and check for catalogue processing artefacts before declaring a manoeuvre, since element set updates and cross-tagging produce apparent jumps that are not real.

Phase 7 — Characterise the mission

Infer likely function from orbit type, altitude, inclination, local time of ascending node, launch vehicle, deployment pattern, radio licence filings and operator statements. State the inference chain explicitly rather than asserting a mission. A good output is a function assessment with each supporting observation named and alternatives considered. Stop before asserting a payload type from orbit alone, since sun-synchronous orbits host imaging, weather, science and signals payloads alike.

Phase 8 — Reconcile registration and licensing

Check the UN register of objects launched into outer space, national registries, ITU space network filings and national spectrum licences. Objects that appear in the catalogue but not in registration filings, or filings for objects never observed, are both reportable findings. A good output is a reconciliation table by object. Stop when the documentary and observational pictures are compared, noting that registration is often late by months, so a gap is not immediately an anomaly.

Phase 9 — Map the ground segment

Identify the ground stations, teleports and gateway sites that command and receive from the constellation, using licence filings, corporate disclosures, imagery of antenna farms and network operator records. The ground segment ties an on-orbit asset to a terrestrial jurisdiction and a responsible entity. A good output is a ground segment map with the evidence per site. Stop when the sites relevant to the question are identified; comprehensive global mapping is rarely necessary.

Phase 10 — Analyse proximity and conjunction behaviour

Where two objects approach repeatedly or maintain relative station, examine closest approach distances over time and whether approaches are maintained by active control. Deliberate rendezvous and proximity operations look very different from chance conjunctions. A good output is a relative motion analysis with uncertainty, since public data often cannot distinguish a close pass from a distant one. Stop before characterising intent, which orbital mechanics alone cannot establish.

Phase 11 — Corroborate with observation and imagery

Where the conclusion matters, corroborate with optical or radio observation from amateur networks, published photometry, or imagery of launch and ground sites. Independent observation resolves catalogue ambiguity and confirms that an object is where the model says. A good output states which findings rest on catalogue modelling and which on observation. Stop when the highest-consequence claims have observational support or are explicitly flagged as model-only.

Phase 12 — Report access and behaviour, not certainty

Deliver overhead windows, manoeuvre history and behavioural findings with error bounds and the element set epochs used, and distinguish clearly between what an asset could have done and what it did. Honour catalogue terms of use in what you redistribute. A good output allows the customer to reason about adversary collection opportunity without overstating knowledge. Stop before asserting that a specific image was taken by a specific satellite unless the operator or metadata says so.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

Source register: what to collect from, and how

Sources are listed with their access model so you can plan around cost and licensing before you build a dependency on them. Open means no account required; registration means a free account or API key; licensed means paid or institutional access. Always confirm current terms — licensing changes, and a source that was free for research may not be free for commercial or evidential use.

Source	Access	What it gives you	How it is used here
CelesTrak	Open	Curated orbital element sets, satellite catalogues, SupGP data and extensive documentation on orbital data formats and accuracy	Primary open source for element sets plus the authoritative explanation of their accuracy limits
Space-Track	Registration	US Space Force catalogue of tracked objects with element sets, decay predictions, conjunction data and launch information	Authoritative catalogue with historical element set history, essential for manoeuvre detection
n2yo	Open	Web-based satellite tracking with pass predictions, live position display and searchable catalogue by name or number	Quick pass prediction and object lookup for triage before deeper analysis
ESA Space Debris Office and DISCOS	Registration	European database of launch, object, orbit and fragmentation data with annual environment reports	Authoritative debris and fragmentation history plus independent statistics on the orbital environment
UNOOSA Register of Objects Launched into Outer Space	Open	Treaty-mandated register of objects with launching state, orbital parameters and general function as declared	The documentary baseline against which observed objects and undeclared deployments are compared
Jonathan McDowell's space report and GCAT	Open	Independently maintained general catalogue of artificial space objects, launches and reentries with detailed notes	Resolves identity disputes and documents launches and deployments that official catalogues describe poorly
ITU space network filings and BR IFIC	Open	Satellite network filings with frequencies, orbital positions, service areas and the notifying administration	Attributes an orbital asset to a responsible administration and operator through its spectrum filing
FCC space station and earth station licensing	Open	US authorisations for satellite systems and earth stations with technical annexes, coverage and orbital debris plans	Detailed technical disclosure on constellations serving the US market, including ground segment locations
SeeSat-L and amateur optical observation community	Open	Long-running observer community publishing optical observations, orbital determinations and analysis of unlisted objects	Independent observation of objects absent from public catalogues, and confirmation of manoeuvres
SatNOGS	Open	Open network of ground stations receiving and archiving satellite beacons with observation metadata and schedules	Confirms an object is transmitting and when, corroborating catalogue and mission assessments
NASA Orbital Debris Program Office	Open	Quarterly news, modelling and analysis of the debris environment including breakup events and mitigation guidance	Authoritative analysis of fragmentation events, debris population growth and their long-term orbital consequences
Union of Concerned Scientists satellite database	Open	Curated list of operational satellites with operator, country, purpose, orbit class and launch details	Fast attribution of an object to an operator and declared purpose for triage and reporting
Secure World Foundation global counterspace assessment	Open	Annual open-source assessment of counterspace capabilities by country with sourcing and analytic caveats	Reference for counterspace risk assessment grounded in citable open evidence with explicit analytic caveats
Launch provider and operator disclosures	Open	Mission press kits, deployment sequences, orbital targets and customer manifests published around launches	Establishes what was declared to be deployed, which the catalogue can then be compared against
Heavens-Above	Open	Pass predictions, orbit displays and visibility calculations for satellites and the ISS from any specified location	Rapid visibility and pass checking for planning optical observation from a given site
Copernicus and commercial imagery archives	Registration	Archives of imagery acquisitions with acquisition times, sensor identifiers and footprints	Cross-checks whether imagery of a location actually exists for a claimed date and satellite

Prefer sources that publish a methodology and a revision history. A dataset that changes silently is a liability in any product that has to survive challenge.

Tooling

Tools commonly used against Space Intelligence. None of these replace judgement, and each carries its own failure modes — know what a tool infers versus what it observes.

python-sgp4 — Reference implementation of the SGP4 propagator for two-line elements; correct and fast, and it will happily produce precise-looking output far beyond the data's validity.
Skyfield — Astronomy and satellite position library with clear time and frame handling; excellent for access windows, requires the analyst to supply uncertainty reasoning.
Orekit — High-fidelity astrodynamics library supporting numerical propagation, orbit determination and manoeuvre estimation; powerful but heavy and Java-based.
GMAT — NASA mission analysis tool for trajectory design and analysis; capable of detailed modelling, oversized for routine catalogue work.
STK — Commercial modelling and simulation for access, coverage and sensor analysis; industry standard with strong visualisation, at substantial licence cost.
Gpredict — Open desktop tracking with pass prediction and radio Doppler correction; useful for planning observation, limited analytically.
TLE history archives and diff tooling — Compares successive element sets to detect manoeuvres; simple and effective, though catalogue processing artefacts produce false positives.
QGIS with ground track plugins — Plots ground tracks and access footprints against terrain and infrastructure; good for briefing products, careless projection use distorts coverage.
Optical observation setups with astrometry solving — Amateur telescope and camera systems producing independent positional observations; effective for confirming catalogue objects, weather and skill dependent.

AI skills and automation in detail

These are deterministic jobs with defined inputs and outputs, not open-ended prompting. Each is idempotent and cursor-based: interrupt one and it resumes where it stopped rather than duplicating work or losing progress.

Score Country Risk — Recomputes country risk from the weighted inputs and snapshots the result so movement over time is measurable.
Sync Intel Domains — Refreshes the reference and country-level intelligence datasets from their authorities.
Resolve Everything — Batch-resolves ASN, country, org and netblock for every IP from local reference datasets — no API calls, so it runs at millions of rows and works offline.
Summarise (Copilot) — Produces a narrative summary beside the underlying records. It explains; it never creates indicators or assigns attribution.
Generate Report — Assembles a sourced product from the current case or query, with provenance attached to each element.

A note on the boundary: the only skill that involves a language model is Summarise (Copilot), and it writes prose about records that already exist. Nothing else on this list involves generation of any kind. No indicator, relationship or attribution in the platform originates from a model. See the full skill list.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

Element sets are perishable. Accuracy is roughly a kilometre near epoch and degrades quickly, and any manoeuvre invalidates them entirely. Always record the epoch you used and refuse to propagate stale data forward merely because it is what you have.
Overhead is opportunity, not observation. Establishing that a satellite passed over a location proves it could have collected, nothing more. Agile pointing widens the field of regard, and cloud, tasking priorities and downlink capacity all intervene.
Manoeuvre detection requires element history, not a snapshot. Discontinuities only appear against a series, and catalogue cross-tagging and processing changes create false jumps, so verify an apparent manoeuvre against a second source before reporting it.
Local time of ascending node is a strong mission clue. Imaging constellations cluster around mid-morning for shadow contrast, while other functions choose different lighting, so orbital geometry narrows function even when the operator says nothing.
Registration gaps are findings but not immediately anomalies. Treaty registration is routinely months late, so compare against the typical lag for that launching state before treating an unregistered object as concealment.
The ground segment is where orbital assets become legally attributable. Antenna farms, teleport licences and gateway filings tie a satellite to a jurisdiction and a company far more firmly than the object catalogue does.
Honour catalogue terms of use. Space-Track redistribution restrictions are a licence condition, and breaching them costs your organisation access to the single most important dataset in the discipline for everyone who works there.

Measuring whether it is working

Capability claims should be falsifiable. These are the measures that show whether work on Space Intelligence is producing anything, and they are worth baselining before you change process or tooling.

Accuracy of predicted access windows against confirmed observation or operator-published acquisition times, tracked to validate propagation practice.
Proportion of reported manoeuvres confirmed by a second catalogue or independent observation before dissemination.
Median element set age used in delivered products, which directly bounds the credibility of every position statement.
Object identification error rate, measured by cases where analysis was later found to have used the wrong catalogue object.
Share of products stating explicit position uncertainty rather than a bare coordinate or time.
Time from a launch to a delivered assessment of what was deployed and whether it matches declarations.
Compliance rate with catalogue terms of use in redistributed products, audited rather than assumed.

Beware of measuring volume alone. Indicator counts and report counts rise easily and say little; time-to-attribution, proportion of findings that survive review, and how often a product changed a decision say a great deal.

Common pitfalls

Using stale element sets, which for low orbits degrade within days and produce confidently wrong position predictions
Assuming the public catalogue is complete; classified and small objects are frequently absent or deliberately withheld
Inferring collection from overhead passage, ignoring tasking priorities, sensor pointing, cloud cover and lighting conditions
Confusing natural orbital decay and drift with deliberate manoeuvre when analysing element history at low resolution
Attributing an object to a state based on launch site alone, when rideshare payloads routinely belong to other operators
Treating close approach in a conjunction message as intent when most close approaches are ordinary orbital coincidence

Legal and ethical considerations

Public catalogue access carries terms of use, notably Space-Track's restrictions on redistribution, which must be honoured. Space situational awareness data and some propagation software fall under export control regimes, and satellite technical data is frequently controlled under ITAR or dual-use lists. Amateur optical observation is lawful, but publishing precise tracking of sensitive assets may raise national security concerns in some jurisdictions. Treaty obligations under the Registration and Outer Space Treaties frame what states must declare, which shapes what absence of a record actually means.

Data integrity: no fabrication, no drift, no hallucination

Intelligence that cannot be traced back to a source is not intelligence, it is assertion. Everything in this entry — and everything in the platform behind it — is built on a small number of non-negotiable rules.

Provenance on every record

Every indicator carries the source that supplied it, a first-seen and last-seen timestamp, and a sighting count. Where several feeds report the same artifact, each contribution is recorded separately rather than collapsed, so you can see whether a finding rests on one source or twelve. Source attribution travels with the data into every export, so a recipient can audit a claim without asking you for the working.

Nothing is invented to fill a gap

If the platform has no data for Space Intelligence, it says so. Empty is displayed as empty — never padded with plausible-looking placeholder values, sample records or illustrative examples that a reader might mistake for observations. A dashboard with no rows is a true statement about collection coverage, and it is treated as a gap to close, not a blemish to hide.

Scoring is deterministic and reproducible

Threat scores, reputation grades and risk tiers are computed from stated inputs with fixed weights, not estimated. The same inputs always produce the same output, and the formula is visible rather than a black box. Aggregates are cached with an explicit time-to-live so a figure on screen is never silently stale — and when a heavy query exceeds its time budget the platform serves the last known-good value and labels it, rather than inventing a fresh number or hanging.

Where AI is used, and where it is not

Language models summarise and explain. They do not create indicators, assign attribution or manufacture relationships. No IP address, wallet, hash or identity in the platform originates from a model — every one is ingested from a named feed, resolved from a reference dataset, or entered by an analyst with a source recorded. Copilot output is presented as narrative alongside the underlying records, never in place of them, so a reader can always check the summary against the evidence.

Guarding against drift

Enrichment is additive and timestamped rather than overwriting. Reference data — sanctions lists, allocations, taxonomies — is re-synchronised from the authority on a schedule instead of being edited in place, so local copies cannot quietly diverge from the source of truth. Attribution is recorded with a confidence level and the reporting it rests on, and inferred relationships are labelled as inferred. When a source retracts or corrects, the correction propagates rather than leaving a stale assertion behind.

What this means for you

You can put a finding from this platform in front of a regulator, a court, a board or a partner agency and show where each element came from. That is the standard the tooling is built to — because in this work, being confidently wrong is more damaging than being usefully uncertain.

By the numbers

The taxonomy this entry belongs to is not a marketing list — it is the actual structure of the platform: 52 mission domains, 52 intelligence disciplines and 65 data points, each with a live dashboard behind it. Supporting that: 18 indicator types, 14 playbooks, 16 AI skills, 18 export formats and a 30-step automated pipeline.

This particular entry connects directly to 5 data points, 3 mission domains, 3 closely related entries — every one of them a tag you can follow, and a dashboard you can open.

Questions analysts actually ask

How accurate are public two-line element sets?

Roughly a kilometre in position near epoch for typical low earth orbit objects, degrading to tens of kilometres within days, and worse for high drag or recently manoeuvred objects. They are a general perturbations format designed to be used with the SGP4 propagator family, and feeding them into a high-fidelity numerical propagator does not improve them. For pass timing this usually means seconds to tens of seconds of uncertainty, which is fine for access analysis and useless for anything requiring metre-level knowledge. Always state the epoch and the propagation interval alongside any position claim.

Can I prove a satellite imaged a specific location?

Not from orbital data alone. You can establish that the satellite passed within a plausible field of regard at a given time with given lighting, which is opportunity. Whether it collected depends on tasking, cloud cover, downlink capacity and priorities you cannot see. Confirmation requires the operator's acquisition metadata, an imagery archive record showing a footprint and timestamp, or the imagery itself. Products should say the satellite could have collected, and reserve stronger language for cases where an archive or operator record confirms an acquisition took place.

How do I detect a manoeuvre reliably?

Build the element set history for the object over weeks, then look for step changes in semi-major axis, inclination, eccentricity or mean motion that atmospheric drag and natural perturbations cannot explain, and estimate the implied delta-v. Routine station-keeping produces small periodic corrections; mission changes produce larger discrete steps. Before reporting, check the same period in a second catalogue and look for signs of cross-tagging, where the catalogue has swapped identities between nearby objects, which produces dramatic false manoeuvres and is the most common trap.

What do I do about objects absent from public catalogues?

Turn to the amateur optical observation community, which has a long record of independently locating and computing orbits for objects that public catalogues omit or list without elements. Corroborate with launch reporting, deployment declarations and radio observation of downlinks. Report the object as observed rather than catalogued, give the observation source and epoch, and be careful about publishing precise tracking of sensitive assets, which raises legal and safety considerations for observers in some jurisdictions and can attract official attention to volunteers.

How do I attribute a satellite to an operator?

Work the documentary layer. ITU space network filings name the notifying administration; national licences, particularly US spectrum authorisations, name the operator and often describe the system in technical detail; the UN register records the launching state and declared function; and corporate filings and press material link the operator to owners. Cross-check the orbital regime and deployment against what the operator claimed. Where filings and observations disagree, report the discrepancy rather than resolving it silently, because inconsistency between declaration and behaviour is often the actual finding.

Are amateur observations good enough for professional work?

For confirming presence, timing and manoeuvres, yes, and they are frequently the only independent check available. Experienced observers produce astrometric positions and derived orbits of documented quality, and the community has repeatedly detected behaviour before it appeared in public catalogues. Record the observer, equipment, time standard and reduction method as you would for any measurement, and prefer multiple independent observers for anything consequential. For precise orbit determination or conjunction assessment, professional sensor networks remain necessary.

What are the legal constraints on this work?

Mostly terms of use and export control rather than criminal law. Space-Track imposes redistribution restrictions that bind your organisation, and breaching them can cost access. Space situational awareness data, conjunction assessment methods and some propagation software fall under export control regimes, and satellite technical data is frequently controlled under ITAR or dual-use lists, so sharing detailed analysis with foreign nationals may require authorisation. Optical observation is lawful, but publishing precise tracking of sensitive assets raises national security sensitivities in some jurisdictions and merits legal advice.

Standards, frameworks and further reading

Work that references a recognised framework is easier to defend, easier to hand over, and easier for a partner to consume:

Outer Space Treaty 1967, which establishes state responsibility for national space activities including those of non-governmental entities.
Convention on Registration of Objects Launched into Outer Space 1976, which requires states to register objects and furnish orbital parameters and general function.
Liability Convention 1972, which governs responsibility for damage caused by space objects and underpins operator accountability questions.
ITU Radio Regulations and space network filing procedures, which allocate frequencies and orbital positions and identify responsible administrations.
IADC Space Debris Mitigation Guidelines and the UN COPUOS guidelines, which set disposal, passivation and post-mission lifetime expectations.
CCSDS orbit data messages, which standardise the exchange of orbit ephemeris, mean elements and conjunction data between operators.
US export control regimes including ITAR category XV and dual-use controls, which cover satellite technical data and space situational awareness methods.
Space-Track user agreement terms, which govern redistribution of catalogue data and bind institutional users of the primary open catalogue.

References

Primary sources and authoritative references for this entry. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

CelesTrak orbital data and documentation — CelesTrak. Curated element sets with authoritative documentation on formats, propagators and accuracy limits
Space-Track satellite catalogue — US Space Force, 18th Space Defense Squadron. Official catalogue of tracked objects with element set history and decay predictions
Register of Objects Launched into Outer Space — UN Office for Outer Space Affairs. Treaty-mandated registry of space objects with declared orbital parameters and function
Space Environment Report and DISCOS database — European Space Agency. Annual assessment of the orbital environment with launch, fragmentation and object statistics
General Catalog of Artificial Space Objects — Jonathan McDowell. Independent catalogue resolving object identity, launches and reentries with detailed sourcing
Orbital Debris Quarterly News — NASA Orbital Debris Program Office. Analysis of breakup events, debris population and mitigation performance
Satellite Database — Union of Concerned Scientists. Curated operational satellite list with operator, purpose and orbit classification
Global Counterspace Capabilities report — Secure World Foundation. Annual open-source assessment of counterspace programmes with explicit sourcing
Space network filings and BR IFIC — International Telecommunication Union. Satellite frequency and orbital position filings identifying responsible administrations
Space station and earth station licensing records — US Federal Communications Commission. Technical authorisations for satellite systems and ground segment serving the US market

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this entry: tracks catalogues, manoeuvres and overhead access windows and links orbital assets to operators and ground segment. Explore the platform, or browse the rest of the library by following any tag above.