Skip to comments.Astronomy Picture of the Day 01-28-04
Posted on 01/28/2004 5:40:32 AM PST by petuniasevan
Discover the cosmos! Each day a different image or photograph of our fascinating universe is featured, along with a brief explanation written by a professional astronomer.
2004 January 28
Explanation: This is the mess that is left when a star explodes. The Crab Nebula, the result of a supernova seen in 1054 AD, is filled with mysterious filaments. The filaments are not only tremendously complex, but appear to have less mass than expelled in the original supernova and a higher speed than expected from a free explosion. The above image, taken by the Canada-France-Hawaii Telescope (CFHT), is in three colors chosen for scientific interest. The Crab Nebula spans about 10 light-years. In the nebula's very center lies a pulsar: a neutron star as massive as the Sun but with only the size of a small town. The Crab Pulsar rotates about 30 times each second.
A single cubic inch of this object would weigh 6 billion tons.
And now a solemn moment - it was 18 years ago today that the shuttle Challenger and its crew were lost 73 seconds after liftoff.
BY SPACEFLIGHT NOW
The following timeline was assembled in the wake of the Challenger disaster by William Harwood, United Press International's Cape Canaveral bureau chief at the time of the accident, and Rob Navias, at that time UPI radio's chief space correspondent. It was assembled in the authors' spare time as an internal reference.
The timeline merges telemetry beamed down from the shuttle, NASA recordings of the flight director's loop in mission control at the Johnson Space Center, the NASA-Select audio circuit heard by the public and a transcript of crew cabin intercom conversations released by NASA after the accident.
While every effort was made to ensure accuracy, the timing of the NASA-Select and mission control audio circuits is based on stopwatch analysis and as such is somewhat subjective. The crew cabin intercom transcript was provided by NASA rounded to the nearest second. Telemetry and photo timing was generated by NASA for the Rogers Commission, the presidential panel that investigated the mishap.
Solid rocket ignition command is sent.
Astronaut Judy Resnik, intercom: "Aaall Riight!"
First of eight 25-inch-long, 7-inch-wide exploding bolts fire, four at the base of each booster, freeing Challenger from launch pad.
First continuous vertical motion is recorded.
Film developed later shows the first evidence of abnormal black smoke appearing slightly above the suspect O-ring joint in Challenger's right-hand solid rocket booster.
The black smoke appears darkest; jets in puffs of three per second, roughly matching harmonic characteristics of the shuttle vehicle at launch.
PHOTO: SMOKE AS SEEN BY CAMERA E-60
Ground launch sequence computers begin post-liftoff "safing" of launch pad structures and equipment.
Shuttle pilot Michael Smith, intercom: "Here we go."
Last positive evidence of smoke above the aft attach fitting that holds the rear of the right-side booster to the external fuel tank. The aft attach fitting is a little less than two feet above the fuel segment joint.
Last positive visual indication of smoke swirling under the bottom of the external fuel tank.
Launch commentator Hugh Harris, NASA-SELECT television: "... Liftoff of the 25th space shuttle mission, and it has cleared the tower."
The three liquid-fueled main engines throttle up from 90 percent thrust to 104 percent thrust as planned.
Data processing systems (DPS) engineer A.F. Algate, mission control, Houston: "Liftoff confirmed."
Flight director Jay Greene, Houston: "Liftoff..."
Loss of data from the shuttle at NASA's Merritt Island antenna complex for four data frames. Four more "data BIT-synch dropouts" occur in the next one minute and six seconds. These are normal and are caused by flame and objects on the horizon that attenuate radio signals.
The backup flight system computer aboard Challenger commands the S-band PM (phase modulated) and S-band FM radio systems to switch antennas to maintain communications during the upcoming roll maneuver.
Internal pressure in the right-side booster is recorded as 11.8 pounds per square inch higher than normal.
The shuttle clears the launch pad tower and begins a maneuver to roll over, putting the crew in a "heads down" position below the external tank.
Shuttle commander Dick Scobee, air-to-ground: "Houston, Challenger. Roll program."
Astronaut Dick Covey, mission control: "Roger roll, Challenger."
Flight dynamics officer (FIDO) Brian Perry, mission control: "Good roll, flight."
Greene: "Rog, good roll."
Smith, intercom: "Go you mother."
Another antenna switch is ordered to transfer data to the Ponce De Leon tracking station.
Resnik, intercom: "LVLH." Resnik is reminding Scobee and Smith about proper cockpit ADI configurations. "LVLH" is an acronym that stands for "local vertical, local horizontal."
Resnik, intercom: "[expletive] hot!"
Mission Control spokesman Steve Nesbitt in Houston, NASA-SELECT television: "Good roll program confirmed. Challenger now heading downrange."
Smith, intercom: "Looks like we've got a lot of wind here today."
Challenger's three main engines receive commands to begin throttling down to 94 percent power, as planned.
The roll maneuver is completed and Challenger is on the proper trajectory.
Right hand SRB thrust decreases before shuttle reaches maximum dynamic pressure. This is accomplished by the burn down of ridges in the solid propellant of the forward fuel segment. Thrust is a function of surface area of propellant burning.
Scobee, intercom: "It's a little hard to see out my window here."
Left hand SRB thrust decreases as planned.
Booster systems engineer (Booster) Jerry Borrer, mission control: "Throttle down to 94." Challenger's three main engines begin throttling down as planned as the shuttle approaches the region of maximum aerodynamic pressure.
Greene: "Ninety four..."
Smith, intercom: "There's 10,000 feet and Mach point five." The shuttle is 10,000 feet high traveling at half the speed of sound.
Nesbitt: "Engines beginning throttling down, now at 94 percent. Normal throttle (setting) for most of the flight is 104 percent. We'll throttle down to 65 percent shortly.
Scobee, intercom: "Point nine."
The three main engines begin throttling down to 65 percent power as planned.
Telemetry data shows the shuttle's computer system responds properly to wind shear to adjust the ship's flight path.
Smith, intercom: "There's Mach 1."
Scobee: "Going through 19,000."
Scobee, intercom: "OK, we're throttling down."
Nesbitt: "Engines are at 65 percent. Three engines running normally..."
A flash is observed downstream of the shuttle's right wing.
A second flash is seen trailing the right wing.
A third unexplained flash is seen downstream of the shuttle's right-hand wing. 70 mm tracking camera closeup: A brilliant orange ball of flame, apparently, emerges from under the right wing and quickly merges with the plume of the solid rocket boosters. This phenomenon, observed during analysis of tracking film after launch, has been seen on previous launches.
Booster systems engineer: "Three at 65."
Nesbitt: "... Three good fuel cells. Three good APUs (auxiliary power units)..."
Greene: Sixty-five, FIDO..."
FIDO: "T-del confirms throttles." The flight dynamics officer is referring to computer software monitoring the flight in real-time.
Greene: "...Thank you."
Challenger's main engines receive commands from the onboard flight computers to begin throttling back up to 104 percent thrust as planned.
Nesbitt: "Velocity 2,257 feet per second (1,539 mph), altitude 4.3 nautical miles, downrange distance 3 nautical miles..."
Scobee, intercom: "Throttling up."
Smith: "Throttle up."
Tracking cameras show the first evidence of an abnormal plume on the right-hand solid rocket booster facing away from the shuttle. Scobee and Smith had no data on the performance of the solid rockets except for a software system that would have alerted them to malfunctions in the booster steering mechanism.
PHOTO: PLUME GROWTH TRACKED BY CAMERA E-207
Challenger passes through the region of maximum aerodynamic pressure, experiencing 720 pounds per square foot.
A continuous "well defined intense plume" of exhaust is seen on the side of the suspect booster by tracking cameras. This is clear evidence of an O-ring joint burn through.
First visual evidence of flame on the right-side booster. 70 mm tracking camera closeup: A flickering tongue of flame appears on the side of the right-side booster away from the shuttle and quickly becomes continuous.
Smith, intercom: "Feel that mother go!"
Unknown, intercom: "Wooooo Hooooo!"
Data radioed from Challenger shows the internal pressure in the right-side SRB begins dropping. This is because of the rapidly increasing hole in the failed joint.
TELEMETRY: RIGHT-HAND SRB CHAMBER PRESSURE DROPS
First evidence of flame from the rupture deflecting and impinging on the external fuel tank.
First evidence of the anomalous plume "attaching" to the fitting that couples the aft end of the right-side rocket to the base of the external fuel tank.
The plume deflection is continuous. 70 mm tracking camera closeup: A thick, well-defined plume of flame arcs away from right solid rocket booster.
The shuttle rolls slightly in response to high winds aloft.
- Smith, intercom: "Thirty-five thousand, going through one point five."
The steering mechanism of the left-hand booster suddenly moves on computer command as Challenger's flight control system compensates for wind shear. It is later noted that wind shear during Challenger's launch was more extreme than for any of the previous 24 shuttle missions, although still within design limits.
Challenger's computers order the shuttle's right-hand "elevon," or wing flap, to move suddenly.
A pressure change is recorded in the right-hand outboard elevon, indicating movement.
The shuttle's computers order a planned change in Challenger's pitch to ensure the proper angle of attack during this phase of the trajectory.
The plume from the burn through changes shape suddenly, indicating a leak has started in the shuttle's liquid hydrogen tank to fuel the fire.
A bright, sustained glow is photographed on the side of the external fuel tank.
The main engine nozzles move through relatively large arcs, trying to keep the shuttle on course as the flight computers attempt to compensate for the unbalanced thrust produced by the booster burn through. The shuttle stops the minute pitching. It is doubtful the crew was aware of the computers' efforts to keep the ship on course given the normal vibrations and acceleration experienced during this phase of flight.
Scobee, intercom: "Reading four eighty six on mine."
Smith: "Yep, that's what I've got, too."
First recorded evidence of Challenger experiencing transient motion.
Data shows the left wing's outboard elevon moves suddenly.
Booster systems engineer: "Throttle up, three at 104."
Greene: "Capcom (Covey), go at throttle up."
Tracking cameras show a bright spot suddenly appears in the exhaust plume from the side of the right-side solid rocket motor and bright spots are detected on the side of the rocket facing the belly of the shuttle.
The pressure in the shuttle's external liquid hydrogen tank begins to drop, indicating a massive leak. Smith had real-time readings of pressure in the liquid hydrogen tank, but it is doubtful he noticed anything unusual because of the rapidity of the failure. It made no difference, ultimately, because even if Challenger's pilots had suspected an SRB problem there was nothing they could have done about it. While the shuttle separates from its external fuel tank shortly before reaching orbit, it does so with no engines firing and in a benign aerodynamic environment. Separating from the tank while the SRBs were firing would drive the shuttle into the bottom of the fuel tank and the SRB exhaust plumes.
The abnormal plumes on the bottom and top of the booster appear to merge into one. This means the flame has wrapped around the joint as the leak deteriorated.
Telemetry indicates falling pressure in the 17-inch-wide liquid oxygen propellant lines feeding the three main engines.
Nesbitt: "Engines are throttling up. Three engines now at 104 percent."
Covey: "Challenger, go at throttle up."
Scobee, air-to-ground: "Roger, go at throttle up."
Data shows divergent up and down motions of the nozzles at the base of both solid rocket boosters.
The two solid rocket boosters change position relative to each other, indicating the right-side booster apparently has pulled away from one of the struts that connected its aft end to the external fuel tank. TV tracking camera: A large ball of orange fire appears higher on the other side of main fuel tank, closer to Challenger's cabin, and grows rapidly.
A "major high rate actuator command" is recorded from one of the boosters, indicating extreme nozzle motions.
The nozzles of the three liquid-fueled main engines begin moving at high rates: Five degrees per second.
Data shows a sudden lateral acceleration to the right jolts the shuttle with a force of .227 times normal gravity. This may have been felt by the crew.
Start of liquid hydrogen pressure decrease. Solid rocket boosters continue showing high nozzle motion rates.
Challenger beams back what turns out to be its final navigation update.
Main engine liquid oxygen propellant pressures begin falling sharply at turbopump inlets.
Smith, intercom: "Uh oh..." This is the last comment captured by the crew cabin intercom recorder. Smith may have been responding to indications on main engine performance or falling pressures in the external fuel tank.
Last data is captured by the Tracking and Data Relay Satellite in orbit overhead, indicating structural breakup has begun in that area.
Start of sharp decrease in liquid hydrogen pressure to the main engines.
Another lateral acceleration, this one to the left, is possibly felt by the crew. Lateral acceleration equals .254 time the force of gravity.
Internal pressure in the right-side rocket booster is recorded as 19 pounds per square inch below that of its counterpart, indicating about 100,000 pounds less thrust. Tracking cameras detect evidence of a circumferential white pattern on the left side of the base of the external tank indicating a massive rupture near the SRB-tank attach ring. This apparently is caused by the aft dome of the liquid hydrogen tank failing. The resulting forward acceleration begins pushing the tank up into the liquid oxygen section in the tip of the external fuel tank.
Vapors appear near the intertank section separating the hydrogen and oxygen sections accompanied by liquid hydrogen spillage from the aft dome of the external tank.
All three main engines respond to loss of oxygen and hydrogen inlet pressure.
Ground cameras show a sudden cloud of rocket fuel appearing along the side of the external tank. This indicates the nose of the right-hand booster may have pivoted into the intertank area, compounding the liquid oxygen rupture.
A sudden brilliant flash is photographed between the shuttle and the external tank. TV tracking camera: Fireballs merge into bright yellow and red mass of flame that engulfs Challenger. A single crackling noise is heard on air-to-ground radio. Engineers later say the sound is the result of ground transmitters searching the shuttle's frequency range for a signal.
Telemetry data from the main engines exhibit interference for the next tenth of a second.
An explosion occurs near the forward part of the tank where the solid rocket boosters attach.
The explosion intensifies and begins consuming the external fuel tank. Television tracking camera: a ball of brilliant white erupts from the area beneath the shuttle's nose.
The white flash in the intertank area greatly intensifies.
Tank pressure for on board supplies of maneuvering rocket fuel begins to fluctuate.
Data indicates the liquid-fueled main engines are approaching redline limits on their powerful fuel pumps.
Channel A of main engine No. 2's control computer votes for engine shutdown because of high pressure fuel turbopump discharge temperature. Channel B records two strikes for shutdown.
Main engine No. 3 begins shutdown because of high temperatures in its high pressure fuel pump. Last data captured by main engine No. 3's controller.
Main engine No. 1 begins shutdown because of high temperatures in high pressure fuel pump.
Last telemetry from main engine No. 1.
The last valid telemetry from the shuttle is recorded as it breaks up: pressure fluctuations in a fuel tank in the left rocket pod at Challenger's rear and chamber pressure changes in auxiliary power unit No. 1's gas generator.
End of last data frame.
Last radio signal from orbiter.
A bright flash is observed in the vicinity of the orbiter's nose. Television tracking camera closeup: The nose of the shuttle and the crew compartment suddenly engulfed in brilliant orange flame, presumably caused by ignition or burning of rocket fuel in the forward reaction control system steering jet pod.
"At that point in its trajectory, while traveling at a Mach number of 1.92 (twice the speed of sound) at an altitude of 46,000 feet, the Challenger was totally enveloped in the explosive burn," said the Rogers Commission report. "The Orbiter, under severe aerodynamic loads, broke into several large sections which emerged from the fireball. Separate sections that can be identified on film include the main engine/tail section with the engines still burning, one wing of the Orbiter, and the forward fuselage trailing a mass of umbilical lines pulled loose from the payload bay."
The nose section had ripped away from the payload bay cleanly, although a mass of electrical cables and umbilicals were torn from the cargo hold, fluttering behind the crew cabin as it shot through the thin air, still climbing. Challenger's fuselage was suddenly open like a tube with its top off. Still flying at twice the speed of sound, the resulting rush of air that filled the payload bay overpressurized the structure and it broke apart from the inside out, disintegrating in flight. Challenger's wings cartwheeled away on their own but the aft engine compartment held together, falling in one large piece toward the Atlantic Ocean, its engines on fire. The TDRS satellite in Challenger's cargo bay and its solid-fuel booster rocket were blown free as was the Spartan-Halley spacecraft. All this happened as the external tank gave up its load of propellant, which ignited in the atmosphere in what appeared to be an explosion. It was more of a sudden burning than an explosion. In any case, the two solid rockets emerged from the fireball of burning fuel and continued on, bereft of guidance from the shuttle's now-silent flight computers.
Nesbitt (not immediately realizing there had been an explosion): "One minute 15 seconds. Velocity 2,900 feet per second (1,977 mph). Altitude nine nautical miles. Downrange distance seven nautical miles."
The nose cap of the right hand solid rocket booster separates and its drogue parachute deploys. Tracking camera closeup: A lone parachute seen emerging from the plume of a solid rocket booster.
TV tracking camera, different view: White streamers of smoking debris blossom from the cloud of smoke and flame marking the spot where Challenger had been. One large burning piece falls toward the ocean. Two solid rocket boosters emerge from the fireball and corkscrew through the sky on their own. Nesbitt's commentary stops.
Greene in mission control utters the first words since the explosion 13 seconds ago: "FIDO, trajectories..."
FIDO: "Go ahead."
Greene: "Trajectory, FIDO."
FIDO: "Flight, FIDO, filters (radar) got discreting sources. We're go."
Ground control (GC) engineer N.R. Talbott, mission control: "Flight, GC, we've had negative contact, loss of downlink (of radio voice or data from Challenger)."
Greene: "OK, all operators, watch your data carefully."
FIDO: "Flight, FIDO, till we get stuff back he's on his cue card for abort modes."
Greene: "Procedures, any help?"
Unknown: "Negative, flight, no data."
Range safety control officers send radio signals that detonate the self-destruct package on right-hand solid rocket.
The left-hand booster self destructs. Tracking camera closeup: a thick cloud of black smoke suddenly engulfs rocket and brilliant but quick explosion ensues. Numerous fragments of the booster emerge from the fireball, including what appears to be a complete aft fuel segment, slowly tumbling.
T+1 min 56 sec
Nesbitt: "Flight controllers here are looking very carefully at the situation. Obviously a major malfunction."
T+2 min 01 sec
Flight controller: "Flight, GC, negative downlink."
T+2 min 08 sec
Nesbitt: "We have no downlink."
T+2 min 20 sec
TV tracking camera: falling bits of debris create white contrails arching through the blue sky. A larger object, trailing a thin cloud of vapor, plummets toward the ocean.
T+2 min 25 sec
FIDO: "Flight, FIDO."
Greene: "Go ahead."
FIDO: "RSO (range safety officer) reports vehicle exploded."
Greene (long pause): "Copy. FIDO, can we get any reports from recovery forces?"
FIDO: "Stand by."
T+2 min 45 sec
Greene: "GC, all operators, contingency procedures in effect."
T+2 min 50 sec
Nesbitt: "We have a report from the flight dynamics officer that the vehicle has exploded. The flight director confirms that. We are looking at checking with the recovery forces to see what can be done at this point."
T+3 min 03 sec
Greene: "FIDO, flight..."
FIDO: "Go ahead."
Greene: "LSO and recovery forces, any contacts?"
T+3 min 09 sec
Nesbitt: "Contingency procedures are in effect..."
FIDO: "We're working with them, flight."
T+3 min 22 sec
Nesbitt: "We will report more as we have information available. Again, to repeat, we have a report relayed through the flight dynamics officer that the vehicle has exploded. We are now looking at all the contingency operations and awaiting word from any recovery forces in the downrange field."
T+3 min 25 sec
TV tracking camera: The first pieces of debris can be seen splashing into the ocean.
T+3 min 53 sec
FIDO: "Flight, FIDO, for what it's worth, the filter shows 'em in the water."
T+3 min 58 sec
Challenger's crew cabin smashes into the Atlantic Ocean at about 200 mph. The astronauts, still strapped in their seats, experience a braking force of 200 times normal gravity. The crew cabin disintegrates and settles to the bottom 100 feet below.
T+4 min 15 sec
Television tracking camera closeup shows ocean surface east of Patrick Air Force Station. A large cloud of ruddy brown smoke hangs over surface of water as objects splash on impact nearby. The cloud probably was caused by hydrazine rocket fuel from wreckage that hit the water.
T+4 min 27 sec
Greene: "FIDO, flight. ... FIDO flight."
FIDO: "Go ahead."
Greene: "Did the RSO's have an impact point?"
FIDO: "Stand by."
T+5 min 03 sec
Nesbitt: "This is mission control, Houston. We have no additional word at this time."
T+5 min 05 sec
FIDO: "Flight, FIDO."
Greene: "Go ahead."
FIDO: "The vacuum IP (impact point) is 28.64 North, 80.28 West."
Greene: "How does that stack with the solid (rocket) recovery forces?" Greene is referring to the Liberty Star and the Freedom Star, two NASA ships on station in the Atlantic to recover Challenger's boosters after a normal launch.
FIDO: "We're still talking to them."
T+5 min 24 sec
Nesbitt: "Reports from the flight dynamics officer indicate that the vehicle apparently exploded and that impact in the water (was) at a point approximately 28.64 degrees North, 80.28 degrees West."
T+5 min 36 sec
TV tracking camera: A dark, irregularly shaped piece of debris - thought to be one of Challenger's wings - cartwheels down from the sky and splashes into the Atlantic. It is the largest piece of Challenger seen on TV impacting in the ocean.
T+5 min 46 sec
Nesbitt: "We are awaiting verification as to the location of the recovery forces in the field to see what may be possible at this point and we will keep you advised as further information is available. This is mission control."
T+6 min 15 sec
NASA television switches from ocean views to the grandstand area at the press site. A large cloud of white smoke remains visible towering into the sky, twisted by winds aloft and slowly dissipating. Small, helical streamers mark debris contrails.
T+6 min 41 sec
Greene: "OK, everybody stay off the telephones, make sure you maintain all your data, start pulling it together."
T+7 min 17 sec
Greene: "Flight, FIDO..."
FIDO: "FIDO, flight, go ahead sir."
Greene: "Are the LSO's on the loop?"
FIDO: "We can get 'em."
Greene: "Get 'em up on the loop, please."
LSO (coordinating recovery activity; identity unknown): "Yes sir, this is the LSO."
Greene: "OK, are there any forces headed out that way?"
LSO: "Yes sir. DOD (Department of Defense) LSO reports that all ... forces have been scrambled and they are on their way."
Greene: "OK, do we have an ETA?"
LSO: "Negative, sir."
T+8 min 00 sec
Greene conducts a poll of his flight controllers to determine if any data indicates what may have gone wrong.
Greene: "Booster, flight."
Booster: "Flight, booster."
Greene: "Did you see anything?"
Booster: "Nothing, sir, I looked at all the turbine temps were perfect (sic), right on the prediction. All the redlines were in good shape."
Mechanical and upper stage systems officer K.A. Reiley: "We looked good, flight."
Greene: "ECOM? ECOM, flight."
Electrical, environmental, consumables and mechanical systems engineer John Rector: "Flight, ECOM, we looked normal."
Data processing systems engineer Andrew Algate: "All our data's normal, flight."
A.J. Ceccacci: "Everything looked good, flight."
Guidance, navigation and control systems engineer Jeffrey Bantle: "Flight, the roll maneuver looked fine, what we saw of it. We were on our way decreasing roll rate as we lost data."
T+8 min 03 sec
NASA select television shows launch pad 39-B with smoke still hanging over the mobile launch platform.
T+8 min 37 sec
NASA select television focuses on a small parachute seen slowly drifting down out to sea.
T+9 min 11 sec
FIDO: "That's, uh, probably a paramedic." Later it is determined that this is the nose cap to one of the solid rocket boosters swinging from its drogue parachute.
T+9 min 19 sec
Nesbitt: "This is mission control, Houston. We are coordinating with recovery forces in the field. Range safety equipment, recovery vehicles intended for the recovery of the SRBs in the general area."
T+9 min 36 sec
Greene: "LSO, flight. LSO, flight..."
Nesbitt: "Those parachutes believed to be paramedics going into that area..."
FIDO: "We're getting them, flight."
Nesbitt: "...To repeat, we had an apparently normal ascent with the data..."
LSO: "This is LSO on flight loop."
Greene: "Rog, are you getting any inputs?"
LSO: "Sir, we've got a Jolly 1 (helicopter) on route right now. We've got ships on the way and we've got a C-130 (Hercules) on the way out."
T+9 min 41 sec
Nesbitt: "...coming from all positions being normal up through approximately time of main engine throttle back up to 104 percent. At about approximately a minute or so into the flight, there was an apparent explosion. The flight dynamics officer reported that tracking reported that the vehicle had exploded and impact into the water in an area approximately located at 28.64 degrees North, 80.28 degrees West, recovery forces are proceeding to the area including ships and a C-130 aircraft. Flight controllers reviewing their data here in mission control. We will provide you with more information as it becomes available. This is mission control, Houston."
T+11 min 05 sec
NASA select television shows the interior of mission control at the Johnson Space Center in Houston. Covey and astronaut Frederick Gregory sit silently at the Capcom console, obviously stunned.
T+11 min 39 sec
LSO: "Flight, LSO."
Greene: "Go ahead."
LSO: "Uh, Jolly's have not been cleared in yet, there's still debris coming down."
Greene: "Copy. Who's controlling this operation, please?"
LSO: "S & R (search and recovery) forces out of Patrick (Air Force Base)."
Greene: "Rog. Do we have a coordination loop with those people?"
LSO: "We're working with the SOC on DDMS coord right now." He is referring to a radio network used by Defense Department personnel.
LSO: "Flight, LSO."
LSO: "Would you like us to try to get up on DDMS coord also?"
Greene: Yes. GC, flight."
GC: "Flight, GC."
Greene: "Take that loop into one of the playback loops please, internal to the building only."
GC: "I didn't copy what you said."
Greene: "DDMS coord, patch it into one of the playback loops internal to the building."
T+12 min 37 sec
Greene: "GC, flight."
GC: "Flight, GC."
Greene: "Checkpoint status, have we taken one?"
Greene: "Take one now."
T+13 min 27 sec
GC: "All flight controllers, hold inputs, lock checkpoint in progress." This is a procedure to take a "snapshot" of all computer data recorded so far to ensure its recovery for documentation.
T+14 min 24 sec
Greene: LSO, flight."
LSO: "LSO here, sir."
Greene: "Any updates?"
LSO: "No sir. No sir, nothing to report."
T+15 min 06 sec
Greene: "Operators, contingency plan copies are coming to each console position. If you have an FCOH (flight control operations handbook) you can start on the checklist, page 27 dash 4, that's page 27-4. Don't reconfigure your console, take hard copies of all your displays, make sure you protect any data source you have."
LSO: "Flight, LSO."
LSO: "Looks like about 50 minutes, five-zero minutes, before the helicopters are cleared in because of debris."
Greene: "Fifty minutes from what time, LSO?"
LSO: "OK, from the time of the explosion."
T+21 min 53 sec
Nesbitt: "This is mission control, Houston. Repeating the information that we have at this time. We had an apparently nominal liftoff this morning at 11:38 Eastern time. The ascent phase appeared normal through approximately the completion of the roll program and throttle down and engine throttle back to 104 percent. At that point, we had an apparent explosion. Subsequent to that, the tracking crews reported to the flight dynamics officer that the vehicle appeared to have exploded and that we had an impact in the water down range at a location approximately 28.64 degrees North, 80.28 degrees west.
"At that time, the data was lost with the vehicle. According to a poll by the flight director, Jay Greene, of the positions here in mission control, there were no anomalous indications, no indications of problems with engines or with the SRBs or with any of the other systems at that moment through the point at which we lost data. Again, this is preliminary information. It is all that we have at the moment and we will keep you advised as other information becomes available. We had, there are recovery forces in the general area. Others being deployed, including aircraft and ships. We saw what we believed to be paramedics parachuting into impact area and we have no additional word at this point. We will keep you advised as details become available to us. This is mission control, Houston."
|Spirit: All 1,855 Raw Images - 2 new images since 01/26/2004 08:57:01 PST|
Sol 17 raw images have arrived!Much of the information coming from Spirit over the past few days has been engineering data. As any new images arrive from Spirit, they will be posted here. Stay tuned, Spirit is on the mend.
|Opportunity: All 449 Raw Images - 89 new images since 01/27/2004 04:10:27 PST|
Sol 3 raw images have arrived!
Opportunity began performing activities requested by the science team during Sol 4. Those images and other data are currently being sent back to Earth for posting on Sol 5. Any data not transmitted on Sol 5 will be stored onboard the rover and sent on subsequent days during the next possible communications opportunities. (Black spaces typically mean partial data has arrived, but Opportunity will fill in the rest of the data as soon as possible). Stay tuned!
It doesn't seem that it was 18 years ago. I've never read that account of the incident. In a few days, we'll be remembering another loss of some astronaut heros.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.