Form 8130 and Liability Question

3 posts / 0 new
Last post
Form 8130 and Liability Question

 

Hello, I hope I'm asking this in the right area. After returning from a conference, the boss of our 145 repair station was asked by several parts broker/engine lease type companies this question: 

 

The broker/lease company would buy an engine that is close to its end of life but with some components like the LPT, Fan Disk and such still having some time left on them, then they would want us to remove the module, inspect the module per the Maint. manuals "continued time inspection" section and if it passes give the module an "Inspected" 8130 (of course only the inspection preformed would be referenced in block 12), give it back to the owner and in turn the owner sells it as a "serviceable" module with an “Inspected” 8130 on it.

 

I’ve been doing this type of work for over 30 years I don’t ever remember installing any items onto an engine that’s going on an aircraft with just an 8130 marked "Inspected" only on it. To me the whole thing sounds fishy but I can’t find anything in the regs that says you can’t. If any of you have any advice please post it.

Thanks.

field_vote: 
5
Your rating: None Average: 5 (2 votes)

Per the FAR's, a 8130-3 can be written to cover an inspected part of an engine, airframe or component.  The Continuing Time/Cycles must be entered into Paragraph 12 along with the reference material for the inspection.  We do quite a few 8130-3's for a aircraft recycler.  All you are doing is certifying that you have inspected a part and state that at that time, the part may be returned to service with continuing time/cycles.  The person who buys the part will make the final AirWorthiness determination of the part prior to installation.

Not so much the "buyer". But it is the responcibility of the person"installing" as indicated in the verbiage at the bottom of the form. You are good to go with the inspected 8130-3. Block 12 should reference all tech data used as well as all other pertainant info.

Cheers

J. Scott Williams

Log in or register to post comments