Explainer: Why Did the Chandrayaan 2 Lander Take so Long to Find?

Read Next

India’s ambitious mission to land on the Moon failed. The Vikram lander, of the Chandrayaan 2 mission, crashed on the lunar surface on September 7, 2019, but it was only in December that scientists found it. Why did it take so long to find the lander?

There are quite a few technical reasons for that. Let’s start with a quick recap of what happened on the landing day.

An artist’s depiction of Vikram lander in lunar descent. Image: ISRO

The Vikram lander’s powered manoeuvres to land on the Moon worked just fine until it was 2.1 km above the surface. Then it lost communication with Earth. ISRO scientists in mission control could see from the data on their screens that the lander had also gone off-course. That means the lander wouldn’t land at the intended location. And that is what made finding Vikram challenging.

Needle in a haystack

Since ISRO had access to the data until loss of communication, it could crunch the numbers and work out an approximate search area for its Chandrayaan 2 orbiter. Not so much for NASA, whose Lunar Reconnaissance Orbiter (LRO) was tasked with finding a needle in a haystack. With ISRO not providing any details, NASA had to rely on guesswork and searching through billions of pixels. Noah Petro, the project scientist for LRO, told Space.com, “Until we know more details about where Vikram is, it’s going to be very hard for us to find it.”

The search challenges can be laid out as follows.

1. There are currently only two orbiters around the Moon that can take high resolution images of the surface. NASA’s LRO can see with a best resolution of 0.5 metres/pixel while Chandrayaan 2’s orbiter can do at best 0.32 metres/pixel. Given that the Vikram lander is not even 2 m across, what you are really looking for is just four pixels – among billions.

2. The orbiters cannot capture images at any time and over any place. We need to wait for the orbiter to go over the landing/crash region to image it. The orbits of Chandrayaan 2 and LRO take them over Vikram’s landing region about once a month.

3. Those four pixels of the lander need to be bright, i.e. reflecting sunlight. That required the lander, or its pieces, to be at a favourable angle to reflect ample sunlight relative to the orbiters. As you can imagine, this geometry isn’t a guarantee.

4. At each pass over the landing region by the orbiters, the Sun’s angle maybe different – low, high or somewhere in between. Low Sun angle means long shadows over the site, which makes the four pixels of the lander nearly impossible to find. So you need to wait for a high Sun angle on the site while simultaneously passing over it. This can take a while, which is exactly why LRO took long to get a good look.

5. When looking at the surface at an angle, surface features like mountains can obstruct your view to the lander. In case of long shadows, even small rocks can.

6. We need at least two images to be able to compare shots of before and after the lander hit the surface and thus have a confirmation.

These are the reasons it was so difficult to find where the Vikram lander was. Since Vikram didn’t land where it was meant to, pretty much the entire region in and around the original landing spot had to be scavenged painfully.

Finding Vikram

NASA’s LRO first passed over the Vikram’s landing region on September 17, when the Sun angle was very low. Most of the region was under shadow and the team found nothing. Any bright pixel, i.e sunlight being reflected off the lander, was indistinguishable from noise.

In line with their policy for publicly funded space missions, NASA released data collected from the pass on September 26, a mere nine days later. ISRO didn’t release any such data of the landing region from its orbiter. Amateurs around the world downloaded NASA’s mosaic of Vikram’s landing region and started scavenging it for any traces of Vikram. Shanmuga Subramanian, a Chennai-based engineer, contacted the LRO team with what seemed to him a piece of Vikram. It was a single bright pixel surrounded by shadows. Note that at this point it wasn’t known if the lander had made it to the surface in one piece or not.

LRO passed again over the landing region on October 14 and November 11 respectively. During these passes, the area around the bright pixel spotted by Subramanian was illuminated. The LRO team compared before and after images of the region and noticed a subtle difference.

Before and after images showing subtle changes to the surface after the Vikram lander crashed. Photo: NASA LROLRO scientists then stacked the images to enhance contrast, which allowed them to clearly see the crash site. It had the characteristic surrounding rays of an impact and multiple bright pixels littered around – Vikram’s pieces.

Before and after images with enhanced contrast showing the Vikram lander crash site, which is near center of the image. Diagonal straight lines are uncorrected background artefacts. Photo: NASA LRO.

Vikram lost and found, but ISRO?

ISRO stayed silent throughout on the state of the lander and switched its public outreach focus to the orbiter, which by the way doesn’t even have a name unlike Vikram and the rover Pragyan. We only got a visual confirmation of Vikram’s crash once NASA released images of the crash site showing pieces of the lander. It is indeed odd that the images didn’t come from ISRO, who said three days after the landing day that they had spotted the lander. ISRO failed to show any pictures or provide location coordinates to the public despite the claims.

The statement is in fact only the third and the last time ISRO publicly spoke of the lander’s condition. However, it didn’t stop ISRO from coming out of the slumber and boasting that they found the lander first, i.e. before NASA did with help from Subramanian.

Going by the publicly available evidence, NASA found the Vikram lander on the Moon’s surface, not ISRO. And what does Chandrayaan 2’s landing failure mean for ISRO? Go back to the launch pad.

This article first appeared on Jatan Mehta’s blog. Read the original here.