It appears we have missed another close call between two satellites – but how close did we really come to a catastrophic event in space?
It all began with a series of tweets from LeoLabs, a company that uses radar to track satellites and debris in space. It predicted that two obsolete satellites orbiting Earth had a 1 in 100 chance of an almost direct head-on collision at 9:39am AEST on 30 January, with potentially devastating consequences.
LeoLabs estimated that the satellites could pass within 15-30m of one another. Neither satellite could be controlled or moved. All we could do was watch whatever unfolded above us.
Collisions in space can be disastrous and can send high-speed debris in all directions. This endangers other satellites, future launches, and especially crewed space missions.
As a point of reference, NASA often moves the International Space Station when the risk of collision is just 1 in 100,000. Last year the European Space Agency moved one of its satellites when the likelihood of collision with a SpaceX satellite was estimated at 1 in 50,000. However, this increased to 1 in 1,000 when the US Air Force, which maintains perhaps the most comprehensive catalogue of satellites, provided more detailed information.
Following LeoLabs’ warning, other organisations such as the Aerospace Corporation began to provide similarly worrying predictions. In contrast, calculations based on publicly available data were far more optimistic. Neither the US Air Force nor NASA issued any warning.
This was notable, as the United States had a role in the launch of both satellites involved in the near-miss. The first is the Infrared Astronomical Satellite (IRAS), a large space telescope weighing around a tonne and launched in 1983. It successfully completed its mission later that year and has floated dormant ever since.
The second satellite has a slightly more intriguing story. Known as GGSE-4, it is a formerly secret government satellite launched in 1967. It was part of a much larger project to capture radar emissions from the Soviet Union. This particular satellite also contained an experiment to explore ways to stabilise satellites using gravity.
Weighing in at 83kg, it is much smaller than IRAS, but it has a very unusual and unfortunate shape. It has an 18m protruding arm with a weight on the end, thus making it a much larger target.
Almost 24 hours later, LeoLabs tweeted again. It downgraded the chance of a collision to 1 in 1,000, and revised the predicted passing distance between the satellites to 13-87m. Although still closer than usual, this was a decidedly smaller risk. But less than 15 hours after that, the company tweeted yet again, raising the probability of collision back to 1 in 100, and then to a very alarming 1 in 20 after learning about the shape of GGSE-4.
The good news is that the two satellites appear to have missed one another. Although there were a handful of eyewitness accounts of the IRAS satellite appearing to pass unharmed through the predicted point of impact, it can still take a few hours for scientists to confirm that a collision did not take place. LeoLabs has since confirmed it has not detected any new space debris.
But why did the predictions change so dramatically and so often? What happened?
Tricky situation
The real problem is that we don’t really know precisely where these satellites are. That requires us to be extremely conservative, especially given the cost and importance of most active satellites, and the dramatic consequences of high-speed collisions.
The tracking of objects in space is often called Space Situational Awareness, and it is a very difficult task. One of the best methods is radar, which is expensive to build and operate. Visual observation with telescopes is much cheaper but comes with other complications, such as weather and lots of moving parts that can break down.
Another difficulty is that our models for predicting satellites’ orbits don’t work well in lower orbits, where drag from Earth’s atmosphere can become a factor.
There is yet another problem. Whereas it is in the best interest of commercial satellites for everyone to know exactly where they are, this is not the case for military and spy satellites. Defence organisations do not share the full list of objects they are tracking.
This potential collision involved an ancient spy satellite from 1967. It is at least one that we can see. Given the difficulty of just tracking the satellites that we know about, how will we avoid satellites that are trying their hardest not to be seen?
In fact, much research has gone into building stealth satellites that are invisible from Earth. Even commercial industry is considering making satellites that are harder to see, partly in response to astronomers’ own concerns about objects blotting out their view of the heavens. SpaceX is considering building “dark satellites” the reflect less light into telescopes on Earth, which will only make them harder to track.
What should we do?
The solution starts with developing better ways to track satellites and space debris. Removing the junk is an important next step, but we can only do that if we know exactly where it is.
Western Sydney University is developing biology-inspired cameras that can see satellites during the day, allowing them to work when other telescopes cannot. These sensors can also see satellites when they move in front of bright objects like the Moon.
There is also no clear international space law or policy, but a strong need for one. Unfortunately, such laws will be impossible to enforce if we cannot do a better job of figuring out what is happening in orbit around our planet.
We need your help. The SpaceDaily news network continues to grow but revenues have never been harder to maintain.
With the rise of Ad Blockers, and Facebook – our traditional revenue sources via quality network advertising continues to decline. And unlike so many other news sites, we don’t have a paywall – with those annoying usernames and passwords.
Our news coverage takes time and effort to publish 365 days a year.
If you find our news sites informative and useful then please consider becoming a regular supporter or for now make a one off contribution.
US authorities said Friday they had granted permission to a TV provider to urgently lift a four-ton (3,600-kilogram) satellite to a so-called “graveyard orbit” over fears a battery fault may soon cause it to explode.
DirecTV had told the Federal Communications Commission its Boeing-built Spaceway-1 satellite had suffered a “major anomaly” in its batteries and did not have time to deplete its remaining fuel before disposing of it by placing it 300 kilometers (190 miles) above the “geostationary arc.” … read more
NASA’s Voyager 1 spacecraft is depicted in this artist’s concept traveling through interstellar space, or the space between stars, which it entered in 2012. Credit: NASA/JPL-Caltech
For the first time since November, NASA’s Voyager 1 spacecraft is returning usable data about the health and status of its onboard engineering systems. The next step is to enable the spacecraft to begin returning science data again. The probe and its twin, Voyager 2, are the only spacecraft to ever fly in interstellar space (the space between stars).
Voyager 1 stopped sending readable science and engineering data back to Earth on Nov. 14, 2023, even though mission controllers could tell the spacecraft was still receiving their commands and otherwise operating normally. In March, the Voyager engineering team at NASA’s Jet Propulsion Laboratory in Southern California confirmed that the issue was tied to one of the spacecraft’s three onboard computers, called the flight data subsystem (FDS). The FDS is responsible for packaging the science and engineering data before it’s sent to Earth.
The team discovered that a single chip responsible for storing a portion of the FDS memory—including some of the FDS computer’s software code—isn’t working. The loss of that code rendered the science and engineering data unusable. Unable to repair the chip, the team decided to place the affected code elsewhere in the FDS memory. But no single location is large enough to hold the section of code in its entirety.
So they devised a plan to divide affected the code into sections and store those sections in different places in the FDS. To make this plan work, they also needed to adjust those code sections to ensure, for example, that they all still function as a whole. Any references to the location of that code in other parts of the FDS memory needed to be updated as well.
After receiving data about the health and status of Voyager 1 for the first time in five months, members of the Voyager flight team celebrate in a conference room at NASA’s Jet Propulsion Laboratory on April 20. Credit: NASA/JPL-Caltech
The team started by singling out the code responsible for packaging the spacecraft’s engineering data. They sent it to its new location in the FDS memory on April 18. A radio signal takes about 22.5 hours to reach Voyager 1, which is over 15 billion miles (24 billion kilometers) from Earth, and another 22.5 hours for a signal to come back to Earth. When the mission flight team heard back from the spacecraft on April 20, they saw that the modification had worked: For the first time in five months, they have been able to check the health and status of the spacecraft.
During the coming weeks, the team will relocate and adjust the other affected portions of the FDS software. These include the portions that will start returning science data.
Voyager 2 continues to operate normally. Launched over 46 years ago, the twin Voyager spacecraft are the longest-running and most distant spacecraft in history. Before the start of their interstellar exploration, both probes flew by Saturn and Jupiter, and Voyager 2 flew by Uranus and Neptune.
Citation:
NASA’s Voyager 1 resumes sending engineering updates to Earth (2024, April 22)
retrieved 22 April 2024
from https://phys.org/news/2024-04-nasa-voyager-resumes-earth.html
This document is subject to copyright. Apart from any fair dealing for the purpose of private study or research, no
part may be reproduced without the written permission. The content is provided for information purposes only.
Osoyoos commuters can celebrate Earth Day as the Town joins in on a national commuter challenge known as “Leg Day,” entering a chance to win sustainable transportation prizes.
The challenge, from Earth Day Canada, is to record 10 sustainable commutes taken without a car.
“Cars are one of the biggest contributors to gas emissions in Canada,” reads an Earth Day Canada statement. “That’s why, Earth Day Canada is launching the national Earth Day is Leg Day Challenge.”
So far, over 42.000 people have participated in the Leg Day challenge.
Participants could win an iGo electric bike, public transportation for a year, or a gym membership.
The Town of Osoyoos put out a message Monday promoting joining the national program.
For more information on the Leg Day challenge click here.
Verticillium wilt is a problem for a lot of crops in Manitoba, including canola, sunflowers and alfalfa.
Read Also
The ugly truth of tuber trauma
Life can be tough on a tuber. Lots of things can cause blemishes or otherwise diminish the visual quality of…
In potatoes, the fungus Verticillium dahlia is the main cause of potato early die complex. In a 2021 interview with the Co-operator, Mario Tenuta, University of Manitoba soil scientist and main investigator with the Canadian Potato Early Dying Network, suggested the condition can cause yield loss of five to 20 per cent. Other research from the U.S. puts that number as high as 50 per cent.
It also becomes a marketing issue when stunted spuds fall short of processor preferences.
Verticillium in potatoes can significantly reduce yield and, being soil-borne, is difficult to manage.
Preliminary research results suggest earlier planting of risk-prone fields could reduce losses, in part due to colder soil temperatures earlier in the season.
Unlike other potato fungal issues that can be addressed with foliar fungicide, verticillium hides in the soil.
“Commonly we use soil fumigation and that’s very expensive,” said Julie Pasche, plant pathologist with North Dakota State University.
There are options. In 2017, labels expanded for the fungicide Aprovia, Syngenta’s broad-spectrum answer for leaf spots or powdery mildews in various horticulture crops. In-furrow verticillium suppression for potatoes was added to the label.
There has also been interest in biofumigation. Mustard has been tagged as a potential companion crop for potatoes, thanks to its production of glucosinolate and the pathogen- and pest-inhibiting substance isothiocyanate.
Last fall, producers heard that a new, sterile mustard variety specifically designed for biofumigation had been cleared for sale in Canada, although seed supplies for 2024 are expected to be slim. AAC Guard was specifically noted for its effectiveness against verticillium wilt.
Timing is everything
Researchers at NDSU want to study the advantage of natural plant growth patterns.
“What we’d like to look at are other things we can do differently, like verticillium fertility management and water management, as well as some other areas and how they may be affected by planting date,” Pasche said.
The idea is to find a chink in the fungus’s life cycle.
Verticillium infects roots in the spring. From there, it colonizes the plant, moving through the root vascular tissue and into the stem. This is the cause of in-season vegetative wilting, Pasche noted.
As it progresses, plant cells die, leaving behind tell-tale black dots on dead tissue. Magnification of those dots reveals what look like dark bunches of grapes — tiny spheres containing melanized hyphae, a resting form of the fungus called microsclerotia.
The dark colour comes from melanin, the same pigment found in human skin. This pigmentation protects the microsclerotia from ultraviolet light.
