PDA

View Full Version : 787 setback


Chris
June 11th 06, 03:23 PM
Oh well, perhaps Boeing are going to fast in the development of the 787.
http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489

Jim Macklin
June 11th 06, 03:37 PM
too, to, two

That's why they test.



"Chris" > wrote in message
...
| Oh well, perhaps Boeing are going to fast in the
development of the 787.
|
http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
|
|

Chris
June 11th 06, 04:55 PM
Bit of a bummer though.

"Jim Macklin" > wrote in message
news:fVVig.28483$ZW3.18841@dukeread04...
> too, to, two
>
> That's why they test.
>
>
>
> "Chris" > wrote in message
> ...
> | Oh well, perhaps Boeing are going to fast in the
> development of the 787.
> |
> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
> |
> |
>
>

John Gaquin
June 11th 06, 05:04 PM
"Chris" > wrote in message

> Bit of a bummer though.
>
> "Jim Macklin" > wrote in message
>>
>> That's why they test.

If everything were to work perfectly the first time, they wouldn't call it
"development".

.Blueskies.
June 11th 06, 06:30 PM
"Chris" > wrote in message ...
> Oh well, perhaps Boeing are going to fast in the development of the 787.
> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
>


Reminds me of a song...."Tinyyyyy bubbles......"

Kingfish
June 11th 06, 09:27 PM
Airbus is having their issues with the A380 wing - that's all part of
the development process, I guess..

Chris wrote:
> Oh well, perhaps Boeing are going to fast in the development of the 787.
>

Bob Gardner
June 11th 06, 10:13 PM
Stories in the Seattle papers don't indicate panic mode.

Bob Gardner

"Chris" > wrote in message
...
> Oh well, perhaps Boeing are going to fast in the development of the 787.
> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
>

Matt Whiting
June 11th 06, 11:28 PM
Chris wrote:

> Oh well, perhaps Boeing are going to fast in the development of the 787.
> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489

Or perhaps this is just the normal course of events in developing a new
design.


Matt

Matt Whiting
June 11th 06, 11:29 PM
Chris wrote:

> Bit of a bummer though.

Why? No new design cycle is every problem-free. If it is, then you
likely aren't really doing anything new or learning anything.


Matt

Matt Whiting
June 11th 06, 11:30 PM
Bob Gardner wrote:

> Stories in the Seattle papers don't indicate panic mode.

Nor should they. Only the completely un-informed would even be
concerned about this.


Matt

RST Engineering
June 12th 06, 12:50 AM
"Research is what I am doing when I don't know what I am doing."

(W. VonBraun)




Jim




"John Gaquin" > wrote in message
. ..
>
> "Chris" > wrote in message
>
>> Bit of a bummer though.
>>
>> "Jim Macklin" > wrote in message
>>>
>>> That's why they test.
>
> If everything were to work perfectly the first time, they wouldn't call it
> "development".
>

Matt Barrow
June 12th 06, 01:04 AM
"Matt Whiting" > wrote in message
...
> Chris wrote:
>
>> Oh well, perhaps Boeing are going to fast in the development of the 787.
>> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
>
> Or perhaps this is just the normal course of events in developing a new
> design.
>
Read some of the detailed stories about Kelly Johnson and the SR-71
development.

Newps
June 12th 06, 01:28 AM
> Chris wrote:
>
>> Oh well, perhaps Boeing are going to fast in the development of the 787.
>> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489


The chem trail generators failed. The new airplane cannot be certified
until they work as designed.

Matt Whiting
June 12th 06, 02:54 AM
Matt Barrow wrote:

> "Matt Whiting" > wrote in message
> ...
>
>>Chris wrote:
>>
>>
>>>Oh well, perhaps Boeing are going to fast in the development of the 787.
>>>http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
>>
>>Or perhaps this is just the normal course of events in developing a new
>>design.
>>
>
> Read some of the detailed stories about Kelly Johnson and the SR-71
> development.

I've read Kelly's book and also Ben's book. Something else you had in mind?

Matt

Matt Whiting
June 12th 06, 02:56 AM
RST Engineering wrote:

> "Research is what I am doing when I don't know what I am doing."
>
> (W. VonBraun)

I'd add that Research is what you are doing when you don't know what you
are doing or why you are doing it.

Development is when you know why you are doing something, but still
don't what you are doing.

Engineering is when you know both why and what, but aren't sure about
when. :-)


Matt

john smith
June 12th 06, 04:07 AM
In article >,
Matt Whiting > wrote:

> RST Engineering wrote:
>
> > "Research is what I am doing when I don't know what I am doing."
> >
> > (W. VonBraun)
>
> I'd add that Research is what you are doing when you don't know what you
> are doing or why you are doing it.
>
> Development is when you know why you are doing something, but still
> don't what you are doing.
>
> Engineering is when you know both why and what, but aren't sure about
> when. :-)

When I started working in a Research & Development department, my boss
told me that it was alright to discuss the project with anyone in the
company except the Marketing Department. When I asked why Marketing, he
replied, "Because Marketing will try and sell it before we can have it
read for production."

Tater Schuld
June 12th 06, 06:18 AM
"Chris" > wrote in message
...
> Oh well, perhaps Boeing are going to fast in the development of the 787.
> http://www.tulsaworld.com/BusinessStory.asp?ID=060610_Bu_E1_Boein52489
were they using wet lay-up or pre-preg?

Matt Whiting
June 12th 06, 11:49 AM
john smith wrote:

> In article >,
> Matt Whiting > wrote:
>
>
>>RST Engineering wrote:
>>
>>
>>>"Research is what I am doing when I don't know what I am doing."
>>>
>>>(W. VonBraun)
>>
>>I'd add that Research is what you are doing when you don't know what you
>>are doing or why you are doing it.
>>
>>Development is when you know why you are doing something, but still
>>don't what you are doing.
>>
>>Engineering is when you know both why and what, but aren't sure about
>>when. :-)
>
>
> When I started working in a Research & Development department, my boss
> told me that it was alright to discuss the project with anyone in the
> company except the Marketing Department. When I asked why Marketing, he
> replied, "Because Marketing will try and sell it before we can have it
> read for production."

True, but that is basically marketing's job. Having seen both extremes,
it is better to sell it before it is ready, than to have it ready and
not be able to sell it.

Matt

Google