AD/WILGA/4 - Elevator Control System Rotational Control Rod

The AD introduces a very narrow set of technical and administrative concepts. Each is embedded in the Requirements and the Applicability statement; the following restates those concepts and the operational mechanisms that follow from them, with direct references to the source language.

• Applicability. The AD applies to "PZL-104 Aeroplanes - All models." That phrase defines the population of aircraft to which the Requirements attach. The AD therefore targets every PZL-104 regardless of sub-model, configuration or operator, subject only to the text's later qualification on dual controls. The source phrase is: "Applicability: PZL-104 Aeroplanes - All models."

• Affected component, part number and failure mode. The AD singles out the elevator control system rotational control rod, identified by "part number (PN) WM261610," and focuses on the "adjustment fork end" of that rod. The failure mode described in the Background is loosening of the fork end safety nut, causing "decoupling and blockage of the control system." The instrument therefore links a specific part and fastening condition to an operational hazard.

• Inspection, remedial tightening and adjustment. Requirement 1 mandates inspection for "correct security of the adjustment fork end with a safety nut." Requirement 3(a) prescribes securing the fork by "pal-nut tightening." Requirement 3(b) then requires a "check of the adjustment of the control system and elevator deflection angles and carry out any subsequent adjustments." The mechanics implied are inspection to confirm presence and security of the safety nut, re-securing with a pal-nut where necessary, and functional adjustment to restore correct control geometry and deflection.

• Logbook entry. Requirement 2 states that if the adjustment fork end is secured properly the inspector must "make an entry in the aircraft maintenance log." The log entry is the record of compliance for cases that require no further remedial works.

• Manufacturer notification. Requirement 3(c) requires that, where the fork end is not appropriately secured, the person performing the remediation "Report the findings to the aircraft manufacturer." The AD thereby establishes a reporting channel to the manufacturer for discovered defects.

• Dual-control obligation. The AD contains a specific note on aeroplanes fitted with dual control systems: "rotational control rods must be checked on both controls." This expands the inspection duty where the aeroplane has duplicate control linkages.

• Temporal sequencing. Compliance timing uses "Before further flight" and "Following the inspection detailed in Requirement 1." The effective date is explicitly stated as 14 June 2005. The AD draws a distinct sequence: inspect, log or remediate, and where remedial steps are required ensure those steps are completed before re-entry to service; reporting must follow the inspection.

• Reference to other authority. The AD explicitly refers to "Polish Civil Aviation Office Airworthiness Directive (AD) Number SP-0004-2005-A dated 17 May 2005" in the Note. That reference indicates the AD's provenance or cross-reference to another regulator's directive.

These concepts collectively define a narrow compliance programme: inspect a named PN for a named defect mode, take defined corrective steps if the defect is present, log verified secure components, and report discovered defects to the manufacturer, with all urgent remedial work completed before further flight.

The AD identifies the immediate and practical stakeholders by name and by the actions it requires. From the source text, the affected parties and who pays or decides are as follows.

• Aircraft owners and operators of PZL-104 aeroplanes. The Applicability line,"PZL-104 Aeroplanes - All models",makes owners and operators the primary subject of the AD. They are responsible for ensuring their aircraft are inspected and not flown if the required corrective action has not been completed. The immediate direct cost and operational consequence falls to operators through inspection labour and any remedial work, as the AD requires actions "before further flight."

• Maintenance personnel and organisations. The AD's operational steps (inspection, securing by pal-nut tightening, checking and adjusting control geometry, logbook entry) are maintenance tasks normally performed by licensed maintenance personnel. The Requirements use operative verbs ("Carry out an inspection", "Secure the adjustment fork end", "Carry out a check", "make an entry in the aircraft maintenance log") that allocate procedural responsibility to the acting maintenance party. Maintenance organisations therefore decide who performs the inspection and how quickly it is scheduled, and they incur labour, parts and downtime costs.

• Pilots and flight crew. Pilots are indirectly affected through grounded time and mandatory "before further flight" constraints. Flight crews must not operate an aircraft subject to the AD until compliance has been completed as prescribed; the AD sets a pre-flight clearance condition based on maintenance completion.

• The aircraft manufacturer. The AD explicitly requires that findings where the adjustment fork end is not appropriately secured be "Report[ed] ... to the aircraft manufacturer." The manufacturer becomes a recipient of defect information and may, through that information, gain concentrated benefits in product surveillance or future design actions. The manufacturer may also be involved in subsequent technical guidance, though the AD itself does not prescribe manufacturer action beyond receiving reports.

• Civil Aviation Safety Authority (CASA) and its delegate. The AD is issued under CASA authority and is signed by "James Coyne, Delegate of the Civil Aviation Safety Authority." CASA, via its delegate, provides the directive, sets the effective date ("This Airworthiness Directive becomes effective on 14 June 2005") and is the issuing decision-maker in the instrument. The AD does not specify enforcement steps, but CASA is the originating regulator.

• Owners/operators of dual-control aircraft. Where an aeroplane is "fitted with a dual control system, rotational control rods must be checked on both controls." This condition increases inspection scope on dual-control aircraft and therefore affects any operator or maintenance organisation operating such configurations.

Who pays: the AD imposes inspection and possible remediation work that will be funded by the aircraft owner/operator or their maintenance provider. The AD does not allocate cost-sharing or compensation. The manufacturer receives reports but the AD does not require manufacturer-funded repairs.

Who decides: Operational decisions (when to schedule inspection, whether to ground the aircraft pending compliance, who performs tightening and adjustment) fall to the operator and their maintenance organisation, subject to the fixed legal requirement of compliance "before further flight" or as otherwise timed in the AD.

Behavioural change required: operators and maintenance personnel must perform an inspection on the specified PN and ensure either a log entry or remedial tightening and control adjustments, plus report to the manufacturer if a defect is found. Aircraft cannot be returned to flight until the AD's remedial conditions are met where the fork end was found insecure.

The AD specifies a concise set of mandatory duties; it does not spell out rights such as review, appeal, or compensation. The core duties are drawn directly from the Requirements and the Compliance table.

Duties (expressed in the AD):

• Inspect the elevator control system rotational control rod (PN WM261610) for "correct security of the adjustment fork end with a safety nut" (Requirement 1). Timing: "Before further flight, after the effective date of this Directive." The inspection is the primary duty that triggers any subsequent obligations.

• Record the inspection result in the aircraft maintenance log if the adjustment fork is correctly secured (Requirement 2): "If the adjustment fork end is secured properly make an entry in the aircraft maintenance log. No further action is required." This duty is both an evidentiary requirement and the AD's compliance mechanism for non-defective findings.

• Remedial obligations when an insecure fork end is discovered (Requirement 3): a. "Secure the adjustment fork end by way of pal-nut tightening." Timing: "Before further flight, following completion of Requirement 1 of this Directive." b. "Carry out a check of the adjustment of the control system and elevator deflection angles and carry out any subsequent adjustments." Timing: "Before further flight, following completion of Requirement 1 of this Directive." c. "Report the findings to the aircraft manufacturer." Timing: "Following completion of Requirement 1 of this Directive." The AD therefore requires both physical correction and a reporting step.

• For dual-control aircraft, check both rotational control rods: "For aeroplanes fitted with a dual control system, rotational control rods must be checked on both controls." This extends the inspection duty to both sides of duplicated controls.

Rights (explicitly stated or reasonably inferred from the AD text):

• The AD does not set out procedural rights for affected parties such as rights of review, appeal or deferral within the text provided. No explicit right to delay, to apply for an exemption, or to seek cost recovery from the manufacturer appears in the AD text. The AD prescribes mandatory action and timing but is silent on avenues for redress or variation.

• The owner/operator retains operational control over scheduling the inspection and remediation so long as actions required are completed "before further flight." That sequencing implicitly gives owners and maintenance organisations discretion over how to implement the AD within the timing constraints provided, for instance by selecting the maintenance provider, allocating resources, and creating maintenance log entries. The AD does not prescribe who must perform the work, only that prescribed inspections and steps must be carried out and logged.

• The manufacturer has the right to receive reports of findings under Requirement 3(c). The AD explicitly makes the manufacturer the recipient of required reporting when a defect is found.

Sequence and conditionality:

• The AD is conditional in structure. Requirement 1 is the precondition: carry out an inspection. If the fork is secure, the obligation is limited to a log entry (Requirement 2). If the fork is not secure, three separate obligations apply (Requirement 3(a)-(c)), each with its timing condition keyed to completion of Requirement 1. The Compliance column clarifies timing for each sub-requirement, explicitly stating which actions must occur "before further flight" and which are to be completed "following completion of Requirement 1."

Evidence and record-keeping:

• The maintenance log entry (Requirement 2) functions as the AD's record of compliance for non-defective inspections. The AD requires maintenance log documentation where the fork is secure but does not prescribe the form of the log entry.

Limitations in the AD:

• The AD does not set express technical standards for how tight is "correct security" beyond mandating pal-nut tightening where loose. The AD does not specify torque values, nor does it prescribe test procedures for "check of the adjustment of the control system and elevator deflection angles." Implementers must therefore use existing maintenance standards or manufacturer guidance, though the AD mandates reporting to the manufacturer where defects are found.

The AD itself, as provided, does not include express statutory penalties or a detailed enforcement protocol. The instrument is an operational safety directive that sets mandatory maintenance requirements and effective timing, but no fines, sanctions, or criminal/civil penalties are described within the text. The AD does, however, carry regulatory weight by its prescriptive requirements and explicit effective date.

What the AD states and leaves unsaid:

• The AD states the mandatory actions and the timetable: inspections, remedial tightening, control adjustments, logbook entry and manufacturer reporting, with repeated timing phrases "Before further flight" and "Following the inspection detailed in Requirement 1 of this Directive." The AD also states an effective date: "This Airworthiness Directive becomes effective on 14 June 2005." The document is signed by a CASA delegate.

• The AD does not set out enforcement mechanisms in the provided text. It contains no wording describing consequences for non-compliance (for example, suspension of certificate, fines, enforcement notices, or criminal liability). No administrative appeal process, compliance notification channel to the regulator, or penalty schedule is included in the AD text.

Practical enforcement implications (derived from the AD’s structure):

• Immediate operational restraint: The repeated "Before further flight" timing creates a practical operational sanction: operators must not return an aeroplane to flight until the AD's required remedial steps are completed for aircraft where the fork end was insecure. Absent the AD, an aircraft might fly; with the AD in force, the operator must either ground and comply or risk operating in breach of the directive. The AD therefore imposes an operational constraint that affects flight release decisions.

• Evidence of compliance rests on maintenance records: The AD prescribes that a log entry is made where no defect exists; remedial actions (pal-nut tightening and adjustments) will be recorded in maintenance documentation. The AD relies on maintenance documentation as the de facto compliance proof.

• Regulatory attribution: The AD is issued by CASA (signed by a delegate). Although enforcement specifics are not in the text, the issuing regulator is evident and would, in practice, be the entity responsible for supervisory or enforcement action where an operator fails to comply. The AD text itself does not document referral, investigation or enforcement steps.

• Reporting obligation as an informational enforcement lever: Requiring the operator or maintenance provider to "Report the findings to the aircraft manufacturer" creates a trail of incident reporting that can prompt manufacturer follow-up and may trigger broader safety actions. The AD therefore leverages reporting to create an information flow that supports oversight and potential corrective action beyond the immediate aircraft.

Uncertainties and implementation risk:

• Because the AD does not specify enforcement measures, the practical consequences of non-compliance are not enumerated in the text. This creates uncertainty for operators about the regulatory enforcement route and possible sanctions for non-compliance, as the AD does not define them.

• The lack of specified technical performance metrics (for example torque values for pal-nut tightening or precise deflection angle tolerances) adds execution uncertainty, which can affect inspectors' and maintenance organisations' ability to demonstrate compliance unambiguously.

In sum, the AD prescribes mandatory actions and dates but does not itself list penalties or a granular enforcement process; enforcement must be inferred from the issuing authority and the operational constraint that aircraft must not be flown until remediation is complete where required.

The AD text contains a direct cross-reference and otherwise leaves implicit any interface with broader regulatory or legal regimes. From the source content, the principal interactions and the mechanisms by which those interactions operate are the following.

Direct cross-reference:

• The AD expressly references another regulator's instrument: "Note: Polish Civil Aviation Office Airworthiness Directive (AD) Number SP-0004-2005-A dated 17 May 2005 refers." This indicates the AD is in part a domestic implementation or recognition of a foreign regulator's AD and suggests information provenance and technical origin in the Polish AD. The interaction here is a direct one-way reference: the CASA AD points to the Polish AD as the relevant action that prompted or supports the domestic directive.

Interaction via record-keeping language:

• The AD requires an entry "in the aircraft maintenance log" where the fork is secure (Requirement 2). That obligation interacts functionally with the maintenance record regime of the operator and any statutory or regulatory recordkeeping obligations that apply to aircraft maintenance. The AD does not itself recite or modify maintenance-log legal standards, but it creates a compliance trigger by relying upon the maintenance log as the compliance record.

Interaction via reporting to the manufacturer:

• Requirement 3(c) instructs that findings where the fork end is not appropriately secured must be "Report[ed] ... to the aircraft manufacturer." That reporting requirement interacts with manufacturer obligations for product monitoring and possible service bulletins, though the AD itself does not create or modify manufacturer duties. The AD’s reporting step creates an information transfer from operators to manufacturer, which can feed into product surveillance frameworks.

Implicit interaction with airworthiness and flight release regimes:

• The AD's repeated requirement "Before further flight" interacts operationally with an operator's flight release process. The AD creates a condition precedent to flight after the effective date. While the AD does not restate broader airworthiness certificate conditions or flight release procedures, the phrase interacts logically with those regimes by imposing a maintenance action as necessary for lawful continued operation.

Limits of the AD’s interaction statements:

• The AD does not explicitly amend, override, or describe conflicts with other legislative provisions or regulations. It does not mention exemptions, permits, or methods for alternative compliance. No provision in the AD lists subordinate instruments it supersedes, nor does it reference domestic civil aviation regulations by section or statute. The AD also does not identify whether reporting to the manufacturer replaces any separate requirement to inform the regulator.

Practical consequences of these interactions:

• Because the AD relies on maintenance log entries and manufacturer reporting, operators must integrate the AD's steps into existing compliance workflows. The AD does not prescribe how to handle conflicts with other maintenance scheduling obligations, nor does the AD specify a coordination mechanism where, for example, other mandatory maintenance or inspections are scheduled.

• The explicit reference to the Polish AD provides a traceable technical origin; this assists implementers seeking technical detail, but the CASA AD's text does not replicate technical specifics from the Polish instrument. Operators and maintenance organisations will therefore need to decide whether to consult the Polish AD (or the manufacturer) for more detailed procedures or technical metrics, since the CASA AD itself is procedural and limited in technical specification.

In short, the AD interacts with other instruments primarily through an explicit foreign AD reference, through reliance on maintenance records and reporting lines, and through its imposition of a before-flight condition that must be accommodated within existing airworthiness and maintenance workflows. The AD does not, within its text, set out broader legal hierarchies, remedial enforcement mechanisms, or formal cross-references to domestic statutes or guidance beyond the cited foreign AD.

The AD text provides limited chronology and no explicit amendment log beyond issue and effective dates and a reference to an originating foreign AD. From the contents available, the amendment history can only record the following items directly stated in the document.

• Issuance and signature. The AD carries a signature block: "James Coyne, Delegate of the Civil Aviation Safety Authority" and is dated "10 June 2005." This indicates the date of signing by the CASA delegate. This is the document's issuance metadata as printed in the AD.

• Effective date. The AD explicitly states: "This Airworthiness Directive becomes effective on 14 June 2005." That is the effective operative date for the Requirements set out in the AD.

• Foreign antecedent reference. The AD notes: "Note: Polish Civil Aviation Office Airworthiness Directive (AD) Number SP-0004-2005-A dated 17 May 2005 refers." That reference records a precursor or related instrument issued by Poland on 17 May 2005 and identified as SP-0004-2005-A. The CASA AD therefore registers the Polish AD as the originating technical action or as an authoritative source that led to or supports the CASA directive.

What is not in the AD with respect to amendments:

• The AD does not list any prior versions, superseded CASA ADs, or subsequent amendments. There is no consolidation note, no amendment number, and no record of revoked or replaced provisions. The instrument contains a single effective date and no further revision history.

• The AD does not include expiry, withdrawal or periodic review clauses. No sunset or review date is provided; the AD is presented as an effective directive from 14 June 2005 forward, without explicit instructions on review cycles or amendment triggers.

• The AD does not record any administrative follow-up, such as later notices, or technical bulletins, within its own text.

Consequences for implementers seeking a formal amendment trail:

• The AD provides minimal documentary history: signatory date, effective date and a reference to a Polish AD. Any further amendment information, such as whether the AD was later revised, rescinded, or superseded, is not contained in the text supplied. Implementers requiring amendment history beyond these citations must consult external registers or the issuing authority’s database, which is outside the text provided.

In sum, the instrument’s amendment history as recorded in the AD consists only of the issuance date (10 June 2005), the stated effective date (14 June 2005), and the reference to the Polish AD dated 17 May 2005. No other amendment entries or versioning information appears in the text.

The AD document itself contains no mentions of litigation, legal challenges, judicial review, or administrative disputes. The text includes background, Requirements, Compliance timing, an applicability statement, a cross-reference to the Polish AD (SP-0004-2005-A dated 17 May 2005), an effective date and a delegate’s signature, but it does not record any court proceedings or contested administrative actions.

What the AD explicitly contains:

• Background explanation of the motivating incident: "An accident occurred when the adjustment forked end of the rotational control rod in the elevator control system became loose, resulting in decoupling and blockage of the control system." This is a factual narrative of the safety issue, and the AD states: "The Requirements specified in this AD address the identified unsafe condition." The AD therefore records the safety rationale but not any subsequent legal steps.

What the AD does not contain regarding litigation:

• There are no references to any legal proceedings, appeals, or disputes challenging the AD's issuance or content. No case names, court decisions, or administrative adjudications are cited. The AD does not indicate that it has been the subject of disputed compliance determinations or enforcement actions that resulted in litigation.

Practical implications of the absence of litigation history in the text:

• From the document itself one can only infer that either no relevant litigation has been recorded in the instrument up to publication, or that any such litigation is not documented within this AD text. The AD does not provide post-issuance contestation information or indicate whether the AD was appealed or litigated.

• Implementers seeking litigation history will not find that information in the AD and would need to consult court or administrative records, or regulatory enforcement histories outside this text to determine whether the AD was contested. That search falls beyond the content provided here.

In short, the instrument contains no litigation history; the AD records the safety incident motivating the directive and the procedural obligations but does not document any subsequent legal contest or decision.

The AD is short but contains several points that may trip up implementers unless they read the text closely. Each "gotcha" below is grounded in the instrument's exact wording and the sequence specified in the Compliance column. These operational pitfalls concern scope, sequencing, record evidence, technical specification, and reporting obligations.

1. Part-number specificity and scope. The AD targets "the elevator control system rotational control rod, part number (PN) WM261610." Implementers must confirm the presence of PN WM261610 on their aircraft. The Applicability heading reads "PZL-104 Aeroplanes - All models," but the Requirements only identify the specified part number. A failure to check the actual PN might lead to unnecessary inspections or overlooked fittings that use a different PN or customised linkage.

2. Dual-control requirement increases inspection scope. If the aeroplane is "fitted with a dual control system, rotational control rods must be checked on both controls." This is an explicit expansion of inspection obligations but only applies when a dual-control system is installed. Operators of trainer or dual-control configurations must inspect both sides; failure to do so would mean partial compliance.

3. Sequencing: inspect before deciding other obligations. Requirement 1 is the trigger. The Compliance table reiterates that actions in Requirement 3 must be performed "following completion of Requirement 1." In practice: the operator must not skip the inspection and proceed directly to remedial work without documenting and sequencing the inspection. The AD makes compliance contingent on first completing Requirement 1.

4. Different timings for remedial actions and reporting. Requirements 3(a) and 3(b) must be completed "Before further flight," whereas Requirement 3(c) (reporting to the manufacturer) is timed as "Following completion of Requirement 1 of this Directive." The sequencing could create ambiguity: the report is not expressly required before further flight, but remedial actions are. Operators must ensure they do not interpret the reporting requirement as a precondition to flight.

5. Logbook entry as the compliance record for non-defective findings. Requirement 2 reads: "If the adjustment fork end is secured properly make an entry in the aircraft maintenance log. No further action is required." The log entry constitutes the AD's required evidence of inspection where no defect is found. Missing or inadequate log entries could create compliance gaps even if the inspection was in fact done.

6. Loose specificity about "correct security" and pal-nut technique. The AD requires "correct security of the adjustment fork end with a safety nut" and, if loose, to "Secure the adjustment fork end by way of pal-nut tightening." The AD does not specify torque figures, locking procedures, or who must perform the work; implementers must rely on existing maintenance practice, manufacturer guidance or internal standards to convert "correct security" into measurable criteria. That absence creates execution risk and possible disputes about what satisfies the AD technically.

7. Reporting destination and content unspecified. Requirement 3(c) requires reporting to the aircraft manufacturer but does not specify the content, format, timeframe (other than "following completion of Requirement 1"), or which manufacturer contact. Operators must determine how to make an adequate report to meet the AD's intent; failure to report in a way the manufacturer recognises may create an information gap.

8. Effective date vs. inspection immediacy. The AD "becomes effective on 14 June 2005" but is signed on 10 June 2005. Implementers must ensure inspections are scheduled "before further flight, after the effective date of this Directive." Misreading the effective date could lead to premature inspections or missed compliance windows.

9. No technical read-across from referenced Polish AD is included. The Note references "Polish Civil Aviation Office Airworthiness Directive (AD) Number SP-0004-2005-A dated 17 May 2005," but the CASA AD does not reproduce that instrument's technical detail. If the Polish AD contains additional procedural or technical specifics, operators will need to consult it. Assuming the CASA AD contains all technical information may result in incomplete action.

10. No explicit enforcement or appeal language: potential compliance uncertainty. The AD does not set out penalties or enforcement procedures, nor does it describe any appeal or exemption route. Operators must therefore assume the obligation is mandatory and act to avoid operational risk, but may be uncertain about formal administrative steps for resolving disputes or requesting variances.

11. Dual wording and duplication in header. The AD includes repeated headings like "AD/WILGA/4" and repeated title lines. While this is typographical rather than substantive, implementers compiling compliance paperwork should ensure they record the correct AD identifier and effective date to avoid administrative confusion.

12. The background recounts an accident that prompted the AD. The presence of an accident-related origin places urgency on compliance; operators should not treat the AD as advisory but as a mandated safety action.

Being attentive to these specific textual points,part number checks, dual-control scope, the requirement sequencing, precise timing for before-flight constraints, logbook entries and reporting mechanics,will reduce risks of non-compliance or operational disruption.

Compliance under this AD is procedural and sequenced. The AD itself lays out the minimal set of steps; the following is a practical checklist directly grounded in the AD's Requirements and Compliance statements. Each bullet maps to the AD language.

1. Identify applicability and affected aircraft. Confirm the aircraft is a PZL-104 model. The Applicability line states: "PZL-104 Aeroplanes - All models." If the aircraft is a PZL-104, proceed to step 2.

2. Confirm the component PN. Verify whether the elevator control system rotational control rod installed is part number "WM261610." The AD identifies the affected part by PN: "rotational control rod, part number (PN) WM261610." If the installed part number differs, the AD does not command action for that part; nevertheless operators should document the PN verification.

3. Schedule and perform the inspection (Requirement 1). Carry out an inspection "for correct security of the adjustment fork end with a safety nut." Timing: "Before further flight, after the effective date of this Directive." That means no aircraft subject to the AD should be dispatched for flight after 14 June 2005 without completing the inspection on the relevant PN.

4. Record inspection results in the aircraft maintenance log (Requirement 2) when the fork end is secure. If the inspector confirms "the adjustment fork end is secured properly" then make an entry in the aircraft maintenance log and no further action is required. Ensure the log entry contains sufficient identifying information to link the inspection to the AD: aircraft registration, PN WM261610 inspection, date, inspector identity, and the AD identifier (AD/WILGA/4 , 8/2005 TX) so the entry functions as compliance evidence.

5. If the fork end is not appropriately secured, perform remedial tightening (Requirement 3(a)). Tighten the adjustment fork end "by way of pal-nut tightening." Completion timing: "Before further flight, following completion of Requirement 1 of this Directive." Document the pal-nut tightening action in maintenance records, including what was done and who performed it.

6. After tightening, check and adjust control geometry (Requirement 3(b)). "Carry out a check of the adjustment of the control system and elevator deflection angles and carry out any subsequent adjustments." This must also be completed "Before further flight, following completion of Requirement 1 of this Directive." Record the check and any adjustments in the maintenance documentation, including post-adjustment deflection angles or descriptive results of the control system check.

7. Report findings to the aircraft manufacturer (Requirement 3(c)). For cases where the adjustment fork end was not appropriately secured, "Report the findings to the aircraft manufacturer." Timing: "Following completion of Requirement 1 of this Directive." Prepare a report that at minimum identifies the aircraft (registration, serial number), the affected part (PN WM261610), the nature of the deficiency (safety nut loose/not tightened), steps taken (pal-nut tightening, adjustments), and the maintenance log entries or work order references. Although the AD does not prescribe the reporting format or address to use, it is best practice to use the manufacturer's documented defect-reporting channel and to keep a copy of the report in the aircraft maintenance records.

8. For dual-control aircraft, inspect both controls. If the aircraft is "fitted with a dual control system, rotational control rods must be checked on both controls." Ensure the inspection, documentation, remedial tightening and control checks are performed for both left- and right-side control linkages and recorded separately or clearly linked in the maintenance log.

9. Ensure sequencing and "before further flight" compliance. The AD repeatedly conditions remedial actions on completion of Requirement 1 and, where required, the completion of Requirements 3(a) and 3(b) must be "before further flight." Therefore do not release the aeroplane to service until these steps are completed and documented.

10. Preserve records as evidence of compliance. The AD places reliance on maintenance log entries: make entries for inspection outcomes, remedial actions and adjustments. Where reporting to the manufacturer is required, retain copies of the report and any manufacturer responses.

11. Consult the referenced Polish AD if technical detail is required. The Note refers to "Polish Civil Aviation Office Airworthiness Directive (AD) Number SP-0004-2005-A dated 17 May 2005." Because the CASA AD does not provide torque values or precise deflection tolerances, if further technical specifics are required consult the referenced Polish AD or the manufacturer for exact procedures. Document any external guidance used to perform the actions.

12. Coordinate operational scheduling to accommodate "before further flight" constraints. Plan inspections and potential remedial work into the aircraft's operational schedule to limit unplanned downtime. Where the fork end is found loose, the aircraft will effectively be grounded until tightening and adjustments are completed and documented.

13. Use licensed maintenance personnel and appropriate parts. While the AD does not prescribe licensing or parts provenance, the actions required (tightening, adjustment) are maintenance operations typically performed by authorised personnel. Record the identity and qualifications of the person(s) performing the work in the maintenance log.

14. Follow-up monitoring. Although not required by the AD text beyond the reporting obligation, operators may wish to institute follow-up inspections at appropriate intervals to monitor for recurrence, and to retain any information provided by the manufacturer in response to the reports.

By following these steps and documenting each action in the maintenance log and manufacturer communications, operators will implement the AD's Requirements as stated. The AD provides clear sequencing and timing: inspect first, log if secure, remediate and adjust if not secure, and report where necessary, with remedial actions completed "before further flight."