Skip to main content

NASA's Genesis Capsule crashes

It was to be plucked out of the air by two helicopters and brought back safely to Earth. But the Genesis space capsule carrying captured particles blown off the Sun crashed back to Earth in the Utah desert after some malfunctionality with its parachutes.


Genesis spacecraft on the ground. Source: www.nasa.gov

According to the latest news from the NASA website, the capsule impacted the ground at a speed of 311 kilometers per hour (193 mph). The officials cannot still say if any or some of the information brought back by the crashed capsule could be recovered.

In critical endeavours such as these, small mishaps could lead to fatal consequences. If I recall correctly, sometime in 1999 too the Polar lander had crashed when it was attempting to land on the Red Planet. So much for the unforgiving nature of these human endeavours to such small errors.


Comments

Popular posts from this blog

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.