What Was Star K, the Mysterious Missing Planet of the 19th Century?

Updated on August 14, 2017
1701TheOriginal profile image

Leonard Kelley holds a bachelor's in physics with a minor in mathematics. He loves the academic world and strives to constantly explore it.

Source

Like many good mysteries, it is best to establish the characters. In this true story, I will first examine the background on the individual responsible for the hype over *K, then we shall dive into what this object could have been...

Source

Credentials

James Ferguson was already a renowned astronomer when he entered into the *K mystery. Before that though, he had found the first asteroid from a 9.6 refracting telescope: 31 Euphrosome, on September 1, 1854. He followed this up with teo more asteroids: 50 Virginia on October 4, 1857 and 60 Echo on September 14, 1860. Clearly, this guy could spot celestial objects. Others noticed his skill, also. Twice (in 1854 and 1860) he received the Lalande Prize of the French Academy of Sciences. He would retire with over 90 papers published and was considered very reliable which is what makes this case so bizarre and something that likely haunted him for years after the object disappeared (Baum 43).

Beginning

The story of *K began on April 12, 1849 when Annibale de Gasparis, the assistant astronomer at Specola di Capodimonte in Naples, found a new 10th magnitude object in the sky. By comparing its motion to stars around it, the mystery object was found to have retrograde motion and a general heading along the equator.

On May 11th, Fabri Scarpellini announces that after more observations the object is in fact an asteroid and is named 10 Hygiea. Our buddy Ferguson decided to do some follow-up observations through the summer and fall of 1850 using a filar to measure the angular distance with nearby stars as a reference (43, 45).

What is this filar, you may ask? It was a micrometer located “at the common focus of the objective lens” an was a great tool for finding the accurate angular distance between objects. Inside the box was 2 wires on parallel frames which moved towards each other or away, depending on the twist of a screw. One would calibrate the filar for one revolution based on the angular distance seen at that magnification and go on from there. This tool would play a role to come and possibly explain what happened (46-7)

Source

What is It?

With all these observations in tow, the discovery of 10 Hygeia was published in The Astronomical Journal on January 18, 1851. Amongst the readers was John Russell Hind from the Royal Astronomical Society, whose big interest was on planets beyond Uranus. Remember, this was in the aftermath of the Neptune drama, so planets were all the rage. And because Hind was searching, he was familiar with many regions of the sky in hopes of seeing some deviations. One of those patches was the area that 10 Hygiea happened to have been in when Ferguson was making his filar measurements, so Hind took a look. Upon examining that area of the sky, he found that 8 out of the 22 stars Ferguson had used were not in Hind’s stellar catalogue. Upon cross refencing with others, Hind was able to account for all but one, a 9.10 magnitude star labeled *K. Nowhere in his maps could said star be found, so was there a mistake on someone’s part? (47-9)

After all, 10 Hygeia had been found during a point where it had been travelling in front of a dense star field. But Ferguson had mentioned in his report that he had not included stars he felt had been incorrectly measured. Besides, Hind knew of Ferguson’s quality in his work and therefore did not doubt him. Hind could only conclude it was a variable star or even perhaps a new asteroid. The latter possibility reached Lt. Maury, the chief of Ferguson, through William Bond, a mutual friend of both Maury and Ferguson who also happened to be the director of the Harvard College Astronomical Observatory (49-50).

Once Maury found out, he sent Ferguson on the hunt for *K. The first night of observation was conducted on August 29, 1851 using a large refractor but nothing was spotted. Maury decided to have the 1850 data examined in hopes of spotting it and back tracking its position. They found that the right ascension would have changed but not the declination. Using this, a possible candidate for *K was spotted in October 16-22, 1850 data but interspersed. Hind hears about this and feels *K must be a planet and so writes to William Gram, the secretary of the US Navy, about it. With the recent Neptune debacle, fresh in everyone’s minds, Gram wastes no time in prompting Hind to get on the case. Therefore, Ferguson was again tasked with hunting down *K (50-1).

By November of 1851, a positive identification still eluded Ferguson. Thus, Hind decided to seek some advice and writes to his friend Benjamin Apthorp Gould about *K. Ben feels that based on the right ascension change, the object cannot be a mistake and that the motion means it cannot be between Mars and Jupiter. Using Kepler’s Laws, he arrives as a distance of 137 AU and a period of 1600 years. Of course, Ben knows such a visible object doesn’t turn off and on with such rapidity and he mentions the intrigue behind such a phenomenon (52-3, 38).

Time goes by and still nothing was found. Ferguson grew concerned for if *K was real then it was heading into the Sagittarius constellation which is star dense and hard to get photo plates for. Not much had been documented and so discerning an object amongst a sea of unknowns would be a challenge. Despite this, he presses on and starts to photograph the area on August 29, 1851. He continued on until December 11, when he finally gave up in frustration (54, 38).

So what happened here? We clearly have a respectable astronomer unable to locate an object that was repeatedly viewed but not consistently present. Christian Heinrich Friedrich, a later astronomer of the 19th century, felt the filar was to blame. You see, three different wires are present in it for different levels of calibration, with the number one wire closest to the main screw. Through some calculations of stars near the *K sightings, Friedrich was able to show that a majority of Ferguson’s observations was actually using the first wire when he had recorded using the second. With this in mind, Friedrich converted the data of Ferguson and was able to show that *K was in fact Lalande No. 36613, a normal star. Any moment when the star disappeared was due to misreading the wire value. Many astronomers made sure to emphasize that this was a minor mistake of Ferguson and that no disgrace should befall him (62-3).

© 2017 Leonard Kelley

Comments

    0 of 8192 characters used
    Post Comment

    • 1701TheOriginal profile imageAUTHOR

      Leonard Kelley 

      18 months ago

      Thanks, Coffeequeeen! I love mysteries of astronomy and I don't hear people talking too much about this one. Here is to hoping this may change that!

    • Coffeequeeen profile image

      Louise Powles 

      18 months ago from Norfolk, England

      Space and astronomy has always interested me. I've never heard of this before, so reading your article has been really interesting. I've learned something today, thankyou. =)

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, owlcation.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://owlcation.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)