NASA-UAP-D017, Preliminary Gemini 4 Crew Debriefing, Part II, 1965

59
⬇ Download HD (31.0 MB)
SHARE Reddit X Facebook HN Email
Agency
NASA
Category
nasa
Type
PDF
Event Date
6/9/65
Released
2026-06-12
Size
31.0 MB
Original Filename
NASA-UAP-D017_Preliminary-Gemini-4-Crew-Debriefing_Part2_1965.pdf
Location
North Atlantic Ocean

This document is a preliminary transcript (Part II) derived from voice recordings of the Gemini 4 flight crew debriefing taken aboard the recovery ship, USS Wasp, on June 9, 1965. Part II of this document contains the “Visual Sightings” section of the debriefing (pages 196-224), where astronauts James McDivitt and Edward White describe their observations while aboard the spacecraft.

The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.

Text of the document

Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 995 words from pages 1, 3, 5, 7, 8, 9, 10 of 290.

PAGE 1

By authority of-E---'-:---'--'-=--::....-~-=-__,___.c.....:::=---1 Cha nged bY--..£:::%:.:~~!l"~~==-- GT-4 FLIGHT CREW DEBRIEFING TRANSCRIPT PART II Prepared By Spacecraft Operations Branch Flight Crew Support Division This material contains information affecting the national defense of the United States within the meaning of the Espionage Laws, Title 18. U. S. c. Section 793 and 794, the transmission or revela­ tion of which in any manner to an unauthorized person is prohibited by law. I Group 4: Downgrade at 3 year intervals Declassified after 12 years NOTICE: This document may be exempt from public disclosure under the Freedom of Infor­ lease to persons outside the U.S. Government should be handled under the provisions of

PAGE 3

This preliminary transcript was made from voice tape -recording3 of the GT-4 flight crew debriefing conducted aboard the recovery ship, the USS Wasp, on June~' 1965, and concluded at the Manned Spacecraft Center on June 12, 1965. Although all the material contained in this transcript has been edited, the urgent need for the preliminary transcript by mission analysis personnel precluded a thorough editorial review prior to its publication. Errors in this transcript will be corrected as soon as possible and an official transcript will be published at a later date. Thia document contains a transcript of the second part of the total debriefing. A preliminary transcript of the first part was published on June 16, 1965, and it contains the crew' s description of the mission from an operational standpoint.

PAGE 5

TABLE OF CONTENTS Paragraph Page number 8.0 SYSTEMS OPERATION 8.4 Environmental Control System •••·················••••···22 9.0 OPERATIONAL CHEDKS 9.2 Apollo Yaw Orientation •••·•··•·•••·•··••·•••···•·•·•••168 9.3 One Attitude Thruster Failure Check ...................171 9.8 Relative Humidity Test ................................185 9.9 Zodiacal Light Check ..................................186 10.0 VISUAL SIGHTINGS 11.2 Synoptic Terrain and Weather Photography (S-5 and S-6).219 11.3 Simple Navigation with the Sextant ....................219 11.5 Proton-Electron Spectrometer and Tri-Axis Flus-Ga.te

PAGE 7

8.0 SYSTEMS OPERATION McDivitt Actually, the first portion of any alinement is to cage the thing. The case of caging the thing is much more important than the alinement itself. In the daytime I felt that I could cage the plat­ form to a reference with an error plus or minus about 3 or 4 degrees in all axes. Did you think we could do that wel l? White Only in the daytime. McDivitt The yaw was a little problem. It took longer to get it, but if you kept after it for awhile, I felt that you could get down to just a few White Within a couple of degrees. McDivitt The big thing is that you have to stop your yaw rates, and then sit there and look outside for awhile and see which way you're going, straight ahead or sideways. If you are going sideways you rotate around for awhile and stop the rate and then look out again. Ri ght? I felt you could get the thing caged quite well. We. didn't do it BEF at all, did we? We never did cage in BEF.

PAGE 8

McDivitt The caging of the thing with small-end-forward in the daytime was relatively easy. At night I don't think it would be quite that simple. I think what you would have to do at night time is to point the spacecraft down at the ground pretty much so you can see the track across the ground, I could see which way the land was moving under me . I felt--although I never did this--that if I could do that and then roll around to where I had no bank angle, and face in my yaw direction, either small-end or blunt-end-forward, stop the roll there and pitch up to the horizon I could cage there within plus or minus 10 degrees for sure. It was much less accurate at night, I felt, than in the White You aren' t kidding! We both felt that on those dark nights when you really couldn 't see anything on the ground, pure star reference for yaw was pretty rough. McDivitt Pure star reference for yaw was almost impossible to use. That was the only place where that thing we decided not to take with us--the view of the stars through the window--might have been of some

PAGE 9

use to us. We knew the stars along our track but you couldn't see enough of them. The quickest way to get the yaw reference was to look down at the ground. Once we got the platform caged, aline­ ment was quite simple. All you had to do was just hold the needles at zero and the platform alined itself. Of course you had to have the scanners on, The modes--the SEF and the EEF were identically the same except the spacecraft is pointing in different directions . You tended to null the needles by using pulses and just hold the needles very close to null and the platform alined itself through the horizon scanners. Orbit Rate was a satisfactory mode, I thought. As a matter of fact, it was very good. White I liked that Orbit Rate, McDivitt Yes, because we finally had a reference where we didn't have to look out and see the ground. It's like having the old altitude indicator back in an airplane. The only thing was, we had the wrong orbit rate in the spacecraft because it was set for an orbit rate that was to take care of, I think, a 60 nautical mile circular orbit. This was to take care of the short period of time between

PAGE 10

going to Orbit Rate at T-5 and firing the retros at TR. We wanted to have exactly the right rate in there so when we did our closed-loop reentry we wouldn' t have an error. As I said, I had the most accurate platform in the world with nothing to do with it. I think the displays were adequate and the controls were adequate. After the first couple of revs I really didn' t have any confidence at all in the platform. I had done nothing to

Where this file fits in the PURSUE archive

This file is one of NASA's 40 files in the Trump PURSUE disclosure. Within the NASA agency block it ranks #34 of 40 by Anomalousness Index. Across the entire 450-file archive it ranks #187 of 450.

That places it in the lower-scoring band of the archive (187 of 450 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.

For the broader cluster context, this file is part of Gemini 4 UFO - the three classified Gemini 4 debriefings (D016/D017/D018) documenting McDivitt's 1965 encounter with an unidentified orbiting object near Hawaii. The cluster page walks through all 3 member files with regional grouping, sensor breakdown, and standout analysis.

Anomalousness Index: 59/100

Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.

🤖 AI-ASSISTED SCORING · methodology

The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.

sensor quality (eyewitness only) 30 × 0.25 = 7.5

Reported by a witness with no instrumented record. The lowest tier in the rubric's sensor axis. Eyewitness perception in field conditions, even when the witness is highly credentialed, scores below capture by any instrumented modality. This report reached the federal record through NASA.

witness credibility (astronaut) 95 × 0.2 = 19.0

Astronaut witness on the official federal record - the highest tier in the rubric's witness-credibility axis. It applies to NASA crew debriefings, mission transcripts, and astronaut interviews across the Mercury, Gemini, and Apollo programs. Witness credibility is only one of six components; the astronaut-witness files that also rank high on the sensor and disposition axes are the eight tied for the archive's top score of 72 - the Gemini 7 Borman audio, the Gordon Cooper interview, and the Apollo 14, 16, and 17 crew debriefings.

corroboration (single witness instrument) 60 × 0.2 = 12.0

Single-witness or single-instrument capture. This is the corroboration tier for the overwhelming majority of the PURSUE archive on the released metadata - the rubric records the honest limit of the underlying record rather than inferring multi-witness corroboration that the released summaries do not establish. A small number of files with an independent second witness or instrument score on the multi-witness/multi-instrument tier above this one.

kinematic anomaly (no kinematic data) 30 × 0.15 = 4.5

No kinematic measurements - speed, acceleration, vector - are published in the released file with sufficient precision to score on the kinematic axis. The rubric does not infer kinematic anomaly from narrative observer estimates. Every file in the archive carries this value, which is itself an observation about the disclosure: kinematic-grade telemetry was not part of what was released.

mundane explanation available (weak mundane candidate) 70 × 0.1 = 7.0

A conventional candidate explanation has been considered but is not dispositive. Every file in the archive scores this way - reflecting that the underlying release metadata systematically caveats strong determinations in either direction. The released summaries warn against reading them as conclusive analytical judgments, and the rubric respects that.

official disposition (open after review) 90 × 0.1 = 9.0

Released as open after formal review by the originating agency. The file passed through a review process and was published in that posture - a stronger disposition signal than 'unresolved with no review,' because review has occurred and the open status is the agency's published conclusion.

Bottom line on the score: the Anomalousness Index of 59/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.

Related files in NASA

Other PURSUE files in the same category, ranked by Anomalousness Index.

NASA · VIDEO SCORE 72

NASA-UAP-D003A, Gemini 7 Audio Excerpt, 1965

NASA · VIDEO SCORE 72

NASA-UAP-D023, Interview Excerpt with Astronaut Gordon Cooper, 1962

NASA · IMAGE SCORE 65

NASA-UAP-D030, STS-80 Unidentified Object Image 1, 1996

NASA · IMAGE SCORE 65

NASA-UAP-D031, STS-80 Unidentified Object Image 2, 1996

NASA · IMAGE SCORE 65

NASA-UAP-D032, STS-80 Unidentified Object Image 3, 1996

NASA · PDF SCORE 59

NASA-UAP-D003, Gemini 7 Transcript, 1965

BROWSE ALL 450 FILES →

Verification

SHA-256:

2be20f887d364078d11c7340380c21800348ac84beb5722c5932ef0be3e57c57

This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →

Source: https://www.war.gov/medialink/ufo/061226/release_03/documents/NASA-UAP-D017_Preliminary-Gemini-4-Crew-Debriefing_Part2_1965.pdf

📡 Subscribe via RSS 🔔 Watch on GitHub