Order 8110.52 Type Validation and Post-Type Validation Procedures
This document is cancelled. Cancelled by 8110.52A. Check the official source before relying on it.
ORDER 8110.52
TYPE VALIDATION AND POST-TYPE VALIDATION PROCEDURES
April 29, 2005
DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION
Distribution: A-W (IR/FS/EE)-3; A-X (CD/FS)-3 Initiated By: AIR-110 A-FAC-O(ALL); A-FFS-10 (ALL)
RECORD OF CHANGES DIRECTIVE NO.
8110.52
CHANGE
DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION
TO
SUPPLEMENT
OPTIONAL
CHANGE
TO
SUPPLEMENTS
OPTIONAL BASIC BASIC
FAA Form 1320-5 (6-80) USE PREVIOUS EDITION
4/29/05 8110.52
Page i (and ii)
FOREWORD In this order, we define the principles guiding Aircraft Certification Office and Directorate staffs certificating imported and exported aircraft, engines, and propellers. We also define principles used to maintain the continued airworthiness of imported and exported products. We prescribe the roles and responsibilities of the importing authority (the validating authority or VA), the exporting authority (the certificating authority or CA), and the applicant. We set up specific procedures for certification personnel working with the European Aviation Safety Agency (EASA) and the Joint Aviation Authorities of Europe (JAA). The procedures are based on the type validation principles (TVP) and post-type validation principles (PTVP) we adopted with EASA and JAA. We define certification personnel duties when we at the FAA are the validating authority, and when we are the certificating authority. If we adhere to these principles and procedures, we’ll ensure an imported product will meet the same level of safety as a comparable product designed, manufactured, and certified within the validating authority’s country. Susan J. M. Cabler Acting Manager, Aircraft Certification Division
OPTIONAL BASIC BASIC
4/29/05 8110.52
Page iii
TABLE OF CONTENTS CHAPTER 1. GENERAL
Paragraph Page 1. Purpose … 1 2. Distribution … 1 3. Scope … 1 4. Background … 2 5. References … 3 6. Suggestions for Improvement … 3 7. Records Management … 3 8. Definitions … 3 9. Acronyms … 3 10. thru 199. Reserved … 3
CHAPTER 2. TYPE CERTIFICATION, TYPE VALIDATION, AND POST-TYPE VALIDATION: AN OVERVIEW
CHAPTER 2. TYPE CERTIFICATION, TYPE VALIDATION, AND POST-TYPE VALIDATION: AN OVERVIEW
200. General … 5
SECTION 1. TYPE CERTIFICATION AND TYPE VALIDATION
201. Type Certification … 5 202. Type Validation … 6 203. Conducting an FAA Validation … 7 204. FAA Validation Process … 8 205. Communications … 9 206. Supplemental Type Certificates (STC) … 10 207. thru 219. Reserved … 10
SECTION 2. POST-TYPE VALIDATION
SECTION 2. POST-TYPE VALIDATION
220. Post-Type Validation Activities … 11 221. VA Responsibilities During Post-Type Validation … 11 222. CA Responsibilities During Post-Type Validation … 11 223. thru 299. Reserved … 12
CHAPTER 3. FAA/EASA/JAA TYPE VALIDATION PROCEDURES
SECTION 1. INTRODUCTION
SECTION 1. INTRODUCTION
300. General … 13 301. Applicability … 13 302. Sequential vs. Concurrent Certification/Validation … 13
SECTION 2. TYPE VALIDATION: KEY CONCEPTS
303. New Terminology … 14 304. Validation Authority Certification Basis … 14 305. Validation Item (VI) … 15
Page iv
Paragraph Page 306. Generic Validation Items … 15 307. Project Validation Items … 16 308. Standards Equivalencies … 17 309. Standards Differences … 17 310. Methods Of Compliance (MOC) … 19 311. Compliance Determinations … 19 312. Issue Papers, Certification Review Item (CRI) and Action Item (AI) … 20 313. Type Validation: Four Phases … 20 314. Phase I: General Familiarization … 21 315. Phase II: Technical Familiarization … 21 316. Phase III: Determining VA Involvement … 22 317. Phase IV: Compliance Determinations … 23 318. Program Schedules and Accountability … 23 319. Product Familiarity and Continued Airworthiness Responsibilities … 24 320. Approved Manuals … 25 321. Supplemental Type Certificates … 26 322. Communications … 27 323. Issue Resolution Process … 27 324. Program Reviews … 28 325. thru 329. Reserved … 28
SECTION 3. RESPONSIBILITIES OF DIRECTORATE STANDARDS STAFF
SECTION 3. RESPONSIBILITIES OF DIRECTORATE STANDARDS STAFF
330. General … 28 331. Comparisons of 14 CFR and CS/JAR Text … 29 332. Identifying Standards Equivalencies … 29 333. Standards Differences Lists … 30 334. Program Status Monitoring … 33 335. thru 339. Reserved … 33
SECTION 4. FAA AS THE VALIDATING AUTHORITY
SECTION 4. FAA AS THE VALIDATING AUTHORITY
340. General … 33 Figure 3-1. VA Four-Phase Type Validation Process … 35 341. Phase I: General Familiarization … 36 342. FAA Receives Application through EASA or NAA … 36 343. Applicant, EASA, and FAA Conduct the General Familiarization Meeting … 37 344. Phase II: Technical Familiarization … 39 345. Applicant, EASA, and FAA Conduct Technical Familiarization Meetings … 41 346. FAA Establishes Certification and Validation Authority Certification Bases … 44 347. FAA Defines the VIs … 45 348. FAA Identifies Applicable Generic VIs … 46 349. FAA Identifies Project VIs … 46 350. FAA Identifies Applicable SSD and Non-SSD … 47 351. Phase III: Determining FAA Involvement … 50 352. FAA Determines Level of Involvement for the VIs … 51 353. Phase IV: Compliance Determinations … 52 354. EASA Makes Compliance Determinations for Assigned VIs and Non-SSD … 54 355. FAA Makes Compliance Determinations for Retained VIs … 54 356. EASA Issues Statement of Compliance to the FAA Certification Basis … 54
4/29/05 8110.52
Page v
Paragraph Page 357. FAA Issues a Type Certificate … 55 358. Responsibilities When the FAA Is the VA … 55 Figure 3-2. Responsibilities When FAA Is VA … 56 359. Supplemental Type Certificates … 58 360. thru 369. Reserved … 59
SECTION 5. FAA AS THE CERTIFICATING AUTHORITY
370. General … 59 Figure 3-3. CA Four-Phase Type Validation Process … 60 371. Phase I: General Familiarization … 61 372. FAA Reviews Application and Forwards It to EASA … 61 373. Applicant, EASA, and FAA Conduct the General Familiarization Meeting … 62 374. Phase II: Technical Familiarization … 64 375. Applicant, EASA, and FAA Conduct Technical Familiarization Meetings … 67 376. EASA Establishes Validating Authority Certification Basis … 70 377. EASA Defines the VIs … 70 378. EASA Defines SSD and Non-SSD … 71 379. Phase III: Determining EASA Involvement … 71 380. EASA Determines Level of Involvement for the VIs … 72 381. Phase IV: Compliance Determinations … 74 Figure 3-4. Phase IV: Compliance Determination Components (FAA as CA) … 76 382. FAA Makes Compliance Determinations for Assigned VIs and Non-SSD … 77 383. EASA Makes Compliance Determinations for Retained VIs … 77 384. FAA Issues Statement of Compliance to the EASA Certification Basis … 77 385. Applicant Declares Compliance to the EASA VA Certification Basis … 78 386. EASA Issues Type Certificate … 79 387. EASA Informs JAA NAAs of Type Certificate Issuance … 79 388. Non-EU JAA NAAs Issue Type Certificate … 79 389. Responsibilities When the FAA Is the CA … 79 Figure 3-5. Responsibilities When the FAA Is the CA … 80 390. Supplemental Type Certificates … 82 391. thru 399. Reserved … 83
CHAPTER 4. FAA/EASA/JAA POST-TYPE VALIDATION PROCEDURES
CHAPTER 4. FAA/EASA/JAA POST-TYPE VALIDATION PROCEDURES
SECTION 1. INTRODUCTION
400. General … 85 401. Scope … 85 402. Vision … 86
SECTION 2. CONTINUED AIRWORTHINESS
403. General … 86 404. Communication … 87 405. Level of Involvement … 87 406. Roles and Responsibilities … 88 407. Service Information Approval … 89
SECTION 2. CONTINUED AIRWORTHINESS
Page vi
Paragraph Page 408. Updates to the Master Minimum Equipment List (MMEL) and the Instructions for Continued Airworthiness … 89 409. FAA as the Validating Authority … 89 410. FAA as the Certificating Authority … 90
SECTION 3. TYPE DESIGN CHANGE APPROVAL PROCESS
411. General … 91 Figure 4-1. Type Design Change Approval Process (Including Approval of Revisions to Approved Manuals) … 94 412. Major Design Change Categorization … 95 413. Recordkeeping … 96 414. thru 419. Reserved … 96
SECTION 4. TYPE DESIGN CHANGE APPROVAL: FAA AS THE VALIDATING AUTHORITY
SECTION 4. TYPE DESIGN CHANGE APPROVAL: FAA AS THE VALIDATING AUTHORITY
420. General … 96 421. Type Certificate Holder Classifies Design Change … 97 422. FAA Notified of Level 1 Major Design Change … 97 423. FAA Responds to Level 1 Design Change Application … 98 424. FAA Establishes Ceritication Basis for Level 1 Major Design Changes … 99 425. FAA Determines Involvement in Level 1 Major Design Changes … 99 426. Closing Actions for Level 1 Major Design Changes … 101 427. Level 2 Major and Minor Design Changes … 101 428. Record Keeping … 102 429. Updates to the VI List … 102 430. thru 439. Reserved … 102
SECTION 5. TYPE DESIGN CHANGE APPROVAL: FAA AS THE CERTIFICATING AUTHORITY
SECTION 5. TYPE DESIGN CHANGE APPROVAL: FAA AS THE CERTIFICATING AUTHORITY
440. General … 102 441. Type Certificate Holder Classifies Design Change … 102 442. EASA Notified of Level I Major Design Changes … 103 443. EASA Responds to Level 1 Design Change Application … 104 444. EASA Establishes Certification Basis for Level 1 Major Design Changes … 105 445. EASA Determines Involvement in Level 1 Major Design Changes … 105 446. Closing Actions for Level 1 Major Design Changes … 106 447. Level 2 Major and Minor Design Changes … 107 448. Record Keeping … 107 449. Updates to the VI List … 107 450. thru 499. Reserved … 107
APPENDIX 1. EUROPEAN UNION MEMBER STATES WITH BAA OR BASA IPA WITH THE UNITED STATES (1 page)
APPENDIX 1. EUROPEAN UNION MEMBER STATES WITH BAA OR BASA IPA WITH THE UNITED STATES (1 page)
APPENDIX 2. DEFINITIONS OF TERMS USED IN THIS ORDER (4 pages)
APPENDIX 3. ACRONYMS (1 page)
4/29/05 8110.52
Page vii (and viii)
APPENDIX 4. FAA/EASA/JAA TYPE VALIDATION PRINCIPLES/POST-TYPE VALIDATION PRINCIPLES (33 pages)
APPENDIX 5. TYPE VALIDATION PROJECT REVIEW CRITERIA (2 pages)
APPENDIX 5. TYPE VALIDATION PROJECT REVIEW CRITERIA (2 pages)
4/29/05 8110.52
CHAPTER 1. GENERAL
1. PURPOSE. This document defines FAA policy and procedures in type certification and post-type certification for imported and exported products (aircraft, aircraft engines, or propellers).
CHAPTER 1. GENERAL
a. We define the expectations, roles, and responsibilities of the importing authority (the validating authority, or VA), the exporting authority (the certificating authority, or CA), and the applicant. We establish specific procedures for certification personnel working with the European Aviation Safety Agency (EASA) and member authorities of the Joint Aviation Authorities of Europe (JAA). This order incorporates Notice 8110.70, FAA/JAA Type and Post- Type Validation Principles
b. If we adhere to these principles and procedures, we’ll ensure an imported product that meets the same level of safety as a comparable product designed, manufactured, and certified within the VA’s jurisdiction.
2. DISTRIBUTION. Distribute this order to the Washington headquarters branch levels in the Aircraft Certification Service, Flight Standards Service, and Office of Environment and Energy; the branch levels of the regional aircraft certification directorates and regional Flight Standards Divisions; all aircraft certification field offices; all Aircraft Evaluation Groups (AEG).
3. SCOPE.
a. All Bilateral Partners. The principles in chapter 2 apply to certification/validation programs with all bilateral partner authorities. You will find more guidance in advisory circular (AC) 21-23, Airworthiness Certification of Civil Aircraft, Engines, Propellers, and Related Products Imported to the United States, dated November 17, 2004. FAA certification personnel must consult the appropriate bilateral airworthiness agreements (BAA) or bilateral aviation safety agreement implementation procedures for airworthiness (BASA IPA) to determine specific expectations for an individual bilateral partner and us.
(1) Do not develop extra certification procedures without first contacting the International Policy Office, AIR-40, and the Certification Procedures Branch, AIR-110. If you are on a validation team, however, your team may set up project-specific documents on administrative details such as team members, responsibilities, and schedule commitments. These administrative details must be consistent with chapter 2 of this order, AC 21-23, and the applicable bilateral agreement.
(2) You can obtain an up-to-date list of countries with which the United States has a bilateral agreement from AIR-40, or directly from their website (http://www.faa.gov/certification/aircraft/BAA-BASA_Listing.htm). AC 21-23 also lists the types of products allowable for import from each country.
b. European Aviation Safety Agency (EASA). The European Parliament approved legislation setting up EASA in July 2002. The new agency began operating in September 2003, assuming the certification and validation authority previously exercised by individual national aviation authorities (NAAs). EASA will recognize existing bilateral agreements between the
United States and European Union member states until a single, new bilateral agreement is negotiated between the United States and the European Union. FAA certification personnel must use the procedures in chapters 3 and 4 when:
(1) Conducting validation programs on imported products of European Union countries where the applicant seeks an FAA type certificate (TC) or supplemental type certificate (STC). (Note that the United States must have a BAA or BASA IPA with that country), or
(2) Conducting certification programs on U.S. products where the applicant seeks an EASA type certificate (TC) or supplemental type certificate (STC).
NOTE: Appendix 1 lists all European Union member states with a BAA or BASA IPA with the United States.
c. Joint Aviation Authorities of Europe (JAA). Because not all countries in Europe are member states of the European Union, U.S. companies will still seek approval from the JAA as the representative of those countries. JAA has agreed to accept an EASA certification decision as the basis for its recommendation to member authorities, without additional investigation.
(1) FAA certification personnel must use the procedures in chapters 3 and 4 when conducting certification programs on U.S. products for which the applicant seeks a type approval from the JAA or a non-EU JAA member authority.
(2) FAA certification personnel may also use the procedures in chapters 3 and 4 when conducting validation programs on products being imported from Norway, Romania, and Switzerland at the specific request of their NAA.
4. BACKGROUND. In the mid-1990’s, the JAA and we recognized the need to streamline certification and continued airworthiness processes applied to imported aviation products. We established type validation and post-type validation principles in a letter of understanding, signed in November 1997. These principles were amended in November 2001. The FAA and NAAs who are members of JAA currently apply these principles when validating products designed/manufactured in each other’s countries.
a. FAA/EASA/JAA Type Validation and Post-Type Validation Principles. Forming EASA gave everyone the opportunity to look at the validation and post-validation processes, to incorporate lessons learned, and tailor them to the new European aviation certification system. As a result, we streamlined the principles and extended the scope. FAA/EASA/JAA type validation principles and post-type validation principles are in appendix 4. EASA, JAA, and we agreed to this document in October 2004.
b. Airworthiness Standards. In TVP/PTVP, we refer to the airworthiness codes used by both FAA and EASA as “airworthiness standards” or “standards.” These standards include those in Title 14 of the Code of Federal Regulations (14 CFR) and EASA Certification Specifications (CS). We cannot call them “requirements” or “regulations” due to the European Union’s unique regulatory structure.
4/29/05 8110.52
Page 3 (and 4)
5. REFERENCES.
a. Title 14, Code of Federal Regulations (14 CFR) part 21.
b. FAA Order 8100.5, Aircraft Certification Service Mission, Responsibilities, Relationships, and Programs.
c. FAA Order 8110.4, Type Certification.
d. FAA Order 8110.37, Designated Engineering Representative (DER) Guidance Handbook.
e. FAA Advisory Circular 21-23, Airworthiness Certification of Civil Aircraft, Engines, Propellers, and Related Products Imported to the United States.
f. International Civil Aviation Organization (ICAO) Annex 8, Airworthiness of Aircraft.
g. FAA Airworthiness Directive Manual, FAA-AIR-M-8040.1
6. SUGGESTIONS FOR IMPROVEMENT.
a. If you find deficiencies, need clarification or want to suggest improvements to this order, please send a record (written or electronic) to the Aircraft Certification Service, Planning and Financial Resources Management Branch, AIR-530, Attention: Directives Management Officer. You can use FAA Form 1320-19, Directive Feedback Information, available at http://feds.faa.gov/
b. You may also send a copy to the Aircraft Engineering Division, AIR-100, Attention: Comments to Order 8110.XX. If you urgently need an interpretation, you may contact AIR-110 at 202-267-9588. Always use Form 1320-19 to follow up each verbal conversation.
7. RECORDS MANAGEMENT. Refer to FAA Orders 0000.1, FAA Standard Subject Classification System, 1350.14, Records Management; and 1350.15, Records, Organization, Transfer, and Destruction Standards, or see your office Records Management Officer/Directives Management Officer for how to retain or dispose of records.
8. DEFINITIONS. See appendix 2.
9. ACRONYMS. See appendix 3.
10. –199. RESERVED
10. –199. RESERVED
4/29/05 8110.52
CHAPTER 2. TYPE CERTIFICATION, TYPE VALIDATION, AND POST-TYPE
VALIDATION: AN OVERVIEW
200. GENERAL. All aircraft, engines, and propellers must meet and maintain minimum design and performance standards before they can be produced and operated.
a. ICAO requires each contracting state to adopt airworthiness standards for the design and performance of aeronautical products. States must ensure that aircraft, including components (engines and propellers), meet these airworthiness standards. ICAO allows states to accept a product approved by another ICAO contracting state without further showing, or to render valid another country’s determination that a product meets airworthiness standards.
VALIDATION: AN OVERVIEW
(1) Two ways of determining a product is airworthy, depending on its origin, are type certification and type validation.
(2) Section 1 below defines the general principles FAA certification personnel follow when carrying out certification and validation programs.
b. The responsibilities of the certificating authority (CA) and validating authority (VA) do not end once an aircraft, engine, or propeller is certificated/validated. Under ICAO Annex 8, the state of registry is responsible for the safety of any aircraft on their national register. This means the VA becomes accountable for the continued airworthiness of imported products operated under their registry. The CA, as state of design, must send mandatory continuing airworthiness information to the state of registry.
(1) We refer to these collectively as “post-type validation activities.” Like type validation, they require the close cooperation of both CA and VA. (See paragraph 202.)
(2) Section 2, further on, defines the principles FAA certification personnel follow when performing post-type validation functions.
SECTION 1. TYPE CERTIFICATION AND TYPE VALIDATION
SECTION 1. TYPE CERTIFICATION AND TYPE VALIDATION
201. TYPE CERTIFICATION. Type certification is the process by which an aviation authority determines compliance of a product to applicable standards, such as noise, environmental, procedural, and airworthiness. Aviation authorities use this process to establish compliance of a domestically manufactured product to their national airworthiness standards. We at the FAA, for example, establish compliance to Title 14 of the Code of Federal Regulations (14 CFR) for products designed and manufactured in the United States. Certification requires direct involvement with an applicant to ensure that they show compliance.
a. Certificating Authority (CA). The CA is responsible for the original type certificate. For example, the FAA is the CA for applicants/certificate holders in the United States. The CA issues the final design approval, or compliance finding, for products designed in their country. The CA may document their approval by issuing a TC or STC.
b. When a product is exported to another country, the CA is expected to support their acceptance by the importing country. To minimize duplicate certifications, the CA should be able to act for the importing authority. The CA, therefore, makes compliance findings to their own airworthiness standards and, when agreed in a bilateral agreement, makes compliance determinations to the VA’s airworthiness standards. Note, however, that bilateral agreements are not required for exporting a product. The United States can export a product to a foreign country even though we do not have a bilateral agreement with that country. Applications to nonbilateral countries for their design approvals or import acceptance should still be transmitted from the FAA to the other aviation authority.
c. Regulatory Basis for CA Activities. FAA personnel serving as CA use procedures based on 14 CFR part 21 subpart B. Among other things, these regulations establish certification basis for a product: the applicable noise, fuel venting, exhaust emissions, and airworthiness standards (§ 21.17), equivalent level of safety findings (§ 21.21), special conditions (§ 21.16), and exemptions.
d. FAA Certification Procedures. FAA Order 8110.4, Type Certification Process, defines the procedures used by personnel certificating products designed and manufactured in the United States.
202. TYPE VALIDATION.
a. Aircraft, engines, and propellers are often designed and manufactured in one country and then exported to another.
b. Validation is the process most commonly used to establish the compliance of an imported product to the importing state’s applicable airworthiness standards. Validation is, in other words, a special form of certification.
c. Validating Authority (VA). The VA is responsible for validating the CA TC or STC. We at the FAA are the VA for applicants/approval holders outside the United States.
d. Validations require trust, communication, and cooperation among the authorities and the applicant.
e. Once compliance is established, the VA may issue a type certificate for the product to show the aircraft, engine, or propeller complies with their airworthiness standards. This TC is sometimes called an import TC or a validated TC.
f. Validation is not universally applied. Some aviation authorities have adopted alternate approaches for imported aviation products. Australia, for example, does not issue a TC for products with FAA or EASA/JAA TC. Australian authorities familiarize themselves with the type design so they can capably oversee the aircraft when it is added to the registry. Other authorities have adopted similar approaches.
g. FAA certification personnel must, therefore, consult the bilateral agreement with a foreign country to identify our responsibilities when a U.S. product is exported there.
4/29/05 8110.52
203. CONDUCTING AN FAA VALIDATION. We can conduct validations of foreign products only under bilateral agreements. FAA certification personnel must consult the correct BAA or BASA IPA to find specific expectations for the individual bilateral partner and us.
a. Bilateral agreements are concluded when we are fully confident in a partner aviation authority and where there is a certification system that produces equivalent results to the U.S. system. We start, therefore, assuming that all compliance determinations within the scope of the bilateral agreement can be assigned to the CA. We then decide which determinations to reserve for ourselves due to the design’s complexity or unique features.
b. The FAA should not unnecessarily duplicate work done by the CA. For example, if we’re the VA, we should use issue papers mainly to address differences between FAA and CA airworthiness standards and interpretations. When the CA and FAA airworthiness standards and interpretations are identical, we should rely on the CA to the maximum extent possible. This reliance includes accepting the CA’s issue paper or equivalent in place of an FAA issue paper. Any such acceptance will be based on our validation team’s technical familiarization of the product, and must be supported by the product accountable directorate. In certain cases, even when FAA and CA airworthiness standards and interpretations are identical, we will still need to write our own issue paper. For example, we’ll write issue papers for equivalent safety findings, per § 21.21(b)(1). We will also write issue papers on certification basis and other unique import requirements.
c. Regulatory Basis for VA Activities. The procedures we use as VA are based on 14 CFR § 21.29, Issue of Type Certificate: Import Product.
(1) This regulation says the FAA may issue a TC for a product that is:
(a) Manufactured in a country with which the United States has an agreement to accept these products for export and import, and
(b) To be imported into the United States.
(2) The regulation says the FAA may certificate such a product if the CA of the country in which the product was manufactured certifies that it was examined, tested, and found to meet:
(a) Applicable FAA airworthiness standards as designated in 14 CFR §21.17, or
(b) Applicable CA airworthiness standards plus any other airworthiness standards that the FAA prescribes to provide a level of safety equivalent to 14 CFR § 21.17.
NOTE: 14 CFR § 21.29 has similar provisions for FAA aircraft noise, fuel venting, and exhaust emissions requirements.
(3) In the case of special classes of aircraft (gliders, airships, and other nonconventional aircraft) for which we have not identified acceptable airworthiness criteria, we must make public notification of the airworthiness standards established under 14 CFR § 21.17(b).
204. FAA VALIDATION PROCESS.
a. The validation process begins when an application is submitted to us through the CA. The applicant gives us a familiarization briefing. We establish the certification basis. Technical information goes back and forth in the form of data, specialist meetings, technical compliance, and/or the development of issue papers. Finally, we issue the design approval. Process steps can be summarized as:
(1) Applicant submits application to the FAA through the CA;
(2) Applicant and CA familiarize the FAA with the details of the design, CA certification basis, and the methods of compliance (MOC);
(3) FAA establishes the VA certification basis;
(4) FAA defines areas of special interest in issue papers;
(5) FAA determines their involvement and assigns compliance determinations to the CA;
(6) CA makes compliance determinations to the elements assigned them by the FAA;
(7) FAA makes compliance determinations to any elements of the FAA certification basis that they retained and notifies the CA;
(8) CA issues a final statement of compliance to the FAA’s certification basis; and
(9) FAA issues the TC.
b. A validation program doesn’t duplicate the CA certification program. It is not an opportunity to audit the CA’s competence, or to scrutinize their work.
c. Sometimes the TC application is for a product in a category not previously certificated, or the product is more complex than previously certificated by the CA. We may then increase the scope of the validation program. The CA should notify us as soon as they learn of this pending application, so each authority can plan for any additional resources required.
d. Compliance Determinations. Compliance determinations are the decisions that establish that the applicant has satisfied a specific airworthiness standard. Determinations of compliance to FAA airworthiness standards may be made either by the CA or us. It is our prerogative to determine our involvement in establishing compliance to our airworthiness standards. We may retain the compliance determination, or assign it to the CA. We will formally and specifically identify any retained compliance determinations, preferably early in the program.
NOTE: The FAA may still request technical help from the CA on a retained compliance determination under the terms of a bilateral agreement. For example, we may ask the CA to witness a test for us.
4/29/05 8110.52
(1) We will maximize assigning compliance determinations to the CA. We may entrust all compliance determinations to the CA, and rely solely on their compliance statements. If we retain any compliance determination, we have to justify it.
(2) Once we decide to assign a compliance determination to the CA, we must ensure that they understand any unique FAA requirements for compliance. We must coach the CA on acceptable MOC and provide them with all publications and documents that affect the determinations for the assigned items.
(3) We will accept CA compliance determinations as if we made them ourselves. We will limit our compliance determination activities to specific, formally identified areas, and not review compliance determinations that we assigned to the CA since communication throughout the project ensures the FAA understands what has been accomplished.
(4) When the CA carries out an activity for us, the CA may do it directly or under their legally constituted delegation system. This means that in other countries, the CA may assign compliance determinations to FAA airworthiness standards to one of their delegated organizations.
(5) We must gain enough product knowledge during validation so we can carry out our continued airworthiness responsibilities. Product knowledge includes continued operational safety issues. When justified, we may request compliance documents, including those related to determinations that were assigned to the CA.
e. Compliance Findings. Based on the compliance statement from the CA and the summary of compliance determinations, we make a final compliance finding and issue a TC.
205. COMMUNICATIONS. Communication is critical to success. Our experience with validation programs shows that effective communication between the VA, CA, and applicant is vital. Program delays are often the result of miscommunication.
a. Communicating with the Applicant.
(1) When acting as VA, we at the FAA must work through the CA to achieve airworthiness standards compliance. Communications should flow through the CA to the applicant. On the rare occasion when the CA cannot be involved, we are responsible for giving them details of any communication with a foreign applicant.
(2) The CA, FAA and applicant will have frequent, regularly scheduled telephone conferences to review the program status, discuss open validation issues, and areas of VA interest.
(3) The FAA may ask the applicant to clarify things during a project. Feedback from FAA to CA and applicant is necessary to confirm if the clarification and explanations are adequate.
b. Communications between Authorities.
(1) Since the CA must understand the FAA position on all the items for which the CA will make determinations of compliance, each authority must include the other in communications throughout the validation program.
(2) We expect there will be an early exchange of information between the CA and the FAA. This exchange will include: proposed use of exceptions (§ 21.101(b)) to the latest CA airworthiness standards, special conditions, exemptions, equivalent safety findings, and MOCs. This exchange will ease the process and help the applicant reach timely validation. Even before the formal application, we at the FAA should respond to applicant requests to discuss issues. The applicant should make those requests through the CA.
(3) Each authority will normally seek the other’s opinions before resolving significant issues. They may even postpone meeting with the applicant until the other authority is adequately represented. The FAA must be notified by the CA of all validation meetings, and invited to participate.
(4) Similarly, authorities will coordinate and circulate all correspondence. The CA must be sent copies of all correspondence between the FAA and applicant. Likewise the FAA should get copies of all validation correspondence between the CA and applicant.
(5) The CA should notify the FAA as soon as possible of all novel or unusual design features, and other design features that may require an exemption, a special condition, an equivalent level of safety finding, or the development of a technical issue paper.
206. SUPPLEMENTAL TYPE CERTIFICATES (STC). FAA certification personnel must review the applicable BASA IPA to determine which, if any, STC provisions are included in the agreement.
NOTE: BAAs, as opposed to BASA IPAs, do not permit U.S. acceptance of STCs from the other country.
a. We should apply a certification procedure similar to paragraphs 203 and 204 and adjust it for the size and complexity of the design change.
b. The key elements to this approach, as outlined in paragraph 204a, apply to STC validation programs. Specifically, when serving as VA for an STC, we will:
(1) Maximize delegation of compliance determinations to the CA;
(2) Instruct the CA in acceptable MOCs for assigned items; and
(3) Accept CA compliance determinations as if we made them ourselves.
c. Although we may decide to retain a compliance determination, we must justify it.
207. –219. RESERVED
4/29/05 8110.52
SECTION 2. POST-TYPE VALIDATION
220. POST-TYPE VALIDATION ACTIVITIES. When the validation program is concluded, the VA and CA should set up regular feedback and continued communication (including specific focal points) on service difficulties, trends, and general experiences with the product. Post-type validation activities (CA/VA) are defined as:
SECTION 2. POST-TYPE VALIDATION
a. Approving changes to the approved type design by the TC holder (including revisions of manuals) not requiring a new or amended TC,
b. Approving airworthiness data, including in-service information, and
c. Continued airworthiness activities including the issuance of Airworthiness Directives.
221. VA RESPONSIBILITIES DURING POST-TYPE VALIDATION.
a. The approach to validation in paragraphs 203 and 204 also applies to approving changes to type design. The FAA, as VA, must ensure that the type design, as amended by posttype certification design changes, continues to comply with its FAA certification basis and is documented to an acceptable standard. As VA, we must also ensure the continued airworthiness of the product, since we are responsible for the safety of all products on our registry.
b. The FAA, as VA, has the right to inquire into any post-type validation activities to ensure acceptable continued airworthiness of aircraft registered in the United States, and any products fitted to such aircraft.
c. The FAA, as VA, has the right to seek information so we can understand and agree on:
(1) Findings of compliance made by the CA to all FAA airworthiness standards,
(2) Any mandatory corrective action, and/or
(3) Any significant ongoing continued airworthiness issue and how it is resolved.
d. We in the FAA, as VA, should become involved with the CA to resolve continued operational safety issues directly related to an accident or incident in the U.S. Again, we should assign maximum responsibility for resolving those issues to the CA.
222. CA RESPONSIBILITIES DURING POST-TYPE VALIDATION.
a. When the FAA is CA, we will monitor the continued airworthiness of the type certificated product worldwide and issue Airworthiness Directives (AD) when necessary. The FAA will inform the VA immediately of all such mandatory actions, including those resulting from reports under 14 CFR § 21.3 on aircraft under VA jurisdiction and products fitted on such aircraft.
b. When the FAA is CA, the certificate holder and we will help the VA investigate significant airworthiness issues about aircraft under VA jurisdiction and products fitted on such aircraft. This support includes giving the VA:
(1) Status of any FAA airworthiness investigations
(2) Status of FAA plans for AD actions within ex parte requirements.
(3) Timely access to related design data and other certification documents as they request.
NOTE: Bilateral agreements commit the FAA to provide timely information to a bilateral partner authority. Similarly, protection of proprietary data protection is an obligation under our BASA IPAs. We cannot withhold access to data based on the issue of its being proprietary.
223. –299. RESERVED
223. –299. RESERVED
CHAPTER 3. FAA/EASA/JAA TYPE VALIDATION PROCEDURES
SECTION 1. INTRODUCTION
300. GENERAL. The FAA and aviation authorities in Europe have been bilateral partners for more than 70 years, facilitating the import and export of hundreds of products. Our shared vision of validation with Europe is that it should be a simple process based on mutual authority and trust, which leads to design acceptance in compliance with the VA airworthiness standards. This process requires effective continual communication between all parties. The FAA/EASA/JAA type validation principles are based on this shared vision.
SECTION 1. INTRODUCTION
a. Chapter 3 defines how to implement the type validation principles with Europe. This chapter is divided into four additional sections.
(1) Section 2 details key TVP concepts, and defines the four phases of a typical validation project.
(2) Section 3 defines responsibilities of the Directorate standards staff in maintaining documentation on FAA and EASA airworthiness standards.
(3) Section 4 defines the procedures used to apply TVP when we (the FAA) are the validating authority (VA).
(4) Section 5 defines the procedures used to apply TVP when we are the certificating authority (CA).
301. APPLICABILITY. This chapter applies to all validation programs with EU member states or non-EU JAA member states, for products covered by a bilateral agreement, and that lead to a type certificate (TC), or supplemental type certificate (STC).
302. SEQUENTIAL VS. CONCURRENT CERTIFICATION/VALIDATION. The FAA/EASA/JAA Type validation principles permit either sequential or concurrent validation.
a. Sequential Validations. Here, the CA has completed its certification, or is well advanced in certification, before the applicant requests VA validation. The CA has established and approved the certification basis and acceptable MOC. Certification flight tests may have been completed. In fact, the CA may already have issued a type certificate to the applicant, and the product may be in service. They may not have considered VA airworthiness standards and MOC.
b. Concurrent Validations. The applicant requests early validation of the product, well before the CA has completed all their certification findings, and while any certification issues may be efficiently addressed in the design development and compliance demonstration. Both authorities’ airworthiness standards and acceptable MOC are addressed simultaneously. The CA and VA will meet early with the applicant to identify their respective applicable airworthiness standards. A common VA/CA type design should be their objective. They will strive to achieve a common certification basis, including special conditions, certification plans, and acceptable
MOC. This promotes approval/closure according to the project schedule. Although CA and VA are working in parallel, everyone must ensure that the CA remains in the leading role.
c. Best Practices. We at the FAA and EASA encourage concurrent certification/validation because it can result in a more efficient program for both the applicant and the authorities. Concurrent certification/validation projects promote CA and VA development of common exceptions to the latest airworthiness standards, special conditions, exemptions, equivalent safety findings and acceptable MOC. Applicants can satisfy both authorities’ airworthiness standards during the product design phase. (Extensive design changes are frequently required when the applicant pursues CA certification without considering VA airworthiness standards.) Lastly, concurrent certification/validation projects will quickly expose areas where jointly-agreed solutions are not readily available.
d. Emphasis of this Order. We assume, throughout this order, that validation activities will be carried out concurrently. We’ll highlight the differences between concurrent and sequential validations when they exist.
SECTION 2. TYPE VALIDATION: KEY CONCEPTS
SECTION 2. TYPE VALIDATION: KEY CONCEPTS
303. NEW TERMINOLOGY. The type validation principles approved by the FAA, EASA and JAA in October 2004 formally defined four terms: validation item (VI), standards differences (significant standards differences (SSD), non-significant standards differences (non- SSD), and standards equivalencies. These are not new terms. They have appeared in previous certification/validation procedures under different names. More importantly, however, the principles established rules that EASA and we are expected to follow when using these terms in a certification/validation project. We will examine each term in the following paragraphs.
304. VALIDATION AUTHORITY CERTIFICATION BASIS. The VA certification basis is the sum of applicable airworthiness standards identified by the VA, plus exemptions, special conditions, and equivalent level of safety findings declared by the VA. It establishes VA design acceptance of an imported product or certification of the design change.
a. Compliance with the VA certification basis for the product is based on compliance with the CA certification basis plus:
(1) The standards differences for the particular amendment pair of standards, and any exemptions, special conditions, and equivalent level of safety findings issued by the VA; or
(2) Any exemptions, special conditions, and additional airworthiness standards issued by the VA that provide an equivalent level of safety.
NOTE: These standards differences are all applicable significant standards differences (SSD, see paragraph 309a(1)) and nonsignificant standards differences (non-SSD, see paragraph 309a(2)) identified by the VA.
b. For the FAA, these two methods of demonstrating compliance with the VA certification basis are based on the requirements defined in 14 CFR § 21.29 (a) (1) (ii) (See paragraph 203c(2)). The first method corresponds to the first provision in (ii). This method demonstrates compliance with the applicable airworthiness requirements in 14 CFR § 21.17. Compliance with CA standards insures compliance with FAA requirements when CA standards are equal or more stringent than FAA requirements. Demonstrating compliance to the standards differences accounts for the remaining requirements. The second method corresponds to the second provision in (ii). Here, we prescribe additional airworthiness requirements to provide a level of safety equivalent to the level defined by requirements in 14 CFR § 21.17.
c. Establishing the VA Certification Basis. The VA certification basis must be defined early in a validation program if the program is to be conducted efficiently. Once established, the VA certification basis does not change except when:
(1) Unsafe conditions arise,
(2) Design changes affect the certification basis,
(3) The VA learns of design features that require special conditions or exemptions, or
(4) The applicant elects to comply with later amendments.
d. Operational requirements, such as 14 CFR parts 91, 121, 125, 135, or JAR OPS, may prescribe equipment requirements that affect the aircraft, engine, or propeller design. The VA should identify these requirements early in the program so they may be included, if the applicant asks, in the validation program. Coordination is required with the appropriate FAA flight standards aircraft evaluation group (AEG) or JAA operational group (or EASA equivalent, when established).
305. VALIDATION ITEM (VI). We define a validation item, generally, as a certification item or airworthiness standard of particular interest to the VA. VIs identify aspects of the design or proposed MOC that warrant further technical involvement (beyond familiarization) by the VA. VIs are primarily used to define and explain VA airworthiness standards and interpretations distinct from CA airworthiness standards. VIs are normally identified during familiarization.
a. Validation items consist of: applicable generic VIs, project VIs, and applicable SSDs. These terms are described in greater detail in paragraphs 306, 307, and 309a(1) respectively.
b. VA Involvement. The basic principle behind the VI is that the VA won’t review CA compliance determinations, or be involved in a deep review of the MOC, except in areas that fall within the scope of the identified VI. A VI must be raised for any item in which the VA intends to be involved in compliance determination. In most cases, we expect the VA to rely on the CA to determine compliance for VIs. Paragraphs 352 and 380 define appropriate VA involvement.
306. GENERIC VALIDATION ITEMS. Generic VIs are certification items the VA identifies for particular scrutiny in all products of a certain class, such as all transport aircraft, or all reciprocating engines.
a. Generic VI Lists. Each directorate should know the VIs raised on previous validation projects of a certain type that could apply to future projects. It’s important to make the applicant and CA aware of these common issues early in a validation project. The way to disseminate this information is to develop and publish a generic VI list.
b. Use the following criteria to identify generic VIs:
(1) New VA standards where the VA has no past experience with their application to a product. The standards have an important impact on the whole product or a critical feature and engineering judgment is required to establish compliance,
(2) New VA standards where the CA has no past experience with their application to a product. The standards have an important impact on the whole product or a critical feature and engineering judgment is required to establish compliance,
(3) Airworthiness standards where VA and CA interpretive, advisory, MOC, or guidance materials are different or insufficient,
(4) Commonly occurring project VIs (see note at the end of paragraph 307)
(5) Standards identified for special emphasis by the VA in a data-driven risk assessment analysis for the product class. If VA and CA both identified a standard for special emphasis, it generally should not be a VI.
307. PROJECT VALIDATION ITEMS. The validation project may also have unique elements due to a product’s design, use, or the methods for establishing compliance. The VA may identify these elements for special review and consideration. Unlike the generic VIs that could apply to all products of a certain class, project VIs are established only to address unique project elements.
a. Project VI Selection Criteria. Project VIs are limited to the following seven specific sources. Project VIs identified using criteria (1), (2), (3), and (4) may result in special conditions.
(1) New Technology. Technology that is new to the FAA or EASA as a whole, not just new to VA team members. For instance, if technology used by the applicant were new to the VA team but not the VA itself, we don’t consider it a project VI. VA management is responsible for making sure the VA team members are properly informed of earlier use of the technology, VA standards and MOC. (See paragraph 347, for further details on VA management responsibilities when we are the VA.)
(2) Novel Applications of Existing Technology. Existing technology being applied for the first time to a particular product line is not automatically novel. Additionally, “novel” applies to the FAA and EASA as a whole, not just VA team members.
(3) Unconventional Product Use. This criterion applies when a product is used for a purpose for which it wasn’t designed.
(4) Unsafe Conditions. The product has design features where experience with other products in service has shown an unsafe condition might occur in that product, even though compliance with the standards in the VA certification basis can be demonstrated. The unsafe condition is measured with respect to the overall level of safety intended by the product VA certification basis.
NOTE: Use the principle of “unsafe condition” only to upgrade the level of safety of the product if the VA has mandated, or will immediately mandate, that upgraded level of safety to other products with similar design features.
(5) New Standard Interpretations or MOC for Existing Standards. Different interpretations/MOC applied by the CA from those already agreed to between CA and VA. We don’t consider a MOC or standards interpretation “novel” or “new” if both the FAA and EASA applied them previously in a similar context.
(6) Exemptions. Subjects identified by VA or CA as potentially requiring an exemption from VA standards.
(7) Equivalent Safety Findings. Subjects identified by applicant, CA, or VA as potentially requiring an equivalent level of safety finding to VA standards.
NOTE: Project VI may be added to the list of generic VIs if the associated issue is expected to have a broader applicability to future programs. The VA will determine this and update the generic VI list accordingly.
308. STANDARDS EQUIVALENCIES. A 14 CFR standard and its counterpart CS/JAR may be equivalent, despite differences in texts. Both standards must meet the following conditions to be equivalent:
a. They must have the same regulatory objective, and
b. They must contain equivalent technical standards, so compliance with one standard meets compliance with the other.
309. STANDARDS DIFFERENCES. When we compare airworthiness standards developed by the FAA and the EASA/JAA, we see that each organization often adopted different airworthiness standards. In some cases, the 14 CFR airworthiness standards are more stringent than CS/JAR airworthiness standards. For example, the FAA requires an 8 lb. bird to comply with 14 CFR § 25.631, Amendment 25-23. EASA requires only a 4 lb. bird to comply with CS-25.631. In other cases the EASA airworthiness standard is more stringent. CS-E 530, Fire Precautions, requires engine mounts to be fireproof; that electronic engine controls to be at least fire resistant, and that the engine be electrically bonded to preclude ignition sources. 14 CFR § 33.17 does not require any of these. We must consider these standards differences when establishing the VA certification basis.
a. When the 14 CFR and CS/JAR airworthiness standards are not equivalent, standards differences are then divided into two classes: significant standards differences (SSD) and nonsignificant standards differences (non-SSD).
(1) Significant Standards Differences (SSD) may require type design changes, approved manual changes, or imposing operational limitations to meet VA airworthiness standards. The type design or operation approved by the VA could then differ from the type design and operation approved by the CA.
(2) Non-Significant Standards Differences (Non-SSD) do not result in a difference classified by the VA as significant. Differences will not result in type design changes, approved manual changes, or imposing operational limitations to meet VA airworthiness standards.
b. SSD and non-SSD are used to identify standards differences. For harmonized airworthiness standards, differences in interpretive guidance material that meet the criteria in paragraph 306a(3) will be addressed as generic VI.
c. The only functional difference between an SSD and a Non-SSD in the validation process is the level of VA involvement in the compliance determinations. The VA may choose to retain the compliance determinations of SSD, or ask the CA to make those determinations for them. The CA will, however, make compliance determinations for all non-SSD not otherwise identified as VIs, per paragraphs 306 and 307.
d. Standards Differences and the VA Certification Basis. All SSD and non-SSD are part of the VA certification basis. SSD and non-SSD are treated in the same manner in this regard.
(1) VA SSD and Non-SSD, plus VA exemptions, equivalent level of safety findings and special conditions are combined with the CA certification basis to form the VA certification basis. To better understand this concept, see the VA certification basis defined in paragraph 304.
(2) SSD and Non-SSD are based on a specific amendment-pair of airworthiness standards. All projects with a common amendment-pair of airworthiness standards will have the same SSD and non-SSD lists.
(3) Although an SSD or non-SSD may not apply to a particular product, it is still included in the VA certification basis. For example, an SSD on ditching airworthiness standards doesn’t apply when validating an aircraft not approved for ditching. The SSD would still be included in the VA certification basis, however, and used if the aircraft were certified for ditching in future.
e. Compliance with VA Airworthiness Standards. Compliance with VA airworthiness standards is to be established for all identified applicable standards differences, both SSD and Non-SSD. The VA is responsible for defining the standards differences for each validation project, since these SSD and non-SSD define unique VA airworthiness standards.
310. METHODS OF COMPLIANCE (MOC).
a. General. The VA accepts CA methods of compliance when they accept the CA certification basis as part of the VA certification basis, except for specific methods of compliance documented in VIs.
b. Reviewing Methods of Compliance. It’s important that the VA understands the MOC used or to be used. The CA and the applicant will brief the VA on the MOC as part of a project’s technical familiarization phase (see paragraph 315). CA and applicant will provide general information sufficiently detailed to allow the VA team to understand the general principle of the MOC. When the VA determines the need to evaluate a MOC with the CA and applicant, the VA confines their evaluation to the general, overall methodology proposed by the applicant. This evaluation can include the assumptions, boundary conditions, and critical parameters of that methodology essential to the technical adequacy of the MOC. Test plans, test parameters, and other MOC steps should be left to the CA to further define and approve. The VA has to justify, and limit, their review of test plans, test parameters, and other MOC steps to the issues covered by the VI.
c. Establishing Methods of Compliance. When there is new technology, novel application of existing technology or MOC, novel MOC, or unconventional product use, the VA will work closely with the CA and applicant during the technical familiarization phase of the program to establish acceptable MOC. The object is to establish common FAA and EASA MOC. When that’s not possible, the VA is responsible for identifying unique MOC in a VI.
d. Accepted Methods of Compliance. Once the VA accepts a MOC for a given standard on any program with the CA, the VA accepts that MOC in the future as long as the original assumptions apply. An exception occurs if the VA determined the MOC insufficient. VA and CA must discuss this.
311. COMPLIANCE DETERMINATIONS. As in any certification program, the applicant shows compliance with airworthiness standards and the authority accepts this demonstration when they’re satisfied that the standards are met. The decision to accept the demonstration is a compliance determination in the type validation principles.
a. The authority determines that the applicant has shown compliance with the standards. Both CA and VA may make compliance determinations in a validation program. The CA will make compliance determinations for all items in the CA certification basis, and does the same to all non-SSDs, and assigned VIs.
b. We should avoid the practice of authorities making joint determinations of compliance for any one specific standard unless there is a justifiable benefit.
c. The VA decides which authority makes the compliance determinations for each VI. The VA may either retain the compliance determination associated with a VI or assign the compliance determination to the CA. The VA should inform the CA of progress and results of retained compliance determinations. Sharing this information promotes smooth future assignment of similar compliance determinations.
d. VA compliance determinations are limited to retained VIs. The VA will not reinvestigate any assigned compliance determinations.
312. ISSUE PAPERS, CERTIFICATION REVIEW ITEM (CRI) AND ACTION ITEM (AI). We at the FAA prepare issue papers identifying the certification basis and validation items. EASA/JAA use two documentation systems to define certification bases and validation items, and to follow their resolution. They are the certification review item system, and the action item system. If we as FAA staff are involved in EASA validation activities, we must understand these systems.
a. Issue Papers. FAA Order 8110.4 shows us how to develop issue papers. It establishes the following issue paper designation system: G-1, type certification basis; G-2, determination of compliance; G-3, environmental consideration; G-4, import requirements. The FAA validation team writes an issue paper for each VI.
b. Certification Review Item (CRI). EASA/JAA use CRIs for the same reason we use issue papers. They document a certification or validation subject that requires an interpretation to be clarified, or that represents a major technical or administrative problem. EASA/JAA use CRIs for significant or controversial regulatory, technical policy, and means of compliance issues. Routine items in showing compliance and work relationships will not normally be raised as a CRI unless special circumstances exist.
c. Action Item (AI). EASA/JAA use the action item system to advance non-sensitive issues. AIs document non-controversial items that require special attention. AIs do not require a CRI.
(1) AIs are most often used to record actions during certification and validation programs and to trace their progress. The AI will define the characteristic to check, the relevant standards, the interpretations used, the action, and responsibilities. The AI system is the basic means to record necessary EASA, FAA, and applicant actions and the basis for their resolution. AIs may also be used as an internal EASA discussion paper.
(2) The EASA project certification manager (PCM) sets up an action item system with the applicant. The object is to make all actions in the EASA process traceable, and ensure continuous and adequate processing of all action items.
NOTE: “Action item” is the official EASA term for these documents. The terms certification action items (CAI) or validation action items (VAI) have, however, been used to describe these documents. They are interchangeable.
313. TYPE VALIDATION: FOUR PHASES. Type validation principles divide a typical type validation program into four phases: general familiarization, technical familiarization, determining VA involvement, and compliance determinations. Their objectives and milestones are summarized in the following paragraphs. You will find detailed descriptions of FAA activities in each of these phases in sections 4 and 5 of this chapter.
a. Before receiving an application, the VA should be able to discuss policy and regulatory issues with the CA to promote timely validation later on.
b. CA and VA Staff Involvement.
(1) It’s essential that CA certification/policy/regulatory staff support the VA in the four phases of a validation program, in particular by attending validation meetings. This is especially important when those meetings cover new exemptions, special conditions and equivalent safety findings.
(2) The VA team will seek advice from VA policy/regulatory staff when considering new exemptions, special conditions, and equivalent level of safety findings applicable to the VA certification basis.
314. PHASE I: GENERAL FAMILIARIZATION.
a. Objective. The applicant and CA present an overview of the project to the VA. The two objectives to this phase are to:
(1) Establish general timelines for the validation process,
(2) Familiarize the VA with the design and help them set up their validation team, and
b. Initiation. Phase I begins when the VA receives CA type certification application.
c. Completion. Phase I ends when:
(1) The VA has set up their validation team,
(2) VA, CA, and applicant have established the initial validation schedule to complete the validation process. The applicant is responsible for proposing a realistic timetable, gaining CA and VA concurrence. The applicant is also responsible for staying as close as possible to the agreed schedule.
d. During the general familiarization meeting, the VA should give a copy of the generic VI list and the standards differences list to both CA and applicant. Early availability of these lists sets the stage for phase II.
e. After phase I, the technical disciplines on a validation team may advance through the phases at different speeds. There is no need for one technical discipline to delay their validation efforts because of the slower progress of another unrelated technical discipline.
315. PHASE II: TECHNICAL FAMILIARIZATION.
a. Objective. The applicant and CA present the project’s technical definition and associated compliance methods to the VA. This phase has several objectives:
(1) Familiarizing the VA technical team with the project’s design and compliance methodology,
(2) Establishing an initial VA certification basis,
(3) Identifying initial VIs, and
(4) Setting up strong communications between VA, CA, and applicant’s technical specialists.
b. The CA and applicant should give general information to the VA so the VA may understand the design and compliance methods. The VA should ask clarifying questions to understand the material. If participants need in-depth discussion or debate of the materials, it’s done during phase III.
c. Initiation. Phase II starts with the scheduling of a technical familiarization meeting (or meetings), unless the product is a derivative and the VA determines that changes from previously validated designs don’t warrant the briefing.
d. Completion. Phase II ends when the VA establishes the initial VA certification basis and identifies initial VIs.
(1) Once the initial VA certification basis has been established, it will not change except when unsafe conditions arise, design changes affect the certification basis, or when the applicant elects to comply with later amendments. The provisions in 14 CFR § 21.17 and EASA Annex Part 21, Paragraph 21A.17 still apply. A new certification basis is established if the project is not completed in the allowable time.
(2) The initial VIs are defined based on the applicant’s design description. Added VIs may be identified during phases III and IV if there’s a change to design, intended use of the product, assumptions used for certification, or compliance methods.
316. PHASE III: DETERMINING VA INVOLVEMENT.
a. Objective. The VA specifically identifies which compliance determinations are assigned to the CA, and which the VA retains.
b. Initiation. Phase III begins after establishing the VA certification basis and initial VIs.
c. Completion. Phase III ends when:
(1) The VA has established final VIs for the project,
(2) VA issues a closure document identifying which authority makes compliance determinations with the airworthiness standards for the VIs,
(3) The VA issues an issue paper/CRI (or an addition to the closure document) that identifies and justifies any information they requested to gain product familiarity (see paragraph 319), and
(4) The completion schedule for the validation program (phase IV) is confirmed.
NOTE: Design/MOC changes may occur during phase IV, yielding new VIs. This would not require a return to phase III.
317. PHASE IV: COMPLIANCE DETERMINATIONS.
a. Objective. The VA and CA make compliance determinations for their assigned VIs.
NOTE: When an activity is carried out by the CA for the VA, that activity may be carried out by the CA or under their legally constituted delegation system.
b. Initiation. Phase IV begins when the VA issues the document or documents establishing compliance determination responsibilities for the VIs.
c. During phase IV of aircraft validation programs, the VA may also conduct abbreviated flight evaluations for a final assessment of airworthiness, maintainability and operational suitability of the aircraft, and to support introducing the aircraft into VA jurisdiction.
d. Approved manuals must be submitted for VA review and acceptance.
e. Completion. Phase IV ends when the VA issues the type certificate or equivalent design approval.
318. PROGRAM SCHEDULES AND ACCOUNTABILITY. Experience shows that significant program delays have occurred because participants failed to establish a program schedule and commit resources to support the schedule. All three parties – VA, CA, and applicant – share this responsibility.
a. Initial Program Schedule. The initial program schedule is established during phase I – general familiarization. The applicant is responsible for proposing a realistic program schedule and seeking CA and VA concurrence. Establishing the initial validation schedule is a phase I completion milestone.
b. Completion of the Project. VA, CA, and applicant will reexamine the program schedule during phase III and update it if necessary. Confirming the program schedule for project completion (phase IV) is a phase III completion milestone.
c. Accountability. The FAA project manager and EASA PCM are responsible for monitoring progress and securing the necessary resources to support any agreed-upon timelines. They inform their respective management if or when meeting the agreed milestones is in jeopardy. The FAA, EASA, and applicant’s management are responsible for resolving conflicts (see paragraph 323) and making resources available to meet the schedule.
319. PRODUCT FAMILIARITY AND CONTINUED AIRWORTHINESS RESPONSIBILITIES.
a. The type validation principles are a project management tool VAs use to manage their resources during a certification/validation program. Under TVP, the VA will make compliance determinations for the retained VIs. The CA makes all other compliance determinations.
b. Relying on the CA does not mean the VA abdicates their responsibilities. Under ICAO, the VA is responsible for the safety of any aircraft under their jurisdiction. Though their active involvement in certification/validation is limited to VIs, the VA must develop an understanding of the design over its full breadth, and at sufficient depth to discharge their continued airworthiness responsibilities. They must develop this understanding by exchanging technical information in a manner that doesn’t delay the program or undermine the CA. The VA must maintain a balanced approach.
c. Recognizing the VA’s continued airworthiness responsibilities, the TVP provide mechanisms to gather this information throughout all phases of the validation program. For example, detailed discussions will occur during technical familiarization (phase II) when the product has unique or novel design features, or unconventional use. Additionally, the CA, VA and applicant should have frequent, regularly-scheduled telephone conferences covering program status, open validation issues, and areas of VA interest. Aircraft design and certification can be an iterative process. Recognizing that some issues may not be totally defined until phase IV, (compliance determination), the TVP provide for continued communication between VA and CA for purposes of awareness. For example, design changes may occur as late as phase IV and must be communicated to the VA.
d. The VA is responsible for using the mechanisms provided by TVP to gather the information required to discharge their continued airworthiness responsibilities. The VA has the opportunity for input during phases I, II, and III. In addition, the VA may ask for information such as test plans or other compliance documents, for determinations made by the CA. The VA may ask for this information for product awareness only—not to check on the CA, or for approval, acceptance or comment.
e. The VA must manage and control requests for information, a responsibility shared by both team and management. Based on the information gathered during phase II, (technical familiarization), and phase III, (determining VA involvement), the validation team may identify certification/compliance activities that they’d like to follow during phase IV, (compliance determination). The team should be cautious when requesting information on these activities. They must justify the request, making the case that access to the information increases their ability to discharge airworthiness responsibilities. When we at the FAA are the VA, the project manager must carefully review these requests and accompanying justifications to ensure they are consistent with the intent of TVP. The FAA standards staff management makes the final decision on these requests. Paragraphs 319g and h below cover expectations governing request for additional information.
f. If, as a result of activities associated with paragraphs 319, the VA wants to challenge a CA compliance determination, they raise the issue immediately to VA senior management for
resolution. The VA should rarely challenge the CA determinations. When we are the VA, the project manager raises the situation to the accountable directorate manager who will resolve it with the CA. This differs from the issue resolution process described in paragraph 323.
g. Request for information about VIs assigned to the CA. During phase III, the VA determines which VIs to assign the CA and which to retain. While the VA should maximize reliance on the CA, the TVP recognize the importance of staying aware of certification/compliance activities during phase IV, even in CA assigned areas. The VA maintains awareness by either retaining the VI (as defined in paragraphs 352 or 380) or by communicating for purposes of awareness. When the VI is assigned to the CA, you should remember that:
(1) VA active involvement with a VI ends once it’s assigned to the CA. However, the VA may ask for more information when they require it to carry our their continued airworthiness responsibilities. Those requests for more information must be identified and justified in the VI issue paper, VI CRI or the phase III closure document.
(2) Requests for information must not be made for every VI assigned to the CA. The VA should exercise engineering judgment when deciding to ask for information. Consider the following examples:
(a) When there is a novel application of existing technology, a VI is established to ensure that the subject is fully discussed during phase II technical familiarization. If the technology is well established and understood when the issue paper is closed at the end of phase III, the VA should assign the compliance determination to the CA and not request access to test plans or other compliance documents.
(b) When there is new technology, or the application is novel, a VI is established to make sure the subject is discussed during phase II technical familiarization. Even though the VA team is confident in the CA’s ability to make a compliance determination, the VA may feel that their own understanding of the design or possible failure modes is incomplete. In this case, the VA team should ask for information to complete their understanding of the technology or its application. This information may be in the form of compliance documents supplied by the CA.
h. Request for Information about Certification Areas Outside of VIs. To understand the design over its full breadth and at sufficient depth to discharge continued airworthiness responsibilities, you may also request information, such as test plans or other compliance documents, about areas outside of VIs. The VA must understand the product’s critical design elements, not just those associated with VIs. The VA must identify and justify this request in an issue paper.
NOTE: These items are not VIs, so it’s not likely that there will be issue papers on them. You must generate a new issue paper if you want access to the information.
320. APPROVED MANUALS. Approved manuals in the SSD definition include those required by 14 CFR, CS/JAR plus any extra manuals submitted by the applicant and approved by the authorities as a part of the type certification.
a. Required Manuals. FAA regulations require applicants to supply manuals and continued airworthiness instructions with each product.
(1) The required manuals for type certification are: airplane, balloon, and rotorcraft flight manuals; the instruction manual for installing and operating the engine, and the instruction manual for installing and operating the propeller. The manual sections requiring approval are in 14 CFR §§ 23.1581, 25.1581, 27.1581, or 29.1581 for aircraft, §31.81 for balloons, in §33.5 for engines, and in §35.3 for propellers.
(2) Instructions for continued airworthiness are required for each balloon, engine, propeller, airplane, and rotorcraft. Approval is required only for the airworthiness limitations section of the instructions for continued airworthiness. The sections that require approval are defined in 14 CFR §§ 23.1529, 25.1529, 27.1529, or 29.1529 for aircraft, §31.82 for balloons, §33.4 for engines, and in §35.4 for propellers.
NOTE: Although only those manual sections listed above require approval, the entire package of data, in manual or data form, must be determined acceptable to the Administrator. This may require the appropriate flight standards’ AEG review and acceptance.
b. Other Submitted Manuals. Structural repair manuals, engine overhaul manuals, or component maintenance manuals may be submitted as a part of a type certification. Although we don’t require them, we will approve these manuals during type certification. Standards differences that require changes to these manuals are also defined as SSD.
NOTE: Some non-EU NAAs require more manuals as additional national airworthiness standards. They will be identified in a CRI.
321. SUPPLEMENTAL TYPE CERTIFICATES. TVP recognizes that modifications vary in scope and complexity. The validation process has to adjust appropriately. We do this by classifying all STCs as either basic or non-basic. When they receive an STC application, the CA will classify the STC as either basic STC or non-basic, in accordance with CA procedures. The VA will concur with CA classification by accepting the application. When they disagree with the classification, VA and CA should follow the issue resolution process in paragraph 323.
NOTE: The FAA does not validate STCs associated with all products from EASA/JAA countries. Consult the appropriate bilateral agreement before accepting an STC validation program.
a. Supplemental Type Certificate Classification Criteria:
(1) Non-basic STCs will generally be more complex and may require some VA involvement (see paragraphs 359 and 390). Criteria for non-basic STCs are:
(a) Changes classified as significant, under14 CFR/JAR § 21.101(b) and EASA’s Annex Part 21, Paragraph 21A.101(b).
(b) Changes meeting any of the criteria in paragraphs 306 and 307, defining SSDs, project and generic VIs; and
(c) Any other design changes categorized as a non-basic STC by the CA.
(2) We consider all other STCs as basic STCs. Here, the CA issues a statement of compliance to the VA certification basis. The VA accepts the statement, reviews the application for completeness, and issues an STC (see paragraphs 359 and 390).
b. For all STCs, significant revisions to approved manuals must be submitted to the VA for review and acceptance. For an individual certification project, the CA will consult with the VA when deciding which revisions are significant and not.
322. COMMUNICATIONS. Program reviews show that effective communications between the VA, CA, and applicant are key to a successful validation program. Program delays are often the result of poor communication. The VA must stay in the communications loop between CA and applicant during all phases of the program for the VA to adequately understand CA and applicant actions. This is particularly true where the CA is determining compliance for the VA. Use the general procedures given in paragraph 205. Based on past experience, we recommend the following specific procedures:
a. Teleconferences. CA, VA and applicant project managers are required to conduct frequent, regularly scheduled telephone conferences to review program status and discuss open validation issues. We recommend monthly teleconferences.
b. Formal Confirmation Procedure. The VA will often request clarifying information from the applicant during a project. Feedback from VA to CA and applicant is necessary to confirm how clear and adequate the explanations were. The FAA, EASA, and industry have agreed to implement such a confirmation process. Key points are as follows:
(1) The applicant will respond to VA questions within 14 days. If the data is not available, the applicant will give the date when data will be available.
(2) Validation team members will acknowledge the applicant’s response within 30 days, saying whether they got enough information to answer the question and complete that phase of the project.
(3) If the team member has not replied to the applicant in 30 days, the FAA project manager or EASA PCM will contact the team member’s direct management and resolve the problem.
323. ISSUE RESOLUTION PROCESS. FAA and EASA management will closely follow the validation programs. The CA, applicant and VA project managers have a collective responsibility to ensure they make every effort to resolve certification impasses between VA and CA teams at the lowest possible level. However, teams should elevate impasses gradually to higher VA and CA management until they get resolution, or the appeal process has run its course. We should not delay the applicant’s certification program while authorities are resolving issues.
NOTE: The exception to this is compliance issues discovered when fulfilling product familiarity responsibilities under paragraph 319 (see paragraph 319(i)).
a. The FAA and EASA issue resolution process assigns three levels of responsibilities to break an impasse. The three levels are:
(1) FAA project manager, EASA PCM, and applicant program manager,
(2) FAA accountable directorate manager, EASA product head, applicant manager, and
(3) FAA Aircraft Certification Service Director, EASA Certification Director, and applicant senior management.
b. The FAA project manager, EASA PCM, and applicant program manager are primarily responsible for resolving validation issues.
c. If managers and applicant can’t establish a plan within two weeks to solve the problem, they refer the issue to the next level up.
d. If management at this second level can’t make a plan to solve the problem within the next two weeks, they refer the issue to the third level.
324. PROGRAM REVIEWS. CA and VA may, for selected projects, review the proper implementation of TVP principles to identify areas for improvement in the type validation principle process. Appendix 5 lists criteria that they can use in these reviews.
325. –329. RESERVED
325. –329. RESERVED
SECTION 3. RESPONSIBILITIES OF DIRECTORATE STANDARDS STAFF
330. GENERAL. The directorate standards staffs play a key role in ensuring that ACOs have the latest information needed to support a successful validation program. For each product class in their responsibility (14 CFR part 23, 29, and so forth), the directorate’s standards staff is responsible for:
SECTION 3. RESPONSIBILITIES OF DIRECTORATE STANDARDS STAFF
a. Developing the Generic VI Lists. The lists should:
(1) Cite the applicable 14 CFR airworthiness standard or standards,
(2) Summarize the technical issue,
(3) Refer to any information issue papers.
b. Publishing and Updating the Generic VI Lists. Publish the lists’ contents in a commonly known location. Standards staffs may post the generic VI lists on their websites.
c. Forwarding the Generic VI Lists to EASA. Notify EASA and JAA of changes to the generic VI lists as they occur.
331. COMPARISONS OF 14 CFR AND CS/JAR TEXT. Literal comparison of the airworthiness standards developed by the FAA and EASA/JAA shows there are places where airworthiness standards texts differ extensively. Here, the directorates’ standards staff must evaluate the text to determine if the two standards are equivalent or different.
a. Standards Equivalencies. In some cases, 14 CFR and counterpart CS/JAR airworthiness standards may be determined equivalent despite text differences. For instance, 14 CFR part 33 and CS-E/JAR E have been determined to be largely equivalent. Paragraph 332 lists the procedures directorate standards staffs should use to determine the equivalence of 14 CFR and the CS/JAR airworthiness standards. The responsible directorate’s standards staff must approve standard equivalencies.
b. Standards Differences. More often, different texts between the standards result in standards differences. Paragraph 333 lists the procedures standards staffs should use when airworthiness standards are not equivalent.
332. IDENTIFYING STANDARDS EQUIVALENCIES.
a. To determine the equivalency of a particular 14 CFR and CS/JAR standards, the standards staffs must do the following:
(1) Identify those airworthiness standards, or group of airworthiness standards with a common objective. The objective must be clearly understood. It can be quantitative (such as 9.0 g), or qualitative (such as “without exceptional pilot skill”).
(2) Define the minimum airworthiness standards of both 14 CFR and the CS/JAR.
(3) Review the regulatory/standards interpretive material. For EASA, acceptable means of compliance (AMC) and guidance material (GM) contain airworthiness standards interpretive material. At the FAA, we find regulatory interpretive material in the preambles to notices and final regulations, plus any formally issued interpretations by FAA headquarters, the accountable directorate, or the Office of the Chief Counsel. For the JAA, the advisory circularjoint (ACJ), advisory material joint (AMJ), and temporary guidance material (TGM) may contain regulatory interpretive material.
(4) Establish the equivalence of these minimum airworthiness standards. Standards staffs must determine that the airworthiness standards in 14 CFR and the CS/JAR yield an equivalent technical result.
(5) Coordinate the Standards Equivalence Lists with EASA. FAA standards staffs must coordinate standards equivalence lists with their EASA counterparts, and develop procedures to do this. Our object is to make sure that each authority operates from the same standards equivalence list for each amendment pair.
(6) Approve the Standards Equivalence Lists. Both FAA and EASA approve their respective standards equivalence lists. The appropriate directorate approves the lists for the FAA, and the Regulation and Certification Directors approve for EASA. Once these lists are approved we will use them for all validation programs.
(7) Document the findings. Standards staff must record their results in detail using standard Directorate practices.
(a) This document should list the 14 CFR and CS/JAR, or group of airworthiness standards, the associated interpretive material, and factors that contributed to this determination.
(b) How specific the 14 CFR and CS/JAR airworthiness standards are determine the rigor of detail required to document the equivalence of airworthiness standards. Obvious equivalencies require less rigor. Subtle equivalencies need more.
(c) Retain these documents for future reference. The standards staff should keep a record of standards equivalency lists they developed for each 14 CFR and CS/JAR amendment pair. The lists may be needed in future validation programs involving aircraft, engines, or propellers certificated at one of these earlier amendment levels.
(8) Compare new 14 CFR and the CS/JAR language. Standards staffs must compare applicable airworthiness standards each time the FAA and EASA issue an amendment to their airworthiness standards. Changes in language may negate a previously established equivalency. Alternately, amendments to either the 14 CFR or the CS/JAR may lead to additional standards equivalencies. The documents defining standards equivalencies must be updated accordingly.
b. Compliance with the CS/JAR will automatically meet the 14 CFR airworthiness standards when the two standards are equivalent. We will require no further finding of compliance to 14 CFR.
333. STANDARDS DIFFERENCES LISTS. 14 CFR-CS/JAR differences must be compiled into lists. Each list is unique to a particular amendment-pair of 14 CFR-CS/JAR. An amendment-pair is a particular 14 CFR amendment number and the chronologically corresponding CS/JAR change and amendment number. Once a list is generated for a particular amendment-pair of airworthiness standards, that list is used as a reference for all validation projects where the FAA and EASA certification bases consists of that same amendment-pair. A standards difference list does not include those differences found to be equivalent as determined in accordance with paragraphs 308 and 332.
a. We at the FAA and EASA develop and maintain the standards differences lists to support all validation programs. FAA standards staffs and EASA counterparts will develop these comprehensive standards differences lists. All differences except those found to be equivalent are included in the lists. We will maintain a list of those standards where the 14 CFR is more stringent than the CS. EASA will maintain a list of those standards where the CS is more stringent than 14 CFR. The FAA and EASA will coordinate these lists, and make them publicly available.
NOTE: These lists define standards differences. 14 CFR-CS/JAR standards with identical language but differences in advisory or interpretive material should be dealt with, if necessary, as separate VIs. See paragraph 305 for more information on developing and using VIs.
b. Standards difference lists will provide the following:
(1) 14 CFR-CS/JAR amendment pair covered by the list,
(2) Identification of all 14 CFR-CS/JAR differences by paragraph number,
(3) Classification of each as an SSD or non-SSD,
(4) Brief explanation of why the standard is more stringent, and
(5) Reference to any associated policy or interpretive material (see paragraph 332a(3) for a detailed list of interpretive material).
NOTE: We have established with JAA, and will establish with EASA, baseline standards differences lists for 14 CFR parts 23, 25, 27, 29, and 33. For copies of these lists, contact the standards staff at the appropriate accountable directorate.
c. FAA Standards Staff Responsibilities. Each standards staff is responsible for developing and maintaining the standards differences lists for the airworthiness standards they administer (such as 14 CFR part 23, part 29 and part 33). Their specific responsibilities are:
(1) Defining Standards Differences. To define the standards differences for a 14 CFR-CS/JAR amendment pair, the staffs must:
(a) Identify the 14 CFR-CS/JAR Standards Differences. FAA standards staffs will compare each 14 CFR standard with the CS/JAR and identify all differences. The staff compares the language found in the 14 CFR and CS/JAR only. Differences between FAA advisory circulars (AC) and JAA advisory circulars joint (ACJ) or JAA advisory material joint (AMJ) or between ACs and acceptable means of compliance (AMC) and guidance material (GM) do not qualify as standards differences.
NOTE: Compare each individual 14 CFR standard to the entire set of CS/JAR standards, not just the corresponding paragraphs in the CS/JAR. Due to organizational differences, 14 CFR standards are, in some cases, addressed in several locations in the CS/JAR.
(b) Identify the 14 CFR Standards that are More Stringent than the CS. A standard is more stringent when compliance with the CS would not demonstrate compliance with 14 CFR.
NOTE: When using these standards differences lists for a certification program under 14 CFR § 21.29, the Administrator will prescribe additional airworthiness standards supplementing the exporting authority’s standards. These additional standards ensure that the proposed design meets the FAA’s applicable airworthiness standards. An examination of the product is necessary to establish them. The examination must be made when the product is presented for certification. Consider the project-specific MOC and the product’s design when making the final determination of which authority’s standards are more stringent. For example, one set of standards will state a quantitative value, while the counterpart standard will state a qualitative value. The product’s design could, then, determine which standard is more stringent. The validation team makes these determinations when conducting the product validation. In practice, the validation team rarely modifies the standards staff’s categorization of the standards differences. The validation team documents and coordinates all standards difference categorization changes with the standards staff.
(c) Classify the Difference as an SSD or a Non-SSD. We must determine if the standards differences are substantive, and if the differences could result in type design or approved manual changes to meet VA standards. This will determine if there’s an SSD or a non- SSD. To find out, FAA standards staffs review all interpretive material associated with the identified standards differences. We may use this review to lessen the standards differences when EASA and we have agreed to a common MOC. For us, the interpretive material is in the preambles to notices and final airworthiness standards, and any formally issued interpretations by FAA headquarters, the accountable directorate, or the Office of the Chief Counsel.
NOTE: Each standard staff may determine whether to maintain separate lists for SSDs and non-SSDs or combine them into one list.
(d) Coordinate the Standards Differences Lists with EASA. FAA standards staffs must coordinate the standards differences lists with their EASA counterparts. Staffs should develop coordination procedures. Our object is to make sure that each authority operates from the same standards differences lists for each amendment pair.
NOTE: The standards staff should work with their EASA counterparts to determine the most efficient method for developing the standards difference lists--to develop one all-inclusive list, or work individually.
(e) Approve the Standards Differences Lists. Both FAA and EASA approve their respective standards differences lists. The appropriate directorate approves the lists for us and the Regulation and Certification Directors approve for EASA. Once these lists are approved we will use them for all validation programs.
(2) Updating the Standards Differences Lists. A new standards differences list is developed each time either EASA or we issue an amendment or change to airworthiness standards. Each directorate standards staff works with their counterpart EASA organization to update the lists. Each standards staff must develop internal procedures to efficiently review new 14 CFR and CS/JAR amendments’ effects on the standards differences lists.
(3) Retaining all Standards Differences Lists for Future Reference. There will be a current standards differences list as well as lists generated for earlier amendment pairs. Each directorate standards staff will keep a historical record of the standards differences lists developed for each 14 CFR-CS/JAR amendment pair. The lists may be needed in future validation programs involving aircraft, engines, or propellers certificated at one of these earlier amendment levels.
(4) Publishing the Standards Differences Lists. Once a standards differences list is generated for a particular amendment-pair of airworthiness standards, that list is published and should be used for all validation projects where the regulatory basis consists of that amendmentpair. Each directorate standards staff posts current and historical standards differences lists on their certification Internet website.
(5) Difference lists may be presented in any manner that meets the needs of the respective directorate, the corresponding EASA organization, and the overall objectives of this paragraph.
334. PROGRAM STATUS MONITORING. We at the FAA and EASA will maintain a list of all ongoing certification/validation programs to help management monitor program status. The list will include completion dates for each validation phase and key points of contact. Each directorate’s standards staff will maintain a list of ongoing projects.
335. –339. RESERVED
335. –339. RESERVED
SECTION 4. FAA AS THE VALIDATING AUTHORITY
340. GENERAL. FAA certification personnel will find themselves in one of two very distinct roles when working on a validation program. For each validation program, we will either be the certifying authority (CA) or the validating authority (VA). The roles and responsibilities are very different in these two situations. The unique roles and responsibilities of FAA team members acting as VA on validation programs are described in this section.
SECTION 4. FAA AS THE VALIDATING AUTHORITY
NOTE: EASA is the CA for a product imported to the United States from an EU member state. For a non-EU JAA member state, that state’s NAA is the CA when a product is imported to the United States from that state.
a. As paragraph 313 indicated, the type validation principles divide a typical validation program into four phases. These four phases overlay our validation process defined in paragraph 204. See how the phases correspond in Figure 3-1. We modified the terms used to define the steps in the validation process to reflect the terms in the type validation principles.
For the same reason, we added an additional component (Step 2. Applicant, EASA, and FAA conduct general familiarization meeting).
FIGURE 3-1. VA FOUR-PHASE TYPE VALIDATION PROCESS
FIGURE 3-1. VA FOUR-PHASE TYPE VALIDATION PROCESS
Type Validation Program Phases FAA Validation Process Phase I: General familiarization
1. FAA receives application through EASA or NAA. 2. Applicant, EASA, and FAA conduct general familiarization meeting Phase II: Technical familiarization 3. Applicant, EASA, and FAA conduct technical familiarization meetings. 4. FAA establishes its VA certification basis. 5. FAA defines the VIs.
FAA identifies applicable generic VIs FAA identifies project VIs FAA identifies SSD and non-SSD for the project Phase III: Determining FAA
involvement
6. FAA determines their level of involvement for the VIs. Phase IV: Compliance determinations 7. EASA makes compliance determinations for assigned VIs and the non-SSD. 8. FAA makes compliance determinations for retained VIs and notifies EASA. 9. EASA issues statement of compliance to FAA VA certification basis. 10. FAA issues a type certificate.
b. The following paragraphs define the roles and responsibilities of FAA validation teams and standards staffs for each phase and component of the process.
341. PHASE I: GENERAL FAMILIARIZATION.
a. General. There are two components:
(1) We receive application through EASA or NAA (see paragraph 342), and
(2) Applicant, EASA, and we conduct general familiarization meeting (see paragraph 343).
b. Objective. The applicant and EASA give us an overview of the project. There are two objectives:
(1) To establish general timelines to complete the validation,
(2) To familiarize us with the design and thereby help us set up our validation team.
c. Initiation. Phase I begins when we receive the type certificate application from EASA or NAA (for applications from non-EASA member states).
NOTE: We should respond to requests to discuss issues before formal applications. The applicant should make these requests through EASA.
d. Completion. Phase I ends with the following items completed:
(1) The FAA has set up their validation team,
(2) FAA, EASA, and applicant have set up the initial schedule to complete the validation process.
NOTE: After phase I, the technical disciplines on a validation team may advance at different speeds. There’s no need for a technical discipline to delay their validation efforts because of the slower progress of another unrelated technical discipline.
342. FAA RECEIVES APPLICATION THROUGH EASA OR NAA.
a. The applicant sends an application for a U.S. type certificate to EASA or the NAA of the state of design. Applications from authorities who are members of the JAA, not in EASA, and have a bilateral agreement with United States have the option of applying directly to us. EASA/NAA forwards the application to the product accountable FAA directorate. Applicants may submit applications for products that have already received a EASA or NAA TC. Applicants may also submit applications for products for which they already applied for a EASA or NAA type certificate.
b. FAA Project Manager’s Responsibilities prior to the General Familiarization Meeting. Upon receipt of an application, the FAA project manager:
(1) Reviews the application to determine compliance with 14 CFR § 21.15, Application for Type Certificate, FAA Order 8110.4, and the appropriate bilateral agreement.
(2) Responds in writing to the EASA or NAA within 30 days, identifying any application deficiencies to the EASA or NAA for resolution. Letter will indicate if we need a general familiarization meeting.
(3) Ensures that the applicant and EASA/JAA know about the generic VI list posted on the product accountable directorate’s website; and
(4) Conducts a top-level review of our generic VI list.
343. APPLICANT, EASA, AND FAA CONDUCT THE GENERAL FAMILIARIZATION MEETING. The key element of this phase is the general familiarization meeting, which should last no more than two days. An effective general familiarization meeting maximizes the quality of any follow-on meetings.
a. Meeting Agenda. The general familiarization meeting agenda will include:
(1) Design overview. The applicant presents an overview of the product design, as currently known, emphasizing new or unusual design features. For derivative programs, applicant should clearly describe and emphasize the changed parts.
(2) Status of program. EASA, with applicant support, brief the program status. This should include a briefing on EASA decisions already made, such as the composition of certification team and commitments to certification schedule and specific milestones.
(3) Validation schedule. The applicant briefs a validation program schedule. The presentation should allow for open discussions between FAA and EASA on resource requirements and risks. The briefing should offer enough information for us to establish the appropriate technical disciplines, the team’s size, and develop guidance for them. The FAA project manager, EASA PCM, and applicant project manager set up the initial validation schedule during the general familiarization meeting. Our standards staff needs to make sure that management is both aware and involved with our approval of the timelines and associated resource requirements.
(4) Validation Item discussion. The FAA will discuss applicable VIs. We will give the applicant and EASA the current generic VI list for the type of product under review, but need not provide the associated informational issue papers. If they’re available, we should show the applicant and EASA how to find the full text of each generic VI. We must make it clear that the generic VIs will be reviewed in greater detail for project applicability during the technical familiarization phase of the project.
(5) Standards Differences List discussion. If available, we’ll also provide copies of the standards differences lists. The lists will be discussed further during phase II--technical familiarization.
(6) Action Items and meeting minutes. Early in the meeting, attendees should decide who among them will keep meeting minutes and compile a separate set of action items. Regardless who prepares the minutes, FAA and EASA team attendees should agree to their content. The minutes-taker should send copies to the FAA project manager and EASA PCM.
b. Meeting Attendees. The applicant, EASA PCM, and FAA project manager, and possibly the FAA standards staff manager and project officer, attend the meeting. FAA and EASA technical specialists do not, as a rule, attend. Detailed technical information will not be presented since the objective is for the applicant to provide only a broad overview of the project. However, the applicant should bring the people qualified to make the presentations, and agree to a validation schedule.
c. Exceptions to conducting a General Familiarization Meeting. Participants may want to waive the general familiarization meeting. This is acceptable only if:
(1) The project is well understood by the FAA, and phase I objectives are met by other means (correspondence, teleconference, and direct discussion), and
(2) EASA and applicant are experienced in this type of project, and their capabilities are well known to us.
NOTE: Before deciding to forego a general familiarization meeting, we must carefully consider the goals of this phase of the project. Specifically, we must ensure that the correct validation team is assembled for the technical familiarization meetings. We could waste time if the correct FAA team members are not at the technical familiarization meetings. Conversely, we’ll waste staff hours if an unneeded specialist attends a technical familiarization meeting. The project manager must have a good understanding of the overall project schedule and key milestones, and agree to those schedule milestones, before the technical familiarization phase begins.
c. FAA Project Manager’s Responsibilities during Phase I. After completing the general familiarization meeting, the FAA project manager will:
(1) Determine the size of our validation team and the technical disciplines needed. Consider the schedule agreed to during the general familiarization meeting when selecting team members. Submit a list of validation team members to the EASA; and
(2) Prepare the FAA technical team for the technical familiarization phase. The project manager will brief the validation team on the results of the general familiarization meeting. This preparation will also include refresher training on the type validation principles. How much preparation the team will need is up to the validation project manager. In addition to
the project’s significance, the manager should also consider the validation team members’ experience with validation projects and type validation principles.
NOTE: We can include the EASA certification team in FAA team validation refresher training. This will give the EASA team a useful perspective on our team, and we’ll have a valuable opportunity to familiarize ourselves with EASA procedures. The FAA project manager should coordinate this training with the EASA PCM.
344. PHASE II: TECHNICAL FAMILIARIZATION. The main purpose of technical familiarization is to acquaint FAA technical specialists in each functional area with the design features of the product and the applicant’s approach to compliance with the requirements. The applicant presents the technical definition of the project and the associated compliance methodology. A collateral benefit is for EASA technical specialists and us to develop a strong working and communication relationship. A trusting relationship is critical for an efficient validation process.
a. General. Phase II has three components. Although each has specific deliverables, the components are linked and worked simultaneously. The components are:
(1) Applicant, EASA, and FAA conduct technical familiarization meetings (see paragraph 345),
(2) FAA establishes our VA certification basis (see paragraph 346), and
(3) FAA defines the VIs (see paragraphs 347, 348, 349, and 350).
b. Objective. Phase II objectives are to:
(1) Familiarize the FAA technical team with the design and associated compliance methodology for the project,
(2) Establish an initial VA certification basis,
(3) Identify initial VIs, and
(4) Establish strong communications between the FAA, EASA, and applicant’s technical specialists.
c. Initiation. Phase II begins with the scheduling of a technical familiarization meeting (or meetings), unless the product is a derivative and we determine that changes from previously validated designs don’t warrant the meeting.
d. Completion. Phase II ends when we at the FAA establish the initial VA certification basis and identify the initial VIs.
(1) We will release a G-1 issue paper defining our initial certification basis. We will also release issue papers that define our initial VIs. The issue papers will state the issue and our position only. The applicant and EASA team respond to the issue papers during phase III.
(2) We define the initial VIs based on the applicant’s description of the design. Additional VIs may be identified during phases III and IV if there’s a change to the design, intended use of the product, assumptions used for certification, or compliance methodology.
Continue reading ↓ 120 of 385 passages shown