AD/DO 228/10 Amdt 1 - Fuselage Frame 19

Short‑field landing. The AD defines this operationally. A short take‑off is made when the aircraft clears a 50‑foot obstacle within 1,500 feet of commencing take‑off. A short landing is made when the aircraft stops within 1,500 feet after passing over a 50‑foot obstacle. This definition is critical because it determines which aircraft fall into the higher‑risk category that triggers the reinforcement requirement. Operators must record each landing and classify it against this distance‑based test. The threshold is 120 such landings in the last 1,200 landings before the effective date. This means an operator cannot rely on typical landing counts; they must know the nature of the landing field.

Structural Significant Item (SSI) Task No. 53.37. This is a specific inspection task from the Dornier 228 Structure Inspection Programme, which is part of the Time Limits/Maintenance Checks Manual. The AD does not reproduce the inspection procedure; it incorporates it by reference. The operator must have access to the manual and follow its detailed steps. The task is directed at the centre section of fuselage frame 19.

Reinforcements and butt straps. The corrective action required for high‑use aircraft is the installation of reinforcing structure on fuselage frame 19 at the lower part of the fuselage. The engineering solution is prescribed in RUAG Service Bulletin SB-228-273. The AD allows use of the original issue or a later EASA‑approved revision. This gives some flexibility if the manufacturer updates the instructions, but only if EASA approves the revision.

Compliance schedule logic. The AD uses two different metrics: landings and calendar months. For the recurring inspection, the interval is 2,400 landings or 72 months, whichever occurs first. This recognises that aircraft may accumulate cycles at very different rates. An aircraft operating many short flights may hit 2,400 landings long before 72 months; a low‑utilisation aircraft may reach 72 months before 2,400 landings. The operator must track both metrics.

EASA‑approved repair solution. For any detected cracking or damage, the repair must be approved by the European Aviation Safety Agency. This ties the Australian AD to foreign regulatory approval, creating a dependency on EASA’s processes. If EASA has not approved a repair for a particular crack pattern, the aircraft cannot return to service.

Interim action status. The AD was issued while the root cause investigation was ongoing. That means the requirements may later be superseded by a permanent solution, but until then the operator must comply with the current directive. There is no guarantee the same inspection interval or modification will remain mandatory.

The AD primarily affects registered operators, owners, and lessees of Dornier 228 models 100, 101, 200, 201, 202, and 212. The specific serial numbers captured are 7011 through 7168 and 8012 through 8245, with serial numbers 8107 and 8169 expressly excluded from the reinforcement requirement. However, the exclusion only applies to the reinforcement obligation; those two serial numbers still fall under the recurring inspection requirement for all aircraft. All remaining Dornier 228 aircraft (i.e., units outside that range or other less‑common models such as the 228-212 not listed) are subject only to the recurring inspection regime. Therefore, any person with operational control over a Dornier 228 in Australia must check whether their aircraft is within the stated serial numbers.

Maintenance organisations are also affected. They must be familiar with the SSI Task No. 53.37 procedure and the Service Bulletin installation instructions. If they perform the reinforcement work, they must have access to the RUAG bulletin and ensure the installation meets its specifications. For any crack repairs, they must coordinate with the operator to obtain an EASA‑approved repair design. This may involve contacting RUAG or EASA directly, imposing time and cost overheads.

Pilots and flight operations departments are indirectly affected because they must track whether each landing meets the short‑field definition. If the aircraft operates from short runways, the operator must keep records. This could be a significant data‑collection burden for operations that frequently use airfields of varying length. It also creates a risk of misclassification if the operator does not accurately measure the landing distance.

Aviation insurers and financiers may also take an interest, because non‑compliance with an AD can affect airworthiness status, insurance coverage, or asset value. An aircraft that has not received the required reinforcement may be worth less or be subject to restrictions on use. The AD does not directly regulate third parties, but the economic effects ripple through contracts and insurance.

Finally, CASA is the enforcement authority. The AD was signed by a delegate of the CEO, and failure to comply exposes the operator to administrative action under the Civil Aviation Safety Regulations, including suspension or cancellation of the aircraft’s certificate of airworthiness or of the operator’s air operator certificate. Although the AD itself does not list penalties, the broader regulatory framework supplies them.

The central duty is to perform the inspections and modifications within the specified compliance times. Aircraft in the high‑stress group (with 120+ short‑field landings in the relevant history) face a sequence: inspect within 800 landings; if no crack, install reinforcements before the accumulation of 800 landings after the effective date; if crack, repair before further flight. Aircraft in the same serial range but below the threshold must do the initial inspection at the schedule in the manual, then repair any damage before further flight. After those initial actions, all affected aircraft (including the excluded serials) must repeat the inspection every 2,400 landings or 72 months. The duty is ongoing and indefinite.

Operators also have a duty to keep accurate records of short‑field landings if applicable. Without that record, they cannot determine whether they fall into the higher‑risk category. The AD does not prescribe a record‑keeping method, but good practice would require a log of each landing field length and the take‑off and landing distances achieved.

The right to use an alternative repair method is constrained. If cracking is found, the repair must be EASA‑approved. The operator cannot unilaterally develop a repair; they must submit it to EASA or use an already approved design. Similarly, the reinforcement must follow the RUAG Service Bulletin or a later EASA‑approved revision. There is no right to deviate from that bulletin without regulatory approval.

Operators also have the right to seek an extension of compliance time under CASA procedures, although the AD does not mention extensions. Under CASR Part 39, a person may apply for an alternative means of compliance. The AD implicitly allows this by referencing EASA‑approved revisions, but the operator would need to demonstrate an equivalent level of safety and obtain CASA’s approval. The text does not grant any automatic waiver.

Another duty arises from the “before further flight” language applicable to crack repairs. This means the aircraft cannot be flown after discovery of cracking until a repair is done. The operator must have procedures in place to detect cracks during inspections and then to ground the aircraft promptly. This imposes a business interruption risk, especially if the aircraft is far from a maintenance base.

Finally, operators have a duty to ensure that maintenance organisations performing the work are appropriately authorised. The AD does not specify repair‑station qualifications, but under CASR, only a licensed aircraft maintenance engineer or an approved maintenance organisation may carry out the work. The operator is ultimately responsible for compliance.

The AD itself does not list a penalty amount or imprisonment term. Instead, it relies on the general enforcement regime under the Civil Aviation Safety Regulations 1998 and the Civil Aviation Act 1988. Breaching an airworthiness directive is a serious matter because the directive is a condition of the aircraft’s certificate of airworthiness. If the required inspection or modification is not done, the aircraft is no longer airworthy, and flying it would breach CASR 21.181 (maintenance of airworthiness). Under section 20A of the Civil Aviation Act, the operator may be subject to a civil penalty of up to 1,000 penalty units for each contravention (a penalty unit is currently $313, so up to $313,000 per breach). Alternatively, CASA may issue an infringement notice with a lower fixed penalty, or it may suspend or cancel the certificate of airworthiness.

Detection of non‑compliance typically occurs during a scheduled maintenance check, a ramp check, or a CASA audit. Because the AD requires a specific inspection task, a maintenance record that lacks the required entry is prima facie evidence of non‑compliance. CASA can also cross‑reference service bulletin accomplishment records.

In practice, the most immediate consequence for an operator is that their aircraft cannot be operated legally after the compliance deadline if the action is not complete. That is a form of regulatory grounding. If the aircraft is used in revenue service, the downtime can be very expensive. Unlike a fine, which is a payment after the fact, grounding is a continuing loss of income.

The AD also has an indirect enforcement aspect through the integrated circuit of international airworthiness. Because the AD references EASA AD 2009-0085, and because Dornier 228s often operate internationally, failure to comply with the Australian AD may also breach foreign regulations if the aircraft flies into EASA‑member states. That creates a risk of detention or denial of entry.

There is no criminal penalty specified, but a deliberate falsification of records (e.g., logging an inspection that never occurred) could attract criminal charges under the Crimes Act or the Criminal Code. The AD does not address this, but the surrounding law does.

Given the high cost of non‑compliance, both financially and reputationally, the incentive to comply is strong. However, the AD’s cost‑benefit trade‑off is not assessed by the instrument itself. Operators must decide whether the cost of the reinforcement (labour, parts, down time) is justified by the risk of enforcement and the risk of structural failure. The AD removes that choice for high‑stress aircraft.

The AD explicitly refers to EASA AD 2009-0085. That European directive is the root source; CASA’s AD is the domestic adoption. Under the bilateral aviation safety agreements between Australia and Europe, CASA generally recognises EASA airworthiness directives, but they must be issued as Australian ADs to be enforceable in Australia. The interaction means that an operator complying with the EASA AD is also complying with the CASA AD, but only if the compliance times match. In this case, CASA’s AD has its own effective date and compliance times, which may differ from the EASA version. The operator cannot simply follow the EASA AD and ignore the Australian version if they differ.

The AD also incorporates the Dornier 228 Time Limits/Maintenance Checks Manual by reference. That manual is itself an approved document under the type certificate. Changes to the manual may affect the inspection procedures, but the operator must use the version current at the time of compliance, subject to any later EASA‑approved revisions. This creates a layered regulatory framework: the AD sits on top of the manual, and the manual sits on top of the type certificate.

There is no mention of Part 91, Part 121, Part 135, or Part 138, but those operational rules also apply. For example, if the aircraft is operated under an air operator certificate, the certificate holder must have an approved maintenance control manual that includes compliance with ADs. The AD may also interact with the operator’s fatigue management system, because the inspection interval is based on landings, which may correlate with pilot duty cycles.

The AD pre‑empts any conflicting maintenance schedules. If the operator’s maintenance schedule calls for fuselage frame inspection at longer intervals than 2,400 landings, the AD overrides that. The AD acts as a minimum requirement; the operator may do more frequent inspections but not less.

The “EASA‑approved repair solution” requirement ties Australian airworthiness to a foreign regulator. If the repair needs EASA approval, the operator must either obtain that directly or use a repair already covered by an EASA Supplemental Type Certificate. This may create a bottleneck if EASA is slow to respond. The AD does not provide an Australian fallback; it does not say “or CASA‑approved solution”. That may be deliberate, as frame 19 design is likely covered by the type certificate held by EASA for RUAG.

Finally, the AD interacts with commercial contracts. A lease agreement may require the lessee to comply with all ADs. If the lessee fails to do so, the lessor may have a right to terminate or claim damages. Similarly, an aircraft purchase agreement may require the seller to demonstrate AD compliance before delivery.

This document is Amendment 1 to AD/DO 228/10. The original AD is not provided in the source, but the background text explains that Amendment 1 was issued in response to a new EASA AD that required installation of reinforcements and butt straps on frame 19 for aircraft used in operations that subject the frame to high stress, as well as recurring inspections for all aircraft. The original AD presumably did not have the reinforcement requirement. Amendment 1 added that obligation for the high‑stress sub‑population and also changed the compliance schedule.

The effective date of Amendment 1 is 4 June 2009. The document was signed on 24 April 2009 by David Villiers, a delegate of the CASA CEO. This means there is a gap of about six weeks between signature and effective date, which is normal to allow operators to prepare.

The source does not provide the text of the original AD, so we cannot compare exact changes. However, from the background, we can infer that the original AD probably only required inspections. Amendment 1 added the mandatory reinforcement for aircraft with a history of short‑field landings. This was a significant expansion of the compliance burden, from an inspection‑only regime to one that required physical modification. It also likely introduced the distinction between aircraft with and without 120 short‑field landings.

The service bulletin referenced, RUAG SB-228-273, was presumably not called out in the original AD. Amendment 1 incorporated it.

There is no indication of any later amendments beyond Amdt 1. The source is a single page; there may be subsequent amendments that supersede this one, but they are not in the text. The user should check the current CASA AD database for later versions.

The amendment was driven by an EASA AD number 2009-0085. That is typical of cross‑border recognition. CASA does not issue an AD in a vacuum; it follows the lead of the state of design. This amendment is therefore part of a coordinated international response to the cracking issue.

The source does not mention any litigation, appeals, or legal challenges relating to AD/DO 228/10 Amdt 1. No cases are cited, and no administrative review is noted. This is not surprising because airworthiness directives are administrative decisions that rarely attract court challenges; the compliance deadline is usually short, and operators have more incentive to comply than to litigate. They can seek an alternative means of compliance from CASA without going to court.

There is no record of any class action or personal injury lawsuit arising from the underlying cracking issue, at least not in the source provided. The background mentions that cracks were detected during a maintenance inspection and that investigation into the cause was ongoing. It does not say whether any accidents occurred. Without those facts, we cannot infer litigation.

If a frame 19 failure had occurred before the AD was issued, there could be product liability claims against the manufacturer (RUAG or formerly Dornier). But the AD does not speculate on liability; it is an airworthiness administrative measure.

The lack of litigation history in the source is itself a data point. It suggests that the AD has not been judicially tested. That means the interpretation of key terms such as “short‑field landing” has not been settled by a court. If a dispute arises over whether a particular landing qualified as short‑field, an operator would rely on the AD’s definition, and if challenged, a court would interpret it. That definition is objective (50‑foot obstacle, 1,500 feet), but it may be difficult to prove retroactively if the operator did not record the landing distance at the time.

Similarly, the phrase “EASA‑approved repair solution” could be contentious if an operator uses a repair that EASA later declines to approve. The AD does not state that the operator must have the approval in hand before starting work, but the “before further flight” requirement suggests that the repair must be completed and approved before flight resumes.

Given the absence of case law, practitioners should treat the AD as enforceable on its face, with little judicial gloss.

Definition trap. The term “short‑field landing” is not the intuitive one. Many pilots might think a short‑field landing is one where the available runway is short relative to aircraft performance. But the AD gives a specific performance‑based definition: the aircraft must stop within 1,500 feet of a 50‑foot obstacle. That is a test of actual stopping distance, not runway length. An aircraft landing on a 2,000‑foot runway might still be classified as a short‑field landing if it stops quickly, or vice versa. Operators must measure landing distance, not just runway length.

120 landings out of 1,200. The threshold is not simply 120 short‑field landings, but 120 such landings within the most recent 1,200 landings before the effective date. If an operator has 120 short‑field landings over the aircraft’s life but only 100 in the last 1,200, they are in the lower‑risk group. That could be a relief or a trap, depending on whether the record‑keeping system can filter for the relevant window.

Excluded serial numbers 8107 and 8169. These two aircraft are exempt from the reinforcement requirement but still subject to the recurring inspection. An operator of one of these aircraft might mistakenly think they have no obligation at all, but they must still do the SSI Task. The exclusion is narrow; it likely reflects that these aircraft already have a different frame configuration or have already been modified.

Interim action risk. The AD says it is an interim action because the cause investigation was still in progress. That means the requirements may change. An operator who spends money on the reinforcement now could later be told that a different modification is needed, or that the reinforcement is no longer required. There is no guarantee of stability.

Landings vs. months interval. The recurring inspection uses 2,400 landings or 72 months, whichever occurs first. For an aircraft that does many landings per year, the landing limit will bind. For a low‑utilisation aircraft, the calendar limit binds. Both must be tracked. If an operator relies only on landings and misses the 72‑month deadline, they are non‑compliant even if they have done only 100 landings in that period.

No Australian repair path. The AD requires an EASA‑approved repair solution for cracks. It does not offer an alternative CASA‑approved solution. That means if EASA is slow, the aircraft stays grounded. Operators may need to plan for possible delay and have a contingency maintenance schedule.

Service bulletin revision dependency. The reinforcement must be installed per SB-228-273 original or a later EASA‑approved revision. If a later revision is not EASA‑approved, the operator cannot use it. Checking the approval status of later revisions is an extra due‑diligence step.

Effective date versus amendment date. The amendment was signed on 24 April 2009 but became effective on 4 June 2009. The compliance times (e.g., “within 800 landings after the effective date”) start from 4 June, not the signature date. Anyone who mistakenly used the signature date would be out of compliance.

Compliance is a sequence of steps that an operator must tailor to their aircraft. Step one: confirm the aircraft model and serial number against the applicability table. If the aircraft is a model 228-100, 101, 200, 201, 202, or 212, and the serial number falls within 7011-7168 or 8012-8245 (excluding 8107 and 8169), then the full AD applies. If it is any other serial number or model, only the recurring inspection applies (Requirement 4). Operators of the excluded serials must still do the recurring inspection per Requirement 4.

Step two: for aircraft in the applicable serial range, determine as of the effective date whether the aircraft has accumulated 120 or more short‑field landings in its last 1,200 landings before the effective date. This requires a review of flight records. Short‑field landings must be classified using the 1,500‑foot/50‑foot obstacle definition. If the operator does not have accurate records, they may assume the aircraft is in the high‑stress group to be safe, but that will commit them to the reinforcement requirement even if it was not actually needed. Alternatively, they may try to reconstruct the landing history from flight logs, but that is difficult.

Step three: schedule the initial inspection. For high‑stress aircraft (120+ short‑field landings), the inspection under SSI Task 53.37 must be done within 800 landings after the effective date. For lower‑stress aircraft (fewer than 120), the inspection must be done within the compliance schedule defined in the manual. The manual likely specifies a threshold based on flight cycles or hours, so the operator must obtain that schedule.

Step four: act on the inspection results. If no cracks found, high‑stress aircraft must install the reinforcement before accumulating 800 landings after the effective date. That means the installation may be done concurrently with the inspection or later, but before the deadline. Lower‑stress aircraft have no reinforcement requirement unless cracks are found. If cracks are found in any aircraft, the operator must obtain an EASA‑approved repair solution and complete the repair before further flight.

Step five: after the initial action, repeat the SSI Task at intervals not exceeding 2,400 landings or 72 months, whichever comes first. There is no end date; this is a recurring obligation for the life of the aircraft unless the AD is superseded.

Step six: maintain records. The operator must keep records of the short‑field landing count, the inspection reports, the reinforcement installation records (including service bulletin revision used), and any repair approvals. These records must be available for CASA inspection.

Step seven: if the aircraft is operated under an air operator certificate, the operator must update the maintenance control manual and the continuing airworthiness management exposition to reflect this AD and to ensure that the inspection and reinforcement tasks are captured in the maintenance schedule.

Step eight: communicate with the maintenance organisation. Provide them with a copy of the AD and the service bulletin. Confirm that they have the required manuals and EASA repair approval capability.

Because the AD is interim, operators should monitor CASA’s AD register for any superseding directives. They should also monitor RUAG service bulletins for possible permanent repairs or revised inspection intervals. Despite the AD’s interim label, the obligations remain in force until formally changed.