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-05.20.24

Airborne-Unlimited-05.28.24

Airborne-FlightTraining-05.29.24 Airborne-Unlimited-05.30.24

Airborne-Unlimited-05.24.24

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

ANN FAQ: Contributing To Aero-TV

How To Get A Story On Aero-TV News/Feature Programming How do I submit a story idea or lead to Aero-TV? If you would like to submit a story idea or lead, please contact Jim Campbel>[...]

ANN's Daily Aero-Linx (05.29.24)

Aero Linx: International Association of Professional Gyroplane Training (IAPGT) We are an Association of people who fly, build or regulate Gyroplanes, who have a dream of a single >[...]

ANN's Daily Aero-Term (05.29.24): NORDO (No Radio)

NORDO (No Radio) Aircraft that cannot or do not communicate by radio when radio communication is required are referred to as “NORDO.”>[...]

Airborne 05.28.24: Jump Plane Down, Starship's 4th, Vision Jet Problems

Also: uAvionix AV-Link, F-16 Viper Demo, TN National Guard, 'Staff the Towers' A Saturday afternoon jump run, originating from SkyDive Kansas City, went bad when it was reported th>[...]

ANN's Daily Aero-Term (05.30.24): Beyond Visual Line Of Sight (BVLOS)

Beyond Visual Line Of Sight (BVLOS) The operation of a UAS beyond the visual capability of the flight crew members (i.e., remote pilot in command [RPIC], the person manipulating th>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

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