Order JO 8020.16D Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting
This Order establishes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and incident notification, investigation, and reporting.
This document is cancelled. Cancelled by JO 8020.16E. Check the official source before relying on it.
Text read by OCR from a scanned file (23 of 156 pages). Check the original, as some words may be misread.
Distribution: Electronic Initiated By: AJI-0
This order prescribes Federal Aviation Administration (FAA) Air Traffic Organization (ATO) procedures and responsibilities for aircraft accident and aircraft incident notification, investigation, and reporting. It provides direction and guidance to ATO service units, service centers, service areas, offices, and facilities when they are called upon to perform 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.16C, Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting, dated December 14, 2018.
This is an ATO order that has been written in coordination with FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting (Office of Primary Responsibility Accident Investigation Division (AVP-100)), and describes specifically the ATO’s roles and responsibilities in aircraft accidents, aircraft incidents, and occurrences as they pertain to notification, reporting, and data retention.
Effective Date:
11/15/2021
Air Traffic Organization Policy
SUBJ: Air Traffic Organization Aircraft Accident and Aircraft Incident Notification,
Investigation, and Reporting
ORDER NUMBER JO 8020.16D
ORDER NUMBER JO 8020.16D
ii
Table of Contents
Chapter 1. General … 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-4
7. Terms and Definitions … 1-4
8. Related Publications … 1-4
8. Related Publications … 1-4
9. Forms and Reports … 1-44
10. Safety Risk Management Analysis … 1-44
11. Distribution … 1-44
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. Safety and Technical Training, Service Center, Quality Assurance Group (QAG) … 2-1
2. Safety and Technical Training, Service Center, Quality Assurance Group (QAG) … 2-1
3. Safety and Technical Training, Litigation Support Group (LSG) … 2-1
4. Mission Support Services, Service Center, Quality Control Group (QCG) … 2-1
5. Technical Operations … 2-1
6. Flight Program Operations … 2-1
Chapter 3. Initial Notification and Reporting Responsibilities … 3-1
Chapter 3. Initial Notification and Reporting Responsibilities … 3-1
1. General … 3-1
2. FCFs … 3-1
3. Safety and Intelligence Response Group … 3-2
4. Notification of Other Operations Centers … 3-2
5. Aircraft Accident and Aircraft Incident Notification and Reporting … 3-3
Chapter 4. Terms and Definitions … 4-1
1. Terms Used in the This Order … 4-1
1. Terms Used in the This Order … 4-1
2. Definitions Used in This Order … 4-2
iii
Chapter 5. Aircraft Accident File/Package Process … 5-1
1. Aircraft Accident File/Package Determination … 5-1
2. Determination of Air Traffic Facility Responsible for Final Data Collection … 5-1
3. Holding and Supporting Facilities … 5-4
4. Data Flow between Involved Facilities … 5-4
4. Data Flow between Involved Facilities … 5-4
5. Review of Services and the Review of Services Memorandum … 5-5
6. Additional Data Collection and Certification Information … 5-6
7. Data Collection Memorandum … 5-7
Chapter 6. Aircraft Accident File/Package … 6-1
1. Numbering of Aircraft Accident File/Package … 6-1
2. Content and Assembly of the Aircraft Accident File … 6-1
2. Content and Assembly of the Aircraft Accident File … 6-1
3. Content, General Instructions, and Assembly of Aircraft Accident Package. ... 6-3
4. Certification of the Aircraft Accident Package … 6-7
5. Distribution … 6-8
6. Review of Aircraft Accident Files … 6-9
7. Changes to the Aircraft Accident Package After the Package Was Released … 6-9
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 … 7-1
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 … 7-1
1. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record … 7-1
2. FAA Form 8020-6, Report of Aircraft Accident … 7-2
3. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … 7-5
4. FAA Form 8020-11, Incident Report … 7-10
4. FAA Form 8020-11, Incident Report … 7-10
5. FAA Form 8020-26, Personnel Statements … 7-11
Chapter 8. Voice Recordings and Transcripts … 8-1
1. Copies of Voice Recordings … 8-1
2. Transcription of Voice Recordings … 8-3
Chapter 9. Radar Data Collection, Radar/Computer/Weather Certification, and Radar Replay … 9-1
1. Radar Data Collection … 9-1
1. Radar Data Collection … 9-1
2. Radar, Weather, and Computer Data Certification … 9-3
3. Litigation/Enforcement Replays … 9-5
iv
4. Production Credits … 9-6
Chapter 10. Retention of Aircraft Accident Files … 10-1
1. Security of Original Records … 10-1
2. Retention and Disposal of Aircraft Accident Records … 10-1
3. Holds Placed on Records … 10-2
3. Holds Placed on Records … 10-2
Chapter 11. Reporting and Notification Responsibilities for Pilot Deviations .... 11-1
1. General … 11-1
2. FCF Responsibilities … 11-1
3. Air Traffic Facility Responsibilities … 11-1
4. QAG Responsibilities … 11-2
5. QCG Responsibilities … 11-2
Chapter 12. Data Provided in Support of Pilot Deviations and Air Traffic Occurrences … 12-1
Chapter 12. Data Provided in Support of Pilot Deviations and Air Traffic Occurrences … 12-1
1. General Data Requirements … 12-1
2. Audio Data … 12-1
3. Radar and Computer Data … 12-1
4. Transcripts … 12-1
5. Replays/Plots … 12-2
6. Personnel Statements … 12-2
7. Documentation … 12-2
8. Examples of Additional Air Traffic Data … 12-2
8. Examples of Additional Air Traffic Data … 12-2
9. Retention … 12-3
Chapter 13. Technical Operations & Flight Program Operations Aircraft Accident Investigation Responsibilities … 13-1
1. General … 13-1
2. Air Navigation Facilities … 13-1
3. Overview of Technical Operations Activities … 13-1
4. Technical Operations Responsibilities … 13-1
4. Technical Operations Responsibilities … 13-1
5. Aircraft Accident Representative … 13-3
6. Process … 13-4
7. Preserving, Copying, and Releasing Reports and Records … 13-13
8. Field Response for Post Aircraft Accident Data … 13-13
v
9. Practice Aircraft Accident Exercise … 13-13
Chapter 14. FOIA Request for Aircraft Accident/Incident and Occurrence Documents … 14-1
Chapter 14. FOIA Request for Aircraft Accident/Incident and Occurrence Documents … 14-1
1. Records Search … 14-1
2. Disclosure Determination … 14-1
3. Release of Records … 14-1
4. Documentation … 14-2
5. Retention of Records … 14-2
Appendix A. Forms Used By Air Traffic … A-1
Appendix B. Example of Aircraft Accident Package … B-1
Appendix B. Example of Aircraft Accident Package … B-1
Appendix C. Cassette Tape and Computer Diskette – Recordable (CD-R) and Digital Versatile Disc (DVD) Labeling … C-1
Appendix D. Original Documentation Transfer … D-1
Chapter 1. General
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, and reporting.
Chapter 1. General
2. Audience. This Order is intended for all ATO employees and anyone using ATO directives supporting activities associated with aircraft accident and incident notification, investigation, and reporting.
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.16C, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, dated December 14, 2018, including all associated notices, are canceled.
5. Explanation of Changes. This revision:
a. In Chapter 2, paragraph 1, updates the responsibilities for the Safety and Technical Training (AJI) Safety Intelligence and Response Group (SIRG).
b. In Chapter 3, paragraph 1.a. and subsequent paragraphs, changes the initial call for an aircraft accident or incident from the Regional Operations Center (ROC) to the Joint Air Traffic Operations Command (JATOC) Safety Event Network (JSEN).
c. In Chapter 3, paragraph 1.d., adds JSEN as a party that may request the completion of FAA Form 8020-11, Incident Report.
d. In Chapter 4, paragraph 2.c., updates the definition for an aircraft accident.
e. In Chapter 4, paragraph 2.f., adds the definition for an event.
f. In Chapter 4, paragraph 2.h., updates the definition of FAA Investigator-in-Charge (IIC) to match the definition in FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting.
g. In Chapter 4, paragraph 2.k., adds the definition for the Flight Service Directorate.
h. In Chapter 4, paragraph 2.l., adds the definition for an Incident.
i. In Chapter 4, paragraph 2.o., updates the definition of an Occurrence.
j. In Chapter 4, paragraph 2.q., updates the definition of a Pilot Deviation.
k. In Chapter 4, paragraph 2.t., updates the definition of an Unmanned Aircraft System (UAS).
l. In Chapter 4, paragraph 2.v., adds the National Transportation Safety Board (NTSB) definition for a UAS accident.
m. In Chapter 5, paragraph 5.i., adds voice data as an item to review when preparing the Review of Services memorandum.
n. In Chapter 5, paragraph 5.j., adds the pre-duty weather briefing as an item to review when preparing the Review of Services memorandum.
o. In Chapter 5, paragraph 7, adds two requirements: to insert a copy of the data collection memorandum in the section of the accident package that would have contained the data and to place the original memorandum in the aircraft accident file.
p. In Chapter 6, paragraph 1, adds Alaska Flight Service Station (FSS) as a distinct type when numbering packages.
q. In Chapter 6, paragraph 2.b.(1)(b), adds the requirement that radar and audio start/stop timeframes must match for radar and computer data when available.
r. In Chapter 6, paragraph 2.b.(1)(j), adds the pre-duty weather briefing as an item to include in the weather section of the aircraft accident package.
s. In Chapter 6, paragraph 3, clarifies the content of aircraft accident packages for holding and support facilities with either pertinent or routine services.
t. In Chapter 6, paragraph 3.b.(1), clarifies that the aircraft registration(s) or flight number(s) that should be used in the aircraft accident package are the aircraft registration(s) or flight number(s) that were in use with air traffic at the time of the accident. This should remain consistent throughout the aircraft accident package.
u. Adds direction to Chapter 6, paragraph 3.c.(9) to use only official FAA Airport Diagrams in the aircraft accident file and aircraft accident package, when possible.
v. Adds wording in the note following Chapter 6, paragraph 3.c.(9), to clarify that every effort should be made to retrieve the Airport Diagram that was in effect at the time of the accident. If the Airport Diagram included is not the Airport Diagram current at the time of the accident, include the diagram without date alterations along with a memorandum explaining the discrepancy.
w. Adds clarification to Chapter 6, paragraph 3.c.(12)(c), that any time notifications are made referencing an accident, FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record, must be completed.
x. Adds clarification to Chapter 7, paragraph 1.a.(1), that the requirement to develop FAA Form 8020-3 does not apply to contract FSSs.
y. Adds a note to Chapter 7, paragraph 1.a.(1), clarifying that facilities may develop a generic FAA Form 8020-3 that may be used for airports with non-significant Air Traffic Control
(ATC) operations and turbulence events, in-flight safety events, etc., that are not associated with a specific airport. Significant ATC operations are those with 25 or more takeoffs or landings within a year.
z. In Chapter 7 paragraph 1.c., adds contact information on FAA Form 8020-3 to include the JSEN.
aa. In Chapter 7, paragraph 2.b.(7), updates flight crew data to add instructions for entering the city and state if outside of the United States.
bb. Adds a note to Chapter 7, paragraph 2.b.(12), to clarify requirements when collecting weather data in the Accident Package Generator (APG) for accidents in locations outside of the United States and its properties.
cc. Updates the certification statement in Chapter 8, paragraph 1.a.(7).
dd. Updates and reformats Chapter 9 radar retention requirements for En Route Automation Modernization (ERAM) and Standard Terminal Automation Replacement System (STARS).
ee. Removes references to Common Automated Radar Terminal System (CARTS) in Chapter 9, paragraph 1.c.
ff. Adds a requirement in Chapter 9, paragraph 1.c.(1)(c), to keep a report/memorandum listing software build, the physical monitor (Terminal Control Workstation (TCW) / Tower Display Workstation (TDW)) where the Terminal Control Positon (TCP) was being used during the time of the accident, and adaptation version in use when the Continuous Data Recording (CDR) data was recorded.
gg. Adds paragraphs (1) and (2) to Chapter 10, paragraph 2.a., to clarify records retention for aircraft accident packages when there have been Freedom of Information Act (FOIA) requests.
hh. In Chapter 11, paragraph 1.a., clarifies when an employee must report that a pilot’s actions may have violated the Code of Federal Regulations (CFR), including Air Defense Identification Zone requirements contained in 14 CFR part 99, or an ATC procedure.
ii. Revises Chapter 13 at the request of Technical Operations.
jj. In Chapter 14, paragraph 1.c., adds a requirement to contact the ATO FOIA Team (AJI-172) manager for guidance on how the search for email records is to be conducted when a FOIA request is received that seeks email records.
kk. In Chapter 14, paragraph 2.b., adds a statement clarifying the Service Center FOIA program office will apply redactions to records prior to their release to the requester.
ll. Updates the definition of a FOIA file in Chapter 14, paragraph 4.
mm. Updates the responsible office for the retention of FOIA files in Chapter 14, paragraph 5.
6. Authority to Change This Order. Authority for future revisions to this Order is delegated to the Vice President of Safety and Technical Training (AJI-0). Submit proposed changes or additions to the ATO Litigation Support Group (LSG) (AJI-17). Supplemental changes and requests for waivers to programs and policies transmitted by this Order must receive prior approval through written requests to AJI.
7. Terms and Definitions. See Chapter 4, Terms and Definitions, 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, and reporting are in Appendix A, Forms Used by Air Traffic. Select completed examples of these forms are in Appendix B, Example of Aircraft Accident Package.
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
Chapter 2. ATO Elements Involved in Notification, Investigation, and Reporting
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. Refer to FAA Order JO 1030.3 for appropriate notification procedures.
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 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 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.
2. Safety and Technical Training, Service Center, Quality Assurance Group (QAG). The QAG reviews Mandatory Occurrence Reports (MORs) and determines if events qualify as possible pilot deviations. If the QAG determines there is a possible pilot deviation, the event is forwarded for processing.
3. Safety and Technical Training, Litigation Support Group (LSG). The LSG directs data collection and retention for aircraft accidents and aircraft incidents in the ATO. The LSG 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 LSG provides direction.
4. Mission Support Services, Service Center, Quality Control Group (QCG). The QCG directs 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 packages are submitted to the LSG for final review and release.
5. 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.
6. 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 Technical Operations Aircraft Accident Representative (NTOAAR) or Technical Operations Aircraft Accident Representative (TOAAR). Flight inspection results are provided to the FAA IIC or TOAAR.
Chapter 3. Initial Notification and Reporting Responsibilities
Chapter 3. 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, Federal Contract Facility (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 facility, Terminal facility, or FSS) or ROC. The air traffic facility (En Route facility, Terminal facility, or FSS) or ROC must immediately notify the Joint Air Traffic Operations Command (JATOC) Safety Event Network (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, the FAA Aeronautical Fixed Telecommunications Network, or any expeditious means appropriate to the aircraft accident or aircraft incident circumstances.
c. Report and make notifications for aircraft accidents and aircraft incidents involving Unmanned Aircraft Systems (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), LSG, QCG, JSEN, Flight Service Directorate, or Compliance Services Group (CSG), complete FAA Form 8020-11, Incident Report, for selected aircraft incidents.
2. FCFs (Federal Contract Tower (FCT), Non-Federal Contract Tower (NFCT), and Federally 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 the FAA Accident Investigation Division (AVP-100), FAA IIC, or LSG. This includes the preparation and retention of an aircraft accident file/package. The FCFs must not forward their aircraft accident file, documents, information, notes, recordings, and/or copies of voice data, etc., 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 6, paragraph 5 of this Order.
Throughout this Order, if the acronym “FAA” precedes the type of facility, the requirement applies to FAA facilities only. If “FAA” is not present, the requirement applies to all facilities (that is, 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 FAA facilities only.)
“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.)
3. Safety and Intelligence Response Group. When a notification of an aircraft accident or aircraft incident is received from any source, the JSEN must contact the appropriate offices and representatives for conferences or briefings as necessary. Notifications are completed in accordance with FAA Order JO 1030.3, Initial Event Response. The ROC and Washington Operations Center (WOC) will make the following notifications.
a. When the reported aircraft accident/incident is one that requires ROC or WOC notification in accordance with Chapter 3, paragraph 4, the ROC officer must set up a telephone conference between the appropriate offices and the notifying party.
b. 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 TOAAR located at the appropriate Operations Control Center (OCC). When the aircraft accident/incident report indicates an FAA aircraft was involved, Flight Program Operations must be included in the conference call.
c. If the report is of a fatal aircraft accident or an in-flight medical incapacitation of a cockpit crewmember, the ROC must immediately notify the appropriate Office of Aerospace Medicine.
d. The ROC must assist the FAA IIC in establishing conference calls to include the WOC, the NTSB, manufacturers, the CSG, the TOAAR, the Office of Airport Safety and Standards, the Civil Aerospace Medical Institute, Aircraft Certification Directorates, and the FAA William J. Hughes Technical Center, as necessary.
e. The ROC must immediately notify the appropriate Regional Airports Division of aircraft accidents and aircraft incidents in their region.
f. 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.
4. Notification of Other Operations Centers. When events in an 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 that, in the opinion of the Regional or Washington Operations Officer, is of official interest.
5. 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 4, paragraph 2.
a. What to Report. Air traffic facilities must report:
(1) All known and suspected aircraft accidents (including UAS, spacecraft, or 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 a foreign country and whose first point of intended landing was in the United States or aircraft that departed the United States for a foreign country. If the aircraft accident occurs within the jurisdiction of the United States or while receiving services from a United States air traffic facility, prepare an aircraft accident package and file it as outlined in this Order.
(3) All aircraft incidents involving criminal acts reported to or by law enforcement agencies, emergency evacuations of aircraft, and 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 ROC. The ROC, in turn, will notify the QCG, WOC, ATO CSG, and 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 that is not on a flight plan.
b. How to Report. Specific reporting instructions are provided below for when the first notification of a known or suspected aircraft accident/incident are received by the JSEN, the ROC, or an air traffic facility.
(1) JSEN. Notify the FAA air traffic facility having radar services 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. Notify the JSEN.
(3) Air traffic facilities.
(a) Notify the JSEN.
(b) Record notifications on FAA Form 8020-3 and include handwritten notifications not listed on FAA Form 8020-3 (see Chapter 7, paragraph 1.b.). 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 (see Chapter 7, paragraph 3).
(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 a reference to any associated MORs.
(e) Immediately notify the CSG and the WOC through the JSEN by telephone, in accordance with FAA Order JO 1030.3, if the incident is noteworthy or significant.
(f) Notify the National Weather Service (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.
(g) Instruct Technical Operations or other appropriate personnel to retain pertinent data having a retention cycle of fewer than 15 days (e.g., ERAM workstation playback files must be retained within 24 hours).
c. When to Report.
(1) Overdue and missing aircraft.
(a) Air traffic facilities must immediately notify the JSEN by telephone in accordance with FAA Order JO 1030.3. The JSEN notifies the ROC who in turn notifies the WOC, CSG, QCG, and Flight Service Directorate.
(b) Issue an alert notice (ALNOT) in accordance with FAA Order JO 7110.65.
(2) Air traffic facilities must immediately notify the JSEN by telephone of any of the following:
(a) Known and suspected aircraft accidents/incidents involving air carrier, air taxi, or commuter aircraft, and/or involving aircraft operating under instrument flight rules (IFR) or special visual flight rules (SVFR).
(b) Criminal acts reported to or by law enforcement agencies.
(c) Emergency evacuations of aircraft.
(d) Major in-flight component failure.
(e) Aircraft accidents/incidents involving Presidential or Vice-Presidential aircraft. (Use secure communications in reporting.)
(f) Members of Congress or other well-known people. (Use secure communications in reporting when members of Congress are on board the aircraft.)
(g) Aircraft accidents/incidents in which hazardous materials are being transported.
(3) All other aircraft accidents/incidents including UAS must be reported to the JSEN as soon as possible.
Chapter 4. Terms and Definitions
Chapter 4. Terms and Definitions
1. 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 documents, records, and reports relating to the aircraft accident. The holding facility aircraft accident file will contain the aircraft accident package.
1. Terms Used in This Order
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 and improves package turnaround time, reduces the rate of errors, allows for data sharing, and provides a method of package data and process tracking.
d. Alert Notice (ALNOT). A request originated by an FSS or an Air Route Traffic Control Center (ARTCC) for an extensive communication search for overdue, unreported, or missing aircraft.
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 the Personal Identity Verification (PIV) card for all FAA employees and contract employees that have been assigned a PIV card.
(2) Contract Employees/Contractors. Digital signatures are accomplished through the use of an Adobe product with digital signature/certificate capability or equipment software for contract employees and/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 STARS).
g. Holding Facility. The air traffic facility that is responsible for the final aircraft accident package.
h. Pertinent Services. 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, and/or services that may be relevant to the unusual, urgent, or emergency situation.
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.
l. Supporting Facility. Any facilities other than the holding facility that provided air traffic services to the aircraft and/or have data (e.g., radar) regarding the aircraft.
2. Definitions Used in This Order
a. Air Navigation Facility. Any facility used in, available for use in, or designated for use in the aid of air navigation, including landing areas, lights, and any apparatus or equipment for disseminating weather information, signaling, radio direction 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 during the landing or takeoff of aircraft.
2. Definitions Used in This Order
b. Aircraft. A device that is used or intended to be used for flight in the air. For the purposes of this order, ultralight vehicle accidents and incidents are not investigated as an aircraft accident/incident.
c. Aircraft Accident. An occurrence associated with the operation of an aircraft that takes place between the time any person boards the aircraft with the intention of flight and the time all persons have disembarked, and in which any person suffers death or serious injury, or in which the aircraft receives substantial damage.
d. Aircraft Incident. An occurrence other than an aircraft accident associated with the operation of an aircraft that affects or could affect the safety of operations. Usually associated with events resulting in minor aircraft damage.
e. Cardinal Minute. A number denoting each minute (0728:00, 0729:00, 0730:00, etc.).
f. Event. Something notable that happened in the NAS, which includes accidents, incidents, and occurrences.
g. 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.
h. Fatal Injury. Any injury resulting in death within 30 days of the aircraft accident.
i. Federal Contract Facility (FCF). FCTs, NFCTs, and FCFSS facilities.
j. Flight Crew Member. A pilot, flight engineer, flight navigator, or flight attendant assigned to duty in an aircraft during flight time. For 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.
k. 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 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.
l. Incident. An occurrence other than an accident, associated with the operation of an aircraft, that affects or could affect the safety of operations.
m. Mandatory Occurrence Report (MOR). An occurrence involving air traffic services for which the collection of associated safety-related data and conditions is mandatory.
n. Navigational Aid. Any visual or electronic device, airborne or on the surface, that provides point-to-point guidance information or position data to aircraft in flight.
o. Occurrence. An abnormal event other than an incident or accident.
p. 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.
q. Pilot Deviation. An action of a pilot that results in the violation of a Federal Aviation Regulation, including Air Defense Identification Zone requirements contained in 14 CFR part 99.
r. Serious Injury. Any injury associated with an aircraft accident that:
(1) Requires hospitalization for more than 48 hours, commencing within 7 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.
s. Substantial Damage. Damage or failure that adversely affects the structural strength, performance, or flight characteristics of the aircraft, and that would normally require major repair or replacement of the affected component. The following are not considered “substantial damage”: 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.
t. Unmanned Aircraft System (UAS). An unmanned aircraft and its associated elements related to safe operations, which may include control stations (ground-, ship-, or air-based), control links, support equipment, payloads, flight termination systems, and launch/recovery equipment. It consists of three elements: unmanned aircraft, control station, and data link.
u. UAS Accident (FAA Definition). Any operation of a small unmanned aircraft (excluding model aircraft) involving at least:
(1) Serious injury to any person or any loss of consciousness; or
(2) Damage to any property, other than the small unmanned aircraft, unless one of the following conditions is satisfied:
(a) The cost of repair (including materials and labor) does not exceed $500; or
(b) The fair market value of the property does not exceed $500 in the event of total loss.
v. UAS Accident (NTSB Definition). 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 substantial damage. (See 49 CFR part 830.2.)
Chapter 5. Aircraft Accident File/Package Process
Chapter 5. Aircraft Accident File/Package Process
1. Aircraft Accident File/Package Determination. The LSG directs air traffic facilities to produce aircraft accident files and packages. 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 in order to complete their portion of the accident package. Data collection may vary between FAA facilities and FCFs if directed by the QCG or Flight Service Directorate after coordination with the LSG. For some aircraft accidents, the LSG may communicate directly with air traffic facilities after notifying the QCG/Flight Service Directorate.
NOTE: The determination and contents of the aircraft accident file/package may vary based on the type of event including turbulence, in-flight safety incidents/accidents, etc. The determination will be made by the QCG, Flight Service Directorate, and/or LSG.
When an aircraft accident occurs, base the aircraft accident file/package determination on the level of air traffic service provided to the aircraft, including weather-related aircraft accidents when a weather briefing was provided within 24 hours of the aircraft accident. For UAS, the determination for an aircraft accident file/package must also meet the definition of an Unmanned Aircraft Accident in Chapter 4, paragraph 2. The phrase “level of air traffic service” denotes the amount and complexity of service provided by air traffic to the accident aircraft. The LSG is responsible for determining the level of air traffic service. The determination process normally flows through the QCG, FAA Control Tower Quality Assurance Group, or Flight Service Directorate. Routinely, the QCG/Flight Service Directorate will consult with the facilities and the QCG/Flight Service Directorate may consult with the LSG.
If a subsequent determination is made by the QCG that the event does not meet the definition of an aircraft accident, then retain data used in the investigation in accordance with Chapter 10, paragraph 2 (i.e., for 45 days).
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 3, paragraph 5. Retain notification forms and documentation in accordance with Chapter 10.
2. Determination of Air Traffic Facility Responsible for Final Data Collection
2. Determination of Air Traffic Facility Responsible for Final Data Collection
a. The air traffic facility that meets the following criteria will be responsible for the final aircraft accident file/package (this includes aircraft accident files/packages created for turbulence events). This facility is the “holding” facility (see Figure 5-2-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 LSG 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 services 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 that communicated with the aircraft for the flight. If more than one vendor is involved, the last FCF that communicated 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 that communicated 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/incident information involving FCFs of the same vendor. If more than one vendor is involved, the last FCF that communicated with the aircraft for each vendor will conduct a final collection. 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, LSG, QCG, or Flight Service Directorate.
FIGURE 5-2-1
FIGURE 5-2-1
Determination of Air Traffic Facility Responsible for Final Data Collection
Type of Aircraft Accident Responsible Facility Reference
Aircraft on IFR flight plan under the control of an FAA facility
FAA facility with jurisdiction over the flight
Para 5-2.a.(1)
Aircraft on IFR flight plan under the control of a military-staffed facility
ARTCC in whose area the aircraft accident occurred
Para 5-2.a.(2)
Aircraft not on an IFR flight plan but in communication with an FAA facility
FAA facility that communicated with the aircraft before the aircraft accident occurred
Para 5-2.a.(3)
Aircraft not in communication with an FAA facility at the time of the aircraft accident
Last FAA facility that communicated with the aircraft
Para 5-2.a.(4)
Other aircraft FAA air traffic facility with radar responsibility for the area in which the aircraft accident occurred
Para 5-2.a.(5)
Aircraft that have not communicated with an FAA facility, but have communicated exclusively with an FCF
The last FCF that communicated with the aircraft. If more than one vendor is involved, the last FCF that communicated with the aircraft for each vendor.
Para 5-2.a.(6)
Aircraft that have communicated with both an FAA facility and an FCF
Multiple facilities will be responsible for the final data collection. See para 5-2.a.(7)(a) for FAA facility requirements. See para 5-2.a.(7)(b) for FCF facility requirements.
Para 5-2.a.(7)
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, the accident aircraft.
a. Holding Facilities:
(1) Generally have pertinent services (those services that take place after air traffic becomes aware of, or is notified of, an unusual, urgent, or emergency situation by the flight crew or other sources). A holding facility may only provide routine services 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, an FAA radar facility retaining radar data for an FCF package).
NOTE: The QCG will notify the holding facility with a link to the APG in order to complete their portion of the package.
(2) Required to gather information from all same type facilities (e.g., FAA facilities, same vendor FCFs) along the route of flight (see Chapter 5, paragraph 4). This requirement is most often communicated to supporting facilities by the QCG (see Chapter 5, paragraph 2).
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 routine or pertinent services or may not have provided services to the accident aircraft but have data (e.g., radar) regarding the aircraft (see Chapter 4, paragraph 1). The QCG, Flight Service Directorate, or LSG may change a facility’s designation from having provided routine services to pertinent services. Supporting facilities must forward data to the holding facility as described in Chapter 5, paragraph 4.
NOTE: The QCG will notify all supporting facilities with a link to the APG in order to complete their portion of the package.
4. Data Flow between Involved Facilities. Determine the amount of data forwarded to the holding facility by the type of services provided (routine or pertinent) and by the type of agencies involved (FAA, FCF, or military). Forward data electronically when able. FAA facilities DO NOT submit data to FCFs. FCFs DO NOT submit data to FAA facilities or other vendor FCFs.
a. Supporting Facility with Routine Services (Data submitted by FAA supporting facilities with FAA holding facility or FCF vendor supporting facilities with same-vendor holding facility). Supporting facilities that provided routine services must submit their Review of Services Memorandum (see Chapter 5, paragraph 5) and FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet), as described in Chapter 7, paragraph 2, 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. 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 (Data 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 5, paragraph 5) and FAA Form 8020-6-1 as described in Chapter 7, paragraph 2. As applicable, forward copies of all data, as required in Chapter 6, paragraph 3, 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. 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 pertinent data. Send the FAA holding facility FAA Form 8020-6-1, a Review of Services Memorandum, and a copy of pertinent data within eight administrative days of notification of the aircraft accident.
5. Review of Services and the Review of Services Memorandum. Air traffic facilities along the route of flight (both holding and supporting facilities) must conduct a review of service to assess and gather data. They must retain all data pertaining to the handling of the accident aircraft, conduct the review within two administrative days of notification of an aircraft accident, and notify the holding facility of their service’s status (routine, pertinent, or no services but have data) by completing a Review of Services Memorandum. The memorandum certifies the data retained by involved facilities. The memorandum must list each item retained in the aircraft accident file/package regardless of whether the document is individually certified or not. The facility manager or acting facility manager must sign the memorandum using the following format:
“I certify that the following original/digital copies of the original are on file at this facility.”
The certification signature must be the same as the typed name. Do not use “for” to sign as the certifier. The signature must be over the certifier’s typed name, and title, and the name of facility. Digital signatures may be used. Supporting facilities send the original Review of Services Memorandum to the holding facility and keep a copy of the memorandum in the supporting facility’s aircraft accident file. Provide the holding facility with a Review of Services Memorandum, FAA Form 8020-6-1, and copies of all required data within eight administrative days of notification of the aircraft accident.
Examples of documentation that must be reviewed are listed below. Retention requirements are detailed in Chapter 10, paragraph 2.
a. FAA Form 8020-3, Facility Aircraft Accident/Incident Notification Record.
b. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice.
c. FAA Form 7230-4, Daily Record of Facility Operation.
d. Personnel logs.
e. FAA Form 7230-10, Position Log, or automated equivalent.
f. Facility layout charts.
g. Flight progress information and strips if printed.
h. Radar data.
i. Voice data.
j. Pre-duty weather briefing.
k. Pilot reports (PIREPs) and weather data (if available, Center Weather Advisories, Weather System Wide Access Capability, Terminal Area Forecasts (TAFs), etc.).
l. Significant Meteorological Information (SIGMET).
m. Airmen’s Meteorological Information (AIRMET).
n. Notices to Airmen (NOTAMs) and non-published NOTAMs.
o. FAA Form 7233-1, Flight Plan.
p. Video maps.
q. Copies of procedures (Standard Instrument Departures (SIDs) / STARSs) that the aircraft was flying or assigned at the time of the aircraft accident.
r. Copies of operations letters, letters of agreement, and facility memoranda.
6. 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.
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 pertinent 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 pertinent to the flight.
(3) Certify data. See Chapter 9 and Appendix B, Review of Services Memorandum, for examples.
e. Facilities Not Providing ATC Services. When requested by the FAA IIC, AVP-100, the LSG, the CSG, the QCG, the Flight Service Directorate, or the air traffic facility responsible for final data collection (see Chapter 5, paragraph 1), any air traffic facility having any pertinent documentation (e.g., audio, radar data) in support of an aircraft accident investigation will retain the documentation in accordance with Chapter 10. 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 service but did have radar data). Although the air traffic facility will maintain an aircraft accident file, most other documentation outlined in Chapter 6, paragraph 2 will not be required. The data must be certified (see Chapter 9, paragraph 2 and Appendix B, Review of Services Memorandum, for examples).
f. Joint Air Traffic Operations Command (JATOC). When the FAA IIC, LSG, CSG, QCG, or Flight Service Directorate determines that the JATOC may have information pertinent to an aircraft accident, the JATOC will be requested to retain data, documentation, and/or copies of recordings in accordance with this Order and local directives.
(1) The JATOC must provide data, documentation, and/or copies of recordings as outlined in this Order.
(2) Certify data. See Chapter 9, paragraph 2 and Appendix B, Review of Services Memorandum for examples.
(3) Retain an aircraft accident file (see Chapter 6, paragraph 3).
g. Domestic Events Network (DEN). When the FAA IIC, LSG, CSG, QCG, or Flight Service Directorate, determines that the DEN may have information pertinent to an aircraft accident, the DEN will be requested to retain data, documentation, and/or copies of recordings when coordinated with the ATO LSG.
(1) The DEN must provide data, documentation, and/or copies of recordings as outlined in this order.
(2) Certify data. See Chapter 9, paragraph 2 and Appendix B, Review of Services Memorandum, for examples.
(3) Retain an aircraft accident file (see Chapter 6, paragraph 3).
7. Data Collection Memorandum. When it is discovered that data have not been collected and/or are no longer available 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 6. Aircraft Accident File/Package
Chapter 6. Aircraft Accident File/Package
1. Numbering of Aircraft Accident File/Package.
a. The APG application will automatically generate a number for an aircraft accident file/package. Aircraft accident files/packages begin with the year (last two numbers of the calendar year), followed by the aircraft accident file/package number (three digits), and then the identifier for the facility (e.g., ZDV). Alaska FSSs will end with “-FSS” following the facility identifier (e.g., FAI-FSS). If the facility is an FCF, the aircraft accident file/package number will end with the appropriate contract type (FCT, NFCT, or FCFSS). Separate each element with a hyphen.
EXAMPLES:
Third aircraft accident file/package for Denver ARTCC in 2022 22-003-ZDV
First aircraft accident file/package for Front Range FCT in 2023 23-001-FTG-FCT
Fourth aircraft accident file/package for Atlanta TRACON in 2023 23-004-A80
Second aircraft accident file/package for Fairbanks FSS in 2022 22-002-FAI-FSS
Second aircraft accident file/package for Washington FCFSS in 2022 22-002-DCA-FCFSS
First aircraft accident file/package for Mohave NFCT in 2023 23-001-MHV-NFCT
b. Supporting FAA facilities retaining information in an FAA aircraft accident file must use the same aircraft accident number used by the holding facility preparing the aircraft accident file/package (see Chapter 5, paragraph 3).
c. Supporting same vendor FCFs retaining information in an aircraft accident file must use the same aircraft accident number used by the holding FCF preparing the aircraft accident file/package (see Chapter 5, paragraph 3).
d. 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.
e. When different FCF vendors have each created an aircraft accident file/package, then the different vendors will use their own aircraft accident file/package number. Different vendors will not share the same aircraft accident file/package number.
2. Content and Assembly of the Aircraft Accident File. The holding and supporting facility’s aircraft accident file must be labeled as described in Chapter 6, paragraph 3.
a. The holding facility’s aircraft accident file must contain:
(1) An electronic or hard copy of the aircraft accident package.
(2) Voice recordings and copies made in accordance with Chapter 8, paragraph 1.
(3) Radar data and computer data (see Chapter 9). When available, radar and audio start/stop timeframes must match.
(4) FAA Form 8020-9 and all other pertinent documents and material gathered or created as part of, or subsequent to, the initial investigation unless specifically excluded by FAA Order JO 8020.16 or written direction from the LSG. Pertinent information in addition to the items required in the aircraft accident package may include:
(a) Charts (e.g., minimum vector altitude (MVA) maps, approach plates).
(b) MORs.
(c) Covered Event Review.
(d) Letters of Agreement.
(e) Facility directives.
(f) Email or other communications containing exchanges of information relevant to the facts of the aircraft accident.
b. The supporting facility’s aircraft accident file must contain, as applicable:
(1) Supporting facility with pertinent services:
(a) Voice recordings and copies (see Chapter 8, paragraph 1).
(b) Radar data and computer data (see Chapter 9). When available, radar and audio start/stop timeframes must match.
(c) FAA Form 8020-6-1.
(d) Review of Services Memorandum.
(e) Transcription of voice recording(s) when requested.
(f) FAA Form 7230-4.
(g) Personnel log(s).
(h) FAA Form(s) 7230-10.
(i) Flight Progress Strip(s) and/or In-Flight Contact Record(s).
(j) Weather products including the pre-duty weather briefing.
(k) Additional information may include:
i) Charts (e.g., MVA maps, approach plates).
ii) MORs.
iii) Covered Event Review.
iv) Letters of Agreement.
v) Facility directives.
vi) Email or other communications containing exchanges of information relevant to the facts of the aircraft accident.
(2) Supporting facility with routine services:
(a) Voice recordings and copies (see Chapter 8, paragraph 1).
(b) Radar data and computer data (see Chapter 9). When available, radar and audio start/stop timeframes must match.
(c) FAA Form 8020-6-1.
(d) Review of Services Memorandum.
(e) Flight Progress Strip(s) and/or In-Flight Contact Record(s).
(f) Email or other communications containing exchanges of information relevant to the facts of the aircraft accident.
(3) Supporting facility with no services but that did have data:
(a) All pertinent data, documentation, and information (e.g., radar).
(b) FAA Form 8020-6-1.
(c) Review of Services Memorandum.
(d) Email or other communications containing exchanges of information relevant to the facts of the aircraft accident.
3. Content, General Instructions, and Assembly of Aircraft Accident Package. Both holding and supporting facilities will use the data/documents/records from their aircraft accident file to assemble an aircraft accident package that will become a part of the aircraft accident file.
a. Content.
(1) Holding Facilities:
(a) Pertinent Services – all records described in paragraph 3.c. below.
(b) Routine Services – all records described in paragraph 3.c.(1)–3.c.(3), 3.c.(13), and 3.c.(17) below. Additional sections may be added as needed.
(2) Supporting Facilities:
(a) Pertinent Services – all records described in paragraph 3.c. below.
(b) Routine Services – the aircraft accident package will normally only contain FAA Form 8020-6-1 and the Review of Services Memorandum (see Chapter 5, paragraph 3).
(3) From military facilities with routine or pertinent services, the aircraft accident package will contain applicable equivalent documents when supplied by the military.
(4) All classified or security sensitive information and/or documentation and information protected under the Privacy Act (e.g., home, cellular, airport, military, and emergency personnel/offices) must be redacted or blacked out from all copies unless requested by AVP, the LSG, or other competent authority. When redacting, do not “white out.” It must be obvious to the reader that the document has been altered.
(5) Only the original aircraft accident file and/or package at the originating air traffic facility will retain the original information and/or documentation.
b. General Instructions. Facilities are required to use the APG to assemble aircraft accident packages (the respective service center QCG is responsible for initiating the package in the APG and notifying both the holding and support facilities). The facility must retain an electronic copy of the aircraft accident package. Retain any original paper components used to produce the electronic package in the aircraft accident file. General instructions for the assembly of the aircraft accident package are as follows:
(1) For the aircraft registration(s) or flight number(s), use the registration(s) or flight number(s) that were in use with air traffic at the time of the accident. Remain consistent throughout the aircraft accident package.
(2) Include a table of contents page that lists each section’s number and content.
(3) Insert a sheet of plain paper between each section with the section number and title of the section centered on the page.
(4) If the information called for by a specific section is unavailable or not pertinent, use that section number for the next required item so that the numbers remain in sequence.
(5) All information in each section must be in chronological order beginning with the first facility having contact with the aircraft and then in order of involvement.
(6) All information must match and be consistent throughout the package. If a discrepancy exists, include a memorandum of explanation in the affected section of the aircraft accident package.
(a) Personnel listed in Section 2, FAA Form 8020-6 (Block 12), must match those in Section 5, Personnel Logs.
(b) Positions of operation identification and type in Section 6, FAA Form 7230-10, and Section 10, Transcription of Voice Recordings and Personnel Statements, must match.
(c) Weather data entered on FAA Form 8020-6 must match the weather data listed in Section 12, Weather Products.
(7) Every page, including the section divider sheets, must reference the aircraft accident number and aircraft registration(s) or flight number(s). The aircraft accident number and aircraft registration(s) or flight number(s) must be in the lower left-hand footer.
(8) Use only one side of the paper when assembling the paper copy of the aircraft accident package.
c. Assembly. Assemble the package in the following order:
(1) Label. The cover page must be labeled in the following manner:
(a) First Line. “Original” or “Copy.”
(b) Second Line. Aircraft Accident Package.
(c) Third Line. Aircraft accident number.
(d) Fourth Line. Aircraft registration(s)/flight number(s) and aircraft type(s). List aircraft types based on the following order of priority:
i) The flight progress strip/inflight contact form.
ii) FAA Order JO 7360.1, Aircraft Type Designators.
iii) The FAA aircraft registry site.
iv) The ICAO aircraft registry site.
(e) Fifth Line. Accident Coordinated Universal Time (UTC) date and UTC time.
(f) Sixth Line. UTC date that the package is to be destroyed (five years for both originals and copies of the aircraft accident package).
EXAMPLE:
Original Aircraft Accident Package
20-003-ARV N9555U, BE36 August 5, 2020, 0233 UTC
Destroy: August 5, 2025
(2) Section 1. Table of Contents (list each section’s number and content). If the information called for by a specific section is unavailable or not pertinent, use that section number for the next required item so that the numbers remain in sequence.
(3) Section 2. FAA Form 8020-6, Report of Aircraft Accident, and FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) (see Chapter 7, paragraph 2). Only the holding facility completes FAA Form 8020-6. Each facility that provided air traffic services or that had communication with or contact regarding the subject aircraft must submit FAA Form 8020-6-1. Place FAA Forms 8020-6-1 in chronological order.
(4) Section 3. Review of Services Memoranda (see Chapter 5, paragraph 5). The certification signature must be the same as the typed name of the facility manager or acting facility manager. Do not use initials. Do not use “for” to sign as the certifier. Digital signatures may be used.
(5) Section 4. FAA Form(s) 7230-4, Daily Record of Facility Operation. Include FAA Form 7230-4 from all pertinent dates. For example, the date on which the service was provided, the date of the aircraft accident, and the date on which it was reported. FAA Form 7230-4 from the facility reporting the accident must have an entry for the aircraft accident (see Chapter 3, paragraph 5.b.(3)(d)).
(6) Section 5. Personnel Log(s). Include personnel logs from all areas of specialization in the facility. Use of the ATO Portal is recommended; however, facilities using the Air Traffic Organization Resource Tool (CRU-ART) are required to include a memorandum listing those employees on regular days off (RDOs) (see Appendix B). Redact any type of leave taken only on copies of the personnel logs.
(7) Section 6. FAA Form(s) 7230-10, Position Log(s), or automated equivalent.
(a) Towers or combined tower/Terminal Radar Approach Control (TRACON) and FSS: Include all positions regardless of whether they are staffed or not.
(b) TRACON, FCF, and ARTCC facilities: Include all positions regardless of whether they are staffed. If the facility has more than one area of specialization, then include all positions of every area of specialization having contact with the aircraft.
(8) Section 7. Facility Layout Chart(s). Identify the facility being depicted on each chart. If positions of operation are identified by something other than traditional abbreviations, include a legend.
(9) Section 8. Airport Diagram. For all aircraft accidents on or within one mile of the airport property, provide an airport diagram current at the time of the aircraft accident. The airport diagram must include the name of the airport and the statement “this diagram not to scale.” If able, use FAA-produced diagrams. The APG has the ability to automatically load the appropriate airport diagram for aircraft accidents within one mile of the airport when available. Use only FAA Airport Diagrams in the aircraft accident package.
NOTE: FAA diagrams are available at (http://www.faa.gov/airports/runway_safety/diagrams/). Every effort should be made to retrieve the Airport Diagram that was in effect at the time of the accident. If the Airport Diagram included is not the Airport Diagram current at the time of the accident, include the diagram without date alterations along with a memorandum explaining the discrepancy.
(10) Section 9. Flight Progress Strip(s) and/or In-Flight Contact Record(s). Indicate the name of the facility and the UTC date(s) on the page displaying the flight progress strips or contact records.
(11) Section 10. Transcription of Voice Recording(s) (see Chapter 8, paragraph 2).
(12) Section 11. FAA Form 8020-3(s), Facility Aircraft Accident/Incident Notification Record (see Chapter 7, paragraph 1).
(a) Only the original aircraft accident file/package at the holding/supporting air traffic facility will retain the un-redacted information.
(b) Redact or black out all classified or sensitive security information from all copies. Generally this includes home, cellular, and unpublished numbers of FAA, airport, military, and emergency personnel/offices.
(c) If FAA Form 8020-3 was not used at the time of the event but notifications were made, FAA Form 8020-3 must still be completed.
(13) Section 12. Weather Products. Weather that was pertinent to the aircraft accident/incident and/or available to the facility (regardless of whether it was issued to the flight crew) and the source of the weather. This includes pre-duty weather briefing and weather entered on FAA Form 8020-6, including remarks. PIREPs, SIGMETs, AIRMETs, TAFs, weather-related NOTAMs, and other weather information should also be included.
(14) Section 13. NOTAMs. Non-published NOTAMs are of a temporary nature, like Temporary Flight Restrictions (TFRs). NOTAMs or aeronautical information of an extended nature are published in the Notices to Airmen Publication (NTAP).
(15) Section 14. FAA Form(s) 7233-2, Preflight Briefing Log, or automated equivalent.
(16) Section 15. FAA Form(s) 7233-1, Flight Plan, or automated equivalent.
(17) Section 16. Other. Include any other materials deemed pertinent. The APG will automatically generate a UTC conversion chart for insertion in this section.
4. Certification of the Aircraft Accident Package.
a. An Information Memorandum addressed to the service center director or the Flight Service Directorate from the facility manager or acting facility manager of the data collection facility must be prepared. The certification signature must be the same as the typed name. Do not use initials. Do not use “for” to sign as the certifier. Digital signatures may be used. This
memorandum will certify that the facility manager or acting facility manager is attesting to the completeness of the entire aircraft accident package. The memorandum will provide the following certification:
“I certify that aircraft accident package [aircraft accident package number] has been reviewed and is complete.”
b. Forward a copy of the Information Memorandum with the completed aircraft accident package to the QCG or Flight Service Directorate (see Appendix B). The certification memorandum is not part of the aircraft accident package. Retain the certification memorandum in the aircraft accident file. Do not distribute the Information Memorandum to the FAA IIC.
5. Distribution.
The facility preparing the aircraft accident package must retain the package with original documentation in the facility files. Original documents (recorded or written) must not be released from the air traffic facility's custody (see Chapter 10, paragraph 1). Facilities must distribute the copies of the package as follows:
a. FAA, with the exception of FAA FSS facilities, FCTs, and NFCT facilities:
(1) One complete package to the appropriate service center QCG within 30 calendar days of the aircraft accident. After review, the service center QCG will forward one copy of the package to the LSG within 45 calendar days of the aircraft accident.
(2) After the LSG has reviewed and released the package, send a COPY to the FAA IIC (AVP-100 or FSDO, as appropriate).
(3) The FAA IIC must forward one COPY to the NTSB within 60 calendar days of the aircraft accident.
b. FAA FSS facilities:
(1) One complete package to the Alaska Flight Service Information Group (AFSIAG) within 30 calendar days of the aircraft accident. After review, the AFSIAG will forward one copy of the package to the LSG within 45 calendar days of the aircraft accident.
(2) After the LSG has reviewed and released the package, the AFSIAG must send a COPY to the FAA IIC, AVP-100, or FSDO, as appropriate.
(3) The FAA IIC must forward one COPY to the NTSB within 60 calendar days of the aircraft accident.
c. FCFSS facilities:
(1) One complete package to the Flight Service Directorate within 30 calendar days of the aircraft accident. After review, the Flight Service Directorate will forward one copy of the package to the LSG within 45 calendar days of the aircraft accident.
(2) After the LSG has reviewed and released the package, the Flight Service Directorate must forward one COPY to the FAA IIC, AVP-100, or FSDO, as appropriate.
(3) The FAA IIC must forward one COPY to the NTSB within 60 calendar days of the aircraft accident.
d. Facilities that prepare an aircraft accident package as a result of an aircraft accident involving military aircraft must distribute the package as described in Chapter 6, paragraph 5.
6. Review of Aircraft Accident Files. The LSG or its designee has the authority to direct facilities to add to or reduce the content of the aircraft accident file/package. This direction must be in written form, either via email or memorandum. Additionally, the LSG may review file content and format at its discretion.
7. Changes to the Aircraft Accident Package after the Package Was Released. Should corrections to the FAA facility or FCF aircraft accident package become necessary, all changes must be distributed in the same manner as outlined in Chapter 6, paragraph 5. A memorandum from the facility manager or acting manager must accompany any changes with a complete explanation of the changes.
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26
Chapter 7. 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.
a. General.
(1) All air traffic facilities (except contract FSSs) with geographical jurisdiction over an airport that is supported by an air traffic facility (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 notification of a known aircraft accident or a suspected aircraft accident must make and record the notification 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) Indicate the facility name on the form.
(7) 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.
(8) 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 aircraft call sign and date of the aircraft accident in the upper right-hand corner.
(2) Enter the airport name for the location on FAA Form 8020-3.
(3) 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 1, 2, and 3 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) The following contacts must be listed in order immediately below the contacts in item (2) above.
(a) The JSEN.
(b) The ROC.
(c) The DEN.
(d) The Air Traffic Manager.
(e) Technical Operations.
(f) Additional law enforcement.
(g) The NWS, at (800) 242-8194.
a. Alternate Number for the NWS: (800) 242-8895.
(h) Military Authority.
(i) Airport Authority.
(4) Additional contact information may be included below the required contacts 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 Number. Reports must be numbered as described in Chapter 6, paragraph 1.
(2) 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. List aircraft types based on the following order of priority:
(a) The flight progress strip/inflight contact form.
(b) FAA Order JO 7360.1, Aircraft Type Designators.
(c) The FAA aircraft registry site.
(d) The ICAO aircraft registry site.
(3) Block 2. Date/Time of Accident (UTC).
(4) 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.
(5) 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 cause 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.
(6) 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, defense VFR, or no flight plan).
(7) Block 6. Flight Crew. Enter the name of each flight crew member, 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 report preparation. When the information is not known, enter “unknown.”
(8) 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.”
(9) Block 8. Aircraft Damage. (Obtained from FSDO.)
(10) Block 9. Property Damage. (Obtained from FSDO.)
(11) Block 10. Operational Status of Navigational Aids/Lights/Communication.
(12) Block 11. Weather Data. Write weather data in plain language. Spell numbers out. Use 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 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.
(13) Block 12. Air Traffic 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), Front Line Manager (FLM), and/or Controller-In- Charge (CIC) not signed on a control position or someone that responded to a point out request. 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.
(b) Place the operating initials for each controller to the right of their name and enclosed in parentheses (see Appendix B).
(c) List the facility involved.
(d) Indicate the position of operation occupied by each person.
(e) Check if the person listed was an eyewitness to the aircraft accident.
(14) 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.
(15) Block 14. Chronological Summary of Flight (FAA Form 8020-6-1). All involved air traffic facilities that provided pertinent or routine services, or that provided no services but have data must complete Block 14. This provides a complete chronological summary of the flight that describes all pertinent communications, emergency assistance, and other air traffic services provided to the aircraft.
(a) Combine entries if they occurred in the same minute.
(b) Identify abbreviations prior to use (e.g., Dothan Airport (DHN) or Local Control (LC)).
(c) If there is insufficient space on the first page of the form, use the continuation sheets to list any additional information.
(d) Type the aircraft accident date accompanied by the statement, “ALL TIMES BELOW ARE COORDINATED UNIVERSAL TIME UNLESS OTHERWISE SPECIFIED.”
(e) If the chronological summary involves more than one date, then type subsequent dates.
(f) 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 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).
(d) Time (UTC).
(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) Box 2. 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 used by FAA inspectors performing flight tests.
(d) Box 4. Enter the type of activity (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.
(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 crewmembers 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 (in person, radio, or telephone).
(12) RECEIVED BY. Provide the signature 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 (on the other side, on a 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) Box 2. Enter the make and model.
(c) Box 3. Enter the 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 to whom the initial information was distributed.
(6) TIME. Enter the UTC time.
(7) RECEIVED VIA. Check the appropriate box (in person, radio, or telephone).
(8) RECEIVED BY. Provide the signature of the person receiving the information and his or her title.
(9) NOTE: Part 1. Check the appropriate box to describe the status of FAA Form 8020-9, Part 1 (on the other side or on a 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/incidents include the abandonment of a search for an overdue/missing aircraft that cannot be located. The form will then be forwarded, as necessary, to:
(a) FAA, WOC, Washington, DC. The WOC will ensure timely notification to the CSG on-call investigator.
(b) NTSB, Washington, DC.
(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) 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 facsimile, 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.
(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 5, paragraph 4, 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. This form is NOT generated by the APG.
a. If requested by the FSDO, LSG, QCG, Flight Service Directorate, or CSG, complete FAA Form 8020-11 for selected aircraft incidents.
b. Form Instructions.
(1) TO. Enter the name of the facility/office receiving the form.
(2) FROM. Enter 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:
(a) Begin with the identifier of the facility.
(b) Followed by the year (last two numbers of the calendar year).
(c) Ending with the incident number (two digits).
EXAMPLES:
Third independent FAA Form 8020-11 for Denver ARTCC in 2020 ZDV-20-03
First independent FAA Form 8020-11 Atlanta TRACON in 2021 A80-21-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 in complete form with enough details 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, 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 Statements. This form is completed through the APG.
a. Complete personnel statements at Airport Traffic Control Towers (ATCTs) (tower cab positions) when the QAG categorizes the event as a pilot deviation. If requested by Flight Standards, personnel statements are required for facilities using surveillance-based ATC. Personnel statements are not required for aircraft accidents. If any personnel statements are completed for aircraft accidents, place them in the section titled “Other.”
b. 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 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.
c. Prior to completing a personnel statement, the employee completing the statement must:
(1) Have the opportunity to review voice and data recordings and other pertinent 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.
d. 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. Enter the 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. Enter the title of the employee completing the statement (e.g., Air Traffic Control Specialist, FLM, 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 (must match FAA Form 7230-10 or automated equivalent).
NOTE: The facility may elect to have items 1 through 8 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.
e. 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.
f. 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 8. Voice Recordings and Transcripts
Chapter 8. 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 (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.”
Continue reading ↓ 120 of 286 passages shown