The Exeter, New Hampshire Project Blue Book file preserves the official Air Force record family for the September 2-3, 1965 police-witness case involving Norman J. Muscarello, Exeter patrolmen Eugene F. Bertrand Jr. and David R. Hunt, Pease Air Force Base, and Project Blue Book's unidentified classification.1234
File Provenance
The National Archives identifies Project Blue Book as the declassified U.S. Air Force UFO investigation record set, with chronological case files and administrative records transferred for public research after the program closed in 1969.1
NARA's current UAP textual-and-microfilm guide places the sanitized Project Blue Book case files in Record Group 341 and identifies the series as National Archives Identifier 597821, while also listing related Blue Book administrative, OSI, artifact, and Air Force command records.5
The T1206 microfilm guide describes Blue Book access through 94 rolls of 35mm microfilm and places the September 3, 1965 Exeter case inside the late-summer 1965 chronological range rather than as an isolated special release.6
The circulated Exeter scan is a 131-page Project Blue Book packet titled 1965-09-9373271-Exeter-NewHampshire; Internet Archive identifies the author as the U.S. Air Force, while Wikimedia Commons identifies Project Blue Book as the author and traces the file source to Internet Archive Blue Book collections.23
UFOScans indexes the same file as a Project 10073 record for Exeter, New Hampshire, classifies the official assessment as unidentified, and summarizes the source file as a Foreign Technology Division, Air Force Systems Command initial report and supporting record packet.4
NICAP preserves a separate document index for resized Blue Book frames from the Exeter file, including statements by Bertrand, Hunt, and Muscarello, Raymond E. Fowler data sheets, press clippings, correspondence, and Air Force evaluation material.7
Witness Origin
The story originated in the file as a small local sequence rather than a single anonymous rumor: Bertrand's statement begins with a distressed female motorist on Route 108 near Exeter, Muscarello's statement begins with five bright red lights over Route 150 about three miles southwest of Exeter, and the police statements then converge when Bertrand returned to the field with Muscarello.37
Muscarello's signed statement says he was hitchhiking on Route 150 at about 2:00 a.m. on September 3, saw five bright red lights in a line at roughly a 60-degree angle, watched them move over a field, and later reported the episode to the Exeter Police Department.37
Bertrand's statement says he first found the upset motorist before returning to the station, then accompanied Muscarello back to the reported site, where he saw five bright red lights emerge from behind trees, move over the field, produce no sound or vibration, and alarm nearby farm animals.37
Hunt's statement says Bertrand called him to the area at about 2:55 a.m., after which Hunt observed bright red lights flashing in sequence over a field southeast of the witnesses before the lights moved away at an estimated altitude near 100 feet.37
The official file therefore anchors the case's origin in three named witness statements, immediate police action, and Pease Air Force Base notification, not merely in later magazine, book, or festival retellings.237
Air Force Handling
Pease Air Force Base handled the first military layer through the 817th Combat Support Group and submitted an Initial Report of Unidentified Flying Object under Air Force Regulation 200-2 to Air Force Systems Command's Foreign Technology Division.34
Major David H. Griffin, identified in the file as the Pease base disaster control officer and a command pilot, reported that investigators had not arrived at a probable cause, that the three principal observers seemed stable and reliable, and that five Pease B-47 aircraft in the area were not believed to be connected with the sighting.34
The same initial-report material records a ground-visual observation, bright red lights moving together as one object, an estimated altitude near 100 feet, erratic movement, a departure heading around 160 degrees, clear weather, a surface-to-5,000-foot temperature inversion, and no physical evidence.34
Project Blue Book's explanation track then tested military-aircraft possibilities rather than leaving the first report untouched, including 8th Air Force Operation Big Blast, refueling-area activity, B-47 crew checks, stars and planets, and the possibility of aircraft or night-photography activity in the region.34
The surviving file shows why the closure stayed unresolved: Blue Book correspondence considered conventional aircraft and exercise explanations plausible in principle, but later summaries noted that no aircraft was placed at the key observation time and the case remained listed as unidentified.34
Dispute and Public Evolution
The case evolved publicly because the official explanation process became part of the controversy. In December 1965, Bertrand and Hunt wrote to Major Hector Quintanilla Jr., Chief of Project Blue Book, objecting that public references to military high-altitude objects, weather inversion, and Operation Big Blast did not fit their close, low, silent observation.37
Their letter emphasized Bertrand's Air Force refueling experience, the officers' police-report obligation, the low-altitude character of the sighting, the lack of sound, and the timing gap between the officers' observation and the cited exercise window.37
The Exeter file also accumulated media and civilian-research layers. NICAP-associated Raymond E. Fowler material appears in the Blue Book document trail, and the NICAP index lists Saturday Review, Haverhill Gazette, Saucer News, Flying Saucer Review, and other public-response materials among the related frames.37
Congressional attention followed during the April 5, 1966 House Armed Services Committee hearing on unidentified flying objects, where Project Blue Book, Major Quintanilla, Dr. J. Allen Hynek, Air Force Secretary Harold Brown, and disputed public cases formed the oversight setting into which Exeter had moved.8
John G. Fuller's 1966 public-broadcast appearance for Incident at Exeter shows the next stage of the story's evolution, as the case shifted from police report and Air Force file into a nationally circulated narrative built around interviews, tape-recorded witness accounts, and criticism of official handling.9
Source Value and Limits
The file's value is unusually high because it preserves named police witnesses, signed witness statements, immediate local response, Pease Air Force Base reporting, Project Blue Book correspondence, explanation testing, civilian-research friction, and the administrative unidentified outcome in one auditable packet.2347
The file's limits are just as important: it preserves testimony, questionnaires, correspondence, summaries, and clippings, but not photographs, radar tracks, physical traces, recovered material, or a specific conventional aircraft tied to the principal observation.347
For this archive, the Exeter file matters because it shows how a frightened teenage witness and two police officers produced a durable official record, how the Air Force tried to fit the report against known aircraft and exercises, and how unresolved paperwork became a long-running public dispute rather than a clean answer.13489