ESA Says SpaceX Would Not Move Satellite For Collision Avoidance | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-11.17.25

AirborneNextGen-
11.11.25

Airborne-Unlimited-11.12.25

Airborne-FltTraining-11.13.25

AirborneUnlimited-11.14.25

LIVE MOSAIC Town Hall (Archived): www.airborne-live.net

Sun, Sep 08, 2019

ESA Says SpaceX Would Not Move Satellite For Collision Avoidance

Company Responds That Communications Error Led To Confusion

A potential collision between two satellites led to a bit of a dust-up between ESA and SpaceX recently, which the U.S. company says was the result of a "bug" in its on-call paging system.

Engadget reports that authorities identified a one in 1,000 chance of a collision between ESA's Aeolus Earth Observation Satellite and SpaceX's Starlink Satellite 44. Holger Krag, head of the Space Debris Office at ESA, told Forbes that when SpaceX was informed of the potential for collision, the company said it would not change the orbit of its spacecraft. ESA fired the thrusters of the Aeolus satellite about half an orbit before the potential collision, if it was going to happen, was anticipated.

While the Aeolus satellite was in position nine months before the SpaceX bird, there are no laws governing right-of-way in space, according to the report. Krag said ESA was not upset by SpaceX's refusal to move, but expressed concerns about how often such an event might happen in the future, given the number of satellites currently in orbit, and the number expected to be launched in the years ahead.

Earlier this week, SpaceX released a statement it hoped would clear up the confusion about its interactions with ESA over the incident.

"Our Starlink team last exchanged an email with the Aeolus operations team on August 28, when the probability of collision was only in the 2.2e-5 range (or 1 in 50k), well below the 1e-4 (or 1 in 10k) industry standard threshold and 75 times lower than the final estimate. At that point, both SpaceX and ESA determined a maneuver was not necessary," the statement said. "Then, the U.S. Air Force's updates showed the probability increased to 1.69e-3 (or more than 1 in 10k) but a bug in our on-call paging system prevented the Starlink operator from seeing the follow on correspondence on this probability increase – SpaceX is still investigating the issue and will implement corrective actions. However, had the Starlink operator seen the correspondence, we would have coordinated with ESA to determine best approach with their continuing with their maneuver or our performing a maneuver."

(Image from file)

FMI: Source report

Advertisement

More News

NTSB Prelim: Funk B85C

According To The Witness, Once The Airplane Landed, It Continued To Roll In A Relatively Straight Line Until It Impacted A Tree In His Front Yard On November 4, 2025, about 12:45 e>[...]

Aero-News: Quote of the Day (11.21.25)

"In the frame-by-frame photos from the surveillance video, the left engine can be seen rotating upward from the wing, and as it detaches from the wing, a fire ignites that engulfs >[...]

ANN's Daily Aero-Term (11.21.25): Radar Required

Radar Required A term displayed on charts and approach plates and included in FDC NOTAMs to alert pilots that segments of either an instrument approach procedure or a route are not>[...]

Classic Aero-TV: ScaleBirds Seeks P-36 Replica Beta Builders

From 2023 (YouTube Edition): It’s a Small World After All… Founded in 2011 by pilot, aircraft designer and builder, and U.S. Air Force veteran Sam Watrous, Uncasville,>[...]

Airborne 11.21.25: NTSB on UPS Accident, Shutdown Protections, Enstrom Update

Also: UFC Buys Tecnams, Emirates B777-9 Buy, Allegiant Pickets, F-22 And MQ-20 The NTSB's preliminary report on the UPS Flight 2976 crash has focused on the left engine pylon's sep>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2025 Web Development & Design by Pauli Systems, LC