## Federal Aviation Administration



# AIRCRAFT CERTIFICATION SERVICE 

# Airworthiness Directives Manual May 17, 2010

U.S. Department of Transportation Federal Aviation Administration

FAA-IR-M-8040.1C

HQ04307QXMay 17, 2010 FAA-IR-M-8040.1C



### RECORD OF CHANGES FAA-IR-M-8040.1C Document No.

CHANGE SUPPLEMENTS OPTIONAL CHANGE SUPPLEMENTS OPTIONAL
TO TO BASIC BASICMay 17, 2010 FAA-I R-M-8040.1 C

FOREWORD

Airworthiness Directives (ADs) are substantive regulations issued by the Federal Aviation Administration (FAA) in accordance with Title 14 of the Code of Federal Regulations (14 CFR) part 39. ADs are issued when (1) an unsafe condition exists in the product (i.e., aircraft, aircraft engine, propeller, or appliance), and (2) the condition is likely to exist or develop in other products of the same type design. Once an AD is issued, no person may operate a product to which the AD applies except in accordance with the requirements of that AD.

Similarities with the Corrective Action Request (CAR) Process Initiate CARs for nonconformances when:



# · The nonconformance is of such a nature that management wants to ensure that the nonconformance never recurs; or



# · The nonconformance is systemic in nature and requires a root cause analysis to ensure the corrective action prevents recurrence.

'D~\..-J C)~

~ David W. Hempe Manager, Aircraft Engineering Division 

# ~t: )jdL

Assistant Chief Counsel for Regulations

Changes to this manual shall be made in a timely manner as conditions in the workplace warrant and as opportunities for improved quality are discovered

i (and ii)

- - --May 17, 2010 FAA-IR-M-8040.1C

Table of Contents

Chapter 1. General Information .................................................................................................. 1
1. Purpose of this Manual. .................................................................................................... 1
2. Audience. ............................................................................................................................ 1
3. Where Can I Find This Manual? .................................................................................... 1
4. Cancellation. ...................................................................................................................... 1
5. Explanation of Changes. ................................................................................................... 1
6. Effective Date. ................................................................................................................... 2

Chapter 2. Laws that Apply to ADs ............................................................................................ 3
1. Purpose of this Chapter. ................................................................................................... 3
2. Use of Legal Terminology. ............................................................................................... 3
3. Definitions. ......................................................................................................................... 3
4. Administrative Procedure Act (APA). ............................................................................ 4
5. FAA Regulations. .............................................................................................................. 6
6. Regulatory Findings Addressed in ADs. ......................................................................... 6

7. Department of Transportation (DOT) Rulemaking Policies and Procedures. ........... 8

Chapter 3. Ex Parte Contacts .................................................................................................... 11
1. General. ............................................................................................................................ 11
2. DOT Policy. ..................................................................................................................... 11
3. Improper Ex Parte Contacts. ......................................................................................... 11
4. Procedures for Ex Parte Contacts. ................................................................................ 12
5. Precautions and Practices. ............................................................................................. 13

Chapter 4. Determining Type of AD Action............................................................................. 15
1. Purpose of this Chapter. ................................................................................................. 15
2. When to issue ADs. ......................................................................................................... 15
3. Advance Notice of Proposed Rulemaking (ANPRM). ................................................. 15
4. Notice of Proposed Rulemaking (NPRM). .................................................................... 15
5. Final Rule after NPRM (FRAN). ................................................................................... 15
6. Emergency ADs. .............................................................................................................. 16

7. Final Rule; Request for Comments (FRC). .................................................................. 16
8. Considerations for IAR and Emergency ADs. ............................................................. 17

iiiMay 17, 2010 FAA-IR-M-8040.1C

9. Sensitive Security Information (SSI) AD Action.......................................................... 18
10. Other Types of Documents Published in the Federal Register .................................... 18

Chapter 5. Changing Existing AD Actions............................................................................... 19
1. Purpose of this Chapter. ................................................................................................. 19
2. “Supplemental notice of proposed rule making (SNPRM); reopening of comment period”.

............................................................................................................................... ......... 19
3. “Proposed rule; withdrawal”. ........................................................................................ 19
4. “Proposed rule; extension of the comment period”. .................................................... 19
5. Superseding AD Actions. ................................................................................................ 19
6. Revising AD Actions. ...................................................................................................... 20

7. “Notice of Proposed Rulemaking (NPRM); correction” or “Final rule; correction”. 21
8. Rescinding (Removing) an Existing AD. ....................................................................... 21
9. Petition for Exemption. .................................................................................................. 22

Chapter 6. Drafting, Coordinating, Issu ing, Publishing, and Distributing ADs................... 23
1. Purpose of this Chapter. ................................................................................................. 23
2. AD Worksheet. ................................................................................................................ 23
3. Drafting References and Tools. ..................................................................................... 24
4. AD Templates.................................................................................................................. 24
5. Review and Coordination of AD Action. ...................................................................... 25
6. Administrator’s AD Alert. ............................................................................................. 25

7. Signature of AD Action. ................................................................................................. 26
8. Continued Airworthiness Notification to the International Community (CANIC). . 26
9. Publication of AD Action. ............................................................................................... 26
10. Distribution. ..................................................................................................................... 27
11. Exchange of Continuing Airworthiness Information. ................................................. 28
12. Biweekly Supplements. ................................................................................................... 29

Chapter 7. Preamble of an AD ................................................................................................... 31
1. Purpose of this Chapter. ................................................................................................. 31
2. Information Headings..................................................................................................... 31
3. AD Numbering. ............................................................................................................... 32
4. Subject Heading. ............................................................................................................. 34

ivMay 17, 2010 FAA-IR-M-8040.1C

5. Summary. ......................................................................................................................... 36
6. Discussion. ........................................................................................................................ 36

7. Relevant Service Information. ....................................................................................... 36
8. Differences Between this [Propo sed] AD and Service Information. .......................... 36
9. Costs of Compliance. ...................................................................................................... 36
10. Interim Actions. ............................................................................................................... 37

Chapter 8. Rule Portion of an AD ............................................................................................. 39
1. Purpose of this Chapter. ................................................................................................. 39
2. Headings in the Rule Portion of an AD. ........................................................................ 39
3. Product Identification. .................................................................................................... 40
4. Effective Date. ................................................................................................................. 40
5. Affected ADs. ................................................................................................................... 41
6. Applicability. ................................................................................................................... 41

7. ATA/JASC Code. ............................................................................................................ 45
8. Compliance. ..................................................................................................................... 45
9. Corrective Action. ........................................................................................................... 49
10. Using Notes. ..................................................................................................................... 52
11. Describing Special Flight Permits. ................................................................................ 52
12. Alternative Methods of Compliance (A MOCs) in Revision or Supersedure AD Actions.

............................................................................................................................... .......... 52
13. Authorization to Perform Work. ................................................................................... 53
14. Reporting Requirements. ............................................................................................... 53
15. Material Incorporated by Reference. ............................................................................ 54
16. Signature Block. .............................................................................................................. 54
17. Specialized AD Subjects. ................................................................................................ 54

Chapter 9. Public Comments ..................................................................................................... 57
1. Purpose of this Chapter. ................................................................................................. 57
2. APA Requirement. .......................................................................................................... 57
3. Where to Find Comments in the Docket. ...................................................................... 57
4. No Comments Received.................................................................................................. 57
5. Comment Disposition. ..................................................................................................... 57
6. Comments to FRCs. ........................................................................................................ 57

vMay 17, 2010 FAA-IR-M-8040.1C

7. Late Comments. .............................................................................................................. 58
8. How to Disposition Comments. ...................................................................................... 58

Chapter 10. Incorporation by Reference and Appendices...................................................... 61
1. Purpose of this Chapter. ................................................................................................. 61
2. Incorporation by Reference (IBR). ............................................................................... 61
3. Incorporating Material as Appendices. ........................................................................ 61

Chapter 11. AD Docket............................................................................................................... 63
1. Purpose of this Chapter. ................................................................................................. 63
2. Maintaining the AD Docket. .......................................................................................... 63
3. AD Docket Contents. ...................................................................................................... 63
4. Proprietary Data in AD Dockets. .................................................................................. 63

Appendix A. Acronyms ............................................................................................................ A-1

viMay 17, 2010 FAA-IR-M-8040.1C

Chapter 1. General Information

1. Purpose of this Manual. This manual provides policy and guidance for the drafting, issuance, and di stribution of ADs. It is intended to explain the laws that apply to ADs, procedures for writing an AD, and policies on key AD-related issues.

2. Audience. Managers and staff of the FAA Ai rcraft Certification Service, including any persons designated by the administrator, and organizations associ ated with the AD process in accordance with 14 CFR part 39.

3. Where Can I Find This Manual? You can find this manual on the FAA Regulatory and Guidance Library (RGL) Web site at http://rgl.faa.gov under the category of Orders/Notices.

4. Cancellation. This manual cancels FAA-IR-M-8040.1B, Airwor thiness Directives Manual, dated May 28, 2008.

5. Explanation of Changes. This version of the manual presents a complete revision of the previous AD Manual, FAA-IR-M8040.1B. This change –

a. Uses plain language whenever possible.

b. Consolidates the discussion of si milar subjects into one location.

c. Avoids excessive use of legal terminology and citations, unless use of the term is the only term that can be used to achieve the desired end.

d. Clarifies ex parte policy.

e. Establishes when the AD process begins and ends.

f. Removes format, text, and style guidance alread y prescribed in the Office of the Federal Register (OFR) Document Drafting Handbook (DDH).

g. Requires use of a standardized AD worksh eet, AD templates, and other documents (forms/templates) used in the AD process.

h. Removes information (e.g., examples) wher e guidance or boilerplate language is provided in the standardized AD template(s).

i. Provides guidance for economic/regula tory aspects of the AD worksheet.

j. Clarifies who must coordinate on the AD worksheet and AD action.

1May 17, 2010 FAA-IR-M-8040.1C

k. Emphasizes which office is responsible fo r drafting, coordinating, and issuing an AD action related to an appliance.

l. Explains the different types of a “Final Rule; Request for Comments” (FRC) AD.

m. Standardizes how we a ddress on-condition costs.

n. Clarifies how to write the s ubject, product identification, a nd applicability statements when an AD action is applicable to a S upplemental Type Certificate (STC) or Parts Manufacturer Approval (PMA).

o. Clarifies when and how to use the term ‘series’ in the s ubject, product iden tification, and applicability statements.

p. Establishes how to identify commenters.

q. Emphasizes AD corrective actions are not considered preventative maintenance.

r. Adds guidance for drafting Sensitive Security Information AD actions.

s. Corrects guidance associated with where to send an Administrator's AD Alert.

t. Removes general discussion related to al ternative method of compliance (AMOC).

u. Removes the requirement for distributing paper copies for certain types of ADs.

v. Establishes what documentation is placed in the Federal Docket Management System (FDMS).

w. Removes the processes for technical deci sionmaking, AD manual changes, AD process measurement, and continuous AD process improvement.

6. Effective Date. This manual, including use of the standardized AD worksheet and AD templates, is effective June 21, 2010.

2May 17, 2010 FAA-IR-M-8040.1C

Chapter 2. Laws that Apply to ADs

1. Purpose of this Chapter. This chapter describes the laws that apply to ADs, including the Administrative Procedure Act (APA), Executive Orders, and FAA regulations. This information is intende d to serve only as an aid to understanding the general purpose of the law and does not serve as a substitute for reference to the actual laws.

2. Use of Legal Terminology. Rulemaking is a legal process. For this reason it is common to find extensive use of legal terms in rulemaking documents. Use of legal termi nology is essential to communication between attorneys and in legal do cuments, but is not always required, mu ch less helpful, to non-lawyers. For this reason, in this manual we avoid exces sive use of unnecessary legal terminology and instead use plain language if th e equivalent legal meaning can be achieved. In addition, legal citations are moved to the footnotes to improve readability.

3. Definitions.

a. Rulemaking . The internal process used by agen cies to write and issue rules or regulations.

b. Actual Notice. A legal term to describe the act of an individual personally delivering a legal document to another person. In rulema king, the FAA can provide “actual Notice” by personal delivery of the rulemaking document or sending a copy by U.S. Postal Service or by facsimile.

c. Executive Order (E.O.). A law created/enacted by the Executive, Legislative or Judicial branches of government. The President of the Un ited States issues Executive Orders to convey policies, responsibilities, and procedures.

d. Informal Rulemaking. Unlike formal rulemaking that i nvolves adjudication (a trial-like hearing that uses witness testimony), a written r ecord, and a final decision; informal rulemaking pertains to agency decisions that are made without formal trial-like procedures. Informal rulemaking provides to the public Notice of prop osed regulatory actions and an opportunity to comment, which can be achieved by public he arings, conferences, and/or negotiations.

e. Statutes. A law or group of laws enacted by Cong ress that commands or prohibits some type of conduct, activity, or action.

f. Legislation. The process of making a new law or changing an existing law, which includes a proposal presented to Congress called a “bill.” Legislation in cludes the period during which Congress debates and consid ers the bill and the pr ocess of adopting the bill, which makes it law. Legislation can have many purposes: to re gulate, to authorize, to provide (funds), to sanction, to grant, to de clare or to restrict.

g. Substantive rules. Rules issued by federal agencies th at change the rights of the public to act in a specific manner, impose a burden or rest ore rights to act in a specific manner, which

3May 17, 2010 FAA-IR-M-8040.1C

do not apply to internal organiza tional issues. Substantive rules have the force of law and are codified (“published”) in the Code of Federal Regulations (CFR). Failure to comply with a substantive rule results in a vi olation of the law. ADs are subs tantive rules because they impose requirements on the regulated public to stop taking a specified action or require that a specific action be taken, and have the force of law.

4. Administrative Procedure Act (APA).

a. General. The APA 1 is a body of laws that, work ing together, provides minimum guidelines and rules that federal agencies are requ ired to follow when issuing a rule or changing existing rules that, if adopt ed, would impact the rights of the regulated public.

b. The APA governs both formal and informal rulemaking.

(1) An AD is a substantive rule and therefore must be issued in accordance with APA requirements because it imposes mandatory requir ements on the affected public that limit or restore rights to engage in certain activities. 2

(2) The APA allows a person who has been adve rsely affected by an agency action, such as an AD, to challenge the agency in court. 3 This is significant to pe rsons engaged in rulemaking because it means that if the FAA is challenged, and the court finds that the FAA was arbitrary and capricious, 4 the court can overturn the rulemaking or order that the FAA correctly repeat the entire rulemaking process.

c. Notice. The APA requires federal agencies to give the public Notice of its intent to add, change or remove information in a rule. Notice in forms members of the public of its intent to take an action that may impact their rights. For “n otice” to be meaningful, an agency should state what it proposes to change in the CFR and why the proposed change is necessary. 5 If the Notice published by the agency is inaccurate, confusing or unclear, it can be fairly argued before a court that the agency did not give adequate Notice. The FAA complies with the APA requirement by publishing Notice in the Federal Register

.
d. Opportunity to Comment. The APA also requires agencies to give the public an opportunity to participate in rulemaking actions. The FAA complies with this requirement by including a request for comments in the Notice or giving the date, time , and place for a public

1 Public Law 79-404, 5 U.S.C. § 551, et. seq.

2 5 U.S.C. § 551(4)

3 5 U.S.C. § 702

4 Arbitrary and capricious” is a legal term id entifying which test the court will apply when making its decision. Under this test, the court’s focus is usually on three questions: 1. Does the record support the factual conclusions on which th e rule is based? 2. Are the policy conclusions for the rule reasonable? and 3. How well did the ag ency explain its reasons for concluding as it did?

5 5 U.S.C. § 553(b)

4May 17, 2010 FAA-IR-M-8040.1C

meeting. The opportunity to comment is meaningf ul only if the public receives accurate Notice of the proposed action (so that they can res pond to the real issues), and the public has a reasonable period of time to submit their comments to the FAA. We meet these requirements by publishing a Notice in the Federal Register for public comment.

e. Publication. The APA requires agencies to publis h a Notice for all proposed rulemaking actions in the Federal Register unless an exception exists for doing otherwise. The Federal Register is similar to a legal newspaper where the public can review the ru lemaking activities of federal agencies. Rules issued by federal agencies are published in the Federal Register chronologically.

f. Good Cause Exceptions. The APA authorizes agencies to bypass the “Notice and Comment” requirements when we find “good caus e” to do so. Congress cr eated three good cause exceptions which should be used reluctantly, na mely: impractical, unnecessary, and contrary to the public interest. The failure of agency personn el to be efficient or responsible by exercising diligence in processing a rulemaking is not, in it self, an appropriate reason to use a good cause exception. The conditions under which each exception can be used are described below.

(1) Impracticable. This exception can be used when an urgent and unsafe condition exists and going through Notice and Comment rule making would increase risks to safety. Giving Notice would be “impracticable” if immediate ac tion must be taken because safety could be compromised during the time it woul d take to comply with “Noti ce and Comment” requirements. If you use the impractical exception, you must expl ain the urgency of the unsafe condition in the “Supplementary Information” section of the AD preamble. In addition, the compliance time in the AD must reflect the urgency or describe the facts that drive the expedited processing. Process ADs quickly to be consistent with the determ ination of “impracticab ility,” which denotes urgency of some type. If you ca nnot present a viable reason for the expedited processing, issue an NPRM.

(2) Unnecessary. This exception can be used when the general public has little or no particular interest in the pr oposed change. We use this just ification for minor corrections, clarifications, and editorial cha nges. We may use this justification also for ADs on products that have a U.S. type certificate, but are not installed on U.S. regist ered aircraft. In this case, no person would be affected by the AD because only operators of U.S. registered aircraft are required to comply with an AD. The “unnecessary” exception is inappropriate for use if the AD reduces regulatory requ irements, provides another method of compliance or removes a regulation from 14 CFR. Under these circumstances, you should comply with “Notice and Comment” requirements.

(3) Contrary to the Public Interest. This exception is generall y not used for ADs. The purpose of this exception is to excuse an agen cy from the Notice requi rement if providing advance Notice would defeat the purpose of th e agency action. For example, issuing advance Notice that the government is c ontemplating financial controls could cause public reactions so excessive that the financial system could be pl aced in jeopardy. In such a case, it would be contrary to the public interest to publish a dvance Notice of the gove rnment’s intentions.

5May 17, 2010 FAA-IR-M-8040.1C

g. Beyond the Scope of Notice. Generally, this phrase is used to address a requirement the agency is about to adopt, or ha s adopted, in a final rule that was not proposed in the published Notice. The phrase is used by agency personnel, courts or anyone point ing out a discrepancy between what was proposed and what is finally a dopted in the final rule . As discussed earlier, Notice is meaningful only if the actions proposed in the NPRM are basically the same as those being adopted by the final rule. But, a final rule is not required to perf ectly mirror the proposals made in the Notice if the added requirement is a logical outgrowth of a proposal made in the Notice.

(1) Example of “beyond the scop e” and logical outgrowth:

(a) If an NPRM proposes to re quire a modification to the tail wheel assembly for a certain aircraft, the final rule cannot also require modification to the main landing gear assembly, regardless if a commenter suggested it, because it’s beyond the scope of what was proposed. The additional modification to the main landing gear assembly is beyond the scope because it was not proposed in the NPRM. Also, reducing the complianc e time from that originally proposed would be considered beyond the scope of the NPRM.

(b) If an NPRM proposed a modification to the tail wheel assembly, and the FAA decided to add a requirement that the modification include an insp ection (that is not part of a standard inspection) to insure the modificati on was effective, the FAA could argue that the additional requirement for an insp ection is a logical outgrowth of the original proposal because modification without an insp ection would be unsafe.

(2) Consider additional rulemaking such as issuing a Supplemental NPRM 6 if the requirement adopted by the final rule is not a logical outgrowth of the NPRM. Changing the number, or type of items addressed in an AD from the number or type proposed in the Notice would be improper with out additional action.

5. FAA Regulations. The FAA regulations are found in 14 CFR. Regula tions govern conduct, directly or indirectly, related to aviation and have the forc e and effect of law. For example:

a. 14 CFR part 11. The regulations in part 11 explain the FAA's rulemaking process and include descriptions on how the public can fo llow and participate in the FAA’s rulemaking activities, who may file comments, what is an ex parte contact, etc.

b. 14 CFR part 39. This part provides the map for na vigating through the legal framework for ADs. Specifically, 14 CFR § 39.3 defines ADs to be legally enfo rceable rules that apply to aircraft, aircraft engines, propellers, and appliances.

6. Regulatory Findings Addressed in ADs.

a. Federalism (E.O. 13132). This Order requires that every ru le be assessed for its impact on state and local government. The purpose of th is EO is to minimize or prevent the Federal government from imposing regulations that unnecessa rily interfere with Stat e, local, and tribal

6 Refer to Chapter 5, paragraph 2

6May 17, 2010 FAA-IR-M-8040.1C

governments. Where possible, the federal governmen t is encouraged to work in cooperation with the State, local, and tribal governments. Ge nerally, ADs do not have an effect on other government entities. Aircraft operated by governme nt entities are typically public aircraft which are not subject to the Federal Aviation Regulations’ requirements for civil aircraft to have type and airworthiness certificates.

b. Significant Regulatory Action (E.O. 12866). 7 Send regulatory actions considered to have a “significant” impact to the Office of Management and Budget (OMB) for review. A “significant regulatory acti on” is defined as any regulatory action th at is likely to result in a rule that might:

(1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of th e economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities;

(2) Create a serious inconsistency or otherwise interfere with an ac tion taken or planned by another agency;

(3) Materially alter the budgetar y impact of entitlements, gr ants, user fees, or loan programs or the rights and obligatio ns of recipients thereof; or,

(4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this Executive order.

c. The Regulatory Flexibility Act (RFA). 8 The RFA is part of the economic evaluation that requires federal agencies to analyze the impact that thei r regulatory actions will have on small entities (i.e., small businesses, small non-pr ofit organizations, and small jurisdictions of government). If the regulatory im pact is likely to be “signifi cant,” which means it affects a “substantial number” of these small entities, th e agency considers less burdensome alternatives, or explains why a less burdensome alternative was not chosen. However, the agency is not required to adopt the less burdensome alternative.

d. Paperwork Reduction Act (PRA). 9 The PRA requires agencies to get approval from OMB for information collection activities, and to list a record of the approval in the Federal Register . The purpose of the PRA is to minimize pa perwork requirements. The control number assigned for ADs is “2120-0056.”

e. Congressional Review Act (CRA). 10 The CRA requires that, before a rule can take effect, the federal agency issuing the rule must submit a form titled “Submission of Federal Rules Under the Congressional Review Act” to Congress and the Comptr oller General. The form provides information that enables Congress to re view every new federal regulation issued by the

7 Executive Order 12866, 58 F.R. 51735 (Oct. 4, 1993).

8 5 U.S.C. §§ 601 et seq. 5 U.S.C. 602). Execu tive Order 12866 "Regulatory Planning and Review," signed September 30, 1993 (58 FR 51735)

9 Public Law 96-511, 94 Statute 2812 (1980) (current version codified at 44 U.S.C. §§3501-20)

10 5 U.S.C., Chapter 8, Sec. 251

7May 17, 2010 FAA-IR-M-8040.1C

government agencies and, if necessary, overrule it. This process enables Congress to maintain some transparency and oversight of the regulator y process. ADs are generally identified as nonmajor rules and are, therefore, r outine and not subj ect to review.

f. Intrastate Aviation in Alaska Act. 11

(1) Congress requires the FAA, “when modifying its regulations in a manner affecting intrastate aviation in Alaska, to consider th e extent to which Alaska is not served by transportation modes other than aviation, and to es tablish appropriate regu latory distinctions.” The statutory requirement applies only to regulat ions that could impact aviation transportation services occurring strictly within the state of Alaska (i.e., intrasta te), if aviation transportation is the only type of transportati on service provided, and the avia tion transportation in question serves one or more remotely located communities.

(2) When issuing an AD, consider whether compliance with the proposed action would interrupt aviation transportation to a remote Alas kan community that is not serviced by other modes of transportation. If you determine that the proposed regulatory action would have a negative impact on the availability of transporta tion services to a remotely located community, and the safety concerns outweigh the benefits of making transportation available, a statement to that effect might be sufficient. However, to be certain, contact your local Regional Airworthiness Counsel for guidance.

7. Department of Transportation (DOT) Rulemaking Policies and Procedures.

a. The DOT is the executive agency that acts as a hub to agencies that have a transportation related mission, such as the FAA. The role of th e DOT in FAA rulemaking is to act as a conduit between the FAA and all other federal agencies . The DOT monitors FAA actions against those of other agencies for possible duplication or conflicts. The DOT also reviews whether the FAA has complied with the statutory requirements es tablished by Congress, such as the E.O.s we describe in this section. 12

b. The DOT emphasizes that an opportunity for co mment must be provided for all proposed rulemaking actions unless the good cause exception applies or otherwise exempted. In addition, DOT policy states that when it is not possible to ask for comment pr ior to its issuance of Notice, an opportunity for the public to comment must be provided after the fina l rule is issued. The requirement to provide opportunity for comment also applies to emergency ADs published as a “Final rule; request for comment” ADs.

c. The DOT policy requires that the FAA make a determination for each rulemaking that involves a substantive rule, on whether the prop osed action would have an impact that is significant, non-significant, or constitutes an emergency. The criteria for considering a rulemaking to be significant includes matters havi ng a significant public interest, which are those that are estimated to cost $100 million or more per year, and those that result in a major increase in costs or prices for indi vidual industries. The FAA must notify the DOT of significant

11 Section 1205 of the FAA Reauthorization Act of 1996 (110 Stat. 3213)

12 44 FR 11034, February 26, 1979

8May 17, 2010 FAA-IR-M-8040.1C

regulatory action. For ADs, the determinations are made by the Chief Counsel’s Office for Regulations, AGC-200, and/or th e Associate Administrator fo r Aviation Safety, AVS-1.

9May 17, 2010 FAA-IR-M-8040.1C

Chapter 3. Ex Parte Contacts

1. General. An ex parte contact occurs when not all parties to an issue are present when the issue is discussed. In the context of AD rulemaking, whic h begins when the AD worksheet is signed, an ex parte contact is any oral or written comm unication between the FAA (this does not include FAA designees) and someone outside the government regarding the substance of a specific rulemaking that excludes other inte rested parties and takes place befo re the final rule is published or the NPRM is withdrawn. 13

2. DOT Policy. 14

a. Obtaining Information. Notwithstanding the general rest rictions placed on ex parte communication, DOT policy encourages agencies to contact the public directly when there is a need for factual information to resolve questions of substance and justif ication. This type of contact can be especially important in the develo pment of ADs where there is a specific need to obtain a thorough understanding of the products involved and relevant information can be obtained only from the design approval holder (DAH) or affected operators.

b. Draft Regulatory Document or Text. It is contrary to DOT and FAA policies to disclose to any private party outside the agency the proposed preamble or re gulatory text prior to publication. The purpose of the policy is to prev ent an unfair advantage to any one party or appear that the agency is seeking approval from an outside party. Be aware that no group or individual should be given special access to a ny information regarding rulemaking that is not available to all groups or individuals.

3. Improper Ex Parte Contacts.

a. Inappropriate Contacts. The standard for determining if an ex parte contact is improper is whether the communication affects the basic openness and fairness of the agency’s decisionmaking process, or if the communication influences the agency’s position. Prior to engaging in ex parte contact, consider whether the communica tion provides an unfair advantage to a party or creates the appearance of impropriety. As a genera l rule, if a person attempts to inappropriately influence your decision on a rulemaking, the co mmunication should be immediately terminated. An inappropriate ex parte c ontact could involve implied re wards for changing the rule.

b. Disclosing Rulemaking Document or Text. Both DOT and FAA policy prohibit disclosing any part of the rulemaking document, which includes the NPRM, Interim AD actions, Supplemental NPRM or Final Rule before they are made public. Disclo sing unpublished text can give the appearance that we are seeking approval from an outside party before issuing the AD. It also can give an advantage to some parties over other members of the public. For example, it can give some parties the advantage of knowing what the issues will be when the NPRM is published, thereby giving more time for them to prepare their comments. For this reason, the

13 14 C.F.R. § 11, App. 1

14 DOT Order 2100.2, Policies for Public Contacts in Rulemaking

11May 17, 2010 FAA-IR-M-8040.1C

public (including DAHs and operators) must not ha ve access to the rulemaking text before it is published in the Federal Register or put on display at the OFR.

c. Proprietary Information. This type of information should be held strictly confidential. Any questions concerning possible exceptions to a llowing disclosure should be coordinated with your Regional Airworthiness Counsel.

4. Procedures for Ex Parte Contacts.

a. Recording of Contact. For cases where communication involves a substantive issue related to a rulemaking, place a record of the contact, including any documents discussed or handed out, in the AD docket at Web site http://www.regulations.gov . An ex parte communication that takes place by telephone or email is still “ex parte communication” and a record of the contact must be placed in the AD docket. If you have any questions whether the contact was ex parte, contact you r Regional Airworthiness Counsel.

(1) For ex parte communication that occurs prio r to submittal of the AD worksheet to the appropriate directorate, record the contact on the AD worksheet.

(2) For ex parte communication that involve a substantive issue and occurs after submittal of the AD worksheet to the appropriate di rectorate, record the following information at a minimum:

(a) The date and time that the meeti ng or conversation takes place;

(b) A list of the participants;

(c) A statement of the topics discussed and wh at was said about each topic. This statement must be more than a list of the topi cs discussed. The purpose of the statement is to supply a record of the information relied upon during the rulemaking process so the FAA can provide a complete and thorough record for la ter judicial review. The thoroughness of the statement also will foster public trust for agency actions. And;

(d) Any commitments made by DOT/FAA personnel.

b. Referencing Contact in an AD Action. Reference ex parte contac ts that takes place after the AD worksheet has been signed that influenc ed the agency’s position by doing one of the following:

(1) Identify each ex parte contact along with a short discussion of the communication in the AD preamble, unless it is unreasonable to do so. For example, when we make a large number of ex parte contacts to get information fr om several DAHs and operators, identify the circumstances giving rise to the discussion, and just give a genera l reference in the AD preamble about how we gathered the information. You don’t have to discuss each individual contact; or

(2) Include the following statement in the AD preamble:

12May 17, 2010 FAA-IR-M-8040.1C

In preparation of Notices and immediately adopted final rules w ithout Notice, it is the practice of the FAA to obtain tec hnical information and information on operational and economic impacts from design approval holders and aircraft operators. A discussion of each contact or se ries of contacts influencing the agency's position can be found in the rulemaking docket.

5. Precautions and Practices.

a. Prior to Issuance of Notice. Ex parte contacts that take pl ace closer to the date that rulemaking will be published have a higher likel ihood of being considered inappropriate than those that take place early in th e process. If you have questions about specific contacts during this time, discuss them with your Regional Airworthiness Counsel.

b. During the Comment Period. Ex parte contacts duri ng the comment period are discouraged because interested parties can still subm it a written comment to the AD docket or present their concern at a public meeting announced in the Federal Register . If you discuss the NPRM with an outside party, limit the informati on to only that contained in the proposed rule and information made generally available dur ing a public meeting. Do not discuss other information or the factors the agency is consid ering as it prepares to issue the final rule.

c. After Comment Period Closes. Ex parte contacts after the comment period closes must also be recorded in the AD docket and, if the comment is significant, consider reopening the comment period. If you determine it would be help ful to meet with a person or group after the comment period closes, announce the meeting in the Federal Register

.
d. After Announced Meeting. Ex parte contacts after a m eeting that was announced to the general public are particul arly vulnerable to suspic ion. If a contact occurs outside of the meeting (as in stepping out in the hall to discuss the rule with one or more , but not all, participants), or after the meeting, you must place a reco rd of the contact in the AD docket.

e. International Airworthiness Authorities. Contacts with internat ional authorities are vulnerable because these people represent the offici al interests of their governments, and they often represent the interests of DAHs and operators in their countries. Limit your communications with them to exchanging fact s or to gaining mutual understanding or “harmonization” during any phase of the rulemaking process. To ensure harmonization, ask the representative not to distribute information or documents about the proposed rules to private individuals.

13May 17, 2010 FAA-IR-M-8040.1C

Chapter 4. Determining Type of AD Action

1. Purpose of this Chapter. This chapter describes:

a. When to issue ADs;

b. The primary types of AD actions the FAA issues; and

c. The standard APA procedure for issuing a final rule and the exceptions to this procedure, e.g., emergency AD and “Final ru le; request for comments.”

2. When to issue ADs. ADs are issued when (1) an unsafe condition exists in the product (i.e., airc raft, aircraft engine, propeller, or appliance), and (2) th e condition is likely to exist or de velop in other products of the same type design. Once an AD is issued, anyone who operates a product th at does not meet the requirements of the AD is in violation of 14 CFR § 39.7. If the unsafe condition only exists on one product and there are no other existing pr oducts of the same type design, accomplish corrective action through means other than an AD.

3. Advance Notice of Proposed Rulemaking (ANPRM). We issue an ANPRM when we woul d like to gather public input a bout the possibility of issuing a new rule before deciding to go forward with an NPRM. The ANPRM is valuable because the public can be the best source of that informati on. Using an ANPRM is also beneficial when we have identified a wide range of alternatives and want public help narrowing the choices down before issuing the NPRM. The ANPRM can be in th e form of a proposed rule or it can be a list of questions to obtain additional information to be used in developing an NPRM.

4. Notice of Proposed Rulemaking (NPRM).

a. An NPRM is the most common type of AD action. After an unsafe condition and when proposed corrective actions are identified, we publish an NPRM, which requests public comment on the proposed corrective action(s). After the co mment period closes, we reopen the comment period, withdraw the NPRM, or issue the final rule, taking into account all comments received. Change the rule as warranted by the comments.

b. After the OFR publishes an NPRM and the comment period closes, publish either a “Final rule” (i.e., Final rule after NPRM) or a “Proposed rule; withdraw al.” An NPRM becomes “stale” 16 months after the comment period clos es. Depending on the circumstances that caused the NPRM to become stale, you might have to issue a Supplemental NPRM.

5. Final Rule after NPRM (FRAN).

a. After the comment period closes, we prepare a final rule provided any changes made do not go beyond the scope of the proposed AD.

b. If we do not issue the final ru le within 16 months after the close of the comment period, consult with your Regional Airworthiness Counsel.

15May 17, 2010 FAA-IR-M-8040.1C

6. Emergency ADs. We issue an emergency AD when an unsafe conditi on presents an immediate risk to safety of flight, when it requires immediat e action by owners/operators, and when we cannot wait for publication in the Federal Register to address the unsafe conditi on. Consider the following:

a. Affected Parties. An emergency AD applies only to the people who receive “actual notice”. Those who do not physically receive th e AD in person, by U.S. mail or fax are not required to comply with it, even if they hear about it.

b. Follow-up Publication in the Federal Register

. Unless you immediately supersede 15 the emergency AD, it is critical to follow it with publication in the Federal Register as soon as possible, but no later than 30 days. Other th an very minor corrections (such as obvious typographical errors) and the addi tion of boilerplate language, cost of compliance, standard format, and material required for incorporati on by reference, the version published in the Federal Register as a final rule MUST BE IDENTICAL to the emergency AD. If an FRV differs from (but does not supersede) the emergency AD, it creat es two classes of persons required to comply: those who got the emergency AD and those w ho did not. The existence of two different corrective actions to the same unsafe condition make s it appear that one is insufficient or not as effective as the other one. Further, we coul d be creating another uns afe condition by causing such a situation to occur.

c. Changing an Emergency AD. To make a change to a prev iously issued emergency AD, we have three options:

(1) Issue an FRV that is identical to the em ergency AD, except for the changes identified in paragraph 7.b. above. This rule is effectiv e to all persons except those who received the emergency AD. After issuing that FRV, issue an IAR that supersedes the FRV and contains the corrected information.

(2) Issue an IAR that supersedes or revises the existing emergency AD and contains the corrected information.

(3) Issue a new emergency AD that supersedes or revises the existing emergency AD, followed by Federal Register publication of an FRV.

7. Final Rule; Request for Comments (FRC). When necessary in the interest of safety, we can issue a final rule immediately without first issuing an NPRM. Do not shorten compliance times artificially to fit the criteria of an FRC in an effort to avoid the notice requirement procedur es. The APA does not set a specific time limit for a rule to qualify for immediat e adoption. In general, we issue an FRC only when it is “impractical” to complete the notice requirement procedure because the compliance time for the required action is shorter than the time necessary for the public to comment and for us to publish the final rule 16

.

15 Refer to Chapter 5, paragraph 5

16 Refer to Chapter 2, paragraph 4f

16May 17, 2010 FAA-IR-M-8040.1C

b. Types of FRCs:

(1) Immediately Adopted Rule (IAR). This type of AD action is used when all of the following apply:

(a) The unsafe condition and our risk assessmen t indicates an immediate safety of flight problem;

(b) Good cause exists to say it is “impr actical” to comply with “Notice and Comment” requirements before issuing the AD;

(c) There are affected aircraft on the U.S. Register; and

(d) We can wait for publication in the Federal Register to address the unsafe condition and therefore do not need to issue an emergency AD.

(2) No-notice Final Rule (NFR). This type of AD action is used when:

(a) Good cause exists to say it is “unnece ssary” to comply with “Notice and Comment” requirements before issuing the AD (e.g., there are currently no affected aircraft on the U.S. Register and the public will have little or no interest in the AD); and

(b) There is not an immediate sa fety of flight problem.

(3) Federal Register Version of an Emergency AD (FRV). This type of AD action is used to make an emergency AD effective to all persons.

c. Remember that when an AD has not been pr eceded by an NPRM, we must make a “good cause” finding of “impractical” or “unnecessary” and specify that finding in the preamble.

8. Considerations for IAR and Emergency ADs. Sometimes the actions to correct an unsafe c ondition in an IAR and emergency AD involve both a short-term interim action (for example, repetitive inspections or operating restrictions) and a longer-term terminating action (for example, a modification). In these cases, the APA requires that we analyze each required action separately to determine whether we should give notice. If we can make an independent finding of “impracticability” 17 for the terminating action, we may include it as a requirement in the IAR and emer gency AD. If not, only include the short-term interim action in the IAR and emergency AD, t hough we may include the terminating action as an option. In other words, the APA does not perm it “bootstrapping” a long-term requirement into an IAR and emergency AD. For example,

a. If the terminating action is not immediatel y mandated, the public may comment on the terminating action, and the APA requires that we issue an NPRM before mandating the terminating action. (The FRC can include the terminating action as an option.)

b. If the level of safety provided by the inte rim action is inappropriate for long-term

17 Refer to Chapter 2

17May 17, 2010 FAA-IR-M-8040.1C

operation and the compliance time for the termin ating action is too short to allow for public comment, then we can justify impracticability for including the terminating action in the FRC.

9. Sensitive Security Information (SSI) AD Action. DOT Order 1600.75, “Protecting Sensitive Unclassifi ed Information (SUI),” provides policy and guidance for protecting sensitive unc lassified information we create or control. AD actions that relate to national transportation safety or secur ity issues fall within the scope of DOT Order 1600.75 and are defined as sensitive security information (SSI).

a. SSI is a designation unique to the DOT’s operating administrations and to the Department of Homeland Security. It applie s to information we obtain or develop while conducting security activities, including research and developm ent activities. Unauthorized disclosure of SSI would:

(1) Constitute an unwarranted invasion of privacy

(2) Reveal trade secrets or privileged or confidential information obtained from any person; or
(3) Be detrimental to transportation safety or security.

b. In general, persons have a duty to protect the information and then a need to know it before given access to SSI ADs. Use protectiv e measures to safeguard SSI ADs from uncontrolled release outside the FAA and indi scriminate dissemination within the FAA.

c. Issue a ‘Final rule; request for comments’ on ly after the compliance time specified in the ‘Sensitive Security Airworthiness Directive’ has passed. If no aircraft ar e on the U.S. Registry, only issue the ‘Final rule; request for comments’ AD. Do not mark or make reference to a sensitive security information AD action within the text of the AD. Follow this same process for MCAI-related ADs that contain SSI.

10. Other Types of Documents Published in the Federal Register

. The OFR DDH includes a list of other types of documents available for publication in the Federal Register . Contact your directorate AD focal poi nt (e.g., AD Coordinator) for more information about these other types of documents.

18May 17, 2010 FAA-IR-M-8040.1C

Chapter 5. Changing Existing AD Actions

1. Purpose of this Chapter. This chapter explains and defines how to ch ange an AD action through a correction, rescission, revision, withdrawal, or supersedure.

2. “Supplemental notice of proposed rule making (SNPRM); reopening of comment period”. After we issue an NPRM and the comment peri od has closed, we might need to reopen the comment period. The supplemental NPRM allows the public an additional opportunity to review and comment on the requirements.

a. Additional Burden to the Public. Sometimes we change the NPRM requirements, based on new information, before issuing the final rule. We use this AD action if the changed requirements add a burden to the public (by ex panding the applicability or shortening the compliance time, for example).

b. Request to Reopen Comment Period. Sometimes we reopen the comment period based on a request from the public.

3. “Proposed rule; withdrawal”. After we issue an NPRM, we sometimes become aware of new information that prompts us to withdraw the proposed rule. Withdrawing the NP RM constitutes only th at action, and does not prevent us from issuing another NPRM in the future.

4. “Proposed rule; extension of the comment period”. After we issue an NPRM and while the comment period is still open, we might need to extend the comment period. This AD action allows the pub lic additional time to review and comment on the requirements specified in the NPRM.

5. Superseding AD Actions. Superseding AD actions might be issued as an NPRM, final rule, FRC, or emergency AD. We issue a supersedure when we need to correct an error that affects the substance of the AD or to expand the scope of the existing AD. Examples in clude adding a part number, correcting a part number (when that part number actually exists), mandating compliance with additional service information, reducing compliance times, expand ing applicability, changing the methods of compliance, adding corrective actions, adding or changing inspection requirements, and adding mandatory terminating action.

a. Identifying Supersedures. A superseding AD gets a new amendment number and a new AD number; the previous AD is deleted from 14 CFR part 39.

b. Considerations for Writing Supersedures. Keep the following in mind when superseding an AD:

(1) When restating old compliance dates, be careful to limit them to the previous requirements only. When increasing applicability , do not use old compliance dates for newly

19May 17, 2010 FAA-IR-M-8040.1C

added products. On the other hand, do not omit pr ovisions of the previous AD that are intended to remain in effect until operators have complied with the requirements of the superseding AD. A careful “side-by-side” comparison of the prev ious AD and the new AD draft is essential.

(2) Remember to give instructions in the ame ndatory language in terms acceptable to the OFR. “Supersedure” is an internal FAA term.

(3) The preamble must indicate that we are superseding a previous AD.

c. Describing the Change in the AD. Include a discussion of each change in the AD that caused the supersedure. Be sure to consider whether the cha nge affects any compliance time.

d. Verification. When issuing a superseding AD to corre ct an error, directorate personnel must verify that the new AD action corrects the previous error by reviewing and coordinating on the new AD action. A record of the AD action corre cting the previous error can be found in the AD docket.

e. Metrics. Directorate personnel collect and addr ess metrics in QMS per AIR AOD, document, AIR-001-002.

6. Revising AD Actions. Revise an AD if the change is relieving in na ture, e.g., when we add an optional terminating action, reduce applicability, or co rrect an error that causes compliance to be impossible (e.g., non-existent part number). A revised AD cannot impose new requirements or expand the scope of an existing AD.

a. Identifying Revisions. A revised AD gets a new amendment number but retains its AD number with the addition of the revision number (for example, “2006-14-03 R1”).

b. Considerations for Writing Revisions. Keep the following in mind when revising an AD:

(1) When restating old compliance dates, be careful to limit them to the previous requirements only. Do not omit provisions of the pr evious AD that are intended to remain in effect. A careful “side-by-side” comparison of the previous AD and the new AD draft is essential.

(2) Remember to give instructions in the ame ndatory language in te rms acceptable to the OFR. Do not use “Revision,” it is an internal FAA term.

(3) The preamble must indicate that we are revising a previous AD.

c. Describing the Change in the AD. Include a discussion of each change in the AD. Be sure to consider whether the ch ange affects any compliance time.

d. Verification. When issuing a revised AD to correct an error, directorate personnel must verify that the new AD action corrects the prev ious error by reviewing and coordinating on the

20May 17, 2010 FAA-IR-M-8040.1C

new AD action. A record of the AD action correcti ng the previous error can be found in the AD docket.

e. Metrics. Directorate personnel collect and addr ess metrics in QMS per AIR AOD, document AIR-001-002.

7. “Notice of Proposed Rulemaking (NPRM); correction” or “Final rule; correction”. We issue a correction AD action when the chan ge has no effect on compliance with the AD. Examples include, but are not limited to, cha nges to the contact information, address or telephone number for obtaining service inform ation, or an incorrect AD docket number.

a. Identifying Corrections. A correction AD is not assigned a new amendment number or a new AD number because compliance is not affected.

b. Considerations for Writing Corrections. Keep the following in mind when correcting an AD:

(1) Remember to give instructions in the ame ndatory language in te rms acceptable to the OFR.

(2) The preamble must indicate that we are correcting a previous AD.

c. Describing the Change in the AD. Include a discussion of each change in the AD.

d. Verification. When issuing a correction AD to fix an error, director ate personnel must verify that the new AD action corrects the prev ious error by reviewing and coordinating on the new AD action. A record of the AD action correcti ng the previous error can be found in the AD docket.

e. Metrics. Directorate personnel collect and addr ess metrics in QMS per AIR AOD, document AIR-001-002.

8. Rescinding (Removing) an Existing AD. Rescinding an existing AD require s a rule change under 14 CFR pa rt 39. The standard procedure is to use the NPRM process to solicit public comme nt. Process the action as an IAR, if justified.

a. Identifying Rescissions. A rescission AD gets a new ame ndment number but retains its AD number with the addition of the revi sion number (for example, “2007-12-05 R1”).

b. Considerations for Writing Rescissions. Keep the following in mind when rescinding an AD:

(1) Check whether the AD being removed mentions or affects another AD in the system.

(2) Be sure that rescinding the AD does not leave an unsafe condition unresolved.

(3) The fact that all owners or operators have complied with an AD does not make the AD (the change in type design) unnecessary. Do not rescind an AD based on a DAH’s claim that

21May 17, 2010 FAA-IR-M-8040.1C

all affected aircraft have complied with the AD. Do not rescind an AD based on information that no affected aircraft are on the U.S. registry.

(4) Remember to give instructions in the ame ndatory language in te rms acceptable to the OFR.

(5) The preamble must indicate that we are rescinding an existing AD.

c. Describing the Change in the AD. Include a discussion of why it is necessary to rescind the AD.

9. Petition for Exemption. An AD is a regulation promulgated using the procedures of 14 CFR part 11. A petition requesting relief (exemption) from the requirement s of an AD must meet the requirements of 14 CFR 11.81. Refer to Exemptions Proce dures Manual, ARM 001-013, or your Regional Airworthiness Counsel, for more information.

22May 17, 2010 FAA-IR-M-8040.1C

Chapter 6. Drafting, Coordinating, Issu ing, Publishing, a nd Distributing ADs

1. Purpose of this Chapter. This chapter addresses drafting, coordinating, issuing, publishing, and distributing AD actions.

2. AD Worksheet. The AD process begins when the AD worksheet is signed. The AD worksheet is the tool for conveying factual information to the appropriate directorate for drafting an AD action. Typically, separate AD worksheets are used for each applicable model or series when the complexity of the AD (e.g., multiple product configurations, multipl e actions, and multiple compliance times) for a particular unsafe condition varies among those models or series. Th is practice facilitates better review of proposed ADs and easier compliance w ith final rules for owners and operators.

a. Use the AD worksheet approved by the Delegati on and Airworthiness Programs Branch, AIR-140 (contact your directorat e AD focal point (e.g., AD Coordinator) for the location of the current version of the worksheet). An AD worksheet is necessary except for the following:

(1) A Federal Register Version (FRV) of an emergency AD provided the content of the emergency AD is restated in the FRV, or

(2) A final rule after NPRM (FRAN) when no comments or only supportive comments are received in response to the NPRM.

b. Send completed AD worksheet and other supporting information (e.g., service information) to the accountable directorat e AD focal point (e.g., AD Coordinator) for the product. For appliances, provide it as follows:

(1) When the unsafe condition exists in the appl iance (e.g., the applianc e is the cause of a fire, direct cause of occupant in jury, etc.), send it to the director ate with geographical jurisdiction of the appliance design approva l holder. The AD action is issued against the appliance.

(2) When the unsafe condition results from the inst allation of the appliance on an aircraft, engine, or propeller, send it to the directorate responsible fo r that product. The AD action is issued against the aircraft, engine , or propeller; not the appliance.

c. Do not accept assurance from a DAH that al l products are in compliance as a reason to not issue an AD action, e.g., ther e is no assurance that a modi fication remains on the product.

d. Coordination. AD worksheets must be signed by all appropriate parties. Signatures can be accomplished by actual signature, by initiali ng the hard copy, or by providing electronic concurrence with the worksheet.

(1) If a worksheet is used, it is comple te when the following personnel sign it:

(a) The Aviation Safety Engineer (ASE);

Note : For the purposes of this manual, any reference to an ASE includes a flight test engi neer and flight test pilot.

23May 17, 2010 FAA-IR-M-8040.1C

(b) The ASE’s manager or person acting on the manager’s behalf;

(c) Continued Operational Safety (COS) focal as defined by local office (optional);

(d) The Aircraft Evaluation Group (AEG) fo cal (except for appliances); and

(e) The Manufacturing Inspection District Office (MIDO), Manufacturing Inspection Office (MIO) or Certificate Management Office (CMO) representative when a quality control problem is identified.

(f) ACO/Staff Office Manager

(2) For the disposition comment page of the AD worksheet, it is complete when:

(a) For comments received, the ASE and th e ASE’s manager (or person acting on the manager’s behalf) signs it. Or,

(b) When no comments are received, the checkbox “No Comments Received” is marked and the page is placed onto FDMS at http://www.regulations.gov

.

e. Regulatory Evaluation. The ASE must complete and submit the Regulatory Evaluation, which is part of the AD worksheet, to the accountable directorate AD focal point (e.g., AD Coordinator) for the product. Refer to ch apter 2 of the AD Manua l for guidance on the economic/regulatory aspects of the AD worksheet.

3. Drafting References and Tools.

a. Document Drafting Handbook (DDH). The OFR DDH contains guidelines for developing and formatting rules. Failure to fo llow those guidelines might result in the OFR rejecting an AD.

b. U.S. Government Printing Office (GPO) Style Manual. The GPO Style Manual contains guidance for proper grammar and punctuation.

c. FAA Order 1000.36. Follow this order to ensure we are communicating clearly, effectively, and in plain language.

4. AD Templates.

a. Use the AD templates approved by AIR-140 (c ontact your directorate AD focal point (e.g., AD Coordinator) for the location of the curr ent version of the templates). Refer to FAA Order 8040.5, Airworthiness Directive Process for Mandatory Continuing Airworthiness Information, for guidance on templates for MCAI-related ADs.

b. For a SSI AD, mark the AD with ‘Sensitive Security Airworthiness Directive’ in accordance with 49 CFR § 15.13.

24May 17, 2010 FAA-IR-M-8040.1C

5. Review and Coordination of AD Action.

a. It is essential that the reviewers, listed belo w, identify and resolve all possible issues with the ASE, and raise unresolved issues immediatel y through appropriate levels of management to obtain resolution. Except as provided in paragra ph b. below, the AD action is ready for signature once the following personnel have re viewed and coordinated on the grid:

• The ASE;

• The ASE’s manager or person acting on the manager’s behalf;

• Project officer (as applicable);

• AEG (except for ADs for appliances);

• MIDO, MIO, or CMO (for a quality control issue);

• Regional Airworthin ess Counsel; and

• Directorate Management.

b. For the following AD actions, you may coordina te on the grid with only the Regional Airworthiness Counsel, AEG, a nd Directorate Management:

(1) A Federal Register Version (FRV) of an emergency AD provided the content of the emergency AD is restated in the FRV, or

(2) A final rule after NPRM (FRAN) when no comments or only supportive comments are received in response to the NPRM.

c. For AD actions involving appliances that can be installed on various types of aircraft (e.g., transport category airp lanes, small airplanes, or rotorcraft), coordinate the draft AD action with the other affected directorate(s).

6. Administrator’s AD Alert.

a. Prepare an Administrator's AD Alert usi ng the template approved by AIR-140 (contact your directorate AD focal point (e.g., AD Coordinator) for the location of the template). Transmit the completed template to the Director, Aircraft Certification Service, AIR-1, in advance of the issuance of a “sensitive” AD. Do not send the AD to the OFR for publication or AIR-140 for distribution before AIR-1, or person acting on th eir behalf, has approved the Administrator's AD Alert.

b. Typical examples of ADs th at are considered “sensiti ve” include ADs that are:

(1) Unusually burdensome (e.g., imposes a si gnificant cost impact under the DOT Policies, or might add a significant cost increase over previously issued ADs),

(2) Controversial;

25May 17, 2010 FAA-IR-M-8040.1C

(3) Expected to generate a high level of congressional or public interest;

(4) Grounding aircraft;

(5) Affecting a large fleet of aircraft; or

(6) Anticipated to generate significant news me dia coverage, especially if related to a well-publicized accident.

7. Signature of AD Action. After coordination with all ne cessary parties, the AD action is signed by the Directorate Manager. The Directorate Managers may redelegate authority to sign ADs for their directorate to the Assistant Directorate Manager, but no further.

8. Continued Airworthiness Notification to the International Community (CANIC).

a. A CANIC is used to notify civil airworthine ss authorities of othe r countries of pending significant safety actions. A signi ficant safety action can be de fined as, but not limited to, the following:

(1) Urgent safety situations;

(2) The pending issuance of an Emergency AD;

(3) A safety action that affects many people, operators;

(4) A Special Federal Aviation Regulation (SFAR);

(5) Other high interest event (e.g., a special certification review).

b. Refer to QMS documents AIR-001-030-F1, CANIC Template , and AIR-001-030-W1, AIR Continued Airworthiness Notifica tion to the International Community , for the CANIC template and procedures regarding initiating, drafting, coordinating, i ssuing, and distributing CANICs.

9. Publication of AD Action.

a. Sending the AD Action to the OFR. After the AD action is signed, the issuing directorate either:

(1) Sends the original AD action, two certified copies, a copy of the service information for incorporation by reference if appropriate, and a diskette or co mpact disc (CD), to the OFR for publication. A designated certifyi ng official in the directorat e certifies the copies, or

(2) Sends the digitally signed AD action, if authorized by the OFR, to the OFR for publication.

b. Correcting or Withdrawing Documents from the OFR. Procedures for correcting or withdrawing documents from the OFR can be found in the OFR DDH.

26May 17, 2010 FAA-IR-M-8040.1C

10. Distribution. The AD process ends when the AD is distribute d to the affected parties. After the AD is published in the Federal Register , AIR-140 distributes the AD pe r the process below. AIR-140 also posts it on the FAA Web site at http://rgl.faa.gov

.

a. Special Notification for the Presidential Fleet and Surplus Aircraft of the U.S. Armed Forces (including engines).

(1) When issuing an AD that affects aircraft in the Presidential fleet or other surplus aircraft of the U.S. Armed Forces, including en gines, the issuing directorate must notify the Military Certification Office (MCO), ACE-100M. If unsure, contact the MCO to determine whether the affected aircraft, including engines, are in one of these categories. The MCO is responsible for notifying the U.S. Armed Forces.

(2) AIR-140 distributes the AD action electronically.

b. Emergency ADs.

(1) For emergency ADs that require AI R-140 support after business hours and on weekends or holidays, notify the AIR-140 Manage r as soon as possible to ensure personnel are available to complete AIR-140’s distribution responsibilities.

(2) Within 24 hours after receiving the AD fr om the directorate, AIR-140 must:

(a) For transport category airplanes, includi ng engines, propellers, or appliances installed on them:

 Fax the emergency AD to all affected operators with an A447 OpSpec paragraph listed in the Web-ba sed Operator Safety System (W ebOPSS), as called out in the “applicability” of the AD;

 Mail the emergency AD to all affected owners listed in the FAA Aircraft Registry, as called out in the “applicability” of the AD; and

 Notify appropriate FAA personnel using th e distribution list maintained in AIR-140.

(b) For rotorcraft or small airplanes, incl uding engines, propellers, or appliances installed on them:

 Mail the emergency AD to all affected owners listed in the FAA Aircraft Registry, as called out in the “applicability” of the AD; and

 Notify appropriate FAA personnel using th e distribution list maintained in AIR-140.

27May 17, 2010 FAA-IR-M-8040.1C

c. Final Rules, including “Final rules; request for comments”

(1) AIR-140 distributes th e AD electronically.

(2) The issuing directorate e-mails the following to AIR-140 at 9-AMC-AIR140- Information-Products@faa.gov :
(a) All final rule AD actions, including corrections, and

(b) A completed form titled “Submission of Federal Rules Under the Congressional Review Act” (contact your directorate AD focal point (e.g., AD Coordina tor) for a current copy of this form).

(3) AIR-140 mails copies of the AD and completed form to AGC-200 on a weekly basis.

d. NPRMs. AIR-140 does not distribute NPRMs to owners or operators. You can find NPRMs at:

 The FAA Web site at http://rgl.faa.gov

 The Federal Docket Management System at http://www.regulations.gov

 The OFR at http://www.gpoaccess.gov/fr

e. ADs Affecting Appliances.

(1) The FAA Aircraft Registry Database does not contain appliance information. Therefore, when possible, the issuing directorat e includes in the applicability statement of the AD the aircraft make and m odel(s) in which an appliance might be installed on.

(2) For ADs that don’t or can’t identify a speci fic affected appliance model (such as a transceiver AD), AIR-140 might have to distribute the AD to the entire fleet or a large portion of the fleet. If preparing an AD that requires su ch a distribution, contac t AIR-140 as soon as possible to discuss distribution.

f. An SSI AD.

(1) An AD resulting from SSI must be distribu ted only to need-to-know persons. Each Directorate must coordinate ea rly with AIR-140 and provide a lis t of affected operators for specific distribution.

(2) An SSI AD is not posted to RGL. A follow- up version of the AD is published in the Federal Register and RGL in the form of a ‘Final rule ; request for comments’ only after the compliance time specified in the ‘Sensitive Secu rity Airworthiness Directive’ has passed.

11. Exchange of Continuing Airworthiness Information.
a. International Civil Aviation Organization (ICAO) Annex 8. Amendment 100 to ICAO Annex 8, Airworthiness of Aircraft, Section 4, obligates the United States to exchange

28May 17, 2010 FAA-IR-M-8040.1C

continuing airworthiness information with ICAO member states.

b. Effect on ADs. Bilateral agreements between the Unite d States and other countries also require the exchange of AD information. This requirement is met by ensuring that ICAO Member States that have notifie d the FAA of the inclusion of a U.S.-manufactured aircraft on its registry are sent all applicable ADs. AIR-140 is the focal point fo r the exchange of airworthiness information with international civil aviation authorities.

12. Biweekly Supplements. A biweekly supplement contains all ADs issu ed by the FAA during the previous two-week period. AIR-140 posts each biweekly supplement on the FAA Web site at http://rgl.faa.gov

.

29May 17, 2010 FAA-IR-M-8040.1C

Chapter 7. Preamble of an AD

1. Purpose of this Chapter. This chapter provides policy and guidance on certain sections of the preamble. You can find more detail about the preamble in the OFR DDH. Refer to FAA Order 8040.5, Airworthiness Directive Process for Mandatory Con tinuing Airworthiness Information , for guidance on MCAIrelated ADs.

2. Information Headings. The preamble provides the basic information about the “who, what, where, when, and why” of the document for the average reader rather than just the aviation expe rt. It does not include regulatory text; the regulatory text is in the rule portion of the AD. All documents we send to the OFR must include the information headings shown in Example 7-1 and explained in Table 7-1.

Example 7-1: Information Headings in an AD Action

Table 7-1: Explanation of Information Headings
Information Heading Explanation

[4910-13-P] Billing Code:

• This information heading appears on the first line in the text of the AD action that we send to the Federal Register . It does not appear in the published version of the document.

DEPARTMENT OF TRANSPORTATION Department Name

Federal Aviation Administration Subagency Name

31May 17, 2010 FAA-IR-M-8040.1C

Information Heading Explanation

14 CFR Part 39 CFR Citation:

• The CFR chapter the document amends or proposes to amend.

[Docket No. FAA-20**-+++++; Directorate Identifier 20**-**-***-AD; Amendment 39-**; AD **] Agency Identification Numbers:

• AD docket number obtained from the FDMS.

• Directorate identifier is uni que to each directorate.

• Amendment number to CFR Part 39, assigned by AIR140. This number doesn’t appear in NPRMs.

• AD number, assigned by AIR-140. This number doesn’t appear in NPRMs.

RIN 2120-AA64 RIN Number:

• Assigned by the Regulatory Information Service Center to identify each regul atory action listed in the Unified Agenda of Federal Regulatory and Deregulatory Actions.

Airworthiness Directives; ** Subject Heading; Name of Product Affected:

• The name of the make and model of the product (i.e., aircraft, aircraft engine, prope ller, or appliance) affected with additional qualifiers, as necessary. Name of agency issuing the regulatory action AGENCY Type of AD action (e.g., NPRM, Final Rule, etc.) ACTION

3. AD Numbering.

a. Identifying AD Actions. The directorate issuing the AD action assigns a directorate identifier and obtains a FDMS docket number.

(1) Docket Number (underlined below).

Docket No. FAA-2008-XXXX ; Directorate Identifier 2008-NE-XX-AD; Amendment 39-XXXXX; AD 2008-XX-XX

(a) The directorate issuing the AD action c ontacts the DOT DMS Docket Office by telephone or by e-mail and reque sts an FDMS docket number. The directorate supplies the following information to the DOT DMS Docket Office:

• AD Docket Title (i.e., Directorate Identifier)

• Category (i.e., Rulemaking)

• Subcategory (i.e., Airworthiness Directives)

• Action Office (e.g., ASW-112)

32May 17, 2010 FAA-IR-M-8040.1C

• AD Docket Subject (i.e ., Make/Model/Subject)

(b) The DOT DMS Docket Office then a ssigns the next sequential AD docket number, which includes the calendar year the directorate requested th e FDMS docket number. Example: FAA-2008-2432.

(2) Directorate Identifier (underlined below). The directorate identifier includes the calendar year we start the AD acti on, the two-letter designator fo r the directorate region, and a sequential number. The director ate regions are as follows:

• CE (Central region),

• NE (New England region),

• NM (Northwest Mountain region), and

• SW (Southwest region)

Docket No. FAA-2008-XXXX; Directorate Identifier 2008-NE-XX-AD ; Amendment 39-XXXXX; AD 2008-XX-XX

b. Retaining Directorate Identi fier and Docket Number. For final rules that follow NPRMs, use the same directorate identifier a nd FDMS docket number used for the NPRM.

c. Revising ADs Issued Before Impl ementation of DMS and FDMS. For revisions to ADs issued before we started using DMS or FD MS, convert the original AD docket number to a directorate identifier and obtain a new FDMS docket number.

d. Changing the Directorate Identifier and Docket Number. The issuing directorate may change the directorate identifier and AD docket nu mber if it becomes impractical to continue using the original numbers. Some reasons to change include:

• Age of the AD action

• Change in directorate responsibility.

e. Amendment Number (underlined below). After a Directorate Ma nager or Assistant Directorate Manager signs an AD, the issuing di rectorate gets a part 39 amendment number and an AD number from AIR-140. Pr ovide to AIR-140 the FDMS docket number (except for emergency ADs), directorate identi fier, issue date, whether it is a revising or superseding AD action, and the design approval holder (e.g., TC hol der) and model/series of the product affected.

Docket No. 2008-NE-XX-AD; Amendment 39-XXXXX; AD 2008- XX-XX

f. AD Number (underlined below).

Docket No. 2008-NE-XX-AD; Amendment 39-XXXXX; AD 2008-XX-XX

33May 17, 2010 FAA-IR-M-8040.1C

(1) AIR-140 assigns an AD number to every AD. The AD number is used for agency tracking, maintenance recordkeeping by operators, and filing purposes. The number consists of a series of eight digits separated by dashes. The firs t four digits indicate th e calendar year in which the AD action is issued. The second two digits indicate the biweekly period of the year in which the AD number was assigned. The last two digits are issued sequentially, beginning with –01 for each biweekly period and continuing in ascending order until the next biweekly period begins, unless the AD is an emergency AD.

(2) For emergency AD numbers, AIR-140 designa ted the “50 series.” Examples are 2005-10-51 and 2004-14-52. The AD numbers follow th e same system described previously.

(3) Revisions to ADs are identified by a suffix to the basic AD number that indicates the level of revision. Examples are 2005-10-05 R1; 2005-10-05 R2.

4. Subject Heading.

a. For AD actions involving type ce rtificated (TC) aircraft, engi nes, or propellers, specify the affected make and model of the product wi th additional qualifiers , as necessary. For example:

Example 7-2: Subject Heading with Product and Additional Qualifier
The Boeing Company Model 777 Airplanes Equipped With RollsRoyce plc Model RB211-TRENT 892-17 Engines

(1) Use the legal name of the TC holder speci fied on the TCDS. Identify previous TC holder(s) if including them makes it easier to identify the prod uct. For example:

Example 7-3: Subject Heading with Previous TC Holder
Hawker Beechcraft Corporation (Type Certificate previously held by Raytheon Aircraft Company) Models 1900, 1900C, and 1900D Airplanes

(2) If many different TC holders are affected, replace the product make and model with “Various [Aircraft/Engines/Propellers],” as appr opriate. Use product desc riptor as necessary (e.g., Transport Airplanes, Reciprocating Engines). For example:

Example 7-4: Subject Heading Involving Many Different TC Holders
Various Transport Helicopters

(3) If many different models are affected, use the product’s basic model number (e.g., The Boeing Company Model 747).

(4) The term “series” denotes similar models of a product. Referring to products by series leaves the AD open to interpretation and incons istent use is a constant source of problems. Although it is a useful short cut, it's only useful if it's accurate and clear to affected parties.

34May 17, 2010 FAA-IR-M-8040.1C

(a) Use this term with caution, i.e., only if it appears as a make-model-series description on the TCDS or design approva l letter (e.g., The Boeing Company Model 757- 200CB series airplanes as listed on TCDS A2NM). Do not use the term ‘series’ if the AD applies to only certain products within the make -model-series description. For example:

Example 7-5: Using “Series” as Defined on a TCDS
The Boeing Company Model 757-200, -200PF, -200CB, and -300 Series Airplanes

(b) For TCDS’s or design approval letters which do not list models by a make-modelseries description, specify each individual model that applies to the AD.

(5) You may include a product model’s “common” name for additional clarity. Place the common name in parentheses after the TCDS’s legal name. For example:

Example 7-6: Subject Heading with a Common Name
Piper Aircraft, Inc. (Piper) Model PA-46-350P (Mirage) Airplanes

(6) For unsafe conditions associated with PMAs and STCs:

(a) Identify the TC holder’s legal name of th e product affected (not the holder of the PMA or STC). Identify previous TC holder(s) if including them makes it easier to identify the product.

(b) Include a qualifier for the PMA and STC. For example:

Example 7-7: Subject Heading Involving an STC
The Boeing Company Model 737-300, -400, and -500 Series Airplanes Modified by Supplemental Type Certificate (STC) ST00127BO

Example 7-8: Subject Heading Involving Various Aircraft and STCs
Various Small Airplanes Modified by Supplemental Type Certificate SA1921CE, SA1922CE, or SA1923CE

Example 7-9: Subject Heading Involving a PMA
Lycoming Engines (Type Certific ate previously held by Textron Lycoming) Models 320, 360, and 540 Engines Modified by Certain Engine Components, Inc., Cylinder Assemblies

b. For AD actions involving appliances, identi fy the DAH’s name followed by the affected part name and part number(s) or model number(s) as appropriate. For example:

35May 17, 2010 FAA-IR-M-8040.1C

Example 7-10: Subject Heading Involving an Appliance with a P/N
Honeywell International, Inc., Vertical Gyros, Part Number 1234

Example 7-11: Subject Heading Involving an Appliance with a Model Number
PTC Aerospace, Passenger Oxygen System, Model Number 91700

5. Summary. Using the information from the AD worksheet and service information, as appropriate, the summary must briefly describe the following:

a. The mandated or proposed corrective action( s) (e.g., This AD requires you to XXX ...);

b. The unsafe condition (e.g., This AD was prompted by XXX ...); and

c. The root cause, if known, of the unsafe cond ition and the end-level effect (e.g., We are issuing this AD to XXX ...).

6. Discussion. This section clearly justifies why the AD action is necessary. Fu lly explain the unsafe condition and the circumstances that created a need for the AD. Present the history of the information that the FAA has received to date. Describe what would happen if we did not take AD action (i.e., this condition if not corrected could result in ...). To further support why the AD action is necessary, we also may describe elements of a risk analysis.

7. Relevant Service Information. This section describes all service information that is relevant to the AD action and gives a brief description of the pr ocedures specified.

8. Differences Between this [Propose d] AD and Service Information. This section describes major differences from the service information (e.g., changes to avoid bootstrapping, mandating term inating action, etc.).

9. Costs of Compliance. This section includes the costs associated with the mandatory corrective action(s) and adds together the following: the number of work -hours required to complete the AD (or one inspection cycle if the AD requires repetitive inspections) multiplied by the current established burdened labor rate, plus the cost of parts. The stated costs must address all actions mandated by the AD (e.g, revising the Instructions for Conti nued Airworthiness (ICA)) . You can express the labor and parts costs for indivi dual products, and when known, give a total cost for the entire affected U.S.-registered fleet. When de termining the costs of an AD action:

a. Make sure the number of work-hours (at the bur dened labor rate), the cost of parts, the total number of U.S.-registered aircraft or the total number of products installed on U.S.-registered aircraft equal the total cost stated in the AD. Don’ t include other uns tated factors. We must give the necessary cost information so the public can see how we reached the total.

36May 17, 2010 FAA-IR-M-8040.1C

b. Don’t make unsubstantiated presumptions a bout how many aircraft, engines, or other products have already had the wo rk required by the AD performed.

c. If different actions are require d for more than one aircraft certification ca tegory, state the cost for each category separately.

d. Calculate the total cost to comply with th e actions of the proposed AD (e.g., accessing, testing, parts, closing, etc.). State them in the Cost of Compliance section of the preamble as if no warranty program exists. If a TC holder or DAH offers warranty coverage, add a statement mentioning the warranty program.

e. Do not state any costs beyond initial work-hour s and parts costs; th at is, don’t include costs that operators might incu r in individual maintenance sche duling or costs that operators might pass on to others.

f. Include on-condition costs (e.g., those costs associated with follow-on actions to a required inspection, such as repairing a crack det ected during an inspection) per product. Do not include the total fleet on-condition costs.

10. Interim Actions. The requirements of some ADs are “interim act ions” until a more effective modification or action is developed or to a void bootstrapping. The preamble of these ADs must contain a statement indicating that it is interim action so all affected operators know that we may issue additional rulemaking in the future. The following are some specific examples:

a. If the AD requires repetitive inspections and we know that the manufacturer is developing a modification or act ion that makes those inspections unnecessary, you may use one of the following statements, as appropriate.

Example 7-12: Interim Action Statements
We consider this proposed AD interim action. If final action is later identified, we might consider further rulemaking then.

Example 7-13: Interim Action Statements
We consider this proposed AD interim action. The design approval holder is currently developing a modification that will address the unsafe condition identified in this AD. Once this modification is developed, approved, and available, we might consider additional rulemaking.

b. Sometimes we issue an IAR or an emergency AD that requires operators to initiate repetitive inspections within a short time. When we issue the IAR or emergency AD, there might be a modification available that, once installed on the aircraft, would end the need for the repetitive inspections. If we plan to require the modification, but th e compliance time for its installation exceeds the criteria for an “immediate” rule and there is enough time to allow the public to comment on the modification, then you may use the following statement in the

37May 17, 2010 FAA-IR-M-8040.1C

preamble to the IAR or emergency AD:

Example 7-14: Interim Action Awaiting Terminating Action
We consider this AD interim action. We are currently considering requiring [the installation of..., which will constitute terminating action for the repetitive inspections required by this AD action]. However, the planned compliance time for the installation of the modification would allow enough time to provide notice and opportunity for prior public comment on the merits of the modification.

c. Some ADs require that operators send a report of inspection results to us or to the DAH. The information is used to determine if an addi tional action or a final action is necessary (see Chapter 8, paragraph 14, for more informati on about reporting requirements). You may use a statement similar to the following in these cases:

Example 7-15: Interim Action Awaiting Inspection Results
We considered this AD interim action. The inspection reports that are required by this AD will enable us to obtain better insight into [the nature, cause, and extent of the cracking,] and eventually to develop final action to address the unsafe condition. Once final action has been identified, we might consider further rulemaking.

38May 17, 2010 FAA-IR-M-8040.1C

Chapter 8. Rule Portion of an AD

1. Purpose of this Chapter. This chapter provides policy and guidance for cert ain sections in the rule portion of an AD. Although the preamble explains the AD and its purpos e, the rule portion of the AD stands alone. Refer to FAA Order 8040.5, Airworthiness Directive Pro cess for Mandatory Continuing Airworthiness Information , for guidance on MCAI-related ADs.

2. Headings in the Rule Portion of an AD. While the actual content of each AD varies, you must include certain headings in the rule portion of every AD. Example 8-1 provides an excerpt fro m a Final Rule AD. Refer to the standardized templates for the headings require d in other types of AD actions.

Example 8-1: Headings in the Rule Portion of an AD

39May 17, 2010 FAA-IR-M-8040.1C

3. Product Identification. The product identification specifies the name of the TC holder or DAH used in the Subject Heading in the preamble. 18

Example 8-2: Product Identification for an NPRM
Lycoming Engines (Type Certific ate previously held by Textron Lycoming): Docket No. FAA-2005-23269; Directorate Identifier 2005-NE-50-AD.

Example 8-3: Product Identification for a Final Rule
2009-05-11 The Boeing Company: Amendment 39-15835. Docket No. FAA-2009-0199; Directorate Identifier 2009-NM-017- AD.

a. If many different TC holders are affected, replace the product make with “Various [Aircraft/Engines/Propellers],” as appropriate. For example:

Example 8-4: Product Identification for a Final Rule Involving Many Different TC Holders
2008-06-19 Various Transport Helicopters: Amendment 39- 15902. Docket No. FAA-2008-38273; Directorate Identifier 2008- SW-037-AD.

b. For AD actions that result from an unsafe c ondition associated with an STC or PMA, use the TC holder’s legal name of the product affected (not the ho lder of the PMA or STC). For example, write the product identification statem ent for an STC issued to American Airplane Company on a Boeing Model 737 airplane as the following:

Example 8-5: Product Identification for a Final Rule Involving an STC
2010-05-14 The Boeing Company: Amendment 39-15512. Docket No. FAA-2010-0051; Directorate Identifier 2010-NM-012- AD.

c. For AD actions associated with appliances, use the appliance DAH’s name. For example:

Example 8-6: Product Identification for a Final Rule Involving an Appliance
2006-19-04 Honeywell International, Inc.: Amendment 39- 14761. Docket No. FAA-2006-24639; Directorate Identifier 2005- NM-171-AD.

4. Effective Date. Standard effective dates are presen ted in the templates. In rare in stances (usually at the direction of the directorate management), you can specif y that an AD is effective upon publication. The

18 Refer to Chapter 7, paragraph 4

40May 17, 2010 FAA-IR-M-8040.1C

correct way to do so is to ente r the following bracketed statement in the space left for the effective date.

Example 8-7: Effective on Publication
(a) This AD is effective [INSERT DATE OF PUBLICATION IN THE FEDERAL REGISTER].

5. Affected ADs.

a. List any AD numbers that are supe rseded or revised. For example:

Example 8-8: Affected ADs for a Supersedure
(b) This AD supersedes AD 2004-12-15, Amendment 39- XXXXX.

b. List the AD number of other ADs if the re quirements of those ADs are affected. For example:

Example 8-9: Affected ADs Related to Other ADs
(b) Paragraph (g) of this AD terminates the requirements of paragraph (g)(2) of AD 2007-12-19, Amendment 39-XXXXX.

6. Applicability. Include a statement or table that identifies the a ffected product using the information specified in the Subject Heading in the preamble. Use only MS Word tables, since they are searchable, when using tables. Add serial numbers (S/Ns), line numbers, etc., if they are appropriate and useful. For example:

Example 8-10: Identifying Applicability Using a Statement with Subparagraphs
(c) This AD applies to the airplanes identified in paragraphs (c)(1) and (c)(2) of this AD, certificated in any category. (1) The Boeing Company Model 757-200 series airplanes, as identified in Boeing Special Attention Service Bulletin 757-21-0106, dated March 24, 2005. (2) The Boeing Company Model 757-300 series airplanes, as identified in Boeing Special Attention Service Bulletin 757-21- 0107, dated March 24, 2005.

Example 8-11: Identifying Applicability Using a Single Statement
(c) This AD applies to Robinson Helicopter Company Model R44 helicopter.

41May 17, 2010 FAA-IR-M-8040.1C

Example 8-12: Identifying Applicability Using Tables
(c) This AD applies to the following The Boeing Company airplanes, certificated in any category, as identified in Table 1 of this AD:

Table 1 – Applicability

Models – Boeing –
737-600, -700, -700C, -800, -900 series airplanes Special Attention Service Bulletin 737-24-1165, Revision 1, dated October 20, 2005 737-300, -400, -500 series airplanes Alert Service Bulletin 737- 24A1166, Revision 4, dated May 21, 2009 747-400, -400D, -400F series airplanes Service Bulletin 747-24-2254, Revision 1, dated March 5, 2007

Example 8-13: Identifying Applicability Using Tables with S/Ns

(c) This AD applies to the following Hawker Beechcraft Corporation (Type Certificate previously held by Raytheon Aircraft Company) airplanes, certificated in any category, as identified in Table 1 of this AD:

Table 1 – Applicability

Model – Serial Numbers –

1900 UA-3
1900C UB-1 through UB-74, UC-1 through UC-174, and UD-1 through UD-6
1900D UE-1 through UE-439

a. STC or PMA. Some ADs correct a condition that ar ises when one or more different models of aircraft, engine, or propeller ar e altered as a result of an STC or PMA.

(1) Use the following: (a) If only one TC holder is affected, list th e name of the TC holder and model(s) affected and reference the STC or PMA as identifi ed in the Subject Heading in the preamble. For example:

42May 17, 2010 FAA-IR-M-8040.1C

Example 8-14: Applicability Statement for STC
(c) This AD applies to Learjet Inc. (Type Certificate PreviouslyHeld by Gates Learjet Corporation) Model 23, 24, 24A, 24B, 24BA, 24D, 24D-A, 24E, 24F, 25, 25A, 25C, 25D, and 25F airplanes, certificated in any category, modified by Supplemental Type Certificate SA1731SW, SA1669SW, or SA1670SW.

Example 8-15: Applicability Statement for PMA
(c) This AD applies to Bell Helicopter Textron Model 212, 412, and 412EP helicopters, certificated in any category, modified by Aeronautical Accessories, Inc., Parts Manufacturer Approval reservoir assembly, part number 212-372-050.

(b) If the Subject header and product identif ication statements applied to many different TC holders (e.g., Vari ous Airplanes), list the name of each TC holder and model(s) affected. Reference the STC or PMA as identified in the Subject Heading in the preamble. For example:

Example 8-16: Applicability Statement for Many TC Holders and STCs
(c) This AD applies to all serial numbers of the following airplanes, certificated in any category, that are modified by Supplemental Type Certificate (STC) SA1921CE, SA1922CE, or SA1923CE, as identified in Table 1 of this AD:

Table 1 – Applicability Type Certificate Holder – Models –

Aerostar Aircraft Corporation PA-60-600, PA-60-601, PA-60- 601P, and PA-60-700P
Hawker Beechcraft Corporation (Type Certificate Previously Held by Hawker Beechcraft Company) 2000

Piper Aircraft, Inc. PA-46-310P and PA-46-500TP Cessna Aircraft Company T303, 310R, 425, and 441 Sabreliner Corporation NA-265-40, NA-265-60, NA265-70 and NA-265-80

(2) An alternative is to issue a separate AD for each TC holder affected by the STC or PMA.

b. Appliance ADs. For appliance ADs (e.g., TSOs), use the information specified in the Subject Heading in the preamble. If known, include the aircraft, engine, or propeller model(s) in

43May 17, 2010 FAA-IR-M-8040.1C

which the appliance might be installed on. For example:

Example 8-17: Applicability Statement for Appliance ADs
(c) This AD applies to Sicma Aero Seat cabin attendant seats series 150 type FN and 151 type WN, all part and serial numbers. These attendant seats are installed on, but not limited to, Airbus Models A319, A320, and A321 series airplanes.

c. Serial Numbers (S/Ns) or Other Identifiers. You may use or reference S/Ns or other identifiers with the model number to furt her identify products affected by an AD.

(1) If the product currently is in production, th e engineer works with the manufacturer to determine when the production run will end or when a product improvement will eliminate the unsafe condition cited by the AD, and then stat e the complete range of S/Ns. Ensure the production run ends as represented by the manufacturer.

(2) When several S/Ns are cited in seque nce, such as “S/N 12340 through S/N 12345 inclusive,” be sure that no S/N in the sequence is excluded from the applicability.

d. Certification Category.

(1) Type Certification Categories. Aircraft are type certificated in categories, such as transport, normal, commuter, restricted, acrobatic , etc. For aircraft ADs, boilerplate language includes the phrase “certifi cated in any category” in the app licability. You must identify those categories that are excluded fr om the AD if the unsafe condition does not exist in all of the categories for which the aircraft is type certificated. For example:

Example 8-18: Excluding TC Categories from an AD
(c) This AD applies to Aerotek II, Inc. Models B-1 and B-1A airplanes, certificated in any category except restricted.

(2) Airworthiness Certification Categories. Unless specifically stated, ADs apply to the make and model of the product set forth in the applicability statement regardless of the classification or category of the airworthin ess certificate issued for the aircraft.

(3) Type-Certificated Engine or Propeller In stalled on Non-U.S.-Type Certificated Aircraft. Do not exclude a type certificated engine or propeller from the applicability statement of an AD because it might be installed on an aircraft that does not hold a U.S. type certificate. Write the applicability statement to include all affected engine or propeller models, but do not specify a non-U.S.-type certificat ed aircraft that it might be installed on (e.g., amateur-built aircraft).

e. Military Aircraft. List military aircraft in the applicability paragraph of ADs if:

• The military aircraft is eligible for certification under a civilian TC; or

• The AD affects the civil counterpart.

44May 17, 2010 FAA-IR-M-8040.1C

Example 8-19: Applicability Statement with Military Aircraft
(c) This AD applies to McDonnell Douglas Corporation ModelDC-9-31, DC-9-32, DC-9-32 (VC-9C), DC-9-32F, DC-9-33F, DC9-34, DC-9-34F, and DC-9-32F (C-9A, C-9B) airplanes.

7. ATA/JASC Code. Include the code and subject title that clearly and concisely refl ects the contents of the AD action (e.g., 32, Landing Gear; or 3220, Nose /Tail Landing Gear). Contact your directorate AD focal point (e.g., AD Coordinator) for a c opy of the ATA/JASC document.

8. Compliance. The compliance requirements involve compliance times and mandated corrective actions.

a. Basic Elements of Compliance Times. We consider the following information when establishing a compliance time or period:

(1) Establishing a Compliance Threshold. A compliance “threshold” establishes the point in the life of a product before which action must be taken to detect or prevent the unsafe condition. The threshold is based on an engineering assessment. For example, if fatigue cracking has been found on airplanes with 10,000 landings, the engineer might determine that an initial inspection for fatigue cracking is necessary be fore the airplane accumulates 5,000 landings.

(2) Establishing a Grace Period for Produc ts that Have Exceeded the Threshold. Some products might have already exceeded the th reshold that the engineer establishes for an AD. In those cases, the engineer must include a “grace period” so aircraft aren’t grounded unnecessarily. In those cases, the engineer se lects a grace period that avoids grounding or interfering with normal maintenance schedules, ye t still obtains expeditious compliance within an acceptable level of safety. It’s important to note though, that in some cases, we might need to ground aircraft. Consider several factors when determining an appr opriate grace period: (a) The degree of urgency of the unsafe condi tion, which must be balanced against the amount of time necessary to do the required actions. (b) The availability of replacement parts. (c) Operators’ regular maintenance schedules. (d) Other factors affecting the abil ity of operators to comply.

b. Expressing Compliance Times Using Time -in-Service (TIS) or Flight Hours.

(1) Simple Compliance Times. A simple way to express a compliance time is to state the number of hours of operation at which all affected products mu st be in compliance with the AD. Using the phrase “within [X] hours TIS” mean s any time up to or at [X] hours. The phrase “before the [product] accumulates [X] hours TIS” means up to but not including [X] hours. Use the following examples as guidance.

45May 17, 2010 FAA-IR-M-8040.1C

Example 8-20: Simple Compliance Times Using TIS
Required within 100 hours time-in-service (TIS) after the effective date of this AD.

Example 8-21: Compliance Times Using Landings
Before the airplane accumulates 100 landings after the effective date of this AD ...

(2) Multiple Compliance Times. When there are multiple compliance times, avoid stating compliance times that create overlapping requirements. Use the following example as guidance:

Example 8-22: Multiple Compliance Times Using TIS
Before the airplane accumulates 5,000 hours time-in-service (TIS) or within 300 hours TIS after the effective date of this AD, whichever occurs later ...

(3) Compliance time for a Component. If compliance times relate to the hours time-inservice of a part, use a stat ement similar to Example 8-23.

Example 8-23: Compliance Time for a Component Using TIS
Before the torque link, P/N 13579 accumulates 1,000 hours timein-service (TIS) or within 100 hours TIS after the effective date of this AD, whichever occurs later ...

c. Expressing Compliance Times Using Calendar Times.

(1) Use calendar times (e.g., “within 6 months afte r the effective date of this AD”) when: (a) We can establish a direct relationship between calendar time and airworthiness. For example, after operating in a corrosive enviro nment, an airplane might not be operated for 6 months. Corrosion could conti nue to develop over time; th erefore a compliance based on calendar time would be necessary to detect the unsafe condition. (b) An aircraft’s usage rate varies greatly throughout the fleet. In this instance, we generally can’t prioritize the co mpliance time any other way; or (c) Logistics for the operators, such as parts availability, repair facility availability, means they must perform the actions in the AD on an attrition basis with a calendar deadline.

(2) When we express compliance times in months or calendar months after the effective date of the AD, we might establish the time from the effective date as follows: (a) If the compliance time is “within 12 months after the effective date of this AD” and the effective date is January 15, 2006, th e deadline for compliance is January 15, 2007. (b) If the compliance time is specified as a number of calendar months after the effective date, the time is measured from th e end of the month during which the AD becomes

46May 17, 2010 FAA-IR-M-8040.1C

effective. If the compliance time is “within 12 calendar months after the effective date of this AD” and the effective date is January 15, 2006, the deadline for complying is January 31, 2007.

d. Expressing Compliance Times Using Dates. During the period of time that we develop an AD, effective dates can’t usua lly be determined with any pr ecision, especially at the NPRM stage. Therefore, citing a calendar date (for example, “before December 1, 2006”) isn’t usually an appropriate method of specifying a grace period. However, when a direct analytical relationship can be established and it is appropriate to use calendar dates, give a brief explanation of the relationship in the preambl e of the AD. The mere fact th at the service document or an international civil aviation author ity’s AD refers to a calendar date isn’t enough to justify using a calendar date in a U.S. AD. In most cases, this relationship does not exist because:

(1) Compliance thresholds are usua lly a function of usage, whic h is unrelated to calendar dates.

(2) Grace periods are a function of the time nece ssary after the effec tive date to do the required actions.

e. Expressing Compliance Times Using the Number of Landings or Flight Cycles.

(1) Use the number of landings or flight cycles on an aircraft to express compliance time if the problem is related to land ings or flight cycles; for exampl e if the problem is related to landing gear, flaps, or fatigue that is aggravated by la nding or pressurization cycles.

Example 8-24: Compliance Time Using Number of Landings
Required before accumulating 100 landings after the effective date of this AD.

(2) If applicable, use a statement in the AD to provide for operators that do not keep landing records. For example:

(a) The compliance times of this AD are pres ented in landings. If you do not keep a record of the total number of landings, then mu ltiply the total number of aircraft hours TIS by (whatever multiplier is appropriate for the affected aircraft).

(b) Subject to acceptance by [appropriate FAA official], operators that do not have landing records can determine the number of landings by dividing the number of hours of TIS of each airplane by the time of the average flight for th e aircraft of that type in the operator's fleet.

f. Expressing Compliance Times Using Engine Cycles. You may use cycles to express compliance time for ADs that affect turbine engine s. Use the standard cy cle definition and cycle counting methodology specified in the approved se rvice document for the applicable engine model. When the definitions for the cycle or counting methods in the AD differ from those in the approved service document, include the cycle de finition or the cycle counting method in the regulatory text of the AD. In this case, make sure the cycle definition or counting methodology doesn’t allow an airplane to exceed its approve d cyclic retirement life sp ecified in the approved service document.

47May 17, 2010 FAA-IR-M-8040.1C

g. Expressing Compliance Times for Inspection and Repair. If a required inspection could result in a required repair or replacement, the AD must clearly state the compliance times for both the inspection and the re pair or replacement. Use the following examples as guidance.

Example 8-25: Inspection Compliance Time

Within the next 100 hours time-in-service after the effective date of this AD, visually inspect the internal structure at Wing Station 12 for cracks using dye penetrant and a glass of at least 10 power in accordance with the procedure specified in paragraph (a) of Vega Service Bulletin No. 25, dated November 29, 1988.

Example 8-26: Repair or Replacement at Time of Inspection
If a crack is found, repair before further flight in accordance with the procedure specified in paragraph (b) of Vega Service Bulletin No. 25, dated November 9, 1988

.
Example 8-27: Repair or Replacement at Time Different From Inspection
If a crack is found, repair within the next 50 hours time-in-service after the inspection required by paragraph (a) of this AD in accordance with the procedure specified in paragraph (b) of Vega Service Bulletin No. 25, dated November 29, 1988.

h. Expressing Compliance Times that Coin cide with Scheduled Maintenance. Compliance times that coincide with scheduled maintenance are appropriate when the unsafe condition isn’t so urgent that a shorter comp liance time is necessary. However, don’t express compliance times in terms of an indefinite or no nspecific maintenance interval, such as “at the next ‘C’ check.” Maintenance schedules vary from operator to operator, so there is no assurance that the action will be done within the time frame for safe operation of the aircraft.

i. Maintenance Intervals Together With Ca lendar Times, Hours, or Cycles. Specify compliance times in terms of maintenance interval s together with a specific calendar time, hours, or cycles. For example:

Example 8-28: Maintenance Interval and Calendar Time
Required at the next shop visit or 60 days after the effective date of this AD, whichever occurs later.

j. Expressing Compliance Times for Interim Action. If the AD requires an interim action before a repair or replacement (such as in stalling an operating limita tions placard), use a statement in the rule portion of the AD similar to the Examples below:

Example 8-29: Interim Action Statements
Within the next 10 hours TIS after the effective date of this AD, install a placard ...

48May 17, 2010 FAA-IR-M-8040.1C

Example 8-30: Interim Action Statements

Within the next 500 hours time-in-service after the effective date of this AD, modify the wing panel in accordance with the procedures specified in...

k. Expressing Repetitive Compliance Times.

(1) When an initial inspection is followed by repetitive inspections at periodic intervals, you may use the statement in Example 8-31 but use it in the instruction itse lf, not as a separate compliance paragraph. This can be specified as part of the compliance requirement or as part of the inspection instruction. For example:

Example 8-31: Repetitive Compliance Time
Required within 25 hours time-in-service (TIS) after the effective date of this AD, and thereafter at intervals not to exceed 25 hours TIS from the last inspection.

(2) Example 8-32 shows a compliance time for an inspection before the effective date of the AD. The phrase in Example 8-32 “unless alre ady done within the last 75 hours TIS” accounts for an operator that has made an inspecti on before the effective date of the AD.

Example 8-32: Allowance for Inspections before the Effective Date
Within 25 hours time-in-service (TIS) after the effective date of this AD, unless already done within the last 75 hours TIS, and thereafter at intervals not to exceed 100 hours TIS from the last inspection, inspect ...

9. Corrective Action. Every AD contains a clear and concise statement of the action(s) that addresses the unsafe condition. This statement includes:

• The method of performing the actions, and

• Corrective measures or limitations required.

a. Method of Specifying Corrective Actions. Identify the corrective actions in an AD in a manner that ensures the actions are comple te, clear, and enforceable. For example:

(1) Include the corrective actions from th e service information in the AD text;

(2) Include the corrective actions determined by the ASE; or

(3) Incorporate the service information by reference. 19 In the AD text, provide complete service information identification and do not si mply say, “Do the service bulletin.” If we incorporate service information into an AD by re ference, do not use the phrase “or later FAA-

19 Refer to Chapter 10

49May 17, 2010 FAA-IR-M-8040.1C

approved revision” when referring to the servic e information. This phrase violates OFR policies for approving materials that are incorporated by reference. Service information that we incorporate by reference in an AD is often revise d after we issue the AD. We can approve later revisions of service information as an AMOC.

Example 8-33: Citing a Service Bulletin that is Incorporated by Reference
Do the x-ray inspection to detect cracking in Body Station XYZ in accordance with the procedures specified in the Accomplishment Instructions of the service bulletin.

b. Method of Referring to Servi ce Information without IBRing. For procedures where standard practices exist or there is more than one way to accomplish the action, do not incorporate by reference the service information. In other words, if it is not important how the action is accomplished, referring to service information, without mandating its use, is acceptable. In this case, give an informational reference, for example:

Example 8-34: Informational Reference to Service Information
Safety wire the servo plug with 0.025-inch diameter wire to the regulator cover. Refer to Precision Airmotive LLC Mandatory Service Bulletin No. PRS-999, dated September 8, 2005, for guidance on properly safety wiring the plug.

c. Describing Inspections. If an AD requires an inspection:

(1) Define the area of the product or th e specific parts to be inspected.

(2) State whether it is necessary to do extra actions when it is not specified in the service information, e.g., disassembling an area or re moving bolts in order to do the inspection.

(3) Describe provisions for an FAA-approve d method, if acceptable. For example,

Example 8-35: Language for FAA-Approved Method
If any crack is found during any inspection required by this AD, and Lockheed Service Bulletin 329II-55-4, dated July 9, 2008, specifies contacting Lockheed Martin Corporation/Lockheed Martin Aeronautics Company for appropriate action: Before further flight, repair the spar cap doublers in accordance with a method approved by the Manager, Atlanta Aircraft Certification Office (ACO), FAA. For a repair method to be approved by the Manager, Atlanta ACO, as required by this paragraph, the Manager’s approval letter must specifically refer to this AD.

( 4) Refer to the applicable service information or document for the inspection procedures if the procedures are in that document.

d. Records Review in Lieu of Inspection. When the need to take corrective action depends on whether a particular P/N is installed, we al low review of maintena nce records instead of

50May 17, 2010 FAA-IR-M-8040.1C

inspection of the product, if the P/N can be positively identifie d from the review.

e. Describing Replacement Parts. Except in ADs that require an immediate grounding, one important consideration when writing an AD is the availability of replacement parts. Compare the availability of replacement parts versus the risk of not addressing the unsafe condition in a timely manner. This avoids unnece ssary groundings. Ensure that risk is managed at an acceptable level. If risk cannot be managed within part av ailability, then grounding results.

f. Terminating Action.

(1) Mandating Terminating Action. A terminating action is mandated when we have determined that long-term conti nued operational safety is better ensured by design changes that remove the source of the problem and end the ne ed for any repetitive in spections or special operating procedures, e.g., operating limitations . Mandating a terminating action might be necessary to ensure the con tinued operational safety of the product, if for example: (a) The inspection area is hard to reach, making detecti on of cracking or corrosion difficult or unreliable; or (b) The detection method is hindered by an in tervening structure or is otherwise unreliable; or (c) The sheer size of the area covered, or the physical demands on the inspector, make detection unreliable.

(2) Optional Terminating Action. Mandating a terminating action might not be necessary to ensure the con tinued operational safety of the product, if for example: (a) The repetitive inspections are in an area that is easily accessible, (b) The unsafe condition (e.g., cracki ng) is easily detectable, and (c) The consequences of the unsafe conditi on (e.g., cracking) is not likely to be catastrophic.

(3) No Terminating Action Available. Mandating a terminating action might not be possible, if for example the unsaf e condition is under i nvestigation. In this case, you may include an explanation in the preamble of the AD w hy we are not providing a terminating action.

g. Allowing Credit for Corrective Actions Already Done.

(1) Whenever possible, allow credit for co rrective actions alr eady done. If the AD requires a one-time action such as an inspecti on, modification, or repl acement, use a statement similar to Example 8-36.

Example 8-36: Allowing Credit for Corrective Action
Required within 100 hours time-in-service after the effective date of this AD, unless already done.

(2) You can also limit credit for corrective action already done if the unsafe condition

51May 17, 2010 FAA-IR-M-8040.1C

warrants it, for example, if a recent inspection would do, but not an inspection done a year ago. For example:

Example 8-37: Limiting Credit for Corrective Action
Required within 100 hours time-in-service (TIS) after the effective date of this AD, unless already done within the last 50 hours TIS.

( 3) When appropriate, allow credit for actions accomplished using an earlier revision of the service information than identifi ed in the AD action. For example:

Example 8-38: Credit for Actions Accomplished in Accordance with Previous Service Information
Actions accomplished before the effective date of this AD in accordance with the procedures specified in Boeing Alert Service Bulletin 717-38A0004, dated December 6, 2006, are considered acceptable for compliance with the corresponding actions specified in paragraph (f) of this AD.

h. Referencing Maintenance Documents or Programs. Do not state that a maintenance document or program is “FAA-approve d” without verification from AFS.

10. Using Notes. Use notes in the text of the rule portion of an AD only for informational purposes where the information is not required by the AD itself, but might help the operator to comply with the AD.

11. Describing Special Flight Permits. 14 CFR part 39 allows special flight permits for every AD. The only way to prohibit or limit special flight permits is by including the limita tion or prohibition in the AD itself. When any special flight permit limitation or prohibition is included in an AD, th e ASE must coordinate with the appropriate AEG.

12. Alternative Methods of Compliance (AMOCs) 20 in Revision or Supersedure AD Actions. Include a provision in the AMOC paragraph of all revision and s upersedure ADs, if you intend to provide credit for previously a pproved AMOCs that continue to be valid. If not all of the AMOCs are valid or approved under the revision or superseding AD, then list those that are. This information might help operators and elimin ate unnecessary applic ations for AMOCs. Previously approved AMOCs continue to be valid for revi sion and supersedure ADs only if the approved AMOC information is included in the revision or supersedure AD. If the revision or supersedure AD does not include the approved AMOC in formation, the AMOC is no longer valid.

20 Refer to FAA Order 8110.103, Alternative Methods of Compliance (AMOC)

52May 17, 2010 FAA-IR-M-8040.1C

Example 8-39: Previous AMOC Information
AMOCs approved previously in accordance with AD 2001-10-01, amendment 39-12226, are approved as AMOCs for the corresponding requirements in paragraph (g) of this AD.

13. Authorization to Perform Work. Work required by ADs can only be done by persons prescribed in 14 CFR 43.3 and 43.7. AD corrective actions are not consid ered preventative maintenance.

14. Reporting Requirements. When we need to know the results of an inspec tion to determine whether we will take additional action, include a statement in the AD to require reporting the results of the inspections to the responsible FAA Office, DAH for th e affected product, or the ci vil aviation authority (or its delegated agent).

a. Reporting and the Paperwork Reduction Act. When a reporting requirement is needed in an AD, the ASE must be able to justify th at requiring reporting meets the criteria of the Paperwork Reduction Act. The Office of Manage ment and Budget (OMB) previously approved the inclusion of reporting requirements in ADs based on the FAA’s need to:

• Help develop a corrective action;

• Determine the scope of the problem and how adequate the DAH corrective actions are; and

• Avoid unsafe consequences if we do not collect the information. We have approval from the OMB to require a repo rt and collect information. According to this Act, we must:

• Specify the information we’re requiring in the report;

• Include the address(es) (e.g., mail, e-mail, f acsimile) to which the reporter sends the report; and

• State that reporting requirements have been approved by the OMB and assigned OMB control number 2120-0056.

b. Quality Control (QC) Problems. Collecting inspection results is one means that can be used to affect quality control on a DAH or repair station. When it appears that we can attribute an unsafe condition addressed by an AD to a DAH’s QC problem, include a reporting requirement in the AD. These reports can help us gather as much information as possible about the nature and extent of the QC problem.

c. Reporting for Repetitive or Continuing Requirements. If we’re requiri ng a report and the AD has repetitive inspections or other continuing requirements, limit the reporting requirement to the initial inspec tion findings unless we determine th at later reports are necessary. If the AD requires repetitive re porting, revise the AD to remove that requirement once the certification office has accumu lated sufficient information.

53May 17, 2010 FAA-IR-M-8040.1C

d. Reporting Requirement Compliance Times.

(1) For domestic ADs that include a reporting requirement, use the following compliance times:

Table 8-1: Reporting Compliance Times

AD Action Compliance Time
IARs 10 days Any AD other than an IAR or emergency AD 30 days

(2) Consider, on a case-by-case basis, those ADs where the ASE considers the need for information to be critical enough to warrant an even shorter compliance time than those provided above. When including compliance times shor ter than those provide d above, additional justification and discussion for deviating from the compliance times provided above is required in the AD worksheet, e.g., just saying it is urgently needed is insufficient.

15. Material Incorporated by Reference. If the AD instructions mandate use of servi ce information, the OFR approves the document for incorporation by reference. Chap ter 10 of this Manual explains the approval process regarding referenced material.

16. Signature Block. The signature block is the last item on the last page of the AD. It has two parts: the Issuing Statement, and the Signature of the Issu ing Official. Include both of these.

a. Issuing Statement. The issuing statement is the city and state where the signing official signed the document and the date when we issued the document.

Example 8-40: Issuing Statement
Issued in [city, state], on [date]

b. Signature of Issuing Official. Only the Directorate Manager, the Assistant Directorate Manager, or their actors may sign the AD. No one may sign an AD “for” the Directorate Manager or the Assistant Director ate Manager. The OFR requires that the typed name and title of the signer appear below the signature.

• For handwritten signatures, signers must use any color other than black ink to make sure the original document won’t be confused with copies. The OFR recommends that signers use blue ink.

• For electronic signatures, signers must be authorized by the GPO.

17. Specialized AD Subjects.

a. ADs for Surplus Aircraft of the U.S. Armed Forces. An AD issued against surplus aircraft of the U.S. Armed Forces that have ci vilian TCs must be issued on the basis of civil

54May 17, 2010 FAA-IR-M-8040.1C

operating experience or appropriate military experience similar to civil operations.

b. ADs that Affect Products in Production. Some ADs require a specific design change (or equivalent) for products that are currently in production. Compliance with the actions in the AD is accomplished before the product leaves the production facility.

c. ADs to Change Life Limits or Inspections. Life limits and inspections change when current life limits contribute to unsafe conditions , or when inspections are needed to check for the presence of unsafe conditions. Not all products have Instructions for Continued Airworthiness (ICA) and not all operators are requir ed to follow ICA. We can enforce changes to life limits and inspections in the following ways:

(1) Including the Life Limits and Inspections in the AD Action. We can write reduced life limits or new or different in spection requirements to address an unsafe condition directly into an AD. For example:

Example 8-41: Typical Language for Life Limited Parts
Remove the torque link and replace it with a new or serviceable part before accumulating 5,000 cycles on the torque link, or within 50 hours TIS after the effective date of this AD, whichever occurs later. Thereafter, replace torque link, P/N 13579, with a serviceable part before accumulating 5,000 cycles.

(2) Requiring a Revision to the Limita tions Section through an AD Action. The DAH might revise the ALS to reduce the life limits or to impose new or different inspection requirements to address an unsafe condition. For this to be mandato ry, issue an AD that requires revision of the ALS. Once the ALS section is re vised, the AD has been fully complied with and the life limit or inspection change remains enfor ceable as a part of the ALS. Requiring revision of the ALS, rather than requiring individual repetitive inspections, is advantageous for operators. It allows them to record AD compliance once when they make the revision, rather than after every inspection. Example 8-42 shows AD language to revise airworthiness limitations. Paragraph (2) in Example 8-42 is also nece ssary because 14 CFR 91.403(c) would otherwise permit operation under alternativ e inspection intervals set fo rth in approved operations specifications or inspection programs, which migh t conflict with the intervals required by the AD.

Example 8-42: Language to Revise Airworthiness Limitations
(1) Revise the airworthiness limitations section, as follows:

__________ (2) Thereafter, except as provided in paragraph (h) of this AD, no alternative replacement times or structural inspection intervals may be approved for this [part].

d. ADs that Revise FAA-Approved Flight Manuals.

(1) Only an AD can mandate changes to the Limitations Section of an FAA-approved

55May 17, 2010 FAA-IR-M-8040.1C

Aircraft or Rotorcraft Flight Manual (AFM/RFM). An owner or operator doesn’t have to comply with any change to a manual other than a cha nge mandated by an AD. Service information, even if FAA-approved, can’t mandate comp liance for products in service.

(2) When the AD requires changing the AFM/RF M, compliance is complete when the affected party:

(a) Makes the manual revisions,

(b) Installs any related required pl acards (if appropriate); and

(c) Makes a maintenance record entry or gains Principal Operations Inspector approval of change to a customized AFM/RFM.

(3) If the intent is to mandate the AFM/RF M provision, the AD must specify adding that provision to the limitations section of the AF M/RFM, since that’s the only section of the AFM/RFM that’s mandatory. 21 If it is intended that the adde d AFM/RFM provisions be advisory only (e.g., warnings), the provisions may be a dded to other appropriate sections of the AFM/RFM by issuing an AD.

e. ADs that Correct Maintenance-Related De fects or Quality Control Failures.

(1) We may issue an AD to change current maintenance procedures if the current maintenance procedures are incorr ect or incomplete, and thereby lead to an unsafe condition. We don’t issue ADs to correct individu al cases of improper maintenance or lack of maintenance that contributed to or produc ed an unsafe condition.

(2) We may also issue an AD if, as a result of a quality control failure, a product does not meet its type design, and the nonconforma nce results in an unsafe condition.

f. ADs for Products Manufactured Outside the U.S. We issue ADs against products manufactured outside the Unite d States that are type-certif icated under 14 CFR 21.29 (or its predecessor, CAR 10) under the same circumstan ces as we issue ADs against domestic products, that is, when we determine that an unsafe condi tion might exist or develop in other products of the same type design. Refer to FAA Order 8040.5, Airworthiness Directive Process for Mandatory Continuing Airworthiness Information , for guidance addressing MCAI-related ADs.

21 14 CFR 91.9

56May 17, 2010 FAA-IR-M-8040.1C

Chapter 9. Public Comments

1. Purpose of this Chapter. This chapter explains:

a. The APA requirement for considering comments;

b. Where to place comments and when to begin dispositioning them;

c. How to handle comments received on FRCs and late comments; and

d. How to disposition comments.

2. APA Requirement.

a. The APA requires that agencies fully consid er all comments received in response to NPRMs. We comply with this APA requirement in the “Comments” section of a final rule. It is not necessary to address comments that are not relevant to the NPRM or the unsafe condition addressed by it, although relevance is not always obvious and is ultimately a legal question. The disposition of comments in the preamble of a final rule shows that the FAA’s decision to promulgate a rule is not “arbi trary and capricious” and, therefor e, is not subject to being invalidated by a court. Comments are usually directed at the most controversial pa rts of rules, and the answers to the comments could protect the AD from future legal or poli tical challenge.

b. Section 553(c) of the APA requires that we give the public time to comment on a proposed AD. The APA doesn’t give any par ticular amount of time for a comment period.

3. Where to Find Comments in the Docket. Comments can be found at the Federal eRulemaking Portal website http://www.regulations.gov

. All comments received via postal mail, email, or fax must be posted at http://www.regulations.gov

.
4. No Comments Received. If no comments are received, mark the checkbox “No Comments Received” and place the page onto FDMS at http://www.regulations.gov

.
5. Comment Disposition. Place in FDMS any written or oral comments we receive including supportive or “no objection” comments. Begin dispositioning comments as soon as the comment period closes using the “Disposition Comments” page(s) from the AD work sheet. Evaluate all comments, and any other related information received in response to the proposed AD. Decide whether or not changes are within the scope of the NPRM. 22

6. Comments to FRCs.

a. We request public comments in FRCs. If comments, including supportive or “no

22 Refer to Chapter 2, paragraph 4g

57May 17, 2010 FAA-IR-M-8040.1C

objection” comments, are received during the comme nt period to an FRC, one of the following must be done:

(1) Complete the form entitled “Comments in Response to ‘Final rule; request for comments’” after the comment peri od has closed and the comments analyzed. This form must be posted to FDMS.

(2) Respond directly to the commenter in writi ng. A copy of the comment (if not already in FDMS) and the response must be posted to FDMS.

b. If comments warrant a change to an FRC, publish a disposition of the comments that warranted the change in a subsequent AD action. You may also use the preamble to discuss other comments received.

c. If a comment raises a significant issue that might have wide or c ontinuing interest among members of the affected public, but does not result in a change to an F RC, publish a response to the comment in the Federal Register as a “Final rule; disposition of comments.”

7. Late Comments.

a. Place in FDMS any late written or oral comm ents we receive after the comment period closes.

b. If a person files a comment after the comment period closes, under 14 CFR 11.45(b), consider late comments to the extent possible only if they do not si gnificantly delay the rulemaking process (i.e., check for and consider incorporating any comments received until the final rule is issued). For FRCs, check for and consider any comments r eceived for a period of 30 calendar days after th e comment period closes.

8. How to Disposition Comments.

a. Organizing Comments. Group the comments by issue, not by commenter. Don’t group all of the comments made by one commenter together.

b. Identifying Commenters.

(1) Don’t refer to the commenter’s gender.

(2) Identify all commenters by name or or ganization. For cases when different commenters send a comment relating to the same issu e, not all commenters need to be identified. Instead, refer to the commenters generically by group (e.g., Five carriers requested that the proposed rule be modified to include . . .). If one commenter in the group addressed the issue more thoroughly than the others, or is potentially more adversely impacted by the AD than the others, it is appropriate to ca ll that commenter by name (e.g., De lta requested that the proposed rule be modified to include . . . . Seve ral other carriers echoed this approach.).

58May 17, 2010 FAA-IR-M-8040.1C

c. Addressing Comments.

(1) Always address comments in the past te nse (“One commenter requested that we modify the proposed rule to include. . . ”).

(2) If we agree with a comment as stated by the commenter, don’t restate the reason when agreeing with it. If ther e is an additional reason for agreement, include that reason.

(3) If a commenter proposes a change but does not give any reasons for it, state that the commenter does not justify the requested change.

(4) If a commenter simply states an observation but does not propose a change, infer the change. For example, if the commenter states, “T he proposal would not be cost effective,” infer that the commenter would like to see the proposal withdrawn.

(5) Acknowledge supportive or “no objection” comments.

(6) If you change the AD in response to a comm ent, include a statement to explain the change.

(7) Do not state that a comment is “beyond the scope of the notice.” The word “scope” is a legal term that implies notice according to the APA requirement that agencies give the public the opportunity to comment. We are prohibited from adopting rules that are “beyond the scope” of the notice without providing additional opportunity fo r public comment. If we disagree with the comment, give solid reasons for disagreeing rather than sayi ng simply that the comment is “beyond the scope.” If a comment is beyond the scope of the notice, but stil l has merit, consider additional rulemaking. For example:

(a) Issue a SNPRM if the change itself doesn’ t address an immediate safety of flight problem. Doing this gives the publ ic additional time to comment on the change before adopting a final rule.

(b) Issue a final rule that is within the scope of the original proposed AD. Then issue a new proposed AD to supersede the AD with a ne w AD action that incorporates the necessary change.

(c) Issue an IAR that incorporates the change . Use this option if the change addresses an immediate safety of flight problem. Discuss the comments submitted for the proposed AD and solicit additional comments.

(8) If you are unsure how to address a comme nt, talk to your Regional Airworthiness Counsel.

59May 17, 2010 FAA-IR-M-8040.1C

Chapter 10. Incorporation by Reference and Appendices

1. Purpose of this Chapter. This chapter describes incorporating material by reference or as an appendix to an AD action.

2. Incorporation by Reference (IBR).

a. Incorporation by reference allows Federal agen cies to comply with the requirement to publish rules in the Federal Register by referring to materials alre ady published elsewhere. The legal effect of IBR is that the material is treated as if it were published in the Federal Register

. This material, like any other properly issued ru le, has the force and effect of law. Congress authorized IBR in the Freedom of Information Ac t to reduce the volume of material published in the Federal Register and the Code of Federal Regulations (CFR). For guidance on IBR procedures, see the Fe deral Register DDH at http://www.archives.gov/federal-register

.
b. The OFR will not publish the final rule AD in the Federal Register until the reference material is approved.

c. The OFR does not require that you resend se rvice information that they previously approved for IBR.

3. Incorporating Material as Appendices. If supplemental information is inappropriate for IBR, or if actual publication is preferable, you may add the information to the AD as an appe ndix. You may use selected parts of a service bulletin as an appendix. The most important thing to remember is that, for the purposes of the AD, the material in the appendix is sent by the FAA, and is not someone else’s publication. For this reason, it is critical that you identify everyt hing that you do not want pr inted (e.g., letterhead, stray lines or marks, or any information not referenced in the AD language). Refer to the DDH for additional information.

a. Referencing an Appendix within the AD. In the text of the AD action, only refer to the appendix number (“in accordance with Appendix 1 of this AD...,” for example). Do not use an appendix as an alternative to IBRing a service document.

b. Numbering Paragraphs or In structions in an Appendix. Although the appendix might be an extract from another document, the append ix must be complete. Check that the appendix does not begin with extracted details (e.g., “Instruction 4,”). If n ecessary, redesignate paragraphs so the appendix does not appear to be missing information.

61May 17, 2010 FAA-IR-M-8040.1C

Chapter 11. AD Docket

1. Purpose of this Chapter. This chapter describes what information a nd documents are placed in the AD docket (i.e., FDMS).

2. Maintaining the AD Docket. We must maintain a docket for each AD acti on in FDMS. The docket must include enough information to support the AD action. Don’t incl ude any drafts of the AD or any copies not identical to the version sent to the OFR. De stroy all paper copies once placed into FDMS.

3. AD Docket Contents. Except for proprietary data, the AD docket must contain any documents that support the 14 CFR part 39 action. The following information, at a mi nimum, must be placed in the AD docket at website http://www.regulations.gov :

a. Record of technical decisionmak ing (i.e., the version of the AD action that is published in the Federal Register or emergency AD);

b. FAA reports, summaries or lists of facts, data, or reports that support the AD action;

c. ADs or other similar documents issued by an international civil aviation authority;

d. Regulatory Evaluation Form;

e. Records of each ex parte cont act or series of contacts;

f. Comments received on the propos ed rulemaking (if any); and

g. Records of approval of IBR documents.

4. Proprietary Data in AD Dockets. Give careful consideration to i ssues related to including or excl uding proprietary information in the AD docket, since all documents in the docke t are available for public inspection. We must have enough information in the docket to form the basis for our rulemaking action and support the choices we made. Exclude pr oprietary data from a DAH or other sour ce, unless the DAH or other source specifically states that we can incl ude it in the docket. All documents placed in the AD docket are available for public inspection. Consult with the Regional Ai rworthiness Counsel for any questions.

63May 17, 2010 FAA-IR-M-8040.1C

Appendix A. Acronyms

AC — Advisory Circular

ACO — Aircraft Certification Office

ACMT — Aircraft Certif ication Management Team

AD — Airworthiness Directive

ADC — AD Coordinator
AEG — Aircraft Evaluation Group
AFM — Aircraft Flight Manual

AGC — Office of the Chief Counsel

AIR — Aircraft Certification Service

ALS — Airworthiness Limitations Section

AMOC — Alternative Method of Compliance
ANPRM — Advanced Notice of Proposed Rulemaking

AOA — Office of the Administrator

APA — Administrative Procedures Act
ASE — Aerospace Engineer
ATA — Air Transport Association of America
CAA — Civil Aviation Authority

CANIC — Continued Airworthiness Notifi cation to the International Community
CAR — Civil Air Regulation
CFR — Code of Federal Regulations
CMO — Certificate Management Office
COS — Continued Operational Safety
DAH — Design Approval Holder
DDH — Document Drafting Handbook

A-1May 17, 2010 FAA-IR-M-8040.1C

DOT — Department of Transportation
ECO — Engine Certification Office

FAA — Federal Aviation Administration
FAR — Federal Aviation Regulation
FDMS — Federal Docket Management System

FR — Final Rule
FRC — Final rule; request for comments

FRV — Final Rule Version
GPO — Government Printing Office
IAR — Immediately Adopted Rule
ICAO — International Civil Aviation Organization
IBR — Incorporation by Reference
JASC — Joint Aircraft System/Component Code
MCAI — Mandatory Continuing Airworthiness Information
MCO — Military Certific ation Office, ACE-100M
MIDO — Manufacturing Inspection District Office
MIO — Manufacturing Inspection Office

NARA — National Archive and Records Administration
NPRM — Notice of Proposed Rulemaking
OFR — Office of the Federal Register
OMB — Office of Management and Budget

P/N — Part Number
PMA — Parts Manufacturer Approval
RIN — Regulatory Information Number
RFM — Rotorcraft Flight Manual

A-2May 17, 2010 FAA-IR-M-8040.1C

RGL — Regulatory Guidance Library

S/N — Serial Number
SFAR — Special Federal Aviation Regulation
SNPRM — Supplemental Notice of Proposed Rulemaking
STC — Supplemental Type Certificate
TC — Type Certificate
TCDS — Type Certificate Data Sheet

TIS — Time-in-service

TSO — Technical Standard Order

USC — United States Code

A-3U.S. Department of Transportation

Federal Aviation Administration

Directive Feedback Information
Please submit any written comments or recomm endation for improving this directive, or suggest new items or subjects to be added to it. Also, if you find an error, please tell us about it.

Subject: FAA-IR-M-8040.1C, Airworthiness Directives Manual
To: Directive Management Officer, AIR-530
(Please check all appropriate line items)
An error (procedural or typogra phical) has been noted in paragraph

_______ on page

_______ . Recommend paragraph

_______ on page

_______ be changed as follows: (attached separate sheet if necessary)

In a future change to this order, please include coverage on the following subject (briefly describe what you want added):

Other comments:

I would like to discuss the above. Please contact me.

Submitted by:

________________________________________ Date:

_________________

Telephone Number:

____________________ Routing Symbol:

____________________ FAA Form 1320-19 (10-98)