File:Challenger - GPN-2000-001347.jpg
![File:Challenger - GPN-2000-001347.jpg](https://upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Challenger_-_GPN-2000-001347.jpg/400px-Challenger_-_GPN-2000-001347.jpg?20090409044430)
Original file (2,308 × 3,458 pixels, file size: 4.77 MB, MIME type: image/jpeg)
Captions
Captions
DescriptionChallenger - GPN-2000-001347.jpg |
English: Close-up view of the liftoff of the Shuttle Challenger on mission STS-51L taken from camera site 39B-2/T3. From this camera position, a cloud of grey-brown smoke can be seen on the right side of the Solid Rocket Booster (SRB) on a line directly across from the letter "U" in United States. This was the first visible sign that an SRB joint breach may have occured.
On January 28, 1986 frigid overnight temperatures caused normally pliable rubber O-ring seals and putty that are designed to seal and establish joint integrity between the Solid Rocket Booster (SRB) joint segments, to become hard and non-flexible. At the instant of SRB ignition, tremendous stresses and pressures occur within the SRB casing and especially at the joint attachmentment points. The failure of the O-rings and putty to "seat" properly at motor ignition, caused hot exhaust gases to blow by the seals and putty. During Challenger's ascent, this hot gas "blow by" ultimately cut a swath completely through the steel booster casing; and like a welder's torch, began cutting into the External Tank (ET). It is believed that the ET was compromised in several locations starting in the aft at the initial point where SRB joint failure occured. The ET hydrogen tank is believed to have been breached first, with continuous rapid incremental failure of both the ET and SRB. A chain reaction of events occurring in milliseconds culminated in a massive explosion. The orbiter Challenger was instantly ejected by the blast and went askew into the supersonic air flow. These aerodynamic forces caused structural shattering and complete destruction of the orbiter. Though it was concluded that the G-forces experienced during orbiter ejection and break-up were survivable, impact with the ocean surface was not. Tragically, all seven crewmembers perished. |
||||||
Date | Taken on 28 January 1986 | ||||||
Source | Great Images in NASA Description | ||||||
Author | NASA | ||||||
Permission (Reusing this file) |
|
||||||
Other versions | Derivative works of this file: STS51L-10144 black smoke.jpg |
![]() |
This image or video was catalogued by Johnson Space Center of the United States National Aeronautics and Space Administration (NASA) under Photo ID: GPN-2000-001347 and Alternate ID: 51L-10144. This tag does not indicate the copyright status of the attached work. A normal copyright tag is still required. See Commons:Licensing. Other languages:
العربية ∙ беларуская (тарашкевіца) ∙ български ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ English ∙ español ∙ فارسی ∙ français ∙ galego ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ italiano ∙ 日本語 ∙ македонски ∙ മലയാളം ∙ Nederlands ∙ polski ∙ português ∙ русский ∙ sicilianu ∙ slovenščina ∙ Türkçe ∙ українська ∙ 简体中文 ∙ 繁體中文 ∙ +/− |
File history
Click on a date/time to view the file as it appeared at that time.
Date/Time | Thumbnail | Dimensions | User | Comment | |
---|---|---|---|---|---|
current | 04:44, 9 April 2009 | ![]() | 2,308 × 3,458 (4.77 MB) | BotMultichillT (talk | contribs) | {{Information |Description={{en|1=Close-up view of the liftoff of the Shuttle Challenger on mission STS-51L taken from camera site 39B-2/T3. From this camera position, a cloud of grey-brown smoke can be seen on the right side of the Solid Rocket Booster |
You cannot overwrite this file.
File usage on Commons
The following page uses this file:
- File:Challenger (16503077212).jpg (file redirect)
Metadata
This file contains additional information such as Exif metadata which may have been added by the digital camera, scanner, or software program used to create or digitize it. If the file has been modified from its original state, some details such as the timestamp may not fully reflect those of the original file. The timestamp is only as accurate as the clock in the camera, and it may be completely wrong.
_error | 0 |
---|