The AD operates by reference and by a small set of concrete obligations framed around aircraft records and the applicability of specified FAA ADs. The principal concepts in the text are these.

Applicability: The instrument applies to “All Univair Aircraft Corporation Stinson Model 108 series aircraft” (Applicability). That phrase defines the population of aircraft to which the requirements attach.

Reference to State‑of‑Design ADs: Rather than restating the technical corrective measures, CASA uses the FAA’s ADs as the substantive source of required actions. Requirement 1 asks the responsible person to determine “from Aircraft Records if the requirements of the Federal Aviation Administration ... Airworthiness Directives, as in force at the time of issue of this AD, specified in Table 1 of this AD have been carried out.” That wording imports the FAA ADs “as in force at the time of issue,” creating a temporal snapshot of the FAA ADs that CASA is enforcing through this instrument.

Two‑step duty structure: The AD splits the compliance obligation into (1) an initial records determination and (2) remedial action where the FAA AD is applicable and not already complied with. Requirement 2 is a clear, conditional obligation: “If it is determined that an FAA AD listed in Table 1 ... is applicable and has not been previously complied with, then perform the actions required by that AD.”

Table 1 content: The Table lists four FAA ADs (by number and subject), each of which is the technical directive that CASA requires to be verified and, if necessary, implemented. The subjects are varied: ash tray modification/placard, wing fabric inspection/rectification, fuel drip strip installation, and wheel ski rigging. The AD does not reproduce the technical steps for those items; it requires compliance with the corresponding FAA AD documents.

Timing and linkage to certification: The compliance clause ties fulfilment to CofA status. If no CofA yet issued, compliance is required before issue; if a CofA has been issued, compliance is due within 60 days of the AD’s commencement date (Compliance). The AD’s commencement date is stated explicitly: 31 August 2018.

Scope limits: The Background expressly notes that the FAA ADs listed are once‑only actions with compliance dates already passed, that CASA determined they “may be applicable to recently registered Stinson model 108 aircraft,” and that “due to date of aircraft manufacture or aircraft configuration and modification status, some of the ADs listed in Table 1 will not be applicable to some aircraft” (Background). That acknowledges heterogeneity across aircraft in the applicability of each FAA AD.

Record focus: The initial obligation is to inspect aircraft records rather than to perform a mandatory physical inspection in every case. That emphasis places documentary evidence at the front of compliance.

Delegation and issuance: The document is signed by “Pieter van Dijk, Delegate of the Civil Aviation Safety Authority” and dated 21 August 2018, which grounds the directive in CASA’s delegated authorising function (signature block). The AD number and commencement notation (AD/STINSON 108/1; 17/2018) are administrative identifiers.

Taken together, the AD is a narrow, targeted instrument: it imports specific foreign state‑of‑design directives by reference, requires owners/operators to verify compliance from records and to carry out the foreign ADs where applicable, and sets short deadlines tied to CofA issuance and an explicit commencement date.

The AD names the affected equipment class and thus identifies the primary persons and entities affected. The explicit applicability line reads “All Univair Aircraft Corporation Stinson Model 108 series aircraft” (Applicability). From that single specification the following categories of parties are implicated by the AD’s requirements and structure.

Registered owners and operators of Stinson Model 108 series aircraft on the Australian Aircraft Register. The Background states that the Stinson 108 type has been on the Australian register since 1987 and that “there are currently 12 aircraft of this type on the register with the majority having been registered in 1994/95.” The directive is issued “to ensure that compliance with these AD’s has been accomplished for aircraft imported into Australia,” which targets those aircraft that have been imported and subsequently registered. Owners and operators bear the primary legal responsibility to have and maintain aircraft records and to undertake the works required by applicable ADs.

Applicants for a certificate of airworthiness (CofA) for an affected aircraft. The Compliance provision conditions some obligations on CofA status: if a CofA “has not been issued for the aircraft - accomplish before the issue of the CofA.” That imposes a pre‑certification hurdle on new CofA applicants for affected aircraft.

Holders of existing CofAs for affected aircraft. Where a CofA has been issued, compliance is required “within 60 days after the commencement date of this Directive.” Therefore existing certificate holders must execute the records review and, if applicable, the corrective actions within that 60‑day window.

Maintenance organisations and certificated maintenance personnel. The AD’s requirements step from a records check to “perform the actions required by that AD” if an FAA AD listed in Table 1 applies and has not been complied with. Performing those AD actions will typically involve maintenance organisations, engineers and certificated personnel capable of implementing modifications, inspections, installations or placard placements described in the FAA ADs.

Importers and earlier custodians of aircraft records. The AD refers to verifying compliance “from Aircraft Records,” making the quality and completeness of historical maintenance and modification records a central issue. Parties who imported the aircraft or who held custody of records at importation may be involved to the extent historical records must be tracked down.

CASA as regulator. CASA, through the delegated signatory, is the issuing authority and thus directs the compliance obligations; the AD is framed to achieve an outcome,assurance that the listed FAA ADs have been complied with for Australian registered/imported examples.

Others potentially affected include insurers and purchasers of Stinson 108 aircraft: while not named in the AD text, the AD’s obligations affect airworthiness status and CofA eligibility, which have commercial consequences for transfer, insurance and operations. The AD does not spell out duties for insurers or purchasers, but those market actors will be practically affected insofar as compliance influences legal airworthiness.

Finally, because the instrument references FAA ADs “as in force at the time of issue of this AD,” anyone tasked with determining applicability must consult the historical FAA AD versions current at CASA’s issue date, which brings in record‑keepers capable of locating and interpreting those FAA documents.

The AD sets a short list of duties and leaves other rights and review mechanisms unstated in the text. The express duties and the limited statements about applicability and compliance windows are the primary legal content.

Duties

• Records determination duty: Responsible persons must “determine from Aircraft Records if the requirements of the Federal Aviation Administration ... Airworthiness Directives, as in force at the time of issue of this AD, specified in Table 1 of this AD have been carried out” (Requirement 1). That is an affirmative, document‑based inquiry duty; it does not by its terms require a physical inspection unless that inspection is needed to resolve the records inquiry.

• Remedial action duty: If, after the records determination, “it is determined that an FAA AD listed in Table 1 ... is applicable and has not been previously complied with, then perform the actions required by that AD” (Requirement 2). This creates a conditional obligation to implement the substantive technical measures in the referenced FAA AD.

• Timing duties: Compliance timing is conditional on CofA status: comply before issuing a CofA if none exists; otherwise comply within 60 days of the AD’s commencement date (Compliance). The AD commences on 31 August 2018.

• Documentation and traceability implied duty: While not stated as a separate clause, the AD’s reliance on aircraft records implies that those records must be available and sufficiently detailed to demonstrate whether the FAA ADs have been complied with. The AD directs action “from Aircraft Records,” placing evidentiary weight on recorded entries, placards or modification documentation.

Rights and unstated procedural elements

• No express reservation for appeal or review is contained in the AD text. The AD does not set out an internal right of review, an appeal route or an exemption mechanism in its body. The Background observes that “CASA acknowledges ... some of the ADs listed in Table 1 will not be applicable to some aircraft,” which indicates a recognition of non‑applicability rather than an express process to claim an exemption.

• The AD references FAA ADs “as in force at the time of issue of this AD.” That phrasing creates a definitional right for affected parties to consult the snapshot of each FAA AD effective at CASA’s issue date to determine required works, rather than being obliged to comply with later FAA AD amendments. The AD therefore defines the reference point for technical obligations.

• The AD does not state compensatory rights, cost recovery mechanisms, or transitional relief beyond the two timing alternatives tied to CofA status.

Practical effects of these duties

• The records determination duty concentrates agency on whoever controls an aircraft’s maintenance records. That person must be able to interpret the FAA AD text applicable at the snapshot time and make a binary assessment of applicability and prior compliance.

• The remedial action duty creates a downstream obligation to carry out the FAA ADs’ specified works, which may include modifications, installations, inspections and placard installations. The AD imports technical content by reference rather than reproducing it.

• The timing duty forces near‑term action: the commencement date and the 60‑day window are short, and for pending CofA applications the requirement is pre‑issuance.

Because the AD is concise and narrowly drafted, many procedural issues that practitioners might otherwise expect are simply left unstated. There is no express process described in the AD text for disputing applicability, seeking exemptions, or documenting completion beyond the instruction to “determine from Aircraft Records” and to “perform the actions required by that AD.”

The text of this AD does not include express penalty clauses, monetary fines, enforcement processes or administrative sanctions. The instrument sets compliance obligations and deadlines but does not specify the consequences for non‑compliance within the words reproduced.

What the AD does say that bears on enforcement is limited and procedural: it prescribes that, where a CofA “has not been issued for the aircraft - accomplish before the issue of the CofA,” and where a CofA has been issued the required actions must occur “within 60 days after the commencement date of this Directive” (Compliance). Those provisions create scheduling constraints that tie directly into certification processes.

Because the AD does not itself specify penalties or enforcement mechanisms, the following are directly supportable, source‑grounded observations rather than assertions about what absent clauses mean:

• The AD links compliance to CofA issuance timing, creating a nexus between the AD’s requirements and the administrative act of issuing a certificate of airworthiness. The AD therefore places compliance obligations in the path of certification, which is the only enforcement‑adjacent mechanism explicitly mentioned in the text.

• The AD is framed as a CASA directive, signed by the CASA delegate, which identifies the issuing authority and implies that the directive is part of CASA’s regulatory toolkit; however, the instrument itself does not set out the broader enforcement toolkit CASA may use elsewhere in law or policy to secure compliance. The AD does not state fines, licence suspensions, or mandatory inspections as consequences.

• The AD’s Background states its purpose is “to ensure that compliance with these AD’s has been accomplished for aircraft imported into Australia.” That aim suggests CASA’s interest in ensuring airworthiness documentation and compliance, but the AD leaves details of enforcement and follow‑up out of its text.

Given the absence of specified penalties or procedures for enforcement in the AD text, readers must treat this instrument as establishing obligations and deadlines but not prescribing, in this text, the sanctions for failing to comply. Any formal enforcement, sanctioning or follow‑up procedures would either arise from other CASA instruments, regulatory frameworks, or administrative practice; those are not contained within the provided text and therefore are not described here.

The AD explicitly interacts with foreign state‑of‑design airworthiness directives and with Australian certification practice. The instrument imports FAA ADs by reference and links compliance to Australian CofA issuance, thereby creating a cross‑jurisdictional compliance dependency.

Reference to FAA ADs as substantive law: Requirement 1 directs the responsible person to determine whether the “requirements of the Federal Aviation Administration ... Airworthiness Directives, as in force at the time of issue of this AD, specified in Table 1 of this AD have been carried out.” By doing so the CASA AD effectively incorporates the content and obligations of those FAA ADs into the Australian regulatory regime for the affected aircraft, at least as to the snapshot effective at the issue date. The AD therefore establishes a direct interface between Australian regulatory compliance and FAA state‑of‑design directives.

Temporal snapshot: The AD imports the FAA ADs “as in force at the time of issue of this AD.” That narrows the cross‑jurisdictional interaction to a specific temporal version of each FAA AD rather than necessarily requiring compliance with later FAA AD amendments. Practically, this requires affected parties to consult archival or historical FAA AD texts current at CASA’s issue date to determine the substantive obligations they must meet under the CASA AD.

Certification law interaction: The Compliance clause conditions obligations on the status of an Australian certificate of airworthiness: if no CofA is issued, the works must be accomplished “before the issue of the CofA”; if a CofA exists, compliance is required within 60 days of the AD’s commencement date. This creates a legal interaction between the CASA AD and the CofA issuance process. While the AD text does not state explicit CofA denial powers or procedures, the phrasing makes CofA issuance and the AD obligations interdependent in practice.

Incomplete reproduction of technical requirements: The AD does not reproduce the FAA ADs’ technical provisions. Consequently, the substantive technical compliance obligations remain located within the FAA AD documents referenced. Affected parties must reconcile the CASA AD’s directive with those external documents to understand the full technical content of the duty, in effect creating a legal dependency across jurisdictions where the Australian instrument refers to foreign regulatory texts for specifics.

Applicability to imported aircraft: The Background identifies the AD’s purpose as ensuring compliance “for aircraft imported into Australia.” That creates an explicit interface with customs, importation and registration processes insofar as imported aircraft need demonstrable compliance to secure CofAs and to meet the AD’s timing requirements.

No mention of other Australian statutes or regulations: The AD text does not cite specific Australian statutes, regulations or penalty provisions. It is an administrative directive that prescribes duties; any interaction with criminal law, administrative penalties, or other statutory frameworks is not set out in the AD itself and therefore not described here.

In short, the AD interacts principally by importing FAA AD content as the substantive technical standard and by tying compliance to the Australian CofA process. It does not reproduce or restate the FAA ADs; it requires affected parties to consult those external documents as they stood at CASA’s issue date.

The AD itself is short and contains its own issuance and commencement metadata but does not record any amendments within the text provided. The relevant contained dates and identifiers in the instrument are:

• Document identifiers: AD/STINSON 108/1 and 17/2018 appear as the AD number and administrative year identifiers printed in the heading.

• Issue date: The AD is dated and signed “21 August 2018” by “Pieter van Dijk, Delegate of the Civil Aviation Safety Authority.”

• Commencement date: The AD states “This AD commences on 31 August 2018.” The compliance window for certificated aircraft is defined relative to that commencement date.

• No subsequent amendments or revocations are recorded in the provided text. There is no text indicating that this AD amends, supersedes or is superseded by any earlier CASA instrument.

• No variations: The AD does not include clause headings such as “variation,” “revocation,” or “transitional” that might indicate prior amending history within the instrument.

Because the AD makes compliance contingent on FAA ADs “as in force at the time of issue of this AD,” the AD de facto locks in that snapshot on 21 August 2018 (the signed date) for interpretive purposes, and it sets the commencement date to 31 August 2018. Any later CASA amendment to the AD or revocation would need to be reflected in a subsequent instrument; no such instrument is included in the provided material.

Practitioners should therefore treat this document as a single, dated directive with the metadata above and no recorded internal amendments. If amendments or revocations exist elsewhere, they are not reproduced in the text provided and thus cannot be reported here.

The provided AD text includes no litigation history, references to judicial review or judicial decisions, nor any citation to cases. It is a stand‑alone CASA airworthiness directive and the document does not record any legal challenges, appeals or court proceedings concerning it.

The AD’s Background and text do not identify any disputed interpretations or prior legal determinations that would form a litigation history. Likewise, there are no notes of interim injunctions, declarations, or litigation outcomes attached to the AD.

Given that the text contains only the directive itself, its administrative metadata and explanatory background, there is nothing in the provided material to indicate that the AD has been the subject of court proceedings or that any litigation has interpreted its scope. For litigation history beyond the material reproduced here, parties would need to consult external legal databases or CASA records; those materials are not included in the AD text provided and therefore are not summarised here.

The AD contains several features that create practical traps for non‑specialists or for operations with incomplete records. These are concrete issues that arise directly from the AD language and the table of referenced FAA ADs.

Snapshot of FAA ADs: The AD requires determination of compliance with FAA ADs “as in force at the time of issue of this AD.” That means the technical obligations are those versions of the FAA ADs current at CASA’s issue date. Practically, affected parties must locate and consult the historical FAA AD documents as they stood at the CASA issue date to determine what actions were required. Treating later FAA AD amendments as relevant would be incorrect under the AD’s wording; conversely, failing to consult the correct historical version risks a false negative or false positive on compliance.

Once‑only items with lapsed compliance dates: The Background points out that the FAA ADs listed “require once‑only actions for which the compliance date and/or period has passed.” In other words, the FAA ADs typically imposed one‑off fixes whose compliance windows have long expired. The risk here is that older imported aircraft may not have the extant documentary proof on the Australian register to show those once‑only actions were performed prior to importation, yet CASA still requires verification and remediation where the FAA ADs apply and have not been complied with.

Record quality and availability: The initial obligation is to “determine from Aircraft Records” whether specified FAA ADs have been carried out. For aircraft with manufacturing dates in the decades prior to the AD, or for aircraft that changed custodians or were imported with incomplete paperwork, sufficient records may not exist. Missing or ambiguous documentation will then trigger the conditional remedial duty, potentially requiring modification work or inspections.

Applicability varies by manufacture and configuration: The AD itself acknowledges that “due to date of aircraft manufacture or aircraft configuration and modification status, some of the ADs listed in Table 1 will not be applicable to some aircraft.” That creates a factual determination exercise; owners must be prepared to justify non‑applicability based on traceable evidence of manufacture date, configuration or prior modifications.

Multiple technical interventions: Table 1 items range across different systems and interventions: ashtray modification or placard, wing fabric inspection and rectification, fuel drip strip installation, and wheel ski rigging. Operators must be ready to engage diverse maintenance activities, possibly requiring different maintenance skills, parts or subcontractors.

Timing constraints: The AD’s commencement date is 31 August 2018, and a 60‑day compliance window applies to aircraft with an existing CofA. The issued date is 21 August 2018, giving a tight lead‑in between issue and commencement. For CofA applicants, the AD requires actions “before the issue of the CofA,” which can delay certification if records are inadequate or remedial work is necessary.

Imported aircraft focus: The AD is phrased to ensure compliance for aircraft imported into Australia. If an aircraft was imported and registered with incomplete evidence of compliance with the listed FAA ADs, CASA’s requirement effectively forces retrospective compliance work at the cost of the registrant or owner.

No procedural dispute mechanism in the text: The AD does not set out an explicit mechanism for contesting applicability, seeking an exemption or applying for an alternative means of compliance. Practitioners should be aware that the AD’s silence on procedure means that claims of non‑applicability must be demonstrably documented in the aircraft records relied upon under Requirement 1.

Evidence standard: Since the AD requires a determination “from Aircraft Records,” the standard of proof for prior compliance is documentary. Verbal assurances or oral histories without record entries will be insufficient for the initial determination.

In sum, the practical “gotchas” are about historical records, the need to consult the correct historical FAA AD versions, the once‑only nature of the FAA actions, the diversity of remedial work that might be required, and the absence of procedural text within the AD for contesting or seeking variation. Each of these stems directly from the AD’s language and the Table 1 contents.

The AD prescribes a clear two‑step compliance pathway; compliance will require documentary work and, where necessary, physical maintenance actions drawn from the FAA ADs listed in Table 1. The following are source‑grounded, actionable steps to satisfy the AD’s requirements.

1. Identify affected aircraft and confirm application. Start from the AD’s applicability: verify whether the aircraft is a “Univair Aircraft Corporation Stinson Model 108 series aircraft.” If so, the AD applies.

2. Establish the relevant FAA AD versions. The AD requires determination “from Aircraft Records if the requirements of the Federal Aviation Administration ... Airworthiness Directives, as in force at the time of issue of this AD, specified in Table 1 ... have been carried out.” Therefore obtain the FAA AD documents corresponding to each FAA AD number listed in Table 1 (FAA AD 47‑50‑11; FAA AD 49‑16‑02; FAA AD 50‑25‑01; FAA AD 54‑02‑02) as they existed at the time CASA issued this AD. The AD’s signed date is 21 August 2018 and it “commences on 31 August 2018”; the instruction is to consult the FAA ADs “as in force at the time of issue of this AD,” so use the versions effective at that issue date.

3. Conduct a records review. Following Requirement 1, review the aircraft’s maintenance, modification and certification records to determine whether the FAA AD requirements have been complied with. Document each records check with a dated entry that identifies the FAA AD consulted (by number and version), the determinations made about applicability, and the documentary evidence supporting any conclusion that the AD has been complied with. Because the AD specifies “determine from Aircraft Records,” recorded proof of modification, placard fitment, inspection entries or maintenance release paperwork will be dispositive for the initial determination.

4. Assess applicability for each FAA AD. For each FAA AD listed in Table 1, make a factual determination whether that FAA AD is applicable to the aircraft in its present configuration and with its manufacture date. The AD itself recognises that “some of the ADs listed in Table 1 will not be applicable to some aircraft.” Record the factual basis for any non‑applicability finding (for example, manufacturing serial number, absence of the relevant equipment, or configuration differences).

5. Where an FAA AD is applicable and not complied with, perform the required actions. Requirement 2 states that if a listed FAA AD “is applicable and has not been previously complied with, then perform the actions required by that AD.” Consequently, schedule and perform the physical works, inspections, placard installations or rigging adjustments identified in the FAA AD text. Because the CASA AD does not reproduce the technical steps, rely on the FAA AD documents for the specific methodology, parts, and any required certification or release procedures.

6. Engage appropriate maintenance personnel. For the remedial works, use appropriately certificated maintenance organisations or personnel capable of performing the FAA AD‑specified tasks. Ensure entries are made in the aircraft maintenance logbooks or other mandated records to reflect the completed works in a manner that demonstrates compliance.

7. Timing: observe CofA‑linked deadlines. If the aircraft does not yet have a certificate of airworthiness, complete the records determination and any necessary remedial actions before CofA issue, as the Compliance clause requires. If the aircraft already holds a CofA, complete the records check and any required actions within 60 days after the AD’s commencement date (commencement: 31 August 2018). Practically, that means a 60‑day window starting on 31 August 2018.

8. Document completion and retain records. After performing any required actions, update aircraft records to show the FAA AD number, the date of the remedial action, details of the work performed, references to parts or placards fitted, and maintenance release signatures, so that the records themselves are the primary proof of compliance under the AD.

9. Prepare to justify non‑applicability where relevant. For FAA ADs judged non‑applicable, retain documentary substantiation (manufacture data, configuration sheets, previous modification certificates) to demonstrate why the FAA AD does not apply to the particular aircraft.

10. Use the AD’s administrative metadata when certifying. When seeking CofA issuance or renewal, present the records showing compliance with the CASA AD’s requirements (records check and any remedial works) and identify the FAA AD versions consulted “as in force at the time of issue of this AD” to ensure the certifying authority can verify compliance against the same reference point.

These steps follow directly from the AD’s two requirements, the Table 1 listing, and the Compliance timing provisions. The AD does not provide procedural waiver, variation, or appeal wording, so practitioners should build a robust documentary file, ensure technical works are performed to the FAA AD specifications, and time actions to the CofA‑linked deadlines recorded in the AD.