Within Blue Book
Why Was Kecksburg Called a Meteor So Early?
The surviving memo shows the Air Force recommending a meteor explanation for the press while Kecksburg enquiries were still continuing.
On this page
- The Pentagon request for a press ready answer
- What the memo says about the unfinished inquiry
- Public messaging versus final evidential judgment
Page outline Jump by section
Introduction
One of the most frequently cited inconsistencies in the surviving Project Blue Book record on the Kecksburg incident is that the Air Force endorsed a meteor explanation before its own documented enquiries had concluded. Rather than proving a cover-up on its own, the surviving memorandum reveals a more nuanced situation: a Pentagon official requested a press-ready explanation, Blue Book director Major Hector Quintanilla authorised describing the object as a meteor, yet the same memorandum explicitly states that the investigation was still under way. This apparent contradiction has become an important point in assessing how Project Blue Book balanced public communication with an investigation that had not formally reached its end.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
The Pentagon request for a press-ready answer
The key surviving document is a “Memo for the Record” dated 10 December 1965, one day after the Kecksburg event. It records a telephone call from a Pentagon officer, Major Howard, who wanted information that could be released publicly concerning the widely reported fireball over Pennsylvania.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
According to the memorandum, Quintanilla summarised what Blue Book knew at that stage:
- personnel from the Oakdale Radar Site had searched with Pennsylvania authorities until about 2 a.m.;
- the search had been unsuccessful;
- the object had not been tracked by radar;
- witnesses had reported the phenomenon across several states;
- there was no known space debris entering the atmosphere on 9 December 1965.
Only after outlining those preliminary findings did Quintanilla state that it was acceptable to describe the object publicly as “a meteor” or “a bolide” (a particularly bright meteor that may produce audible effects).[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
The sequence matters. The recommendation appears in response to a request for a public statement rather than as the final conclusion of a completed investigation.
What the memo says about the unfinished inquiry
The document contains a sentence that is often overlooked in discussions of Kecksburg:
“…it was OK to call it a meteor… He said that investigation is still under way.”[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
This wording creates the central tension.
If the investigation were already complete, there would be no reason to note that enquiries continued. Conversely, if investigators genuinely considered the matter unresolved, describing the object publicly as a meteor could be seen as premature.
The memorandum therefore reflects two simultaneous positions:
- Operationally, Blue Book acknowledged that enquiries had not yet finished.
- Publicly, it considered the meteor explanation sufficiently plausible to release immediately.
Importantly, the document does not explain why the investigation remained open after this advice was given. It neither records additional discoveries nor states that investigators expected significant new evidence.
Why Blue Book may have made an early meteor call
The surviving record does not explicitly justify Quintanilla’s decision, but several factors evident from the memo and Blue Book’s broader operating practices help explain why an early meteor explanation may have been considered appropriate.
A provisional explanation was better than saying nothing
The Pentagon had requested information suitable for release to the press while public interest was already high. Government agencies commonly issue preliminary assessments before every detail has been verified, provided they are clearly subject to revision.
The memo reads much more like preparation for a media response than a final investigative report.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
The observations broadly matched a meteor event
The reports available to Blue Book described a bright object observed over a very large geographical area, extending across multiple states. Such widespread visibility is characteristic of exceptionally bright fireballs rather than local aircraft incidents.
The memo also notes that the object was not detected by radar, reducing support for the idea that investigators were dealing with a conventional aircraft target.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
No confirmed alternative had emerged
The memorandum specifically states that there was no known space debris entering the atmosphere on 9 December 1965. Whatever later theories developed about satellites or other objects, Blue Book’s documented information at the time apparently excluded a confirmed re-entering spacecraft from its working assessment.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
This left a meteor as the most straightforward explanation available from the information then in hand.
Public messaging versus final evidential judgment
The memo illustrates an important distinction that is sometimes blurred in later discussions.
A recommendation for public communication is not necessarily identical to a completed evidential finding.
The surviving document shows Blue Book addressing two different tasks simultaneously:
- informing another military office what could responsibly be said publicly;
- continuing whatever internal enquiries remained open.
That distinction weakens two opposite claims that sometimes appear in discussions of Kecksburg.
One claim is that the memo proves investigators had definitively solved the case before speaking publicly. The wording does not support this because it explicitly says the investigation continued.
The opposite claim is that the early meteor explanation demonstrates deliberate deception. The memo alone also does not establish that. It shows that Blue Book regarded a meteor explanation as acceptable before the investigation formally ended, but it does not reveal whether later enquiries changed, confirmed or simply added nothing to that provisional assessment.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
Why this memo remains significant in the Project Blue Book record gap
Within the broader question of missing or incomplete Kecksburg documentation, this memorandum is significant because it preserves a snapshot of decision-making rather than a polished final report.
It demonstrates that:
- Blue Book acknowledged an organised search had taken place.
- The search had reportedly failed to recover the reported object.
- A meteor explanation was approved for public release.
- The investigation had nevertheless not formally concluded at the time that advice was given.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
For historians, this combination is more informative than either an unequivocal explanation or an absence of records. It shows that official messaging and investigative procedure briefly ran in parallel. Whether that reflected ordinary administrative practice, confidence that later enquiries would not materially alter the explanation, or a desire to satisfy immediate press enquiries cannot be determined from the surviving memo alone. The document supports careful scrutiny of Blue Book’s handling of the case, but by itself it does not establish either a final evidential judgment or proof of concealment.[Bluebook Files]files.bluebookfiles.org1965.12 8693327 IndianaBluebook Files1965-12-8693327-IndianaFebruary 10, 2026…
Amazon book picks
Further Reading
Books and field guides related to Why Was Kecksburg Called a Meteor So Early?. Use these as the next step if you want deeper reading beyond the article.
The Report on Unidentified Flying Objects
Regardless of whether or not one believes that the study of UFO reports has any merit it is a simple fact that such reports were studied...
UFOs and Government: A Historical Inquiry
Governments around the world have had to deal with the UFO phenomenon for a good part of a century. How and why they did so is the subjec...
The UFO Experience: A Scientific Inquiry
Cited by the New York Review of Books as "the best brief for visitation," this classic study presents an analysis of UFO reports and conc...
Mirage Men: A Journey into Disinformation, Paranoia and UFOs
Seeking the truth about UFOs in America, Mark Pilkington and John Lundberg uncover a 60 year-old story stranger than any conspiracy thril...
eBay marketplace picks
Marketplace Samples
Live-tested eBay searches with available results related to this page.
Selected frommeteor fireball poster oneBay.co.uk.
Endnotes
1.
Source: files.bluebookfiles.org
Title: 1965.12 8693327 Indiana
Link:https://files.bluebookfiles.org/pdfs/1965.12%20-%208693327%20-%20Indiana.pdf
Source snippet
Bluebook Files1965-12-8693327-IndianaFebruary 10, 2026...
Published: February 10, 2026
2.
Source: enigmalabs.io
Title: Kecksburg Incident | Enigma Labs
Link:https://enigmalabs.io/library/f45bb19d-5803-4ab6-a373-8799f64095c0
Source snippet
Air Force’s investigation into unidentified flying objects, told the Associated Press late on De...
3.
Source: uapfiles.com
Link:https://uapfiles.com/analysis/rgBTMzFd-hg/people/book
Additional References
4.
Source: archives.gov
Link:https://www.archives.gov/research/topics/uaps/publications
Source snippet
ives | National ArchivesApril 24, 2025 — PUBLICATIONS ABOUT RECORDS RELATED TO UNIDENTIFIED FLYING OBJECTS (UFOS) AND UNIDENTIFIED ANOMAL...
Published: April 24, 2025
5.
Source: archives.gov
Link:https://www.archives.gov/research/topics/uaps/rg-collections
Source snippet
ecord Group or Collection | National ArchivesDecember 12, 2025 — RECORD GROUP 64: RECORDS OF THE NATIONAL ARCHIVES AND RECORDS ADMINISTRA...
Published: December 12, 2025
6.
Source: appalachianhistorian.org
Link:https://appalachianhistorian.org/the-[kecksburg-ufo-incident
Source snippet
Later accounts and official statements said searchers found nothing. That tension, between the first breathless hea...
7.
Source: uapedia.ai
Title: Contemporary scientific records describe a bolide
Link:https://www.uapedia.ai/wiki/kecksburg-uap-crash-1965/
Source snippet
Kecksburg UAP Crash (1965) - UAPediaOctober 14, 2025 — KECKSBURG UAP CRASH (1965) On the late afternoon of December 9, 1965, thousands ac...
Published: October 14, 2025
8.
Source: archives.gov
Title: National Archives Project BLUE BOOK
Link:https://www.archives.gov/research/military/air-force/ufos
Source snippet
National ArchivesProject BLUE BOOK - Unidentified Flying Objects | National Archives...
9.
Source: thecoldfile.com
Title: 1965 kecksburg
Link:https://www.thecoldfile.com/articles/1965-kecksburg/
Source snippet
The Acorn in the Woods: The 1965 Kecksburg Incident | The Cold FileMay 25, 2026 — UFO/UAP / Case file / Filed May 25, 2026 THE ACORN IN T...
Published: May 25, 2026
10.
Source: paradigmresearchgroup.org
Link:https://www.paradigmresearchgroup.org/News_Items-3.htm
11.
Source: cufon.org
Link:https://www.cufon.org/cufon/obrien.htm
12.
Source: riseupparanormal.com
Link:https://www.riseupparanormal.com/ufotop10-2.htm
13.
Source: qsl.net
Link:https://www.qsl.net/w5www/kecksburg.html