Due to horizon trees, I often am 'forced' to point near eclipse, and sometimes the bino 5* fov or scope 3* fov does not leave enough room for 'error.' I saw a post from David indicated that he did see a 2d pass 72A ok although I did not compare the UT times to see how it matched relative to your non_obs. but looking now :) David saw it "again" 12sep 2055 ut, ditto PN, hummm, interim of ~ 7 hours, but only 1 rev, 97 min, from Ted's 0144. I suppose it could move lots in 97 mins if it fired... re eclipse predictions in general and specifically, I was watching milstar 3 last night and it faded in E and I noted the time without knowing in advance the predicted eclipse, and I then ran the text_ephem w/eclipse in Guide8 and the prediction agreed with the obs within a second or 2 (time)!! (Guide was open and the data was a click or 2 away) I have several apps that predicted shadow, and some variation is noted in the predictions, I think I have seen up to 10 secs. easier to trak sat into shadow than to always see it coming out. meanwhile 72A still seems too low for me :( At 10:58 9/13/2002 -0400, you wrote: >As previously reported, I observed 96072A on one pass last night, 2002 >Sep 13 UTC. Not previously reported is that it did not appear when I >attempted to observe it on my second pass. > >I attempted to intercept it at 03:21:03 UTC, about 4 s after it should >have exited the penumbra of Earth's shadow. ----------------------------------------------------------------- Unsubscribe from SeeSat-L by sending a message with 'unsubscribe' in the SUBJECT to SeeSat-L-request@lists.satellite.eu.org http://www.satellite.eu.org/seesat/seesatindex.html
This archive was generated by hypermail 2b29 : Fri Sep 13 2002 - 12:01:09 EDT