01.07.2014 Views

Exploring the Unknown: Selected Documents in ... - The Black Vault

Exploring the Unknown: Selected Documents in ... - The Black Vault

Exploring the Unknown: Selected Documents in ... - The Black Vault

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

350<br />

First Steps <strong>in</strong>to Space: Projects Mercury and Gem<strong>in</strong>i<br />

<strong>The</strong> relative motion of spacecraft 6 from <strong>the</strong> separation maneuver was stopped at<br />

a range of about 30 miles.<br />

<strong>The</strong> spacecraft and its systems performed very satisfactorily throughout<br />

<strong>the</strong> mission, except for <strong>the</strong> delayed-time telemetry tape recorder which failed<br />

at 20 hours 55 m<strong>in</strong>utes ground elapsed time be cause of a bear<strong>in</strong>g seizure. This<br />

recorder malfunction resulted <strong>in</strong> <strong>the</strong> loss of all delayed-time telemetry data for<br />

<strong>the</strong> rema<strong>in</strong>der of <strong>the</strong> mission.<br />

<strong>The</strong> flight progressed nom<strong>in</strong>ally to its full duration. All check lists and<br />

stowage were completed <strong>in</strong> preparation for retrofire and re entry and <strong>the</strong> reentry<br />

control system was activated. Retrofire occurred exactly on time at 25:15:58 ground<br />

elapsed time for a land<strong>in</strong>g <strong>in</strong> <strong>the</strong> West Atlantic land<strong>in</strong>g area (primary). <strong>The</strong> reentry<br />

and land<strong>in</strong>g were nom<strong>in</strong>al, and <strong>the</strong> land<strong>in</strong>g po<strong>in</strong>t achieved was less than 7 nautical<br />

miles from <strong>the</strong> planned land<strong>in</strong>g po<strong>in</strong>t. <strong>The</strong> crew rema<strong>in</strong>ed <strong>in</strong> <strong>the</strong> spacecraft until<br />

<strong>the</strong> spacecraft had been secured on <strong>the</strong> deck of <strong>the</strong> recovery ship.<br />

[pp. 2-1 through 7-17 not <strong>in</strong>cluded]<br />

[7-18]<br />

7.1.2.3 Rendezvous Phase. -<br />

7.1.2.3.1 Radar acquisition of spacecraft 7: At approximately 3 hours<br />

g.e.t., <strong>the</strong> ground update for acquisition of spacecraft 7 was received as an attitude<br />

of or yaw and 5.50 pitch up. <strong>The</strong> ground con trollers also <strong>in</strong>dicated that <strong>the</strong> <strong>in</strong>itial<br />

computer readout of range (248 nautical miles) would occur at 3 hours 15 m<strong>in</strong>utes<br />

g.e.t. <strong>The</strong> [7-19] radar was turned on <strong>in</strong> <strong>the</strong> standby position at approximately<br />

3 hours 5 m<strong>in</strong>utes g.e.t. <strong>The</strong> analog meter <strong>in</strong>dication cycled exactly as pre dicted,<br />

and <strong>the</strong> range and range rate <strong>in</strong>dications oscillated until <strong>the</strong> set warmed up. <strong>The</strong><br />

radar was <strong>the</strong>n placed on “ON”.<br />

<strong>The</strong> first radar-range readout on <strong>the</strong> MDRU was 248.66 nautical miles,<br />

which is <strong>the</strong> maximum range readable. At this time, <strong>the</strong> radar lock-on light was<br />

flicker<strong>in</strong>g. <strong>The</strong> radar lock-on became steady at 246.22 nautical miles, At that time,<br />

a radar test was performed with <strong>the</strong> rendezvous mode of <strong>the</strong> computer to verify<br />

<strong>the</strong> <strong>in</strong>terface and sequenc <strong>in</strong>g of <strong>the</strong> computer and <strong>the</strong> radar. This radar-computer<br />

test was not conclusive <strong>in</strong> that <strong>the</strong> specified 130° angle of orbit travel to rendez vous<br />

(wt) was not <strong>in</strong>serted and <strong>the</strong> last wt that was loaded was 180°, which had been<br />

used for a prelaunch test. Subsequent to <strong>the</strong> N SR<br />

ma neuver and <strong>the</strong> f<strong>in</strong>al switch<strong>in</strong>g<br />

to <strong>the</strong> rendezvous mode, <strong>the</strong> correct value of wt (130°) was loaded. <strong>The</strong> computer<br />

cycled properly, hold<strong>in</strong>g <strong>the</strong> range <strong>in</strong> <strong>the</strong> register for 100 seconds, and <strong>the</strong> IVI’s<br />

corresponded to <strong>the</strong> computer readout of total-velocity-change for rendezvous.<br />

<strong>The</strong> <strong>in</strong>itial-velocity-change for target <strong>in</strong>tercept was also noted, and <strong>the</strong> values were<br />

found to be decreas<strong>in</strong>g as range decreased. <strong>The</strong> event timer was synchronized<br />

with <strong>the</strong> <strong>in</strong>itiation of <strong>the</strong> N SR<br />

maneuver. Four m<strong>in</strong> utes after <strong>in</strong>itiation of <strong>the</strong> N SR<br />

maneuver, <strong>the</strong> computer was switched to <strong>the</strong> rendezvous mode and cont<strong>in</strong>uously<br />

monitored by <strong>the</strong> pilot. A time synchronization revealed that <strong>the</strong> event timer was<br />

approximately 7 sec onds ahead of <strong>the</strong> computer time sequence (for 100-second<br />

<strong>in</strong>tervals). <strong>The</strong> event timer was resynchronized with <strong>the</strong> computer-time and counted

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!