Re: NASA Astronaut on Columbia Repair (and others)


Neil Gerace wrote:
"Alan Jones" <alanvj@xxxxxxxxxxxxxxxx> wrote in message
news:ua73n293i1fm9d4rgk6u7lmu8753j3pkh4@xxxxxxxxxx

I've never seen the Phantom II rocket ship in action. However, what
looked good to me, on paper, was the F18L, a land based variant of the
F18 without the heavy undercarriage required for carrier landings.

The RAAF must be flying its Hornets with the original setup, then.

Not the right thread, as the original post was pertaining to an
astronauts statements,

http://www.stpns.net/view_article.html?articleId=21543251064362304

Gutierrez said the fault lies in two words - engineering arrogance.
"NASA engineers were confident that they did everything right,"
Gutierrez said. "They were so sure everything would work as planned
they didn't think an escape system was necessary. The fact is, if there
had been an escape system on Columbia and Challenger, the crews could
have survived."

A description of root cause analysis can be found at the website below
from the nasa's office of safety & mission Assurance chief
engineer's office, which includes information pertaining to
organizational factors that contribute to a systems failure such as the
challenger tragedy.

http://www.hq.nasa.gov/office/codeq/rca/rootcauseppt.pdf
"Root Cause Analysis Overview
Office of Safety & Mission Assurance Chief Engineers Office
July 2003
Purpose of this Root Cause Analysis overview:
· Establish common terminology in the NASA community to facilitate
improved communication and understanding.
· Ensure that when teams say that they have performed "root cause
analysis," they are describing the results of detailed evaluations
which reach the same level of causation.
When performing root cause analysis, it is necessary to look at more
than just the immediately visible cause, which is often the proximate
cause.
There are underlying organizational causes that are more difficult to
see, however, they may contribute significantly to the undesired
outcome and, if not corrected, they will continue to create similar
types of problems.
These are root causes....

Definitions...

Organizational factors
· Any operational or management structural entity that exerts control
over the system at any stage in its life cycle, including but not
limited to the system's concept
development, design, fabrication, test, maintenance, operation, and
disposal.
· Examples: resource management (budget, staff, training); policy
(content, implementation, verification); and management decisions.""

tom

.

Relevant Pages

  • Re: NASA Astronaut on Columbia Repair (and others)
    ... Composites Mud Fighter was interesting, sort of a poor mans A-4. ... they didn't think an escape system was necessary. ... Root Cause Analysis Overview ... · Establish common terminology in the NASA community to facilitate ...
    (sci.space.history)
  • Re: Plywood from China and other crap from China
    ... Don't disagree but I would suggest that consistently bad management is ... clusterfuck like the US economy, so I will ignore that this time. ... management strategy was the root cause for that. ... be more secure in this environment. ...
    (rec.woodworking)
  • Re: Root privilege (SOLVED)
    ... non-granularity of privileges .. ... I use root (e.g. ... · manually adjusting the system & hardware clock ... · mounting/unmounting file systems ...
    (Debian-User)
  • Re: Solaris 9 Volume Manager vx. Veritas VM
    ... > much simpler, supported, and better understood way to manage your root disks. ... > Leave Veritas for enterprise data management, ... with all rootdg volumes visible in VTOC as disk ...
    (comp.unix.solaris)
  • Re: hack that changes root to Root
    ... first line where the cursor starts (like "root" in etc/passwd). ... >For more information on this free incident handling, management ... >and tracking system please see: http://aris.securityfocus.com ...
    (Incidents)