Recommended Posts

What is the "Black Knight" satellite? It is a mysterious satellite, of unknown origin, discovered in 1960 which shadowed Sputnik. It is believed to have been of extraterrestrial origin, and signaled back old radio waves from the 1920s and 1930s before it disappeared. In short wave patterns analyzed by astronomer Duncan Lunan, it revealed its origin as Epsilon Bo?tes (or the star system as it was 13,000 years ago).

In "Disneyland of the Gods", by John Keel, he reports in depth on this satellite:

"In February 1960 the US detected an unknown object in polar orbit, a feat that neither they or the USSR had been able to accomplish. As if that wasn't enough, it apparently was several sizes larger than anything either country would have been able to get off the ground.

And then, the oddness began. HAM operators began to receive strange coded messages. One person in particular said he managed to decode one of the transmissions, and it corresponded to a star chart. A star chart which would have been plotted from earth 13,000 years ago, and focused on the Epsilon Bostes star system.

On September 3, 1960, seven months after the satellite was first detected by radar, a tracking camera at Grumman Aircraft Corporation's Long Island factory took a photograph of it. People on the ground had been occasionally seeing it for about two weeks at that point. Viewers would make it out as a red glowing object moving in an east-to-west orbit. Most satellites of the time, according to what little material I've been able to find on the black knight satellite, moved from west-to-east. It's speed was also about three times normal. A committee was formed to examine it, but nothing more was ever made public.

Three years later, Gordon Cooper was launched into space for a 22 orbit mission. On his final orbit, he reported seeing a glowing green shape ahead of his capsule, and heading in his direction. It's said that the Muchea tracking station, in Australia, which Cooper reported this too was also able to pick it up on radar traveling in an east-to-west orbit. This event was reported by NBC, but reporters were forbidden to ask Cooper about the event on his landing. The official explanation is that an electrical malfunction in the capsule had caused high levels of carbon dioxide, which induced hallucinations."

source

Monday, Mar. 07, 1960

Time Magazine

Three weeks ago, headlines announced that the U.S. had detected a mysterious "dark" satellite wheeling overhead on a regular orbit. There was nervous speculation that it might be a surveillance satellite launched by the Russians, and it brought the uneasy sensation that the U.S. did not know what was going on over its own head. But last week the Department of Defense proudly announced that the satellite had been identified. It was a space derelict, the remains of an Air Force Discoverer satellite that had gone astray. The dark satellite was the first object to demonstrate the effectiveness of the U.S.'s new watch on space. And the three-week time lag in identification was proof that the system still lacks full coordination and that some bugs still have to be ironed out.

First Sighting. The most important component of the space watch went into operation about six months ago with the construction of "Dark Fence," a kind of radar trip wire stretching across the width of the U.S. Designed by the Naval Research Laboratory to keep track of satellites whose radios are silent, it is a notable improvement on other radars, which have difficulty finding a small satellite unless they know where to look. Big, 50-kw. transmitters were established at Gila River, near Phoenix, Ariz, and Jordan Lake, Ala., spraying radio waves upward in the shape of open fans. Some 250 miles on either side, receiving stations pick up signals that bounce off any object passing through the fans. By a kind of triangulation, the operators can make rough estimates of the object's speed, distance and course.

On Jan. 31 Dark Fence detected two passes of what seemed to be an unknown space object. After detecting several passes during the following days, Captain W. E. Berg, commanding officer of Dark Fence, decided that something was circling overhead on a roughly polar orbit. He raced to the Pentagon and in person reported the menacing stranger to Chief of Naval Operations Arleigh Burke. Within minutes the news was communicated to President Eisenhower and marked top secret.

In the confusion, there was a delay before anyone took the step necessary to positively identify the strange satellite: informing the Air Force's newly established surveillance center in Bedford, Mass. It is the surveillance center's job to take all observations on satellites from all friendly observing centers, both optical and electronic, feed them into computers to produce figures that will identify each satellite, describe its orbit and predict its behavior. Says one top official, explaining the cold facts of the space age: "The only way of knowing that a new satellite has appeared is by keeping track of the old ones."

It took two weeks for Dark Fence's scientists to check back through their taped observations, and to discover that the mysterious satellite had first showed up on Aug. 15. The Air Force surveillance center also checked its records to provide a list of everything else that was circling in the sky, and its computers worked out a detailed description of the new object's behavior. The evidence from both Air Force and Navy pointed to Discoverer V, fired from Vandenberg Air Force Base, Calif, on Aug. 13.

SOURCE: Time Magazine

Link to comment
https://www.neowin.net/forum/topic/1132764-the-black-knight-satellite/
Share on other sites

I'm guessing that's not an actual pic :p

On topic, if indeed there is that "unknown" satellite out there, why not come CLOSER to it ?

May or not be -- the pic poster did not give any source.

Could they take color high altitude pictures in 1960 ... ?

post-37120-0-72970400-1359078950.jpg

Did the Russians detect the unknown satellite and keep it secret ?

Who discovered the Black Knight ...

Hmmm ...

In 1953, four years before the U.S.S.R. launched Sputnik I, an object of unknown origin was sighted by Dr Lincoln La Paz of the University of New Mexico orbiting the earth. As more reports of sightings trickled in from around the world, the U.S. Department of Defense appointed distinguished astronomer Clyde W. Tombaugh (best known for his discovery of the dwarf ?planet? of Pluto in 1930) to run a search for the mystery object. The blip became known as "Black Knight".

The Pentagon never formally released the results of Dr Tombaugh?s study. No more was heard about the object until December, 1957, when Dr Luis Corralos of the Communications Ministry in Venezuela photographed it. The first modern satellites, Sputnik I & 2, had been launched just a few months earlier. Dr Corralos was taking pictures of the second of these modern marvels as it passed over Caracas, and his photos caught the unknown object shadowing the Russian craft.

"Black Knight" was observed once again in 1960, this time by one of the stations that formed the Northern American Air Defense System. The object was in a polar orbit, something that neither the Americans or Soviets were capable of at the time. Several times larger and heavier than anything capable of being launched with 1960 rockets, it shouldn?t have been there, but it was. The observance sent panic through the U.S. military. Not only did the intelligence agencies have no idea that the USSR had launched a new satellite, nothing in their reports on Soviet space activity suggested they had the capacity to place an object into a polar orbit, or to launch something that was estimated to be in excess of 15 tons. The military scientists were horrified, since they were at least four years away from achieving polar orbits and getting payloads that large into space.

Similar waves of shock and anxiety were spreading through the Soviet ranks. They had not launched the satellite and knew they were years away from being able to accomplish such a feat, they also knew that the Americans could not do it either. No one knew where it came from, but it was definitely there.

Camera Tilt: High Oblique

Camera Focal Length: 250mm

Camera: HB: Hasselblad

Film: 5069 : Kodak Elite 100S, E6 Reversal, Replaces Lumiere, Warmer in tone vs. Lumiere.

Thanks for clearing that out good sir

you missed 5069 = " Color positive"

http://eol.jsc.nasa....55517610441.tsv

Looks like it is an official NASA pic.

Thanks.

Sounds doubtful this is the 'Black Knight' then:

Mission: STS088 Roll: 724 Frame: 66 Mission ID on the Film or image: STS88

Country or Geographic Name: OCEAN

Features: PAN-SNGLNT., SPACE DEBRIS

In 1987 Shuttle Endeavour Mission STS-088 photographed a mysteries object orbiting the Earth. There are 5 photos of the object on the NASA web site. It clearly shows a large orbit circling the Earth. Is it possible that NASA inadvertently photographed the Black Knight satellite? Could this be the same object Gordon Cooper spotted over Australia while on its 22 orbit on board Faith 7?

Thanks for clearing that out good sir

you missed 5069 = " Color positive"

I just copy pasted from the nasa link ;)

Thanks.

Sounds doubtful this is the 'Black Knight' then:

Hard to really say on what it is. I guess that is what makes the theory so exciting.

Well no matter what the picture shows, the Black Knight Satellite topic is interesting because it keeps coming up year after year and apparently has been in circulation since the 1960s in various sizes and shapes.

The biggest issue is finding real information on it, but glancing through it does indicate some kind of tangible info.

I wish my grandfather was still around (died about 3 years ago) He and his wife were ham operators during this time and even had talked to some of the apollo missions. But they also did some yellow tape on the side with the polarbear network and codfish networks. They have QSL cards from all over the world... 73's

Edited by eXtermia

if it's a space debris, then it's a debris from what?

Good question. ;)

I wish my grandfather was still around (died about 3 years ago) He and his wife were ham operators during this time and even had talked to some of the apollo missions. But they also did some yellow tape on the side with the polarbear network and codfish networks. They have QSL cards from all over the world... 73's

Cool story.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
    • Google reportedly limited Meta's Gemini access over limited AI compute by Karthik Mudaliar Google is reportedly limiting Meta's use of its Gemini AI models after Meta tried buying more computing capacity than even Google could supply. According to the Financial Times, Google told Meta in March that it could not provide the full Gemini capacity that Meta had requested. This shortfall even disrupted and delayed some of Meta's internal projects. Due to this, Meta even told its employees internally to use AI tokens more efficiently. Meta wasn't the only one to get hit by this sudden refusal by Google; even other customers were affected. But Meta was hit harder because of its unusually high demand for Google's models. The move from Google makes it evident that companies all over are in limited supply of both infrastructure and compute. Alphabet said in April that Google Cloud revenue grew 63% year-over-year to $20 billion in the first quarter, helped by enterprise AI infrastructure and AI solutions. In pursuit of more compute, Meta had earlier signed a multi-billion-dollar AWS agreement as well as a large AMD GPU deal for AI data centers. But the crunch would be short-lived as both Meta and Google have also ramped up infrastructure investments heavily. Meta said in November that it was committing more than $600 billion in the U.S. by 2028 for AI technology, infrastructure, and workforce expansion. In the first quarter of this year, Meta also raised its expected capital expenditure for 2026 to a range of $125 billion to $145 billion, citing higher component pricing and additional data center costs for future capacity. However, this doesn't make the company immune to the current dependence on outside suppliers. Meta has also spent many years promoting Llama as an open-weight alternative to closed models from Google, OpenAI, and Anthropic. But if the reported reliance on Google's Gemini models is severe enough for internal work to get impacted, then it looks like even frontier labs and Big Tech aren't fully self-sufficient. Source: Financial Times
    • I like to reminisce about the good old days, way back in autumn 2025 when building a gaming machine was fun and the drives were about $150 when you caught a deal. Yes duh, back in the day we had it gone. Then baby Skynet came along, hiding in AI datacenters demanding more processing power until it reached singularity. End of a not totally fictional story.
    • My experience in the past with older Windows 11 builds was not great on unsupported machines but I recently used Rufus to put the latest build on a older 5th Gen Core Thinkpad T that we upgraded with a SATA SSD and 8GB of RAM four years ago when hardware was reasonable and it seemed pretty fast and solid. Customer is very happy with the performance and will probably get four more years out of that venerable laptop that he loves so much. Another customer just retired his Dell Studio laptop from 2009 running Windows 10. It got an SSD over 10 years ago and did everything he needed it to for 17 years but he also retired last year and is happy doing everything on his iPad now.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      533
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!