A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Soaring
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Wow! Ooops, take #3



 
 
Thread Tools Display Modes
  #1  
Old April 3rd 15, 11:15 PM posted to rec.aviation.soaring
Charlie M. (UH & 002 owner/pilot)
external usenet poster
 
Posts: 1,383
Default Wow! Ooops, take #3

On Friday, April 3, 2015 at 5:34:23 PM UTC-4, Dave Nadler wrote:
On Friday, April 3, 2015 at 5:25:34 PM UTC-4, howard banks wrote:
On Thursday, April 2, 2015 at 2:44:59 PM UTC-6, Dave Nadler wrote:
Yikes.
http://ad.easa.europa.eu/ad/2015-0052-E


Based on Mr Nadler's description, failure more or less inevitable.
Too small a radius will reduce the part's fatigue limit by somewhere
between one third and one half roughly speaking. A 90 degree non-radius
would result in a more or less infinite reduction in the fatigue limit
(which is the stress on a part below which it should have an infinite
fatigue life; in the real world all sorts of things reduce this limit,
as we are seeing).
Rough machining can be even more insidious. Each piece of rough machining
that you can see by eye is more or less the same as an already existing
early fatigue crack. Its root radius at a microscopic level is effectively
infinite with a corresponding reduction in the fatigue limit.
Very bad news especially when it happens at a designed in place of
inherently high stress.
All they had to do was to add some hard chromium plate on any wear
surface that ran around the radius and failure would have been even
earlier.
Pretty basic stuff. For it to have been repeated, as seems to have
happened after a known problem, amounts to extreme carelessness.


To be clear: The failed part I examined in fall 2013 was a "take #2" part.
The part was redesigned for "take #3", "resolving" the 2013 AD.
The new "take #3" part failed, leading to the most recent AD.
I have no idea what the failure of "take #3" looks like...

It is a bit surprising that 3 iterations of this part have failed...

But it is not an easy problem!

Hope that is clear,
Best Regards, Dave


I'm NOT an "ME", I'm a field service guy with a "ME" background (as well as spending a lot of time fixing "good enough bits" on many different types of machines.....).

My link before was to show that there are quite a few factors to consider (not that anyone here know all the facts or can direct the final decision).
Just pointing out that some failures have been hit before, thus a research can find a suitable resolution.

"Thus that ignore history are doomed to fail in the same manner"..... or close to that....
  #2  
Old April 3rd 15, 11:33 PM posted to rec.aviation.soaring
Craig Funston
external usenet poster
 
Posts: 208
Default Wow! Ooops, take #3

On Thursday, April 2, 2015 at 1:44:59 PM UTC-7, Dave Nadler wrote:
Yikes.
http://ad.easa.europa.eu/ad/2015-0052-E


Excellent paper on torsional vibration in aviation drive trains.
http://www.vibrationdata.com/tutoria..._vibration.pdf

Not always a simple as it appears at first.

Cheers,
Craig
7Q
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Ooops... Zomby Woof[_3_] Aviation Photos 0 April 21st 09 04:36 AM
ooopS! my Bdadd Bertie the Bunyip[_2_] Piloting 4 March 29th 07 10:40 PM
Ooops ... incident at Santa Fe A. Sinan Unur Piloting 18 November 10th 06 01:44 AM
Derby weekend ooops Jack Harkin Soaring 0 June 22nd 06 05:44 PM
Ooops - Correction Bill Denton Piloting 0 August 9th 04 01:53 PM


All times are GMT +1. The time now is 07:21 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.