AD/CESSNA 170/50 - Aileron Hinge Pin

The AD embodies several core concepts and mechanisms that determine its scope and effect. These are visible directly in the text and not inferred.

1. Applicability by model and serial number: The AD lists specific Cessna models (172N, 172P, 172Q, 172RG, R172K, F172N, F172P, FR172K and implicitly the Cessna 170/175 family heading) and enumerates serial-number ranges for each. This creates a precise, takable criterion for whether an aircraft is within scope. The Applicability table is the primary determinant of whether an aeroplane falls under the AD.

2. External technical standard: The substantive corrective action is not described within the AD; compliance is "in accordance with Cessna S.I.L. SE83-18" (Requirement). That makes the S.I.L. the operative technical document. The AD therefore functions as a regulatory direction to follow an external manufacturer instruction.

3. Compliance timing defined relative to a date and maintenance events: The compliance rule is a compound trigger: compliance is required unless the action was already completed "within 100 hours time in service after 31 January 1984 or at the next scheduled inspection for Maintenance Release issue after 31 January 1984, whichever is the later." This ties compliance to two possible events , elapsed flight hours or the next scheduled inspection at which a Maintenance Release is issued , and requires the later of them. The AD could therefore allow deferral until that later point for some aircraft.

4. Safety rationale specified briefly: The Background section gives the causal safety concern: "Possible migration and loss of the aileron hinge pin could result if the retaining split pin holes are incorrectly located." This states the mechanical failure mode the S.I.L. is designed to address.

5. Cross-reference to a foreign authority action: The AD notes "FAA AD 83-22-06 refers." The AD thus signals coordination or equivalence with an FAA airworthiness directive but does not reproduce any FAA text.

6. Administrative placement: The instrument is issued as an entry in the Schedule of Airworthiness Directives under Part 39 of the Civil Aviation Regulations 1998 (header). That placement indicates the AD’s status as a regulatory instrument within the Australian airworthiness-directive framework.

These concepts interact: the narrow serial-number applicability limits the number of aircraft that must follow the S.I.L.; the external S.I.L. determines the technical steps; and the compliance timing provides a legal window during which the action must be taken. The AD does not itself define enforcement measures, nor does it reproduce the S.I.L. content.

The AD’s Applicability table defines the directly affected parties by model and serial number. Practically, those parties are:

• Registered owners and operators of the listed Cessna models and serial numbers. The table lists serial-number ranges for multiple 172 variants (172N, 172P, 172Q, 172RG), the R172K, F172N, F172P, and FR172K. If an aircraft’s model and serial number fall within any of the listed ranges, that aircraft is subject to the AD.
• Maintenance organisations and licensed maintenance personnel responsible for carrying out work "in accordance with Cessna S.I.L. SE83-18." The AD requires action "in accordance with" the S.I.L., so approved maintenance facilities or persons authorised to implement the S.I.L. will be the agents of compliance.
• Registrars and operators who schedule Maintenance Release inspections. The Compliance trigger explicitly references "the next scheduled inspection for Maintenance Release issue after 31 January 1984," which places a consequential duty on those scheduling and performing Maintenance Release inspections to include the AD check where applicable.

Who pays: The text does not state cost allocation, but by the structure of the AD the immediate financial burden falls on the aircraft owner/operator or whoever holds responsibility for maintaining the aircraft within the regulatory framework, because they must have the S.I.L. work performed. That cost includes labour, potential replacement parts and associated grounding time required to meet the AD timeline.

Who decides: The AD delegates the technical decision about what exactly to do to Cessna S.I.L. SE83-18; the regulator decides compliance is mandatory by issuing the AD. The S.I.L. contains the prescriptive technical steps. The AD does not grant discretion to operators to select alternative methods; it prescribes compliance "in accordance with" the S.I.L.

Secondary effects on market participants: Maintenance providers that service the listed models and serial numbers will see demand to carry out the S.I.L. work. Parts suppliers may be involved if the S.I.L. requires replacements. Aircraft owners of non-listed serial numbers are not covered by this AD and are unaffected by its direct legal requirement, although they may choose to apply the same fix voluntarily; the AD does not address voluntary compliance.

Record-keeping and inspection scheduling: Because the compliance trigger references Maintenance Release inspections, owners and maintenance organisations that maintain compliance logs and schedule inspections must ensure that the AD action is timed and documented according to the rule.

Duties imposed by the AD are explicit and narrow.

Primary duties:

• For each aircraft whose model and serial number are within the Applicability table, the AD imposes a duty to carry out the action required by Cessna S.I.L. SE83-18. The AD words this as "Requirement: Action in accordance with Cessna S.I.L. SE83-18." The duty is not to a standard of care or performance generally; it is a duty to implement the S.I.L. instructions.

• The timing duty: the AD’s Compliance provision prescribes when the action must be completed. Aircraft must have the S.I.L. action completed unless it has already been done "within 100 hours time in service after 31 January 1984 or at the next scheduled inspection for Maintenance Release issue after 31 January 1984, whichever is the later." This imposes a deadline that is the later of two events: (a) completion within 100 hours time-in-service after 31 January 1984 and (b) completion at the next scheduled Maintenance Release inspection after 31 January 1984. Operators must therefore assess both time-in-service and inspection schedules to determine the operative deadline.

Rights and decision points visible in the text:

• The AD does not grant an explicit right to use alternative corrective methods; it requires action "in accordance with Cessna S.I.L. SE83-18." If an owner/operator wishes to adopt an alternative compliance method, the AD text does not provide for that; the AD itself does not state a pathway for alternative compliance. The presence of the unamended S.I.L. requirement suggests the regulator intended adherence to the manufacturer procedure.

• The AD does not entitle an operator to compensation or reimbursement for costs arising from compliance. No cost-shifting mechanism appears in the text.

• The AD refers to an FAA AD (FAA AD 83-22-06) in the Note; that does not create rights within the Australian AD text but signals that operator information or guidance may be available through the FAA document. The AD itself does not incorporate the FAA AD beyond the referral.

Prescriptive vs discretionary elements:

• Prescriptive: The requirement to follow the S.I.L. is prescriptive. The AD prescribes a defined action (the S.I.L.) and sets a compliance timing rule.
• Non-prescriptive: The AD does not set out procedural discretion for maintenance organisations (for example, it does not specify whether a licensed engineer or an authorised repair station must perform the action), nor does it specify follow-up inspections, reporting obligations, or certification steps beyond the maintenance/inspection scheduling trigger.

Documentation and maintenance-release process:

• The AD’s timing reference to the "Maintenance Release issue" implies that the Maintenance Release inspection schedule is an operational lever for compliance. Maintenance organisations that issue Maintenance Releases must incorporate the AD action into that inspection where it is the later trigger. The AD does not specify how the Maintenance Release must be annotated after completing the S.I.L. action.

In sum, the AD creates a straight-line duty: operators of the listed serial-numbered aircraft must have the Cessna S.I.L. SE83-18 action carried out by the stated timing. The AD leaves technical detail, procedural steps and the mechanics of implementation to the S.I.L. and existing maintenance-release processes.

The AD text itself does not set out penalties, fines, or an enforcement procedure within the four corners of the document. The instrument’s content is limited to identification of affected aircraft, the requirement to act "in accordance with Cessna S.I.L. SE83-18", and the compliance timing. No specific enforcement mechanism, sanction, or administrative remedy is stated in the AD text provided.

What the text does allow the reader to infer without asserting external law is:

• The AD is issued as an entry under the Schedule of Airworthiness Directives within Part 39 of the Civil Aviation Regulations 1998 (header). That structural placement indicates the AD functions as a regulatory directive within the airworthiness-directive regime. The AD itself, however, contains no standalone penalty clause or enforcement procedures.

• Because the AD prescribes a mandatory action and includes a compliance timeframe, practical enforcement will depend on the surrounding regulatory framework and the compliance surveillance practices of the Civil Aviation Safety Authority or relevant regulatory body. The AD text does not describe those surveillance or sanction mechanisms.

Implementation risk and compliance monitoring (text-grounded observations):

• The AD’s enforcement status is implied by its mandatory language, but the document provides no compliance-reporting form, no requirement to notify the regulator upon completion, and no conditions for granting alternative methods of compliance. That absence means that, from the AD alone, there is no specified administrative pathway for documenting compliance to the regulator in this instrument.

• The AD’s referral to an external S.I.L. creates a practical enforcement point: a maintenance organisation or an inspector can verify completion by checking maintenance records and entries that document adherence to Cessna S.I.L. SE83-18 and the date/inspection entry showing the work was completed within the specified compliance window. The AD does not state this expressly; it follows from the requirement structure.

Limits on what can be said from the text:

• The AD does not identify who will initiate enforcement activity, how often compliance will be audited, what evidence will be accepted, or what penalties (if any) will attach to non-compliance. These matters are outside the text supplied.

Where the AD does provide cross-reference context that may be relevant to enforcement:

• The AD notes "FAA AD 83-22-06 refers." That cross-reference may be used by regulators, inspectors or affected operators to find corroborating technical direction or to check parallel FAA actions, but the AD itself does not make the FAA AD operative in Australia; it simply notes the FAA document as a reference.

In practical terms, the AD’s absence of stated penalties shifts emphasis to record-keeping and demonstrable compliance with the S.I.L. Operators and maintenance organisations that are subject to broader regulatory oversight will need to rely on inspection records and maintenance-release documentation to demonstrate compliance when inspected, given the AD’s prescriptive requirement and its specific compliance timing.

The AD’s header places it within a particular statutory framework: it is an item in the "SCHEDULE OF AIRWORTHINESS DIRECTIVES" under the Civil Aviation Regulations 1998, Part 39. The text thus sits inside an administrative regime of airworthiness directives rather than being a freestanding statutory provision. The AD itself does not reproduce or restate Part 39’s provisions, nor does it quote other regulations; it uses the Part 39 schedule as its publication vehicle.

Direct, textually explicit interactions from the AD:

• The AD references the Civil Aviation Regulations 1998, Part 39 by way of header only. It does not cite any other sections of the Civil Aviation Regulations or other statutes.

• The AD explicitly references an FAA action: "Note: FAA AD 83-22-06 refers." The AD does not state how or whether the FAA AD has legal effect in Australia; it simply records the FAA AD as a point of reference. The presence of that note indicates there is at least one foreign counterpart action addressing the same technical issue, but the AD does not incorporate the FAA AD’s text or provisions.

Implications for interaction with maintenance and certification processes:

• The Compliance provision ties the AD to maintenance-release scheduling ("next scheduled inspection for Maintenance Release issue after 31 January 1984"). That creates an operational interaction between the AD and maintenance documentation and certification practices (Maintenance Release issuance), although the AD does not specify the content of those maintenance or certification rules. Operators and maintenance organisations must therefore integrate the AD action into their existing maintenance/airworthiness certification processes,an interaction that will be governed by the maintenance regulations and procedures that exist outside the text.

• Because the AD mandates performance "in accordance with Cessna S.I.L. SE83-18," there is an interaction between the regulatory instrument and manufacturer technical documentation. The AD does not explicitly state whether the S.I.L. is incorporated by reference into the regulation, but it binds operators to comply with it. That creates an operational dependency: compliance with the AD requires access to and adherence to the manufacturer's instruction letter.

No textual cross-references to other Commonwealth, state or territory laws, or to international treaties, are included beyond the FAA note. Therefore:

• Any interplay between this AD and other legal regimes, such as broader civil aviation offences, registration requirements, air operator certificates, or contractual warranties, is not stated in this AD text. Those interactions exist in the surrounding legal and operational environment but are not specified here.

Limitations arising from the AD’s form:

• Because the AD delegates technical detail to an external S.I.L., the AD’s legal interaction with other rules will depend on how regulators and courts treat a regulatory instrument that requires compliance with an external manufacturer's document. The AD text itself does not specify whether compliance with the S.I.L. is the sole acceptable method, nor whether alternative methods may be approved under other parts of the regulatory framework.

In sum, the AD is an instrument published under Part 39 and it references an FAA AD. Its operational interactions are with maintenance release procedures and the manufacturer's S.I.L., but the AD text does not elaborate statutory cross-links or enforcement relationships with other legislation.

The AD text contains limited chronological markers that allow only a modest, text-grounded reconstruction of its issuance context.

Identifying markers in the text:

• The AD identifier includes "1/84" at the end of the title line "AD/CESSNA 170/50 Aileron Hinge Pin 1/84." That suffix functions commonly as a dating convention in airworthiness directives (the source text uses it), indicating the AD’s series or issuance year in the AD numbering system. The document does not state an explicit date of issue within the body beyond the compliance reference date.

• The Compliance provision uses the fixed calendar date "31 January 1984" as the baseline for calculation of the 100-hour time-in-service compliance window and as the date from which the next scheduled Maintenance Release inspection is measured. The inclusion of that date confirms that the compliance window was intended to operate with reference to that 31 January 1984 milestone.

No textual record of subsequent amendments:

• The AD text, as supplied, does not include an amendment log, revocation statement, supersession note or later serial-numbered amendment. It neither lists previous ADs that it replaces nor subsequent ADs that modify it. There is no explicit "amendment history" section in the provided text.

• The AD does include the note "FAA AD 83-22-06 refers." That may provide a clue to contemporaneous foreign action (FAA AD 83-22-06) relevant to the timeframe indicated by the 1983/1984 numbering. The AD text does not say whether the FAA AD preceded or followed this AD, nor does it claim to be harmonised or derived from the FAA AD.

Consequences of the absence of recorded amendments in the text supplied:

• Because the AD as supplied does not record subsequent amendments, one cannot from this text alone determine whether later amendments, extensions, supersessions or cancellations exist. Any such alterations would appear in later AD entries, amendment bulletins, or databases maintained by the regulator, none of which are included in the supplied text.

• The AD’s compliance timing anchored to 31 January 1984 implies that the AD was current or operative around that date. The AD’s identifier including "1/84" further supports that inference, but the AD does not give a precise issuance date or record any later administrative history.

What the AD does show, textually, is a single directive specifying applicability, requirement and compliance timing with reference to early 1984. The supplied document contains no subsequent amendment notes or version history.

The text supplied contains no references to litigation, legal proceedings, disputes, case names, or judicial consideration. It does not mention any appeals, administrative reviews, prosecutions, or court orders connected to AD/CESSNA 170/50. There are no citations to judicial decisions, no mention of an appeal route, and no record of contested enforcement within the AD.

What can be stated strictly from the document:

• The AD itself does not record any litigation history or challenge to the directive in the supplied text. It contains the technical requirement, the applicability listing, and the compliance scheduling, with no commentary on contested legal outcomes.

Implications for users of this AD:

• If an operator or maintenance organisation needs to understand whether this AD has been the subject of litigation, or whether court decisions interpret its scope, requirements, or enforcement, that information is not present in the AD text and would need to be sought in external legal databases, regulatory records, or court archives. The AD text does not provide such references.

• For compliance planning, absence of litigation history in the AD does not affect the duty it imposes; it is a mandatory directive within the Schedule of Airworthiness Directives. However, legal uncertainty about interpretation, if any, would require recourse to broader legal and regulatory resources, which are outside the supplied document.

Therefore, strictly on the basis of the supplied text, there is no litigation history to report.

The AD’s brevity and reliance on external documents and maintenance processes creates a number of practical pitfalls that are evident from the text. These are concrete operational risks and compliance traps, stated strictly from what the AD requires.

1. Narrow serial-number applicability requires careful verification.

• The Applicability table lists multiple models and extensive serial-number ranges, sometimes with fragmented ranges (e.g. many discrete ranges for 172P and 172Q). Operators must check an aircraft’s exact serial number against the listed ranges to determine whether the AD applies. Misreading ranges or mistyping a serial number could lead to incorrect compliance assessments.

2. The operative technical instruction is external.

• The Requirement is "Action in accordance with Cessna S.I.L. SE83-18." The S.I.L. is not reproduced. Operators and maintenance organisations must obtain the S.I.L. to know what exact work is required. If the S.I.L. is difficult to access, ambiguous, or has multiple revisions, the AD gives no internal guidance on which revision applies. The AD does not incorporate the S.I.L. textually; it simply binds operators to the S.I.L.’s content. That external dependency is a compliance friction point.

3. Dual-trigger timing with "whichever is the later" can be misapplied.

• The Compliance clause offers two potential timing triggers: within 100 hours time-in-service after 31 January 1984, or at the next scheduled inspection for Maintenance Release issue after 31 January 1984, whichever is the later. Operators must calculate both triggers correctly and choose the later. Errors in calculating time-in-service hours or the scheduling date of the Maintenance Release inspection can result in premature or late action, with potential regulatory consequences not specified in the AD but relevant in practice.

4. Retrospective or pre-existing compliance ambiguity.

• The Compliance clause contains the phrase "Unless already accomplished within 100 hours time in service after 31 January 1984 or at the next scheduled inspection for Maintenance Release issue after 31 January 1984," which means that if the S.I.L. action was already completed within those windows, no further action is required. Determining whether a past maintenance action is equivalent to the S.I.L. action requires record evidence. Maintenance records must show the completion date and work scope to demonstrate past compliance; incomplete records are a risk.

5. No procedural guidance for documenting compliance in the AD itself.

• The AD does not state how to annotate completion on maintenance release documents, how to present evidence to an inspector, or whether a specific entry form is required. This leaves room for inconsistent record-keeping that may create disputes during audits or inspections.

6. The safety problem described is mechanical and specific.

• The Background identifies "Possible migration and loss of the aileron hinge pin could result if the retaining split pin holes are incorrectly located." This points to a specific potential failure mode. Operators and inspectors should note that the AD addresses hole location and retaining split pin security; failure to focus on these specifics when following the S.I.L. could leave the safety risk partially unaddressed.

7. Cross-reference to FAA AD creates expectation of additional material.

• The Note "FAA AD 83-22-06 refers" suggests parallel FAA guidance exists. Operators may assume the FAA AD contains extra procedural or compliance guidance, but the Australian AD does not say the FAA AD is binding in Australia. Reliance on the FAA AD without consulting the Cessna S.I.L. could lead to non-conformance with the AD’s explicit requirement.

8. The AD does not state who must perform the work.

• The AD requires adherence to the S.I.L. but does not specify licensing, certification or authorised personnel requirements for performing the S.I.L. action. Practical maintenance regulation outside the AD will determine permitted performers, but the AD itself provides no clarity on this point, which may create interpretive confusion for operators seeking to outsource work.

9. Potential for overlapping or fragmented compliance across fleet.

• An operator managing multiple affected aircraft must track each aircraft’s serial number, time-in-service hours, and maintenance release schedules individually. Aggregation errors could lead to non-compliance for a subset of aircraft.

10. No mention of follow-up inspections or monitoring frequency.

• The AD addresses an initial corrective or inspection action but does not state any follow-up inspection schedule to monitor whether hinge pin migration recurs. If the S.I.L. also includes follow-up steps, that will be in the S.I.L.; absent that, the AD gives no guidance on long-term monitoring.

Each of these "gotchas" arises directly from the AD’s textual structure: precise serial-number applicability, external technical instruction, compound compliance timing, and lack of procedural detail within the AD itself.

The AD sets a clear but procedural compliance requirement. The following steps are a directly actionable, text-grounded route to compliance, using only the AD content as the authority.

1. Determine applicability by model and serial number.

• Consult the AD’s Applicability table and verify the aircraft’s model and serial number exactly against the ranges listed for each model (172N, 172P, 172Q, 172RG, R172K, F172N, F172P, FR172K). If the aircraft’s serial number appears in any listed range, the AD applies.

2. Obtain Cessna S.I.L. SE83-18.

• The AD’s Requirement is explicit: "Action in accordance with Cessna S.I.L. SE83-18." Operators and maintenance providers must obtain the referenced S.I.L. to know the specific inspection and corrective steps. The AD does not reproduce the S.I.L., so compliance cannot be completed without it.

3. Determine the applicable compliance deadline.

• Use the Compliance clause to calculate the operative deadline. Two alternative means of satisfying the AD are identified: a) If the S.I.L. action was already performed within 100 hours time in service after 31 January 1984, document that completion; or b) If the S.I.L. action is to be performed at the next scheduled Maintenance Release inspection after 31 January 1984, ensure it is completed at that inspection.
• Whichever of those two events is later becomes the operative compliance deadline ("whichever is the later"). Therefore, compute both: (i) whether an action has already been done within 100 hours after 31 January 1984; and (ii) when the next scheduled inspection for Maintenance Release issue after 31 January 1984 is scheduled for the specific aircraft.

4. Plan and schedule the work.

• If the action has not already been done within the specified window, schedule the S.I.L. procedure to be performed no later than the applicable deadline determined above. Because the AD ties one compliance route to a Maintenance Release inspection, coordinate with the maintenance organisation issuing the Maintenance Release so the S.I.L. action is included at that inspection if it is the later trigger.

5. Execute the S.I.L. instructions.

• Ensure that the maintenance organisation or personnel performing the work follow Cessna S.I.L. SE83-18 exactly as written. The AD requires action "in accordance with" that S.I.L.; the AD does not authorise substitution in its text.

6. Record and document completion.

• Make an explicit maintenance log entry documenting:
  • The AD identifier (AD/CESSNA 170/50 Aileron Hinge Pin 1/84).
  • The aircraft model and serial number.
  • Reference to Cessna S.I.L. SE83-18 and the S.I.L. revision used.
  • Date and hours time in service at which the work was completed.
  • The Maintenance Release entry if the work was performed in conjunction with the scheduled Maintenance Release inspection.
  • The name, signature and licence/authorisation of the person or organisation that performed the work.
• The AD’s Compliance provision relies upon demonstrable completion within the defined windows; documented evidence is the practical means of proving compliance.

7. Cross-check FAA reference where helpful.

• The AD notes "FAA AD 83-22-06 refers." If additional clarifying material is needed, the FAA AD may be a relevant reference, but do not substitute the FAA AD for Cessna S.I.L. SE83-18, because the Australian AD explicitly requires action per the S.I.L.

8. Retrospective equivalence determination.

• If an operator believes an earlier action completed prior to the AD date or within the prescribed 100 hours window satisfies the S.I.L. requirements, maintain documentary evidence specifying scope, method and results of that earlier work. The AD’s Compliance clause recognises prior completion within the specified windows as satisfying the AD, but documentation will be necessary to demonstrate that the earlier work matched the S.I.L. action.

9. Keep records for audit.

• Because the AD does not specify a reporting requirement or form, retain contemporaneous records in the aircraft’s maintenance logbook and any regulatory records as required by the operator’s broader airworthiness obligations.

10. If uncertainty about scope or technical steps arises, seek the S.I.L. clarification from the manufacturer or the regulator.

• The AD itself does not grant discretion to deviate from the S.I.L. and gives no alternative method-of-compliance. If a maintenance organisation believes an alternative method is necessary, the AD provides no process in its text for approval of alternatives. Consequently, seek formal guidance through the manufacturer or the Civil Aviation Safety Authority (or the applicable regulatory authority) to obtain an approved alternative procedure. The AD text does not provide that route itself; it only requires the S.I.L.

By following these steps , verify applicability, obtain the S.I.L., determine the later compliance trigger, schedule and perform the S.I.L. work, and document completion , an operator or maintenance organisation can implement the AD’s obligations as stated in the document.