Posted on 02/07/2003 4:08:42 PM PST by Lokibob
Many thanks for those; it also shows a larger 'plume' off the rear left wing.
Anyone got any thoughts on the speculation given by musicman in his post at #152? Looking at the series of slides and the depictions of the sensor dropouts, it seems to me that the 'orange' wire bundle was impacted and cut by plasma leakage. The rear sensors on the blue bundle stayed nominal, those tied into the orange bundle just dropped. That, to my mind, indicated that the leading edge RC/C was compromised.
As I understand the situation, Columbia was just completing their first s-turn to the right when the problems began to manifest themselves. The picture in my mind is 40 degrees nose up, with the right wing pointing at the earth...initially 80 degrees, then 43 degrees. Similar to a "camera pass" at an air show, only more extreme. They were slicing thru the thin air to lose altitude.
From the following description of the Digital Auto Pilot [DAP], it appears that the pitch and roll thrusters were inhibited at the point in the descent when the breakup started, but the yaw thrusters were still enabled. I assume that the rudder was ineffective at this point because it was being blanked by the high pitch attitude. Any comments? Do I have this right that the right wing (not the left) was pointing into the wind pretty much?
I must have something backwards because the picture in this thread shows the left wing down, not the right.
(BTW, the shuttles determine the dynamic pressure by measuring the deceleration.)
The aft RCS jets maneuver the spacecraft until a dynamic pressure of 10 pounds per square foot is sensed; at this point, the orbiter's ailerons become effective, and the aft RCS roll jets are deactivated. At a dynamic pressure of 20 pounds per square foot, the orbiter's elevators become effective, and the aft RCS pitch jets are deactivated. The orbiter's speed brake is used below Mach 10 to induce a more positive downward elevator trim deflection. At Mach 3.5, the rudder become activated, and the aft RCS yaw jets are deactivated (approximately 45,000 feet).Entry flight control is maintained with the aerojet DAP, which generates effector and RCS jet commands to control and stabilize the vehicle during its descent from orbit. The aerojet DAP is a three-axis rate command feedback control system that uses commands from guidance in automatic or from the flight crew's RHC in control stick steering. Depending on the type of command and the flight phase, these result in fire commands to the RCS or deflection commands to the aerosurfaces.
In the automatic mode, the orbiter is essentially a missile, and the flight crew monitors the instruments to verify that the vehicle is following the correct trajectory. The onboard computers execute the flight control laws (equations). If the vehicle diverges from the trajectory, the crew can take over at any time by switching to CSS. The orbiter can fly to a landing in the automatic mode (only landing gear extension and braking action on the runway are required by the flight crew). The autoland mode capability of the orbiter is used by the crew usually to a predetermined point in flying around the heading alignment cylinder. In flights to date, the crew has switched to CSS when the orbiter is subsonic. However, autoland provides information to the crew displays during the landing sequence.
So the adverse yaw must have come from drag. And any roll must have been inertial. But according to NASA, the flight attitude of the vehicle was within nominal parameters up to the point where comm was lost.
From the briefing I heard yesterday, it appears that a number of sensors in the left wheel well and on the left trailing edge either dropped offline in the two minutes before the loss of comm, or registered out-of-norm temperature increases, some as high as 14 degrees/minute. That would indicate some kind of thermal event in that vicinity, although there are certainly other explanations.
I wonder if anyone has ruled out the possibility of fire, maybe of electrical origin.
I realized that, but decided not to comment on it. The actual distance is not significantly different from that to have great bearing on your analysis. I believe somewhere in this thread someone estimated that at the time of this picture the Shuttle was 200-300 miles from the camera, but I'm not going to look for it. I've no reason to doubt that ball park estimate, especially given the 4miles/sec speed the Shuttle was travelling at the time. Sounds reasonable to me.
That leads me to wonder just what kind of cameras the conspiracy theorists have, by the way. I figure that in a thousandth of a second exposure the Shuttle would have travelled around 15-20 feet. Wreaks havoc on the clarity you can get... to say nothing about the kind of lensing and tracking required to get anywhere near that kind of film speed capability even ignoring the plasma effects ... Oh, but we know NASA and the AF are hiding loads of info, so they must be able to do it... just snap their fingers...
Don't be so sure. I saw pictures of a Titan ascent after it had shed the boosters, and the resolution was remarkable. They were classified as secret. Six months later the same photos were published in an aerospace calandar for public consumption. The investigation is not done yet.
Could be.
In this flight regime, the yaw thrusters were enabled, as they should have been. I am pretty sure that the rudder was blanked by the body of the orbiter at the high pitch angle at the time.
--Check Six my friend...
Musicman has a good idea, I would suspect that the NASA and contractor engineers would be looking for any differences in the shuttle systems data available from telemetry prior to and after the external tank insulation debris even.
brityank, my first impression of the NASA sensor timeline graphics brought me to the same preliminary conclusion you did concerning damage to the "orange" wire bundle - the failure mode of ALL of the temperature sensors in that bundle failed offline, there were no temperature changes noted. I do not know the type of temperature sensors used, thermocouples, RTDs, thermistors, or likely a mix, but it does not matter in this instance - its clear in the data then that there was no heating of these particular sensors to the point of failure. Exactly how the sensor wiring failed is not so clear, but certainly open to various theories at this point. If the sensors are indeed routed as per the NASA graphic, any damage near the wing cove/wheel well area could have caused this, whether the damage was exteme heat due to a wing breach, or physical damage due to debris. If I had to guess at this point, I would go with the leading edge RCC damage you postulate, or maybe even a significant loss of tiles on the wheel well area leading to a breach.
Of course, the precursor to all of this were the first sensor anomolies, which were increases in temperature of the brake lines. This was well noted in one of Ron Dittemore's early press conferences (Feb. 3?): http://www.newsday.com/news/health/orl-ss-nasa-transcript020303,0,5690321.story?coll=ny-health-utility
Hopefully, we will get more detailed techncial data from NASA, I don't expect it from the news media!
By the way, there is an excellent 3D cutaway graphic of the orbiter's left wing at the Orlando Sentinel:
http://www.orlandosentinel.com/news/custom/space/orl-asec-ssphoto020803,0,7510410.graphic
NASA must go through every branch of the fault trees, must not assume anything, in order to find the root cause. That is the essence of a good root cause analysis. I trust these guys, they will do a good job. But hey, what can I say- in the end, it will be the foam.
(Take your left hand, turn it 3/4th of the way palm in toward your face while pointing your fingers up, and you'll have a pretty good representation of the angle you're viewing the shuttle from in this photo.)
Now look at the edge of the left wing, which is on the bottom in this perspective. Notice how, beginning where the wing meets the middle of the fuselage, there is a sharp right angle and something pointing out from the edge. Then there is a kind of curve inward, leading to another less prominent portion sticking out, then a longer, more gradual curve inward before the normal outward curvature of the wing resumes.
This photo was shot only 1 minute before the breakup over Texas. If it does, indeed, show what it appears to, that means large pieces of that wing came off in the preceding 5 or 6 minutes of re-entry. This is consistent with what the videos of the shuttle over California show: large pieces breaking off. This is not just some tiles coming off, but actual pieces of the wing structure.
I don't think there's any question that left wing started coming apart as it met resistance from earth's atmosphere. The only reason the shuttle didn't fall straight out of the sky immediately upon the breakup of the wing, as a plane would, was its velocity.
Now as to what the root cause of the structural failure of the wing was, it's going to be exceedingly difficult to determine. The foam debris may or may not be the root cause. Could be just a coincidence. If it is the root cause, it must have done a heck of a lot more than just damage a few tiles on liftoff.
That indeed is my gut feel at this point. In case you missed it, the following thread has a lot of good info and informed FReep-Expert speculation on the breakup:
Observation on TPS damage on Orbiter [opens in new window]
I think this is significant, since if the leading edge of the left wing had been damaged (either during launch, or by ice from the urine-dump port), it would have been out of the wind during the initial roll to the right.
As the shuttle reversed and rolled to the left, the left wing would be poining at the ground and toward the forward path of the Columbia - IOW, into the wind.
I found this at a NASA website and thought it was concise [Link]:
Deorbit burn occured at 8:15 a.m. EST (1315 GMT) for a planned landing on KSC Runway 33. At approximately 8:52 a.m. EST, Columbia was crossing over the coast of California and entering Roll Reversal #1. Columbia was traveling at Mach 20.9 and 224,390 ft (MET 15 days 22 hours 17 min 50 seconds)At 8:52:20 EST, Columbia's Left Main Gear Brake Line Temp D in the left wheel well showed an off nominal temperature rise (2 degrees/min) followed by an off nominal temperature rise in Brake Line Temp A (6 degrees/min) at 8:52:39 (13:52:39 GMT) and Temp C (5 degrees/min) at 8:52:48. At 13:52:59 GMT, flight controllers saw a loss of sensor data (offscale low) from the Left Inbord Elevon Lower Skin Temp followed by a loss of sensor data from the Hydraulic System 3 Left Outboard Elevon Actuator Return Line Temp (13:53:10), Hydraulic System 1 Left Inboard Elevon Actuator Return Line Temp (13:53:11), Hydraulic system 1 Left Outboard Elevon Actuator Return Line Temp (13:53:31), Hydraulic System 2 Left Inboard Elevon Actuator Return Line Temp (8:53:36). Wires from these sensors are routed inside the wing from the orbiter midbody, in front of the main landing gear towards the leading edge and then back to the sensor locations near the trailing edge of the wing.
At 8:54 a.m. EST, while the orbiter was crossing over Eastern California, sensors indicated there was an increase in temperature in the left wheel well and Mid Fuselage. The Left Main Gear Brake Line Temp B showed an off nominal temperature rise (6 degrees/min) (8:54:13) followed by an off nominal rise (6 degrees/min) of the Mid Fuselage Left Body Line (X-axis=1215) Temperature (8:54:22), Left Main Gear Strut Actuator Temp (7 degrees/min) (8:54:27), Left Main Gear Uplock Actuator Unlock Line Temp (4 degrees/min) (13:54:36) and the System 3 Left Hand Forward Brake Switch valve Return line Temp (5 degrees/min) (13:55:23). Over a 5 minute period, Columbia's left side increased 60 degrees F while the right side increased only 15 degrees F during the same time. During this time, the inside of the Payload Bay was normal.
Shortly before 8:58 a.m. EST, while the orbiter was over New Mexico, sensors indicated an increase in drag on the left side and the flight control systems were automatically compensating. Then the Main Landing Gear Left Outboard Wheel Temperature Sensor went offline (13:55:35) followed by the Left Upper and Lower Wing Skin Temp Sensor (13:56:20). At 13:57:54, the System 2 Left Hand Aft Brake Switch Valve Return Temp increased in temperature (14 degrees/min) and the Main Landing Gear Left Hand Outboard and Inboard Tire Pressure 1&2 (13:58:33/13:58:39) and Wheel Temperature (13:58:35) goes offline (offscale low).
At 8:59 a.m. the Tire pressure sensor caused an onboard alert that was acknowledged by the crew. Communication with the crew and loss of data occured shortly after while Columbia was at a Mission Elapsed Time (MET) of 15 days 22 hours 20 minutes 22 seconds. The vehicle broke up while traveling at 12,500 mph (Mach 18.3) at an altitude of 207,135ft over East Central Texas resulting in the loss of both vehicle and crew. (Reference: JSC Ron Dittemore Post flight Technical News Conference 2/1/03, 2/2/03 and 2/7/03 3:30 pm CST).
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.