AD/CESSNA 560/10 - Angle of Attack System

The Directive applies to a narrow, identifiable set of aircraft and a defined group of actors who bear the operational and compliance responsibilities.

Aircraft owners/operators and registrants: The Applicability clause lists Model 560 aeroplanes, serial numbers 560‑0001 through ‑0538 inclusive. Only those aeroplanes fall within the Directive’s scope; operators of other serial numbers are not covered by the text provided.

Maintenance organisations and maintenance personnel: The Directive requires performance of a functional test and calibration in accordance with the specified Cessna Alert Service Letters (ASLs). That places work on maintenance providers who will have to follow the ASL procedures, including any tools, jigs, calibration settings and test protocols the ASLs require (Requirement 1; ASL references). The Directive also notes that Maintenance Manual Revision 24 of Cessna 560 Maintenance Manual 56MM has been changed to reflect the ASLs' intent for maintenance actions and periodic inspections, indicating that maintenance personnel must work with the revised maintenance manual (Note 1).

Operators responsible for flight operations and documentation: Those who maintain the AFM must amend the Limitations Section by removing the specifically quoted warning once the Requirement 1 actions are completed (Requirement 3). That alters operational documentation that flight crews and operators rely on.

Regulatory and manufacturer contacts: The Directive is issued by the Civil Aviation Safety Authority (CASA) delegate (signature block: James Coyne), making CASA the issuer; however, the Directive directs submission of test data to a Cessna contact in Wichita, Kansas (Glenn Todd, Citation Customer Support Engineer) and provides direct US contact details (Requirement 2 and contact block). This creates an administrative interface between Australian-registered (or other) operators and the US manufacturer for data collection.

Timing actors: The compliance timeframes allocate obligations to operators: Requirement 1 within six months, Requirement 2 within 30 days after the test, and Requirement 3 within 30 days after completing Requirement 1 (or within 30 days after the effective date, whichever is later) (Compliance). AD/CESSNA 560/9 is to be cancelled six months after the effective date, changing the obligations of operators who had been complying with the prior AD (Background).

There is no statement in the Directive text of penalties or enforcement agencies beyond the Directive’s effective date, and no monetary sanctions or administrative procedures are specified in the text provided.

Duties imposed by the Directive are stated in three numbered requirements, with explicit compliance schedules and reporting obligations.

Requirement 1 (functional test and calibration): If not previously accomplished in accordance with the optional terminating action of AD/CESSNA 560/9 (FAA AD 2007‑23‑13), the operator must carry out a functional test of the AOA system and adjust the calibration settings as applicable. The test and calibration must follow ASL560‑34‑34 (for single AOA systems) or ASL560‑34‑35 (for dual AOA systems), both Revision 3, both dated 6 March 2008, including attachments (Requirement 1). Successfully performing these actions in accordance with the Directive terminates the need for the placard installation required by AD/CESSNA 560/9.

Requirement 2 (reporting): If the Requirement 1 actions have not previously been accomplished under the terminating action, the operator must submit the AOA system test data report for the functional test to the named Cessna contact (Glenn Todd). The report must include the AOA test data, aeroplane serial number, registration number, and the number of landings and flight hours on the aeroplane. This reporting obligation must be met within 30 days after performing the functional test (Requirement 2).

Requirement 3 (AFM amendment): For aeroplanes on which Requirement 1 has been completed, the operator must revise the Limitations Section of the AFM by removing the specified warning about stick shaker activation. This must be done within 30 days after completing Requirement 1 actions or within 30 days after the effective date of the Directive, whichever occurs later (Requirement 3).

Rights and acceptances stated in the text:

• Actions performed before the Directive’s effective date in accordance with ASL560‑34‑34 or ASL560‑34‑35 Revision 1 or Revision 2 are considered acceptable for compliance with the corresponding action specified in the Directive (Actions accomplished before the effective date clause). This gives operators credit for prior compliance under earlier ASL revisions.
• Later revisions of the ASLs approved by the FAA as an Alternate Method of Compliance (AMOC) to FAA AD 2008‑26‑04 are expressly considered acceptable for compliance with the equivalent Requirements of this Directive (Requirement 3 clause). This creates an avenue for using FAA‑approved AMOCs to satisfy the Directive’s requirements.

Operational consequence stated: accomplishing the functional test, adjusting calibration and submitting the test data as specified "terminates the requirement for the placard installation required by AD/CESSNA 560/9 (FAA AD 2007‑23‑13)" (Requirement 1). The Directive thus substitutes the test-and-report regime and AFM amendment for the placard that had been required under the prior AD.

Compliance timing duties are explicit: Requirement 1 within six months; Requirement 2 within 30 days of the test; Requirement 3 within 30 days of completing Requirement 1 or within 30 days after the effective date, whichever is later (Compliance).

The document does not articulate appeals, waiver procedures, or civil penalties in its text; it does, however, reference FAA ADs and FAA approval pathways for later ASL revisions (AMOC), suggesting an acceptance mechanism for alternative compliance determined by the FAA.

The text of AD/CESSNA 560/10 sets out mandatory technical and reporting requirements and precise compliance deadlines, but it does not specify monetary penalties, demerit schemes, or a step‑by‑step enforcement process in the text provided. The Directive states an effective date (12 March 2009) and prescribes compliance times for the three Requirements (Compliance). It also identifies that the Directive supersedes AD/CESSNA 560/9, which will be cancelled six months after the effective date (Background). Those temporal commitments create clear deadlines that operators are required to meet.

What the Directive contains relevant to enforcement:

• Effective date: "This Airworthiness Directive becomes effective on 12 March 2009" (Compliance). That date sets when the legal obligation to comply with the Directive’s requirements begins.
• Supersession and cancellation: The Directive "supersedes AD/CESSNA 560/9 which will be cancelled six months after the effective date of this Directive" (Background). That changes which mandatory actions remain in force and which do not after the stated periods.
• Compliance times: The Directive prescribes discrete deadlines for each Requirement (Requirement 1 within six months; Requirement 2 within 30 days after the functional test; Requirement 3 within 30 days after completion of Requirement 1 or within 30 days after the effective date, whichever is later) (Compliance). These are the operative enforcement triggers in the text.

What the Directive does not contain (in the provided text):

• The Directive does not list fines, suspension processes, or criminal penalties. It does not set out an administrative enforcement regime within the text provided.
• The Directive does not set out procedures for enforcement actions, notices of non‑compliance, rectification periods, or an appeal or review mechanism.

Practical enforcement implications that follow from the Directive’s content (textual inferences only):

• Because the Directive prescribes specific maintenance actions, documentation changes and a reporting obligation to a manufacturer contact, compliance will be visible in maintenance records and in receipt of the report by the named contact. The text requires the submission of test data within 30 days (Requirement 2), creating an observable compliance artefact.
• The Directive’s statement that completion of the specified actions "terminates the requirement for the placard installation required by AD/CESSNA 560/9" (Requirement 1) indicates that, following proper compliance, operators may remove a previously required placard and must reflect changes in the AFM (Requirement 3), again creating documentary evidence of compliance.

Because the text does not itself set penalties or describe CASA enforcement mechanisms, readers should treat the Directive’s compliance deadlines and reporting obligations as mandatory technical directions, and should consult the administering regulator or statutory enforcement provisions outside this text for the specific legal consequences of non‑compliance. The Directive’s own text does not expand on that.

The Directive explicitly cross‑references previous and parallel regulatory instruments, creating defined interactions with FAA airworthiness directives and Cessna service documentation.

Link to prior domestic AD: The Directive "supersedes AD/CESSNA 560/9 which will be cancelled six months after the effective date of this Directive" (Background). AD/CESSNA 560/9 had mandated temporary AFM changes and a warning placard, and contained an optional terminating action. By superseding AD/CESSNA 560/9 and setting out that completion of the Requirement 1 actions terminates the placard obligation imposed by AD/CESSNA 560/9, the Directive changes the set of contemporaneous mandatory requirements for the relevant aircraft (Requirement 1; Background).

References to FAA ADs: The Directive notes that AD/CESSNA 560/9 mandated the technical requirements of FAA AD 2007‑23‑13 and refers also to FAA AD 2008‑26‑04 (Background; Note 2). It further states that "later revisions of the above ASLs, approved by the FAA as an Alternate Method of Compliance (AMOC) to FAA AD 2008‑26‑04, are considered acceptable for compliance with the equivalent Requirements of this Directive" (Requirement 3 clause). That creates an explicit conduit whereby FAA approvals (AMOCs) for subsequent ASL revisions can be relied on to satisfy the Directive’s requirements. The Directive thus recognises the FAA’s AMOC approvals as a permissible pathway to compliance for this Australian AD.

Interaction with manufacturer maintenance documentation: The Directive notes that Maintenance Manual Revision 24 of Cessna 560 Maintenance Manual 56MM has been changed to reflect the intent of the ASLs for maintenance actions and periodic inspections of the AOA/Stall Warning System (Note 1). This ties the Directive to the manufacturer’s maintenance manual and suggests that operators who follow the updated maintenance manual are working towards compliance with the Directive’s maintenance intent.

Acceptance of prior compliance: The Directive expressly states that actions accomplished before the effective date in accordance with ASL560‑34‑34 or ASL560‑34‑35 Revision 1 or Revision 2 are considered acceptable for compliance with the corresponding action in the Directive (Actions accomplished before the effective date clause). That creates a temporal interaction: prior work done under earlier ASL revisions is carried forward, avoiding duplicative work for operators who already complied.

Geographical/administrative interface: Although this instrument is issued by the Civil Aviation Safety Authority (signature block), it directs the submission of the required AOA test data report to a Cessna representative in Wichita, Kansas, USA, providing US postal, email and fax details (Requirement 2). This establishes an administrative interaction across national jurisdictions between the Australian issuing authority’s Directive and the US manufacturer’s data collection processes.

What the text does not specify: The Directive does not set out how its requirements interact with other domestic statutory enforcement mechanisms or administrative appeal procedures. The Directive also does not mention interactions with insurance, commercial contracts, or operational authorisations; such interactions are therefore not addressed in the text provided.

The Directive itself contains internal information about its relationship to earlier documents and acceptable alternative documentation, which constitutes the amendment history accessible in the text.

Effective date and supersession:

• The AD becomes effective on 12 March 2009 (Compliance).
• It supersedes AD/CESSNA 560/9 and states that AD/CESSNA 560/9 "will be cancelled six months after the effective date of this Directive" (Background). That is the principal amendment action in the text: the new Directive replaces the prior AD and sets a termination date for the earlier instrument.

Service letter revisions accepted:

• The Directive mandates ASL560‑34‑34 and ASL560‑34‑35, both Revision 3 dated 6 March 2008, as the operative service documents for Requirement 1 (Requirement 1). It also accepts actions accomplished prior to the Directive’s effective date if done in accordance with Revision 1 or Revision 2 of those ASLs (Actions accomplished before the effective date clause).
• The Directive additionally accepts "later revisions of the above ASLs, approved by the FAA as an Alternate Method of Compliance (AMOC) to FAA AD 2008‑26‑04" as acceptable for compliance with the equivalent Requirements of this Directive (Requirement 3 clause). This creates a forward‑looking amendment pathway: FAA‑approved later ASL revisions can be relied upon to satisfy the Directive.

Maintenance manual update:

• The Directive notes that Maintenance Manual Revision 24 of Cessna 560 Maintenance Manual 56MM "has been changed to reflect the intent of the ASLs for the maintenance actions and periodic inspections of the AOA/Stall Warning System" (Note 1). This documents an accompanying change to the manufacturer’s maintenance manual that aligns with the ASLs and the Directive’s requirements.

Relationship to FAA ADs:

• The Directive describes AD/CESSNA 560/9 as having mandated the technical requirements of FAA AD 2007‑23‑13, and also refers to FAA AD 2008‑26‑04 (Background; Note 2). By referring to those FAA ADs, the Directive places itself in a lineage of regulatory actions relating to the same technical issue, and documents that the current Directive is the Australian instrument implementing the FAA‑originated technical requirements, while also accepting FAA AMOC approvals as acceptable for compliance.

No statutory amendment text: The AD as presented does not include text amending other legislative instruments or regulations directly; instead it identifies earlier ADs and service letters and defines which revisions or approvals will be accepted going forward. The cancellation of AD/CESSNA 560/9 six months after the effective date is the explicit change to the AD corpus recorded in the Directive.

The text of AD/CESSNA 560/10 contains no litigation history, judicial references, or mention of legal proceedings. It does not record any court cases, administrative appeals, or adjudicative decisions related to the Directive. The document confines itself to technical requirements, applicable aircraft serial numbers, compliance times, acceptance of prior ASL revisions, and administrative reporting instructions.

What the text does state that is relevant to the absence of litigation history:

• It supersedes an earlier AD (AD/CESSNA 560/9) and changes the compliance landscape by cancelling that earlier AD six months after the effective date (Background). The text does not indicate any contestation or legal challenge to that administrative change.
• It accepts prior compliance actions performed under earlier ASL revisions (Revision 1 and Revision 2) and accepts later ASL revisions approved by the FAA as AMOCs for the FAA AD as acceptable for compliance (Actions accomplished before the effective date clause; Requirement 3 clause). These procedural acceptances suggest administrative coordination rather than contested legal processes.

Implication for readers seeking litigation context: If one requires a record of any judicial or administrative reviews, appeals against the Directive, or enforcement actions taken under its terms, that information is not present in the Directive text and must be sought from external sources such as regulator enforcement records, court registries, or industry publications. The Directive itself does not supply any litigation or adjudicative history.

The Directive contains precise technical and administrative requirements whose practical effects can catch operators if the details are overlooked. Below are concrete points from the text that commonly produce compliance risk.

Narrow applicability , serial numbers only: The Directive applies only to Model 560 aeroplanes S/N 560‑0001 through ‑0538 inclusive (Applicability). Operators must check the aircraft serial number carefully. Aircraft outside that serial number range are not covered by this Directive; conversely, aircraft within the range are covered even if previously subject to different operator-level practices.

Timing sequencing traps:

• Requirement 1 must be carried out "within six months after the effective date" (Compliance). That sets a hard six‑month window to perform the functional test and calibration unless it was already done under the optional terminating action of AD/CESSNA 560/9. Operators who relied on the earlier AD’s placard or temporary AFM changes must schedule the test/calibration within six months even if they had been operating under temporary measures.
• Requirement 2 (the data report) is due within 30 days after doing the functional test (Compliance). Submitting the test report late would fail the report deadline even if the test itself was timely.
• Requirement 3 (AFM amendment) must be completed within 30 days after completing Requirement 1, or within 30 days after the effective date, whichever occurs later (Compliance). If Requirement 1 is completed early in the six‑month window, operators must ensure the AFM change follows promptly.

Administrative routing and international contact: The Directive requires submission of test data to a named Cessna representative in Wichita, KS (Glenn Todd) with a US postal address, email and two fax numbers provided (Requirement 2). For Australian operators used to sending compliance information to CASA, the requirement to submit the AOA test data to a US manufacturer contact is a logistical detail that must be followed precisely , the Directive specifies the recipient and contact details.

Credit for earlier ASL compliance limited to certain revisions and dates: Actions accomplished before the effective date in accordance with ASL560‑34‑34 or ASL560‑34‑35 Revision 1 or Revision 2 are acceptable (Actions accomplished before the effective date clause). However, only those earlier revisions and only actions completed before the effective date are credited. Operators who performed work under a different procedure or under an ASL revision not listed will need to check whether their work is within the specific prior revisions accepted.

Placard termination depends on completing test and reporting: The Directive states that accomplishing the functional test, adjusting calibration, and submitting the AOA system test data "terminates the requirement for the placard installation required by AD/CESSNA 560/9" (Requirement 1). That means an operator cannot remove the placard simply by performing the test , the report requirement must also be met. Both the technical action and the administrative reporting are required to be able to remove the placard.

AFM textual change is prescriptive: Requirement 3 requires removing a specific warning text from the Limitations Section of the AFM. Operators must ensure the AFM amendment precisely removes that quoted warning: "Warning: Stick Shaker May Not Activate Prior To Buffet/Roll‑Off If Airspeed Is Reduced Below The Appropriate Minimum Speed." Operators should also ensure the AFM amendment is documented and retained.

Acceptance of later ASL revisions only if FAA AMOC: The Directive allows later ASL revisions that have been "approved by the FAA as an Alternate Method of Compliance (AMOC) to FAA AD 2008‑26‑04" as acceptable for compliance with equivalent Requirements. That acceptance depends on FAA approval; ASL revisions without FAA AMOC approval are not automatically accepted under this Directive.

Maintenance Manual update relevance: The Directive notes that Maintenance Manual Revision 24 of Cessna 560 Maintenance Manual 56MM "has been changed to reflect the intent of the ASLs" (Note 1). Operators should ensure they are consulting the revised maintenance manual where relevant, as following an older manual revision could lead to non‑conformance with the ASL methods the Directive mandates.

No penalties stated: The Directive contains no explicit penalty clauses in the text provided. Operators should not assume the absence of penalties in this document equates to the absence of regulatory consequences; CASA or other applicable aviation laws outside this text may govern enforcement.

The Directive sets out a clear, three‑step compliance pathway with precise documentation and timing requirements. The following replicates the steps and the information required by the text.

Step 1 , Determine applicability and prior compliance:

• Verify the aeroplane serial number is within 560‑0001 through ‑0538 inclusive (Applicability).
• Check records to see whether the optional terminating action of AD/CESSNA 560/9 (FAA AD 2007‑23‑13) has already been accomplished for that aeroplane. If the optional terminating action was previously done, Requirement 1 may be considered already accomplished (Requirement 1).

Step 2 , Perform the functional test and calibration (Requirement 1):

• If the terminating action has not already been done, carry out a functional test of the AOA system and adjust calibration settings as applicable.
• Use the applicable ASL: ASL560‑34‑34 (for single AOA systems) or ASL560‑34‑35 (for dual AOA systems), both Revision 3 dated 6 March 2008, including attachments (Requirement 1).
• If the actions were already done before the Directive’s effective date using ASL Revision 1 or Revision 2, such actions are acceptable for compliance (Actions accomplished before the effective date clause).

Step 3 , Submit the AOA system test data report (Requirement 2):

• After performing the functional test, prepare and submit the AOA system test data report within 30 days of doing the test (Compliance).
• The report must include:
  • The AOA test data (as generated by the functional test),
  • The aeroplane serial number,
  • The aeroplane registration number,
  • The number of landings and flight hours on the aeroplane (Requirement 2).
• Submit the report to:
  • Glenn Todd, Citation Customer Support Engineer, Department 572, P.O. Box 7706, Wichita, KS 67277‑7706;
  • e‑mail: gatodd@cessna.textron.com;
  • fax: +1‑316‑517‑8500 or +1‑316‑206‑2337 (Requirement 2). Follow any procedural or data formatting instructions set out in the ASL for including or organising test data.

Step 4 , Revise the AFM Limitations section (Requirement 3):

• For aeroplanes on which Requirement 1 actions have been completed, revise the Limitations Section of the AFM by removing the exact warning: "Warning: Stick Shaker May Not Activate Prior To Buffet/Roll‑Off If Airspeed Is Reduced Below The Appropriate Minimum Speed" (Requirement 3).
• Do this within 30 days after completing Requirement 1 actions, or within 30 days after the effective date of the Directive if Requirement 1 has already been completed, whichever occurs later (Compliance).

Step 5 , Recordkeeping and maintenance manual alignment:

• Ensure maintenance records document the functional test, calibration adjustments, and the AFM amendment.
• Note that Maintenance Manual Revision 24 of Cessna 560 Maintenance Manual 56MM has been changed to reflect the ASLs’ intent; consult and use the revised maintenance manual as applicable (Note 1).

Step 6 , Use of alternate or later ASL revisions:

• If relying on a later revision of the ASLs, ensure that the later revision has been "approved by the FAA as an Alternate Method of Compliance (AMOC) to FAA AD 2008‑26‑04"; only then are later ASL revisions considered acceptable for compliance with the equivalent Requirements of this Directive (Requirement 3 clause).

Step 7 , Credit for earlier work:

• If the functional test and calibration were performed before the Directive’s effective date using ASL560‑34‑34 or ASL560‑34‑35 Revision 1 or Revision 2, treat those actions as compliant with the corresponding Requirement in this Directive. If so, record the documentation demonstrating that the earlier ASL revision and the date of performance align with the Directive’s acceptance (Actions accomplished before the effective date clause).

Step 8 , Consequences for placard and AFM items:

• On completing the functional test, calibration adjustments, and submitting the test report as specified, the requirement to maintain the placard previously required by AD/CESSNA 560/9 is terminated. Ensure the placard is removed only after both the technical and reporting obligations are satisfied (Requirement 1).

Timelines summary:

• Functional test and calibration: within six months after 12 March 2009 (Compliance).
• Test report submission: within 30 days after the functional test (Compliance).
• AFM amendment (removal of specified warning): within 30 days after completing Requirement 1 or within 30 days after the effective date, whichever occurs later (Compliance).

Operational checklist for an operator:

• Verify S/N applicability.
• Check whether prior terminating action was completed under AD/CESSNA 560/9.
• Schedule and perform ASL‑specified functional test and calibrations using the correct ASL revision or an FAA‑approved AMOC.
• Compile required data (AOA test data, S/N, rego, landings, hours).
• Submit the report to the named Cessna contact within 30 days.
• Amend AFM Limitations as required within the stated time.
• Keep all documentation to evidence compliance.

Following these steps in the order and within the timeframes set out in the Directive will satisfy the explicit Requirements contained in the text.