Order JO 8020.16E Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting with Change 2
This change transmits revised pages to Federal Aviation Administration (FAA) Order JO 8020.16E, Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting.
Text read by OCR from a scanned file (2 of 176 pages). Check the original, as some words may be misread.
Order_JO_8020.16E_Change_2 › 7. Disposition of Transmittal.
CHANGE U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
JO 8020.16E
CHG 2
Air Traffic Organization Policy
Effective Date:
09/22/2025
SUBJ: Air Traffic Organization Aircraft Accident and Aircraft Incident Notification,
Investigation, and Reporting
1. Purpose of This Change. This change transmits revised pages to Federal Aviation Administration (FAA) Order JO 8020.16E, Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting.
2. Audience. This change applies to all Air Traffic Organization (ATO) employees and anyone using ATO directives to support activities associated with aircraft accident and aircraft incident notification, investigation, reporting, and documentation.
3. Where Can I Find This Change? This change is available on the FAA website at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications website at https://www.faa.gov/air_traffic/publications.
4. Explanation of Changes. Chapter 10, paragraph 3, Aircraft Accident File, was changed to require FAA facilities to upload audio recordings and radar files into the Accident Package Generator (APG) as a part of the aircraft accident file/package assembly.
5. Distribution. This change is distributed to the following ATO service units: Air Traffic Services; Technical Operations; Mission Support; System Operations Services; Safety and Technical Training; Flight Program Operations; the Air Traffic Safety Oversight Service; the William J. Hughes Technical Center; and the Mike Monroney Aeronautical Center.
6. Background. The ATO is moving toward an electronic accident package. The initial phase of development was the web-based APG. The next steps will be cloud storage of all data removing the requirement for facilities to store data. The initial phase of cloud storage will be facilities uploading copies of audio and radar data. This will allow the process to be verified and improvement to be made prior to transitioning to a completely electronic package.
7. Disposition of Transmittal. Retain this transmittal until it is superseded by a new basic order.
Distribution: Electronic Initiated By: AJI-0
8. Page Control Chart. See below.
PAGE CHANGE CONTROL CHART
Remove Pages Dated Insert Pages Dated
10-2 through 10-5 01/12/2024 10-2 through 10-5 09/22/2025
Order_JO_8020.16E_Change_2 › Dated
Franklin J. McIntosh Chief Operating Officer Air Traffic Organization
ii
CHANGE U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
JO 8020.16E
CHG 1
Air Traffic Organization Policy
Effective Date: 09/23/2024
SUBJ: Air Traffic Organization Aircraft Accident and Aircraft Incident Notification,
Order_JO_8020.16E_CHG_1 › 5. Distribution.
Investigation, and Reporting
1. Purpose of this Change. This change transmits revised pages to JO 8020.16E, Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting.
2. Audience. This change applies to all Air Traffic Organization (ATO) employees and anyone using ATO directives to support activities associated with aircraft accident and incident notification, investigation, reporting, and documentation.
3. Where Can I Find This Change? This change is available on the Federal Aviation Administration website at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications website at https://www.faa.gov/air_traffic/publications.
4. Explanation of Changes.
a. Chapter 8, paragraph 1, Radar Data Collection was changed to clarify that Playback Workstation (SkyRec) files are only retained for positions having pertinent services.
b. Chapter 8, paragraph 1.d.(5), no longer refers to Airport Movement Safety Area System (AMASS) and Terminal Automation Interface Unit (TAIU) data.
c. Changed Chapter 8, paragraph 1.d.(5)(c) to “Airport Surface Surveillance Capability (ASSC) – Extract ASSC logs and retain applicable radar map(s) current at the time of the aircraft accident or occurrence.”
d. Removed the current Sample Technical Performance Record (PAPI) in Chapter 14 and added Appendix E with updated examples to include Glideslope, Localizer, Medium Intensity Approach Light Setting with RAIL and runway-End Identifier Lights.
e. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record, was updated to remove the statement, “Accidents requiring telephone notification to Washington shall be made immediately following notification for emergency equipment and/or search and rescue.”
5. Distribution. This change is distributed to the following ATO service units: Air Traffic Services; Technical Operations; Mission Support Services; System Operations; Safety and Technical Training; Flight Program Operations; the Air Traffic Safety Oversight Service; the William J. Hughes Technical Center; and the Mike Monroney Aeronautical Center.
Order_JO_8020.16E_CHG_1 › Dated
6. Background. FAA Order JO 8020.16E became effective on January 12, 2024. The requirement in Chapter 8, paragraph 1.d.(2)(d) did not limit the retention of Playback Workstation (SkyRec) files to positions having pertinent services. Retaining Playback Workstation (SkyRec) files for all En Route Automation Modernization (ERAM) positions involved in an aircraft accident is unnecessary and creates additional workload for ERAM equipped air traffic facilities.
AMASS and TAIU have been removed from all sites, and documentation is in progress for decommissioning. References to these systems were removed and replaced with references to ASSC.
Additionally, the statement, “Accidents requiring telephone notification to Washington shall be made immediately following notification for emergency equipment and/or search and rescue” was incorrectly included on FAA Form 8020-3.
7. Disposition of Transmittal. Retain this transmittal until it is superseded by a new basic order.
8. Page Control Chart. See below.
PAGE CHANGE CONTROL CHART
Remove Pages Dated Insert Pages Dated
8-2 through 8-4 01/12/2024 8-2 through 8-4 09/23/2024
14-20 through 14-21 01/12/2024 14-21 09/23/2024
A-2 01/12/2024 A-2 09/23/2024
B-44 01/12/2024 B-44 09/23/2024
B-45 01/12/2024 B-45 09/23/2024
E-1 through E-5 09/23/2024 Katrina W Hall
Distribution: Electronic Initiated By: AJI-0
FAA_Order_JO_8020.16E (1)
This order prescribes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and aircraft incident notification, investigation, reporting, and documentation. It provides direction and guidance to ATO service units, service centers, service areas, offices, and facilities when they are called upon to perform or support aircraft accident investigations. All concerned personnel must familiarize themselves with the provisions of this order that pertain to their responsibilities and exercise their best judgment if they encounter situations not covered by the order.
This order cancels FAA Order JO 8020.16D, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, dated November 15, 2021.
This ATO order has been written in harmonization with FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting, and describes specifically the ATO’s roles and responsibilities in aircraft accidents, aircraft incidents, and occurrences as they pertain to notification, investigation, reporting, and data retention.
Timothy L. Arel Chief Operating Officer Air Traffic Organization
Effec tive Date:
01/12/2024
Air Traffic Organization Policy
SUBJ: Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting
ORDER NUMBER JO 8020.16E
FAA_Order_JO_8020.16E (1) › Explanation of Changes
E of C-1
Explanation of Changes
Direct questions through the appropriate facility/service center office staff to the Safety and Technical Training (AJI) Air Traffic Organization (ATO) Litigation Group (AJI-17). The explanation of changes provides background information, details of changes made for consistency, and paragraph changes detailed by chapter.
The Purpose of the Order was changed to read, “This order establishes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and incident notification, investigation, reporting, and documentation.” The words “and documentation” were added to include the accident package and file process.
a. The four major goals for the changes to the order are:
(1) Provide consistency between FAA Order JO 8020.16E and the Accident Package Generator (APG).
(2) Change the layout of the order to place chapters in the following sequence:
• General Information
• ATO Elements Involved in Notification, Investigation, and Reporting
• Definitions and Terms
• Initial Notification and Reporting Responsibilities
• FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26
• Aircraft Accident File/Package Process
• Voice Recordings and Transcripts
• Radar Data Collection, Radar/Computer/Weather Certification, and Radar Replay
• Review of Services and Review of Services Memorandum
• Aircraft Accident File/Package Development and Distribution
• Retention of Aircraft Accident Files
• Reporting and Notification Responsibilities for Pilot/Vehicle/Pedestrian Deviations
• Data Provided in Support of Pilot/Vehicle/Pedestrian Deviations and Air Traffic Occurrences
• Technical Operations Aircraft Accident Investigation Responsibilities
• Freedom of Information Act (FOIA) Request for Aircraft Accident/Incident and Occurrence Documents
(3) Reduce the amount of voice and radar data retained for aircraft accidents. The requirement to retain 30 minutes of voice and radar data before initial contact and after last
Explanation of Changes › 3. Chapter 3. Definitions and Terms.
E of C-2
contact was changed to 15 minutes. This provides consistency with the data retained for pilot deviations and other air traffic incidents.
(4) Eliminate duplicate requirements throughout the order. Once a requirement is stated the reader will be referred to that paragraph, when necessary, throughout the order.
b. Some general changes made throughout the order are listed below:
• Changed Litigation Support Group (LSG) to ATO Litigation Group (AJI-17).
• Changed Quality Assurance Group (QAG) to Service Area Safety Groups.
• Changed Notice to Airmen (NOTAM) to Notice to Air Mission (NOTAM).
• Changed Front Line Managers (FLM) to Operations Supervisor (OS).
• Removed references to the Compliance Services Group (CSG) and replaced with the Safety Intelligence and Response Group (SIRG) or Joint Air Traffic Operations Command (JATOC) Safety Event Network (JSEN) as appropriate.
1. Chapter 1. General.
a. This chapter contains several general paragraphs required for all FAA orders. Of special interest is Chapter 1, paragraph 7, which points readers to Chapter 3 where terms and definitions used in the order can be found.
2. Chapter 2. ATO Elements Involved in Notification, Investigation, and Reporting.
a. All elements covered in FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting, were removed from FAA Order JO 8020.16D. Responsibilities for the Safety and Technical Training, SIRG, Operations Centers, Safety Group, ATO Litigation Group, Quality Control Group, Technical Operations, and Flight Program Operations are included.
b. Safety and Intelligence Group notification details in Chapter 3, paragraph 3, were moved to Chapter 2, paragraph 1.
c. Chapter 3, paragraphs 3 and 4 Regional Operations Center (ROC) and Washington Operations Center (WOC) responsibilities were moved to Chapter 2, paragraph 2.
3. Chapter 3. Definitions and Terms.
a. This chapter defines terms and definitions that are necessary for understanding and applying the requirements of the order. This chapter defines the following:
• The difference in an aircraft accident file and aircraft accident package. • Call sign / aircraft identification as used in this order. • The difference in pertinent and routine services. • The difference in extracted and retained data. • The difference in a holding and supporting facility.
Explanation of Changes › 4. Chapter 4. Initial Notification and Reporting Responsibilities.
E of C-3
• An aircraft accident to include the definition of serious injury and substantial damage. • An unmanned aircraft system accident.
b. Four changes were made to this chapter:
(1) The paragraph for “Definitions” was placed before the paragraph for “Terms.”
(2) The definition of an ALNOT was moved from the “Terms” paragraph to the “Definitions” paragraph.
(3) Expanded the definition of Federal Contract Facilities to include the requirements from Chapter 3, paragraph 2 of FAA Order JO 8020.16D.
(4) Added the definition of an air traffic incident.
c. The following definitions and terms were updated:
• Air Navigation Facility • Aircraft • Aircraft Accident • Aircraft Incident • Mandatory Occurrence Report (MOR) • Pertinent Services • Pilot Deviation • Routine Services • Substantial Damage • Unmanned Aircraft System (UAS) • UAS Accident
4. Chapter 4. Initial Notification and Reporting Responsibilities.
a. This chapter is broken down into three major areas: what to report, when to report, and how to report.
b. FAA Order JO 8020.16D Chapter 3, paragraph 2 was moved to Chapter 3, paragraph 1k.
c. FAA Order JO 8020.16D Chapter 3, paragraphs 3 and 4 were moved to Chapter 2, paragraph 2.
d. FAA Order JO 8020.16D Chapter 3 paragraph 5b(3)(e) moved the statement, “Immediately notify the JSEN by telephone, in accordance with FAA Order JO 1030.3, if the incident is noteworthy or significant” under Chapter 4 paragraph 2b(2)(a) and (3)(a).
e. In paragraph 2b(3)(d) the requirement to include the call sign of the aircraft when making an entry on FAA Form 7230-4, Daily Record of Facility Operation, for an aircraft accident was added.
Explanation of Changes › 6. Chapter 6. Aircraft Accident File/Package Process.
E of C-4
f. Numerous editorial changes were made to the chapter.
5. Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26.
a. Paragraph 2b(15)(e) added two NOTES to clarify a person observing the aircraft accident on radar and/or other surveillance tool does not qualify as an eyewitness to the accident, and if there is an eyewitness, a brief factual description of what was observed must be included when completing FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet).
b. Paragraph 2b(17) added the requirement to “Type all entries using the standard capitalization of an English sentence, with the first letter uppercase and subsequent letter lowercase with exceptions such as proper nouns or acronyms.”
c. Paragraph 4a, “If requested by the Flight Standards District Office (FSDO), ATO Litigation Group, QCG, Flight Service Directorate, or JSEN, complete FAA Form 8020-11, Incident Report, for selected aircraft incidents,” was moved under the paragraph heading.
6. Chapter 6. Aircraft Accident File/Package Process.
a. The Review of Services and Review of Services Memorandum information was removed from this chapter and placed in Chapter 9.
b. The following was added to Chapter 6, paragraph 1 to clarify air traffic services as defined in this order:
(1) When an aircraft accident occurs, an aircraft accident file/package is required when air traffic services were provided. Air traffic services as defined in this order include services provided for the purpose of:
(a) Preventing collisions between aircraft and on the maneuvering area between aircraft and obstructions.
(b) Providing a safe, orderly, and expeditious flow of air traffic to include additional services as defined in FAA Order JO 7110.65.
(c) Supporting National Security and Homeland Defense missions.
(d) Providing emergency assistance to include contacting emergency services and emergency equipment (e.g., Airport Emergency Equipment, 911, Sheriff’s Office, City Police, Search and Rescue.)
(e) Providing Flight Information Service.
NOTE: For the purposes of this order an En Route facility that issued an ALNOT is NOT considered to have provided air traffic services if the ALNOT issuance was their only involvement.
E of C-5
c. This chapter defines the initial aircraft accident file/package process to include the following:
Explanation of Changes › 7. Chapter 7. Voice Recordings and Transcripts.
(1) The initial notification of the requirement for a facility to develop an aircraft accident file/package. Facilities are defined as Holding and Support Facilities and services are defined as Routine or Pertinent.
(2) The method for determining the facility responsible for final data collection.
(3) Holding and support facilities initial responsibilities.
(4) Data flow between facilities. FAA facilities DO NOT submit data to Federal Contract Facilities (FCFs). FCFs DO NOT submit data to FAA facilities or other vendor FCFs.
(5) Requirements for data collection from a facility that has air traffic data but did not provide Air Traffic Control (ATC) services.
d. In paragraph 3a the distinction between a holding facility with pertinent services and a holding facility with routing services was defined by adding paragraphs 3a(1)(a) and 3a(1)(b).
e. In paragraph 4 changed the word “data” to the word “documents.”
f. Removed paragraph 6f “Joint Air Traffic Operations Command (JATOC)” and paragraph 6g “Domestic Events Network (DEN).”
7. Chapter 7. Voice Recordings and Transcripts.
a. Instructions are provided for preparing voice recordings and partial/full transcripts. Prepare partial/full transcriptions when requested by the FAA Investigator In-Charge (IIC), ATO Litigation Group, Quality Control Group (QCG), Office of the Chief Counsel, or Flight Service Directorate.
b. Changed paragraph 1a(3) to read “Certified copies of the recording must include all communications, including time track, relevant to the aircraft accident from the period beginning 15 minutes before the initial contact and ending 15 minutes after last contact (Federal Contract Flight Services Station (FCFSS) facilities do not need to include any time before initial contact or after last contact).” Removed the NOTE following the paragraph.
c. Added the following NOTE after paragraph 1a(10):
NOTE: Storage media must only contain data from a single aircraft accident, aircraft incident, or occurrence.
d. Added National Airspace System (NAS) Voice Recorder (NVR) to paragraph 1b.
e. Removed the statement, “Part-time facilities should not turn off the Digital Audio Legal Recorder (DALR) system when the facilities close; however, air traffic managers should develop procedures to ensure that frequencies are not recorded when facilities are officially closed” from
Explanation of Changes › 9. Chapter 9. Review of Services and the Review of Services Memorandum.
E of C-6
paragraph 1b(1) as this is an FAA Order JO 7210.3, Facility Operation and Administration, requirement.
f. Added the JSEN to paragraphs 2a and 2b.
g. Changed paragraph 2f to read “A partial transcript must contain all recorded communication about the subject aircraft. Unless advised otherwise, partial transcripts include 15 minutes before initial contact until 15 minutes after the last contact (see Chapter 7, paragraph 1).”
h. Added “or appropriate incident number” to paragraph 2g(1)(b).
8. Chapter 8. Radar Data Collection, Radar/Computer/Weather Certification, and Radar Replay.
a. This chapter defines the requirements for the collection and certification of radar, computer, and weather data. Efforts were made to adequately define the requirement for radar data retention, but it is important to keep in mind the overriding requirement is “Retain radar and automation data necessary to recreate the event on the automation platform that recorded the data.”
b. Paragraph 1a clarified that radar and audio data start/stop timeframes must match in the Standard Terminal Automation Replacement System environments. In En Route Automation Modernization environments the radar time must encompass the start and end times of the audio data.
c. Changed paragraph 2a to read “Facilities providing radar data, but no voice data, must coordinate with the QCG for the time period of the radar data.”
d. Paragraph 1b was split into two paragraphs for better clarity.
e. In paragraph 1d examples of file names for various radar files were added.
f. In paragraph 1d(2) a separate paragraph for System Analysis Recording files, radar files, and Playback Workstation files was written.
g. Changed paragraph 4 to read “When a presentation is produced from raw data or extracted data, accompany the presentation with the name of the producer, the date made, the data used, and the software and the version used. These production credits may be listed in the presentation itself or placed on the label of the storage media (e.g., on the label of the CD-R). Any subsequent modifications, such as recording the SATORI presentation with Camtasia/Snag-It, also require production credits.”
9. Chapter 9. Review of Services and the Review of Services Memorandum.
a. Chapter 9 is a new chapter detailing the requirements for a review of services following an aircraft accident and the preparation of a Review of Services Memorandum. The chapter is broken down into the following:
Explanation of Changes › 10. Chapter 10.
E of C-7
• General Requirements • Conducting the Review of Services • Preparing the Review of Services Memorandum
10. Chapter 10. Aircraft Accident File/Package Development and Distribution.
a. The title of the Chapter was changed from “Aircraft Accident File/Package” to “Aircraft Accident File/Package Development and Distribution.”
b. FAA Form(s) 7230-10, Position Log(s), or automated equivalent. Holding and Supporting facilities with pertinent services are required to retain positions logs in the accident file. Only include position logs from positions providing pertinent services in the aircraft accident package. Place position logs in the chronological order of personnel listed in Block 12 of FAA Form 8020-6.
c. Paragraphs were laid out in the following order to provide clarity to the file and package content and process:
• Numbering of Aircraft Accident File/Package • Labeling the Aircraft Accident File/Package • Aircraft Accident File • Aircraft Accident Package General Instructions • Aircraft Accident Package Assembly • Aircraft Accident Package Content • Certification of the Aircraft Accident Package • Distribution • Changes to the Aircraft Accident Package After the Package Was Received
d. FIGURE 10-3-1. Aircraft Accident File was added to detail the contents of the accident file for the following types of facilities:
• Holding Facility Pertinent Services • Holding Facility Routine Services • Supporting Facility Pertinent Services • Supporting Facility Routine Services • Supporting Facility No Services with Data
e. FIGURE 10-6-1. Aircraft Accident Package was added to detail the contents of the accident package for the following types of facilities:
• Holding Facility Pertinent Services • Holding Facility Routine Services • Supporting Facility Pertinent Services • Supporting Facility Routine Services • Supporting Facility No Services with Data
Explanation of Changes › 15. Chapter 15.
E of C-8
11. Chapter 11. Retention of Aircraft Accident Files.
a. Numerous editorial changes were made. Also, much of the information in paragraph 1 was moved to a new paragraph 4, “Original Document Transfer.”
12. Chapter 12. Reporting and Notification Responsibilities for Pilot/Vehicle/Pedestrian Deviations.
a. Paragraph 1a was changed to require the report of a pilot deviation to match the reporting requirements in FAA Order 8020.11D (replaced ATC procedure or Code of Federal Regulations with violation of a Federal Aviation Regulation).
b. Detailed reporting requirements were removed with FAA Order JO 8020.16C. This order only details the initial notification to the pilot, the notification to the Supervisor or CIC, and the requirement for personnel statements.
13. Chapter 13. Data Provided in Support of Pilot/Vehicle/Pedestrian Deviations and Air Traffic Occurrences.
a. Removed paragraph 3b, “Facilities providing radar data, but no voice data, will coordinate for the time-period of the radar data. The QCG may assist in this coordination.” A facility providing radar data but no voice data would follow the instructions in the body of paragraph 3.
14. Chapter 14. Technical Operations Aircraft Accident Investigation Responsibilities.
a. The goal of Technical Operations activity is to ensure the continued safe operation of the NAS, investigate potentially involved facilities in a timely manner, restore operation of facilities removed from service in a timely manner, and provide appropriate aircraft accident-related facility documentation to appropriate authorities.
b. Specific responsibilities to accomplish this goal are outlined in this chapter.
15. Chapter 15. FOIA Request for Aircraft Accident/Incident and Occurrence Documents.
a. This chapter applies to Freedom of Information Act (FOIA) (5 U.S.C. 552) requests for records that were created or obtained by FAA facilities or personnel and under agency control at the time of the FOIA request.
b. Retention of the official FOIA files must be kept by the respective Service Center FOIA program office for six years from the date of the FOIA response. The files must include a copy of the responsive records and those records that were released with the FOIA.
i
Table of Contents
Explanation of Changes … E of C-1
Chapter 1. General Information … 1-1
1. Purpose of This Order … 1-1
2. Audience … 1-1
3. Where Can I Find This Order? … 1-1
4. What This Order Cancels … 1-1
5. Explanation of Changes … 1-1
6. Authority to Change This Order … 1-1
7. Definitions and Terms … 1-1
8. Related Publications … 1-1
9. Forms and Reports … 1-2
10. Safety Risk Management Analysis … 1-2
11. Distribution … 1-2
Chapter 2. ATO Elements Involved in Notification, Investigation, and Reporting … 2-1
1. Safety and Technical Training, Safety Intelligence and Response Group (SIRG). . 2-1
2. Operations Centers … 2-1
3. Safety and Technical Training, Service Area Safety Groups … 2-2
4. Safety and Technical Training, ATO Litigation Group … 2-3
5. Mission Support, Service Center, Quality Control Group (QCG) … 2-3
6. Technical Operations … 2-3
7. Flight Program Operations … 2-3
Chapter 3. Definitions and Terms … 3-1
1. Definitions Used in This Order … 3-1
2. Terms Used in This Order … 3-4
Chapter 4. Initial Notification and Reporting Responsibilities … 4-1
1. General … 4-1
2. Aircraft Accident and Aircraft Incident Notification and Reporting … 4-1
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 … 5-1
1. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record … 5-1
2. FAA Form 8020-6, Report of Aircraft Accident … 5-2
ii
3. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … 5-6
4. FAA Form 8020-11, Incident Report … 5-10
5. FAA Form 8020-26, Personnel Statement … 5-11
Chapter 6. Aircraft Accident File/Package Process … 6-1
1. Aircraft Accident File/Package Determination … 6-1
2. Air Traffic Facility Responsible for Final Data Collection … 6-2
3. Holding and Supporting Facilities … 6-4
4. Document Flow between Involved Facilities … 6-4
5. Additional Data Collection and Certification Information … 6-5
6. Data Collection Memorandum … 6-6
Chapter 7. Voice Recordings and Transcripts … 7-1
1. Copies of Voice Recordings … 7-1
2. Transcription of Voice Recordings … 7-3
Chapter 8. Radar Data Collection, Radar/Computer/Weather Certification, and Radar Replay … 8-1
1. Radar Data Collection … 8-1
2. Radar, Weather, and Computer Data Certification … 8-4
3. Litigation/Enforcement Replays and Plots … 8-6
4. Production Credits … 8-7
Chapter 9. Review of Services and the Review of Services Memorandum … 9-1
1. General Requirements … 9-1
2. Conducting the Review of Services … 9-1
3. Preparing the Review of Services Memorandum … 9-2
Chapter 10. Aircraft Accident File/Package Development and Distribution … 10-1
1. Numbering of Aircraft Accident File/Package … 10-1
2. Labeling the Aircraft Accident File/Package … 10-1
3. Aircraft Accident File … 10-2
4. Aircraft Accident Package General Instructions … 10-7
5. Aircraft Accident Package Assembly … 10-8
6. Aircraft Accident Package Content … 10-9
7. Certification of the Aircraft Accident Package … 10-11
iii
8. Distribution … 10-12
9. Changes to the Aircraft Accident Package After the Package Was Released. .. 10-13
Chapter 11. Retention of Aircraft Accident Files … 11-1
1. Security of Original Records … 11-1
2. Retention and Disposal of Aircraft Accident Records … 11-1
3. Holds Placed on Records … 11-2
4. Original Document Transfer … 11-2
Chapter 12. Reporting and Notification Responsibilities for Pilot/Vehicle/Pedestrian Deviations … 12-1
1. General … 12-1
2. FCF Responsibilities … 12-1
3. Air Traffic Facility Responsibilities … 12-1
4. Service Area Safety Group … 12-2
5. QCG Responsibilities … 12-2
Chapter 13. Data Provided in Support of Pilot/Vehicle/Pedestrian Deviations and Air Traffic Occurrences … 13-1
1. General Data Requirements … 13-1
2. Audio Data … 13-1
3. Radar and Computer Data … 13-1
4. Transcripts … 13-1
5. Replays/Plots … 13-1
6. Documentation … 13-2
7. Examples of Additional Air Traffic Data … 13-2
8. Retention … 13-3
Chapter 14. Technical Operations Aircraft Accident Investigation Responsibilities 14-1
1. General … 14-1
2. Air Navigation Facilities … 14-1
3. Overview of Technical Operations Activities … 14-1
4. Technical Operations Responsibilities … 14-1
5. Aircraft Accident Representative … 14-3
6. Process … 14-3
7. Preserving, Copying, and Releasing Reports and Records … 14-12
iv
8. Field Response for Post-Aircraft Accident Data … 14-13
9. Practice Aircraft Accident Exercise … 14-13
Chapter 15. FOIA Request for Aircraft Accident/Incident and Occurrence Documents … 15-1
1. Introduction … 15-1
2. Records Search … 15-1
3. Disclosure Determination … 15-1
4. Release of Records … 15-1
5. Documentation … 15-2
6. Retention of Records … 15-2
Appendix A. Forms Used By Air Traffic … A-1
A-1. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record … A-2
A-2. FAA Form 8020-6, Report of Aircraft Accident … A-3
A-3. FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) … A-4
A-4. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … A-5
A-5. FAA Form 8020-11, Incident Report … A-7
A-6. FAA Form 8020-26, Personnel Statement … A-8
Appendix B. Example of Aircraft Accident Package … B-1
B-1. Certification of the Aircraft Accident Package (Chapter 10, paragraph 7) … B-2
B-2. Labeling the Aircraft Accident File/Package (Chapter 10, paragraph 2) … B-4
B-3. Package Divider Sheets (Chapter 10, paragraph 4) … B-7
B-4. Table of Contents (Chapter 10, paragraph 5) … B-8
B-5. FAA Form 8020-6, Report of Aircraft Accident (Chapter 5, paragraph 2) … B-10
B-6. FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) (Chapter 5, paragraph 2) … B-11
B-7. Review of Services and the Review of Services Memoranda (Chapter 9) … B-16
B-8. FAA Form(s) 7230-4, Daily Record of Facility Operation (Chapter 10, paragraph 5). … B-23
B-9. Personnel Log(s) (Chapter 10, paragraph 5) … B-25
B-10. FAA Form(s) 7230-10, Position Log(s), or automated equivalent (Chapter 10, paragraph 5) … B-30
B-11. Facility Layout Chart (Chapter 10, paragraph 5) … B-31
B-12. Airport Diagram (Chapter 10, paragraph 5) … B-34
v
B-13. Flight Progress Strip(s) and/or In-Flight Contact Record(s) (Chapter 10, paragraph 5). … B-35
B-14. Transcription of Voice Recording(s) (Chapter 7, paragraph 2) … B-37
B-15. FAA Form(s) 8020-3, Facility Aircraft Accident/Incident Notification Record (Chapter 5, paragraph 1) … B-43
B-16. Weather Products (Chapter 10, paragraph 5) … B-46
B-17. NOTAMs (Chapter 10, paragraph 5) … B-50
B-18. FAA Form(s) 7233-2, Preflight Briefing Log, or automated equivalent (Chapter 10, paragraph 5) … B-50
B-19. FAA Form(s) 7233-1 Flight Plan, or automated equivalent (Chapter 10, paragraph 5) … B-50
B-20. Other (Chapter 10, paragraph 5) … B-50
B-21. Changes to the Aircraft Accident Package after the Package Was Released (Chapter 10, paragraph 9) … B-50
Appendix C. Storage Media Labeling … C-1
Appendix D. Original Documentation Transfer … D-1
Chapter 1. General Information › 8. Related Publications.
Chapter 1. General Information
1. Purpose of This Order. This order establishes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and incident notification, investigation, reporting, and documentation.
2. Audience. This order is intended for all ATO employees and anyone using ATO directives to support activities associated with aircraft accident and incident notification, investigation, reporting, and documentation.
3. Where Can I Find This Order? This order is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications website at http://www.faa.gov/air_traffic/publications/.
4. What This Order Cancels. FAA Order JO 8020.16D, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, dated November 15, 2021, and all associated notices are canceled.
5. Explanation of Changes. The significant changes to this order are identified in the Explanation of Changes page(s).
6. Authority to Change This Order. Authority for future revisions to this order is delegated to the Vice President, Safety and Technical Training (AJI). Submit proposed changes or additions to the ATO Litigation Group (AJI-17). Supplemental changes and requests for waivers to programs and policies transmitted by this order must receive prior approval through written requests to Safety and Technical Training.
7. Definitions and Terms. See Chapter 3, Definitions and Terms, for a complete list of terms and definitions used in this order.
8. Related Publications. The following publications are the primary references to be used in coordination with provisions of this order:
a. FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting.
b. FAA Order JO 7210.3, Facility Operation and Administration.
c. FAA Order JO 7210.632, Air Traffic Organization Occurrence Reporting.
d. FAA Order JO 7210.633, Air Traffic Organization (ATO) Quality Assurance (QA).
e. FAA Order JO 1030.3, Initial Event Response.
f. FAA Order JO 7110.65, Air Traffic Control.
g. FAA Order JO 7110.10, Flight Services.
9. Forms and Reports. Forms used by Air Traffic facilities for aircraft accident and incident notification, investigation, reporting, and documentation are in Appendix A, Forms Used by Air Traffic. Select samples of completed forms are in Appendix B, Example of Aircraft Accident Package.
Chapter 1. General Information › 11. Distribution.
10. Safety Risk Management Analysis. This order has no operational effect on the National Airspace System (NAS).
11. Distribution. Electronic Distribution.
Chapter 2. ATO Elements Involved in Notification, Investigation, and Reporting
1. Safety and Technical Training, Safety Intelligence and Response Group (SIRG). The ATO participates in the investigation of aircraft accidents and aircraft incidents when FAA Air Traffic Control (ATC) or aeronautical communications facilities are involved. For all aircraft accidents and significant aircraft incidents, the SIRG responds by disseminating timely, accurate, and unbiased information about the events. The SIRG also serves as the lead ATO representative responsible for ensuring that aircraft accidents and aircraft incidents involving ATO facilities or functions are investigated in a timely manner. The same requirements pertain to privately- and publicly owned and operated non-federal facilities. If a facility is operating within the NAS, it must comply with the same rules and regulations as the federal facility.
Chapter 2. › 2. Operations Centers.
a. When a notification of an aircraft accident or aircraft incident is received from any source, the Joint Air Traffic Operations Command (JATOC) Safety Event Network (JSEN) will contact the appropriate Regional Operations Center (ROC) for conferences or briefings as necessary. Notifications are completed in accordance with FAA Order JO 1030.3.
2. Operations Centers. Operations centers alert appropriate offices and assist in the notification process for aircraft accidents and aircraft incidents. When requested, a center establishes communication conferences to obtain, analyze, and disseminate information on aircraft accidents and aircraft incidents so that all FAA levels are informed, and decision-making can proceed in a timely manner.
a. Washington Operations Center (WOC). The WOC is a twenty-four-hours-a-day, seven-days-a-week operation. Its primary function is to maintain detailed knowledge of the NAS and events that impact civil aviation worldwide to provide Command and Control Communications and situational awareness to the FAA Administrator and Senior Leadership. The WOC continuously monitors activities in the NAS using various systems, both classified and unclassified, to ensure domain monitoring and the continuity of operations particularly during crises or emergencies. Communications are maintained with the industry and the intergovernmental network to support national level decision-making regarding aviation safety, national security, and homeland defense.
b. Regional Operations Centers. Coordinates communications responses related to aircraft accidents, emergencies, missing aircraft, hijackings, security threats, facility and system outages, airport closures, severe weather, earthquakes, and public information requests and complaints. During these events, the ROCs support FAA management, the National Transportation Safety Board (NTSB), law enforcement, airport operators, pilots, airlines, the National Weather Service (NWS), aircraft manufacturers, the Department of Transportation, the Federal Emergency Management Agency, the Department of Defense, and other federal agencies. This type of support requires the handling of routine, sensitive, and classified information. By providing the Command and Control Communications structure, systems, procedures, and equipment, the ROCs also support National Security Emergency Preparedness and Continuity of Operations programs.
Chapter 2. › 3. Safety and Technical Training, Service Area Safety Groups.
c. WOC and ROC Notification Responsibilities.
(1) When the reported aircraft accident/incident is one that requires ROC or WOC notification in accordance with Chapter 4, paragraph 2, the ROC officer must set up a telephone conference between the appropriate offices and the notifying party.
(2) When telephone notification of an aircraft accident/incident indicates that the use of a navigational aid may have been involved, the ROC officer must confer with Flight Program Operations and the Technical Operations Aircraft Accident Representative (TOAAR) located at the appropriate Control Center. When the aircraft accident/incident report indicates an FAA aircraft was involved, Flight Program Operations must be included in the conference call.
(3) If the report includes a fatal aircraft accident or an in-flight medical incapacitation of a flight deck crewmember, the ROC must immediately notify the appropriate Office of Aerospace Medicine.
(4) The ROC must assist the FAA Investigator-in-Charge (IIC) in establishing conference calls to include the WOC, NTSB, manufacturers, JSEN, TOAAR, Office of Airport Safety and Standards, Civil Aerospace Medical Institute, Aircraft Certification Directorates, and FAA William J. Hughes Technical Center, as necessary.
(5) The ROC must immediately notify the appropriate Regional Airports Division of Aircraft Accidents and Aircraft Incidents in their region.
(6) The WOC must notify the Environment, Energy, and Employee Safety Division within eight hours of all aircraft incidents covered by Occupational Safety and Health Administration reporting requirements when a fatality is involved.
(7) When events in a ROC’s area of responsibility may be of concern to other regions or centers, the ROC officer must provide information to other ROCs and/or the WOC. These events include:
(a) Aircraft accidents or aircraft incidents in which the aircraft operators’ operating certificate is held by another region or in which another region has the certification responsibility for that aircraft.
(b) Aircraft accidents or suspected aircraft accidents (overdue and missing aircraft) of aircraft that are carrying prominent persons from another region.
(c) Aircraft accidents involving injuries or death of FAA personnel from another region.
(d) Any other aircraft accident or aircraft incident, which, in the opinion of the Regional or Washington Operations Officer, is of official interest.
3. Safety and Technical Training, Service Area Safety Groups. The Service Area Safety Groups review Mandatory Occurrence Reports (MORs) and Preliminary Aviation Risk Identification and Assessment Reports and determine if events qualify as possible pilot/vehicle
Chapter 2. › 7. Flight Program Operations.
deviations. If the Service Area Safety Group determines there is a possible pilot/vehicle deviation, the event is forwarded for processing.
4. Safety and Technical Training, ATO Litigation Group. The ATO Litigation Group provides direction and oversight for data collection and retention related to aircraft accidents and aircraft incidents involving ATO services. The ATO Litigation Group orchestrates and communicates requirements with Air Traffic Services, AJI, and other offices within and outside the ATO. This order recognizes the priority of ongoing air traffic services, overlapping requirements of participants during investigations, and the need for collaboration. In situations not addressed by this order, the ATO Litigation Group provides direction.
5. Mission Support, Service Center, Quality Control Group (QCG). The QCG directs facility data collection and retention for aircraft accidents and aircraft incidents in local facilities. The QCG initiates, reviews, and processes aircraft accident packages in accordance with this order. Air traffic aircraft accident packages are submitted to the ATO Litigation Group for final review and release.
6. Technical Operations. Technical Operations’ 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 aircraft accident-related facility documentation.
7. Flight Program Operations. Flight Program Operations is responsible for scheduling a flight inspection of facilities after an aircraft accident or aircraft incident when requested by the National TOAAR (NTOAAR) or TOAAR. Flight inspection results are provided to the FAA IIC or TOAAR.
Chapter 3. Definitions and Terms › 1. Definitions Used in This Order.
Chapter 3. Definitions and Terms
1. Definitions Used in This Order.
a. Air Navigation Facility. Any facility used in, available for use in, or designated for use in aid of air navigation, including landing areas, lights, and any apparatus or equipment for disseminating weather information, for signaling, radio directional finding, or radio or other electronic communication, and any other structure or mechanism having a similar purpose for guiding or controlling flight in the air or the landing or takeoff of aircraft.
b. Air Traffic Incident. An air traffic incident encompasses all problems not affecting the aircraft directly; for example, near mid-air collisions; pilot, vehicle, or pedestrian deviations; and Traffic Alert and Collision Avoidance System Resolution Advisory occurrences. An air traffic incident differs from an aircraft incident.
c. Aircraft. Device(s) that are used or intended to be used for flight in the air, and when used in ATC terminology, may include the flight crew.
NOTE: For the purposes of this order, ultralight vehicle accidents and incidents are not investigated as aircraft accidents/incidents.
d. Aircraft Accident. An occurrence associated with the operation of an aircraft which takes place between the time any person boards the aircraft with the intention of flight and all such persons have disembarked and in which any person suffers death or serious injury or in which the aircraft receives substantial damage.
e. Aircraft Incident. An occurrence other than an aircraft accident associated with the operation of an aircraft, which affects or could affect the safety of operations.
f. Alert Notice (ALNOT). A request originated by a Flight Service Station (FSS) or an Air Route Traffic Control Center (ARTCC) for an extensive communication search for overdue, unreported, or missing aircraft.
g. Cardinal Minute. A number denoting each minute (0728:00, 0729:00, 0730:00, etc.).
h. Event. Something notable that happened in the NAS, which includes accidents, incidents, and occurrences.
i. FAA Investigator-in-Charge (IIC). FAA personnel assigned to supervise and coordinate all FAA employees participating in an investigation. In each investigation, the FAA IIC is responsible for the management of all FAA resources and for determining whether the facts of the investigation indicate that any of the nine FAA responsibilities were involved in the event. During an NTSB investigation, the FAA IIC serves as the party coordinator for the FAA. During an international investigation, the FAA IIC typically serves as the technical advisor to an NTSB investigator who has been assigned as the United States Accredited Representative to the foreign investigative authority in accordance with International Civil Aviation Organization (ICAO) Annex 13 protocol.
j. Fatal Injury. Any injury resulting in death within 30 days of the aircraft accident.
k. Federal Contract Facility (FCF). Federal Contract Towers (FCTs), Non-Federal Contract Towers (NFCTs), and Federal Contracted Flight Service Station (FCFSS) facilities. FCFs must follow the same procedures as those outlined for FAA Air Traffic facilities unless an exception to the requirement is made in this order or when specifically directed by Accident Investigation and Prevention (AVP) Accident Investigation and Recommendations (AVP-100), the FAA IIC, or ATO Litigation Group. This includes the preparation and retention of an aircraft accident file and package. The FCFs must not forward their aircraft accident file, documents, information, notes, recordings, copies of voice data, or similar data concerning an aircraft accident or incident to the FAA except as outlined in FAA Order JO 7210.633, FAA Order JO 1030.3, and Chapter 10, paragraph 8 of this order.
(1) Throughout this order, if “FAA” precedes the type of facility, the requirement applies to FAA facilities only. If the acronym “FAA” is not present, the requirement applies to all facilities (i.e., FAA facilities and FCFs).
NOTE: An FCT is considered an FCF and not an FAA facility.
EXAMPLES:
“…the FAA Air Traffic facility with jurisdiction over the flight when the aircraft accident occurred.” (This guidance would apply to only FAA facilities.)
“The Air Traffic facility first receiving notification of a known aircraft accident, or a suspected aircraft accident, must make and record initial notification using FAA Form 8020-3.” (This guidance would apply to both FAA facilities and FCFs.)
l. Flight Crew Member. A pilot, flight engineer, flight navigator, or flight attendant assigned to duty in an aircraft during flight time. For an Unmanned Aircraft System (UAS), any individual required to support flight operations is considered a crewmember, including visual observers, “internal” and “external” pilots, and sensor operators trained to work as part of an assigned crew.
m. Flight Service Directorate. The Flight Service Directorate is the central authority for all FSSs; it also serves as the Office of Primary Responsibility (OPR) for the FCFSS facilities. The Alaska Flight Service Information Area Group (AFSIAG) is the Flight Service Directorate’s designee for the FAA FSS, and it serves as the OPR for FAA FSS aircraft accident/incident notification, investigation, and reporting.
n. Mandatory Occurrence Report (MOR). A report of an occurrence involving air traffic services or technical operations services for which the collection of associated safety-related data and conditions is mandatory.
o. Navigational Aid. Any visual or electronic device, airborne or on the surface, which provides point-to-point guidance information or position data to aircraft in flight.
p. Occurrence. An abnormal event other than an incident or accident.
q. Operation of Aircraft. The use of aircraft for the purpose of air navigation, including the navigation of aircraft. Any person who causes or authorizes the operation of aircraft, whether with or without the right of legal control (in the capacity of owner, lessee, or otherwise) of the aircraft, must be deemed to be engaged in the operation of aircraft within the meaning of Title 49 United States Code.
r. Pilot Deviation. An action of a pilot that results in the violation of a regulation in Title 14 of the Code of Federal Regulations (CFR) or a North American Aerospace Defense (Command Air Defense Identification Zone) tolerance.
s. Serious Injury. Any injury associated with an aircraft accident that:
(1) Requires hospitalization for more than 48 hours, commencing within seven days from the date an injury was received.
(2) Results in a fracture of any bone (except simple fractures of fingers, toes, or nose).
(3) Causes severe hemorrhages or nerve, muscle, or tendon damage.
(4) Involves any internal organ.
(5) Involves second- or third-degree burns or burns of any degree affecting more than five percent of the body surface.
t. Substantial Damage. Damage or failure which adversely affects the structural strength, performance, or flight characteristics of the aircraft and which would normally require major repair or replacement of the affected component. Engine failure or damage limited to an engine if only one engine fails or is damaged; bent fairings or cowling; dented skin; small puncture holes in the skin or fabric; ground damage to rotor or propeller blades; and damage to landing gear, wheels, tires, flaps, engine accessories, brakes, or wing tips are not considered “substantial damage.”
u. UAS. A system that includes an unmanned aircraft, control station, and various mission elements used, or intended to be used, for flight. This includes all classes of airplanes, helicopters, airships, and translational lift aircraft that have no onboard pilot. The term UAS includes the airframe and all associated support elements, including the control station, communication links, equipment, and personnel necessary to conduct operations.
v. UAS Accident. An occurrence associated with the operation of any public or civil UAS that takes place between the time that the system is activated with the purpose of flight and the time that the system is deactivated at the conclusion of its mission, in which:
(1) Any person suffers death or serious injury; or
(2) The aircraft has a maximum gross takeoff weight of 300 pounds or greater and sustains serious damage.
Chapter 3. Definitions and Terms › 2. Terms Used in This Order.
NOTE: The NTSB definition of an accident (refer to 49 CFR § 830.2) is the definition of a UAS accident for FAA investigation purposes. UAS events that do not meet the NTSB definition should be investigated as occurrences or incidents. For UAS investigation information, refer to 14 CFR § 107.
NOTE: The accident reporting requirements for UAS operated under 14 CFR § 107, which are also applicable to public and civil Certificate of Waiver or Authorization holders, are described in 14 CFR § 107.9. These reporting requirements are separate from the investigation definitions above. The reporting of a UAS event does not automatically classify it as an accident.
2. Terms Used in This Order.
a. Aircraft Accident File. An aircraft accident file is completed by both holding and supporting facilities. The aircraft accident file contains all original documents, records, and reports relating to the aircraft accident. The holding facility aircraft accident file will contain the aircraft accident package.
b. Aircraft Accident Package. The aircraft accident package provides an overview of the aircraft accident, the events prior to the aircraft accident, the current environment at the time of the aircraft accident, and the operating environment from the air traffic perspective. The aircraft accident package contains documents from both the holding facility and supporting facilities. The final released aircraft accident package is retained at the holding facility.
c. Aircraft Accident Package Generator (APG). An automated and enterprise-based system that assists in aircraft accident package creation and form filling. The APG improves package production time, reduces the rate of errors, allows for data sharing, and provides a method of packaging data and process tracking.
d. Call Sign/Aircraft Identification. The combination of identifying letters, letters and numbers, or words assigned to an operator, office, activity, vehicle, or station for use in communication (as in the address of a message sent by radio).
e. Digital Signature. A digital signature is a technology specific process used to authenticate identity and verify the integrity of signed electronic records. When used as a signature documenting the signer’s intent, it provides evidence that a specific individual signed the electronic record and that the electronic record was not altered after being signed.
(1) FAA Employees/Contract Employees. Digital signatures are accomplished through the use of a Personal Identity Verification (PIV) card for all FAA employees and contract employees that have been assigned a PIV card.
(2) Contractors / Contract Employees. Digital signatures are accomplished through the use of an Adobe product with digital signature/certificate capability or equipment software for contract employees or employees working for contractors doing business with the FAA.
NOTE: A scanned representation of a written signature by itself is not an accepted form of a digital signature.
f. Extracted Radar Data. Data taken from the retained data (e.g., extracting a Plot Playback File from the retained data in the Standard Terminal Automated Replacement System (STARS)).
g. Holding Facility. The Air Traffic facility that is responsible for the final aircraft accident package.
h. Pertinent Services. Services that may be relevant to the unusual, urgent, or emergency situation (e.g., aircraft lands gear up and emergency services are notified) and/or all services that take place after Air Traffic becomes aware of, or is notified of, an unusual, urgent, or emergency situation by the flight crew or other sources (e.g., an aircraft reports a rough running engine and then crashed one mile short of the runway). All facilities that worked the aircraft after the rough running engine report would have pertinent services.
i. Retained Radar Data. Data that remains as close to the original state as possible. Retained data gives the ATO the ability to produce litigation / enforcement replays after the normal retention time for the data has passed.
j. Review of Services Memorandum. A memorandum from the manager of the holding or supporting facility certifying data in the aircraft accident file. The Review of Services Memorandum must indicate the type of service provided (pertinent or routine) and list each item in the aircraft accident file and/or package.
k. Routine Services. Services that take place before Air Traffic becomes aware of, or is notified of, an unusual, urgent, or emergency situation by the flight crew or other sources (e.g., an Instrumental Flight Rules (IFR) aircraft switched to the common traffic advisory frequency at an uncontrolled airport and receives substantial damage during the landing).
l. Supporting Facility. Any facility other than the holding facility that provided air traffic services to the aircraft and/or has data (e.g., radar) regarding the aircraft.
Chapter 4. Initial Notification and Reporting Responsibilities › 2. Aircraft Accident and Aircraft Incident Notification and Reporting.
Chapter 4. Initial Notification and Reporting Responsibilities
1. General. In order to provide authorities in the FAA, NTSB, or military services with information on aircraft accidents and aircraft incidents, follow notification procedures as outlined in this chapter.
a. Any FAA, FCF, or non-federal facility employee who becomes aware of an aircraft accident or aircraft incident must report the facts immediately to the nearest FAA Air Traffic facility (En Route, Terminal, or FSS) or ROC. The Air Traffic facility or ROC must immediately notify the JSEN.
b. To report an aircraft accident or aircraft incident when you do not have access to an FAA Air Traffic facility, ROC, or JSEN, as in the case of international events, use established channels such as the Department of State or the FAA Aeronautical Fixed Telecommunications Network or by any expeditious means appropriate to the aircraft accident or aircraft incident circumstances.
c. Report and make notifications for aircraft accidents and aircraft incidents involving UAS or spacecraft in the same manner as other aircraft accidents and aircraft incidents.
d. Use FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record, and FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice, to initiate preliminary notification of aircraft accidents and aircraft incidents. If requested by the Flight Standards District Office (FSDO), ATO Litigation Group, QCG, JSEN, or Flight Service Directorate, complete FAA Form 8020-11, Incident Report, for selected aircraft incidents.
2. Aircraft Accident and Aircraft Incident Notification and Reporting. This paragraph is divided into three categories for aircraft accidents and aircraft incidents: what to report, how to report, and when to report. The definition of an aircraft accident and aircraft incident can be found in Chapter 3, paragraph 1.
a. What to Report. Air Traffic facilities must report:
(1) All known and suspected aircraft accidents (including UAS, spacecraft, and military). An example of a suspected aircraft accident is the simultaneous unexplained loss of voice communications and radar contact with an aircraft.
(2) Aircraft accidents involving aircraft that departed another country and whose first point of intended landing was in the United States or aircraft that departed the United States for another country. If the aircraft accident occurs within United States controlled airspace or while receiving services from a United States Air Traffic facility, prepare an aircraft accident file and aircraft accident package as outlined in this order.
(3) All aircraft incidents, criminal or illegal acts reported to or by law enforcement agencies, emergency evacuations of aircraft, in-flight major component failures, and any aircraft incident that threatened or caused damage or injury to property, aircraft, or persons.
(4) The following special emphasis aircraft accidents/incidents:
(a) Aircraft accidents/incidents involving Presidential or Vice Presidential aircraft, members of Congress, or well-known people. Use secure communications in reporting when the President, Vice President, or members of Congress are on board the aircraft.
(b) Aircraft accidents/incidents in which hazardous materials are being transported.
(c) Aircraft accidents/incidents involving United States manufactured aircraft of foreign registry that occur outside the United States, its territories, and its possessions.
(d) Other aircraft accidents/incidents that the reporting facility or FSDO personnel believe warrant telephone notification to the JSEN. The JSEN, in turn, will notify the ROC, ATO QCG, WOC, and the Flight Service Directorate.
(5) Overdue and missing aircraft when:
(a) Neither voice/data communication nor radar contact can be established, and 30 minutes have passed since the estimated time of arrival over a specified or compulsory reporting point or at a clearance limit in your area or the clearance void time. If you have reason to believe that an aircraft is overdue before 30 minutes have passed, take the appropriate action immediately.
(b) Information is received that search and rescue procedures have commenced for an aircraft.
b. How to Report. The reporting process described below is when the facility listed in each paragraph is the first to receive notification of a known or suspected aircraft accident/incident:
(1) JSEN. Notify the FAA Air Traffic facility having ATC service responsibility for the area in which the aircraft accident occurred. If the facility is closed, contact the FAA facility with jurisdiction over the closed facility.
(2) ROC.
(a) Notify the JSEN.
NOTE: Immediately notify the JSEN by telephone in accordance with FAA Order JO 1030.3 if the aircraft accident/incident is noteworthy or significant.
(b) Notify the FAA Air Traffic facility having ATC service responsibility for the area in which the aircraft accident occurred. If the facility is closed, contact the FAA facility with jurisdiction over the closed facility.
(3) Air Traffic Facilities.
(a) Notify the JSEN.
NOTE: Immediately notify the JSEN by telephone in accordance with FAA Order JO 1030.3 if the aircraft accident/incident is noteworthy or significant.
(b) Record notifications on FAA Form 8020-3 and include handwritten notifications not listed on FAA Form 8020-3 (see Chapter 5, paragraph 1). There may be more than one FAA Form 8020-3 for an aircraft accident/incident. The Air Traffic facility having jurisdiction over the aircraft accident site, if different from the facility receiving initial notification, must also complete FAA Form 8020-3 if any notifications were made.
(c) Complete and transmit FAA Form 8020-9.
(d) Make an entry on FAA Form 7230-4, Daily Record of Facility Operation, using agency-approved automation methods or other means. In the text, include “Aircraft Accident” and the call sign. Include a reference to any associated MORs.
(e) Notify the NWS if known or suspected aircraft accidents resulted (or are likely to have resulted) in serious injury or death to persons or substantial damage to aircraft/property (see FAA Form 8020-3 in Appendix A for numbers). Base the initial notification on preliminary information.
(f) Instruct Technical Operations or other appropriate personnel to retain relevant data having a retention cycle of fewer than 15 days (e.g., En Route Automation Modernization (ERAM) workstation playback files must be retained within 24 hours, Integrated Terminal Weather System (ITWS), etc.).
c. When to Report. All aircraft accidents/incidents including UAS must be reported to the JSEN as soon as possible. The following aircraft accidents/incidents require immediate notification (this list is NOT all-inclusive) to the JSEN by telephone in accordance with FAA Order JO 1030.3. The JSEN notifies the ROC who in turn notifies the WOC, QCG, and Flight Service Directorate.
(1) Overdue and missing aircraft. (Issue an ALNOT in accordance with FAA Order JO 7110.65.)
(2) Known and suspected aircraft accidents/incidents involving air carrier, air taxi, or commuter aircraft, and/or involving aircraft operating under IFR or Special Visual Flight Rules (SVFR).
(3) Criminal acts reported to or by law enforcement agencies.
(4) Emergency evacuations of aircraft.
(5) Major in-flight component failure.
(6) Aircraft accidents/incidents involving the President, Vice President, members of Congress, or other well-known people. (Use secure communications in reporting when members of Congress are on board the aircraft.)
(7) Aircraft accidents/incidents in which hazardous materials are being transported.
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26
1. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record. This form may be developed electronically and is NOT generated by the APG.
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 1. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification…
a. General.
(1) All Air Traffic facilities (except contract FSSs) with geographical jurisdiction over an airport (including private airports) must develop and maintain a current FAA Form 8020-3 for each airport.
NOTE: Facilities may develop a generic FAA Form 8020-3 that may be used for airports with non-significant ATC operations and turbulence events, in-flight safety events, etc., that are not associated with a specific airport. Significant ATC operations are 25 or more takeoffs or landings within a year.
(2) Facilities with part-time jurisdiction over airspace designated to another facility must develop a separate FAA Form 8020-3 for each airport supported by the part-time facility.
(3) FAA Form 8020-3 must be updated annually or more frequently as information changes.
(4) The Air Traffic facility first receiving information of a known aircraft accident, or a suspected aircraft accident must make and record notifications on FAA Form 8020-3.
(5) There may be more than one FAA Form 8020-3 for an aircraft accident/incident. The Air Traffic facility having jurisdiction over the aircraft accident site, if different from the facility receiving initial notification, must also complete FAA Form 8020-3.
(6) If more than one FAA Form 8020-3 was used at the time of the aircraft accident, include all copies in the aircraft accident file/package.
(7) If the form does not have enough lines for contact numbers, a second page continuing the contact numbers may be attached.
b. Form Instructions.
(1) Enter the facility name.
(2) Enter the airport name.
(3) Enter the aircraft call sign in the upper right-hand corner.
(4) Enter the date of the accident.
(5) Enter the airport identifier.
(6) Enter comments at the bottom of the form.
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 2. FAA Form 8020-6, Report of Aircraft Accident.
(7) Include attached telephone number listings and handwritten notifications not listed on the form.
c. Contact Information.
(1) The order and number of calls will be determined by the situation involved.
(2) Lines one, two, and three are available to be used to identify contacts for emergency services and emergency equipment (e.g., Airport Emergency Equipment, 911, Sheriff’s Office, City Police, Search and Rescue).
(3) Line 4 – Safety Event Network (JSEN).
(4) Line 5 – Regional Operations Center (ROC) if instructed by the JSEN.
(5) Line 6 – Domestic Events Network.
(6) The following contacts must be listed below line six in the order best suited for the facility.
(a) Air Traffic Manager.
(b) Technical Operations.
(c) Additional Law Enforcement.
(d) NWS – 800-242-8194.
(e) Alternate Number for NWS – 800-242-8895.
(f) Military Authority.
(g) Airport Authority.
(h) Aircraft Operator.
(7) Additional contact information may be included as necessary.
2. FAA Form 8020-6, Report of Aircraft Accident. This form is completed through the APG.
a. General.
(1) FAA Form 8020-6 is used to record and report information about aircraft accidents. Only holding facilities complete this form.
(2) The report must be written in clear language. Destroy any drafts at the time that FAA Form 8020-6 is physically or digitally signed.
(3) For any information that is unknown at the time this form is prepared, enter “unknown.”
b. Form Instructions.
(1) Report Date. Enter the date the report was completed.
(2) Report Number. Reports must be numbered using the aircraft accident package/file number described in Chapter 10, paragraph 1.
(3) Name of Reporting Facility. Enter the name of the facility completing the report.
(4) Block 1. Aircraft identification and type. If more than one aircraft is involved, list one aircraft identification and type in Block 1. List each additional aircraft’s information on FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet). List aircraft types based on the following order of priority:
(a) The flight progress strip / in-flight contact form.
(b) FAA Order JO 7360.1, Aircraft Type Designators.
(c) The FAA aircraft registry site.
(d) The ICAO aircraft registry site.
(5) Block 2. Date/Time of Accident (UTC).
(6) Block 3. Location of Accident (required). List the city, state, and latitude/longitude (if known). Use standard latitude/longitude DD MM SS format when using latitude/longitude. The APG software can use latitude/longitude to automatically find the nearest weather reporting stations.
(7) Block 4. Nature of Accident. A brief factual statement of the aircraft accident must be included if known. Do not use language that suggests the causal and/or contributing factor(s) of the aircraft accident (the NTSB determines the cause of the aircraft accident). Some examples of factual statements would be taxiing collision, landed with gear up, landed off-airport, and crashed on final approach. When the information is not known or can only be surmised, enter “unknown.”
NOTE: The block for the factual statement will only accept 175 characters.
(8) Block 5. Type of Flight. State the type of flight plan on which the aircraft was operating (i.e., Visual Flight Rules (VFR), IFR, SVFR, or no flight plan).
(9) Block 6. Flight Crew. Enter the name of each flight crew member, the name of each flight attendant, and his or her position. Enter the city and state (if outside of the United States, use the closest city and International State Identifier). Enter the extent of his or her injuries
(uninjured, injured, fatality, or unknown). Give the extent of the injuries as known at the time of the report preparation. When the information is not known, enter “unknown.”
(10) Block 7. Passenger Data. Include number aboard aircraft, number uninjured, number injured, and number of fatalities. Do not include passengers’ names, addresses, extent of injuries, or flight crew information (see Block 6). When the information is not known or can only be surmised, enter “unknown.”
(11) Block 8. Aircraft Damage. (Obtained from FSDO and/or NTSB.)
(12) Block 9. Property Damage. Provide a brief description (chain link fence destroyed, airport signage damaged, etc.).
(13) Block 10. Operating Status of Navigational Aids/Lights/Communication. Provide a brief description (Instrument Landing System (ILS) out of service, Guard frequency unusable, etc.).
(14) Block 11. Weather Data. Write weather data in plain language. Spell numbers out. Use Coordinated Universal Time (UTC) date and UTC time for each weather report. Do not use the statement “weather not available” or “not applicable” if the date, time, and location of the aircraft accident are known. Aviation Routine Weather Report (METAR) remarks and Pilot Reports (PIREPs) are not appropriate in Block 11 but should be included in the weather products section.
NOTE: When collecting weather data in the APG for accidents in locations outside of the United States and its properties, the user can toggle between United States “states” and international “states.”
(a) Time: Enter the last reported weather observation at or prior to the time of the aircraft accident. In the next block, enter the first reported weather observation subsequent to the aircraft accident.
(b) Location: If conditions/reports are not available at the scene, identify and use the nearest reporting station. If this is an international weather station, use the ICAO state.
(15) Block 12. ATO Personnel Involved.
(a) List the names of personnel involved (first name, middle name, or initial, last name) in chronological order (from both holding and supporting facilities) of any person who provided pertinent services or was an eyewitness to the aircraft accident. This may include, for example, an Operations Manager (OM), Operations Supervisor (OS), and/or Controller-In- Charge (CIC) not signed on a control position or someone that responded to a point out request.
(b) Personnel names and positions of operation must match the personnel names and position of operation from the position logs.
(c) Do not list personnel that provided routine services (holding or supporting facility) in this block. There are two exceptions to this requirement:
i) FCF holding facilities do not list FAA or other vendor supporting facility personnel.
ii) FAA holding facilities do not list FCF supporting facility personnel.
(d) Place the operating initials for each controller to the right of their name and enclosed in parentheses (see Appendix B).
(e) List the facility involved.
(f) Indicate the position of operation occupied by each person.
(g) Check if the person listed was an eyewitness to the aircraft accident.
NOTE 1: Observing the aircraft accident on radar does not qualify a person as an eyewitness to the accident.
NOTE 2: If there is an eyewitness, provide a brief factual description of what was observed when completing FAA Form 8020-6-1.
(16) Block 13. Signature of Facility Manager. The facility manager or the acting facility manager must sign this block. Type the facility manager or the acting facility manager’s name in this item. The signature must be the same as the typed name. Do not use initials. Digital signatures may be used.
(17) Block 14. Chronological Summary of Flight (FAA Form 8020-6-1). All involved Air Traffic facilities that provided air traffic services, had communication, or contact regarding the subject aircraft, or that provided no services but have data, must complete Block 14. This provides a complete chronological summary of the flight that describes all relevant communications, emergency assistance, and other air traffic services provided to the aircraft.
(a) Type the aircraft accident date accompanied by the statement, “ALL TIMES BELOW ARE COORDINATED UNIVERSAL TIME UNLESS OTHERWISE SPECIFIED.”
(b) If the chronological summary involves more than one date, then type subsequent dates.
(c) Type all entries using the standard capitalization of an English sentence, with the first letter uppercase and subsequent letter lowercase with exceptions such as proper nouns or acronyms.
(d) Combine entries if they occurred in the same minute.
(e) Identify abbreviations prior to use (e.g., Dothan Airport (DHN) or Local Control (LC)).
(f) If there is insufficient space on the first page of the form, use the continuation sheets to list any additional information.
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 3. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice.
(g) At the end of the written report, type an underscore line completely across the page and type, “No More Follows” (see Appendix B) under the line.
3. 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 complete and distribute FAA Form 8020-9. (This must be accomplished within three hours of the detection of the known or suspected aircraft accident/incident.) This form is NOT generated by the APG.
a. General Instructions.
(1) The facility/office distributing the form enters the following information on the top of each page that will be distributed:
(a) The name of the facility/office preparing the form in the box labeled “FROM.”
(b) The name of the facility/office receiving the form in the box labeled “TO.”
(c) Date (UTC) the form is completed.
(d) Time (UTC) the form is completed.
(2) FAA Form 8020-9, Part 1. Complete for all known or suspected aircraft accidents/incidents.
(3) FAA Form 8020-9, Part 2. Complete when radio navigational aids, communications equipment, radar automated systems, or approach lights may have been or were involved. Notify appropriate Technical Operations personnel of the facilities potentially involved and use data provided by them to complete FAA Form 8020-9, Part 2.
(4) Enter “unknown” for any item unavailable when the form is prepared.
b. Aircraft Accident/Incident Preliminary Notice – Part 1.
(1) CODE A. Enter the name of the facility/office preparing the form.
(2) CODE B. AIRCRAFT INFORMATION.
(a) Box 1. Enter the aircraft registration number.
(b) Box2. Enter the make and model.
(c) Box 3. Enter the name of the operator. Include “FAA” in Code B3, OPERATOR OF AIRCRAFT, if the aircraft is owned or operated by the FAA, flown by FAA personnel on official duty, or utilized by FAA inspectors performing flight tests.
(d) Box 4. Enter the type of activity (i.e., air taxi, instruction, pleasure, etc.).
(e) Box 5. Provide a brief description of the circumstances surrounding the occurrence.
(f) Box 6. Enter the weather at the time of the occurrence.
(g) Box 7. Check the appropriate box describing the damage to the aircraft.
NOTE: Damage determinations are made by the NTSB or FSDO.
(3) CODE C. OCCUPANTS – INDICATE INJURIES: FATAL, SERIOUS, MINOR, NONE.
(a) Box 1. Enter the name and address of the pilot and the category of injury.
(b) Box 2. Enter the name of crew members and the category of injury.
(c) Box 3. Enter the number of passengers and the category of injury.
(4) CODE D. Enter the location of the occurrence.
(5) CODE E. Enter the UTC date and time of the occurrence.
(6) CODE F. Enter the name of the FAA IIC if known. Indicate the office notified (e.g., SW-FSDO-65) if the name is unknown.
(7) CODE G. FAA AIR TRAFFIC SERVICE SUMMARY OF FLIGHT HANDLING.
(a) Box 1a. Enter the last departure point for the flight.
(b) Box 1b. Enter the UTC date and time the aircraft departed.
(c) Box 1c. Enter the intended destination.
(d) Box 2. Enter the position of the last radio or radar contact with the aircraft.
(e) Box 3. Enter the last ATC clearance issued.
(f) Box 4. Check the appropriate box for the type of flight.
(g) Box 5. Check the appropriate box for a pilot briefing.
(h) Box 6. Enter any additional pertinent information.
(8) RECEIVED AT. Enter the name of the facility/office receiving the initial report.
(9) DELIVERED TO. Enter the name of the facility/office the initial information was distributed to.
(10) TIME. Enter the UTC time.
(11) RECEIVED VIA. Check the appropriate box (i.e., in person, radio, or telephone).
(12) RECEIVED BY. Signature of the name of the person receiving the information and his or her title.
(13) NOTE: Part 2. Check the appropriate box to describe the status of FAA Form 8020-9, Part 2 (i.e., on the other side, on separate form, or not required).
c. Aircraft Accident/Incident Preliminary Notice – Part 2.
(1) CODE H. AIRCRAFT INFORMATION.
(a) Box 1. Enter the aircraft registration number.
(b) Box2. Enter the make and model.
(c) Box 3. Enter UTC date and UTC time of the incident.
(2) CODE I. STATUS OF POTENTIALLY INVOLVED AIRWAYS FACILITIES.
(a) Box 1. Enter the facility type.
(b) Box 2. Enter the identifier of the facility/runway.
(c) Box 3. Indicate the status of the facility just prior to the occurrence.
(d) Box 4. Indicate the status of the facility at the time of the occurrence.
(e) Box 5. Indicate the status of flight inspections conducted.
(f) Box 6. In the remarks section, explain briefly any entry that is marked as abnormal or out of service.
(3) CODE J. STATUS REPORT RECEIVED FROM PILOTS OR OTHERS.
(a) Box 1. Enter the facility type.
(b) Box 2. Enter the identifier of the location/runway.
(c) Box 3. Enter the identification number of the aircraft and name of the person providing the report.
(d) Box 4. Enter the status of the facility.
(e) Box 5. Enter the UTC time of the observation.
(4) RECEIVED AT. Enter the name of the facility/office receiving the initial report.
(5) DELIVERED TO. Enter the name of the facility/office that the initial information was distributed to.
(6) TIME. Enter the UTC time.
(7) RECEIVED VIA. Check the appropriate box (i.e., in person, radio, or telephone).
(8) RECEIVED BY. Signature of the name of the person receiving the information and their title.
(9) NOTE: Part 1. Check the appropriate box to describe the status of FAA Form 8020-9, Part 1 (i.e., on the other side or on separate form).
d. Distributing Form and Data (Preliminary Message).
(1) The Air Traffic facility must distribute FAA Form 8020-9, Parts 1 and 2, as appropriate, to the ROC via fax or email within three hours of the detection of the known or suspected aircraft accident/incident. Suspected aircraft accidents include ALNOT cancellation due to the abandonment of a search for an overdue/missing aircraft that cannot be located. The form will then be forwarded, as necessary, to:
(a) FAA – WOC, Washington, D.C.
(b) NTSB – Washington, D.C.
(c) FAA Service Center QCG with jurisdiction over the area in which the aircraft accident/incident occurred. If the aircraft was under the control of any facility in another service center, other applicable service center(s) must be addressed.
(d) The Flight Service Directorate.
(e) Aviation Medicine (AAM) Aerospace Medical Research Division, AAM-600, Mike Monroney Aeronautical Center.
(f) United States Air Force Rescue Coordination Center, 650 Florida Avenue, Tyndall Air Force Base, Florida, 32403-5017.
(g) El Paso Intelligence Center, Texas.
(h) The appropriate civil aeronautical authority in accordance with ICAO Annex 13 for aircraft accidents involving aircraft of Canadian or Mexican registry.
(2) Immediately transmit by fax, email, or telephone any significant aircraft accidents/incidents (e.g., involving air carriers, air taxis, commuters, 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 distribute using this format when:
(a) An Air Traffic facility receives initial notification more than 24 hours after the aircraft accident/incident.
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 4. FAA Form 8020-11, Incident Report.
(b) There is an aerial application (agricultural) or industrial aircraft accident/incident.
(3) FSDO and NTSB notification is accomplished by the ROC.
(4) When the facility originating the message is at the same location as one or more of the above offices, immediately arrange delivery of a copy of FAA Form 8020-9 in accordance with local agreements.
(5) The facility originating the message, if not the facility responsible for preparing the aircraft accident file as determined in Chapter 6, paragraph 2, must forward a copy of FAA Form 8020-9 to the responsible facility. If the responsible facility cannot be determined, the QCG must make the determinations, notify the responsible facility, and furnish essential information.
(6) Provide the originating facility with a copy of FAA Form 8020-9 when a separate facility distributes the form.
e. Distributing Updates/Amendments.
(1) Update FAA Form 8020-9 as new and/or amended information is available. For example, send a subsequent message upon locating aircraft wreckage to revise the original message or to downgrade the aircraft accident to an aircraft incident. Use any of the following methods when updating FAA Form 8020-9.
(a) Place a single line through the updated or erroneous information and enter the new data.
(b) Write “Supplemental” at the top of the form.
(c) Enter the new information on a new FAA Form 8020-9. Include the aircraft identification, aircraft accident/incident date, and Item F information.
(2) Fax or email the updated information to the ROC, who will then forward to all recipients of the original message.
4. FAA Form 8020-11, Incident Report. If requested by the FSDO, ATO Litigation Group, QCG, Flight Service Directorate, or JSEN, complete FAA Form 8020-11 for selected aircraft incidents. This form is NOT generated by the APG.
a. Form Instructions.
(1) TO. The name of the facility/office receiving the form.
(2) FROM. The name of the facility/office preparing the form.
(3) TYPE OF INCIDENT. Enter the type of incident (e.g., emergency evacuation, parachute jumping).
(4) DATE. Enter the date of the incident.
(5) DAY or NIGHT. Check the appropriate box.
(6) INCIDENT NO. If FAA Form 8020-11 is being completed to support an MOR, pilot deviation, etc., use the incident number of the incident being supported. If FAA Form 8020-11 is being used to support an independent event number, document the event as described below:
Chapter 5. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 5. FAA Form 8020-26, Personnel Statement.
(a) Begin with the identifier of the facility,
(b) Followed by the year (last two numbers of the calendar year) and
(c) Ending with the incident number (two digits).
EXAMPLES:
Third independent FAA Form 8020-11 for Denver ARTCC in 2023 ZDV-23-03
First independent FAA Form 8020-11 Atlanta TRACON in 2023 A80-23-01
(7) AGENCY/AIRCRAFT IDENTIFICATION. Enter the aircraft identification number.
(8) NAME OF PERSONNEL OR PILOT. Enter the name of the pilot.
(9) SUMMARY OF INCIDENT. Summarize the incident with enough detail to permit a complete understanding. If appropriate, show the chronological order of events by citing the specific UTC time.
(10) REMARKS. List any records on file at the facility such as radar data, voice recordings, communications, or any other records pertaining to the incident.
(11) ATTACHMENTS. List copies of any records forwarded with the report.
(12) DATE. Enter the date that the form is forwarded.
(13) SIGNATURE OF FACILITY MANAGER. The signature must be the facility manager or acting facility manager.
5. FAA Form 8020-26, Personnel Statement. Complete personnel statements at Airport Traffic Control Towers (ATCTs) (tower cab positions) when the Service Area Safety Group categorizes the event as a potential pilot deviation. Personnel statements are not required for aircraft accidents. If personnel statements are completed for aircraft accidents, place them in the section titled “Other” in the Aircraft Accident Package. This form may be completed through the APG.
a. General.
(1) FAA Form 8020-26 is prepared and used to provide information concerning the circumstances that cannot be retrieved via some type of recorded data source. Facts concerning what was observed and what actions were taken may not have been completely captured. The purpose of the personnel statement is to provide any facts within your personal knowledge that
will provide a complete understanding of the circumstances surrounding the aircraft accident/incident. Speculations, hearsay, opinions, conclusions, and/or other extraneous data are not to be included in the personnel statement. The statement may be released to the public through the Freedom of Information Act (FOIA) or litigation activities including pretrial discovery, depositions, and actual court testimony.
(2) The text of the statement (Block 10) may be hand printed in blue or black ink or entered via keyboard. The accuracy of the statement is certified by the signature of the employee completing the form (Block 6). The personnel statement must not be edited. If additional space is needed, do not write on the back of the form. At the end of Block 10, write/type “page 1 of 2.” Attach a second FAA Form 8020-26 and write “continued from page 1” at the top. Sign and date the second form.
b. Prior to completing a personnel statement, the employee completing the statement must:
(1) Have the opportunity to review voice and data recordings and other relevant information.
(2) Be briefed that the statement must include only:
(a) Statements in the first person (e.g., “I am,” “I saw,” “I did”).
(b) Factual information regarding the occurrence. Opinions, conclusions, or other extraneous data must not be included.
c. Form Instructions.
(1) Block 1. Name of Reporting Facility.
(2) Block 2. Report Number. Number reports as described in appropriate paragraphs for the type of aircraft accidents/incident, MOR, or pilot deviation number.
(3) Block 3. Aircraft Identification and Type.
(4) Block 4. Location of Occurrence (city and state).
(5) Block 5. Date/Time of Occurrence (UTC).
(6) Block 6. Name. Name of the employee completing the statement (i.e., first name, middle name or initial, last name) and, in parentheses, his or her operating initials used on personnel logs and/or position logs.
(7) Block 7. Title. Title of the employee completing the statement (e.g., Air Traffic Control Specialist, OS, OM).
(8) Block 8. Position and Time (UTC). The position identifier and type of the operational position worked at the time of the occurrence and the times logged on and off (it must match FAA Form 7230-10 or automated equivalent).
NOTE: The facility may elect to have items one through eight completed prior to providing FAA Form 8020-26 to the employee for completion. If the facility elects to complete the form in advance, review the items with the employee prior to the employee signing the form.
(9) Block 9. Instructions. Ensure that this information is read and understood before completing the form.
(10) Block 10. Text of Statement. Indicate if the personnel statement is the original or a supplemental statement.
(11) Block 11. Signature. Once signed, the signature will certify the accuracy of the statement. Digital signatures are approved.
(12) Block 12. Date of Signature. The date that the original or supplemental statement was actually signed.
d. If it becomes necessary to make a correction when preparing a written personnel statement (due to a misspelled word or other editorial change), the employee preparing the statement must place a single line through the error and initial (actual initials, not operating initials) and date the change to the text. (In this case, the date will be the same date as Block 12’s “Date of Signature.”) Treat editorial changes made after the personnel statement has been signed as described above. However, any substantial changes or changes that may alter the meaning and/or context or personnel statements that have been digitally signed must be treated as a supplemental personnel statement and attached to the original document. Supplemental statements are prepared as described throughout this paragraph and must be marked as supplemental in Block 10. Attach supplemental statements to the original statement.
Chapter 6. Aircraft Accident File/Package Process › 1. Aircraft Accident File/Package Determination.
Chapter 6. Aircraft Accident File/Package Process
1. Aircraft Accident File/Package Determination. The ATO Litigation Group is the final authority for the determination of an aircraft accident file/package. The QCG or Flight Service Directorate will typically communicate the work assignment. For FAA facilities, the QCG will notify all holding and supporting facilities with a link to the APG to complete their portion of the aircraft accident package. The data required in the aircraft accident file/package may vary from the requirements in this order if directed by the QCG or Flight Service Directorate after coordination with the ATO Litigation Group. For some aircraft accidents, the ATO Litigation Group may communicate directly with air traffic facilities after notifying the QCG/Flight Service Directorate.
a. If a subsequent determination is made by the QCG that the event does not meet the definition of an aircraft accident, then standard data retention requirements apply.
NOTE: The determination and contents of the aircraft accident file/package may vary based on the type of event including turbulence, in-flight safety accidents/incidents, etc. The determination will be made by the QCG, Flight Service Directorate, and/or ATO Litigation Group.
b. When an aircraft accident occurs, an aircraft accident file/package is required when Air Traffic services were provided. Air Traffic services as defined in this order include services provided for the purpose of:
(1) Preventing collisions between aircraft and on the maneuvering area between aircraft and obstructions.
(2) Providing a safe, orderly, and expeditious flow of air traffic to include additional services as defined in FAA Order JO 7110.65.
(3) Supporting National Security and Homeland Defense missions.
(4) Providing emergency assistance to include contacting emergency services and emergency equipment (e.g., Airport Emergency Equipment, 911, Sheriff’s Office, City Police, Search and Rescue).
(5) Providing Flight Information Service.
NOTE: For the purposes of this order an En Route facility that issued an ALNOT is NOT considered to have provided air traffic services if the ALNOT issuance was their only involvement.
(6) For UAS, the determination for an aircraft accident file/package must also meet the definition of an Unmanned Aircraft Accident in Chapter 3, paragraph 1.
(7) In cases where no air traffic service was provided to the accident aircraft, yet Air Traffic became aware of the aircraft accident (from police or similar sources), then Air Traffic must report the aircraft accident in accordance with Chapter 4, paragraph 2. Retain notification forms and documentation in accordance with Chapter 11.
Chapter 6. Aircraft Accident File/Package Process › 2. Air Traffic Facility Responsible for Final Data Collection.
2. Air Traffic Facility Responsible for Final Data Collection.
a. The Air Traffic facility that meets the following criteria will be responsible for the final aircraft accident file/package (this includes aircraft accident files/packages created for turbulence events). This facility is the “holding” facility (see Figure 6-1, Determination of Air Traffic Facility Responsible for Final Data Collection).
(1) Aircraft on IFR flight plans under the control of an FAA-staffed facility – The FAA Air Traffic facility with jurisdiction over (i.e., authority for and/or working) the flight when the aircraft accident occurred.
(2) Aircraft on IFR flight plans under the control of a military-staffed facility – The ARTCC in whose area the aircraft accident occurred. The ARTCC will cooperate with the military by furnishing the required information to the assigned investigator through the air traffic representative. The ARTCC must obtain permission to release documents from the ATO Litigation Group through the appropriate service center QCG.
(3) Aircraft not on an IFR flight plan but in communication with an FAA facility – The FAA facility communicating with the aircraft when the aircraft accident occurred.
(4) Aircraft not in communication with an FAA facility at the time of the aircraft accident – The last FAA facility communicating with the aircraft.
NOTE: Communication may include two-way radio or telephonic communication with the pilot or inter/intra-facility coordination regarding the flight.
(5) Other Aircraft – The FAA Air Traffic facility having radar service responsibility for the area in which the aircraft accident occurred.
(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 and/or different vendor FCFs.
(a) The last FAA facility having communication with the aircraft for the flight will conduct the final collection of all aircraft accident information involving FAA facilities. No information from an FCF will be included in the FAA aircraft accident file/package.
(b) The last FCF facility that communicated with the aircraft will conduct the final collection of all aircraft accident 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. There is no exchange of data between FAA facilities and FCFs or different vendor FCFs.
NOTE: When both FAA facilities and FCFs have created an aircraft accident file/package, two separate aircraft accident file numbers must be used: an FAA facility number and an FCF number.
b. The ATO does not establish an aircraft accident file/package for agricultural, ultralight, balloon, and/or industrial aircraft accidents unless requested by AVP-100 or the FAA IIC, ATO Litigation Group, QCG, or Flight Service Directorate.
Determination of Air Traffic Facility Responsible for Final Data Collection
Type Aircraft Accident Responsible Facility Reference
Aircraft on IFR flight plan under the control of an FAA facility
FAA facility with jurisdiction over the flight
Paragraph 6-2a(1)
Aircraft on IFR flight plan under the control of a military staffed facility
ARTCC in whose area the aircraft accident occurred
Paragraph 6-2a(2)
Aircraft not on an IFR flight plan but in communication with an FAA facility
FAA facility having communication with the aircraft when the aircraft accident occurred
Paragraph 6-2a(3)
Aircraft not in communication with an FAA facility at the time of the aircraft accident
Last FAA facility having communication with the aircraft
Paragraph 6-2a(4)
Other Aircraft FAA Air Traffic facility with radar responsibility for the area in which the aircraft accident occurred
Paragraph 6-2a(5)
Aircraft that have not communicated with an FAA facility but have communicated exclusively with an FCF
The last FCF having communication with the aircraft. If more than one vendor is involved, the last FCF having communication with the aircraft for each vendor
Paragraph 6-2a(6)
Aircraft that have communicated with both an FAA facility and an FCF
Multiple facilities will be responsible for the final data collection. See paragraph 6-2a(7)(a) for FAA facility requirements. See paragraph 6-2a(7)(b) for FCF facility requirements
Paragraph 6-2a(7)
Figure 6-1: Determination of Air Traffic Facility Responsible for Final Data Collection
Chapter 6. Aircraft Accident File/Package Process › 4. Document Flow between Involved Facilities.
3. Holding and Supporting Facilities. The holding facility is responsible for final data collection. Supporting facilities are Air Traffic facilities that provided services for or had communication/contact with or regarding the accident aircraft.
a. Holding Facilities:
NOTE: The QCG will notify both holding and support facilities with a link to the APG in order to complete their portion of the package.
(1) A holding facility may have either pertinent or routine services.
(a) Pertinent services are services that may be relevant to the unusual, urgent, or emergency situation (e.g., aircraft lands gear up and emergency services are notified) and/or all services that take place after Air Traffic becomes aware of, or is notified of, an unusual, urgent, or emergency situation by the flight crew or other sources (e.g., an aircraft reports a rough running engine and then crashed one mile short of the runway). All facilities that worked the aircraft after the rough running engine report would have pertinent services.
(b) Routine services are those that take place BEFORE Air Traffic becomes aware of, or is notified of, an unusual, urgent, or emergency situation by the flight crew or other sources. The holding facility may only provide routine services to the aircraft and/or have data (e.g., radar data), but they are still responsible for the aircraft accident package. (E.g., an IFR aircraft switched to the common traffic advisory frequency at an uncontrolled airport receives substantial damage during the landing or an FAA radar facility retaining radar data for an FCF package.)
(2) Required to gather information from all same type (e.g., FAA facilities, same vendor FCFs) facilities along the route of flight. This requirement is communicated to supporting facilities by the QCG.
NOTE: FAA facilities do not support FCFs, and FCFs do not support FAA facilities or other vendor FCFs. In situations where FAA facilities and FCFs were involved in the same aircraft accident, the FAA facility and each FCF vendor prepares a package as the holding facility using an aircraft accident package number appropriate for their facility.
b. Supporting Facilities: May have pertinent services, routine services, or may not have provided services to the accident aircraft but have data (e.g., radar) regarding the aircraft (see Chapter 3, paragraph 2). The QCG, Flight Service Directorate, or the ATO Litigation Group may change a facility’s designation from having provided routine services to pertinent services.
4. Document Flow between Involved Facilities. Determine the appropriate documents to be forwarded to the holding facility by the type of services provided (routine or pertinent) and by the type of agencies involved (i.e., FAA, FCF, or military). Forward documents electronically when able. FAA facilities DO NOT submit documents to FCFs. FCFs DO NOT submit documents to FAA facilities or other vendor FCFs.
a. Supporting Facility with Routine Services. (This applies to documents submitted by FAA supporting facilities with an FAA holding facility or FCF vendor supporting facilities with same vendor holding facility.) Supporting facilities that provided routine services must submit
Chapter 6. Aircraft Accident File/Package Process › 5. Additional Data Collection and Certification Information.
their Review of Services Memorandum (see Chapter 9) and FAA Form 8020-6-1 to the holding facility within eight administrative days of notification of the aircraft accident. Forward the original Review of Services Memorandum and retain a copy in the aircraft accident file. Retain air traffic data of the services provided to (or about) the accident aircraft in the aircraft accident file using the holding facility’s aircraft accident file/package number.
b. Supporting Facility with Pertinent Services. (This applies to documents submitted by FAA supporting facilities with FAA holding facility or FCF vendor supporting facilities with same vendor holding facility). Supporting facilities that provided pertinent services must submit their Review of Services Memorandum (see Chapter 9) and FAA Form 8020-6-1, along with copies of all documents, as required in Chapter 6, paragraph 4, to the holding facility within eight administrative days of notification of the aircraft accident. Forward the original Review of Services Memorandum and retain a copy in the aircraft accident file. Retain air traffic data of the services provided to (or about) the accident aircraft in the aircraft accident file using the holding facility’s aircraft accident file/package number.
c. FAA Supporting Facilities That Did Not Provide Services but Have Relevant Data. Send the FAA holding facility FAA Form 8020-6-1 and a Review of Services Memorandum within eight administrative days of notification of the aircraft accident.
5. Additional Data Collection and Certification Information.
a. Military Facilities. Request information from military Air Traffic facilities that provided services and/or have data on the accident aircraft through the service center military air traffic representative. Permission to release documents must be obtained from the ATO Litigation Group through the appropriate service center QCG.
b. FAA FSS Facilities and FCFSS Facilities.
(1) FAA FSS and FCFSS facilities will, at times, be either the holding facility or supporting facility. In either case, the following applies:
(a) For data required by an FAA FSS/FCFSS for inclusion in an aircraft accident package or file or for use in an aircraft accident investigation, the facility must obtain an Event Reconstruction (EVR) or Contact History and Briefing History printout from its operating system.
(b) The facility must retain all relevant EVR/Contact History and Briefing History data.
(c) The data may be retained electronically.
(2) Retain separately in the aircraft accident file, but not as part of the actual aircraft accident package, any information that may have been relevant to the flight.
(3) Certify the data. See Chapter 8, paragraph 2, for examples.
c. Facilities Not Providing ATC Services. When requested by the FAA IIC, AVP-100, ATO Litigation Group, JSEN, QCG, Flight Service Directorate, or Air Traffic facility responsible for final data collection, any Air Traffic facility having relevant documentation (e.g., audio, radar data) in support of an aircraft accident investigation will retain the documentation in accordance with Chapter 11, paragraph 2. This only applies to Air Traffic facilities that provided no direct or indirect air traffic services to the aircraft in question (i.e., facilities that did not provide air traffic services but did have radar data). Although the Air Traffic facility will maintain an aircraft accident file, most other documentation outlined in Chapter 11, paragraph 2 will not be required.
Chapter 6. Aircraft Accident File/Package Process › 6. Data Collection Memorandum.
(1) The data must be certified. See Chapter 8, paragraph 2 for examples.
(2) Retain an aircraft accident file (see Chapter 11, paragraph 2).
6. Data Collection Memorandum. When it is discovered that data have not been collected and/or are no longer available to be collected in accordance with this order, a memorandum must be prepared and signed by the Air Traffic Manager to explain what was discovered and why it happened. Insert a copy of this memorandum in the section of the Accident Package that would have contained the data and place the original memorandum in the aircraft accident file.
Chapter 7. Voice Recordings and Transcripts › 1. Copies of Voice Recordings.
Chapter 7. Voice Recordings and Transcripts
1. Copies of Voice Recordings. Facilities use a variety of voice recording systems. When the recording system records voice data into its mechanism (i.e., hard drive, tape), this order refers to the voice data as the “recording.” The first copy of the recording is defined as the “Original Copy;” any subsequent copies are referred to as the “Working Copy.”
a. General Instructions. The term “contact” (as used in this paragraph) is defined as communication and/or coordination with or about the subject aircraft. Retained voice data must include all communications and/or coordination pertaining to the subject aircraft even if a transmission is not completed or acknowledged. This definition may be extended to include transmissions and/or coordination involving search and rescue efforts, crash fire rescue, “attention all aircraft” broadcasts, weather advisories, recorded phone lines, and all Automatic Terminal Information Service (ATIS) / Automatic Flight Information Service (AFIS) recordings made during the time that the subject aircraft was under ATC.
(1) Determine all recorded contact(s) regarding the subject aircraft. Protect the recording(s) from being altered, damaged, or lost.
(2) Produce and certify the “Original Copy” and “Working Copy(s).” Make additional copies from the “Working Copy.”
(3) Certified copies of the recording must include all communications, including time track, relevant to the aircraft accident from the period beginning 15 minutes before the initial contact and ending 15 minutes after last contact. (FCFSS facilities do not need to include any time before initial contact or after last contact.)
(4) Compressed digital formats (e.g., MP3, AAC, WMA) for certified copies of original voice data are not permitted.
(5) Check all certified copies for adequate time and quality of voice.
(6) Certify each position of operation separate and independent of other positions.
(7) A voice announcement preceding the “Original Copy” and “Working Copy” of the recording must be made using the following format as necessary to certify the copy:
“This copy is being prepared by [facility’s name; do not use abbreviations]. The subject concerns [type of aircraft accident, aircraft incident, occurrence] involving [aircraft identification] on [date, UTC] at approximately [time, UTC]. The position of operation being copied is [facility, position, e.g., Denver Tower local control, Miami Tower ground control, Denver Center Sector R34 Radar position].”
“I certify that the following is a true copy of the original recorded transmissions pertaining to the [type of aircraft accident, aircraft incident or occurrence]. My name is [name]. I am employed as [title] at [facility].”
(8) Each position of operation recorded will be preceded by a certification statement naming the position and the UTC start and stop times of the copy as follows:
“This portion of the copy concerns communications at the [position] during the period of [time, UTC] to [time, UTC] on [date, UTC].”
(9) Conclude the recording of each position with the following statement:
Continue reading ↓ 120 of 295 passages shown