2/10/16

 

8900.1 CHG 445

VOLUME 15  FAA Safety TEAM POLICIES AND PROCEDURES

Chapter 3  DATA COLLECTION, ANALYSIS, AND REPORTING

Indicates new/changed information.

Section 1  General Information

15-3-1-1    GENERAL. The Federal Aviation Administration (FAA) Safety Team (FAASTeam) Program Managers (FPM) and/or the Regional FAASTeam Point of Contact (RFPOC) will collect, analyze and record data to determine common factors of accidents, incidents, runway incursions, pilot deviations (PD), and/or any identified safety hazards, unsafe conditions or concerns. The data collected is used to develop analysis reports that prioritize hazards with unacceptable risk levels within each Flight Standards District Office (FSDO) district.

Indicates new/changed information.

A.    Purpose. This chapter describes the procedures for collecting historic and current accident and incident data that is applicable to the FPM’s assigned FSDO district. The chapter also provides a reporting method to use once information has been collected and analyzed. This analyzed data can be used to develop educational outreach programs in the interest of preventing future mishaps, mitigate unacceptable risk levels, or limit exposure to recognized unsafe conditions. These programs may be included in the FPM’s annual work program. The FPM can share this de-identified information with the aviation community through specific briefings, formal presentations, safety recommendations, or other mitigation strategies.

Indicates new/changed information.

B.    Scope. This chapter is applicable to RFPOCs and FPMs. It provides guidance on collecting incident and accident information from within existing National Transportation Safety Board (NTSB) and FAA databases, as well as analyzing the information to develop educational products and mitigation strategies. The identification of probable cause remains the responsibility of the NTSB. The information gathered during this task may be used as the basis of FAASTeam program activities and events.

15-3-1-3    TASK PREREQUISITES AND SIGNIFICANT INTERFACES.

A.    Program Tracking and Reporting Subsystem (PTRS) Activity Code. Not applicable.

B.    Significant Interfaces. This task requires coordination with the following organizations or individuals:

    FAA Aviation Data System Branch (AFS-620);

    FAA Investigator-in-Charge (IIC);

    National FAASTeam Branch (AFS-850);

    FPMs;

    Flight Standards Field Office (FSFO) Management Team;

    NTSB; and

    RFPOC.

C.    Automation Tools:

    Accident/Incident Data System (AIDS);

    National FAASTeam SharePoint site and associated tools;

    NTSB Aviation Accident Database;

    Safety Performance Analysis System (SPAS);

    Air Traffic Quality Assurance (ATQA);

    Service Difficulty Reports (SDR);

    NASA—Aviation Safety Reporting System (ASRS);

    Emergency Operations Network (EON); and

    Near Midair Collisions Subsystem (NMACS).

D.    References (current editions):

1)    Procedural Guidance:

    FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting.

    FAA Order 8900.1, Flight Standards Information Management System (FSIMS).

2)    Additional Guidance:

    Advisory Circular (AC) 20-109, Service Difficulty Program (General Aviation).

    Service Difficulty Reports (SDR).

E.    Forms:

    FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice.

    FAA Form 8020-15, Investigation of Near Midair Collision Report.

    FAA Form 8020-18, Investigation of Pilot Deviation Report.

Indicates new/changed information.

    FAA Form 8020-23, FAA Accident/Incident Report.

F.    Job Aids. [Reserved]

15-3-1-5    BACKGROUND. This chapter can be used for data analysis and reporting on a scheduled or as-needed basis to provide briefings, plan activities, retarget programs, or as an educational and outreach service to other aviation stakeholders. Some examples are provided below:

Indicates new/changed information.

A.    Annual FSDO Report. Develop the annual FSDO district accident/incident report to support work program development and justification for budget planning.

B.    Certificated Flight Instructor (CFI) Special Emphasis. Brief CFIs at workshops or open forums on recent, local incidents and accidents, and proactively suggest mitigation strategies based on historical data for upcoming events.

Indicates new/changed information.

C.    Inspection Authorization (IA) Renewal Meetings. Meet with IAs to discuss airworthiness-related accidents/incidents, maintenance-related causal factors (if maintenance-related), and local or national special emphasis programs.

Indicates new/changed information.

D.    Local Experimental Aircraft Association (EAA) Chapter Meetings. Provide local and national information on incidents/accidents specific to the experimental, amateur-built, and light-sport pilots, technicians and/or mechanics and suggest mitigation strategies to address common causal factors.

Indicates new/changed information.

E.    Information Sharing. Share information with other groups, organizations or individuals involved in aviation, such as flight and maintenance schools, repair stations, agricultural aircraft operators, Title 14 of the Code of Federal Regulations (14 CFR) parts 133 and 135 operators, National Business Aircraft Association (NBAA), Experimental Aircraft Association (EAA), The Ninety Nines, Inc., International Organization of Women Pilots, etc.

15-3-1-7 through 15-3-1-17 RESERVED.