|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Soyuz on-orbit rendezvous burns delayed -- problem fixed?
The first two rendezvous burns for Soyuz today were slipped several hours,
and then made successfully with revised durations, so as not to affect the scheduled docking time. Anybody hearing air-to-ground or internal rumors as to the reason for this unusual delay, and whether it might influence the day-of-rendezvous maneuvers? JimO |
#2
|
|||
|
|||
"Jim Oberg" wrote The first two rendezvous burns for Soyuz today were slipped several hours, More info is available now at today's OFFICIAL USE ONLY 'NASA On-Orbit ISS Status Report" http://www.spaceref.com/news/viewsr.html?pid=14231 Soyuz TMA-5/9S (no. 215) launched last night on time (11:06pm EDT) with no issues. Orbit was attained at L+ 9 min. as planned and all deployment events (antennas, solar arrays, docking probe) were nominal and on time, automatically upon booster separation sensor signal. A computer glitch caused a delay of the first two orbit correction maneuvers. Expedition 10+1 is on its way to the ISS, with docking set for 10/16 at 12:25am EDT. During the Orbit 3 RGS (Russian ground site) pass, portions of the maneuver plan settings for correction burns DV1 and DV2 were not received by the onboard computer, due to a temporarily badly aligned gain pattern of the spacecraft's telemetry antenna. In addition, the Molniya relay satellite link was unexpectedly lost. TsUP/Moscow immediately cancelled the entire maneuver plan and uplinked the backup command load. The DV1 and DV2 maneuvers were delayed from Orbits 3 & 4 to Orbits 4 & 5 (over RGS). Because the magnitude of each of the burns was adjusted to compensate for the slip, 9S docking time remains unaffected. Investigation of the glitch continues to ensure there are no other probable cause versions or future impacts.] |
#3
|
|||
|
|||
"Jim Oberg" wrote:
A computer glitch caused a delay of the first two orbit correction maneuvers. TMA-1: Rentry problems (computer failure). TMA-2: Recontacted ISS (human error). TMA-3: Helium leakage in the propulsion system. TMA-4: (still in progress) TMA-5: Computer glitch. -- Touch-twice life. Eat. Drink. Laugh. -Resolved: To be more temperate in my postings. Oct 5th, 2004 JDL |
#4
|
|||
|
|||
"Jim Oberg" wrote in message ...
"Jim Oberg" wrote The first two rendezvous burns for Soyuz today were slipped several hours, More info is available now at today's OFFICIAL USE ONLY 'NASA On-Orbit ISS Status Report" http://www.spaceref.com/news/viewsr.html?pid=14231 Soyuz TMA-5/9S (no. 215) launched last night on time (11:06pm EDT) with no issues. Orbit was attained at L+ 9 min. as planned and all deployment events (antennas, solar arrays, docking probe) were nominal and on time, automatically upon booster separation sensor signal. A computer glitch caused a delay of the first two orbit correction maneuvers. Expedition 10+1 is on its way to the ISS, with docking set for 10/16 at 12:25am EDT. During the Orbit 3 RGS (Russian ground site) pass, portions of the maneuver plan settings for correction burns DV1 and DV2 were not received by the onboard computer, due to a temporarily badly aligned gain pattern of the spacecraft's telemetry antenna. In addition, the Molniya relay satellite link was unexpectedly lost. I was hoping to see the action in NASA's J-Track 3D:- http://science.nasa.gov/RealTime/JTr.../JTrack3D.html It seems station-bound Russian TMA flights aren't covered. Is there another site that gives a real time graphic showing such flights? |
#6
|
|||
|
|||
"Derek Lyons" wrote in message ... "Jim Oberg" wrote: A computer glitch caused a delay of the first two orbit correction maneuvers. TMA-1: Rentry problems (computer failure). TMA-2: Recontacted ISS (human error). TMA-3: Helium leakage in the propulsion system. TMA-4: (still in progress) TMA-5: Computer glitch. Oh come on, capsules are safer. Toe the party line! -- Touch-twice life. Eat. Drink. Laugh. -Resolved: To be more temperate in my postings. Oct 5th, 2004 JDL |
#7
|
|||
|
|||
rk wrote:
Derek Lyons wrote: "Jim Oberg" wrote: A computer glitch caused a delay of the first two orbit correction maneuvers. TMA-1: Rentry problems (computer failure). TMA-2: Recontacted ISS (human error). TMA-3: Helium leakage in the propulsion system. TMA-4: (still in progress) TMA-5: Computer glitch. I have been a bit behind in my reading, have they published a report yet on the root cause (or any cause!) of the unintended pyrotechnic initiation? They haven't published (that I have seen) a report on any of those incidents. D. -- Touch-twice life. Eat. Drink. Laugh. -Resolved: To be more temperate in my postings. Oct 5th, 2004 JDL |
#8
|
|||
|
|||
"Greg D. Moore \(Strider\)" wrote:
"Derek Lyons" wrote in message "Jim Oberg" wrote: A computer glitch caused a delay of the first two orbit correction maneuvers. TMA-1: Rentry problems (computer failure). TMA-2: Recontacted ISS (human error). TMA-3: Helium leakage in the propulsion system. TMA-4: (still in progress) TMA-5: Computer glitch. Oh come on, capsules are safer. Toe the party line! I made no editorial comments on the safety or lack thereof, I just provided a box score for those playing the home game to catch up with. D. -- Touch-twice life. Eat. Drink. Laugh. -Resolved: To be more temperate in my postings. Oct 5th, 2004 JDL |
#9
|
|||
|
|||
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Orbital Mechanics | JOE HECHT | Space Shuttle | 7 | July 21st 04 09:27 PM |
Jonathan's Space Report, No. 524 | Jacques van Oene | Space Shuttle | 0 | May 1st 04 12:49 PM |
Soyuz 6 mionth life in orbit | Hallerb | Space Shuttle | 28 | February 6th 04 08:42 AM |
Docking of the Soyuz TMA-3 transport spacecraft with the International Space Station | Jacques van Oene | Space Station | 0 | October 21st 03 09:41 AM |
Ed Lu Letter from Space #6 | Jacques van Oene | Space Station | 0 | July 4th 03 11:10 AM |