1996 STS-75 Tether UFO Video

The tether failure and its date

A documented engineering event: Columbia launched on February 22 and returned March 9, 1996. NASA's NSTS-37406 report records TSS-1R deployment beginning February 25 at 20:45 GMT. The tether broke inside the deployment boom at February 26, 01:29:35 GMT, with 19,695.2 metres deployed. This was still February 25 in US time zones. The satellite separated; possible retrieval was considered but not implemented because of projected propellant limits. Experiments continued during free flight. The failure is documented independently of later UFO interpretations; the known satellite is not itself an unidentified craft. [1] p. 15

Science continued after separation

The broken tether did not end contact with the satellite immediately. NASA's mission report describes restoring science operations by ground command and receiving or recording telemetry through nine ground stations during almost four and a half days of free flight. About 200 commands were sent in that phase. Later, a 50-minute interval of shuttle communications supported further experiments, while the crew saw the tether hanging below the satellite, consistent with its telemetry. This explains why later tracking images exist after the failure. Those communications concern the known TSS-1R hardware; they do not provide telemetry from the surrounding bright patches. [1] p. 16

Later tracking in the official programme

Later observations and the official video: the report records a close approach on March 1 at 05:10 GMT and crew observation of the satellite with its tether below it. NTRS identifies the Flight Day 9 programme, dated March 1, and links directly to NASA STI Program's upload. Its tether imagery is visible around 4:10; the following exchange discusses the long line and foreground material. Automated subtitles contain transcription errors and are not a precision flight transcript. The edited programme's date does not assign an exposure time to every shot, nor authenticate every commercial or social-media excerpt. [1] p. 16 · [2]

How the giant-disc interpretation spread

How the giant-disc claim developed: Billy Cox's June 2, 2000 Florida Today report, preserved in a republication, describes a commercial compilation and interviews its advocate Martyn Stubbs. The interpretation depends on patches appearing to pass behind the distant tether, making them look enormous. That apparent overlap is not a distance measurement. Cox also quotes Joseph Nuth finding Oberg's ordinary explanation reasonable, while Jack Kasher's qualified comment followed limited viewing and incomplete camera information. These are reported assessments, not separate optical experiments or a NASA institutional verdict. [4]

The proposed optical explanation

The optical explanation: Oberg's argument, republished in 2000, points to a tether image whose length changes with zoom while its apparent width does not. He proposes bright-image spreading and central darkening, with defocused point sources producing disc-like shapes; notch orientation, he argues, follows image position. These are distinct imaging effects, not simply proof that every object is ice. His claimed ranges, water-dump association and unshown refocusing sequence have not been independently reproduced here. The original board posting is not authenticated by its republication, and the argument is not a peer-reviewed, calibrated camera test. [3]

Camera C and the separate TOP instrument

Engineering context is not identification: NASA's report lists poor distant focus in low light for CCTV camera C, but does not tie that camera to the disputed images. The separate Tether Optical Phenomenon instrument had its own synchronization issues; transferring one camera's fault to another would be misleading. Philip Chien's contemporary reporting discusses orbital separation and recovery constraints, not disc identification. Together these sources document an unusual operating environment without supplying the complete detector, lens, focus, gain and processing record required to infer physical dimensions from a luminous patch. [1] p. 39 · [6] · [5]

The TOP engineering account distinguishes two brief video problems from generally reliable operation. Early downlink instability was traced to a ground frame synchronizer at White Sands; removing it restored a good picture that was used for public broadcasts. A separate loss of synchronization lasted a few seconds and cleared after a power cycle, with no recurrence during more than 30–40 further hours of camera use. The report leaves its internal or external cause uncertain. This is narrower than saying the mission's cameras were persistently defective, and neither incident is identified there as the source of the disputed disc-shaped images. [6] p. 37–38

What the records can establish

A useful archive comparison: the real satellite, real broken tether and genuine NASA broadcast do not make a giant-craft interpretation real. Foreground particles and camera effects are a plausible explanation, not a measured identity for every patch. Range must be established independently before apparent diameter or overlap becomes a size or depth claim. This case offers accessible primary footage, engineering records and traceable competing interpretations. The deployment photograph precedes the break; the later programme is shown intact through its official player. No precise terrestrial sighting point is invented for the orbital scene. [1] · [2] · [3] · [7]