![]() |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
![]()
"James Oberg" writes:
I just listened to the NASA replay of the MMT audio tapes. At 9:14:48 EDT after a three and half minute discussion, Linda Ham agrees that there is no safety of flight issue, despite the absence of any test or analysis data that a foam impact on RCC is safe -- they just assumed it was -- and asks for any questions. The room was quiet as a tomb. I'd think you'd want to separate your "safety board" from the mission management team. I've been working in software development for quite some time and have observed that the products with higher quality tend to be those that have a quality assurance team that's separate from the development team. The development team is always under pressure to get projects done on schedule. Quality often suffers because their boss only cares that the project is released on schedule. These guys only seem to speak in some dialect of Microsoft Project. Microsoft Project does nothing to track quality, only schedule (I wonder if the MMT deals with Microsoft Project). The quality assurance team is responsible for running automated testing, which catches some of the bugs by testing previously existing functionality. They are also generally responsible for introducing new tests based on the customer requirements for new projects. They won't sign off on a project until it's clear that it has the functionality and quality demanded by the customer. Their boss is only concerned with quality, not schedule, so there isn't much pressure to sign off on projects that have clearly missed their quality goals. Jeff -- Remove "no" and "spam" from email address to reply. If it says "This is not spam!", it's surely a lie. |
#2
|
|||
|
|||
![]()
"James Oberg" writes:
I just listened to the NASA replay of the MMT audio tapes. At 9:14:48 EDT after a three and half minute discussion, Linda Ham agrees that there is no safety of flight issue, despite the absence of any test or analysis data that a foam impact on RCC is safe -- they just assumed it was -- and asks for any questions. The room was quiet as a tomb. Something else I noticed from another meeting (1/24), Linda Ham says, "Right, okay, same thing you told me about in my office, we've seen pieces of this size before, haven't we?". She never gets an answer because there's an interruption that a remote site isn't hearing everything, and she wraps up the foam discussion immediately afterwards. I interpret this to mean either someone told her that this foam piece was no larger than any previously seen, or that she believed that she had been told that. In fact, the foam piece was about twice as big as any seen before, and the vast majority of previous foam strikes were much smaller. |
#4
|
|||
|
|||
![]() Brian Gaff wrote: Hmm, having read that, there are a few comments. Firstly, it seems that everyone is assuming that the tiles are the main worry in this situation, and the rcc is not a worry. Folk are seemingly assuming its just too strong to be damaged. With hindsight, we can see that is not the case of course, but were there ever any tests carried out to this area in the past? Looks from my poking about as if there were never any tests because no impact should ever hit that high up. As I say, hindsight can make most of look like idiots, but in this case I'd have thought an alarm bell of a foam hit that high might have been just loud enough to hear, or is it just that the present generation of people 'assume' that the previous bunch had covered this or just did not appreciate the behaviour of such a brittle substance of that age? Brian -- Brian Gaff.... It generally looks like they believed that the impact happened about a foot or so back from where it apparently took place. Given the tools and timing available, this is not bad, just not good enough in this case. There has been a fair amount of impact testing on aircraft wing and tail leading edges at similar energy levels (4# @500 ft/s vs 2# @ 700ft/s). These structures are generally constructed of metal or composite in a single thin sheet or thin-faced honeycomb and have proven to be rather tough, with most off-center hits simply bouncing off with limited damage. A comparison to these results simply based on the relative ultimate strengths of the materials involved could have lead to a false sense of security. The tests done on the shuttle leading edges for low mass high velocity impacts may have reinforced this feeling. In this case, the overall structure does not have time to respond, so things like the overall stiffness or strength of the target do not play much of a role. A .025 oz. object at 25000 ft/s has the same kinetic energy as a 2# object at 700 ft/s, but only 3% of the inertia. In the case of high mass, low velocity impacts material elongation capability counts as much or more that strength and even new carbon/carbon is not noted for its ductility. Some folks wanting to make everything on an aircraft a casting have run into the same trap with impact prone components. The element held up to all the static ultimate and fatigue loads, but shattered when hit by a 500 ft/s 4# bird. |
#5
|
|||
|
|||
![]() Thanks, eric, very informative post. |
#6
|
|||
|
|||
![]()
"jeff findley"
the products with higher quality tend to be those that have a quality assurance team that's separate from the development team The CAIB has looked at the US nuclear submarine program for guidance on how to handle safety issues, and the experience of the Navy is at some variance with the "separate quality team" concept" in that the regular crew looks out for off-nominal conditions, and the off-nominal condition is corrected. One thing that made this more workable for the Navy than for NASA is that the Navy crew racked up thousands of hours at their jobs, while flight operations at NASA are intermittent. |
#7
|
|||
|
|||
![]() |
#8
|
|||
|
|||
![]()
"Kent Betts" writes:
"jeff findley" the products with higher quality tend to be those that have a quality assurance team that's separate from the development team The CAIB has looked at the US nuclear submarine program for guidance on how to handle safety issues, and the experience of the Navy is at some variance with the "separate quality team" concept" in that the regular crew looks out for off-nominal conditions, and the off-nominal condition is corrected. One thing that made this more workable for the Navy than for NASA is that the Navy crew racked up thousands of hours at their jobs, while flight operations at NASA are intermittent. Perhaps part of this success at the Navy is the whole "nuclear" thing. It's obvious to anyone on the job that a screw up with the nuclear reactor is a "bad thing", especially when everyone making the decisions is on the same ship and could potentially die if the wrong decision is made. Self preservation is a big motivator here. The assumption is naturally made that issues are safety issues, until proven otherwise. The recent press conference with Ham, and others, reveals that NASA's current culture is in a mode where it was assumed that the shuttle was safe until proven otherwise. Furthermore, they defended this decision making process saying they were doing the best they could with the information available. Unfortunately, they started with the wrong base assumption, that the shuttle was safe until proven otherwise. When presented with an impact case that had not been investigated before, they accepted the assumption that RCC could handle the impact. This assumption that the shuttle is safe if something unexpected happens must change. Jeff -- Remove "no" and "spam" from email address to reply. If it says "This is not spam!", it's surely a lie. |
#9
|
|||
|
|||
![]()
Robert Clark wrote:
"they've done thermal analysis of the areas of wherethere may be damaged tiles uh the analysis is not complete there is one case yet they wish to run but were just kind of jumping to the conclusion of all that um they do show obviously there's potential for significant tile damage here but, BUT THEY DO NOT INDICATE THAT THE THERMAL ANALYSIS DOES NOT INDICATE THAT THERE IS A POTENTIAL FOR A BURN THROUGH, there could be localized heating damage um obviously there is a lot of uncertainty in all this in terms of the size of the debris and where it hit and angle of incidence and uh its difficult" Use of the double-negative is common but it is often confusing. LOGICALLY what this phrase should mean is that the thermal analysis people WERE ALLOWING FOR THE POSSIBILITY OF CATASTROPHIC DAMAGE. However, from the rest of the statement I gather what he means is that the analyses argues against catastrophic damage. It appears to be a double negative as written. I suspect that, as spoken, there was a pause after the first part, as in "But they do not indicate that the thermal analysis ... [pause] ... (it) does not indicate that there is a potential for a burn through." I added the [pause] and the unspoken (it). Many people speak this way. They start a sentence and revise it in real time. You pause, back up a few words, and continue. I'll be listening to the audio myself when I get some time this weekend. Not exactly a little light beach reading ![]() -- bp Proud Member of the Human O-Ring Society Since 2003 |
#10
|
|||
|
|||
![]() |
|
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
questions about the universe... | Roger | Space Science Misc | 5 | March 17th 04 05:18 PM |
Questions about some things in the CAIB report... | Terrence Daniels | Space Shuttle | 1 | July 17th 03 10:45 PM |