Anomaly•Registry
AR-0151

The Kecksburg Incident

Partially explained
Date 9 December 1965
Location Kecksburg, Mount Pleasant Township, Westmoreland County, Pennsylvania, United States
Coordinates 40.1847, -79.4614

Summary

On 9 December 1965 a fireball was seen over Ontario and at least eight US states, and people in Kecksburg, Pennsylvania, said something had fallen into the woods. The fireball was a meteor that ended more than 300 kilometres away, and the search at Kecksburg found nothing.

The recovered, acorn-shaped craft now linked to the village first appeared in accounts given nearly 25 years later. The Soviet space probe most often offered as the answer is ruled out in NASA's own catalogue. What happened in the woods rests on a thin 1965 record and a much thicker later one.

where the fireball ended, against where it was said to land Detroit, Windsor end of the fireball's flight Lake Erie more than 300 km apart Pittsburgh Kecksburg said to be where it fell 100 km THE METEOR ENDED MORE THAN 300 KM AWAY 1965: the search found nothing. Cosmos 96: ruled out by NASA. the acorn-shaped craft first appears nearly 25 years later.
Figure Drawn by Anomaly Registry from NASA's catalogue entry for Cosmos 96, Chamberlain and Krause's 1967 trajectory study as summarised by Robert Sheaffer, and James Oberg's 2008 statement. A sketch map, to scale, of where the fireball's flight ended, near Windsor or over western Lake Erie, and Kecksburg, more than 300 km to the south-east.

What is documented

The fireball. At 4.43 pm Eastern Standard Time (21:43 UT) on 9 December 1965, a bright fireball was seen, in the words of NASA's spacecraft catalogue, "over southwestern Ontario, Canada and at least eight states from Michigan to New York".

Kecksburg. Kecksburg is a village about 55 kilometres south-east of Pittsburgh. According to Joe Nickell and James McGaha, writing in the Skeptical Inquirer in 2012, a boy playing outdoors there saw an object plummet into nearby woods. NASA's catalogue records "unconfirmed reports" that the fireball landed near the village at 4.46 pm, and adds that estimating the impact point of a fireball from eyewitness accounts "is notoriously inaccurate." The space writer James Oberg says that from the Kecksburg area the meteor "was low in the western sky and was reported to have hit the ground behind a tree-covered hill."

The search. State police and military personnel searched the woods. The next day's Greensburg Tribune-Review ran two versions of the story. Its county edition was headlined "Unidentified Flying Object Falls Near Kecksburg" and "Army Ropes Off Area"; its city edition, "Searchers Fail To Find Object". Nickell and McGaha, who quote both, report that the Air Force and the state police said nothing had been found. The sceptic Brian Dunning adds that the Air Force searchers carried Geiger counters.

The astronomy. In February 1966 Sky and Telescope identified the fireball as a very bright meteor, a bolide. The same report quoted the geophysicist George Wetherill: "Almost everyone who saw the fireball thought it was much closer than it really was." In 1967 Von Del Chamberlain and D. J. Krause published an analysis in the Journal of the Royal Astronomical Society of Canada. According to Robert Sheaffer's summary, they used photographs of the trail taken from two places, calculated the meteor's orbit before it entered the atmosphere, and placed the end of its flight over land about 15 miles (24 kilometres) south-east of Windsor, Ontario. NASA's catalogue says the photographs and sightings indicate a path "probably too steep to be consistent with a spacecraft re-entering from Earth orbit", more likely that of "a meteor in a prograde orbit from the vicinity of the asteroid belt", which "probably ended its flight over western Lake Erie." Either end point lies more than 300 kilometres north-west of Kecksburg, by the registry's calculation.

Cosmos 96. Cosmos 96 was a Soviet spacecraft, intended as a Venus lander, launched on 23 November 1965. It failed to leave Earth orbit, stayed up for 16 days and re-entered on 9 December 1965, the day of the fireball. NASA's catalogue states that US Air Force tracking data "indicate the spacecraft orbit decayed earlier than 21:43 UT on 9 December", and that other analyses of the orbit "definitively indicate it could not have been the Cosmos 96 spacecraft." Oberg, who says he once wondered whether the Air Force's claim was a diversion, wrote in 2008 that the probe's path "could not possibly be made to coincide with the path of the meteor".

The acorn. Nearly 25 years later, two local men described finding a large metallic object shaped like an acorn, partly embedded in the earth and marked with something like Egyptian hieroglyphics, which they said the military took away (Nickell and McGaha). NBC's Unsolved Mysteries broadcast the story in September 1990. More than fifty residents of Kecksburg sent a petition objecting to the broadcast. A replica of the object, made for a documentary, now stands at the village fire station.

NASA and the lawsuit. In 2003 a lawsuit was filed to force NASA to release documents about the incident. In 2005, commenting on the suit, a NASA spokesperson told the Associated Press that a Russian satellite had been found at the site, according to the Pennsylvania Center for the Book. The registry has not seen the Associated Press report. The remark as reported names no satellite; NASA's catalogue excludes Cosmos 96, the Soviet probe that re-entered that day. In January 2008 Oberg said NASA was unlikely to hold any such documents and called the suit "almost certainly a publicity stunt".

Leading explanations

A meteor. Established for the fireball. Sky and Telescope identified it as a bolide in February 1966. Chamberlain and Krause triangulated it from photographs and computed its orbit before it met the atmosphere. NASA's catalogue describes a path too steep for a re-entering spacecraft, ending near the western end of Lake Erie.

Misjudged distance (the explanation offered by Wetherill and Oberg for the Kecksburg reports; consistent with the trajectory, but general rather than a test of each account). Oberg notes that from Kecksburg the meteor was low in the western sky. Wetherill's observation that witnesses judged it far closer than it was is the caution NASA's catalogue also makes.

The Soviet probe Cosmos 96. Rejected. The Air Force tracking data put its re-entry before the fireball, and NASA's catalogue says later orbital analyses definitively exclude it.

A recovered craft or other artificial object (the later witness accounts; unsupported by any 1965 record). The acorn, the markings and the military removal appear in accounts first given nearly 25 years after the event. No 1965 document describes an object being found, and the reports of the day say the opposite.

What the popular version gets wrong

"The military recovered an acorn-shaped craft from the woods." The 1965 reports say the search found nothing, and the Air Force and state police said so the next day. The acorn first appears in accounts given nearly a quarter of a century later. The acorn on display in Kecksburg was made for television.

"NASA identified the object as the Soviet probe Cosmos 96." NASA's own spacecraft catalogue says the opposite: the fireball's path was too steep for a re-entering spacecraft, the probe came down earlier, and orbital analyses "definitively" rule it out. A spokesperson's reported 2005 remark to a news agency named no satellite, and it is not the agency's published finding.

"The fireball crashed at Kecksburg." Photographs taken from two places put the end of its flight near Windsor or over western Lake Erie, more than 300 kilometres away. Seen from Kecksburg it was low in the western sky and was reported to have come down behind a tree-covered hill.

"The Army sealed off the area, so something was there." The county edition that reported the Army roping off the area was followed by a city edition headlined "Searchers Fail To Find Object". A cordon records a search. It does not record a find.

Current status

Partially explained. The fireball is settled: a meteor, photographed from two places, with a computed orbit and an end point near Windsor, far from Kecksburg. Cosmos 96 is excluded. What is not settled is the ground at Kecksburg. The 1965 record of the search is a handful of newspaper reports; no military log of it has been published; the claims of a recovered object date from nearly 25 years later; and a NASA spokesperson's reported 2005 remark that a Russian satellite was found there sits beside a NASA catalogue entry that rules out Cosmos 96.

The registry does not treat the later accounts as evidence of a recovery, and does not call the witnesses liars. It records that the one documented search found nothing. Contemporaneous Air Force or Army records of the 9 December search, or the documents sought in the 2003 lawsuit, would change this entry.

Sources

  • NASA Space Science Data Coordinated Archive. "Cosmos 96" (1965-094A), including "The Great Lakes Fireball and Kecksburg Incident". nssdc.gsfc.nasa.gov, page version 5.2.0, 8 September 2026.
  • Nickell, J., and McGaha, J. (2012). "The Roswellian Syndrome: How Some UFO Myths Develop." Skeptical Inquirer 36(3), May/June 2012. Quotes both editions of the Greensburg Tribune-Review of the day after the fireball and the February 1966 Sky and Telescope identification.
  • Greensburg Tribune-Review, county and city editions of the day after the fireball. Known to the registry through Nickell and McGaha (2012).
  • Sky and Telescope, February 1966, p. 78. Report identifying the fireball as a bolide, quoting G. W. Wetherill. Known to the registry through Nickell and McGaha (2012) and Sheaffer.
  • Chamberlain, V. D., and Krause, D. J. (1967). "The Fireball of December 9, 1965." Journal of the Royal Astronomical Society of Canada 61(4), 184 to 190. Known to the registry through Sheaffer's summary and Dunning's reference list.
  • Sheaffer, R. Kecksburg page. The Debunker's Domain, debunker.com. Undated.
  • Oberg, J. (2008). Statement on the NASA lawsuit over Kecksburg documents, 7 January 2008. jamesoberg.com.
  • Dunning, B. (2019). "Alien Visitation and Kecksburg." Skeptoid podcast, episode 681, 25 June 2019.
  • Pennsylvania Center for the Book (2010). "Acorn from Space: The Kecksburg Incident." Penn State University Libraries, Fall 2010.

Last reviewed: September 2026. Records are provisional. Where the evidence changes, the entry changes. Found an error? Tell us.

Advertise on Anomaly Registry

A documentary archive of 175 investigated cases, read slowly and at length by an audience that arrives on purpose. Below are the current delivery figures and what is available to buy.

Figures are rolling daily averages, current as of September 2026. They are restated as the traffic changes rather than left to age quietly, and we are happy to screen-share the underlying Ad Manager and analytics reporting before an insertion order is signed.

Anomaly Registry is a reference archive rather than a feed. Every one of its 175 records is written to a fixed structure, sourced to contemporaneous documents, inquest files, peer-reviewed literature or credible reporting, and each carries a section setting out precisely what the popular version of the story gets wrong. Cases that were later explained and cases that were comprehensively debunked are kept alongside the unsolved ones, because an archive that keeps only its mysteries is not an archive. That editorial position is the reason people stay.

It also explains the shape of the traffic. A session here runs to more than four pages and close to nine minutes, which is several times what a typical content site sees. Readers arrive looking for one case, find the sources laid out, and follow the cross-references into the next record. For an advertiser, the practical consequence is that a banner on this site is in front of a settled, attentive reader for minutes rather than seconds, and it is seen repeatedly across a single visit without ever being the reason someone leaves.

Three placements are available on every page. The leaderboard sits above the masthead and accepts 728x90, 970x90 and 320x50. The in-article unit sits inside the body of the record, where the reader is already stopped, and accepts 728x90, 300x250 and 336x280. The footer unit closes the page and accepts 728x90, 970x90 and 320x50. There are three slots per page and there will not be a fourth: the inventory is deliberately limited so that each impression is worth more than it would be on a page carrying eight.

What we do not run matters as much as what we do. There are no interstitials, no pop-ups, no auto-playing video, no content-recommendation chumboxes, and nothing that reflows the page after the reader has started reading. Ads are served in reserved space so the layout does not jump. This protects viewability for the advertiser as directly as it protects the reading experience, and it is the reason we can quote the session figures above with a straight face.

The editorial environment is unusually safe for a subject area that is often anything but. This site does not publish conspiracy content, it does not promote pseudoscience, and it does not treat a rumour as a finding. Its entire method is to separate what is documented from what has merely been proposed, and to say plainly when a famous mystery has an unglamorous answer. A brand placed here sits next to sourced, corrected, carefully hedged writing rather than next to speculation dressed as news.

The readership is a general-interest one with a research habit: people who read long-form nonfiction, follow science and history coverage, and check citations. In practice the categories that fit well are books and publishing, documentary and streaming, museums and exhibitions, education and online courses, audio and podcasts, consumer technology, outdoor and travel, and financial services. If your product rewards attention and explanation rather than impulse, this is a good room to be in.

Everything is delivered through Google Ad Manager, so you can buy the way you already buy. Direct-sold campaigns can be trafficked as a guaranteed line item with standard reporting on impressions, viewability and click-through. Programmatic demand can reach the same inventory through the open auction or through a preferred deal or private marketplace at a floor we agree in advance. We accept standard IAB display creative and HTML5, and we can accommodate a reasonable third-party ad server or verification tag.

Category sponsorship is available for advertisers who want something more durable than a rotation. The register is organised into seven categories, and a sponsor can take the whole of one, appearing across every record inside it with an acknowledgement in the page furniture. Sponsorship never buys editorial influence: a sponsor cannot commission a record, cannot review one before publication, cannot have a record altered, and cannot have one removed. That rule is not negotiable and it is the thing that keeps the inventory worth buying.

Some categories are declined outright, and it is fairer to say so up front than to discover it after an insertion order. We do not accept adult content, gambling, payday or high-cost short-term credit, cryptocurrency speculation and token sales, dietary supplements making health claims, political advocacy, psychic or clairvoyant services, or anything that reads as a scare advertisement dressed up as an article. Nothing may be styled to look like a record or like part of the editorial page.

Rates depend on placement, volume, whether the buy is run-of-site or targeted to a category, and how long it runs. There is no rate card on this page because a sensible number depends on what you are trying to do, and quoting one in the abstract usually wastes both parties' time. Tell us the campaign, the flight dates and the budget you are working to, and you will get a straight answer including whether we think the fit is wrong.

To start, write to or use the contact form and mark the message for the advertising desk. Include the flight dates, the placements you want, the creative sizes you have ready and any verification requirements, and we will come back with availability and a quote. Media buyers who want the underlying analytics before committing are welcome to ask; we would rather show the reporting than be taken on trust.

Privacy Policy

This policy explains what information Anomaly Registry collects when you visit this website, why it is collected, how it is used, and what choices you have. It applies to anomalyregistry.com and to any subdomain operated by us. It was last updated on the date shown at the end of this policy, and we will revise it if our practices change.

We have designed this site to collect as little personal information as possible. You do not need an account to read anything here. There is no login, no user profile, and no comment system. In the ordinary course of reading the register, you are not asked to identify yourself, and we do not ask you to.

Like virtually every web server, ours produces access logs. These logs record the internet protocol address of the requesting device, the date and time of the request, the page or file requested, the referring page if one was sent, and the browser user agent string. These logs exist for security, abuse prevention, and diagnosing technical faults. They are retained for a limited period and then discarded. We do not use them to build profiles of individual readers.

If you write to us through the contact form, we receive whatever you choose to put into it: typically a name, an email address, and a message. We use that information for the sole purpose of reading and answering your message. Writing to us does not add you to any list, and we do not sell, rent, or trade contact details with anyone.

There is one optional mailing list, and you only join it by asking. If you submit the subscribe form we store the address you gave, the time you submitted it, the IP address it came from, and the exact wording of the consent you agreed to. We keep that record because Canadian anti-spam law expects us to be able to show when and how you asked to hear from us. The list is used to say that records have been published or materially revised, and for nothing else. Every message carries a way to leave, and asking to be removed by email works just as well.

Corrections are a special case, and worth stating plainly. If you write to point out an error in a record, we may act on that correction and revise the entry. We will not publish your name or your email address in connection with a correction unless you explicitly ask us to be credited.

This site is supported by advertising served through Google Ad Manager. Advertising technology providers may set and read cookies or similar identifiers on your device in order to select advertisements, limit how often you see the same advertisement, and measure performance. These identifiers are set by those third parties, not by us, and the data they collect is governed by their own privacy policies rather than this one.

We do not have access to the personal data that advertising partners collect, and we cannot delete it on your behalf. If you wish to limit interest-based advertising, you can adjust the advertising settings offered by Google, use your browser's cookie controls, or use the industry opt-out tools that are available in your region. Details are set out in our Cookie Policy.

We may use privacy-respecting aggregate analytics to understand which records are being read and how people move through the register. Where we do, we configure it to avoid collecting information that identifies individual readers. Aggregate figures tell us that a case page is popular; they do not tell us who read it.

We do not knowingly collect personal information from children. This site is a documentary archive intended for a general adult and older student readership. If you believe a child has sent us personal information through the contact form, write to us and we will delete it.

Depending on where you live, you may have rights over personal data relating to you, including the right to ask what we hold, to ask for a copy, to ask for correction, and to ask for deletion. Because we hold so little, these requests are usually simple to answer. Write to us and we will respond within the period required by the law that applies to you.

Our servers are located in North America, and information sent to this site is processed there. If you are visiting from elsewhere, your request necessarily crosses borders in order to reach us. By using the site you understand that this transfer takes place.

If we change this policy, the revised version will be posted here with a new date. Material changes will be noted plainly rather than buried. Questions about this policy should be sent through the contact page.

Cookie Policy

A cookie is a small text file that a website asks your browser to store, and that your browser sends back on later requests. Similar technologies, including local storage and pixel tags, do comparable work. This policy explains which of these are used on Anomaly Registry, by whom, and what you can do about them.

The registry itself is a reading site. It does not require a cookie to show you a record. We do not set cookies to track you across the internet, and we do not operate a first-party advertising identifier of our own.

Strictly necessary cookies may be set to keep the site secure and functioning, for example to help mitigate automated abuse of the contact form. These are limited in scope and are not used for advertising or profiling.

Advertising cookies are set by Google Ad Manager and by the advertising technology partners that operate within it. Their purposes include selecting which advertisement to show, capping the number of times a given advertisement is repeated, detecting invalid traffic and click fraud, and measuring whether an advertisement was actually seen.

Some of these advertising cookies support interest-based advertising, in which the advertisement you see is influenced by inferences drawn from browsing activity over time and across sites. Whether this occurs depends on your region, your settings, and the choices you have already made with those providers.

We may use aggregate analytics to count page views and understand which records are read. Where an analytics tool is used, we prefer configurations that do not identify individual readers and that do not follow readers across other websites.

We do not embed social media widgets, share buttons, or tracking pixels from social networks. This is a deliberate choice for an archive of this kind, and it removes an entire category of third-party tracking that most content sites carry.

Your browser gives you direct control over cookies. Every major browser can block third-party cookies, delete existing cookies, and clear stored data on exit. Blocking third-party cookies will not prevent you from reading anything on this site, though it may make the advertising you see less relevant.

You can also manage advertising preferences with Google directly through its advertising settings, and through the industry opt-out mechanisms operated in various regions. Because these are operated by third parties, we cannot make the choice on your behalf.

Where the law in your region requires consent before non-essential cookies are set, a consent notice will be shown and your choice will be respected. Withdrawing consent later is possible through the same mechanism.

Advertising partners may change over time. Rather than publish a list that goes stale, we identify the advertising system in use, which is Google Ad Manager, and direct you to Google's own disclosures for the current set of partners operating within it.

If you have a question about cookies on this site that this policy does not answer, write to us through the contact page and we will answer it.

Anomaly Registry is an independent documentary archive. It is published as a work of reference and public interest reporting, and it is supported by advertising. It is not affiliated with, endorsed by, or acting on behalf of any government, university, police service, coroner, scientific institution, or investigative body named in any record.

The register documents real events, including in some cases deaths, criminal investigations, and inquests. Where a record concerns a criminal matter, nothing on this site should be read as an allegation of guilt against any living person. Where an individual has been named in the public record, we report the fact of that naming and its evidentiary standing; we do not accuse.

Records are written from sources. Where a source is a primary document, we say so. Where a claim rests on secondary reporting, we say so. Where sources conflict, we state the conflict rather than quietly choosing a side. Where a widely repeated claim cannot be traced to any source, we say that too, because an untraceable claim is itself a finding.

Every record separates what is documented from what has been proposed. Hypotheses are labelled as hypotheses and attributed to whoever advanced them, together with their standing: peer-reviewed, contested, dismissed, or untested. We do not advance theories of our own.

The registry treats its own entries as provisional. Records carry a review date, and they are revised when the evidence changes. A record you read today may be corrected tomorrow, and that is a feature of the method rather than a defect in it.

Despite this method, errors will occur. If you find one, write to us. Corrections supported by evidence are made promptly, and we would rather be corrected than be consistent.

Scientific and forensic conclusions reported here are the conclusions of the researchers and officials who reached them, not ours. Reporting that a study proposed a mechanism is not an endorsement that the mechanism is correct, and the status assigned to a case reflects the state of the evidence rather than our opinion of it.

Nothing on this site is legal, medical, psychological, financial, or safety advice. Records that touch on medical or psychological matters, including mass psychogenic illness, report the diagnoses reached by clinicians at the time and afterward. They are not a substitute for professional care.

Quotations from sources are used sparingly and for the purposes of reporting, comment, criticism, and review. Copyright in quoted material remains with its owner. If you hold rights in material you believe has been used improperly, contact us and we will address it.

Original text, structure, record numbering, and editorial apparatus on this site are the property of Anomaly Registry. You are welcome to quote briefly and link to us. Wholesale reproduction of records, including reproduction for the purpose of training generative models, is not permitted without written permission.

Outbound links are provided as references. We do not control linked sites and are not responsible for their content, their accuracy, or their handling of your data.

This site is operated from British Columbia, Canada, and these notices are governed by the laws applicable there, without regard to conflict-of-law principles.

Accessibility Statement

Anomaly Registry is built to be usable by as many people as possible, including people who use screen readers, keyboard navigation, magnification, or other assistive technology. We treat accessibility as part of the build rather than as a later remediation.

We aim to meet the Web Content Accessibility Guidelines version 2.1 at level AA. This is a target we work toward continuously rather than a certification we claim to have completed.

The site is written as semantic HTML. Headings describe the real structure of a record, lists are marked up as lists, and the register is a genuine table with proper header cells, so that a screen reader can announce which column a value belongs to.

Every interactive element is reachable and operable by keyboard alone. Focus is visible at all times, and a skip link at the top of each page lets keyboard and screen reader users jump straight to the register without traversing the navigation.

Status is never conveyed by colour alone. Each status carries its written label in text, so a reader who does not perceive the colour difference between "Unsolved" and "Debunked" still receives the distinction.

Text colours have been chosen to meet or exceed the contrast ratios required at level AA against the page background. The typefaces are set at a comfortable reading size with generous line height, and the layout reflows to a single column on small screens without loss of content or function.

The site contains one animated element, an annotation on the home page. It respects the reduced-motion preference set in your operating system, and when that preference is on, the annotation appears without movement.

Text can be resized up to two hundred percent in the browser without breaking the layout or clipping content. Nothing on this site depends on a specific screen orientation.

Advertising is served by a third party. We control where advertisements are placed and label them as advertisements, but we do not control their internal markup, and their accessibility is ultimately determined by the advertiser.

We are developing an audio version of each record. When it is published, it will be an alternative way to receive the same content, not a replacement for the written entry, and the written entry will remain the authoritative version.

Accessibility work is never finished, and parts of this site will fall short of the standard we have set. If you encounter a barrier, we want to know about it. Please tell us what page you were on, what you were trying to do, and what assistive technology you were using.

Write to us through the contact page. We aim to respond within five business days and to fix genuine barriers promptly.

Terms of Use

These terms govern your use of anomalyregistry.com. By using the site you accept them. If you do not accept them, please do not use the site.

Anomaly Registry is offered as a free documentary reference. There is no account, no subscription, and no paywall, and nothing here is offered as a professional service of any kind.

You may read, quote briefly with attribution, link to, and print records for personal, educational, and research use. This is an archive, and it is meant to be used.

You may not reproduce records wholesale, republish the register or substantial parts of it, or scrape the site systematically. In particular, you may not reproduce this content for the purpose of training generative models. Permission for other uses can be requested through the contact page and is often granted.

Original text, the record numbering system, the status taxonomy, the editorial apparatus, and the design of this site are the property of Anomaly Registry. Third-party material quoted or referenced remains the property of its owners.

We work hard to make records accurate, and we correct them when they are not. Even so, the site is provided as it is, without warranty of any kind, express or implied, including any warranty of accuracy, completeness, or fitness for a particular purpose.

Records are provisional by design. A status can change, an identification can be confirmed or overturned, and a leading explanation can be displaced by a better one. Do not treat any record as a final word, and check the review date.

To the fullest extent permitted by law, Anomaly Registry and its operator are not liable for any loss or damage arising from your use of, or reliance on, anything published here.

If you send us a correction, a source, or a suggestion, you grant us permission to use it in the register. You will not be identified in connection with it unless you ask to be credited.

Do not use the contact form to send abuse, threats, spam, or automated submissions. We may block access to anyone who misuses the site or attempts to interfere with its operation.

Outbound links are provided as references and are not endorsements. We are not responsible for the content or conduct of any site we link to.

We may revise these terms. The version published here is the version in force. These terms are governed by the laws of British Columbia, Canada, and any dispute will be heard in the courts of that province.