AD/TB10/11 Amdt 1 - Fuselage Frame 9

The AD is compact and builds on a small number of discrete legal and technical concepts. Those concepts are explicit in the document. Each concept below is stated as it appears in the Directive, then followed by the concrete operational consequence that the Directive text creates.

Applicability by serial number and modification status. The Directive applies only to "TB9 and TB10 series aeroplanes with S/N 1 to 795 without modification No 70 embodied." This produces a binary rule: subject aircraft are those within the serial number band and without Mod No 70; aircraft outside the serial number band, or aircraft within the band that have Mod No 70 embodied, are outside the Directive.

Delegation to a manufacturer service bulletin. The Requirement reads "Action in accordance with Aerospatiale (Socata) Service Bulletin No 35/1." The AD therefore makes the substantive inspection method a function of the content of Service Bulletin No 35/1. The AD operates as a legal instrument that mandates compliance with that external technical document.

Tiered compliance timing tied to total time in service. The Compliance provisions create different deadlines depending on total airframe hours as at the relevant reference date. For aircraft with 1,500 or more hours, the action is required "before further flight after 9 October 1987." For aircraft with less than 1,475 hours, the action must occur "within 25 hours time in service after 9 October 1987." For all affected aircraft, "Thereafter, reinspect at each issue of a new Maintenance Release." Thus the AD imposes an immediate or near-immediate inspection, plus recurring inspections tied to Maintenance Releases.

Terminating action by embodiment of a specified modification. The Note states: "Embodiment of Aerospatiale (Socata) modification No 70 constitutes terminating action for this Directive." The AD therefore provides a permanent alternate path to cease recurring inspection obligations, conditioned on incorporation of the specific manufacturer modification.

Safety rationale recorded as manufacturer notification of cracking. The Background records the precipitous fact prompting the AD: "Notification has been received from the manufacturer of in service cracking on overseas aircraft." The Background also states the AD "has been amended to reflect the terminating action specified in the Requirement document." The AD thus ties its existence to an identified airworthiness concern, and it explains the amendment as reflecting the terminating action.

Administrative provenance. The heading identifies the source regulatory framework: "COMMONWEALTH OF AUSTRALIA (Civil Aviation Regulations 1998), PART 39 - 105 CIVIL AVIATION SAFETY AUTHORITY SCHEDULE OF AIRWORTHINESS DIRECTIVES." That places the AD within a statutory schedule of directives and identifies the administrative issuer as the Civil Aviation Safety Authority.

Notably absent provisions. The AD does not set out who must perform or pay for inspections, the detailed inspection criteria or allowable findings, the content of Mod No 70, any recordkeeping requirements, nor any penalties or enforcement steps in this text. Those matters are either delegated to other instruments or not specified in the Directive itself.

Taken together, the main concepts are: a clearly delimited applicability class, a delegation to a manufacturer service bulletin for technical execution, tiered timing windows tied to airframe hours and to Maintenance Releases, a terminating modification, and a stated safety prompt of cracking notifications.

The Directive identifies a narrow set of affected subjects by aircraft model, serial number and modification status. The Applicability provision reads: "TB9 and TB10 series aeroplanes with S/N 1 to 795 without modification No 70 embodied." That yields the primary group affected: owners and operators of Aerospatiale (Socata) TB9 and TB10 series aeroplanes whose airframes have serial numbers in the range 1 to 795, and which have not had Aerospatiale (Socata) modification No 70 embodied. If an airframe has Mod No 70 embodied, the Note states that embodiment "constitutes terminating action," which removes that airframe from the Directive's inspection obligation.

The AD does not name particular persons, companies, maintenance organisations or the Civil Aviation Safety Authority as responsible parties in the text provided. It does not use the words "owner" or "operator" or "licensed maintenance organisation." The Directive therefore affects such named aircraft in the sense that the aircraft themselves are the objects of the requirement, but the text is silent as to who must carry out the required action, who pays for it, and how compliance is to be recorded or certified. The operative Requirement mandates "Action in accordance with Aerospatiale (Socata) Service Bulletin No 35/1." That creates an indirect effect on anyone who must implement that Service Bulletin, such as maintenance personnel, certificated maintenance organisations, and the aircraft owner or operator, but the AD does not itself specify which of those parties is obliged in law.

Timing distinctions affect owners and operators differently depending on airframe total time in service as at 9 October 1987. Aircraft with 1,500 hours or more must be inspected "before further flight after 9 October 1987." Aircraft with less than 1,475 hours must be inspected within 25 hours time in service after 9 October 1987. Aircraft whose total time in service falls between 1,475 and 1,500 hours are not specifically addressed in the AD text, which raises a practical question for affected owners or operators about the applicable deadline. The AD requires "Thereafter, reinspect at each issue of a new Maintenance Release," thereby affecting maintenance management processes and the frequency at which maintenance organisations issuing Maintenance Releases will be required to repeat the inspection.

Because the AD defers the inspection methodology to Service Bulletin No 35/1, anyone who performs maintenance must obtain and follow that document to meet the AD's Requirement. Similarly, embodying Aerospatiale (Socata) modification No 70 is expressed as the terminating action; therefore, parties capable of undertaking and certifying embodiment of that modification are affected insofar as their actions will remove the aircraft from the ongoing inspection cycle.

Finally, because the AD is expressed within the Commonwealth Civil Aviation Regulations context, it will be relevant to compliance frameworks within Australian civil aviation, even though the AD text does not itself identify enforcement agents or penalties. In short, the Directive affects the subset of TB9/TB10 aircraft described, and indirectly affects the maintenance actors and corporate entities that service, own or operate them, though those roles are not explicit in the instrument text.

The AD text sets a precise set of duties relating to inspection and reinspection of the specified aircraft, and it creates one right: the right to terminate inspection obligations by embodying a specified modification. The instrument does not create duties beyond those discrete prescriptions, nor does it set out procedural rights, appeals, or penalties.

Inspect according to the Service Bulletin. The Requirement is categorical: "Action in accordance with Aerospatiale (Socata) Service Bulletin No 35/1." The duty, as expressed, is to carry out whatever action the Service Bulletin prescribes. The AD does not reproduce the steps or criteria, so the content of the duty depends on the Service Bulletin No 35/1. The AD thus converts the Service Bulletin into a mandatory action for applicable aircraft.

Observe staged inspection timing. Compliance is time-sensitive. The Compliance clause imposes three duties:

• For aircraft with 1,500 hours or more total time in service, inspectors must inspect "before further flight after 9 October 1987." That is an immediate pre-flight inspection obligation in the first instance.
• For aircraft with less than 1,475 hours total time in service, the duty is to inspect "within 25 hours time in service after 9 October 1987." That is a near-term routine inspection obligation.
• Thereafter, the duty is to "reinspect at each issue of a new Maintenance Release." That converts the inspection into a recurring duty linked to maintenance releases.

Terminate inspections by embodiment of Mod No 70. The Note grants a concrete right: "Embodiment of Aerospatiale (Socata) modification No 70 constitutes terminating action for this Directive." An owner or operator that embodies Mod No 70 therefore gains the right to cease the recurring inspection obligations imposed by the AD. The AD does not define Mod No 70 within its text, so the nature, cost, and acceptability of embodying that modification are set out elsewhere.

Absence of express assignment of responsibility. The AD does not state which party is legally obliged to perform the inspections, nor which party bears the cost of inspections or of embodying Mod No 70. The AD also does not state how inspections must be recorded, who may certify compliance, or whether compliance requires specific licencing or approved maintenance organisations. Those silences leave practical questions about duty-holders unresolved within the AD itself.

No procedural rights or objections set out. The AD does not contain provisions for objection, appeal, or applications for deferred compliance in the text provided. It likewise does not provide alternatives to the Service Bulletin method. Consequently, the only right expressly created is the terminating right upon embodiment of Mod No 70, and the only duties are to perform the Service Bulletin action within the specified time windows and to re‑inspect at each Maintenance Release until termination.

In summary, the AD imposes inspection duties by reference to the Service Bulletin, sets staged deadlines and recurrent obligations, and grants a terminating right via Mod No 70. It does not specify who must do the work, how compliance is to be certified, nor the administrative remedy or enforcement mechanisms within the text provided.

The AD text supplied does not set out penalties, fines, or specific enforcement processes. The document is titled and placed within the framework "COMMONWEALTH OF AUSTRALIA (Civil Aviation Regulations 1998), PART 39 - 105 CIVIL AVIATION SAFETY AUTHORITY SCHEDULE OF AIRWORTHINESS DIRECTIVES," which implies the Directive operates within a statutory regime that includes enforcement mechanisms. However, the Directive itself contains no penalty clause, no administrative sanctioning provision, and no description of enforcement steps. The AD therefore specifies what must be done but does not, in its text, describe how failure to do it will be punished.

Operational enforcement consequences will depend on the wider regulatory environment and on how the Civil Aviation Safety Authority applies Part 39 - 105 directives. Those enforcement mechanisms are not reproduced in the instrument before us. The AD does indicate compliance periods and a terminating action, which are the factual triggers an enforcement authority would use to verify compliance, but the text does not say who will verify, how verification will take place, or what evidential standard will be applied.

Because the AD requires action "in accordance with Aerospatiale (Socata) Service Bulletin No 35/1," enforcement will likely rely on evidence that the Service Bulletin actions were carried out. The AD itself does not state what constitutes acceptable proof. The requirement to "reinspect at each issue of a new Maintenance Release" links compliance to the maintenance process and to the issuance of Maintenance Releases, which are typically cognate with certification of maintenance tasks. But the AD does not state whether a Maintenance Release must explicitly record the inspection required by this AD, nor whether the mere issuance of a Maintenance Release will suffice as proof.

Given the AD's silence on penalties and enforcement steps, practitioners should note that the instrument sets mandatory actions but leaves enforcement modalities and sanctions to the broader regulatory framework. The AD's Background states a safety rationale, "Notification has been received from the manufacturer of in service cracking on overseas aircraft." That statement establishes an airworthiness concern that could inform enforcement decisions, but it does not itself prescribe penalties or enforcement procedures.

In short, the AD mandates inspection and reinspection obligations, and allows termination by embodiment of Mod No 70, but the AD text does not specify penalties, who enforces the directive, or the evidentiary standards for establishing compliance.

The AD sits inside the Commonwealth civil aviation regulatory architecture, as indicated by the header: "COMMONWEALTH OF AUSTRALIA (Civil Aviation Regulations 1998), PART 39 - 105 CIVIL AVIATION SAFETY AUTHORITY SCHEDULE OF AIRWORTHINESS DIRECTIVES." That positioning indicates the AD is part of a statutory schedule of Airworthiness Directives. The AD therefore functions as a regulatory instrument that interacts with other rules governing aircraft maintenance, modification, and airworthiness certification, although those other instruments are not included in the text provided.

Interaction with manufacturer documents. The Requirement explicitly references Aerospatiale (Socata) Service Bulletin No 35/1. The AD therefore converts the Service Bulletin into a mandatory standard for the specified aircraft. The Service Bulletin is external to the AD and presumably contains detailed inspection methodology. The AD also references Aerospatiale (Socata) modification No 70 as the terminating action. Both the Service Bulletin and Mod No 70 are external technical materials, and the AD's effect depends on their contents. The AD thus interacts with the corpus of manufacturer directives, service bulletins and modification documentation.

Interaction with maintenance procedures. The Compliance clause demands reinspections "at each issue of a new Maintenance Release." That creates an operational interaction with whoever issues Maintenance Releases. The AD implicitly ties the inspection schedule to maintenance cycles, and therefore to maintenance-related legal and administrative instruments. The AD does not define "Maintenance Release," so the term's meaning must be found in other regulations or in maintenance practice. The AD therefore imposes duties that will be coordinated with maintenance release procedures and documentation, but those cross-references are not specified here.

Interaction with modification procedures. The Note provides that embodiment of Mod No 70 "constitutes terminating action for this Directive." That creates an interaction between the AD and the regulatory or procedural law governing aircraft modifications, modification approvals, and modification embodiment. Whether Mod No 70 requires engineering approval, downtime, parts, or certification will be governed by other documents; the AD does not specify those processes.

Temporal interaction with dates and aircraft hours. The Compliance deadlines are expressed with reference to "9 October 1987" and to aircraft total time in service thresholds. These temporal references interact with recordkeeping and hours-logging regimes; for example, an operator will need to establish total time in service at the relevant date to determine the applicable compliance window. The AD itself does not specify the recordkeeping standard or how to calculate total time in service, so the calculation will interact with maintenance records and other regulatory definitions.

Absence of enforcement detail and evidentiary interaction. Because the AD contains no penalty or enforcement provisions, it will interact with enforcement statutes and regulatory powers elsewhere in Part 39 or in other Civil Aviation Regulations. The AD's compliance prescriptions will be enforced, if at all, through those other mechanisms. The AD does not set out how conflicts between the Service Bulletin and the AD texts are to be resolved; for example, if the Service Bulletin indicates a different inspection interval than the AD, the AD's instruction to "action in accordance with" the Service Bulletin suggests the Service Bulletin governs the technical method, but the AD's timing provisions remain binding.

In sum, the AD interacts with manufacturer service bulletins and modification documentation, with maintenance release and modification embodiment processes, and with the recordkeeping and enforcement rules that sit elsewhere in the civil aviation regulatory framework. The AD itself provides the mandate and key cross-references, but leaves operational details to the referenced external documents and to the broader regulatory scheme.

The instrument is presented as AD/TB10/11 Amdt 1, with the identification line "Fuselage Frame 9 6/88." The inclusion of "Amdt 1" indicates this document is an amendment to an earlier AD; the Background expressly says, "This Directive has been amended to reflect the terminating action specified in the Requirement document." The Requirement document here is Aerospatiale (Socata) Service Bulletin No 35/1. Therefore, the AD as presented is not the original AD but an amended version incorporating or reflecting a terminating action appearing in the Service Bulletin or its associated documentation.

The textual evidence in the AD does not supply the prior version(s) of AD/TB10/11, nor does it describe the changes in detail beyond stating that the amendment "reflect[s] the terminating action specified in the Requirement document." The Note that "Embodiment of Aerospatiale (Socata) modification No 70 constitutes terminating action for this Directive" appears to be the amendment reflected. The AD header date marker "6/88" indicates the amendment's date marker, and the compliance deadlines reference the date "9 October 1987." That suggests the initial safety concern was notified before or around that date and that the amendment was formalised in mid-1988, but the AD text provides only the dates and the statement that the Directive was amended.

No further amendment entries or historical entries are provided in the text. There is no schedule of prior amendments, no notation of superseded ADs, and no textual history of how the AD's requirements changed from the original to Amendment 1. The AD does not reproduce prior language or indicate whether the timing windows or the Service Bulletin reference are new or unchanged.

Because the AD expressly ties termination to embodiment of Mod No 70 and states the Directive was amended to reflect that terminating action, the principal substantive addition in this amendment is the Note creating the terminating action. The AD does not indicate whether the Service Bulletin itself was changed, or whether the Service Bulletin was the new source of the terminating action. The Background indicates that manufacturer notification of in-service cracking prompted the AD, and that the amendment is to reflect the Service Bulletin's terminating action.

In short, the amendment history shown in this text is minimal: the document is Amendment 1 to AD/TB10/11, dated 6/88, and was amended to incorporate a terminating action (embodiment of Mod No 70), with prior action and dates referenced to 9 October 1987. No further amendment trail or version history is included in the AD text provided.

The AD text contains no litigation history. It names no cases and cites no judicial or administrative decisions. There is no record within this document of challenges, appeals, enforcement actions, or court determinations relating to AD/TB10/11 Amdt 1. The Background simply records that "Notification has been received from the manufacturer of in service cracking on overseas aircraft" and that the Directive was amended "to reflect the terminating action specified in the Requirement document."

Consequently, there are no source-provided precedents, disputes, or recorded interpretations of this AD to summarise. Any litigation or administrative challenges arising from this AD, if they exist, would be outside the text provided and are not recited here. The AD furnishes only the directive language and an explanatory Background; it does not catalogue any enforcement proceedings, civil penalties imposed, or judicial review outcomes. For practitioners seeking litigation history, the AD as supplied offers no entries and thus requires consultation of external legal or regulatory records to discover any subsequent disputes or determinations.

The Directive is brief, but the text contains a number of drafting features and silences that create operational hazards for practitioners and operators. These are concrete, source-grounded points that can create confusion or compliance risk.

Serial number and modification gating. Applicability is limited to "TB9 and TB10 series aeroplanes with S/N 1 to 795 without modification No 70 embodied." That creates a strict gate: aircraft outside the serial number band are out, and aircraft within the band with Mod No 70 embodied are out. Practically, operators must be able to demonstrate the serial number and modification status. The AD does not define what evidence is acceptable to show Mod No 70 is embodied.

Service Bulletin as the operative technical standard. The Requirement mandates "Action in accordance with Aerospatiale (Socata) Service Bulletin No 35/1." The AD does not include the technical steps or acceptance criteria. Operators must obtain and follow that Service Bulletin to know what precisely the inspection requires. The AD does not state whether deviation from the Service Bulletin is permissible, nor whether a documented alternative inspection method can be approved.

Timing gap between 1,475 and 1,500 hours. The Compliance paragraphs create separate deadlines for aircraft with 1,500 hours or more and for those with less than 1,475 hours. Aircraft with total time in service between 1,475 and 1,500 hours are not addressed by the text as written. That creates an ambiguity as to when such aircraft must be inspected. The AD does not resolve that gap. Practitioners must note this drafting gap is present in the source text.

Reference date implications. The deadlines are anchored to the date "9 October 1987": inspection for 1,500+ hours is required "before further flight after 9 October 1987"; inspection for <1,475 hours is "within 25 hours time in service after 9 October 1987." The AD does not say how to treat aircraft that change hands, or aircraft whose logbook records are incomplete for that specific reference date. The AD is silent on how to calculate total time in service for the purpose of determining which deadline applies.

Recurring inspection tied to Maintenance Release. The AD requires reinspections "at each issue of a new Maintenance Release." The AD does not define "Maintenance Release" within its text. Practitioners must therefore identify the governing definition elsewhere. The linkage to Maintenance Release issuance could require repeated inspections even if no further suspicious conditions exist, and it imposes an inspection at whatever administrative frequency Maintenance Releases are issued.

Termination by Mod No 70 but Mod No 70 not described. The Note gives a terminating action but does not describe Mod No 70 or where to obtain its engineering data. The AD also does not say whether Mod No 70 must be embodied in accordance with particular approval procedures. The AD leaves unspecified whether embodiment requires downtime, parts, or certification by a particular authority.

No enforcement or penalty detail in text. The AD does not specify penalties or enforcement mechanisms. That leaves open questions about the consequences of non-compliance and the evidentiary standard for proving compliance.

No specification of who performs or pays for the inspection. The AD mandates inspection but does not identify the duty-holder or who bears the expense. That could raise commercial and regulatory coordination issues among owners, operators and maintenance organisations.

Service Bulletin availability and versioning. The AD references Service Bulletin No 35/1 without providing the date or revision. If multiple revisions of the Service Bulletin exist, the AD does not state which revision applies. That creates a potential conflict if later or earlier revisions differ.

These "gotchas" are all deducible from the AD text as provided. They present concrete operational and compliance questions that parties must address by consulting the external documents referenced, the maintenance and modification records, and the broader regulatory framework not reproduced in this instrument.

The AD itself prescribes the substantive compliance method and schedule, but leaves out several operational details. The following steps are a source-grounded practical compliance checklist rooted in the AD text. Each step ties back to the AD language.

1. Determine applicability. Verify whether the aeroplane is a TB9 or TB10 series airframe and whether its serial number is within the range 1 to 795. Verify whether Aerospatiale (Socata) modification No 70 has been embodied. The AD's Applicability provision is "TB9 and TB10 series aeroplanes with S/N 1 to 795 without modification No 70 embodied." If the airframe is outside that serial number range or already has Mod No 70 embodied, the AD does not apply to that airframe.

2. Establish total time in service as at the reference date. The Compliance timings depend on total time in service relative to specific thresholds and to the date "9 October 1987." The AD requires different deadlines for aircraft with "1500 hours or more total time in service" and those with "less than 1475 hours total time in service." Operators should identify the aircraft's total time in service to determine which compliance bucket applies. The AD text itself requires the inspection either "before further flight after 9 October 1987" for 1,500+ hour aircraft, or "within 25 hours time in service after 9 October 1987" for those under 1,475 hours.

3. Obtain Aerospatiale (Socata) Service Bulletin No 35/1. The Requirement directs: "Action in accordance with Aerospatiale (Socata) Service Bulletin No 35/1." Compliance therefore requires the exact Service Bulletin that the AD references. The AD does not reproduce the Service Bulletin, so compliance work will involve securing the bulletin from the manufacturer, reviewing the inspection steps, parts lists, allowable damage criteria, and any required procedures.

4. Carry out the inspection per the Service Bulletin and within the AD time windows. For aircraft in the 1,500+ hours category, perform the Service Bulletin inspection "before further flight after 9 October 1987" as required by Compliance(a). For aircraft with less than 1,475 hours, perform the Service Bulletin inspection "within 25 hours time in service after 9 October 1987" as required by Compliance(b). The AD's text requires action "in accordance with" the Service Bulletin, so strictly follow the Service Bulletin's technical instructions.

5. Reinspections at each Maintenance Release. The AD mandates: "Thereafter, reinspect at each issue of a new Maintenance Release." Incorporate the inspection required by Service Bulletin No 35/1 into the checklist for every Maintenance Release, so that the inspection is performed whenever a new Maintenance Release is issued.

6. Consider terminating action. The AD Note states: "Embodiment of Aerospatiale (Socata) modification No 70 constitutes terminating action for this Directive." If economically and operationally practicable, plan for embodiment of Mod No 70, in accordance with the engineering and approval procedures relevant to modifications (which are not specified in this AD text), to terminate the recurring inspection obligation.

7. Address the timing gap (1,475 to 1,500 hours). The AD does not specify the deadline for aircraft whose total time in service is between 1,475 and 1,500 hours. Until authoritative guidance is obtained from the issuing authority or from the Service Bulletin, operators should treat this as an ambiguity and seek clarification from the Civil Aviation Safety Authority or the aircraft manufacturer. The AD's text makes clear the gap exists; the AD does not resolve it.

8. Maintain documentary evidence. Although the AD text does not set recordkeeping obligations, the Requirement and the Compliance schedule will be tested by regulators or auditors through maintenance records and Maintenance Releases. Maintain copies of Service Bulletin No 35/1 used for the inspection, records showing the inspection was performed within the specified time window, and documentation of any embodiment of Mod No 70. Keep Maintenance Release documentation showing reinspections performed at each new Release.

9. Coordinate with maintenance approval authorities. The AD does not specify who may perform or certify the required inspections or the embodiment of the modification. Consult the applicable regulatory maintenance approval rules and the Service Bulletin for any instructions about required qualifications for personnel or approval for modifications. The AD places the technical requirement in the Service Bulletin, but does not identify the certifying maintenance entity.

10. Seek formal clarification where necessary. For matters left unspecified in the AD text , for example, which revision of Service Bulletin No 35/1 applies, what evidence is acceptable to show Mod No 70 is embodied, how to treat aircraft with ambiguous total time in service records, or how to interpret "Maintenance Release" , obtain formal guidance from the Civil Aviation Safety Authority or the manufacturer. The AD itself does not answer these questions.

These steps implement the AD as written: check applicability, obtain and follow Service Bulletin No 35/1 within the AD's specified times, reinspect at each Maintenance Release, and consider embodying Mod No 70 as terminating action. The AD supplies the mandate and timing but not operational details about recordkeeping, payor, certifier or enforcement; operators and maintenance organisations must address those matters using their existing regulatory and commercial processes and by seeking clarifications where the AD is silent.