Follow one launch through eleven steps, from its first signal to a record anyone can examine. Use the chapter list to jump around.
Real places. Representative paths. Explore the ideas, then open the public dashboard for launch records.
The origin
Choose a launch site and follow an ascent. The place is real; the path opens a wider view of the sky we share.
Change your perspective. Choose a launch site. Watch the view move around Earth.
A location identifies the origin. It does not tell you every mission’s flight path or where each payload will go. The paths here demonstrate the concepts.
The signal
An observed signal begins an investigation. Follow how a LaunchDetect record connects time, place, and source so someone else can examine the evidence.
Follow the signal. Play the ascent or scrub through it, one moment at a time.
Observation time and publication time answer different questions. They are recorded separately, and neither one is a delivery guarantee.
The possible path
A line shows one possible path. The space around it helps explain where a search might begin as assumptions and observations change.
Make room for possibility. Move the width slider and see the space around the path change.
The range of possible positions, not the rocket’s size. This width control explains the idea; it is not a measured confidence interval or a map of confirmed debris.
The next observation
A launch record gives the next observation a starting point. Explore how direction, timing, and viewing geometry can help focus a search.
See the connection. Isolate the sensing layer to follow the link between spacecraft and ascent.
A cue suggests where or when to look. Tracking needs observations of the object, and custody requires keeping its identity associated over time. A launch alert alone does not establish custody.
Launch COLA
Two paths can cross without their objects arriving together. Change the timing to see why launch collision avoidance analysis considers position, time, and uncertainty as one picture.
Keep the paths. Change the timing. Try Earlier, Aligned, and Later. Then play or scrub the shared timeline to follow both objects.
A crossing shows geometry. A possible close approach needs both objects near one another at the same time. Assessing its significance also needs object sizes, relative motion, and uncertainty. A screening candidate is not a confirmed collision.
This example explains timing. It does not calculate collision probability or assess a real event.
Radar cueing
Explore a modeled pass above Hawaiʻi. A reference station shows how the horizon, direction, and timing shape a cue an operator can test.
Follow the handoff. Play the pass. Watch the station turn toward the corridor when the object rises above its local horizon.
No. Geometric visibility is one condition. Acquisition also depends on the sensor, the object, operating conditions, and tasking. A useful cue becomes a question the operator can test.
A conceptual station at a Hawaiʻi reference location. The coast orbit and pass are teaching examples.
Observing new objects
New payloads, spent hardware, and possible fragments need separate histories. Explore why repeated observations must be associated with an object before an orbit can be estimated.
Look along the corridor. Follow three modeled objects and an orbiting observer. The view respects Earth’s obstruction of the sightline.
Time-tagged observations can support orbit determination once measurements are associated with an object. A two-line element set, or TLE, is one way to represent a fitted orbit for use with its matching propagation model. A cue alone does not produce a validated TLE.
The scene shows a sensing workflow. Its objects and measurements are conceptual; no orbit catalog is produced here.
Continuity in orbit
Bring launch context into your screening workflow. Compare where new objects may travel with the spacecraft you already operate.
Change the arrival time. Follow the amber payload and the blue spacecraft. A shared region only matters when you compare their positions at the same time.
A close approach is a reason to investigate, not a collision prediction. Assessment requires orbit estimates, uncertainties, object sizes, and follow-up observations.
From an event to a defensible record
A launch record gives insurance teams a dated, sourced starting point. Connect it to the missions they cover, then follow what changed.
Follow the review. Start with one mission, widen the view to the fleet, then see what belongs in a useful event record. Select a story row to look closer.
Launch context can support underwriting and incident review. This scene does not calculate loss, premiums, coverage, or the likelihood of a claim.
A connected space picture
Carry launch context into traffic coordination, situational awareness, and domain awareness. Help existing systems connect the next observation to the bigger picture.
Follow the information. Watch a new arrival, build an observation history, then carry the context into a shared space picture. Select any story row to revisit that step.
Launch context complements tracking and operational systems. It does not by itself establish a complete catalog, maneuver guidance, or an object’s intent.
From a coastal launch to a shared ocean
Follow a hypothetical launch from Wenchang on China’s Hainan coast. At separation, the upper stage heads toward orbit. The spent stage returns toward waters west of Luzon in the Philippines.
Where LaunchDetect fits
Watch the paths divide. Follow liftoff, separation, and return. Switch perspectives or pause anywhere to see how the two journeys connect.
State where an event was observed or a return is predicted. Keep the event time separate from the time a notice was issued.
Identify the observation or model behind a statement. A launch detection, a return forecast, and a confirmed debris sighting answer different questions.
Share the estimated range and its assumptions. Mark what remains unconfirmed, then update the record as better evidence arrives.
A spent stage falling during launch is different from an uncontrolled return from orbit. Both highlight the value of clear location, timing, and evidence.
For uncontrolled orbital returns, voluntary international space sustainability guidelines encourage timely information sharing and cooperation to improve predictions.
Launch context can give regional teams a starting point for investigation. A forecast, an observation, and a confirmed return should remain distinct as the picture develops.
Read the guidelines · B.9 ↗A hypothetical sequence from Wenchang toward waters west of Luzon. Hardware is enlarged for clarity. This is not an actual flight, return forecast, or maritime boundary.
From the LaunchDetect archive ↗Examine a real
Launch