Radar Vectors
FAA Order Cancelled Issued Nov 24, 2010 AJV-4 248 pages Copy saved Nov 18, 2026

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

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

Official source ↗ Open PDF

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

FAA Order JO 8020.16A Air Traffic Organization Aircraft Accident and…

Distribution: A-W-1; A-W(HL/HP/EE/ST) -2; Initiated By: AJV-4 A-W(GC/IA/PA/AS/CS/AI/IR/FS/TA/TP/TX/NS/OP/VN) -3; Mission Support, Litigation Liaison Office A-X(CC/GC/IA/PA) -2; A-X(HR/CD/FS/AM/AF/AT/AS/CS) -3; A-Y(CC/GC/PA/CS/HR) -2; A-Y(CS/HR/AY) -3; A-Z(CC/GC/PA/CS/HR) -2; AAR-400/AAR-422(2 ea); A-FOF-0(STD)

Effective Date: December 27, 2010

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.16, dated September 13, 2005, including all associated notices. Significant changes have been made to creating Aircraft Accident Packages, required records in Formal and Informal Aircraft Accident Files, data required for Pilot Deviations, electronic data retention and certification, and forms used by air traffic.

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 air traffic incidents as they pertain to notification, reporting, and data retention. Henry P. Krakowski Chief Operating Officer Air Traffic Organization

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Air Traffic Organization Policy

ORDER JO 8020.16A

FAA Order JO 8020.16A Air Traffic Organization Aircraft Accident and… › Explanation of Changes

ii

Explanation of Changes

Direct questions through appropriate facility/service center office staff to Mission Support, Litigation Liaison Office.

a. 12. Safety Risk Management (SRM) Analysis This paragraph has been added.

b. 62. Operations Centers Notification procedures have been updated to include Order JO 1030.3, Incident Response Order.

c. 65. Aircraft Accident and Incident Notification Reporting Procedures on what, how, and when to report aircraft accidents and incidents have been clarified or expanded.

d. 70. Determination of Air Traffic Facility Responsible for Final Data Collection This change cancels and incorporates N JO 8020.184, Determination of Air Traffic Facility Responsible for Final Data Collection, effective March 20, 2010.

e. 71. Formal Accident File/Package Data Collection The process for downgrading a formal accident file/package was clarified. The requirement to prepare an informal accident file when a formal accident file/package is not prepared was made clearer. FSS vendor responsibilities were spelled out. More examples of pertinent data were given. The requirement to perform an ARTS clock comparison was removed. This change cancels N JO 8020.182, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, effective January 1, 2010.

f. 72. Data Collection and Certification by Selected Facilities References to FSS equipment/processes were modernized. The DEN was added. Computer certification statements were moved.

g. 73. Radar and Computer Data A new paragraph detailing the expanded amount and types of radar and computer data now required was added.

h. 74. Correction Memorandums A new paragraph explaining the process for correction memorandums was added.

i. 81. Support Facilities Facilities providing normal services was clarified.

j. 82. Content, Assembly, and Distribution of Formal Accident Package The requirement to place the accident package number and aircraft identification in the lower left hand footer was added (transcriptions excluded). Certification Memorandums were removed from the accident package contents. The provision for electronic copies, instead of paper copies, was included. Use of the ATO Portal for personnel logs was recommended. The requirement for towers or combined tower/TRACONs to include all positions (FAA Form 7230-10) of operation in the accident package was clarified. Weather certification statements were modified. Distribution procedures were modified. This change cancels N JO 8020.182, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, effective January 1, 2010.

k. 83. Certification of the Air Traffic Aircraft Accident Package This memorandum was removed from the accident package content. This change cancels N JO 8020.182, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, effective January 1, 2010.

l. 84. Informal Accident File Data Collection A certified index, radar and computer data were added to the list of required contents.

m. 91. FAA Form 8020-26, Personnel Statements FAA Form 8020-26, Personnel Statement, was amended to delete the Equipment Attachment. Also in Block 10, Text of Statement, an individual now will check the box "Comment" if they wish to provide any facts pertaining to said accident or check the box "No Comment" if they have no information to add, with one exception. The “Comment” box must be utilized for air traffic incidents. This change cancels N JO 8020.182, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, effective January 1, 2010.

n. 114. Pilot Deviations Added clarification to NORDO processing. This change cancels N JO 8020.188, Pilot Deviations, effective August 28, 2010.

iii

o. 119. Miscellaneous Incidents This change added procedures for retaining data pertaining to tarmac delays. This change cancels and incorporates N JO 8020.186, Tarmac Delay Data Retention, effective April 29, 2010.

p. 156. Decisions Clarified Technical Operations processes regarding equipment as it pertains to accidents/incidents. Added clarification that a suspect facility must remain in the same operational condition as at the time of the accident/incident.

q. Appendix A. Forms Used by Air Traffic FAA Form 8020-3 has changed. The current version is dated 10/10. Please remove unused outdated versions from operating quarters, quality assurance offices, etc., and replace them with the 10/10 edition. Changes include adding the Domestic Events Network (DEN), and Operational Control Center (OCC). Note well: the DEN number must be redacted from all copies of the 8020-3 leaving the facility for a FOIA request, accident package, etc.

The OCC is tasked with determining what, if any, NAS facilities are suspected of being involved in an aircraft

accident/incident. (For example, a navigational aid sending erroneous information to a pilot.) The particulars of the accident/incident will determine whether or not the OCC is called. Paragraph 156a(1) and (2) gives guidance on when to call the OCC, “Accidents which are clearly related to the aircraft condition or to a failure aboard the aircraft (e.g., nosewheel collapse during an otherwise normal landing, fuel exhaustion, ground loops, blown tires, engine failure, etc.) may be excluded from this notification procedure….” While there may be a duplication of information given to the ROC/WOC and/or to the SMO, it is necessary for the OCC to receive timely information when equipment failure/malfunction may have contributed to the accident. The following number will route you to the OCC for your area of the country: (866) 432-2622.

r. Appendix F. Definitions Definitions were moved to an appendix and modified or added to reflect changes in the ATO (for example, unmanned aircraft systems) pertaining to litigation.

s. Additional editorial/format changes were made where necessary.

iv

Table of Contents

Paragraph Page Chapter 1. General

FAA Order JO 8020.16A Air Traffic Organization Aircraft Accident and… › Table of Contents

1. Purpose of This Order … 1 2. Audience … 1 3. Where to Find This Order … 1 4. Cancellation … 1 5. Explanation of Changes … 1 6. Distribution … 1 7. Authority to Change This Order … 1 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, and Flight Service Program Offices in Aircraft Accident Investigations … 3 15. FAA and NTSB Accident and Incident Investigation Agreements … 3 16. Post-Accident or Incident Drug Testing … 4 17. FAA Investigator-in-Charge (IIC) … 4 18. FAA Participants … 4 19. Other FAA Personnel … 4 20. FAA Safety Recommendation Program … 4 21. Training … 5 22-29. RESERVED … 5

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

30. Office of Accident Investigation and Prevention … 6 31. Operations Centers … 7 32. Air Traffic Organization (ATO) … 7 33. Flight Standards Service … 8 34. Office of Aviation Medicine … 9 35. Office of Airport Safety and Standards … 9 36. Office of the Chief Counsel … 9 37. Assistant Administrator for Security and Hazardous Materials … 9 38. Aircraft Certification Service … 9 39. Office of Communications … 9 40. Office of International Aviation … 10 41-59. RESERVED … 10

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

60. General … 11 61. FAA Contract Facilities (FCF) … 11 62. Operations Center … 11 63. Notification of Other Operations Centers … 12 64. National Transportation Safety Board (NTSB) … 12 65. Aircraft Accident and Incident Notification and Reporting … 12 66. Completing and Transmitting FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … 14 67. Military Notification to the FAA When the FAA Is Involved In a Military Aircraft Accident … 16 68–69. RESERVED … 16

v

Paragraph Page Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection

70. Determination of Air Traffic Facility Responsible for Final Data Collection … 17 71. Formal Accident File/Package Data Collection … 17 72. Data Collection and Certification by Selected Facilities … 19 73. Radar and Computer Data … 20 74. Correction Memorandums … 21 75-79. RESERVED … 21

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files

80. Numbering of Air Traffic Formal Accident File/Package and Informal Accident File … 22 81. Support Facilities … 22 82. Content, Assembly, and Distribution of Formal Accident Package … 23 83. Certification of the Air Traffic Aircraft Accident Package … 26 84. Informal Accident File Data Collection … 26 85–89. RESERVED … 27

Chapter 6. Preparation of Forms, Personnel Statements, Certified Indexes,

Voice Recordings, and Transcripts

90. FAA Form 8020-6, Report of Aircraft Accident … 28 91. FAA Form 8020-26, Personnel Statements … 29 92. Certified Index … 31 93. Copies of Voice Recordings … 31 94. Transcription of Voice Recordings … 33 95. Automated Aircraft Accident Package Program … 35 96–99. RESERVED … 35

Chapter 7. Retention of Formal and Informal Air Traffic Aircraft Accident Files, and

Air Traffic Incident Files

100. Security of Records … 36 101. Retention of Voice Data … 36 102. Retention and Disposal of Aircraft Accident Records … 36 103–109. RESERVED … 37

Chapter 8. Air Traffic Incidents

110. Air Traffic Incident Notification and Reporting … 38 111. Near Midair Collisions (NMAC) … 39 112. U.S. Air Force (USAF) Hazardous Air Traffic Reports (HATR) … 41 113. U.S. Army Operational Hazard Reports (OHR) … 42 114. Pilot Deviations … 43 115. FAA Form 8020-11, Incident Report … 46 116. Vehicle and Pedestrian Deviations … 47 117. Emergency Evacuations … 48 118. Parachute-Jumping Incidents … 48 119. Miscellaneous Incidents … 48 120. Flight Standards … 50 121. Retention and Disposal, Contents, and Labeling of Air Traffic Incident Records … 50 122. Request for Information and Records Furnished Outside of the FOIA Process … 50 123. Knowledge Services Network (KSN) … 51 124-129. RESERVED … 51

vi

Paragraph Page Chapter 9. Aircraft Accident Investigation Responsibilities

Section 1. Office of Accident Investigation and Prevention

130. Office of Accident Investigation and Prevention Responsibilities … 52 131. Regional Flight Standards Division Responsibilities … 52 132. Designation of the FAA IIC … 52 133. Possible Involvement of Navigation Facilities … 52 134. Technical Operations Aviation System Standards Responsibilities … 52 135. Washington Headquarters "Go Team” … 53 136. Additional Information … 53 137–139. RESERVED … 53

Section 2. Air Traffic Services

140. General … 54 141. Air Traffic Accident Representative … 54 142. Air Traffic Accident Representative Responsibilities … 54 143–149. RESERVED … 55

Section 3. Technical Operations Services

150. Introduction … 56 151. Scope … 56 152. Overview of Technical Operations Services Activities … 56 153. Responsibilities … 56 154. Aircraft Accident Representative … 57 155. Process … 58 156. Decisions … 58 157. Field Work … 61 158. Documentation … 62 159. Preserving, Copying, and Releasing Reports and Records … 63 160. Field Response for Post Aircraft Accident Data … 63 161-169. RESERVED … 64 FIG 9-3-1. Aircraft Accident/Incident TOAAR Checklist … 65 FIG 9-3-2. Facility Restoral Checklist … 67 FIG 9-3-3. Aircraft Accident/Incident Package Cover Page … 69 FIG 9-3-4. Technical Operations Services Post-Aircraft Accident Process … 70

Section 4. Office of the Chief Counsel

170. General … 71 171. Extent of Legal Participation … 71 172. Additional Information … 71 173–179. RESERVED … 71

Chapter 10. Public Release of Accident and Incident Information

180. General … 72 181. Military Aircraft Information … 72 182. Public Requests for Reports … 72 183. FOIA Request for Accident or Incident Investigation Documents … 72 184–189. RESERVED … 73

vii

Paragraph Page 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-4 FIG A-4. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … A-5 FIG A-4. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice (continued) … A-6 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-16 FIG A-9. FAA Form 8020-24, Preliminary Vehicle or Pedestrian Deviation Report (continued) … A-17 FIG A-9. FAA Form 8020-24, Preliminary Vehicle or Pedestrian Deviation Report (continued) … A-18 FIG A-10. FAA Form 8020-26, Personnel Statement … A-19

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

Appendix E. Original Documentation Transfer … E-1

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

Appendix F. Definitions … F-1

Chapter 1. General › 7. Authority to Change This Order

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 Web site at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications Web site at http://www.faa.gov/air_traffic/publications/.

4. Cancellation

FAA Order 8020.16, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, dated September 13, 2005, 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 pilot deviations, including those involving security temporary flight restrictions.

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

Only the Director of Technical Operations or Director of Mission Support, Litigation Liaison Office, may approve changes except those involving policy, assignment of responsibility, and delegation of authority. Those organizations with aircraft accident and incident notification, investigation, and reporting responsibilities should submit proposed changes or additions to the Litigation Liaison Office.

Chapter 1. General › 13. FAA Responsibilities in Aircraft Accident Investigations

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 Litigation Liaison Office.

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.56, Air Traffic Quality Assurance

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 National Airspace System (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 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. FAA's nine responsibilities in accident investigations are to determine whether:

(1) Performance of FAA facilities or functions was a factor.

(2) Performance of non-FAA owned and operated air traffic control facilities or navigational aids was a factor.

(3) Airworthiness of FAA-certificated aircraft was a factor.

(4) Competency of FAA-certificated airmen, air agencies, commercial operators, or air carriers was involved.

(5) Federal Aviation Regulations were adequate.

(6) Airport certification safety standards or operations were involved.

(7) Airman medical qualifications were involved.

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

(8) There was a violation of Federal Aviation Regulations.

(9) Airport security standards or operations were involved.

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 on-scene 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, and Flight Service Program Offices 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.

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.

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.

Chapter 1. General › 18. FAA Participants

(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 or the Regional 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 service-conducted 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.

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. This course is sponsored by TSI and conducted at the Bell Helicopter Customer Training Academy, Fort Worth, Texas.

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 near midair collisions (NMAC), operational errors, pilot deviations, runway incursions, and vehicle and pedestrian deviations.

(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.

Chapter 2. › 32. Air Traffic Organization (ATO)

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.

(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 decisionmaking can proceed in a timely manner. Refer to FAA Order JO 1030.3 for appropriate notification procedures.

32. Air Traffic Organization (ATO)

a. The Office of Safety, System Operations Services, Acquisition and Business Services, En Route and Oceanic Services, and Terminal Services. The ATO participates in the investigation of aircraft accidents and incidents when FAA air traffic control or aeronautical communications facilities are involved. Service area directors, service center directors, and the Flight Service Program Operations Director are responsible for ensuring that incidents in their assigned area that involve only air traffic functions are investigated and reported in a 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.

Chapter 2. › 33. Flight Standards Service

(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.

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

c. Acquisition and Business Services, Information Technology, Technical Services Program. The Acquisition and Business Services, Information Technology, Technical Services is responsible for collecting, automating, and analyzing operational error, near midair collision, pilot deviation, and vehicle and pedestrian deviation reports.

d. The Office of Safety, Runway Safety and Operational Services. Runway Safety and Operational Services is responsible for evaluating all surface incident reports and making a determination as to whether or not the incident meets runway incursion criteria. Additionally, Runway Safety and Operational Services tracks and maintains all runway incursion data in the Runway Safety and Operational Services 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. If an incident involves only air traffic functions; that is, air traffic operational errors or deviations, the service center director or FSPO Director must assume responsibility for the required investigative and reporting responsibilities in accordance with the latest edition of FAA Order 7210.56.

(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 NMAC and pilot deviation reports 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, except for operational errors, near midair collisions, pilot deviations, and vehicle and pedestrian deviations, all of which are maintained by Acquisition and Business Services, Information Technology, Technical Services. 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 and Operational Services, and maintained in its database.

Chapter 2. › 38. Aircraft Certification Service

34. 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.

35. 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 vehicle and pedestrian deviation reports received in the preceding quarter, the status of those reports, and the status of reports open at the beginning of the preceding quarter.

36. 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, paragraph 170.

37. 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.

38. 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.

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.

39. 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.

Chapter 2. › 41-59. RESERVED

40. 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. › 62. Operations Center

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).

b. Contact from points that are not readily accessible to an FAA air traffic facility, such as those outside the United States, its territories, and possessions, must be made through established channels; that is, 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 contact the Unmanned Aircraft Program Office, 202-385-4636, through the Regional Operations Center (ROC).

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, except for emergency evacuations, which require FAA Form 8020-11, Incident Report. If requested by the FSDO, the Litigation Liaison Office, service center, Flight Service Program Office, or Safety Investigations and Evaluations, FAA Form 8020-11 will also be completed for selected aircraft incidents.

e. FAA Form 8020-11, Incident Report; FAA Form 8020-17, Preliminary Pilot Deviation Report; FAA Form 8020-21; Preliminary Near Midair Collision Report; and FAA Form 8020-24, Preliminary Vehicle or Pedestrian Deviation Report, are to be used to report air traffic incidents (see paragraph 110 for description of air traffic incidents and appendix A for copies of the forms).

61. FAA Contract Facilities (FCF)

Unless indicated in the following paragraphs or specifically directed by the FAA Accident Investigation Division, the FAA IIC, or the Litigation Liaison Office, 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, other data, 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.

NOTE- 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, or an air traffic 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.

Chapter 3. › 65. Aircraft Accident and Incident Notification and Reporting

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, Air Traffic, 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 telecopies 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 4 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.

63. Notification of Other Operations Centers

Each ROC officer must provide information to other ROCs 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.

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

64. 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 air traffic incident file.

65. Aircraft Accident and Incident Notification and Reporting

The definition of an aircraft accident is in appendix F. An aircraft accident or aircraft incident differs from an air traffic incident, which includes NMACs, pilot deviations, vehicle or pedestrian deviations, and other occurrences. Air traffic incidents are discussed in chapter 8. This paragraph is broken into three categories: 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. An example of a suspected accident is the simultaneous unexplained loss of radio communications and radar contact with an aircraft. For accidents where the aircraft has not been physically located, air traffic facilities must immediately contact the service center Quality Control Group through the ROC. (FAA

Flight Service Stations [FSS] normally contact Alaskan FSIAG [AFSIAG].) The service center Quality Control Group will then contact Safety Search and Rescue.

(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 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 wellknown 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 of the ROC or the WOC.

(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.

(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.

(1) Any air traffic facility first receiving notification of a known or suspected accident/incident must make and record notification using FAA Form 8020-3, which is a list of contacts (see appendix A). There may be more than one 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 and updated periodically. Notification to the nearest National Weather Service (NWS) of known or suspected accidents in which any person suffers death or serious injury or the aircraft received substantial damage is mandatory. Unless otherwise outlined in a Letter of Agreement between the respective Service Area and the NWS, notify the nearest NWS office or forecast center. Initial notification is based on preliminary information. FAA Form 8020-3 is not used to report air traffic incidents. See chapter 8 for reporting air traffic incidents.

(2) 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.

EXAMPLE- Indianapolis Air Route Traffic Control Center (ARTCC) must have an FAA Form 8020-3 for Evansville Airport Traffic Control Tower (ATCT) and all satellite airports.

Chapter 3. › 66.

(3) The air traffic facility must complete and transmit FAA Form 8020-9 (see paragraph 66).

c. When to Report.

(1) Overdue and missing aircraft.

(b) Air traffic facilities must immediately contact the service center Quality Control Group through the ROC when an aircraft becomes overdue or missing. The service center Quality Control Group will then contact Safety Search and Rescue.

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

(2) Air traffic facilities must notify the ROC of all known and suspected aircraft accidents/incidents within 2 hours of becoming aware of any of the following:

NOTE- The ROC will notify the WOC of accidents/incidents within 2 hours of the original accident/incident report.

(a) Air carrier, air taxi, or commuter aircraft.

(b) Aircraft operating under instrument flight rules (IFR) or special visual flight rules (SVFR).

(c) For all other accidents/incidents, the determination of whether Safety Investigations and Evaluations notification is necessary or required must be based on 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. The level of air traffic service is used to denote the amount and complexity of service being provided. The determination of the "amount of complexity" of air traffic service must be based on the best assessment of the appropriate service center, or FSPO in consultation with the facility. Although not all-inclusive, 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 a separation, sequencing, and/or vectoring to a VFR aircraft within Class B airspace.

(d) Selected criminal acts reported to or by law enforcement agencies, emergency evacuations of aircraft, and in-flight major component failures.

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

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

66. 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. Enter "unknown" for any item unavailable when the message is prepared.

a. Completing FAA Form 8020-9.

(1) Complete Part 1 of FAA Form 8020-9 for all known or suspected accidents/incidents.

(2) Complete Part 2 of FAA Form 8020-9 when radio navigational aids, communications equipment, radarautomated 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) FAA Form 8020-9 must be updated as new and/or amended information becomes available. Because it serves as a worksheet, these amendments must be accomplished simply by placing a single line through the erroneous information and entering the new data. Examples of items commonly amended are the aircraft type, aircraft damage, and location and time of occurrence. For transmitting a second message, see paragraph 66c.

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, or by National Airspace Data Interchange Network (NADIN)/Network Enterprise Management Center (NEMC) message, using immediate (DD) precedence where it will then be forwarded, as necessary, to:

(a) FAA, Washington Operations Center, Washington, D.C.

(b) NTSB, Washington, D.C.

(c) FAA service center with jurisdiction over the area in which the accident/incident occurred. If the aircraft was under the control of an FAA facility in another service center, both service centers 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 or telephone significant accidents/incidents (for example, 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.

(7) When transmitting information from FAA Form 8020-9 via NADIN/NEMC, the manager's name and title of the air traffic facility responsible for compiling the required information (as determined by paragraph 70) must be included in the format.

c. Transmitting a Second Message.

(1) Send a second message upon locating aircraft wreckage, to revise the original message, or to downgrade the accident to an incident.

(2) Distribute the message to the same addresses as the original message and include a reference to the accident/incident date and aircraft identification number in the original message.

(3) Include the letters "FAA" in FAA Form 8020-9, Part B, 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.

Chapter 3. › 67.

(4) Enter "unknown" for any item unavailable when the message is prepared.

(5) Complete FAA Form 8020-9, item F, in all cases. If the name of the FAA IIC for the accident/incident is unknown, the office(s) notified should be indicated; for example, NTSB FTW, SW-FSDO-65.

67. 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 second 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.

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

68–69. RESERVED

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection › 71. Formal Accident File/Package Data Collection

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection

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

a. The field facility that meets the following criteria will be responsible for the final air traffic file (see Appendix C, Determination of Air Traffic Facility Responsible for Final Data Collection Flow Chart):

(1) Aircraft on IFR flight plans under the control of an FAA-staffed facility: the FAA air traffic facility with jurisdiction over 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 Litigation Liaison Office 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.

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

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

(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 71e, 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. When permitted by the service center, or FSPO, it is possible and permissible that data collection will vary between FAA and FCF facilities. This is determined by the type and/or level of service provided (see paragraph 71).

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, the Litigation Liaison Office, the service center, or FSPO.

71. Formal Accident File/Package Data Collection

Initiate a formal accident file/package for all investigations, including military investigations, when air traffic facilities may be or are involved in the accident. The determination may be made to downgrade the file after consultation with the service center, or FSPO and the Litigation Liaison Office.

a. Continue the formal accident files/packages for the following (all of which include military aircraft):

(1) Air carrier, air taxi, and commuter accidents.

(2) Accidents involving aircraft operating under IFR or SVFR which resulted in fatalities or serious injuries.

(3) For any suspected aircraft accidents when wreckage and/or other debris is not immediately located but when there is reason to believe that an accident may have occurred and the accident meets any of the requirements in accordance with paragraph 71a(1)-(3).

(4) When requested by the FAA IIC, the Litigation Liaison Office, service center, or FSPO.

b. For all other accidents, the determination of whether a formal accident file/package is necessary or required must be based on the "level of air traffic service" (if any) which was being provided to the aircraft, including weather-related accidents when a weather briefing was provided within 24 hours of the accident. The level of air traffic service is used to denote the amount and complexity of service being provided. The determination of the "amount of complexity" of air traffic service must be based on the best assessment of the service center, or FSPO in consultation with the facility or after coordination with the Litigation Liaison Office. Although not all-inclusive, an example of minimum service may be a 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.

(1) If a determination has been made that no formal accident file/package will be prepared, the service center or FSPO may request the facility(ies) that provided air traffic service(s) or pertinent information prepare an informal accident file in accordance with paragraph 84, unless a determination of a nonoccurrence has been made (see paragraph 71g(2)).

(2) In the case where no air traffic service was being provided to the aircraft but air traffic subsequently became aware of the accident (via notification by police or similar organizations), no formal or informal file/package is required, and all forms and documentation associated with the notification process must be retained.

c. Obtain documentation as follows:

(1) After the preliminary notification, appropriate facilities along the flight route must be requested to provide pertinent documentation (see paragraph 71c(6)).

(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) Contracted 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 (per 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) Upon receipt of such a request, air traffic facilities must promptly advise the requesting facility if pertinent documentation is available and the date it will be forwarded. Negative replies must be forwarded within 4 hours. Normal service statements (see paragraph 81), certified index, and FAA Form 8020-6-1, must be forwarded within 4 administrative days.

(3) Responding facilities must impound all pertinent original documents and voice recordings, including both interphone and radio communications, and all available radar and computer data. Unless otherwise advised by the Litigation Liaison Office, retention must be in accordance with chapter 7.

(4) Particular attention must be given to the handling of voice recordings to avoid damage and tampering charges. Generally, the playback of such recordings should be limited to the minimum number of times necessary to make recorded copies and to meet the needs of the accident investigators.

(5) Responding facilities must furnish the requesting facility with one copy of pertinent records, certified indexes, and/or normal service statements. Information obtained from military facilities may not be in FAA format.

(6) Examples of pertinent documentation include but are not limited to FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice; FAA Form 8020-26, Personnel Statements; FAA Form 7230-4, Daily Record of Facility Operation; personnel logs; FAA Form 7230-10, Position Log (or automated equivalent); facility layout chart; flight progress strips; radar data; pilot reports (PIREP) and weather data; Significant Meteorological Information (SIGMET); Airmen's Meteorological Information (AIRMET); notice to airmen (NOTAM); FAA Form 7233-1, Flight Plan; video maps; nonpublished NOTAMs; and copies of operations letters, letters of agreement, and facility

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection › 72. Data Collection and Certification by Selected Facilities

memoranda. The determination of which information is pertinent will be made by the requesting facility manager based on the level of service provided.

d. The formal accident file must contain:

(1) The accident package.

(2) Voice recordings made in accordance with paragraph 93.

(3) FAA Form 8020-9, FAA Forms 8020-24 and 8020-25 (if applicable), 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.16A or via written direction from the Litigation Liaison Office. Pertinent information, may include, but not be limited to

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

(b) Quality Assurance Review (QAR).

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

(d) Letters of agreement.

(e) Facility directives.

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

e. Include a copy of transcripts (full or partial, as appropriate) and certified copies of recordings prepared by all involved FCFs in the FAA air traffic formal accident file, not package. When there is an accident/incident with no FAA air traffic involved, FCFs do not need to forward data. No other FCF documents will be retained in the FAA air traffic formal accident file without the permission of the FAA Accident Investigation Division or the Litigation Liaison Office.

f. The formal accident file must be labeled as described in paragraph 102a.

g. When notified by Flight Standards that an aircraft accident has been:

(1) Downgraded to an aircraft incident, the responsible originating facility (see paragraph 70) will assemble an informal accident file instead of a formal accident file and must notify all supporting facilities after coordination with the service center, or FSPO.

(2) Determined to be a nonoccurrence, the responsible air traffic facility (see paragraph 70) will coordinate with the appropriate service center, or FSPO regarding retention of documentation.

72. Data Collection and Certification by Selected Facilities

a. FAA FSS Facilities and FCFSS Facilities.

(1) 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 printout from its operating system.

(a) The facility must compile all pertinent EVR/Contact History data and produce two printouts.

(b) Certify one printout as the original and one printout as the copy. The certified copy may be retained electronically.

(2) The facility must include the certified copy in the accident file. The certified original may be kept in a separate secured area. The certified original must be retained for the same period as the accident package.

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

Chapter 4. Air Traffic Aircraft Accidents/Incidents Data Collection › 73. Radar and Computer Data

b. Facilities Not Providing ATC Services. When requested by the FAA IIC, the FAA Accident Investigation Division, the Litigation Liaison Office, Safety Investigations and Evaluations, 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. Although the air traffic facility will maintain an air traffic formal or informal file, other documentation as outlined in paragraphs 82 and 84 will not be required.

c. Air Traffic Control System Command Center (ATCSCC).

(1) When it has been determined by the FAA IIC, the Litigation Liaison Office, Safety Investigations and Evaluations, 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.

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

d. Domestic Events Network (DEN). When it has been determined by the FAA IIC, the Litigation Liaison Office, Safety Investigations and Evaluations, 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 Litigation Liaison Office.

73. Radar and Computer Data

a. Data Collection.

(1) For aircraft accidents/incidents or suspected aircraft accidents/incidents, pertinent computer data, such as Data Analysis and Reduction Tool (DART), Continuous Data Recording (CDR), and National Track Analysis Program (NTAP) must be extracted onto an electronic storage media (for example, diskette, computer diskette – recordable [CD-R], zip diskette, 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 protect original computer data from possible damage, arrangements must be made to re-record or reproduce all pertinent data as soon as possible after an accident/incident. The 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 recorded by the Host Computer System (HOST)/Standard Terminal Automation Replacement System (STARS)/Automated Radar Terminal System (ARTS) platforms 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 CDR data extracted from the STARS Data Reduction and Analysis Tool (DR&A) required to replay the event on a STARS Terminal Controller Workstsation display.

(b) Common Automated Radar Terminal System (CARTS) – retain a CDR Time Selected Output (CDTSO) so that the data can be replayed on the CARTS RETRACK system.

(c) HOST/En Route Automation Modernization (ERAM) – retain data so that the event can be replayed on a HOST/ERAM display or if replay capability is not available on the HOST system, then retain a SATORI playback file of the event along with the System Analysis Recording (SAR) and display system replacement (DSR) information.

(d) Airport Surface Detection Equipment (ASDE) and Safety Logic Systems – Retain data so that it can be replayed on the original system as well as be converted to other electronic formats (for example, .avi).

(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.

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

b. Radar and Computer Data Certification.

(1) A certification statement is signed by the manager of the air traffic facility, or the acting manager or support specialist. This certified data becomes the official printed historical document after the recording media has been returned to service.

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

(2) A certification statement is signed by the person at the aeronautical information system replacement (AIS-R) host facility that fulfills the data request:

"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]."

(3) All requests to the system maintenance organization manager for data will be through the air traffic facility manager or designee.

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

“Please note that the program we used to transfer this data in the host computer utilizes 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.”

74. Correction Memorandums

When it is discovered that data has not been collected in accordance with FAA orders and directives, a memorandum must be prepared to explain when it was discovered, why it happened, and the steps that will be taken to ensure the same error will not happen again.

75-79. RESERVED

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files › 81. Support Facilities

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 HNL-ATCT-0013 JUN-FSS-0044 OLM-FCT-0001 PRC-FCFSS-0022

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

c. FCFs retaining information in an air traffic informal or formal accident file must use the same accident number being used by the 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 more than one FCF vendor has created an air traffic informal or formal accident file, each vendor will utilize an accident file number for the vendor’s FCF preparing the informal or formal accident file.

81. Support Facilities

a. Facilities that provided normal services to the subject aircraft are those that did not have control over the aircraft just prior to or at the time of the accident, or have pertinent transmissions with the subject aircraft. After coordination with the facility responsible for preparing the aircraft accident file (see paragraph 70), these supporting facilities must submit a normal service statement. Forward the original document and retain a copy.

b. Those facilities providing normal services must provide a statement certified by the facility manager or acting manager that:

"All services provided by [name of facility] were normal, and there were no pertinent transmissions."

c. A certified index listing each document being held by the facility to support a normal service statement must also be included on a separate sheet (see paragraph 92 and appendix B).

d. Those facilities providing normal services must provide FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet), as described in paragraph 90b(11).

e. Facilities providing normal service statements are required to retain all pertinent documentation (see paragraph71c(6)).

f. Other than normal services:

(1) Supporting facilities must provide all documents as required in paragraph 71c, as appropriate, to the facility responsible for preparing the air traffic accident package.

(2) Supporting facilities must retain all radar and computer data as required in paragraphs 71-73.

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

(3) Supporting facilities must retain all items mentioned in the above sub-paragraph in an accident file for their facility using the responsible facility’s accident file number.

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

a. Content. The formal accident package must contain the accident report forms, all pertinent records, personnel statements, transcriptions of voice recordings, charts, and facility memoranda (see appendix B). Include items in the accident package as required. Copies of records from facilities other than the one originally reporting the accident or responsible for the preparation of the package must be obtained and included in the package, if pertinent.

b. Copies.

(1) FAA facilities providing hard copy documents to the preparing (holding) facility must submit one copy and retain the original. The copy must be forwarded to the facility preparing the formal accident file/package within 10 calendar days. Copies must not have original signatures (exception: facilities providing normal service statements; see paragraph 81b). The facility preparing the accident package must assemble the original package. Additionally, the facility must prepare four paper copies or an electronic copy.

NOTE– Upon coordination with the FAA IIC, the facility may elect to prepare electronic copies of accident packages for distribution.

(2) FCFs must prepare one copy and retain the original. The copy must be forwarded as described in paragraphs 82d. The copies must not include original signatures.

(3) Unless requested by the FAA Accident Investigation Division, the Litigation Liaison Office, or a 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.

c. Assembly. Assemble 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 or flight number, aircraft type, 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 must be placed on top of the completed package and delivered with the package. The Certification Memorandum is no longer a part of the formal accident package.

(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 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. Normal Service Statement(s) and Certified Indexes (see paragraph 81b 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 "for" to sign as the certifier.

(5) Section 4. FAA Form 7230-4, Daily Record of Facility Operation. Include FAA Form 7230-4 from the date of the accident and the date it was reported, if different.

(6) Section 5. Personnel Logs. 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 7230-10, Position Log, or automated equivalent.

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

(b) TRACON 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. 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. 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.

(10) Section 9. Flight Progress Strips and/or In-Flight Contact Record. Make sure the name of the facility providing the flight progress strips or contact records is indicated.

(11) Section 10. Transcriptions of Voice Recordings (see paragraph 94).

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

(13) Section 12. Personnel Statements (see paragraph 91).

(14) Section 13. 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, but is not limited, PIREPs, SIGMETs, AIRMETs, and weather-related NOTAMs. Certified weather may be obtained from the National Climatic Data Center. In Alaska, FAA air traffic facilities can also obtain certified weather for inclusion in a formal accident file from an associated FSS.

(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 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 12/27/10.”

(e) Air traffic facilities that do not take weather observations must obtain certified weather from the National Climatic Data Center.

(f) The FSS and FCFSS will use their respective weather product(s) to obtain weather.

(15) Section 14. Non-published applicable NOTAMs.

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

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

(18) Section 17. Other. Include any other materials deemed pertinent.

d. 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(ies) 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 Litigation Liaison Office within 45 calendar days of the accident.

(ii) After the Litigation Liaison Office 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.) 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 FSPO within 30 calendar days of the accident. After review, the FSPO will forward one copy of the package to the Litigation Liaison Office within 45 calendar days of the accident.

(ii) After the Litigation Liaison Office has reviewed and released the package, the AFSIAG must send two complete packages or one electronic package to the FAA IIC (the FAA Accident Investigation Division or FSDO, as appropriate). The FAA IIC must forward one copy to the NTSB within 60 calendar days of the accident.

(c) Should corrections to the FAA or FCT accident package become necessary, all changes must be distributed in the same manner as outlined in paragraphs 82d(1)(a) and 82d(1)(b). A memorandum from the facility manager or acting manager must accompany any change(s) with a complete explanation of the change(s).

(2) FCFSS. 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:

(a) 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 Litigation Liaison Office on a Quarterly Review Basis. If the package is not part of the Quarterly Review process, the FSPO will return the copy of the package to the facility for distribution to the FAA IIC who will then forward it to the NTSB within 60 calendar days after the accident. Quarterly Review periods include October, January, April, and July.

(b) 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 82d(2)(a). A memorandum from the FCF manager or acting manager must accompany any change(s) with a complete explanation of the change.

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files › 84. Informal Accident File Data Collection

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

83. Certification of the Air Traffic Aircraft Accident Package

a. An Information Memorandum addressed to the service center Director or the FSPO Manager from the facility manager, or acting facility manager, of the data collection facility must be prepared. The certification signature must be the same as the typed name. Do not use "for" to sign as the certifier. This memorandum will certify that the facility manager or acting facility manager is attesting to the completeness of the entire air traffic aircraft accident package. The memorandum will provide the following certification:

“I certify that air traffic aircraft accident package, [air traffic aircraft accident package number], has been reviewed and is complete.”

b. A copy of the certification memorandum will accompany the completed air traffic aircraft accident package that is forwarded to the service center or FSPO (see appendix B).

NOTE- The certification memorandum is not part of the accident package, but is retained in the accident file. If any corrections are made after the certification statement is made and signed, a new “Information Memorandum” must be created, signed and dated— summarizing the corrections made.

84. Informal Accident File Data Collection

a. When an aircraft accident/incident does not require data collection in accordance with paragraph 71, data must be retained in an informal file.

b. The facility retaining the informal file must notify other facilities that may have supporting data. Supporting facilities must forward a copy of the Certified Index to the responsible facility. The data that is maintained in a supporting facility must include the responsible facility’s informal file number.

c. The file must include the original:

(1) FAA Form 8020-3 (see paragraph 65).

(2) FAA Form 8020-9 (see paragraph 66).

(3) FAA Forms 8020-6 and 8020-6-1 (see paragraph 90).

(4) FAA Form 8020-11 (as appropriate) (see paragraph 115).

(5) FAA Forms 8020-24 (see paragraph 116) and 8020-25.

(6) FAA Form 8020-26 (see paragraph 91).

(7) FAA Form 7230-10, Position Logs.

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

(9) One certified copy of the recording in .wav format on CD-R or other storage medium, or two certified copies of the recording on cassette tape; one will be marked “Original Copy” and one will be marked “Working Copy” (see paragraph 93).

(10) Include a copy of all transcripts and certified copies of recordings prepared by all involved FCFs in the FAA air traffic informal accident file. No other FCF documents are to be retained in the FAA air traffic informal accident file without the permission of the FAA Accident Investigation Division or the Litigation Liaison Office.

(11) Radar and Computer Data (see paragraph 73).

(12) Certified Index.

(13) Other pertinent items.

Chapter 5. Formal and Informal Air Traffic Aircraft Accident Files › 85–89. RESERVED

d. Affix a label (maximum size 3" x 5") to the file. The label must be clearly marked "INFORMAL ACCIDENT FILE" with the facility accident number, aircraft registration or flight number, aircraft type, accident UTC date and UTC time, and the UTC date the file is to be destroyed.

e. Every page must reference the accident number and aircraft registration or flight number.

85–89. RESERVED

Chapter 6. › 90. FAA Form 8020-6, Report of Aircraft Accident

Chapter 6. Preparation of Forms, Personnel Statements, Certified Indexes,

Voice Recordings, and Transcripts

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

a. General.

(1) FAA Form 8020-6 is used to record and report information about aircraft accidents (see appendix A). This information will be used by FAA and other Government investigating bodies.

(2) The report must be typewritten in clear language. Any drafts must be destroyed at the time the typewritten FAA Form 8020-6 is signed.

(3) For any information that is unknown at the time this form is prepared enter “unknown.”

b. Form Instructions.

(1) Report Number. Reports must be numbered as described in paragraph 80.

(2) Block 1. Aircraft identification and type. If more than one aircraft is involved, list one aircraft identification and type in Item 1. List the additional aircraft information on the 8020-6-1. If there are more than two aircraft, list each additional aircraft’s information on the 8020-6-1.

(3) Block 2. Date/Time of Accident (UTC).

(4) Block 3. Location of Accident. City, state, and specify the location of accident (that is, location on airport, distance from runway, distance from prominent landmarks, street address, etc.). Be as specific as possible; however, do not use latitude/longitude.

(5) Block 4. Nature of Accident. A brief factual statement of the accident must be included if known. Examples: taxiing collisions, landed with gear up, crashed on final approach. When the information is not known or can only be surmised, enter "unknown."

(6) Block 5. Type of Flight. State the type of flight plan on which the aircraft was operating (VFR, IFR, SVFR, defense visual flight rules [DVFR], and no flight plan).

(7) Block 6. Flightcrew. If known, enter the name of each flightcrew member and flight attendant(s), his or her position, address (City and State only), and extent of injury (uninjured, injured, fatality, unknown). Give extent of injuries as known at time of report preparation.

(8) Block 7. Passenger Data. If known, include number aboard aircraft, number uninjured, numbered injured, and number fatalities. Do not include passenger names, addresses, and/or extent of injuries, or flightcrew information (see Block 6).

(9) Block 8. Aircraft Damage. (This should be obtained from FSDO.)

(10) Block 9. Property Damage. (This should be obtained from FSDO.)

(11) Block 10. Operational Status of Navigational Aids/Lights/Communication.

Continue reading ↓ 120 of 410 passages shown