Radar Vectors
FAA Order Cancelled Issued Dec 18, 2014 AJI-1 227 pages Copy saved Nov 18, 2026

Order JO 8020.16B Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting

This order prescribes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and incident notification, investigation, and reporting. It provides direction and guidance to ATO service units, service centers, service areas, offices, and facilities when they are called upon to perform accident investigations. All concerned personnel must familiarize themselves with the provisions of this order that pertain to their operational responsibilities and exercise their best judgment if they encounter situations not covered by the order.

This document is cancelled. Cancelled by JO 8020.16C. Check the official source before relying on it.

Official source ↗ Open PDF

Text read by OCR from a scanned file (9 of 227 pages). Check the original, as some words may be misread.

12/31/2014

SUBJ: Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting

This order prescribes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and incident notification, investigation, and reporting. It provides direction and guidance to ATO service units, service centers, service areas, offices, and facilities when they are called upon to perform accident investigations. All concerned personnel must familiarize themselves with the provisions of this order that pertain to their operational responsibilities and exercise their best judgment if they encounter situations not covered by the order.

This order cancels FAA Order 8020.16A, dated December 27, 2010.

This is an ATO order that has been written in coordination with FAA Order 8020.11 and describes specifically the ATO's roles and responsibilities in aircraft accidents, aircraft incidents, and occurrences as they pertain to notification, reporting, and data retention.

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Air Traffic Organization Policy

ORDER NUMBER JO 8020.16B

Distribution: Electronic Initiated By: AJI-17 ATO Safety Litigation Support

Table of Contents

Chapter 1. General … 1

1. Purpose of This Order … 1

2. Audience … 1

3. Where to Find This Order … 1

4. What This Order Cancels … 1

5. Explanation of Changes … 1

6. Distribution … 1

7. Authority to Change This Order … 2

8. Supplements … 2

9. Definitions … 2

10. Related Publications … 2

11. Forms and Reports … 2

12. Safety Risk Management (SRM) Analysis … 2

13. FAA Responsibilities in Aircraft Accident Investigations … 2

14. Responsibilities of Regional Divisions, Aircraft Certification Directorates, Service Areas, Service Centers, Flight Service Program Offices, and the ATO Litigation Support Group in Aircraft Accident Investigations … 3

15. FAA and NTSB Accident and Incident Investigation Agreements … 4

16. Post-Accident or Incident Drug Testing … 5

17. FAA Investigator-in-Charge (IIC) … 5

19. Other FAA Personnel … 5

20. FAA Safety Recommendation Program … 5

21. Training … 6

22.-29 RESERVED … 6

Chapter 2. FAA Elements Involved in Notification, Investigation, and Reporting … 7

30. Office of Accident Investigation and Prevention … 7

31. Operations Centers … 9

32. Air Traffic Organization (ATO) … 9

33. Flight Standards Service … 10

34. Office of Aviation Medicine … 11

i

35. Office of Airport Safety and Standards … 11

36. Office of the Chief Counsel … 11

37. Assistant Administrator for Security and Hazardous Materials … 11

38. Aircraft Certification Service … 11

39. Office of Communications … 12

40. Office of International Aviation … 12

41.-59. RESERVED … 12

Chapter 3. Air Traffic and Other Initial Notification and Reporting Responsibilities … 13

60. General … 13

61. FAA Contract Facilities (FCF) … 13

62. Operations Center … 14

63. Notification of Other Operations Centers … 14

64. National Transportation Safety Board (NTSB) … 15

65. Aircraft Accident and Incident Notification and Reporting … 15

66. Completing and Transmitting FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … 18

67. Military Notification to the FAA When the FAA Is Involved In a Military Aircraft Accident … 20

68.-69 RESERVED … 21

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection … 22

70. Determination of Air Traffic Facility Responsible for Final Data Collection … 22

71. Formal Accident File/Package Data Collection … 23

72. Additional Data Collection and Certification Information for Selected Facilities … 27

73. Radar and Computer Data … 28

74. Data Collection Memorandums … 31

75.-79. RESERVED … 31

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files … 32

80. Numbering of Air Traffic Formal Accident File/Package and Informal Accident File … 32

81. Holding and Support Facilities … 32

82. Content, Assembly, and Distribution of Formal Accident Package … 34

ii

83. Certification of the Air Traffic Aircraft Accident Package … 39

84. Informal Accident File Data Collection … 39

85. Review of Formal/Informal Files … 40

86. Changes to the Accident Package After the Package was Released … 40

87.–89. RESERVED … 40

Chapter 6. Preparation of Forms, Personnel Statements, Certification of Data, Voice Recordings, and Transcripts … 41

90. FAA Form 8020-6, Report of Aircraft Accident … 41

91. FAA Form 8020-26, Personnel Statements … 43

92. The Review of Services Memo and the Certification of Extracted Data … 45

93. Copies of Voice Recordings … 45

94. Transcription of Voice Recordings … 48

95. Automated Air Traffic Aircraft Accident Package Program … 52

96. Litigation/Enforcement Replays … 52

97. Production Credits … 53

98.–99. RESERVED … 53

Chapter 7. Retention of Aircraft Accident Files … 54

100. Security of Original Records … 54

101. Retention and Disposal of Aircraft Accident and Aircraft Incident Records … 54

102. Holds Placed on Records … 56

103.–109. RESERVED … 56

Chapter 8. Reporting and Notification Responsibilities for Occurrences … 57

110. General … 57

111. FAA Contract Facilities (FCF) … 57

112. Air Traffic Facility Responsibilities … 57

113. Quality Assurance Group (QAG) Responsibilities … 59

114. Quality Control Group (QCG) Responsibilities … 59

115. Required Data Provided to AFS, Airports Division, or Military in Support of Air Traffic Occurrences … 60

116.-129. RESERVED … 63

iii

Chapter 9. Aircraft Accident Investigation Responsibilities … 64

SECTION I. Office of Accident Investigation and Prevention … 64

130. Office of Accident Investigation and Prevention Responsibilities … 64

131. Regional Flight Standards Division Responsibilities … 64

132. Designation of the FAA IIC … 64

133. Possible Involvement of Navigation Facilities … 64

134. Technical Operations Aviation System Standards Responsibilities … 64

135. Washington Headquarters "Go Team.” … 65

136. Additional Information … 65

137.–139. RESERVED … 65

SECTION II. Air Traffic Services … 66

140. General … 66

141. Air Traffic Accident Representative … 66

142. Air Traffic Accident Representative Responsibilities … 66

143.–149. RESERVED … 67

SECTION III. Technical Operations Services … 68

150. Introduction … 68

151. Scope … 68

152. Overview of Technical Operations Services Activities … 68

153. Responsibilities … 68

154. Aircraft Accident Representative … 70

155. Process … 70

156. Decisions … 71

157. Field Work … 76

158. Documentation … 78

159. Preserving, Copying, and Releasing Reports and Records … 79

160. Field Response for Post Aircraft Accident Data … 79

161.—169. RESERVED … 80

FIG 9-3-1 Aircraft Accident/Incident TOAAR Checklist … 81

FIG 9-3-2 Facility Restoral Checklist for Field Facilities … 83

FIG 9-3-2a Aircraft Accident Summary Checklist for SSC Personnel … 86

iv

FIG 9-3-2b Sample Technical Performance Record … 87

FIG 9-3-3 Aircraft Accident/Incident Package Cover Page … 88

FIG 9-3-4 Technical Operations Services Post-Aircraft Accident Process … 89

SECTION IV. Office of the Chief Counsel … 90

170. General … 90

171. Extent of Legal Participation … 90

172. Additional Information … 90

173.–179. RESERVED … 90

Chapter 10. Public Release of Accident and Incident Information … 91

180. FOIA Request for Aircraft Accident/Incident and Occurrence Documents … 91

181.–189. RESERVED … 92

Appendix A. Forms Used by Air Traffic … A-1

FIG A-1 FAA Form 8020-3, Facility Accident/Incident Notification Record … A-2

FIG A-2 FAA Form 8020-6, Report of Aircraft Accident … A-3

FIG A-3 FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) … A-3

FIG A-4 FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … A-5

FIG A-5 FAA Form 8020-11, Incident Report … A-7

FIG A-6 FAA Form 8020-17, Preliminary Pilot Deviation Report (Page 1) … A-8

FIG A-6 FAA Form 8020-17, Preliminary Pilot Deviation Report (Page 2) … A-9

FIG A-6 FAA Form 8020-17, Preliminary Pilot Deviation Report (Page 3) … A-10

FIG A-6 FAA Form 8020-17, Preliminary Pilot Deviation Report (Page 4) … A-11

FIG A-7 FAA Form 8020-19, Reclassification of Aviation Incident Report … A-12

FIG A-8 FAA Form 8020-21, Preliminary Near Midair Collision Report … A-13

FIG A-8 FAA Form 8020-21, Preliminary Near Midair Collision Report (continued) … A-14

FIG A-8 FAA Form 8020-21, Preliminary Near Midair Collision Report (continued) … A-15

FIG A-9 FAA Form 8020-24, Preliminary Vehicle or Pedestrian Deviation Report … A-166

FIG A-9 FAA Form 8020-24, Preliminary Vehicle or Pedestrian Deviation Report (cont’d) A-17

FIG A-9 FAA Form 8020-24, Preliminary Vehicle or Pedestrian Deviation Report (cont’d) A-17

FIG A-10 FAA Form 8020-26, Personnel Statement … A-19

v

Appendix B. Example of Air Traffic Aircraft Accident Package … B-1

Appendix C. Determination of Air Traffic Facility Responsible for Final Data Collection

Flow Chart … C-1

Appendix D. Cassette Tape and Computer Diskette- Recordable (CD-R) Labeling … D-1

FIG D-1 Examples of Cassette Tape Labeling … D-1

FIG D-2 Examples of CD-R Labeling … D-3

Appendix E. Original Documentation Transfer … E-1

FIG E-1 Example of Original Documentation … E-2

Appendix F. Definitions … F-1

vi

Chapter 1. General

Chapter 1. General

1. Purpose of This Order. This order prescribes FAA ATO procedures and responsibilities for aircraft accident and incident notification, investigation, and reporting.

2. Audience. This order applies to ATO employees and anyone using ATO directives.

3. Where to Find This Order. This notice is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications website at http://www.faa.gov/air_traffic/publications/.

4. What This Order Cancels. FAA Order 8020.16A, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, dated December 27, 2010, including all associated notices, is canceled.

5. Explanation of Changes. This revision:

a. Incorporates editorial changes.

b. Reflects recent organizational and procedural changes.

c. Updates ATO procedures related to the collection of documents and other items associated with an aircraft accident or incident and incorporates updated procedures for occurrences.

6. Distribution. This order is intended for all Assistant Administrators, Associate Administrators, and heads of offices and services; division level in the offices of Labor Management Relations, Environment and Energy, Aviation Policy, Planning and Environment; branch level in the offices of Chief Counsel, International Aviation, Communications, Aviation Safety, Aviation Safety Analytical Services, Aviation Safety - Air Traffic Safety Oversight, Rulemaking, Airport Safety, Airports, Security and Hazardous Materials, Accident Investigation and Prevention, Aerospace Medicine; Aircraft Certification Service and Flight Standards Services; Air Traffic Organization Senior Vice Presidents and Vice Presidents, Service Area Directors, Managers, service centers, Flight Service Program Operations Director, and field facilities, National Airspace System (NAS) Transition and Implementation; NAS Operations; and Aviation System Standards; regional division level in Regional and Center Operations, International Aviation, and Communications; regional branch level in Human Resource Management, Certification Directorates, Flight Standards Services, Aerospace Medicine, Technical Operations, Airports, and Security and Hazardous Materials; Aeronautical Center division level in Operations Center, Center Counsel, and Communications; and branch level in Security and Hazardous Materials, Human Resource Management, and FAA Academy; Technical Center division level in Operations Center, Center Counsel, Communications, Security and Hazardous Materials, and Human Resource Management; and a standard distribution to all field offices and facilities.

7. Authority to Change This Order. Authority for future revisions to this order is delegated to the Vice President for Safety and Technical Training, AJI-0. Those organizations with aircraft accident and incident notification, investigation, and reporting responsibilities should submit proposed changes or additions to the ATO Litigation Support Group. Supplemental changes and requests for waivers to program and policies transmitted by this order must receive prior approval through written requests to AJI.

8. Supplements. Supplements to this order must be approved prior to implementation. One copy of each line of business, service center, office, or facility supplement to this order must be sent to the Office of Accident Investigation and Prevention through the ATO Litigation Support Group.

9. Definitions. See appendix F, Definitions, for a complete list of definitions for terms used in this order.

10. Related Publications. The following publications are the primary references to be used in coordination with provisions of this order:

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

b. FAA Order JO 7210.3, Facility Operation and Administration

c. FAA Order JO 7210.632, Air Traffic Organization Occurrence Reporting

d. FAA Order JO 1030.3, Initial Event Response

e. FAA Order JO 7110.65, Air Traffic Control

f. FAA Order JO 7110.10, Flight Services

11. Forms and Reports. Forms used by air traffic facilities for aircraft accident and incident notification, investigation, and reporting are in appendix A, Forms Used by Air Traffic. Selected, completed examples of these forms are in appendix B, Example of Air Traffic Aircraft Accident Package.

12. Safety Risk Management (SRM) Analysis. This order has no effect on the NAS.

13. FAA Responsibilities in Aircraft Accident Investigations. The responsibilities of the FAA pertinent to aircraft accident investigations in accordance with Sections 40113 and 44702 of title 49 United States Code (U.S.C.) are to:

a. Ensure that all facts, conditions, and circumstances leading to the accident are recorded and evaluated, and action is taken to prevent similar accidents.

b. Promulgate and enforce Federal Aviation Regulations for certificating civil aircraft airworthiness, for certificating airmen and air carriers for competency, and for certifying airports used by air carriers utilizing aircraft with more than 30 passenger seats for compliance with

Chapter 1. General › 14.

certain safety standards. This responsibility includes the continued surveillance of the airworthiness of aircraft and competence of airmen, air agencies, commercial operators, and air carriers, and the safety of airports.

c. Support the National Transportation Safety Board (NTSB) by verbally informing the office with jurisdictional accident investigation responsibility of all facts, conditions, and circumstances surrounding an accident in which the NTSB does not participate on scene. The FAA investigator-in-charge (IIC) will provide the NTSB with photographs, statements, and other pertinent information necessary for determining probable cause. The exception is that a written statement about a particular segment of the investigation; that is, an engine teardown, can be provided to the NTSB.

d. Participate in any civil aircraft accident investigation or any accident investigation conducted by the NTSB that involves both civil and military aircraft so that the Administrator may properly discharge his or her duties and responsibilities in accordance with title 49 U.S.C.

(1) In the case of accidents that involve only military aircraft and when functions of the FAA are or may be involved, the military authorities will provide for investigation participation by the Administrator.

(2) The Armed Forces have developed a joint regulation by mutual agreement to implement title 49 U.S.C. (See Air Force Regulation AFJI91-206, Army Regulation 95-30, Operations Navy Instruction 3750.16B, Coast Guard Regulation 307, and Chapter 7).

e. Participate with the NTSB in foreign accident investigations upon request by the State of accident occurrence. International Civil Aviation Organization (ICAO) Annex 13, Aircraft Accident Investigation, provides that such investigations must be conducted by authorities of the State in which an accident occurs. Title 49 Code of Federal Regulations (CFR) 831.2(a) excludes the investigation and reporting of aircraft accidents in foreign countries.

f. Notify the NTSB, through the FAA IIC, when the NTSB does not participate in the onscene investigation prior to authorizing NTSB funds.

g. Conduct autopsies and tests of the remains of persons aboard the aircraft at the time of the accident under authority delegated by the Administrator to any medically qualified official or medically qualified FAA employee. Designated aviation medical examiners are not deemed to be FAA officials or employees for this purpose.

14. Responsibilities of Regional Divisions, Aircraft Certification Directorates, Service Areas, Service Centers, Flight Service Program Offices, and the ATO Litigation Support Group in Aircraft Accident Investigations.

a. Regional personnel in Flight Standards, Airports, Aviation Medicine, and Civil Aviation Security Divisions, the Aircraft Certification Directorates, Regional Counsel, and Public Affairs staff may be required to participate in an accident investigation. During such participation, a representative is designated to coordinate the division, directorate, or staff responsibilities and provide assistance and required reports to the FAA IIC.

Chapter 1. General › 15. FAA and NTSB Accident and Incident Investigation Agreements.

b. Service area, service center, and Flight Service Program Office (FSPO) personnel in air traffic and technical operations may be required to participate in an accident investigation. During such participation, a representative is designated to coordinate the service area, service center, Flight Services Information Area Group (FSIAG), directorate, or staff responsibilities and provide assistance and required reports to the FAA IIC.

c. The ATO Litigation Support Group directs data collection and retention for aircraft accidents and incidents and occurrences in the ATO. The ATO Litigation Support Group orchestrates and communicates requirements with Air Traffic Services, ATO Safety and Technical Training, and other offices within and outside the ATO. This Order recognizes the priority of on-going air traffic services, overlapping requirements of participants during investigations, and the need for collaboration. In situations not addressed by this Order, the ATO Litigation Support Group provides direction.

15. FAA and NTSB Accident and Incident Investigation Agreements.

a. FAA and NTSB have agreed that the following apply when NTSB conducts an investigation:

(1) The investigation is under the control and direction of the NTSB IIC.

(2) The FAA must at all times have a coordinator (FAA IIC) designated as its principal representative until the investigation is complete. The designation of a person as FAA IIC conveys the authority to procure and utilize the services of all needed FAA personnel, facilities, and records. Through this principal representative, the NTSB will make available to the FAA all documents, reports, and other evidence from the investigation and any tentative recommendations so that the FAA may immediately take the necessary corrective actions.

(3) Participation of other FAA personnel must be determined by the FAA IIC. The FAA IIC must work with the NTSB IIC in coordinating FAA's activities.

(4) FAA personnel assigned to a group must work under the direction of the group chairperson and remain with the group until that phase of the investigation has been completed or they are released by the NTSB IIC and the FAA IIC.

(5) The NTSB IIC must inform the FAA IIC of all aspects of the investigation.

(6) Pertinent investigation records and reports must be made available to the FAA in a timely manner.

b. Additional facts needed by FAA, but not required by NTSB, must be obtained by the FAA IIC in coordination with the NTSB IIC in a manner that does not interfere with the NTSB investigation. In obtaining such facts, FAA personnel must clarify that they are not acting under NTSB direction.

c. The NTSB must investigate all accidents and incidents involving FAA aircraft or airmen. An FAA aircraft is defined as any aircraft which is owned, leased, under military bailment, rented by the FAA, or piloted by FAA personnel when in an official FAA capacity. The FAA must participate in the NTSB investigation of FAA aircraft accidents and incidents in the same manner as in the NTSB investigation of civil aircraft accidents and incidents.

d. The FAA must investigate all accidents and incidents involving aircraft piloted by NTSB personnel.

e. FAA procedures for participation in NTSB incident investigations will be the same as for accident investigations.

16. Post-Accident or Incident Drug Testing. Post-accident drug testing must be conducted in accordance with current Department of Transportation (DOT) and FAA directives.

17. FAA Investigator-in-Charge (IIC). The FAA IIC directs and controls all FAA participation in the investigation until the investigation is completed. FAA activity at hearings and depositions, however, is under the direction and control of the Office of the Chief Counsel. The FAA IIC reports to AVP-1 through the Manager, Accident Investigation Division. (NTSB and the military service use the term "FAA coordinator" during NTSB or military serviceconducted investigations.)

18. FAA Participants.

a. Participants are responsible to the FAA IIC in all matters related to the function(s) assigned by and/or agreed to by the FAA IIC. FAA participants must not withdraw from the investigation (if assigned to a group) until that phase of the investigation has been completed or they are released by the NTSB IIC and the FAA IIC. Participants must submit reports if requested by the FAA IIC.

b. Participants may provide information or reports only to members of the investigative team and appropriate FAA management. The FAA IIC must be made aware of the nature and content of this information.

c. Personnel that represent an FAA office that has been authorized access to the accident scene but have not been assigned as participants are subject to the requirements of paragraphs 18a and 18b. These personnel must provide the FAA IIC with reproducible copies of all investigation reports which they prepare or receive.

d. Event Investigation Manager (EIM). A specially trained ATO Safety and Technical Training employee appointed by the Vice President of ATO Safety and Technical Training to oversee, manage and serve as the primary contact for all field aspects of a significant event review. The EIM is the focal point for event response activities and directs the Event Review Team members. Until EIM selection, the EIM Team Lead (supervisor) may attend to EIM responsibilities and activities.

19. Other FAA Personnel. FAA personnel not specifically assigned as participants or support personnel must not be present at the scene of an accident or incident without knowledge and consent of the FAA IIC.

20. FAA Safety Recommendation Program. The main purpose of accident and incident investigation is prevention. The FAA Safety Recommendation Program is the process utilized to identify and correct safety deficiencies in the NAS. For more information regarding the responsibilities of FAA personnel, recommendation procedures, and corrective actions, see FAA Order 8020.11.

Chapter 1. General › 22.-29. RESERVED

21. Training. The following courses offered at the Transportation Safety Institute (TSI), Mike Monroney Aeronautical Center, Oklahoma City, Oklahoma, are the recommended training requirements for FAA personnel who are designated to participate in accident or incident investigations:

a. Basic Aircraft Accident Investigation, Course 00035

b. Advanced Aircraft Accident Investigation, Course 00003

c. Basic Rotorcraft Accident Investigation, Course 00007

d. Human Factors in Aircraft Accident Investigation, Course 00008

e. Aircraft Cabin Safety Investigation, Course 00379

22.-29. RESERVED

Chapter 2. › 30. Office of Accident Investigation and Prevention.

Chapter 2. FAA Elements Involved in Notification, Investigation, and Reporting

30. Office of Accident Investigation and Prevention.

a. Director of Accident Investigation and Prevention. The overall mission of the Office of Accident Investigation and Prevention is accomplished under the Director who:

(1) Serves as focal point for the Administrator in coordinating with public, private, military, domestic, and international counterparts, and with representatives of accident and incident investigation interests, on those matters under the direct purview of the office.

(2) Reviews and assesses safety programs, operational policies, and activities as they relate to accident and incident investigations and makes recommendations.

(3) Apprises the associate administrators, regions, centers, and other FAA elements on safety issues and programs related to accident and incident investigation findings and analyses.

(4) Coordinates with the Office of the Chief Counsel (AGC) on participation in NTSB hearings.

b. Accident Investigation Division. The Division:

(1) Provides the FAA IIC for NTSB accident and incident investigations and provides specialized technical support to NTSB working groups, as necessary, by arranging for the assignment of headquarters or field specialists.

(2) Conducts independent FAA investigations, as required, in major air carrier accidents or incidents; accidents associated with FAA licensed commercial space activities; significant commuter, air taxi, or general aviation accidents or incidents which reflect a lack of safety consciousness; and accidents and incidents that are catastrophic or involve recurring safety problems.

(3) Conducts investigations of selected occurrences.

(4) Conducts, at the request of the Director, Special Aviation Safety Investigations.

(5) Serves, on behalf of the Director, as the primary FAA office for NTSB interaction.

(6) Provides the FAA spokesperson at all NTSB public hearings.

(7) Serves as the accident and incident investigation liaison with other FAA elements, U.S. departments and agencies, the U.S. military offices, foreign governments, and the aviation industry.

(8) Reports to the Director and appropriate FAA officials the facts, conditions, and circumstances of accidents and incidents investigated, the apparent causes, and the relationships of those findings to FAA safety programs, regulations, and responsibilities.

(9) Identifies safety issues and corrective action issues that arise from accident and incident investigations which will reduce the likelihood of recurrence and will enhance air safety.

(10) Develops and monitors a system for disseminating within FAA factual information identified as a result of accident and incident investigations.

(11) Assesses techniques and methods of accident and incident investigation and prescribes accident and incident investigation policies, practices, and procedures.

(12) Maintains a duty roster of the 24-hour Office of Accident Investigation and Prevention duty officer for purposes of coordination and notification.

(13) Operates the FAA Office of Accident Investigation and Prevention duty room, including management of the automated information-dissemination program and the accident and incident briefing program.

c. Recommendation and Analysis Division. The Division:

(1) Manages, on behalf of the Director, a system for FAA responses to NTSB safety recommendations.

(2) Coordinates with DOT on NTSB safety recommendation status and the automation of the NTSB Safety Recommendation Program.

(3) Manages, on behalf of the Director, a system for FAA responses to FAA safety recommendations.

(4) Manages the Accident Investigation Quality Assurance Program and provides reports, information, and recommendations resulting from the program.

(5) Develops and manages accident and incident reporting programs and furnishes accident and incident information to other FAA elements.

(6) Integrates the Accident/Incident Data System, Service Difficulty Reports, and other operational databases into accident and incident analysis functions in support of specific investigations or trends analysis.

(7) Conducts analyses of air carrier and general aviation accident and incident data to identify trends and safety deficiencies.

(8) Serves as the program manager to provide support and curriculum guidance to TSI's Aircraft Accident Investigation courses.

(9) Provides analytical and research support for litigation for the Office of the Chief Counsel.

32. Air Traffic Organization (ATO). › c. Aviation System Standards.

(10) Serves as the focal point for NTSB requests other than on-scene requests.

31. Operations Centers. Operations centers alert appropriate offices and assist in the notification process for aircraft accidents and incidents and FAA licensed commercial space activities. When requested, a center establishes communication conferences to obtain, analyze, and disseminate information on accidents and incidents so that all FAA levels are kept informed and decision-making can proceed in a timely manner. Refer to FAA Order JO 1030.3 for appropriate notification procedures.

32. Air Traffic Organization (ATO).

a. Safety and Technical Training, System Operations Services, Acquisition and Business Services, Air Traffic Services. The ATO participates in the investigation of aircraft accidents and incidents when FAA air traffic control or aeronautical communications or navigation facilities are involved. For all significant accident and incidents the ATO Safety Compliance Services Group (CSG) will serve as the Lead ATO Representative and is responsible for ensuring that accidents and incidents that involve the Air Traffic Organization facilities or functions are investigated and reported in a timely manner that ensures the proper discharge of FAA responsibilities. These same requirements pertain to private, non-Federal facilities. If a facility is operating within the NAS, it must comply with the same rules and regulations as the Federal facility.

b. Technical Operations Services. Technical Operations Services responsibilities and actions following an aircraft accident or incident are to ensure the continued safe operation of the NAS, investigate potentially involved facilities in a timely manner, restore operations of facilities removed from service, and provide appropriate accident-related facility documentation.

c. Aviation System Standards.

(1) The Director of Aviation System Standards must ensure that the appropriate Aviation System Standards elements assign personnel to participate in the investigation of accidents and incidents that involve FAA aircraft. The purpose for this participation is to identify noncompliance with and/or inadequacies in FAA standards, policies, and supervision related to the operation and maintenance of FAA aircraft. Additional investigative guidelines are in the latest edition of FAA Order 4040.9, FAA Aircraft Management Program. Aviation System Standards personnel must report the findings and recommendations to their assigning element. A copy of their report will also be given to the FAA IIC. A verbal report summary and any recommendations will be made to the FAA IIC as soon as possible.

(2) Aviation System Standards must:

(a) At the request of the NTSB, FAA IIC/Coordinator (AVS), the FAA Accident Investigation Division, National Technical Operations Aircraft Accident Representative (NTOAAR) or Technical Operations Services Aircraft Accident Representative (TOAAR), schedule a flight inspection of facilities after an accident or incident.

32. Air Traffic Organization (ATO). › b. Flight Standards District Office (FSDO).

(b) Provide flight inspection results to the FAA IIC or TOAAR.

d. ATO Safety, Runway Safety Group. The Runway Safety Group is responsible for evaluating all surface incident reports and making a determination as to whether or not the incident meets runway incursion or runway excursion criteria. Additionally, the Runway Safety Group tracks and maintains all runway incursion data in the Runway Safety Group database.

33. Flight Standards Service. Flight Standards Service participates in the investigation of aircraft accidents and incidents through the Regional Flight Standards Divisions and the Flight Standards District Offices (FSDO).

a. Regional Flight Standards Division.

(1) The manager of the Regional Flight Standards Division is responsible for ensuring that aircraft accidents and incidents that occur in the division's geographical area are investigated and reported to ensure the proper discharge of FAA responsibilities.

(2) When an aircraft accident or incident occurs in one region's geographical area, but the aircraft continues flight to/through the airspace of another FAA region prior to flight termination, the Flight Standards division in the region when the aircraft first lands following the occurrence, is responsible for ensuring the accomplishment of FAA responsibilities, except for pilot deviations.

(3) The Flight Standards Division Manager also must:

(a) Determine which accident or incident report files are required and where they should be located to fulfill the division's responsibility.

(b) Include estimates for investigation costs in the annual budgetary "call for estimates."

(c) Submit quarterly reports to Acquisition and Business Services, Information Technology, Technical Services on the Mandatory Occurrence Reports (MOR) and Electronic Occurrence Reports (EOR) received in the preceding quarters, the status of those reports, and the status of reports open at the beginning of the preceding quarter.

b. Flight Standards District Office (FSDO).

(1) The FSDO responsible for the geographical location of an accident or incident is responsible for investigating and reporting such accidents or incidents as assigned by the manager of the Regional Flight Standards Division (see paragraph 33a(2) on multiple region investigation responsibility).

(2) The type of response for accident and incident investigations will vary by type of occurrence and other factors, from delaying departure to the following day to initiating a major investigation immediately.

c. Aviation Data Systems Branch. The Aviation Data Systems Branch serves as the FAA focal point for the receipt and encoding of general aviation and air carrier accident and incident

reports. The Aviation Data Systems Branch also serves as the office of primary interest for the accident/incident data system. Reports/incidents which meet runway incursion criteria are analyzed and tracked by the Runway Safety Group, and maintained in its database.

33. Office of Aviation Medicine. The Office of Aviation Medicine provides the expertise to support FAA in the investigation of medical aspects of aircraft accidents. Their purpose is to provide support in the area of accident causation related to pilot incapacitation and also in the area of "crash injury" analysis. The Office of Aviation Medicine will continue to provide pathological and toxicological services to the NTSB without reimbursement in accordance with the existing Memorandum of Agreement between the FAA and the NTSB.

34. Office of Airport Safety and Standards. The Office of Airport Safety and Standards participates in aircraft accident and incident investigations when airport functions are involved. The regional Airports division is responsible for the investigation and completion of reports (FAA Form 8020-25, Investigation of Vehicle or Pedestrian Deviation Report) on all vehicle and pedestrian deviations at airports certificated under title 14 CFR Part 139. The Regional Airports Division Manager must submit quarterly reports to Acquisition and Business Services, Information Technology, Technical Services on the Mandatory Occurrence Reports (MOR) and Electronic Occurrence Reports (EOR) received in the preceding quarter, the status of those reports, and the status of reports open at the beginning of the preceding quarter.

35. Office of the Chief Counsel. The Office of the Chief Counsel is responsible for all legal services required for FAA functions involved in the investigation of aircraft accidents and incidents and FAA licensed commercial space activities. The legal representative is responsible for all legal services required for FAA functions involved in the investigation of the types of aircraft accidents and incidents in FAA Order 8020.11, Chapter 3, Section 5.

36. Assistant Administrator for Security and Hazardous Materials. The Assistant Administrator for Security and Hazardous Materials provides specialized technical and investigative assistance for enforcement or referral action for aircraft accidents and incidents and FAA licensed commercial space activities that directly involve hazardous material, atmospheric/radiological material, etiological contamination, or criminal activity. Examples include hijacking, sabotage, explosive incidents, forged certificates, drug trafficking, false markings, and alien smuggling. Office personnel may also provide assistance in such matters as certification of security clearances, preparation of identification media, handling of classified information, and other matters.

37. Aircraft Certification Service. Aircraft Certification Service is responsible for the safety of civil aircraft. This organization consists of the headquarters policy office and four special policy offices called "directorates." Each directorate is responsible for policy under Federal Aviation Regulations covering a particular category of aircraft or aeronautical part. The four directorates serve as "geographical directorates" and are responsible for all of the field offices within a geographical area. The field offices are responsible for:

a. Issuing product-type certificates and other design approvals held by manufacturers in the responsible geographic area.

Chapter 2. › 41.-59. RESERVED

b. Providing engineering specialists to assist in the investigation of aircraft accidents and incidents that raise questions of product design.

c. Developing design-related corrective actions.

38. Office of Communications. The Office of Communications and/or the appropriate regional/center communications staff respond to news media inquiries on FAA functions and responsibilities associated with an aircraft accident or incident or FAA licensed commercial space activity until the NTSB investigation team arrives at the scene. The NTSB becomes responsible for answering all media questions related to the accident itself, circumstances surrounding the accident, and its probable cause. For FAA investigations, media response is the responsibility of the headquarters Communications staff.

39. Office of International Aviation. The Office of International Aviation maintains a current list of countries to which the Department of State will not normally authorize travel by accident investigators unless explicit approval is first obtained from the Office of Aviation, Department of State. Also, when the FAA Accident Investigation Division indicates interest in a foreign accident investigation in which the FAA is not entitled to participate under the Chicago Convention, the geographically responsible FAA International Representative will, with the local U.S. embassy, attempt to secure an invitation for FAA participation from the civil aviation authority of the crash-scene country.

41.-59. RESERVED

Chapter 3.

Chapter 3. Air Traffic and Other Initial Notification and Reporting Responsibilities

60. General. In order to provide authorities in the FAA, NTSB, or military services with information on aircraft accidents and incidents, follow notification procedures as outlined in this chapter.

a. Any FAA or FAA contract facility (FCF) employee who becomes aware of an aircraft accident or incident must report the facts immediately to the nearest FAA air traffic facility (en route, terminal facility, flight service station), or Regional Operations Center (ROC).

b. To report an aircraft accident or incident when you do not have ready access to an FAA air traffic facility or ROC, such as international events, use established channels such as the Department of State, the FAA Aeronautical Fixed Telecommunications Network, or by any expeditious means appropriate to the accident or incident circumstances.

c. For incidents/accidents involving UAS or spacecraft, the notification and reporting shall be accomplished in the same manner as other aircraft accidents/incidents.

d. FAA Form 8020-3, Facility Accident/Incident Notification Record, and FAA Form 8020- 9, Aircraft Accident/Incident Preliminary Notice, are to be used by air traffic facilities to initiate preliminary notification of aircraft accidents and aircraft incidents. If requested by the FSDO, the ATO Litigation Support Group, service center, Flight Service Program Office, or ATO Safety Compliance Services Group, FAA Form 8020-11, Incident Report will also be completed for selected aircraft incidents.

61. FAA Contract Facilities (FCF). Unless otherwise indicated in the following paragraphs or specifically directed by the FAA Accident Investigation Division, the FAA IIC, or the ATO Litigation Support Group, in complying with this order, FCFs must follow the same procedures as those outlined for FAA air traffic facilities. This includes, but is not limited to, the preparation and retention of a formal or informal aircraft accident file. The FCF must not forward their formal or informal aircraft accident files, documents, information, notes, recordings, and/or copies of voice data, etc., concerning an aircraft accident or incident to the FAA, except as outlined in this order (see paragraph 71c) JO 7210.633 and JO 1030.3.

Throughout this Order, if the type of facility is preceded by the acronym “FAA,” then the guidance being provided is to be applied to FAA facilities only. If the acronym “FAA” is not present, then the guidance being provided is to be applied to all facilities (that is, FAA and FCF).

EXAMPLES:

“…the FAA air traffic facility with jurisdiction over the flight when the accident occurred.” (This guidance would apply to FAA facilities only.)

“The air traffic facility first receiving notification of a known accident or a suspected accident must make and record initial notification using FAA Form 8020-3…” (This guidance would apply to all air traffic facilities [that is, FAA and FCF]).

62. Operations Center. When a notification of an aircraft accident or incident is received from any source, the Washington Operations Center (WOC) or ROC operations officer must contact the appropriate offices and representatives for conferences or briefings as necessary. Notification will be conducted following FAA Order JO 1030.3, Initial Event Response.

a. When the reported occurrence is one that requires regional or Washington notification in accordance with paragraph 65, the ROC officer must set up a telephone conference between the appropriate offices and the notifying party.

b. When telephone notification of an occurrence indicates that the use of a navigational aid may have been involved, the ROC officer must confer with the Flight Inspection Central Operations (FICO) and the TOAAR located at the appropriate operations control center (OCC). Also, Aviation System Standards must be included whenever notification is received that an FAA aircraft is involved in an accident or incident.

c. The ROC officer must immediately notify the appropriate Aviation Medical division after receiving a report of a fatal aircraft accident or a report of an in-flight medical incapacitation of a cockpit crewmember.

d. The ROC officer must assist the FAA IIC in establishing conference calls to include the WOC, NTSB, manufacturers, ATO Compliance Services Group, TOAAR, Office of Airport Safety and Standards, Civil Aerospace Medical Institute, Aircraft Certification Directorates, and FAA William J. Hughes Technical Center, as necessary.

e. The WOC Operations Officer compiles all the accident and incident messages received each day for the Accident Investigation Division Duty Room. Each working day, the FAA Accident Investigation Division electronic copies to the Aviation Data Systems Branch a list of accidents derived from the WOC compilation.

f. The ROC officer must immediately notify the appropriate Regional Airports Division of accidents and incidents in their region.

g. The WOC must notify the Environment, Energy, and Employee Safety Division within four hours of all incidents covered by Occupational Safety and Health Administration (OSHA) reporting requirements. These incidents include FAA fatalities and/or when three or more FAA employees are involved in an accident and hospitalized on an in-patient basis.

62. Notification of Other Operations Centers. Each ROC officer must provide information to other ROCs and/or the WOC when events occurring in the ROC officer's area of responsibility may be of concern to other regions or centers. These events include:

a. Accidents or incidents in which the aircraft operator's operating certificate is held by another region or in which another region has the certification responsibility for that aircraft.

b. Accidents or suspected accidents (overdue and missing aircraft) of aircraft that are carrying prominent persons from another region.

c. Accidents involving injuries or death of FAA personnel from another region.

Chapter 3. › 63. National Transportation Safety Board (NTSB).

d. Any other occurrences which, in the opinion of the Regional or WOC Operations Officer, are of official interest.

63. National Transportation Safety Board (NTSB).

a. The NTSB will notify the FAA immediately when it receives notification of an aircraft accident or incident from a non-FAA source.

b. If the NTSB intends to investigate the accident or incident, it will inform the FAA. The FAA will provide the FAA IIC's name, location, contact point, etc., to the NTSB.

c. Any NTSB requests and replies must be kept in the air traffic aircraft accident or incident file.

64. Aircraft Accident and Incident Notification and Reporting. The definition of an aircraft accident is in appendix F. This paragraph is divided into three categories for aircraft accidents and incidents: what to report, how to report, and when to report.

a. What to Report. Air traffic facilities must report:

(1) All known and suspected accidents (including unmanned aircraft systems, spacecraft or military). An example of a suspected accident is the simultaneous unexplained loss of radio communications and radar contact with an aircraft.

(2) Accidents involving aircraft that departed a foreign country and whose first point of intended landing was in the United States or aircraft that departed the United States for a foreign country. For such accidents:

(a) The completion of FAA Form 8020-3 (see paragraph 65b) and FAA Form 8020- 9 (see paragraph 66) must conclude the initial notification procedures.

(b) If the aircraft accident occurs within the jurisdiction of the United States or while receiving services by an air traffic facility, prepare a formal accident file in accordance with chapters 4 through chapter 7.

(3) All aircraft incidents, selected criminal acts reported to or by law enforcement agencies, emergency evacuations of aircraft, in-flight major component failures, and any incident that threatened or caused damage or injury to property, aircraft, or persons.

(4) The following special-emphasis accidents/incidents:

(a) Accidents/Incidents involving Presidential or Vice Presidential aircraft, members of Congress, or well-known people. Secure communications will be used in reporting whenever either of the first two individuals is on board the aircraft.

(b) Accidents/Incidents in which hazardous materials are being transported.

(c) Accidents/Incidents involving U.S.-manufactured aircraft of foreign registry which occur outside the United States, its territories, and possessions.

(d) Other accidents/incidents which the reporting facility or FSDO personnel believe warrant telephone notification to the ROC. The ROC in turn will notify the Service Center Quality Control Group (QCG), WOC, ATO Safety Compliance Services Group, and Flight Service Program Office (FSPO).

(5) Overdue and missing aircraft when:

(a) Neither communication nor radar contact can be established and 30 minutes have passed since its estimated time of arrival over a specified or compulsory reporting point or at a clearance limit in your area, or its clearance void time. If you have reason to believe that an aircraft is overdue prior to 30 minutes, take the appropriate action immediately.

(b) Information is received that search and rescue procedures have commenced for an aircraft that is not on a flight plan.

b. How to Report. Any air traffic facility first receiving notification of a known or suspected accident/incident must:

(1) Notify the ROC (see paragraph 65c).

(2) Record notifications on FAA Form 8020-3 (also handwrite notifications not listed on the form) (see appendix A on how to maintain form(s); see appendix B for accident package examples).

(3) Complete and transmit FAA Form 8020-9 (see paragraph 66).

(4) Make reference on FAA Form 7230-4 via Comprehensive Electronic Data Analysis and Reporting (CEDAR) program or other means. (If the incident is noteworthy or significant immediately notify ATO Safety Compliance Service Group and the WOC through the ROC by telephone IAW FAA Order 1030.3.) Also make reference to any associated MORs if applicable.

(5) Notify the nearest National Weather Service (NWS) or forecast center if known or suspected accidents resulted (or is deemed likely to have resulted) in serious injury or death to persons or substantial damage to aircraft/property. Initial notification is based on preliminary information. (A letter of agreement between the respective Service Area and the NWS may dictate different notification processes.)

(6) Notify Technical Operations or other appropriate personnel to retain pertinent data having a retention cycle of less than 15 days. (For example, ERAM workstation playback files must be retained within 24 hours.)

There may be more than one FAA Form 8020-3 for an aircraft accident/incident. The air traffic facility having jurisdiction over the accident site, if different from the facility receiving initial notification, must also complete FAA Form 8020-3. Managers must ensure that copies of FAA Form 8020-3 with telephone numbers inserted are available, current and updated annually.

63. National Transportation Safety Board (NTSB). › c. When to Report.

All air traffic facilities (except FSSs) having geographical jurisdiction over an airport that is supported by an air traffic facility and/or has a published instrument approach, must develop and maintain a current FAA Form 8020-3 for each such airport. FAA Form 8020-3 is not required for private airports not meeting the above criteria. Those facilities having part-time jurisdiction over airspace designated to another facility must develop a separate FAA Form 8020-3 for each such facility.

c. When to Report.

(1) Overdue and missing aircraft.

(a) Air traffic facilities must immediately notify the ROC by telephone in accordance with FAA Order 1030.3. The ROC in turn notifies the WOC, ATO Safety Compliance Services Group, the Service Center Quality Control Group (QCG), and Flight Service Program Office (FSPO). The QCG helps facilitate ATO search and rescue activities.

(b) Issue an alert notice (ALNOT) in accordance with FAA orders.

(2) Air traffic facilities must immediately notify the ROC by telephone of any known and suspected aircraft accidents/incidents involving air carrier, air taxi, or commuter aircraft; and/or involving aircraft operating under instrument flight rules (IFR) or special visual flight rules (SVFR).

(3) Air traffic facilities must immediately notify the ROC by telephone of any of the following:

(a) Criminal acts reported to or by law enforcement agencies.

(b) Emergency evacuations of aircraft.

(c) In-flight component failure.

(d) Accidents/incidents involving Presidential or Vice-Presidential aircraft (secure communications will be used in reporting).

(e) Members of Congress, or other well-known people (secure communications will be used in reporting whenever members of congress are on board the aircraft).

(f) Accidents/incidents in which hazardous materials are being transported.

(4) For all other accidents/incidents, the determination of whether the ATO Safety Compliance Services Group notification is necessary or required must be based on the significance and the level of air traffic service (if any) which was being provided to the aircraft, including weather-related accidents/incidents when a weather briefing was provided within 24 hours of the accident/incident. For all other accidents/incidents, air traffic facilities must immediately notify the ROC by telephone when they determine the significance and/or level of air traffic service requires notification.

63. National Transportation Safety Board (NTSB). › b. Transmitting Form Data (Preliminary Message).

(a) The significance of an accident/incident is covered in FAA Order 1030.3, Initial Event Response. Although not all-inclusive, examples of significant accidents/incidents are selected criminal acts, emergency evacuations of aircraft, and in-flight major component failures.

(b) The level of air traffic service is used to denote the amount and complexity of service being provided. Determine the "amount of complexity" based on the best assessment of the appropriate service center, or FSPO in consultation with the facility. Although not allinclusive, an example of minimum service may be a visual flight rules (VFR) arrival or departure to or from an airport in Class D airspace. A higher level of service may be separation, sequencing, and/or vectoring to a VFR aircraft within Class B airspace.

65. Completing and Transmitting FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice. Immediately after completing telephone notification using FAA Form 8020-3, the reporting air traffic facility must compile the required information, complete FAA Form 8020-9, and transmit it.

a. Completing FAA Form 8020-9.

(1) Complete Part 1 of FAA Form 8020-9 for all known or suspected accidents/incidents. If the aircraft involved is owned or operated by the FAA, flown by FAA personnel on official duty, or utilized by FAA inspectors performing flight tests then include “FAA” in Code B3, OPERATOR OF AIRCRAFT.

(2) Complete Part 2 of FAA Form 8020-9 when radio navigational aids, communications equipment, radar-automated systems, or approach lights may have been or were involved. Notify appropriate Technical Operations personnel of the facilities potentially involved and use data provided by them to complete FAA Form 8020-9, Part 2.

(3) Enter “unknown” for any item unavailable when the form is prepared.

(4) Complete FAA Form 8020-9, Item F. If the name of the FAA IIC is unknown the offices notified should be indicated (i.e., SW-FSDO-65)

b. Transmitting Form Data (Preliminary Message).

(1) The air traffic facility must transmit FAA Form 8020-9, Parts 1 and 2, as appropriate, within 3 hours of the detection of the known or suspected accident/incident to the ROC via fax or email. Suspected accident/incidents include the abandonment of a search for an overdue/missing aircraft that cannot be located. The form will then be forwarded, as necessary, to:

(a) FAA, Washington Operations Center, Washington, D.C. (The WOC will ensure timely notification to the ATO Safety Compliance Services Group on-call investigator.)

(b) NTSB, Washington, D.C.

63. National Transportation Safety Board (NTSB). › c. Transmitting Updates/Amendments.

(c) FAA service center with jurisdiction over the area in which the accident/incident occurred. If the aircraft was under the control of any facility in another service center, other applicable service center(s) must be addressed.

(d) The Headquarters Flight Service Safety and Operations (FSSOPS) or AFSIAG, as appropriate.

(e) Aerospace Medical Research Division, AAM-600, Mike Monroney Aeronautical Center.

(f) U.S. Air Force Rescue Coordination Center (AFRCC), 650 Florida Avenue, Tyndall Air Force Base, Florida, 32403-5017.

(g) El Paso, Texas, Intelligence Center (EPIC).

(h) The appropriate civil aeronautical authority for accidents involving aircraft of Canadian or Mexican registry in accordance with ICAO Annex 13.

(2) Immediately transmit by facsimile, email, or telephone significant accidents/incidents (e.g., involving air carriers, air taxis, commuter, media interest, or prominent persons) to the ROC. The message must follow the format of FAA Form 8020-9, Parts 1 and 2, as appropriate. Also transmit using this format when:

(a) An air traffic facility receives initial notification more than 24 hours after the aircraft accident/incident.

(b) There is an aerial application (agricultural) or industrial accident/incident.

(3) Notify the FSDO and the NTSB field office with jurisdiction over the area in which the accident occurred by telephone, facsimile, or in accordance with a service center agreement. A copy of FAA Form 8020-9 must also be forwarded to the FSDO.

(4) When the facility originating the message is at the same location as one or more of the above offices, immediate delivery of a copy of FAA Form 8020-9 must be made in accordance with local agreements.

(5) The facility originating the message, if not the facility responsible for preparing the accident file as determined in paragraph 70, must forward a copy of FAA Form 8020-9 to the responsible facility. If the responsible facility cannot be determined, the service center must make the determination; notify the responsible facility, and furnish essential information.

(6) When a facility transmits the information from FAA Form 8020-9 for the originating facility, the originating facility must be provided a copy of the transmittal.

c. Transmitting Updates/Amendments.

(1) FAA Form 8020-9 must be updated as new and/or amended information is available. For example, send a subsequent message upon locating aircraft wreckage, to revise

the original message, or to downgrade the accident to an incident. Because FAA Form 8020-9 serves as a worksheet, these amendments may be accomplished by placing a single line through the updated or erroneous information. Then enter the new data. You may also write “Supplemental” at the top of the form to further indicate new and/or amended information, in addition to lining out and replacing the erroneous information. A new form may also be used to transmit updates/amendments. Enter the new or changed information. Include the aircraft identification, accident/incident date, and Item F information.

(2) Fax or email the updated information to the ROC, who will then forward to all recipients of the original message.

66. Military Notification to the FAA When the FAA Is Involved In a Military Aircraft Accident. When a military accident occurs and military authorities determine that a function of the FAA Administrator is or may be involved, the commander or the designated representative at the installation involved will transmit by telephone, via the nearest or most convenient FAA facility, all unclassified information. The military will also deliver a complete and final message to the air traffic facility as soon as possible, normally within 24 hours of the accident. If FAA Form 8020-9 has already been distributed, the FAA facility must send a subsequent message in accordance with paragraph 66c that would include the new information supplied by the military. The information required from the military is:

a. Date and time of accident, both stated in coordinated universal time (UTC).

b. Location of accident scene based on direction and distance from the military base or prominent geographical location, if known; otherwise, latitude and longitude coordinates.

c. Aircraft type, model, and serial number.

d. Unit to which the aircraft was assigned.

e. Point of departure.

f. Type of air traffic clearance.

g. Destination.

h. Last known position in flight and/or radio contact with pilot.

i. Security classification of accident, if applicable.

j. Presence of radioactive or hazardous materials, if applicable.

k. Description of accident.

l. Identity of FAA functions involved.

m. If FAA participation is requested by the military.

n. If other investigations will be conducted.

Chapter 3. › 68.-69 RESERVED

o. Name, telephone number, and address of the military contact.

68.-69 RESERVED

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection

70. Determination of Air Traffic Facility Responsible for Final Data Collection

a. The air traffic facility that meets the following criteria will be responsible for the final air traffic file. This facility is referred to as the “holding” facility. Other facilities that provided air traffic service to the accident/incident aircraft are “supporting” facilities (see paragraph 81). See the Determination of Air Traffic Facility Responsible for Final Data Collection Flow Chart in appendix C for additional information.

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection › 70.

(1) Aircraft on IFR flight plans under the control of an FAA-staffed facility: the FAA air traffic facility with jurisdiction over (i.e., authority for and/or working) the flight when the accident/incident occurred.

(2) Aircraft on IFR flight plans under the control of a military-staffed facility: the ARTCC in whose area the accident/incident occurred. The ARTCC will cooperate with the military by furnishing the required information to the assigned investigator through the air traffic representative (ATREP). The ARTCC must obtain permission to release documents from the ATO Litigation Support Group through the appropriate service center.

(3) Aircraft not on an IFR flight plan but in communication with an FAA facility: the FAA facility having communication with the aircraft when the accident/incident occurred.

(4) Aircraft not in communication with an FAA facility: the last FAA facility having communication with the aircraft.

NOTE: Communication may include two-way radio or telephonic communication with the pilot or inter/intra-facility coordination regarding the flight.

(5) Other Aircraft: the FAA air traffic facility having radar services responsibility for the area in which the accident/incident occurred (at time of occurrence).

(6) Aircraft that have not communicated with an FAA facility, but have communicated exclusively with an FCF: the last FCF having communication with the aircraft for the flight. If more than one vendor is involved, the last FCF having communication with the aircraft for each vendor.

(7) Aircraft that have communicated with both an FAA facility and an FCF:

(a) The last FAA facility having communication with the aircraft for the flight will conduct the final collection of all accident/incident information involving FAA facilities. Except as noted in paragraph 71c, no information from an FCF will be included in the file.

(b) The last FCF facility that communicated with the aircraft will conduct the final collection of all accident/incident information involving FCFs of the same vendor. If more than

one vendor is involved, the last FCF that communicated with the aircraft for each vendor will conduct a final collection. No information from an FAA facility will be included.

b. It is possible and permissible that data collection may vary between FAA and FCFs as conveyed, respectively, by the service center or FSPO after coordination with the ATO Litigation Support Group (see paragraph 71). This Order ascribes to the service centers/FSPO the customary role of communicating data requests to air traffic facilities. For some accidents/incidents, the ATO Litigation Support Group will communicate directly with air traffic facilities once notification has been accomplished with the service center/FSPO.

c. The ATO does not need to establish a file for agricultural, ultralight, balloon, and/or industrial accidents/incidents unless requested by the FAA Accident Investigation Division, the FAA IIC, ATO Litigation Support Group, the service center, or FSPO.

71. Formal Accident File/Package Data Collection. The ATO Litigation Office directs air traffic facilities to produce formal accident files/packages. This assignment of work to facilities may come directly from the ATO Litigation Support Group but is more often communicated through the service center or FSPO.

An accident file/package determination is based on the level of air traffic service provided to the aircraft (including weather-related accidents when a weather briefing was provided within 24 hours of the accident). The phrase “level of air traffic service” denotes the amount and complexity of service provided by air traffic to the accident aircraft. The ATO Litigation Support Group is responsible to determine the level of air traffic service. The determination process will normally flow through the service center, Federal Control Tower Quality Assurance Group, or FSPO. (Routinely, the service center/FSPO will consult with the facility(ies); then the service center/FSPO may consult with the ATO Litigation Support Group.)

Air traffic facilities may be directed to produce informal accident files (no package required for informal files). The assignment of work follows the same process described above. Collect data for an informal file in accordance with paragraph 84.

If a subsequent determination is made by AFS that the occurrence does not meet the definition of an accident or an incident then retain data used in the investigation in accordance with chapter 7, i.e., 45 days.

In cases where no air traffic service was provided to the accident aircraft, yet air traffic became aware of the accident (by police or similar organizations) then air traffic must report the accident in accordance with paragraphs 65 and 66. Retain notification forms and documentation in accordance with paragraph 101.

a. Obtain documentation for a holding facility’s formal accident file/package as follows:

(1) FAA holding facilities are required to gather information from all facilities along the route of flight. This requirement is most often communicated to supporting facilities by the holding facility (see paragraph 70).

(a) AFSIAG - The FSS in whose flight plan area the accident occurs must deliver the request to each Direct User Access Terminal System (DUATS) vendor.

(b) Contract Flight Service Station (FCFSS) – Information regarding possible services provided by an FCFSS will be coordinated through the FSPO as follows: The reporting facility can obtain information about FCFSS services through notification of the ROC (paragraph 65). The ROC will notify the Central Region ROC of the accident and the Central Region ROC will contact the FSPO. (The FCFSS will also query each DUATS vendor for services provided.)

(2) Air traffic facilities (the holding facility and the supporting facilities) along the route of flight must conduct a review of service (see paragraph 81) to assess and gather data. This review must be conducted within two administrative days of notification of an accident/incident. Notify the holding facility of your services status (routine, pertinent, no services but have data, no services/no data). A Review of Services Memo, FAA Form 8020-6-1, and copies of all required data must be forwarded to the holding facility within eight administrative days of notification of the accident/incident.

(3) Request information from military air traffic facilities that provided services and/or have data on the accident aircraft. This may be done through the service center military air traffic representative.

(4) Examples of documentation that must be reviewed and retained are:

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

(b) FAA Form 7230-4, Daily Record of Facility Operation.

(c) Personnel logs.

(d) FAA Form 7230-10, Position Log (or automated equivalent).

(e) Facility layout charts.

(f) Flight progress information and strips if printed.

(g) Radar data.

(h) Pilot reports (PIREP) and weather data (if available, Center Weather Advisories, Weather DART, TAFs, etc.).

(i) Significant Meteorological Information (SIGMET).

(j) Airmen's Meteorological Information (AIRMET).

(k) Notice to Airmen (NOTAM).

(l) FAA Form 7233-1, Flight Plan.

(m) Video maps.

(n) Non-published NOTAMs.

(o) Copies of operations letters, letters of agreement, and facility memoranda.

NOTE: Because the ATO Litigation Support Group continually assesses what pertinent documentation is, based on safety investigations, changes in technology and legal trends, the ATO Litigation Support Group will, at times, require more documentation than the involved facilities gathered. Also, the ATO Litigation Support Group will, at times, reach out to facilities to review the contents of accident files/packages.

b. The holding facility’s formal accident file must contain:

(1) The accident package.

(2) Voice recordings (digital audio tape [DAT], tape reel) and copies made in accordance with paragraph 93.

(3) FAA Form 8020-9 and all other pertinent documents and material gathered or created as part of, or subsequent to, the initial investigation unless specifically excluded by FAA Order JO 8020.16 or via written direction from the ATO Litigation Support Group. Pertinent information, may include, but not be limited to

(a) Charts (for example, minimum vector altitude (MVA), approach plates).

(b) Covered Event Review.

(c) Radar data and computer data (see paragraph 73). When available, radar and audio start/stop timeframes must match.

(d) Letters of agreement.

(e) Facility directives.

(f) Email or other communications containing exchanges of information relevant to the facts of the accident.

c. FAA holding facilities include the FCF supporting facilities original Review of Services Memo and FCF’s FAA Form 8020-6-1 in the FAA air traffic formal accident package. Additionally, FAA holding facilities include in their file (not package) certified working copies of voice recordings and transcripts from FCF supporting facilities that had pertinent services. Normally the transcripts, full or partial as appropriate, are only produced by a supporting facility with pertinent services. No other FCF documents will be retained in the FAA air traffic formal accident package or file without the permission of the ATO Litigation Support Group. Similarly, nothing from an FAA facility or other-vendor FCF will be retained in a FCF formal accident file. (See paragraph 81c for more details on what data supporting facilities submit to the holding facility.)

d. The supporting facility's formal accident file must contain, as applicable:

(1) Supporting facility with pertinent services. (Generally, pertinent services are those that take place after air traffic becomes aware of, or is notified of an unusual, urgent or emergency situation by the flight crew or other sources).

(a) Voice recordings and copies (see paragraph 93).

(b) Radar data and computer data (see paragraph 73).

(c) FAA Form 8020-6-1.

(d) Review of Services Memo.

(e) Transcription of Voice Recording(s).

(f) FAA Form 7230-4.

(g) Personnel Log(s).

(h) FAA Form(s) 7230-10.

(i) Flight Progress Strip(s) and/or In-Flight Contact Record(s).

(j) Weather Products.

(k) And all other pertinent documents and material gathered or created as part of, or subsequent to, the initial investigation unless specifically excluded by FAA Order JO 8020.16, or via written direction from the ATO Litigation Support Group. Pertinent information, may include, but not be limited to charts, covered event review, letters of agreement, facility directives, email or other communications containing exchanges of information relevant to the facts of the accident.

(2) Supporting facility with routine services.

(a) Voice recordings and copies (see paragraph 93).

(b) Radar data and computer data (see paragraph 73).

(c) FAA Form 8020-6-1.

(d) Review of Services Memo.

(e) Flight Progress Strip(s) and/or In-Flight Contact Record(s).

(f) Email or other communications containing exchanges of information relevant to the facts of the accident.

(3) Supporting facility with no services but did have data.

(a) All pertinent data, documentation, and information (for example, radar).

72. › a. FAA FSS Facilities and FCFSS Facilities.

(b) FAA Form 8020-6-1.

(c) Review of Services Memo.

(d) Email or other communications containing exchanges of information relevant to the facts of the accident.

e. The holding and support facility’s formal accident file must be labeled as described in paragraph 101a.

72. Additional Data Collection and Certification Information for Selected Facilities.

a. FAA FSS Facilities and FCFSS Facilities.

(1) FAA FSS and FCFSS facilities will at times be either the holding facility or supporting facility. In either case the following applies. For data required by a FAA FSS/FCFSS for inclusion in a formal accident package or file, or for use in an accident investigation, the facility must obtain an Event Reconstruction (EVR) or Contact History and Briefing History printout from its operating system. The facility must compile and retain all pertinent EVR/Contact and Briefing History data. (This data may be retained electronically.)

(2) Information that may have been pertinent to the flight, but not actually provided to the flight crew or operator, must be obtained and retained separately in the accident file but not as part of the actual accident package.

(3) Certify data. See paragraph 73b and appendix B, Review of Services Memo for examples.

b. Facilities Not Providing ATC Services. When requested by the FAA IIC, the FAA Accident Investigation Division, the ATO Litigation Support Group, ATO Compliance Services Group, , service center, FSPO, or the air traffic facility responsible for final data collection (see paragraph 70), any air traffic facility having any pertinent documentation, audio, radar data, etc., in support of an aircraft accident or incident investigation will retain this documentation in accordance with chapter 7. This only applies to air traffic facilities, which provided no direct or indirect air traffic services to the aircraft in question (i.e., a facility which did not provide air traffic service but did have radar data). Although the air traffic facility will maintain an air traffic formal or informal file, most other documentation as outlined in paragraphs 82 and 84 will not be required. The data must be certified (see paragraph 73b and appendix B, Review of Services Memo for examples).

c. Air Traffic Control System Command Center (ATCSCC). When it has been determined by the FAA IIC, the ATO Litigation Support Group, ATO Compliance Services Group, the service center, or FSPO that the ATCSCC may have information pertinent to an accident or incident, the ATCSCC will be requested to retain data, documentation, and/or copies of recordings in accordance with this order and local directives.

(1) The ATCSCC must provide data, documentation, and/or copies of recordings as outlined in this order.

72. › a. Data Collection.

(2) Certify data. See paragraph 73b and appendix B, Review of Services Memo for examples.

(3) Retain an accident file (see paragraph 101).

d. Domestic Events Network (DEN). When it has been determined by the FAA IIC, the ATO Litigation Support Group, , ATO Compliance Services Group, the service center, or FSPO that the DEN may have information pertinent to an accident or incident, the DEN will be requested to retain data, documentation, and/or copies of recordings when coordinated with the ATO Litigation Support Group.

(1) The DEN must provide data, documentation, and/or copies of recordings as outlined in this order.

(2) Certify data. See paragraph 73b and appendix B, Review of Services Memo for examples.

(3) Retain an accident file (see paragraph 101).

73. Radar and Computer Data. This paragraph makes a distinction between data retention and data extraction. Retained data is data as close to the original state as possible (e.g., in the HOST system, taking a DSR tape out of its retention cycle and saving it in the accident file is retention or retained data). Retained data gives the ATO the ability to produce Litigation/Enforcement replays after the normal retention time for the data has past. In contrast, extracted data is data taken from the retained data (e.g., in the HOST system extracting a DART or NTAP job from the retained data). Litigation/Enforcement replays from retained/extracted data are generally made if the need arises (e.g., for investigations, litigation), rather than producing Litigation/Enforcement replays for every aircraft accident/incident. Litigation/Enforcement replays and other productions must be documented in accordance with Paragraph 97.

a. Data Collection.

(1) For aircraft accidents/incidents or suspected aircraft accidents/incidents, pertinent computer data must be retained and/or extracted onto an electronic storage media (for example, diskette, CD+R, DVD, etc.). After extraction, the data must be reviewed to ensure the completeness and accuracy of the transferred data onto the electronic storage media.

(2) To preserve original computer data from possible damage, arrangements must be made to protect, copy or reproduce all pertinent data as soon as possible after an accident/incident. Copied/reproduced data must reflect the same time period as all copies of recordings pertinent to the accident/incident and/or pertinent captured data of the accident/incident.

(3) Radar and Automation data must be retained in sufficient quantity in order to be able to reasonably recreate the event on the automation platform that recorded the data. In order to do that, facilities must retain data as follows:

(a) STARS – Retain the adaptation file in use at the time of the accident. Retain CDR data taken from the STARS Data Reduction and Analysis Tool (DR&A) required to replay the event on a STARS Terminal Controller Workstation display. Keep a report/memo listing software build and adaptation version in use when the CDR data was recorded. If necessary for a replay, extract a Plot Playback File with the Exercise Filter set only to Operational Data for the time period associated with the accident/incident.

(b) Common Automated Radar Terminal System (CARTS) – Retain the adaptation file in use at the time of the accident and the CDR Time Selected Output (CDTSO) so that the data can be replayed on the CARTS RETRACK system. Keep a report/memo listing the software build and adaptation version in use when the CDR data was recorded. If necessary for a replay, extract a CDR Extraction with the following data classes: Tracking Associated (TA), Tracking Unassociated (TU), Target Reports (TG), and CDR Recorded Dump (CR) for the same time period associated with the accident/incident.

(c) HOST – Retain the adaptation file in use at the time of the accident, and SAR Tapes, LCN and BCN (DSR Tapes). Keep a report/memo listing the release software build and adaptation version in use when the HOST data was recorded. If necessary for a replay, extract the files required to prepare a SATORI for the same time period associated with the accident/incident.

(d) ERAM – Retain the adaptation file in use at the time of the accident, and SAR Files and, if possible, Playback Workstation Files (Playback workstation files must be extracted within 24 hours of the accident/incident). Keep a report/memo listing the local and national release information associated with the SAR Files. If necessary for a replay, extract the files required to prepare a SATORI for the same time period associated with the accident/incident.

(e) MEARTS – Retain the adaptation file in use at the time of the accident and a CDR Time Selected Output (CDTSO) so that the data can be replayed on the MEARTS RETRACK system. Keep a report/memo listing the software build and adaptation version in use when the CDR data was recorded. If necessary for a replay, extract a CDR Extraction with the following data classes: Tracking Data (TD), Beacon Targets (BT), Radar Targets (RT), Reinforced Targets (RB), System Scan (SC), MSAW Alerts (MA), and Conflict Alerts (CA) for the same time period associated with the accident/incident.

(f) REHOST – Retain the adaptation file in use at the time of the accident and a CDR Time Selected Output so that the data can be replayed on the REHOST Replay system. Keep a report/memo listing software build and adaptation version in use when the CDR data was recorded. If a replay is necessary, use Revue. Other recording devices must be approved by the Litigation Support Group.

(g) Airport Surface Detection Equipment (ASDE-X/AMASS & TAIU Data) and Safety Logic Systems – The facility must coordinate with the Surface Surveillance Systems Team (AJW-148) to have data saved (prior to the 45 day retention built into the surface surveillance system). Facilities must advise AJW-148 what to name the data.

(i) ASDE-X – Save both Legal Recording and SGF (engineering files) data and applicable radar map(s) current at the time of the accident.

(ii) AMASS – Extract AMASS logs and TAIU logs and retain applicable radar map(s) current at the time of the accident.

(iii) Contact Technical Operations’ Surface Surveillance Systems Team to request assistance. [email protected]

(4) Data that is preserved in any other equipment not listed above that contributes to a more complete understanding of the accident needs to be retained (for example, low-level windshear systems, pre-departure clearance messages, status information displays, etc.) if the capability exists.

(5) Refer to appendix D, Cassette Tape and Computer Diskette- Recordable (CD-R) Labeling for labeling examples.

b. Radar and Computer Data Certification. All requests to the system maintenance organization manager for data will be through the air traffic facility manager or designee. Radar and computer data require authentication. Ensure radar and computer data files are certified. The Review of Services Memo (see appendix B) lists what is retained whereas, certification memos give more details about the retained and/or extracted data.

(1) Examples of language for certification memos:

(a) "I certify this data is derived from computer recordings from [UTC date and UTC time] to [UTC date and UTC time]."

(b) "I certify this data is derived from the AIS-R data received by this facility for the period from [UTC date and UTC time] to [UTC date and UTC time]."

(2) The following statement is signed by the manager or acting manager of the En Route facility when recorded en route host/ERAM computer data is transferred to a diskette or CD-R:

“Please note that the program we used to transfer this data in the host/ERAM computer may utilize several control character codes which are not represented by printable characters and may or may not have ASCII equivalents. Therefore, we make no representations regarding the completeness of the data or the exactness of its conformity to previous or future downloads, either paper or electronic, or to the data on the mainframe itself. Please check data closely before using it to make sure that it is suitable to your needs.”

(3) Any Litigation/Enforcement replay made must be documented in accordance with paragraph 97.

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection › 75.-79. RESERVED

74. Data Collection Memorandums. When it is discovered that data has not been collected and/or is no longer available in accordance with this order, a memorandum must be prepared to explain what was discovered and why it happened. Insert this memorandum in the file.

75.-79. RESERVED

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files › 80.

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files

80. Numbering of Air Traffic Formal Accident File/Package and Informal Accident File

a. Air traffic formal accident files and packages, and informal accident files must be numbered with the facility accident number beginning with the (4-digit) number 0001 and continuing in numerical sequence without regard to year. The number must be preceded by the 3-character facility identifier and the facility type identifier (for example, ARTCC, terminal radar approach control [TRACON], ATCT, FSS, FCT, FCFSS). Do not use a separate numbering system for formal accident files/packages and informal accident files.

EXAMPLES:

ZTL-ARTCC-0095

D10-TRACON-0004

HCF-CCF-0013

JUN-FSS-0044

OLM-FCT-0001

PRC-FCFSS-0022

b. Supporting FAA facilities retaining information in an FAA air traffic informal or formal accident file must use the same accident number being used by the holding facility preparing the informal or formal accident file (as determined in paragraph 70).

c. Supporting same-vendor FCFs retaining information in an air traffic informal or formal accident file must use the same accident number being used by the holding FCF preparing the informal or formal accident file (as determined in paragraph 70).

d. When both FAA and FCFs have created an air traffic informal or formal accident file, two separate accident file numbers must be used, an FAA facility number, and an FCF number.

e. When different FCF vendors have each created an air traffic informal or formal accident file, then the different vendors will use their own accident file number. Different vendors will not share the same accident file number.

81. Holding and Support Facilities. The holding facility is responsible for final data collection (see paragraph 70). Other air traffic facilities that provided services for, or had communication/contact regarding the accident aircraft are referred to as supporting facilities. All facilities, holding and supporting, must review their services to the aircraft and retain all data pertaining to the handling of the aircraft. (See paragraphs 71 through 73, and appendix B for Review of Services Memo)

a. Holding Facilities:

(1) Generally have pertinent services (those services that take place after air traffic becomes aware of, or is notified of an unusual, urgent, or emergency situation by the flight crew or other sources). Holding facilities produce transcripts for each position that had pertinent services (see paragraph 94). Less often, a holding facility will have only provided routine services but are still responsible for the accident package. (For example, an IFR aircraft switched to the common traffic advisory frequency at an uncontrolled airport receives substantial damage during the landing.) Normally, holding facilities do not produce transcripts for positions that provided routine services.

(2) Must list air traffic personnel from supporting facilities with pertinent services on FAA Form 8020-6, Block 12. (Exception: FCF holding facilities do not list FAA nor othervendor supporting facility personnel; FAA holding facilities do not list FCF supporting facility personnel.)

b. Supporting Facilities:

(1) Generally, routine services are those that take place before air traffic becomes aware of, or is notified of an unusual, urgent or emergency situation by the flight crew or other sources.

(2) Generally, pertinent services are those that take place after air traffic becomes aware of, or is notified of an unusual, urgent or emergency situation by the flight crew or other sources.

(3) At times, a facility did not provide services to the accident aircraft but has data (e.g., radar) regarding the aircraft. (See paragraph 81c(5))

(4) The service center, FSPO/AFSIAG, ATO Litigation Support Group, ATO Safety or the FAA IIC may change a facility’s designation from having provided routine services to pertinent services. At that point, the newly designated pertinent support facility shall forward data to the holding facility as described in paragraph 81c.

c. All supporting facilities forward data to the holding facility for inclusion into the accident package. (Same-vendor supporting FCF facilities forward data to their FCF holding facility. FCF supporting facilities do not forward data to other-vendor FCF holding facilities. FAA supporting facilities do not forward data to FCF holding facilities.) The amount of data forwarded to the holding facility is determined by whether the facility provided routine or pertinent services and by the type of agencies involved (FAA, FCF or military). Forward data electronically or via other means.

(1) Supporting-Routine/Same -Type Agencies: FAA supporting facilities with FAA holding facility or FCF vendor supporting facilities with same-vendor holding facility. Supporting facilities that provided routine services must submit their Review of Services Memo (see paragraph 92 and appendix B) and FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) as described in paragraph 90b(2) to the holding facility within eight administrative days of notification of the accident/incident. Forward the original Review of Services Memo and retain a copy. Retain air traffic data of the services provided to (or about) the accident aircraft in the accident file using the holding facility’s accident file number.

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files › 82. Content, Assembly, and Distribution of Formal Accident Package.

(2) Supporting-Pertinent/Same-Type Agencies: FAA supporting facilities with FAA holding facility or FCF vendor supporting facilities with same-vendor holding facility. Supporting facilities that provided pertinent services must submit their Review of Services Memo (see paragraph 92 and appendix B), FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) as described in paragraph 90b(2), and forward copies of all data as required in paragraphs 71 through 73, as applicable, to the holding facility within eight administrative days of notification of the accident/incident. Forward the original Review of Services Memo and retain a copy. Retain air traffic data of the services provided to (or about) the accident aircraft in the accident file using the holding facility’s accident file number.

(3) Supporting-Routine/Other-Type Agencies: FCF vendor supporting facilities with FAA or other-vendor holding facility. FCF supporting facilities do not submit data to other-vendor FCFs. FCF supporting facilities do submit to the FAA holding facility FAA Form 8020-6-1 and a Review of Services Memo within eight administrative days of notification of the accident/incident (FAA facilities do not submit data to FCFs).

(4) Supporting-Pertinent/Other-Type Agencies: FCF vendor supporting facilities with FAA or other-vendor holding facility. FCF supporting facilities do not submit data to other-vendor FCFs. FCF supporting facilities do submit to the FAA holding facility FAA Form 8020-6-1 and Review of Services Memo within eight administrative days of notification of the accident/incident. FCF supporting facilities also submit to the FAA holding facility copies of transcripts and certified working copies of voice recordings within eight administrative days of notification of the accident/incident (FAA facilities do not submit data to FCFs).

(5) Facilities that did not provide services but have pertinent data (see paragraphs 72). Send the FAA holding facility FAA Form 8020-6-1, and a Review of Services Memo, and a copy of pertinent data within eight administrative days of notification of the accident/incident. (FAA facilities send data to other FAA facilities but not FCFs. FCFs send data to same-vendor FCFs and FAA facilities but not to other-vendor FCFs.)

82. Content, Assembly, and Distribution of Formal Accident Package.

a. Content. The formal accident package must contain the holding facility’s accident report forms, all pertinent records, transcriptions of voice recordings, charts, and facility memoranda (see appendix B). Copies of records from supporting facilities must be obtained and included in the package as follows. From supporting facilities with pertinent services, the holding facility’s accident package will contain all applicable records. From supporting facilities with routine services, the holding facility’s accident package will normally only contain FAA Form 8020-6-1 and the Review of Services Memo (see paragraph 81). From military facilities with routine or pertinent services, the holding facility’s accident package will contain applicable equivalent documents if the military supplies them.

Unless requested by the FAA Office of Accident Investigation and Prevention (AVP), the ATO Litigation Support Group, or other competent authority, all classified or security sensitive information and/or documentation and information protected under the Privacy Act (for example, home, cellular, and pager telephone numbers of FAA, airport, military, and emergency personnel/offices, etc.), normally made a part of the formal or informal air traffic aircraft

accident file, including but not limited to the air traffic aircraft accident package, must be redacted or blacked out from all copies. Only the original air traffic accident file and/or package at the originating air traffic facility will retain the original information and/or documentation. When redacting, do not “white out” so it appears as the information was never present. It must be obvious to the reader the document has been altered.

b. Final Assembly. Facilities are encouraged to use the Accident Package Generator to assemble accident packages (contact the Service Center QCG for details). The facility may choose to retain an electronic and/or paper package. (Any original paper components used to produce the electronic package must be retained in the accident file. If a paper package is made, assemble the paper package in a top-fastening hard cover binder with a cover label, dividers, and sections. Affix a label (maximum size 3" x 5") to the front cover. The label must be clearly marked "Aircraft Accident Package" with the facility accident number, aircraft registration(s) or flight number(s), aircraft type(s), (aircraft types, in order of preference, should be taken from the flight progress strip/inflight contact form; the 7110.65; the FAA aircraft registry site; then the ICAO aircraft registry site) accident UTC date and UTC time, and the UTC date the package is to be destroyed (the original accident package -- 5 years; copies of the original package -- 2½ years).

Include a Table of Contents page that lists each section number and content. Insert a sheet of plain paper between each section with the section number and title of the section centered on the page. If the information called for by a specific section is unavailable or not pertinent, use that section number for the next required item so that the numbers remain in sequence. All information in each section must be in the chronological order beginning with the first facility having contact with the aircraft and then in order of involvement. Every page (including the section divider sheets) must reference the accident number and aircraft registration(s) or flight number(s). Except for transcripts (see paragraph 94) the accident number and registration(s) or flight number(s) must be in the lower left hand footer. Assemble the package in the following order:

(1) Certification. The certification memorandum accompanies the package when the package goes to the service center/FSPO for their review. The Certification Memorandum is no longer a part of the formal accident package. Therefore the certification memorandum is not distributed to the FAA IIC after the package is released.

(2) Section 1. Table of Contents (list each section number and content).

(3) Section 2. FAA Form 8020-6, Report of Aircraft Accident, and FAA Form 8020- 6-1, Report of Aircraft Accident (Continuation Sheet) (see paragraph 90). Each facility having provided air traffic services or having communication with or contact regarding the subject aircraft must submit FAA Form 8020-6-1. Place FAA Forms 8020-6-1 in chronological order of contact, or comments concerning or about the subject aircraft.

(4) Section 3. Review of Services Memo(s) (see paragraph 81 and paragraph 92). The certification signature must be the same as the typed name of the facility manager or acting facility manager. Do not use initials. Do not use "for" to sign as the certifier.

(5) Section 4. FAA Form(s) 7230-4, Daily Record of Facility Operation. Include FAA Form 7230-4 from all pertinent dates. For example, the date service was provided, the date of

the accident, and the date it was reported. Any MORs related to the accident need to be included in this section as well.

(6) Section 5. Personnel Log(s). If the facility has more than one area of specialization, then include all personnel logs of every area of specialization having contact with the subject aircraft. Use of the ATO Portal is recommended; however, facilities utilizing Cru- ART are required to include a memorandum listing those employees on Regular Days Off (RDO) (see appendix B). Redact any type of leave taken only on copies of the personnel logs.

(7) Section 6. FAA Form(s) 7230-10, Position Log(s), or automated equivalent.

(a) Towers or combined tower/TRACON and FSS. Include all positions regardless if staffed or not.

(b) TRACON, FCF and ARTCC facilities. Include all positions regardless if staffed or not. If the facility has more than one area of specialization, then include all positions of every area of specialization having contact with the aircraft.

(8) Section 7. Facility Layout Chart(s). Identify the facility being depicted on the chart. If positions of operation are identified by other than traditional abbreviations, include a legend.

(9) Section 8. Airport Diagram. For all aircraft accidents on or within one mile of the airport property, provide an airport diagram current at the time of the accident, where available. The airport diagram must include the name of the airport and, since printed or copied diagrams are not to scale, include the statement "this diagram not to scale" on the diagram. If able, use FAA produced diagrams (see http://www.faa.gov/airports/runway_safety/diagrams/ )

(10) Section 9. Flight Progress Strip(s) (if printed) and/or In-Flight Contact Record. Make sure the name of the facility and the UTC date(s) are indicated on the page displaying the flight progress strips or contact records.

(11) Section 10. Transcription of Voice Recording(s) (see paragraph 94).

(12) Section 11. FAA Form(s) 8020-3, Facility Accident/Incident Notification Record, (see figure A-1).

(13) Section 12. Weather Products. Weather that was pertinent to the aircraft accident/incident and/or available to the facility (regardless if issued to the flightcrew) and the source of the weather. This includes weather entered on the 8020-6 (including remarks). PIREPs, SIGMETs, AIRMETs, TAFs, weather-related NOTAMs and other weather information should also be included.

National Climatic Data Center (NCDC) blue ribbon certified weather does not need an additional certification statement. NCDC weather is no longer recommended for Meteorological Terminal Aviation Routine Weather Reports (METARs) due to the conversions required by the person entering weather into the accident package. Other NCDC products like TAFs, AIRMETs and SIGMETs do not require conversion.

Non-blue ribbon weather needs a certification statement.

(a) AIS-R or OASIS EVR, or copies of weather observation forms must be individually certified by the facility responsible for initiating the record. The air traffic certification must read:

"I certify the attached copy of the [weather product(s)] originated from [source] is an accurate copy of the original."

(b) The certification for air traffic facilities taking weather observations must read:

"I certify that this is an accurate copy of the original which has been forwarded to the National Weather Service Records Center."

(c) En route facilities may also obtain pertinent weather information from the Center Weather Service Unit (CSWU) which must be certified.

"I certify the attached copy of the [weather product(s)] originated from the [source] (example, “Memphis Center Weather Service Unit”) is an accurate copy of the original.”

(d) NEXRAD or similar weather presentations.

“I certify the attached chart is an accurate reproduction of NEXRAD information displayed on [type of equipment or display] at the [facility] on 07/08/13.”

(e) Air traffic facilities that do not take weather observations must include weather data in the weather products section. Air traffic facilities may obtain weather from various sources such as the CWSU, NWS and NCDC. Additionally, the Accident Package Generator (APG) may be used to obtain archived METARs.

“I certify the attached copy of the [weather product(s)] originated from the [source] (example, “APG-link to archived weather” or “National Weather Service” or National Climatic Data Center”) is an accurate copy of the original.”

(14) Section 13. Non-published applicable NOTAM’s. (Non-published NOTAM’s are of a temporary nature, like Temporary Flight Restrictions (TFRs). NOTAM’s or aeronautical information of an extended nature are published in the Notices to Airmen Publication (NTAP).

(15) Section 14. FAA Form(s) 7233-2, Preflight Briefing Log, or automated equivalent.

(16) Section 15. FAA Form 7233-1, Flight Plan, or automated equivalent.

(17) Section 16. Other. Include any other materials deemed pertinent; The APG will automatically generate a UTC conversion chart. (This chart is not mandatory for those who do not use the APG.)

82. Content, Assembly, and Distribution of Formal Accident Package. › c. Distribution.

c. Distribution.

(1) The facility preparing the accident package must retain the package with original documentation in the facility files. Original documents (recorded or written) must not be released from the air traffic facility's custody (see paragraph 100). Facilities must distribute the copy(s) (Copies are readily identified by the 2 ½ year destroy date, versus 5 years for the original) of the package as follows:

(a) FAA terminal, TRACON, and en route facilities; and FCT facilities.

(i) Two complete packages or one electronic package (exception for FCTs: one package, paper or electronic) to the appropriate service center within 30 calendar days of the accident. After review, the service center will forward one copy of the package to the ATO Litigation Support Group within 45 calendar days of the accident.

(ii) After the ATO Litigation Support Group has reviewed and released the package, send two complete packages or one electronic package to the FAA IIC (the FAA Accident Investigation Division or FSDO, as appropriate). (Exception for FCTs: forward the one and only copy to the FAA IIC.) FAA terminal, TRACON and en route facilities will also send one copy to the ATO Litigation Support Group.

(iii) The FAA IIC must forward one COPY (for FCTs, the one and only copy) to the NTSB within 60 calendar days of the accident.

(b) FAA FSS facilities.

(i) Two complete packages or one electronic package to the AFSIAG within 30 calendar days of the accident. After review, the AFSIAG will forward one copy of the package to the ATO Litigation Support Group within 45 calendar days of the accident.

(ii) After the ATO Litigation Support Group has reviewed and released the package, the FAA FSS must send two complete packages or one electronic COPY of the package to the FAA IIC (the FAA Accident Investigation Division or FSDO, as appropriate) and one package to the ATO Litigation Support Group.

(iii) The FAA IIC must forward one copy to the NTSB within 60 calendar days of the accident.

(c) FCFSS facilities. The FCFSS preparing the accident package must retain the package with original documentation in the facility files. Distribute one copy of the package as follows:

(i) To the FSPO. After review for compliance with applicable FAA orders and directives, the FSPO will forward the one and only copy of the package to the ATO Litigation Support Group on a Quarterly Review Basis. (FSPO will forward five FCFSS DRAFTS to the ATO Litigation Support Group per quarter by the 20th of the last month of the quarter. Quarterly Review periods include October, January, April, and July.) After the ATO Litigation Support Group has reviewed and released the package, or if the package is not part of

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files › 83. Certification of the Air Traffic Aircraft Accident Package.

the Quarterly Review process, the facility must forward one copy to the FAA IIC who will then forward it to the NTSB within 60 calendar days after the accident.

(ii) Should corrections to the accident package become necessary after the FCF forwards the copy of the accident package to the NTSB, all changes must be distributed in the same manner as outlined in paragraph 82c(1)(c)(i). A memorandum from the FCF manager or acting manager must accompany any change(s) with a complete explanation of the change.

(2) Facilities that prepare a formal accident package as a result of an accident involving military aircraft must distribute the package in accordance with paragraph 82c.

83. Certification of the Air Traffic Aircraft Accident Package.

Continue reading ↓ 120 of 377 passages shown