The AD contains several embedded operational and compliance trap points that can create implementation risk if missed. These are concrete procedural, timing, documentation and parts-management details, all grounded in the AD text.
Applicability narrowness and the risk of misidentifying affected aeroplanes. The AD applies only to Model 767-200, -300 and -300F series aeroplanes with line numbers 668 through 723 inclusive that are equipped with WEU P/N 285T0035-201 (Applicability). Operators must confirm both the line number and the installed P/N to determine applicability. An incorrect assumption about serial range or installed part number could lead an operator to miss obligations or, conversely, to expend effort unnecessarily.
Condition precedent referencing a prior AD. Requirement 1 opens with a conditional: "If not previously accomplished in accordance with AD/B767/113 Requirement 1, check the status page..." That creates a dependency on maintenance history records. Incorrectly assuming prior compliance under AD/B767/113, or lacking evidence of such compliance, can cause confusion about whether the initial check must be performed within the 15‑day window. Operators must retain and be able to produce documentation that satisfies that conditional.
Dual-frequency monitoring burden and practical scheduling. The AD requires EICAS status page checks before each flight until corrective action is taken (Requirement 2.a), but also requires SB Work Instructions at intervals not to exceed every A check or 45 days (Requirement 2.b). Operators must implement both the high-frequency EICAS check and the periodic maintenance procedure concurrently. Failure to distinguish the two , for example, assuming the A-check procedure suffices for the "before each flight" requirement , risks non-compliance.
Maintenance function classification and release requirement. Note 1 says the EICAS status page check and SB work instructions are maintenance functions requiring a logbook entry and maintenance release prior to flight. Some operators might treat the EICAS status page check as a flight crew pre-flight check; the AD’s maintenance classification means licenced maintenance action and release are required. Misclassifying these actions could lead to improper documentation and regulatory exposure.
Immediate replacement requirement upon detection. Requirement 3 mandates replacement "before further flight" if any failure or loss of alert is detected during checks. That creates a hard stop: an affected aircraft may not legally continue to operate until replacement and a maintenance release occur. Logistics or parts shortages can therefore cause immediate operational disruption if failures are detected in service.
Parts and SB revision specifics. The AD prescribes specific acceptable replacement P/Ns and the service bulletin revision to be used: replacements must be in accordance with SB 767-31-0106 Revision 2 (Requirement 3 and 4). Acceptable replacement P/Ns are 285T0035-202 Mod A, or 285T0035-9, -10, -11. The AD accepts prior replacements to 285T0035-202 Mod A done per SB Revision 1 only if done before the effective date. Practically, this means operators must track both the P/N and the SB revision used for any prior work. A replacement performed to an earlier or alternate standard without the specified SB revision may not be accepted as compliance under the AD.
Installation prohibition scope and inventory control. Requirement 5 states P/N 285T0035-201 "may not be installed on any aeroplane as a replacement part" as of the effective date. That is a contemporaneous blanket prohibition for replacements. Operators must ensure spare pools and vendor inventories do not inadvertently reintroduce the banned P/N during maintenance.
Recordkeeping and audit trail. The AD’s Note 1 requires aircraft logbook entry and maintenance release. Failure to maintain proper entries or a clear maintenance release could make it difficult to demonstrate compliance during an audit , particularly where the AD’s applicability depends on prior AD/B767/113 compliance or on replacements performed before the effective date under SB Revision 1.
Supersession of AD/B767/113 and transitional uncertainty. Because the AD supersedes an earlier AD, there may be transitional uncertainty for operators about which obligations persist, which are replaced, and which prior actions count towards compliance. The opening conditional in Requirement 1 suggests the AD recognises prior compliance, but operators must validate records to apply that exception.
Operational impact of "before each flight" checks. The requirement to check the EICAS status page before each flight until replacement may impose practical pre-flight workflow impacts, especially if the EICAS check is classified as maintenance and requires a release. Operators need to coordinate between flight crew and maintainer functions to avoid operational delays.
In sum, the gotchas centre on narrow applicability, the conditional reliance on prior AD compliance, the maintenance-classification of checks, the dual-frequency monitoring regime, strict replacement and prohibition requirements, and the need to document earlier replacements to specific SB revisions. Each of these items is explicitly present in the AD text and requires operational attention to avoid non-compliance or service interruption.