The answer to this question depends on the quality of the submissions in your Formal Application Package. Using the Safety Attribute Inspection (SAI) data collection tools to audit your safety-critical processes will greatly improve the quality of your Formal Application Package, especially your company manuals and other system documentation, and will reduce the amount of time needed to complete the certification process.
Contact your local FAA Flight Standards District Office (FSDO) for information on the certification process. You can locate the office nearest you by visiting the FAA Public website at http://www.faa.gov.
The FAA can give you guidance on FAA processes such as ATOS. According to Title 49 USC, air carriers have a duty to provide service with the highest possible degree of safety in the public interest, and FAA must determine that an air carrier applicant is equipped and able to operate safely before issuing an operating certificate. (See Title 49 USC, Sections 44702 and 44705.) Refer to paragraph 10-2 in FAA Order 8900.1, Volume 10, Chapter 1, Section 1.
In the Formal Application Package, you have to be able to identify the airplane you intend to use by make/model/serial number so that you can write your training programs and maintenance programs. You do not have to have actual possession of the airplane; you can show intent by including a lease or purchase agreement in your Formal Application Package.
There is some flexibility about when a CPD step should be accomplished. For example, with approval from the AFS 900 Manager, the Certification Process Manager (CPM) can use the Aircraft Configuration Job Aid at any time in the certification process if there are concerns about the applicant�s airplane.
Inspectors use Safety Attribute Inspections (SAIs) to collect data for ATOS design assessments. They are organized into five sections, each addressing the safety attributes. One section covers responsibility and authority. The other sections cover procedures, controls, process measures, and interfaces. These safety attributes are not standards that have to be incorporated into your system processes. However, they do provide a logical structure for the Certification Project Manager to determine whether an air carrier applicant�s system process or program meets the full intent of a regulation. In other words, does the system or program meet the literal requirements and intent of the regulations, and is it capable of identifying operational hazards and managing associated risk (PDF)?
You must audit your processes using any SAI data collection tool that contains regulatory requirements that apply to your proposed scope of operations.
All applicants and certificate holders have some "No" answers. "No" answers do not automatically equate to an unsafe condition or a regulatory violation, unless that particular "No" has a regulatory basis and the documented process includes a possible violation or an unsafe condition. "No" answers fall into one of these categories:
The transition to ATOS has prompted some industry representatives and FAA inspectors to inquire how air carriers can prepare their manuals to become "compliant," "aligned," "integrated," or "conformed" to ATOS. While these questions are well intentioned, they reveal the disconnect from the intent of the program. ATOS does not prescribe a format for air carrier manuals. There is no such thing as an ATOS compliant manual (PDF).
The requirements mentioned in the question imply that ATOS is a standard, which it is not. ATOS is an oversight system for use by inspectors, not a set of standards or processes with which an operator must comply. ATOS helps inspectors determine regulatory compliance, but does not impose new or additional requirements or standards.
System safety requirements are not new. They have a basis in the regulations. The regulatory theory that underlies system safety proclaims that inherent in Title 49, United States Code (49 USC) is the requirement for air carriers to identify operational hazards and manage associated risks. In its simplest form, the rationale for system safety is outlined in Title 49 USC, which states that air carriers have a duty to provide service with the highest possible degree of safety in the public interest, and FAA must determine that an air carrier applicant is equipped and able to operate safely before issuing an operating certificate. (See 49 USC, Sections 44702 and 44705.) Refer to paragraph 10-2 in 8900.1, Volume 10, Chapter 1, Section 1.In Title 49 USC,
ATOS did not invent these requirements. They have existed since the Federal Aviation Act of 1958. The objective of ATOS is to ensure that the Flight Standards Service and certificate holders meet their separate responsibilities in accordance with Title 49 USC. Title 49 USC underpins the regulations in Title 14, Code of Federal Regulations (14 CFR). In other words, at a high level, the statutory requirement for air carriers to be able to identify operational hazards and manage associated risks is carried over into the intent of regulations in 14 CFR. Certificate holders must meet the literal requirements of the regulations as well as their intent. To meet the intent of the regulations, the systems and programs an air carrier uses to conduct its business and to comply with the regulations must be capable of identifying the hazards in the operating environment and managing associated risk.
No. ATOS is an oversight methodology used by FAA inspectors to conduct certification and surveillance of 14CFR Part 121 air carriers.
No, this Data Base is internal to the FAA. Additionally, the ATOS program is a continual improvement program and changes can occur week to week. Major changes to the Data Collection Tools and system functionality are scheduled at various times throughout the year. It is best for certificate holders to download current information from the ATOS public web site at the time they need it. You are also encouraged to contact your FAA Certificate Management Office for assistance.
ATOS is an oversight methodology for use by inspectors, not a set of standards or processes that an operator must comply with. To suggest that an operator must comply with this oversight process is to misconstrue the intent of the system. The term "compliance" as commonly used has referred to regulatory issues. While encouraged, there is no regulatory directive for a carrier to incorporate the underlying concepts of System Safety or to reference the ATOS surveillance tools in any aspect of their operations. Air Carrier certification and surveillance is are based on the regulations requirements and structures specifically outlined in 14 CFR Part 121 the Code of Federal Regulations.
System Safety/Risk Management, as presented in the ATOS process, is only one tool for achieving FAA oversight objectives. FAA Regulations dictate what a carrier has to do, not how to do it. The FAA developed ATOS from several different system safety approaches to form a program that works for them. Certificate holders may choose to adopt the ATOS methodology or develop their own to suite their individual needs. Certificate holders may find it beneficial to use the ATOS approach, however, so that both they and the FAA are looking at the air carriers systems the same way.
The International Civil Aviation Organization has adopted a rule requiring that all member states require all air carriers to implement and document a Safety Management System (SMS). The rule has been in effect for some time and many member states have implemented it. If an air carrier is flying to a member state that chooses to enforce the rule the carrier may be denied entry or not allowed to depart without documentation of a SMS. Implementing a SMS during the certification process will serve the interest of operating to the highest level of safety and may be a necessity for international operations.
The ATOS Program uses a relational database that's made up of several data tables. SQL Server 2000 is the software that is used to manage those tables.
Page Last Modified: 03/19/13 10:44 EDT
This page can be viewed online at: http://www.faa.gov/about/initiatives/atos/air_carrier/cert_ques_and_ans/