Appendix 1 A1-3 Figure 3. Sample of a Type 2 LOA Application using a RTCA/DO-200 Compliance
The ACME Avionics Manufacturer PO Box 1 Nowhere, Arkansas 71953 FAA – Southwest Region 2601 Meacham Blvd Fort Worth, Texas, 76193 Manager, Aircraft Certification Office, ASW-150 Subject: Request for New Type 2 Letter of Acceptance for ACME Company’s Aeronautical Data Process To Whom It May Concern:
The ACME Avionics Manufacturer is applying for a new Type 2 letter of acceptance for our aeronautical data process. We comply with AC 20-153A and RTCA/DO-200 and request your review of the enclosed data being submitted in support of this application. The ACME Avionics Manufacturer receives data from other sources, and develops navigation information per the data processes specified in ACME Documents XXX.XX and YYY.YY, respectively. Acceptance of our aeronautical data process is requested based on the specification and control of these data processes, compliance with AC 20-153A and the compatibility of the delivered data with the following products:
ACME FMS Model XY, P/N 12345-23a ACME FMS Model Z, P/Ns 56789-1 through 56789-8 ACME has established compatibility with these systems based on the original software design documentation approved under the original TSO authorization. Compilation of data to the compatible format is accomplished using ACME Tool 123.
The information will be developed at the ACME Avionics Manufacturer, 3000 Hill Street, Nowhere, Arkansas 71953. The ACME Avionics Manufacturer hereby certifies that the Data Processing Procedures, Quality Assurance, and Configuration Management processes, which are in accordance with RTCA/DO-200, sections 3, 4, and 5 have been established and the navigation information is produced in accordance with this system.
Your efforts in support of this request are most appreciated.
Sincerely,
Administrator, ACME Avionics Manufacturer
Enclosures:
1 copy ACME drawings, tool summary, quality assurance manual, specifications and processes.
Appendix 2 A2-1 Appendix 2. FAA LOAs
Figure 1. Sample of a Type 1 FAA LOA
ACME Data Company December 25, 2010 Box 1 Nowhere, Arkansas 71953
The FAA has determined the ACME Data Company complies with AC 20-153A and RTCA/DO-200A with regards to its processing of navigation data. The Type 1 LOA does not authorize the ACME Data Company to supply navigation data directly to an operator (e.g., enduser, airlines) for loading into the installed equipment.
The following terms and conditions are applicable to this letter of acceptance, are not transferable, and are effective until surrendered or withdrawn by the holder, or terminated by the FAA:
1. The ACME Data Company data quality requirements for the receipt of data from other sources, and for the delivery of data to its customers, are defined in ACME document XXX.XX.
2. The ACME Data Company procedures for processing data are defined in ‘XXX Data Processing Standards’.
3. Reporting of Failures, Malfunctions, and Defects. The ACME Data Company must report to the FAA < insert local FAA LOA Program Manager’s office > any failure, malfunction, or defect of the aeronautical data produced under this LOA that may have a safety effect on operational use of the data.
4. Maintain a Quality Management System (QMS). The ACME Data Company must maintain a QMS as described in RTCA/DO-200A, section 2.5. Changes to the QMS that may affect the data quality objectives must be reported to the < insert local FAA LOA Program Manager’s office/MIDO > before implementation.
5. Design Changes.
a. The ACME Data Company must submit minor changes to the data quality requirements, the data processing standards, or the QMS to the < insert local FAA LOA Program Manager’s office > in accordance with procedures described within ACME document XXX.XX. All other changes are considered major, and must be substantiated and accepted prior to implementation in the same manner as the original LOA.
Appendix 2 A2-2
b. Upon receipt of notification by the < insert local FAA LOA Program Manager’s office > that an unsafe condition exists in a database product supplied under this LOA, the ACME Data Company shall develop a corrective action and submit it to the < insert local FAA LOA Program Manager’s office > for approval. The ACME Data Company shall expedite distribution of the approved corrective action to customers and users.
6. The ACME Data Company must perform periodic internal audits as described in RTCA/DO-200A, section 3, with a maximum time between audits (whether total or incremental) of not more than one year. Any major non-conformities as described in RTCA/DO-200A, section 3.4 must be reported to the < insert local FAA LOA Program Manager’s office >. Additionally, the FAA may perform periodic audits in accordance with procedures described within ACME document XXX.XX.
7. ACME Data Company must advise its customers of the status of its LOA as well as the status of LOAs (or foreign acceptance, including designation of the foreign authority that acknowledges the foreign source’s compliance to RTCA/DO-200A and the means of approval or acceptance) for all previous chain participants (up to, but not including, a Contracting State’s AIP). The method must be timely to ensure that customers can react to changes in the status of its LOA.
Manager, {regional} Aircraft Certification Office
Appendix 2 A2-3 Figure 2. Sample of a Type 2 FAA LOA
ACME Avionics Manufacturer December 25, 2005 PO Box 1 Nowhere, Arkansas 71953
The FAA has determined that the ACME Avionics Manufacturer complies with AC 20-153A and RTCA/DO-200A with regards to its processing of navigation data. Compatibility has been established with the following systems:
ACME FMS Model XY, P/N 12345-23a ACME FMS Model Z, P/Ns 56789-1 through 56789-8
(or)
“…identified in ACME FMS Compatibility Matrix, Document XXX.XX, dated YYY, or latest FAA approved revision.”
The following terms and conditions are applicable to this letter of acceptance, are not transferable, and are effective until surrendered or withdrawn by the holder, or terminated by the FAA:
1. The ACME Avionics Manufacturer data quality requirements for the receipt of data from other sources, and for the delivery of data to its customers, are defined in ACME Documents XXX.XX and YYY.YY, respectively.
2. The ACME Avionics Manufacturer procedures for processing data are defined in ‘XXX Data Processing Standards’.
3. Reporting of Failures, Malfunctions, and Defects. The ACME Avionics Manufacturer must report to the FAA <insert local FAA LOA Program Manager’s office> any failure, malfunction, or defect of the aeronautical data produced under this LOA that may have a safety effect on operational use of the data.
4. Maintain a Quality Management System (QMS). The ACME Avionics Manufacturer must maintain a QMS as described in RTCA/DO-200A, section 2.5. Changes to the QMS that may affect the data quality objectives must be reported to the < insert local FAA LOA Program Manager’s office/MIDO > before implementation.
5. Design Changes.
a. The ACME Avionics Manufacturer must submit minor changes to the data quality requirements, the data processing standards, or the QMS to the < insert local FAA LOA Program Manager’s office > in accordance with procedures described within
Appendix 2 A2-4 ACME document XXX.XX. All other changes are considered major, and must be substantiated and accepted prior to implementation in the same manner as that for the original LOA.
b. Upon receipt of notification by the < insert local FAA LOA Program Manager’s office > that an unsafe condition exists in a database product supplied under this LOA, the ACME Avionics Manufacturer shall develop a corrective action and submit it to the < insert local FAA LOA Program Manager’s office > for approval.
The ACME Avionics Manufacturer shall expedite distribution of the approved corrective action to customers and users.
6. The ACME Avionics Manufacturer must perform periodic internal audits as described in RTCA/DO-200A, section 3, with a maximum time between audits (whether total or incremental) of not more than one year. Any major non-conformities as described in RTCA/DO-200A, section 3.4 must be reported to the < insert local FAA LOA Program Manager’s office >. Additionally, the FAA may perform periodic audits in accordance with procedures described within ACME document XXX.XX.
7. ACME Avionics Manufacturer must advise its customers of the status of its LOA as well as the status of LOAs (or foreign acceptance, including designation of the foreign authority that acknowledges the foreign source’s compliance to RTCA/DO-200A and the means of approval or acceptance) for all previous chain participants (up to, but not including, a Contracting State’s AIP). The method must be timely to ensure that customers can react to changes in the status of its LOA.
Manager, {regional} Aircraft Certification Office
Appendix 2 A2-5 Figure 3. Sample of a Type 2 FAA LOA using RTCA/DO-200 Compliance
ACME Avionics Manufacturer December 25, 2005 PO Box 1 Nowhere, Arkansas 71953
The FAA has determined that the ACME Avionics Manufacturer complies with AC 20-153A and RTCA/DO-200 with regards to its processing of navigation data. Compatibility has been established with the following systems:
ACME FMS Model XY, P/N 12345-23a ACME FMS Model Z, P/Ns 56789-1 through 56789-8
(or)
“…identified in ACME FMS Compatibility Matrix, Document XXX.XX, dated YYY, or latest FAA approved revision.”
The following terms and conditions are applicable to this letter of acceptance:
1. The ACME Avionics Manufacturer data processes for the receipt of data from other sources, and for the delivery of data to its customers, are defined in ACME Documents XXX.XX and YYY.YY, respectively.
2. The ACME Avionics Manufacturer procedures for processing data are defined in ‘XXX Data Processing Standards’. Proper records must be maintained and configuration management guidelines established and followed in accordance with RTCA/DO-200.
3. Reporting of Failures, Malfunctions, and Defects. The ACME Avionics Manufacturer must report to the FAA < insert local FAA LOA Program Manager’s office > any failure, malfunction, or defect of the aeronautical data produced under this LOA that may have a safety effect on operational use of the data.
4. Maintain a Quality Assurance Process. The ACME Avionics Manufacturer must maintain a quality assurance process as described in RTCA/DO-200, section 4.
Changes to these processes must be reported to the < insert local FAA LOA Program Manager’s office > before implementation.
5. Design Changes.
a. The ACME Avionics Manufacturer must submit changes to the data processing standards, or the quality assurances processes to the < insert local FAA LOA Program Manager’s office > in accordance with procedures described within
Appendix 2 A2-6 ACME document XXX.XX. These changes must be substantiated and accepted prior to implementation in the same manner as that for the original LOA.
b. Upon receipt of notification by the < insert local FAA LOA Program Manager’s office > that an unsafe condition exists in database product supplied under this LOA, the ACME Avionics Manufacturer shall develop corrective action and submit it to the < insert local FAA LOA Program Manager’s office > for approval.
The ACME Avionics Manufacturer shall expedite distribution of the approved corrective action to customers and users.
6. The ACME Avionics Manufacturer must perform periodic internal audits as described in RTCA/DO-200, section 4.2, with a maximum time between audits (whether total or incremental) of not more than one year. Any non-conforming processes must be reported to the < insert local FAA LOA Program Manager’s office >. Additionally, the FAA may perform periodic audits in accordance with procedures described within ACME document XXX.XX. Records of audits must be maintained for a period of 5 years.
7. ACME Avionics Manufacturer must advise its customers of the status of its LOA as well as the status of LOAs (or foreign acceptance, including designation of the foreign authority that acknowledges the foreign source’s compliance to RTCA/DO-200 and the means of approval or acceptance) for all Type 1 LOA holders (up to, but not including, a Contracting State’s AIP). The method must be timely to ensure that customers can react to changes in the status of its LOA.
Manager, {regional} Aircraft Certification Office,
Appendix 3 A3-1 Appendix 3. Objectives Matrix
Figure 1. Data processing objectives using RTCA/DO-200A Objective
Reference Verification Method
(e.g., Inspection, Observation)
Applicant’s Reference Document or ID Config.
Control on Reference Document Objective Met Yes, No or Pending Notes
Numerical reference Application of RTCA/DO-200A to operators
1-1 Before loading, the operator must ensure that the data complies with DQRs.
AC 11a
1-2 The operator must document steps, if they have defined the requirements for completeness and timeliness.
AC 11a(5)
1-3 Before loading, the operator must review status of all LOAs (or equivalent) within the data chain.
AC 11a(6)
1-4 If performing data preparation or transmission, operator must comply with AC paras 10 and
11.
AC 12
Relationship between RTCA/DO-200A, airworthiness approval and TSOA
2-1 For existing systems, the DQRs should be identified.
AC 19b/(19a)
2-2 The DQRs must be under configuration control.
AC 20
2-3 The DQRs must be consistent with intended function.
AC 20b
2-4 Required assurance level for data process must be identified and consistent with intended use.
AC 21
2-5 Changes to DQRs must be evaluated (major, minor, or no effect). Ensure processes are in place.
AC 22b
Appendix 3 A3-2
Objective
Reference Verification Method
(e.g., Inspection, Observation)
Applicant’s Reference Document or ID Config.
Control on Reference Document Objective Met Yes, No or Pending Notes
Numerical reference Application of RTCA/DO-200A to data suppliers 3-1 Foreign suppliers must be identified. AC 11a(6)
3-2 Type 2 LOA must be associated with specific equipment.
AC 10a
Compliance plan
4-1 Compliance plan must be developed per RTCA/DO-200A, Sect.2.2.
AC 13b(1)
4-2 Compliance plan shall be prepared to address all aspects of data process. It shall identify the 5 items in RTCA/DO-200A, sect 2.2.
RTCA/DO- 200A
2.2
DQRs
5-1 Documentation of DQRs per RTCA/DO-200A, Sect. 2.3.
AC 13b(2)
5-2 Mutual agreement of DQRs between Type 2 LOA holder and its data suppliers.
AC 13b(2)
5-3 Changes to DQRs must be coordinated between Type 2 LOA holder and its data suppliers.
AC 13b(4)
5-4 Changes to DQRs that result in a major change to a TSOA article must obtain a new TSOA.
AC 10a(3)
5-5 DQRs must be under configuration control. AC 20
5-6 The data shall have the ag reed data accuracy. RTCA/DO- 200A
2.3.2 Item 1
Appendix 3 A3-3
Objective
Reference Verification Method
(e.g., Inspection, Observation)
Applicant’s Reference Document or ID Config.
Control on Reference Document Objective Met Yes, No or Pending Notes
Numerical reference 5-7 The data shall have the agreed data resolution. RTCA/DO- 200A
2.3.2 Item 2
5-8 The data shall have th e agreed data assurance level.
RTCA/DO- 200A
2.3.2 Item 3
5-9 Level 4 data must be distinguishable from any RTCA/DO-200A compliant data.
AC 15b
5-10 Documentation must show traceability between identification of installed data with version of DQRs.
AC 9b(4)(b)
5-11 The data shall have the ag reed data traceability. RTCA/DO- 200A
2.3.2 Item 4
5-12 The data shall have the agreed data timeliness. RTCA/DO- 200A
2.3.2 Item 5
5-13 The data shall have the agreed data completeness.
RTCA/DO- 200A
2.3.2 Item 6
5-14 The data shall have the agreed data format. RTCA/DO- 200A
2.3.2 Item 7
NOTE: Per RTCA/DO-200A, the user is defined as any group or organization in the data chain that receives data. The user shall determine the DQRs. For example, an applicant for a Type 2 LOA is considered to be the ‘user’ of the data received by any Type 1 data supplier.
5-15 The user shall base the data quality upon the most restrictive requirement.
RTCA/DO- 200A
2.3.3 Item 2
Appendix 3 A3-4 Objective
Reference Verification Method
(e.g., Inspection, Observation)
Applicant’s Reference Document or ID Config.
Control on Reference Document Objective Met Yes, No or Pending Notes
Numerical reference 5-16 The user shall assure the quality requirements are attained.
RTCA/DO- 200A
2.3.3 Item 3
5-17 The user shall determine the nature of action to be taken in the event of an error or inconsistency.
RTCA/DO- 200A
2.3.3 Item 4
5-18 The user shall be responsible for establishing its requirement for being notified of any data alteration.
RTCA/DO- 200A
2.3.3 Item 5
5-19 The data supplier shall provide data that meets the agreed user DQRs.
RTCA/DO- 200A
2.3.4 Item 1
5-20 The data supplier shall have a system for handling problems reported during data processing and those reported by the user after delivery.
RTCA/DO- 200A
2.3.4 Item 2
5-21 All problems reported with the data shall be analyzed and any errors or anomalies resolved and documented.
RTCA/DO- 200A
2.3.4 Item 3
5-22 All errors or anomalies detected in the data shall be resolved prior to delivery.
RTCA/DO- 200A
2.3.4 Item 4
5-23 Information concerning any errors or anomalies found after delivery shall be made available to all affected users.
RTCA/DO- 200A
2.3.4 Item 5
5-24 Data supplier must establish a procedure to report to FAA any safety related error or defect.
AC 10a(1)
Appendix 3 A3-5
Objective
Reference Verification Method
(e.g., Inspection, Observation)
Applicant’s Reference Document or ID Config.
Control on Reference Document Objective Met Yes, No or Pending Notes
Numerical reference 5-25 The means by which errors or anomalies are resolved shall be reported to all affected users.
RTCA/DO- 200A
2.3.4 Item 6
5-26 The delivery format requirements shall be documented.
RTCA/DO- 200A
2.3.5 Item 2
5-27 Documentation shall be maintained that identifies all of the suppliers of data and the approval status of each.
RTCA/DO- 200A
2.3.5 Item 3
Data processing requirements
6-1 Data supplier must comply with RTCA/DO- 200A, sect 2.4.
AC 13b(3)
6-2 The data processing procedures shall define the means to confirm that the data has been received without corruption.
RTCA/DO- 200A
2.4.1 Item 1
6-3 The data processing procedures shall define the means by which data is assembled.
RTCA/DO- 200A
2.4.1 Item 2
6-4 The data processing procedures shall define the means to ensure stored data is protected from corruption.
RTCA/DO- 200A
2.4.1 Item 3