City-obliterating asteroid screamed past Earth the other night – and boffins only clocked it just 26 hours beforehand

'We should have seen it earlier' astro-prof tells El Reg after rock whizzed between us and Moon

Video An asteroid zipped past Earth on Thursday, close enough to slide in between our planet and the Moon – and nobody knew the bloody thing was coming until about a day earlier, when it was within spitting distance.

If it had actually smashed into our homeworld, it could have had the same city-annihilating effect of a 5MT thermonuclear warhead going off, we're told.

The near-Earth object was finally spotted by astronomers at the SONEAR observatory in Oliveria, Brazil, at about midnight UTC on 24 July. A second crew of scientists working on the US-based ASAS-SN project, which stands for All-Sky Automated Survey for Supernovae, observed it ten hours later.

Kris Stanek, a professor of astronomy at Ohio State University and co-principal investigator of ASAS-SN, told The Register today that telescopes in Texas and Hawaii snapped several images of the cosmic boulder whizzing across the sky.

“The data showed that there was something moving - and it’s moving fast. The telescopes take 90 second exposures and the thing was moving in between all those exposures. So we needed to figure out what it was because it was moving too fast,” he said.

'That’s a little too close for comfort'

The rock, now known as Asteroid 2019 OK (no, not OK), was heading toward Earth at speeds greater than 20 kilometres per second. It continued to streak across the sky, and passed us at a distance of about 80,000 kilometres – roughly just a fifth of the distance between Earth and the Moon – in between 0100 and 0200 UTC on Thursday, July 25.

“That’s a little too close for comfort. Although nothing happened on Earth, it’s a little unsettling. We should have seen it earlier,” Stanek said.

“It originally came from the opposite direction from the Sun, so it was very much observable since it would have been dark enough to spot it. But then as it came closer, it passed in front of the Sun was lost in the Sun’s glare. In fact, telescopes in Hawaii from the ATLAS (Asteroid Terrestrial-impact Last Alert System) project did observe it earlier in July and the data was logged. It’s just nobody flagged it up.”

So, Asteroid 2019 OK inched closer and closer to Earth right under our noses, and slipped right by us with just a day’s notice. You can watch an animation that retraces the trajectory of Asteroid 2019 to get an idea of just how close it narrowly missed us below:

Luckily, the Earth emerged unscathed. Scientists reckon the hunk of rock could be anywhere from 60 to 130 metres in diameter, which would be big enough to wipe out an entire city if it hit our homeworld.

Hayabusa2 gives asteroid asteroid 1999JU3 the horn

Hayabusa2 stirs up rubble on surface of Ryugu, pokes asteroid with sampling horn


“If it's 100 metres in diameter, it would leave a crater about 1 kilometre in diameter, and the explosion energy would be equivalent to five megatons of TNT,” Stanek told El Reg.

"If it had hit Columbus, Ohio, then there would be Columbus, Ohio, no more. But if it hits somewhere where there is nothing, then not much would happen. If it hits the ocean, it may incite a tsunami, but not one that’s life threatening."

Asteroid 2019 OK is actually pretty small in respect to other asteroids. Though, for a near-Earth object, it’s quite big. It has a strange orbit that flings it beyond Mars at its furthest distance from the Sun and brings it back in within Mercury and Venus at its closest point from the Sun. Beyond that, however, it’s pretty typical apparently.

“That rock is really not that interesting, it’s just it came so close to us,” he said. ®

Similar topics

Other stories you might like

  • Google Pixel 6, 6 Pro Android 12 smartphone launch marred by shopping cart crashes

    Chocolate Factory talks up Tensor mobile SoC, Titan M2 security ... for those who can get them

    Google held a virtual event on Tuesday to introduce its latest Android phones, the Pixel 6 and 6 Pro, which are based on a Google-designed Tensor system-on-a-chip (SoC).

    "We're getting the most out of leading edge hardware and software, and AI," said Rick Osterloh, SVP of devices and services at Google. "The brains of our new Pixel lineup is Google Tensor, a mobile system on a chip that we designed specifically around our ambient computing vision and Google's work in AI."

    This latest Tensor SoC has dual Arm Cortex-X1 CPU cores running at 2.8GHz to handle application threads that need a lot of oomph, two Cortex-A76 cores at 2.25GHz for more modest workloads, and four 1.8GHz workhorse Cortex-A55 cores for lighter, less-energy-intensive tasks.

    Continue reading
  • BlackMatter ransomware gang will target agriculture for its next harvest – Uncle Sam

    What was that about hackable tractors?

    The US CISA cybersecurity agency has warned that the Darkside ransomware gang, aka BlackMatter, has been targeting American food and agriculture businesses – and urges security pros to be on the lookout for indicators of compromise.

    Well known in Western infosec circles for causing the shutdown of the US Colonial Pipeline, Darkside's apparent rebranding as BlackMatter after promising to go away for good in the wake of the pipeline hack hasn't slowed their criminal extortion down at all.

    "Ransomware attacks against critical infrastructure entities could directly affect consumer access to critical infrastructure services; therefore, CISA, the FBI, and NSA urge all organizations, including critical infrastructure organizations, to implement the recommendations listed in the Mitigations section of this joint advisory," said the agencies in an alert published on the CISA website.

    Continue reading
  • It's heeere: Node.js 17 is out – but not for production use, says dev team

    EcmaScript 6 modules will not stop growing use of Node, claims chair of Technical Steering Committee

    Node.js 17 is out, loaded with OpenSSL 3 and other new features, but it is not intended for use in production – and the promotion for Node.js 16 to an LTS release, expected soon, may be more important to most developers.

    The release cycle is based on six-monthly major versions, with only the even numbers becoming LTS (long term support) editions. The rule is that a new even-numbered release becomes LTS six months later. All releases get six months of support. This means that Node.js 17 is primarily for testing and experimentation, but also that Node.js 16 (released in April) is about to become LTS. New features in 16 included version 9.0 of the V8 JavaScript engine and prebuilt Apple silicon binaries.

    "We put together the LTS release process almost five years ago, it works quite well in that we're balancing [the fact] that some people want the latest, others prefer to have things be stable… when we go LTS," Red Hat's Michael Dawson, chair of the Node.js Technical Steering Committee, told The Register.

    Continue reading

Biting the hand that feeds IT © 1998–2021