Reportable Service Difficulty or Routine Snag?
During a line check on a turboprop, an AME finds chafing on a hydraulic line in the wheel well where it passes through a clamp. The chafe has worn through the protective sleeve and into the outer layer of the hose, though no fluid is leaking and the hose passes a pressure check. The AME replaces the hose and clamp, records the defect, and returns the aircraft to service. The same defect was found on a sister aircraft three weeks earlier, and the AME later learns that the fleet has now seen four such cases in two months. The operator's safety management system has a voluntary reporting process, and the AME is unsure whether this is a 'reportable service difficulty' or just a maintenance snag.
1. Should this event be reported as a service difficulty? Apply the criteria for reportable occurrences to the facts.
Read the worked answer
The key criteria are whether the defect is a failure, malfunction, or defect that could affect airworthiness, and whether it indicates a systemic problem rather than an isolated event. Here the chafe did not cause a leak and the hose passed a pressure check, but it had progressed into the outer layer of a flight-critical hydraulic line, and the same condition has now appeared four times across the fleet in two months. That pattern is exactly what the reporting system exists to capture: a recurring defect with a common cause, likely a clamp, routing, or clearance issue.
An isolated chafe on one aircraft might be handled as a routine snag. A fleet pattern of four in two months is not routine. The AME should submit a service difficulty report describing the location, the extent of the chafe, the corrective action, and the fleet recurrence, and should also raise it through the operator's safety management system so the fleet is inspected. The AME should not wait to be told; the reporting obligation is tied to the nature of the defect, not to whether someone else has already noticed it.
2. What are the consequences of treating it as a routine snag, and how should the AME handle the two reporting channels?
Read the worked answer
Treating it as routine means the fleet pattern stays invisible to the regulator and to other operators, and the next aircraft may fly with a hose worn further than this one. The chafe could progress to a leak or rupture in a system where failure has serious consequences. The record would show a repaired hose but no investigation of why hoses are chafing, so the root cause - routing, clamp spacing, or a parts issue - would remain uncorrected.
On channels: the service difficulty report is the regulatory report, and the safety management system report is the operator's internal process. They serve different purposes and the AME should use both rather than choosing one. The SMS report triggers internal investigation and fleet action; the service difficulty report ensures the regulator has the data. The AME should be factual and specific in both, avoid speculation about cause in the formal report, and follow up to confirm the fleet inspection was actually carried out. Protecting the flying public here means surfacing the pattern, not just fixing the one hose.