Home›Maneuver Tracker›Close Approaches›HAWK-15A ⟷ PELICAN-12
HighProximity
WithdrawnNewer orbit data from 14 Nov 22:47 UTC no longer shows this pass. Within 40 minutes of the predicted time the two stayed at least 34.3 km apart. The most recent pass the screening confirmed up to its time: 8.06 km on 15 Nov 08:37 UTC.
After the passBest estimate, from the orbit data published nearest its time: within 40 minutes of the predicted time the two stayed at least 35.2 km apart.
Closest approach15 Nov 202602:37 UTC
Drift speed4.1 m/s15 km/h, seen from PELICAN-12
Altitude591 kmlow Earth orbit
Last confirmed14 Nov02:42 UTC · withdrawn

US HAWK-15A and US PELICAN-12 were predicted to reach a closest approach of 2.34 km at 2026-11-15 02:37 UTC, drifting past at about 4.1 m/s (15 km/h) as seen from PELICAN-12. Withdrawn: newer orbit data from 14 Nov 22:47 UTC no longer shows this pass. Within 40 minutes of the predicted time the two stayed at least 34.3 km apart. The figure above is the forecast as it was published; the newer check is shown beside it, and nothing is overwritten. Best estimate after the pass, from the orbit data published nearest its time: within 40 minutes of the predicted time the two stayed at least 35.2 km apart. Miss distance and time of closest approach are computed by propagating the latest published orbital elements for both objects, and each pass is re-checked every 20 minutes as new element sets are published. See the Satellite Maneuver Tracker for the live picture and space situational awareness for context.

Why it mattersBoth objects are catalogued as payloads. Screening continues as new element sets arrive; operators act on their own conjunction data.

The Two Objects

Dossiers from the satellite directory
HAWK-15APayload
NORAD 101119
CountryUS
Launched2026-10-20
COSPAR2026-237J
Maneuver capableUnknown
PELICAN-12Payload
NORAD 101128
CountryUS
Launched2026-10-20
COSPAR2026-237T
Maneuver capableUnknown

Where This Happens

Altitude context
DEBRIS BELT 700–1000 KM2006001,0001,5002,000 kmTHIS PASS · 591 KMISS 420Starlink 550

At 591 km this pass sits in low Earth orbit. Objects here stay up for decades: there is too little atmospheric drag to clean the band naturally. Why crowded bands matter →

History Between This Pair

5 predicted passes under 10 km
Pair history · HAWK-15A ⟷ PELICAN-12
2026-11-15 08:378.06 km Final forecast0.01 km/s583 kmView →
2026-11-15 07:332.66 km Final forecast · after: 1.56 km0.00 km/s592 kmView →
2026-11-15 06:072.88 km Not re-confirmed · after: 12.4 km0.00 km/s590 kmView →
2026-11-15 05:137.07 km Withdrawn · after: ≥22.9 km0.01 km/s583 kmView →
2026-11-15 02:372.34 km Withdrawn · after: ≥35.2 km0.00 km/s591 kmShown above

Repeat encounters are common for objects in near-intersecting orbital planes. Each pass is re-screened as fresh element sets arrive; "Final forecast" means the screening still predicted it within 45 minutes of its time, "Not re-confirmed" means later screening stopped finding it.

Forecast Record

Every figure published for the pass shown above, newest first. Nothing is overwritten: a withdrawn forecast keeps its figure, with the newer check beside it, and the best estimate after the pass is a row of its own.
Computed · figure · predicted time · orbit data · by
20 Nov 06:11 UTC35.16 km Best estimate15 Nov 03:18 UTC15 Nov 01:47 UTCBest estimate
14 Nov 09:02 UTC35.34 km Withdrawn15 Nov 03:18 UTC14 Nov 06:06 UTCRe-check
14 Nov 02:22 UTC2.34 km Forecast15 Nov 02:37 UTC13 Nov 14:48 UTCRe-check
14 Nov 02:02 UTC3.91 km Forecast15 Nov 02:02 UTC13 Nov 14:48 UTCScreen
14 Nov 01:42 UTC5.31 km Forecast15 Nov 01:42 UTC13 Nov 14:48 UTCScreen

These Objects Elsewhere

Other screened approaches · 7 days
674 m11-17 13:22 UTC
HAWK-15ACONNECTA IOT-6
744 m11-14 06:44 UTC
PELICAN-12SIRIUS-B
1.20 km11-14 08:10 UTC
PELICAN-12SIRIUS-B

How These Numbers Are Computed

Miss distance and TCA come from propagating the latest published orbital elements for both objects and searching for the minimum separation over the screening window. Element sets carry kilometre-scale uncertainty, so figures here describe a close pass, not a collision prediction; a change in either object's published elements re-computes the pass automatically. What is a conjunction? → How conjunction assessment works →