Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Enchanted Trinkets Complete--a hardcover book containing over 500 magic items for your D&D games!
Community
General Tabletop Discussion
*Geek Talk & Media
Ad astra per aspera
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Umbran" data-source="post: 6424927" data-attributes="member: 177"><p>I hate to say this - but it seems like folks are going out of their way to question competence. Is anyone here an aeronautical engineer? If not, who are we to question the competence of someone who is?</p><p></p><p>Yes, SpaceShipTwo has a rocket engine. Did you miss the part where they have already found that engine and the fuel tanks, intact, with no signs of breach or burn through? The primary feared failure modes of the engine have thereby already been ruled out. The thing may have had some vibration issues, which will have to be looked at. Everyone in the space business will want to know what went wrong - finding rocket scientists to help with analysis won't be hard.</p><p></p><p>You guys speak as if the engineering is something kept within the heads of a small number of individuals, difficult to extract r understand. That's not how modern engineering works. Modern engineering is well documented - it is made to be passed around between people in Scaled Composites, so those people can work with it and on it. It is tested, and simulated, and instrumented with sensors for testing phases. It is set up specifically for an aeronautical engineer to access and understand it!</p><p></p><p>And you guys are so focused on the engineering. The engineering itself is the simple part. That is numbers, hard science. Noting where the engineering failed is *not* the same as finding the root cause of the accident. The real ultimate root cause is the answer to the question, "How did you get to the point where this physical failure occurred?" This is not an engineering question, but a *process* question. What was the testing process that let that engineering through to flight? What was the training process - was a training failure responsible for the co-pilot unlocking the feathering system early? Did that contribute to the destruction of the aircraft? Was the company under too great a pressure to test and deliver, such that steps were rushed, or corners cut?</p><p></p><p>Those aren't questions of engineering, but of organizations - and organizational analysis is an area in which the NTSB is very much an expert authority.</p></blockquote><p></p>
[QUOTE="Umbran, post: 6424927, member: 177"] I hate to say this - but it seems like folks are going out of their way to question competence. Is anyone here an aeronautical engineer? If not, who are we to question the competence of someone who is? Yes, SpaceShipTwo has a rocket engine. Did you miss the part where they have already found that engine and the fuel tanks, intact, with no signs of breach or burn through? The primary feared failure modes of the engine have thereby already been ruled out. The thing may have had some vibration issues, which will have to be looked at. Everyone in the space business will want to know what went wrong - finding rocket scientists to help with analysis won't be hard. You guys speak as if the engineering is something kept within the heads of a small number of individuals, difficult to extract r understand. That's not how modern engineering works. Modern engineering is well documented - it is made to be passed around between people in Scaled Composites, so those people can work with it and on it. It is tested, and simulated, and instrumented with sensors for testing phases. It is set up specifically for an aeronautical engineer to access and understand it! And you guys are so focused on the engineering. The engineering itself is the simple part. That is numbers, hard science. Noting where the engineering failed is *not* the same as finding the root cause of the accident. The real ultimate root cause is the answer to the question, "How did you get to the point where this physical failure occurred?" This is not an engineering question, but a *process* question. What was the testing process that let that engineering through to flight? What was the training process - was a training failure responsible for the co-pilot unlocking the feathering system early? Did that contribute to the destruction of the aircraft? Was the company under too great a pressure to test and deliver, such that steps were rushed, or corners cut? Those aren't questions of engineering, but of organizations - and organizational analysis is an area in which the NTSB is very much an expert authority. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Geek Talk & Media
Ad astra per aspera
Top