February 2000

**Table 65.1:** GBES Tracking Pass Summary for February 2000
		no	% lost			Attended	Unattended
pass	% good	op.	total	hardware	software	% recovered	% recoverable	exp	notes
0002180710	99.40	Y
0002190016	99.10	Y
0002190930	99.29	Y							HALCA signal dropout from 09h48m51s to 09h49m23s, phase glitch
0002200142	99.54	X
0002201238	99.19	X
0002210249	88.22	Y	11						large doppler residuals >100 Hz for 1/3 of pass, large noise, phase glitch
0002220457	99.84	Y							phase glitches
0002230714	86.08	Y	13			80			phase glitch, HALCA antenna pointing problem
0002240017	96.76	X	3						HALCA signal ended early
0002240942	99.89	Y
0002250144	99.50	X Y
0002251251	98.56	Y							phase glitch, short pass
0002260253	99.69	X							Decoder did not setup properly, no telemetry data collected, large doppler residuals
0002270457	99.73	Y							HALCA signal dropout from 08h01m01s to 08h01m19s, phase glitch
0002280720	99.85	Y							phase glitch
0002290017	99.16	X
0002290937	99.84	Y							phase glitch

There was a total of 17 tracking passes in February of 2000 with 6 of these being unattended tracking passes. Of the 11 attended tracking passes 11 collected the maximum amount of valid data possible. Of the 6 unattended tracking passes 6 collected the maximum amount of valid data possible. One tracking pass lost data due to orbit prediction having a large error. One tracking pass lost data due to the link from HALCA ending early. Another tracking pass lost data due to the downlink antenna on HALCA not pointing to Green Bank.

11 tracking passes were observed ``remotely'' from the Jansky Operations Center.

$\bullet$ A total of 0.03 tracking passes lost data due to the signal from HALCA being late or ending early.

$\bullet$ A total of 0.13 tracking passes lost data due to HALCA not pointing at the GBES.

$\bullet$ A total of 0.11 tracking passes lost data due to poor orbit predictions.