From the October 2005 issue

Discovering Dactyl

When the Galileo spacecraft flew past Ida in 1993, no one expected to find a moon. Its discoverer recalls how it happened.
By | Published: October 25, 2005 | Last updated on May 18, 2023

Editor’s note: On August 28, 1993, the Galileo spacecraft — on its way toward Jupiter to begin a successful 8-year mission — flew past asteroid 243 Ida. It was Galileo’s second asteroid flyby, following an October 1991 encounter with 951 Gaspra. But Ida had a big surprise: a 1-mile-wide (1.6 kilometer) moon was found orbiting the 35-mile-diameter (56 km) main-belt asteroid. Ann Harch, an assistant science coordinator on Galileo’s imaging team, discovered the moon. This is her story.

Two years of painstaking planning preceded the August 28, 1993, Ida encounter. Because the Galileo spacecraft’s high-gain antenna did not unfurl, we had to make do with a much slower transmission rate than originally planned — just 10 bits per second. So, instead of sending back every last bit of blank space from the image mosaics, the imaging team played back just 3 lines out of every 20 or so. These “jailbar” images let us preview where the important data would be.

Immediately after the Ida encounter, we jailbarred the high-resolution mosaic of Ida. A few minutes before closest approach, Galileo took 30 frames to cover enough area to be sure it would capture all of Ida. The jailbar images revealed Ida in 5 of those 30 frames. It took a month to play them back. For the next 4 or 5 months, the downlink performance dropped too low for playback to continue.

Ida and Dactyl
The Galileo spacecraft imaged Ida’s tiny moon for the first time in 1993. Dactyl was the first satellite found orbiting an asteroid.
NASA / JPL
On February 17, 1994, we were scheduled to receive the first data since the playback of the high-resolution image. It was a jailbar image taken about 10 minutes before closest approach. When the data hit the ground, I got a call from Lisa Wainio at the Multimission Image Processing Facility, who cryptically inferred there was something very odd about the image.

Herb Breneman, Catherine Heffernan (fellow assistant science coordinators under Ken Klaasen on the Solid State Imager team), and I locked ourselves in this dark little closet that had an imaging machine, and we called up the image to take a look. It was important to be secretive about these things so information didn’t leak to the press before it was properly blessed by the imaging team. That was frustrating, because I always wanted to show the engineers and sequence-team people.

When the image came up, Ida was big in the field of view and had about 10 jailbars passing through it. Because the jailbars consisted of 3 lines out of every 20 or so, there were only 3 lit lines for every 17 or so dark lines. For one of those jailbar sets that passed near the center of Ida, 2 of the 3 lines were missing, leaving only one lit line on Ida. It was immediately obvious that, off the asteroid’s bright limb, there were 15 lit pixels of something or other sitting in that single jailbar line.

My first words were something like “What is that?!” The light emanating from the screen of those 15 pixels showed Dactyl, and it had struck my eyes about a nanosecond before it fell into Catherine’s and Herb’s.

We immediately began to investigate. It was clear the little thing had what looked like a sharp, bright limb located, where it should be, on the sunward side, and what looked like a trailing off terminator on the other side. There was no question that if the data were not garbled, this was a little object that had the same approximate albedo (surface brightness) as Ida.

Dactyl
The battered surface of Dactyl bears more than a dozen craters at least 250 feet (80m) across. The biggest crater, which lies on the terminator, measures 1,000 feet (300m) wide. This is Galileo’s highest-resolution view of Dactyl, taken from 2,400 miles (3,900 km) away.
NASA / JPL
After some merriment and carrying on among the three of us, I exclaimed that we had to call imaging team member Joe Veverka. Joe’s response really annoyed me. I said: “Joe, you’ll never guess what we found in the jailbar image. There’s a little object off the bright limb of Ida! It’s 15 pixels across and has a little limb and a terminator.” Joe, being a seasoned veteran of the space business, said something like, “Hmm, are you sure? You know we’ve seen things like this before. Since you only have one line through it, I wouldn’t get your hopes up.” I said, “You’re no fun. I’m going to call Mike,” and hung up. I then called Mike Belton, who was the leader of the imaging team, and he was very excited. (I should note, after Joe got a look at the jailbar image, he became excited about it, too.)

It’s hard to recall, but I think it took about 3 weeks before the ground-system folks found the two missing jailbar lines and confirmed Dactyl. We weren’t allowed to tell anyone about it. I couldn’t keep my mouth shut, and must have told half a dozen people outside the team, swearing them all to secrecy. Later on, we got the full playback of that image and saw the whole little bugger.

But this was just the start of the fun. That image was taken about 10 minutes before closest approach, when Dactyl was still quite small. Once the object was confirmed, the questions started to fly. Is it in orbit? Where is it relative to Ida? Might it be in the highest-resolution images?

Ken Klaasen went off and, with his pencil, a straight edge, and calculator, did some triangulation to determine if the little object might be in one or more of the high-resolution mosaics. His calculations predicted there was a good chance it could be in the 30-frame, high-resolution mosaic that had the best full-frame image of Ida. This was the one we had jailbarred right after closest approach.

In the meantime, images of Dactyl — not yet named, by the way — were rolling in slowly during the playback of Galileo’s approach images. By sheer luck, Dactyl was positioned horizontally to Ida, meaning that every playback scheduled of Ida would also return Dactyl without having to return any additional data. We got a picture of Dactyl in every approach image played back.

When the jailbar sequence for the high-resolution mosaic finally executed and had been played back, we were once again sitting in our dark little closet. This time, it was just Ken and me. Up came the pictures, one after another. All of a sudden, there it was: a little bright object straddling two jailbar lines. We were so happy. I’ve never seen Ken so excited. We went into the hallway and were literally holding hands, jumping up and down like two little kids, laughing and squealing. By then, we didn’t have to hide anything.

So, that’s the story of Dactyl. It was a heck of a lot of fun. In my mind. it rivaled Voyager 2’s first blue images of Neptune that I thought nothing would beat. And then I thought the same thing after Ida and Dactyl, until NEAR-Shoemaker arrived at the near-Earth asteroid Eros. There’s nothing like being on the front lines of discovery.

At some point during the playback, Mike told me the imaging team was conferring upon me the honor of being the discoverer of Dactyl. That was cool, although I think Lisa technically saw it first. I took it as a gift from the team for those 2 years of planning the encounter, and the three-quarters of a year shepherding that painfully slow playback at 10 bits per second.

Two years of painstaking planning preceded the August 28, 1993, Ida encounter. Because the Galileo spacecraft’s high-gain antenna did not unfurl, we had to make do with a much slower transmission rate than originally planned — just 10 bits per second. So, instead of sending back every last bit of blank space from the image mosaics, the imaging team played back just 3 lines out of every 20 or so. These “jailbar” images let us preview where the important data would be.

Immediately after the Ida encounter, we jailbarred the high-resolution mosaic of Ida. A few minutes before closest approach, Galileo took 30 frames to cover enough area to be sure it would capture all of Ida. The jailbar images revealed Ida in 5 of those 30 frames. It took a month to play them back. For the next 4 or 5 months, the downlink performance dropped too low for playback to continue.

Ida and Dactyl
The Galileo spacecraft imaged Ida’s tiny moon for the first time in 1993. Dactyl was the first satellite found orbiting an asteroid.
NASA / JPL
On February 17, 1994, we were scheduled to receive the first data since the playback of the high-resolution image. It was a jailbar image taken about 10 minutes before closest approach. When the data hit the ground, I got a call from Lisa Wainio at the Multimission Image Processing Facility, who cryptically inferred there was something very odd about the image.

Herb Breneman, Catherine Heffernan (fellow assistant science coordinators under Ken Klaasen on the Solid State Imager team), and I locked ourselves in this dark little closet that had an imaging machine, and we called up the image to take a look. It was important to be secretive about these things so information didn’t leak to the press before it was properly blessed by the imaging team. That was frustrating, because I always wanted to show the engineers and sequence-team people.

When the image came up, Ida was big in the field of view and had about 10 jailbars passing through it. Because the jailbars consisted of 3 lines out of every 20 or so, there were only 3 lit lines for every 17 or so dark lines. For one of those jailbar sets that passed near the center of Ida, 2 of the 3 lines were missing, leaving only one lit line on Ida. It was immediately obvious that, off the asteroid’s bright limb, there were 15 lit pixels of something or other sitting in that single jailbar line.

My first words were something like “What is that?!” The light emanating from the screen of those 15 pixels showed Dactyl, and it had struck my eyes about a nanosecond before it fell into Catherine’s and Herb’s.

We immediately began to investigate. It was clear the little thing had what looked like a sharp, bright limb located, where it should be, on the sunward side, and what looked like a trailing off terminator on the other side. There was no question that if the data were not garbled, this was a little object that had the same approximate albedo (surface brightness) as Ida.

Dactyl
The battered surface of Dactyl bears more than a dozen craters at least 250 feet (80m) across. The biggest crater, which lies on the terminator, measures 1,000 feet (300m) wide. This is Galileo’s highest-resolution view of Dactyl, taken from 2,400 miles (3,900 km) away.
NASA / JPL
After some merriment and carrying on among the three of us, I exclaimed that we had to call imaging team member Joe Veverka. Joe’s response really annoyed me. I said: “Joe, you’ll never guess what we found in the jailbar image. There’s a little object off the bright limb of Ida! It’s 15 pixels across and has a little limb and a terminator.” Joe, being a seasoned veteran of the space business, said something like, “Hmm, are you sure? You know we’ve seen things like this before. Since you only have one line through it, I wouldn’t get your hopes up.” I said, “You’re no fun. I’m going to call Mike,” and hung up. I then called Mike Belton, who was the leader of the imaging team, and he was very excited. (I should note, after Joe got a look at the jailbar image, he became excited about it, too.)

It’s hard to recall, but I think it took about 3 weeks before the ground-system folks found the two missing jailbar lines and confirmed Dactyl. We weren’t allowed to tell anyone about it. I couldn’t keep my mouth shut, and must have told half a dozen people outside the team, swearing them all to secrecy. Later on, we got the full playback of that image and saw the whole little bugger.

But this was just the start of the fun. That image was taken about 10 minutes before closest approach, when Dactyl was still quite small. Once the object was confirmed, the questions started to fly. Is it in orbit? Where is it relative to Ida? Might it be in the highest-resolution images?

Ken Klaasen went off and, with his pencil, a straight edge, and calculator, did some triangulation to determine if the little object might be in one or more of the high-resolution mosaics. His calculations predicted there was a good chance it could be in the 30-frame, high-resolution mosaic that had the best full-frame image of Ida. This was the one we had jailbarred right after closest approach.

In the meantime, images of Dactyl — not yet named, by the way — were rolling in slowly during the playback of Galileo’s approach images. By sheer luck, Dactyl was positioned horizontally to Ida, meaning that every playback scheduled of Ida would also return Dactyl without having to return any additional data. We got a picture of Dactyl in every approach image played back.

When the jailbar sequence for the high-resolution mosaic finally executed and had been played back, we were once again sitting in our dark little closet. This time, it was just Ken and me. Up came the pictures, one after another. All of a sudden, there it was: a little bright object straddling two jailbar lines. We were so happy. I’ve never seen Ken so excited. We went into the hallway and were literally holding hands, jumping up and down like two little kids, laughing and squealing. By then, we didn’t have to hide anything.

So, that’s the story of Dactyl. It was a heck of a lot of fun. In my mind. it rivaled Voyager 2’s first blue images of Neptune that I thought nothing would beat. And then I thought the same thing after Ida and Dactyl, until NEAR-Shoemaker arrived at the near-Earth asteroid Eros. There’s nothing like being on the front lines of discovery.

At some point during the playback, Mike told me the imaging team was conferring upon me the honor of being the discoverer of Dactyl. That was cool, although I think Lisa technically saw it first. I took it as a gift from the team for those 2 years of planning the encounter, and the three-quarters of a year shepherding that painfully slow playback at 10 bits per second.