Tweet
Re: Satelite Progress M-27M
che si cae en casa puedo hacerle juicio a alguien?
che si cae en casa puedo hacerle juicio a alguien?
-
-
Re: Satelite Progress M-27M
Asi se rompio en pedazos algo mas grande y pesado que el Progress M-27M
Columbia was scheduled to land at 9:16 a.m. EST.
- 2:30 a.m. EST, February 1, 2003: The Entry Flight Control Team began duty in the Mission Control Center.
The Flight Control Team had not been working on any issues or problems related to the planned de-orbit and re-entry of Columbia. In particular, the team had indicated no concerns about the debris that hit the left wing during ascent, and treated the re-entry like any other. The team worked through the de-orbit preparation checklist and re-entry checklist procedures. Weather forecasters, with the help of pilots in the Shuttle Training Aircraft, evaluated landing-site weather conditions at the Kennedy Space Center.- 8:00: Mission Control Center Entry Flight Director LeRoy Cain polled the Mission Control room for a GO/NO-GO decision for the de-orbit burn.
All weather observations and forecasts were within guidelines set by the flight rules, and all systems were normal.- 8:10: The Capsule Communicator (CAPCOM) told the crew that they were GO for de-orbit burn.
- 830 (EI-1719): Husband and McCool executed the de-orbit burn using Columbia’s two Orbital Maneuvering System engines.
The Orbiter was upside down and tail-first over the Indian Ocean at an altitude of 175 miles (282 km) and speed of 17,500 miles per hour (7.8 km/s) when the burn was executed. A 2-minute, 38-second de-orbit burn during the 255th orbit slowed the Orbiter to begin its re-entry into the atmosphere. The burn proceeded normally, putting the crew under about one-tenth gravity. Husband then turned Columbia right side up, facing forward with the nose pitched up.- 809 (EI+000): Entry Interface (EI), arbitrarily defined as the point at which the Orbiter entered the discernible atmosphere at 400,000 feet (120 km; 76 mi), occurred over the Pacific Ocean.
As Columbia descended, the heat of reentry caused wing leading-edge temperatures to rise steadily, reaching an estimated 2,500 °F (1,370 °C) during the next six minutes (As former Space Shuttle Program Manager Wayne Hale said in a press briefing, about 90% of this heating is the result of compression of the atmospheric gas caused by the orbiter's supersonic flight, rather than the result of friction).
Columbia at about 8:57. Debris is visible coming from the left wing (bottom). The image was taken at Starfire Optical Range atKirtland Air Force Base.
- 839 (EI+270): A sensor on the left wing leading edge spar showed strains higher than those seen on previousColumbia re-entries.
This was recorded only on the Modular Auxiliary Data System, which is similar in concept to a flight data recorder, and was not sent to ground controllers or shown to the crew.- 832 (EI+323): Columbia executed a planned roll to the right. Speed: Mach 24.5.
Columbia began a banking turn to manage lift and therefore limit the Orbiter's rate of descent and heating.- 853 (EI+404): Columbia entered a 10-minute period of peak heating, during which the thermal stresses were at their maximum. Speed: Mach 24.1; altitude: 243,000 feet (74 km; 46.0 mi).
- 800 (EI+471): Columbia was about 300 miles (480 km) west of the California coastline.
The wing leading-edge temperatures usually reached 2,650 °F (1,450 °C) at this point.- 826 (EI+557): Columbia crossed the California coast west of Sacramento. Speed: Mach 23; altitude: 231,600 feet (70.6 km; 43.86 mi).
Columbia debris (in red, orange, and yellow) detected by National Weather Service radar over Texas and Louisiana.
The Orbiter's wing leading edge typically reached more than 2,800 °F (1,540 °C) at this point.- 846 (EI+577): Various people on the ground saw signs of debris being shed. Speed: Mach 22.8; altitude: 230,200 feet (70.2 km; 43.60 mi).
The superheated air surrounding the Orbiter suddenly brightened, causing a streak in the Orbiter's luminescent trail that was quite noticeable in the pre-dawn skies over the West Coast. Observers witnessed four similar events during the following 23 seconds. Dialogue on some of the amateur footage indicates the observers were aware of the abnormality of what they were filming.- 824 (EI+615): The Maintenance, Mechanical, and Crew Systems (MMACS) officer told the Flight Director that four hydraulic sensors in the left wing were indicating "off-scale low". In Mission Control, re-entry had been proceeding normally up to this point.
"Off-scale low" is a reading that falls below the minimum capability of the sensor, and it usually indicates that the sensor has stopped functioning, due to internal or external factors, not that the quantity it measures is actually below the sensor's minimum response value.- 825 (EI+616): Columbia crossed from California into Nevada airspace. Speed: Mach 22.5; altitude: 227,400 feet (69.3 km; 43.07 mi).
Witnesses observed a bright flash at this point and 18 similar events in the next four minutes.- 800 (EI+651): Nearly 11 minutes after Columbia re-entered the atmosphere, wing leading-edge temperatures normally reached nearly 3,000 °F (1,650 °C).
- 832 (EI+683): Columbia crossed from Nevada into Utah. Speed: Mach 21.8; altitude: 223,400 feet (68.1 km; 42.31 mi).
- 852 (EI+703): Columbia crossed from Utah into Arizona.
- 830 (EI+741): Columbia began a roll reversal, turning from right to left over Arizona.
- 845 (EI+756): Columbia crossed from Arizona to New Mexico. Speed: Mach 20.9; altitude: 219,000 feet (67 km; 41.5 mi).
- 824 (EI+795): Columbia passed just north of Albuquerque.
- 800 (EI+831): At this point, wing leading-edge temperatures typically decreased to 2,880 °F (1,580 °C).
- 820 (EI+851): Columbia crossed from New Mexico into Texas. Speed: Mach 19.5; altitude: 209,800 feet (63.9 km; 39.73 mi).
At about this time, the Orbiter shed a Thermal Protection System tile, the most westerly piece of debris that has been recovered. Searchers found the tile in a field in Littlefield, Texas, just northwest of Lubbock.- 815 (EI+906): MMACS told the Flight Director that pressure readings had been lost on both left main landing-gear tires. The Flight Director then instructed the Capsule Communicator (CAPCOM) to let the crew know that Mission Control saw the messages and was evaluating the indications, and added that the Flight Control Team did not understand the crew's last transmission.
- 832 (EI+923): A broken response from the mission commander was recorded: "Roger, uh, bu – [cut off in mid-word] ..." It was the last communication from the crew and the last telemetry signal received in Mission Control.
- 837 (EI+928): Hydraulic pressure, which is required to move the flight control surfaces, was lost at about 837. At that time, the Master Alarm would have sounded for the loss of hydraulics, and the shuttle would have begun to lose control, starting to roll and yaw uncontrollably, and the crew would have become aware of the serious problem.[21]
- 9:00:18 (EI+969): Videos and eyewitness reports by observers on the ground in and near Dallas indicated that the Orbiter had disintegrated overhead, continued to break up into smaller pieces, and left multiple ion trails, as it continued eastward. In Mission Control, while the loss of signal was a cause for concern, there was no sign of any serious problem. Before the orbiter broke up at 9:00:18, the Columbia cabin pressure was nominal and the crew was capable of conscious actions.[21] The crew module remained mostly intact through the breakup, though it was damaged enough that it lost pressure at a rate fast enough to incapacitate the crew within seconds,[22] and was completely depressurized no later than 9:00:53.
- 9:00:57 (EI+1008): The crew module, intact to this point, was seen breaking into small subcomponents. It disappeared from view at 9:01:10. The crew, if not already dead, were killed no later than this point.
- 9:05: Residents of north central Texas, particularly near Tyler, reported a loud boom, a small concussion wave, smoke trails and debris in the clear skies above the counties east of Dallas.
- 939 (EI+1710): After hearing of reports of the shuttle being seen to break apart, Entry Flight Director LeRoy Cain declared a contingency (events leading to loss of the vehicle) and alerted search-and-rescue teams in the debris area. He called on the Ground Controller to "lock the doors". Two minutes later, Mission Control put contingency procedures into effect. Nobody was permitted to enter or leave the room, and flight controllers had to preserve all the mission data for later investigation.
Comment
-
Re: Satelite Progress M-27M
si miras el comentario de mas abajo, no creo que se clave en el fondo de SOLO tu casa....Originally posted by oceaneleven11 View PostComment
-
Re: Satelite Progress M-27M
Comment
-
Re: Satelite Progress M-27M
Aca el prode que estan haciendo entre las direfentes agencias que lo vienen siguiendo
Comment
-
Re: Satelite Progress M-27M
en mañanas campestres dijeron hoy que cae en el atlánticoComment
-
Re: Satelite Progress M-27M
para mi cae en el departamento de Nisman, asi terminamos con el caso... he dicho!Comment
-
Re: Satelite Progress M-27M
Pasa por aca en un rato!
Comment
-
Re: Satelite Progress M-27M
Hay alguna casa de apuestas inglesas para tirar un par de libras jugandome a donde cae?Comment
-
Re: Satelite Progress M-27M
ya cayo o no? decian que caia hoy a las 18,45 aprox...HOY CAEEEE EN EL ARCO DE BAROVEROOOOOOO!!!Comment
-
Comment
-
Re: Satelite Progress M-27M
Supuestamente esto es la nave rusa del orto esta. O el que saco la foto esta vendiendo un monoriel.
Comment
-
Re: Satelite Progress M-27M
ah negro osea que ya casi esta!!Originally posted by El Negro 2007 View PostComment
-
-
Re: Satelite Progress M-27M
ahora 137kmOriginally posted by El Negro 2007 View Post
mira como baja el ultimo dia, se acelero muchisimo la caida
Comment
Comment