deferring defects
Join Date: Aug 2008
Location: moving around
Age: 47
Posts: 98
Likes: 0
Received 0 Likes
on
0 Posts
deferring a defect
to correctly defer a defect it should be recorded in the tech log .before further flight that tech log entry is signed off.
what differs one airline from another is how they get this done according the regulations.
what differs one airline from another is how they get this done according the regulations.
Join Date: Sep 2013
Location: LHR
Posts: 24
Likes: 0
Received 0 Likes
on
0 Posts
Slightly late to the party I know !
As mentioned, defects generally are raised in accordance with the MEL and should be inspected at the nearest opportunity though this depends on the flying schedule and downtime and company rules - some allow non airworthiness defects to be open on short haul until the next Daily check.
But as a general rule any defect raised needs to be closed (fixed) or deferred before flight.
If you're on a sub 40min downtime overseas and it's a broken tray table, chances are you'll defer it.
E.g. A Cat D item I raised on the first of an 8 sector day. It will almost certainly be deferred and rectified at end of the day due to minimum turn around times.
You'd raise an ADD to investigate when there's sufficient time / spares / whatever. However you'll then probably have 6-8hrs downtime overnight where the night shift can investigate. Then obviously they can clear it if spares etc. are available.
With regards an ADD extension (which our company calls a Repeat Interval Extension - RIE - not sure if this is an industry wide thing), this is usually approved by an approved manager.
If it's been raised as an ADD, then extended (RIE'd), I wouldn't have thought it was possible to extended it further.
This is all my understanding at least !
Safe Flying
Tech_Log
As mentioned, defects generally are raised in accordance with the MEL and should be inspected at the nearest opportunity though this depends on the flying schedule and downtime and company rules - some allow non airworthiness defects to be open on short haul until the next Daily check.
But as a general rule any defect raised needs to be closed (fixed) or deferred before flight.
If you're on a sub 40min downtime overseas and it's a broken tray table, chances are you'll defer it.
E.g. A Cat D item I raised on the first of an 8 sector day. It will almost certainly be deferred and rectified at end of the day due to minimum turn around times.
You'd raise an ADD to investigate when there's sufficient time / spares / whatever. However you'll then probably have 6-8hrs downtime overnight where the night shift can investigate. Then obviously they can clear it if spares etc. are available.
With regards an ADD extension (which our company calls a Repeat Interval Extension - RIE - not sure if this is an industry wide thing), this is usually approved by an approved manager.
My question is:
The item was reported end of july, then written on the tech log on 08.08. With the extension the deferred item was valid until 29.08.
Following the JAR procedure .81 extension itīs only allowed for 10 more days from the 19.08 until 29.08.
So, how can CAA aprove an extension beyond this limit? Aircraft is already at maintenance facility but company wants it flying all september.
The item was reported end of july, then written on the tech log on 08.08. With the extension the deferred item was valid until 29.08.
Following the JAR procedure .81 extension itīs only allowed for 10 more days from the 19.08 until 29.08.
So, how can CAA aprove an extension beyond this limit? Aircraft is already at maintenance facility but company wants it flying all september.
This is all my understanding at least !
Safe Flying
Tech_Log
