NASA-UAP-D019 — Gemini 5 Technical Debriefing, Part I, 1965
File NASA-UAP-D019 is a declassified pdf from NASA, recording an incident dated August 2 - September 2, 1965 at Cape Kennedy, Florida, published in Release 03 (2026-06-12). This page carries the original file, its official summary and its full text.
- File
- NASA-UAP-D019
- Agency
- NASA
- Incident date
- August 2 - September 2, 1965
- Location
- Cape Kennedy, Florida
- Released in
- Release 03 (2026-06-12)
- File type
Topics: Apollo & NASA crews
This document is a preliminary transcript (Part I) derived from voice recordings of the Gemini 5 flight crew technical debriefing. NASA conducted this debriefing between August 30, 1965, and September 2, 1965, at the Crew Quarters, Cape Kennedy, Florida.
Open original file · WAR.GOV page
TL;DR
Two weeks of debrief, and they still couldn't clear the fog.
- Gemini 5 Technical Debriefing Part I, NASA, Aug 30–Sep 2 1965, Cape Kennedy.
- Crew discuss window fogging, noises, vibrations, debris, unidentified objects, radar anomalies.
- No official conclusion in the file.
AI summary
A declassified Gemini 5 technical debriefing document from 1965 includes crew discussions on various mission aspects such as countdown procedures, communications, spacecraft systems, and visual observations. Astronauts Conrad and Cooper describe technical issues like window fogging, unusual noises, and vibrations, as well as system performance during flight and reentry. They mention debris seen during reentry, unidentified objects, and challenges with spacecraft control systems, radar tests, and equipment malfunctions. Some sections note possible micrometeorite impacts, temperature control issues, and unusual sounds, while others focus on reentry procedures, parachute deployment, and post-landing activities. The document includes references to unidentified objects and radar anomalies but does not confirm their nature.
Full text
Page 1
. -
,.
19
Y authtrity of E. c 1 1 G
hanged by C4?1 • 'o <<=
/
GEMINI V
TECHNICAL DEBRIEFING (U)
Part 1
NOTICE: This document may be exempt from
public disclosure under the Freedom of lnfor•
mation Act (5 U.S.C. 552). Requests for its re
lease to persons outside the U.S. Government
should be handled under the provisions of
NASA Policy Directive 1382.2.
THIS MAT E RIAL CONTAINS INF'ORM.ATION AFl"IECTING
THE NATIONAL OEFENSE OF THE
UN I TEO STATES
WITHIN THE MEANING OF' TH£ £8P'IONAGIE LAW 5 ,.
TITLE 11. U . S.C, SE CTION 793 ANO 794 . T HE TRANS
M I SSION OR REVELAT I O N Of' WH IC H IN AN Y MANNER
TO AN UNA UTH ORIZED PERSON IS PR OHIB ITE D av L AW.
GROUP 4
OOWNCiftAOEO AT ) V EA R I NTFRVALS,
OECL ASSI F'IEO AFTER 12 VE ARS
t
" 6 () t JF18Er4TI;\ b
Page 2
PRELIMINARY
GT- 5 FLIGHT CREW DEBRIEFING TRANSCRIPT
PART I
Prepared By
Spacecraft Operations Branch
Flight Crew Support Division
September 1 , 1965
This material contains informati on affecting the
national defense of the United States within the
meaning of the Espionage Laws , Ti tle 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.
Gr oup 4 :
Downgrade at 3 year intervals
Declassified after 12 years
Page 3
PREFACE
This preliminary transcript was made from voice tape recordings
of the GT-5 flight crew debriefing conducted August 30, 1965 thru
September 1, 1965 at the Crew Quarters, Cape Kennedy , Florida.
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 .
This document contains a transcript of the first part of the
debriefing, during which the crew described the mission generally
from an operational viewpoint .
A preliminary transcript of the re
mainder of the debriefing will be published by September 3, 1965.
It
will cover systems operations , operational checks, visual sightings,
experiments , pre-mission planning, mission control , and training.
a
i eJ~FIDff:!TIAL
Page 4
CONFIDENTIAL
TABLE OF CONTENTS
Paragraph Page Number
1.0 COUNTDOWN
1.1 CrewInsertion.
1.2 Communications.
1.3 Crew Participation and Countdown. . .1
1.4 Comfort. . . .1
1.5 Environmental Control System . . .2
1.6 Sounds 2
1.7 Vibrations . . 2
1.8 Visual M
1.9 Crew Station Controls and Displays 4
2.0 POWERED FLIGHT
2.1 Lift-Off Cues. 6
2.2 Roll Program 7
2.3 Pitch Program ...
2.4 Aerodynamics.
2.5 Environmental Control System.
2.6 Maximum q . .
2.7 Windshear
2.8 DCS Update. . .
2.9 Engine 1 Operation. ..
2.10 POGO. o
2.11 Engine 2 Status . . 12
2.12 Acceleration g's ... 12
2.13 BECO . . . . . .
2.14 Staging ·· ·. 3
2.15 I Engine 2 Ignition . . 13
2.16 RGS Initiate . 14
2.17 Fairing Jettison 15
2,18 GO/NO GO 20
2.19 Systems Status . 21
2.20 SECO 21
2.21 Steering. .. 22
3.0 INSERTION
3.1 Post-SECO N
3.2 SECO + 20 Seconds
3.3 Insertion Activities . . 30
4.0 ORBITAL FLIGHT 38
CONFIDENTIAL
Page 6
1
1 .0 COUNTDOWN
1.1 Crew Insertion
Cooper
The crew insertion , I thought, went very well .
Conrad
Yes , we had the suiting thing down on my cuffs and
everything so that we got right ou t t here and, boy,
th& Gunter was ready for us and i n we went .
Cooper
They were all set .
There were no delays and every
thing went exceedingly well on t he gantry.
1 . 2 Communications
Cooper
Communications , I thought were good and no probl em at
all on communications, and everything went real well.
Conrad
Yes , Stoney handled that whole thing real well .
Cooper
All right, volume was still down on the little comm
sets in the transfer van there .
That ' s Stoney' s
little improvement .
1 . 3 Crew Participation
in Countdown
Cooper
Crew participation in the countdown was good .
I
didn ' t see anything at all wrong.
Conrad
Yes , we weren ' t rushed .
We felt t hat we had enough
time to get the switches in the right position and
just ever ything went real good.
1.4 Comfort
Cooper
Comfort was real fine .
We went on to two suit fans
Page 7
2
right away.
I thought we felt plenty cool the
whole time.
Cooper
ECS was good.
Never any problem with it .
1.6 Sounds
Cooper
Sounds , I thought the only sounds tha·; we had that
were abnormal we'd been warned about.
When the
prevalves opened, they were fairly loud and when
the engines gimballed they were quite loud , and
both of those we were aware of the fact that they
would cause a lot of noise and vibrat:.on.
Conrad
There is something that really dings t he booster
too when they start .. . .
I don ' t--whet her they
drop a platform away.
Cooper
It ' s before they start moving the gant ry.
Conrad
Just before they start lowering that erector.
Boy,
something really, like it really bangs tha t booster ,
I thought.
I still don't know what it is , but , of
course, we ' d been up there with the erector down
twice before that so we were sort of e~tting used
to those kind of sounds.
1. 7 Vibration
Cooper
Okay , vibrations we already covered tr.at .
vibrations.
Sounds ,
Page 8
3
,.
1.8 Visual
Cooper
Visual .
Nothing....
Conrad
Oh , yes , wait a minute, I started getting this win
dow fogging .
Cooper
Well, let ' s cover that under the right area .
Conrad
Well, it was actually in the countdown when the
erector went down before liftoff .
Cooper
Well , okay , allright .
Conrad
I mean we still had it later .
Cooper
Well, you want to cover that now then in systems .
Conrad
Well, is that what this means , is visual, or does
that just mean something else?
FCSD REP
Yes, that ' s before liftoff.
Conrad
Yes , well t lri,s-tra-,:5pened 6e:f'1
Cooper
/
Powered flight is next .
Allright , even before liftoff ,
really is completely unforgiveable.
was filthy.
hat this
Each window
Just fogged completely over, and it was
on the inside of the outer pane of glass .
It was
I
within the sealed unit of glass , and it was so
foggy when they lowered the erector that it
it was frozen over solid,
I
d neither could
Conrad
Well, it had fogged over before they lowered the
(j()tqflDENTIA[ ,.
Page 9
4
erector and then the guys heated it w:.th hot air to
make it go away and that just made th:.ngs wor se when
they lowered the erector .
Cooper
It didn't make it go away all the way.
Conrad
That I s right it made'"it- ~ actually.
Cooper
/
L
my side in my window ~etweer. the inside
pane and the two outside panes of\\8-~s , I had a
sma ll bee , and I had a fly, and I had\several
flecks of things that I had written u~ before and
never got corrected, and they were the whole flight,
and I ' m sure they will show up on all the films
and everything.
Now between the outer sealed panes
of glass there were numerous little specks and
of stuff and throughout the flight as . .. well , we ' ll
cover that later, but that was even 7rore the flight
started .
The windows were not pla/n a nd were not in
good shape to go forthe--f~.
1 . 9 Crew Station Contr ols
and Displa_ys
Conrad
I think the Gemini cockpit is a pretty good cockpit .
Cooper
I think in general that crew stations eontrols and
displays were pretty adequate .
Conrad
I 've got a couple comments on switches and things,
but these are . . . .
~FIDENTIAL -
Page 10
5
FCSD REP
Okay , how about the time you spent in there on
prelaunch .
Cooper
Do you think that this is about right?
Yes , yes , I think that this is just about right .
I think that if you cut it down too much more
than that you are going to be ....you could cut it
down some more , there's no doubt . .. .
Conrad
It ' s that cabin purge cycles when you ' re not doing
anything really , and that ' s excellent time .
Cooper
... that you can cut it down, but that ' s the thing
that takes the time for both the ground crews ...
and that ' s lost time.
Conrad
I don ' t know . ...
I don ' t think you want to rush the crew and now
our count that second day went by the clock, boy.
We got in there at the right time .
We counted down
and lifted off on, and I didn ' t feel that I was
rushed , and I didn ' t feel that I sat in there for
an excessive amount of time .
Cooper
No , I didn ' t either.
I thought that it went just
about right , time wise .
,.
Conrad
Long as there ' s no holds in the count everything' s
great .
Page 11
FtE>ENTI L
6
2.0
2.1
POWERED FLIGHT
Lif t Off Cues
Cooper
Okay , lift- off cues , CAP COM .
into the act until later .
CAP CO~ didn ' t come
Stoney counted us down
thru ignition and lift-off and then CAP COM picked
us up at l ift- off .
Motion is an excellent clue .
There ' s doubt in your mind when you ljft- off .
You
know, the second you lift- off that yot .' ve lifted .
Vibration was very low.
Conrad
It had dropped out almost completely a.t lift- off,
felt that shaking was very l i ght.
Cooper
There was very little vibrati on at all .
vibration , very l ow.
Okay,
Noise I thought, was quite
low .
Conrad
I was particularl y aware of the noises of goi ng
through the max Q regionar y thing .
Oh , t his is
lift-off again .
I thought the noises were very
well at l iftoff .
You know the engines were
running from the outside before , you know, and man
they really make a racket , but from where you are
it's pretty quite .
You know there running.
You
can here them , there's no doubt about that , but .. .
Cooper
Okay , on visual I don ' t . . . .
day .
~
We had a very cl ear
There weren't even any clouds in sight on
IDENTI~
Page 12
C.(&)Hft0ENTI:,\~~
au,
7
!to
our sight as we were lifting off, and I couldn't
tell any visual cues to lift- off, could you?
Conrad
You had the feeling that you were moving visually.
After you get your ro ll program you see it visually
and you can see the pitch program starting visually,
but just at first
l ift-off you don't really have
any visual cues .
Cockpit displays are just l ike
advertised .
The two stage - one lights go out, and
. .. just l ike the simulator.
2 . 2 Roll Program
Conrad
Yes , I watched roll program on the gyro, I was
watching for it to come i n on time and in glancing
up when the roll program started I was still
looking at nothing but blue sky, but I was aware
visually as you say that the booster was rolling.
Yes , you can have a airplane when you are looking
at nothing but blue sky and start a motion and you
may not know exactly what the motion is, but you
know t hat you are moving.
Cooper
Now on this cockpit display, something that I got two
different answers to from different people on how the
gyro and the actual case was going to be set and it
suddenly dawned on me that they actually set the gyro
so that you are launching down the 90 degrees.
You're
Page 13
8
progressi ng down to 90 degrees line , e. la the
simulator, although the booster sets on 85 degrees
and when you turn to 72 degrees launch azimuth
you are rolling clockwise so far as tr.e crew is
concerned .
Conrad
You roll to zero .
Cooper
But you are rolling to is real ly to O on the gyro
as precessed around so that you are net really
setting on the actual launch azimuth, you are
actually setting so that when you stai§'e on over i n
yaw then pitch over then in your yaw your on the in
plane line.
FCSD REP
You ' re coming down the zero line .
Y01.:. 1 re yawing
down the zero l i ne .
Cooper
That 's right , and I kept getting diffe.rent answers
on this and this is in fact the case.
Roll program
was exactly right on time and ended e>:actly on time.
2 . 3 Pitch Program
Cooper
2. 4
Pitch program started exactly on time.
Aerodynamic
Cooper
Aerodynamic was nothing new or differE:nt about it .
It was just standard.
We build up to the noises at
max Q; the noise built up to gradual level and the
vibration and quantity built up to ma>:~ and then
dropped off very rapidly J.1'd:i!Jitely thereafter.
FlDENTIAL
Page 14
CONFICtleNTIA~ •
2. 5
9
ECS
Conrad
Right on the button.
Cooper
ECS was right on the money , no problem at all .
Max Q we ' ve already stated .
Conr ad
The cabin s ealed a little bit high like they said
it would .
I forget the number.
It was about 5.8.
Cooper
About 5.8 or 9 and just gradually dwindled back down .
Conrad
And just after we got in there by the time I looked
at it again after insertion everything it bled down
on our gage to 4.9, our gage read a little low .
I
think the actual reading , you will pr obably find
the cabin actually was 5.1 1 but the whole rest of
t he flight the gage never budged off the 4.9.
Cooper
The gage stayed right there like it was glued .
2 . 7 Wind Shear
Cooper
The wind shear , we had none and , certainly nothing
that we could
tell , but as I understand we ' ve been
told that for that day anyway we had almost negible
wind shear.
2 . 8 DCS Updates
Cooper
DCS updates were right on time .
FCSD REP
You had two updates?
Conrad
1 plus
45 , 2 plus 25 .
2 , 9 Engine 1 Operat i on
Cooper
The engine 1 operation couldn ' t have been better,
----~~K)ENTIAL
Page 15
..
10
It was beautiful.
Just now in between engine 1
operation and engine 2 here we have t wo items we
will insert in here .
2, 10 POGO
One was POGO..
Cooper
At 2 mi nutes and 5 seconds we started
picking up POGO and I got a fairly gcod amount of
POGO on through , stopping just at abcut 5 to 7
seconds before staging.
POGO dropped. cl ean out
exactly the same time there that we programmed POGO
on the early days.
Yes, that one surprised me .
Conrad
We ' d he1:.rd and read
tbat both John 8{!.d Gus ' s and Jim and Ed ' s f l i ght
that they were hardly even aware of IDGO and boy
when it came in on us it was loud anc. clear and ,
-------
well Gordon , neither one of us could talk hardly;
(
we were really vibrating with it and I was hard
pressed to read the displays.
By golly , if I had
to re ad
__:-t-;-:h;--e- -num;-er
--:b- _ on
__ _ , e ·a:-i~-s p~r-ays
___ I.,,. think I woul d
have been hard pressed to do it, because we really
had it pretty good.
Cooper
Yes , the rate ... the amplitude of them were such
. . . 11 cps frequency and the ampl itude of them was
such that you were on -- you were on the marginal
Page 16
11
edge of reading of any large gage and any fine
reading that you had to read, you would never be
able to read any numbers.
It was exactly like
the POGO we did all along on the program up at
Ames and as the exact amplitude , I don ' t lmow, but
i t was , . . . . .
It was no
I think we don ' t want that ~
POGO.
par icu ar y upsetting to me , because I
really was fai rly familiar with POGO having been
through a ll that POGO program, but this thing kind
of t i ckled me that we got it to see that we had
still hadn ' t solved it , but I don ' t think . . .
its something you don ' t want because if you had ot~er
things going wrong during that period of t i me it
would make it vecy difficult to say what you had
wrong or what
Conrad
It didn ' t upset me , but it surprised me , you lmow,
because I just wasn't expecting POGO.
RCSD REP
Wbat g- level would you estimate it to be?
Cooper
Well , we were sneaking right up there .
FCSD REP
I mean the POGO .
Cooper
Oh, it was right at about 5 g ' s .
FCSD REP
Well , I mean plus or minus amplitude .
Cooper
Well I , my estimate on it was that it was something
·\ 1•
Page 17
12
on the order of maybe three quarters of a g .
Well, I
don I t !mow whether it was that high c,r not .
Conrad
I thought it was at least a half , if not better .
Apparently it wasn't that high .
surprised.
Like I say, we were really getting the
--
ramrod out of it.
Cooper
I ws.s really
s beyond what we selected as we th~ht
should be the cutoff.
It was more tr.an wh~ we
l
had selected at Ames as being max acc 7.
in this.I passed up ver
b •
there one of
the first things that happened immediately about
the time that we got the pitch program was the
IGS Stage 2 fuel needle failed in thE full -max
deflection position.
And it came back on and was
reading after staging briefly and thEn failed again
during staging.
It was intermittent .
2 . 11 Engine 2 Status
Cooper
Engine 2 status stayed ... was perfect .
There was
not anything wrong at al l.
2 .12
Acceleration G' s
Cooper
Acceleration g ' s were right on the piofile , were
certainly very pleasant.
2 . 13 BECO
Nothing wrong at all with them.
Page 18
13
Cooper
.
2 . 14
BECO was right on the money .
Staging
Conrad
Boy, that staging was smooth too .
Cooper
They told us that BECO was going to occur early , but
it was
Conrad
We did loft a little bit apparently like they said
we woul d because, right a fter staging ....
2. 15
Engine 2 I gnition
Conrad
Well , Engine 2 ignition, I wasn't even hardly aware of
that other than we jus t started to get a little , yc,11
know, we just sort of went off the peg at 6 g's and
Gordo said s t aging OK and Engine 2 is good and I
wasn ' t even aware that Engine 2 had lit .
You
can ' t hear it, to speak of, but you can feel the
acceleration slowly building up .
FCSD REP
Did you see anything visually?
Conrad
No , I didn't see anything.
I heard the other guys
talking about s ee the flash at the brig.
Never
saw a thing and I wasn't aware of any flash out
there either .
I\
Cooper
J didn ' t
see anything at all at BEDO.
The best clue
that I have on my side , is that I see the Fuel
and Oxidizer needles start coming down as the engine
Page 19
•
14
starts burning.
And then they coming c.own fairly
rapidly at first, I mean you get a very definite
motion on them right at first there and. they kind of settled
out.
2.16
Engine 2 ignition we've already covered.
RGS Initiate
Cooper
RGS initiate right on the money.
Conrad
I was going to mention that we had l of t ed and
that we were expected to pitch down a.nd we did when
it picked up RGS.
Cooper
It smoothed in very smooth, and the fading was
just right.
Conrad
The IGS needle really deflected and I ~as , you know,
I don't think it pitched, it didn't peg- out , but it
did make a large dip and then when the booster
came down just pitched down very smoottly down to
about 75 or 80 degrees, I guess it pitched down
almost 10 degrees.
FCSD REP
What rate did it pitch over?
Conrad
Very slow, but steady, at just
Cooper
It took about 20 seconds I guess to fade it in there .
Conrad
The needle came in and made a big deflection and
right after that the booster started pitching and
the needle started back and boy the needl e was
•
Page 20
CQ~ElDEhJIJA
15
back and thing was right on the money at about 80
degrees.
It was a very smooth transition and then
do you remember they were telling, us to look
for this one cps oscillation? Well, I didn't have
rate needl e s like Gordo did, but I wasn't aware of
any oscil lations at any time.
That booster was in
pitch and yaw as far as that went
Cooper
Those rate needles were like they were glued .
There was never through boost or second stage was
there ever any rate except that one tiny little
rate , one teensy little rate just at when we were
in POGO we got one tiny little longitudinal rate,
'
just one tiny little fleck on a rate, and was the
only one .
Otherwise it was just smooth as silk,
the whole time, rate wi se .
2.17
Fairing Jettison
Cooper
Fairing jettison.
We jettisoned fairings at 3:25
and man do they ever go .
Conrad
I counted Gordo down to them.
Okay, yes, that ' s
a good point .
Cooper
Beside the scanner fairing and the nose fairing go
and when the nose fairing went it went with all
kinds of debris .
There were pieces flying all
Page 21
16
over.
Conrad
Yes , and I don't think it went right .
I don't
believe it went right , because the Rand R can
was ripped up in the front , and I can show you on
my side the nose went like that and there was some
tape or fiber glass that goes around t he . . ..
It was fiberglass cloth and it was a ll broken loose
in jagged flaps sticking up t hat, you lmow, had
broken loose from a long in here when i.hat cover
went I had decided impression that the cover went
off askew, that it didn 't jettison t he: way i t should
have.
And this could be a good point of putting
it back to a fter insertion.
Cooper
Well, it ' s supposed to go off askew.
Conrad
Yes , well, it just di dn ' t go off clean .
That 's why
this was ripped up, see .
Cooper
Well , it something somebody might look into , but
you don ' t want to recommend that they put back to
after insertion , because your taking a weight
penalty to carry that all the way up.
Conrad
Yes, I realize that , but . . . .
Cooper
It was designed to go off ... .
Conrad
That was the reason in the first place that they
WIDE
Page 22
17
moved it up there anyhow, because they weren't ....
Cooper
No , the reason they moved it up there was because
they didn ' t have strong enough propulsion on those
squibs and spring combinations or whatever they use .
We never did get a reading on that, but whatever
the total propulsive expulsion system wasn't kick
ing, the scanner fairing wide enough but what they
would come back into the booster.
But didn't you
have the distinct impression that the nose fairing
broke into j illions of pieces when it blast .
Conrad
I certainly, I certainly , yes .
That ' s why wh~n
I say askew , I mean something didn't look right.
I can't put my finger on it, but -Cooper
It came off in many pieces anyway.
There were many,
many pieces and the whole area was just filled with
debris .
Conrad
Yes, and then , I 'm not sure that that's when we got
all that gl op on our windshiel d, the spots ...
Cooper
Well, I noted exactly at that time immediately
after the fairing went, I noted about 5 or 6 , I
saw them hit , 5 or 6 gray splots, just small ones ,
very small little gray- type splots and I was
distinctly looking for that and watching for it and
Page 23
18
they were not there before they were t'nere and I
;
saw them when they hit.
They h it duri:'.l.g all this
debris flying around period .
Conr ad
I think that you can s ti11 f i nd them o:'.l. the
windshields .
Cooper
They didn ' t burn off during reentry.
But they ' re not bad and there are just a few little
scattered ones and I think it might be interesting
t o compare how many you get there vers us and how
many you get when you jettison them in orbit .
It
may wel l be that jettisoni ng in orbit would be pre
ferab l e , but I didn ' t f i nd anything objectionable
t o jettisoning where they went , they wenm fine.
It did add a lot of debris and I agree with Pete
there was a big torn something or other out there
which may just be a fiberglass thing that is kind
of . .. ,.
Conrad
Yes , I want to get down and look at the R and R and
and I can tell you what it was , describe it a lot
better.
We ' ll probably have some pictures of it
too in the camera somewhere.
I know it ' ll show
up in some film .
FCSD REP
How l ong was this visible?
bunch of stuff out there .
ONFIDENTIAL
You say there was a big
Page 24
19
Cooper
There ' s a whole fly .
Oh, you mean the debris .
It
was gone .
Conrad
It was gone like that, but it just looked like the
whole darn thing exploded.
Cooper
It looked like it just flew into a jillion pieces.
It was all around you for maybe a period of a
second or two .
Conrad
I didn't think it was that much , i t was just gone .
Cooper
But it was a defininite period of time when you
were aware of all this debris all over and then
clear .
Okay, enough for fairing jettison.
Page 25
20
2 . l8 GO/NO GO
Cooper
GO/NO GO:
We never got a GO/NO GO beeause we lost
our number 1 radio in about 4 minutes s ometime just
prior . . . let see we got a . 8 . . . .
over VR of . 8 .
Wti got a V
We got a GO/NO GO of , ..
FCSD REP
You did get a , 8?
Cooper
We got a .8 .
Conrad
Yes , that comes much later - that com(!S after the
GO/NO GO.
Cooper
Yes, that ' s right , okay, well I don ' t remember
ever getting a ... yea , we did, we go·~ MCC GO.
Right we got a GO/NO GO , okay, but then
immediately after . 8 we never got any·':hing at all
from there on until aft er we were insi~rted and gone
to UHF No . 2.
Conrad
I think it must be in the antenna problem, I really
do .
Cooper
Well , there 's some problem there because the same
thing happened on one of the previous flights and
we definitely and completely lost radio and I
swi tched over just before we inserted,
I switched
over to number 2 and then when I call1~d but the
IVI's we were back with them then .
Page 26
21
2. 19 Systems Status
Cooper
System Status everything .. . .
Conrad
We did have ...
lights .
Let me describe the delta P
Shortly after liftoff I got the number 1
fuel cell delta Plight and I reported i t and just
about t he time I reported it , then the number 2
fuel cell delta Plight came on .
They s tayed on
all the way through boost and they were on aft er
insertion for ten , fifteen seconds and after that
\
they went right back out again and that) i s it .
It didn't effect anything on the fue y e11 operation,
tn
currents , the voltages , / t h i n g stayed fine
other than
• bein
n----tliere was no other way of
telling the~ was out of tolerance so I don ' t think
it is a problem.
Cooper
We expected it.
I ' m glad that we had them changed to orange rather
than red .
Conrad
Yeah, yeah .
Cooper
Systems status in addition to that I don ' t think we
had any systems that were exactly right , except
the radio and the acceleration as we had expected
it . We were right on the profile.
2. 20 SECO
!Oa!IIAL
SECO was ...
Page 27
22
Conrad
I think we burned out at, Gordo, 7 anc. 1/4 g's.
Cooper
Right.
SECO was exactly on time, just exactly on
time and IVI's read 002 AFT.
2. 21
Almost ierfect.
Steering
Cooper
Steering was ... there was no steerine· accelerations
or velocities that we could tell.
Steering was
just smooth as silk , apparently they :t.ad us going
right down the slot .
And when we came off, apparently
we were lined up well because there weren ' t any
rates because when we came off and wajted our 20
seconds there were no rates whatsoever and it was
just setting there just . . . . as smootr.. as
Conrad
As stable as a rock .
Cooper
As smooth as silk so that and when we started
thrusting and separating we came off :ust right
straight forward .
or anything.
Conrad
No deviation , no skidding around
Just right straight off,
I thought the IVI's were plus 2 .
written down here.
That ' s what I haVle
Plus 28 right , 3 t.p.
Cooper
I guess that's what it was.
FCSD REP
This velocity you read?
Conrad
I was going to cover that in your ... ,
Cooper
Your right, plus 2, it was -- that's :r·ight .
Plus
Page 28
~IE>l!NTtAE
23
002 .
3 ,1
Conrad
I have al l the computer readouts .
Cooper
008 right and how many up?
Conrad
3 up .
Post SECO
Cooper
MANEUVER CONTROLLER worked fine .
We went right
through ....
Conrad
Wel l, l et ' s go through t hat.
The way we had practice
SECO, Gordo, got SECO and Gordo unstowed the
CONTROLLER and I armed the BUS ARM Swit ch so that
we get the MSC- 1 doors OFF.
Cooper
Brought the propulsion power ON.
Conrad
Brought the ATTITUDE CONTROL Elect ric Power ON.
Went from RATE COMMAND to DIRECT.
switch and hit the computer.
Armed the
Armed t he sep
spacecraft thing and Gordo and I counted the
seconds down .
I n the meantime , I punched off
address 72 so that it was reading and then in 20
seconds we had SEP s/c . ...
Cooper
In 20 seconds I start ed and I called it out and
started thrusting and Pete would hit the sep
spacecraft ... .
Conrad
The reason we did that was so that we would have
Page 29
the inertial velocity readout on the ga.ge and that
was ·beautiful 25,808 and nominal was S-.lpposed to be
25,807.
You can't ask for a better calculation
from a computer than that, and a lot of people
don ' t have much faith in that thing but, I think
that I'll bet that the computed MCC figure isn't
more than a foot or two off.
I t couldn ' t be
because everything was nominal for hours and hours
in the past,
Day's it went that way where we
stayed on the flight plan to the minute, to the
second so I know that it was a good computation,
and I have the five address readouts that we read ,
We read out address 72 as 25,808; address 94 which
was R dot for gamma was plus 20 feet which is
pretty darn small so we must have almos t a zero
gamma address 97 which is the forward IVI was plus
2 feet; address 52 was perfect , it was zero.
So
there was no adjustment needed and if there had
been an adjustment needed that would ha:ve come
at 3 , 042 seconds on the computer if tbere had been
an address .
52 correction and nominal 3,008
seconds so the computer computed the nomi nal thing
off only by less than a minute, about a half a
Page 30
25
minute of what the actual nominal value
/een , s o I think thats pretty darn good
ascent routine in that comput er, and I think hat
(
now that we have Math flow 6 in there t his i
why I
think the guy shouldn't get so darn worried in MCC
underspeeds and giving them burn co/rections
t his Mickey Movse.
I' ve been
t rying to make tbis pein-t-ewe· since we got
associat ed with . . . .
Cooper
I think we had better immediate data avail abl e on
board than people have been giving it credit for .
Conrad
Tha t ' s right , and it really pleased me to see it
come out on the computer this way.
Cooper
And had we never gotten our communications back
we would have known tha t we were i n good shape
because of the data we had on board, we didn ' t
have to worry about the ground readouts and
what to do ; we would have known what to do whether
we had been under or over or anything else .
Cooper
Attitudes and rates , t here weren ' t any rat es .
The thing was steered right down the s lot .
came off smooth .
Conrad
Spacecraft separation
NflD~NTlAk
We
Page 31
CONF:10ENT-IA
26
Cooper
We separated as smooth as silk just r i ,5ht straight
ahead
Conrad
Well, we counted down and Gordo said h? was
ready and I SEP spacecraft and he thru3ted and I
went back to RATE COMMAND for them and we came
straight off .
I didn't even feel it .
The first
Previous: NASA-UAP-D018 — Gemini 4 Experiment Debriefing, 1967 · Next: NASA-UAP-D020 — Gemini 5 Technical Debriefing, Part II, 1965
Same topic: title & summary match
- NASA-UAP-D020 — Gemini 5 Technical Debriefing, Part II, 1965
- NASA-UAP-D021 — Gemini 7 Technical Debriefing, 1965
- NASA-UAP-D016 — Preliminary Gemini 4 Crew Debriefing, Part I, 1965
- NASA-UAP-D017 — Preliminary Gemini 4 Crew Debriefing, Part II, 1965
- NASA-UAP-D022 — Gemini 9 Debriefing, 1966
- NASA-UAP-D018 — Gemini 4 Experiment Debriefing, 1967
Same period: 1965
Same release: Release 03
- CIA-UAP-017 — Placement on High Alert Due to Perceived Aggressive Foreign Posturing
- DOW-UAP-D084 — US Army-Flying-Saucer-Study 1949
- FBI-UAP-D002 — FD-1057, Unresolved UAP Report, Colorado Springs, 2022
- FBI-UAP-D003 — Digital Rendering, Unresolved UAP Report, Colorado Springs, 2022
- FBI-UAP-D009 — FD-302-67, “Northeastern Orb Sighting,” 2026
- FBI-UAP-D010 — FD-302-71, “Northeastern Orb Sighting,” 2026