Order JO 8020.16C Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting
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 is an ATO order that has been written in coordination with FAA Order 8020.11 and describes specifically the ATO's roles and responsibilities in aircraft accidents, aircraft incidents, and occurrences as they pertain to notification, reporting, and data retention.
This document is cancelled. Cancelled by JO 8020.16D. Check the official source before relying on it.
Text read by OCR from a scanned file (23 of 152 pages). Check the original, as some words may be misread.
Distribution: Electronic Initiated By: AJI-0 ATO Safety and Technical Training
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.16B, dated December 31, 2014.
This is an ATO order that has been written in coordination with FAA Order 8020.11 and describes specifically the ATO's roles and responsibilities in aircraft accidents, aircraft incidents, and occurrences as they pertain to notification, reporting, and data retention.
Teri L. Bristol Chief Operating Officer Air Traffic Organization
Air Traffic Organization Policy
SUBJ: Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting
ORDER JO 8020.16C
Effective Date:
12/ 14/2018
Table of Contents
Chapter 1. General
1 Purpose of This Order … 5 2 Audience … 5 3. Where Can I Find This Order? … 5 4. What This Order Cancels … 5 5. Explanation of Changes … 5 6. Authority to Change This Order … 5 7. Terms and Definitions … 6 8. Related Publications … 6 9. Forms and Reports … 6 10. Safety Risk Management Analysis … 6 11. Distribution … 6
Table of Contents › Chapter 5. Aircraft Accident File/Package Process
Chapter 2. ATO Elements Involved in Notification, Investigation, and Reporting
1. Safety and Technical Training, Compliance Services Group (CSG) … 7 2. Safety and Technical Training, Service Center, Quality Assurance Group (QAG) … 7 3. Safety and Technical Training, Litigation Support Group (LSG) … 7 4. Mission Support Services, Service Center, Quality Control Group (QCG) … 7 5. Technical Operations … 7 6. Flight Inspection … 7
Chapter 3. Initial Notification and Reporting Responsibilities
1. General … 8 2. Federal Contract Facilities … 8 3. Operations Center … 9 4. Notification of Other Operations Centers … 9 5. Aircraft Accident and Aircraft Incident Notification and Reporting … 10
Chapter 4. Terms and Definitions
1. Terms Used in this Order … 13 2. Definitions Used in this Order … 14
Chapter 5. Aircraft Accident File/Package Process
1. Aircraft Accident File/Package Determinations … 17 2. Determination of Air Traffic Facility Responsible for Final Data Collection … 17 3. Holding and Supporting Facilities … 20 4. Data Flow between Involved Facilities … 20 5. Review of Services and the Review of Services Memorandum … 21 6. Additional Data Collection and Certification Information … 22 7. Data Collection Memorandum … 24
Table of Contents › Chapter 11.
Chapter 6. Aircraft Accident File/Package
1. Numbering of Aircraft Accident File/Package … 25 2. Content and Assembly of the Aircraft Accident File … 25 3. Content, General Instructions, and Assembly of the Aircraft Accident Package … 27 4. Certification of the Aircraft Accident Package … 31 5. Distribution … 31 6. Review of Aircraft Accident Files … 32 7. Changes to the Aircraft Accident Package after the Package was Released … 32
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 … 33 2. FAA Form 8020-6, Report of Aircraft Accident … 34 3. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice … 36 4. FAA Form 8020-11, Incident Report … 41 5. FAA Form 8020-26, Personnel Statements … 42
Chapter 8. Voice Recordings and Transcripts
1. Copies of Voice Recordings … 45 2. Transcription of Voice Recordings … 47 Chapter 9. Radar Data Collection, Radar/Computer/Weather Certification, and Radar Replay
1. Radar Data Collection … 50 2. Radar, Weather, and Computer Data Certification … 51 3. Litigation/Enforcement Replays … 53 4. Production Credits … 54
Chapter 10. Retention of Aircraft Accident Files
1. Security of Original Records … 55 2. Retention and Disposal of Aircraft Accident Records … 55 3. Holds Placed on Records … 56
Chapter 11. Reporting and Notification Responsibilities for Pilot Deviations
1. General … 57 2. Federal Contract Facilities (FCF) … 57 3. Air Traffic Facility Responsibilities … 57 4. Quality Assurance Group (QAG) Responsibilities … 58 5. Quality Control Group (QCG) Responsibilities … 58
Table of Contents › Appendix D. Original Documentation Transfer
Chapter 12. Data Provided in Support of Pilot Deviations and Air Traffic Occurrences
1. General Data Requirements … 59 2. Audio Data … 59 3. Radar and Computer Data … 59 4. Transcripts … 59 5. Replays/Plots … 59 6. Personnel Statements … 60 7. Documentation … 60 8. Examples of Additional Air Traffic Data … 60 9. Retention … 61
Chapter 13. Technical Operations & Flight Program Operations Aircraft Accident Investigation Responsibilities
1. General … 62 2. Flight Program Operations Responsibilities … 62 3. Air Navigation Facilities … 62 4. Overview of Technical Operations Activities … 62 5. Responsibilities … 63 6. Aircraft Accident Representative … 65 7. Process … 65 8. Decisions … 65 9. Field Work … 70 10. Documentation … 73 11. Preserving, Copying, and Releasing Reports and Records … 74 12. Field Response for Post Aircraft Accident Data … 74 13. Practice Aircraft Accident Exercise … 74
Chapter 14. FOIA Request for Aircraft Accident/Incident and Occurrence Documents
1. Records Search … 84 2. Disclosure Determination … 84 3. Release of Records … 84 4. Retention of Records … 85
Appendix A. Forms Used By Air Traffic
Appendix B. Example of Aircraft Accident Package
Appendix C. Cassette Tape and Computer Diskette – Recordable (CD-R) and Digital
Versatile Disc (DVD) Labeling
Appendix D. Original Documentation Transfer
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 › 6. Authority to Change This Order.
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.16B, Air Traffic Organization Aircraft Accident and Incident Notification, Investigation, and Reporting, dated December 31, 2014, including all associated notices, are canceled.
5. Explanation of Changes. This revision:
a. Incorporates editorial changes to include rearranging chapters and paragraphs to follow the flow of the aircraft accident reporting, investigation, file, and package process.
b. Adds a new chapter with definitions and terms used in this order.
c. Adds a requirement for the Quality Control Group (QCG) at the service center to initiate the aircraft accident package for both holding and supporting facilities in the Aircraft Accident Package Generator (APG).
d. Reflects a change from facilities creating "formal" and "informal" aircraft accident files. Facilities now create an "Aircraft Accident File" and an "Aircraft Accident Package".
e. Changes the retention requirement for copies of the Aircraft Accident Package to five years.
f. Changes the exchange of data requirements in an aircraft accident package/file between FAA and Federal Contract Facilities (FCFs) as well as between different vendors of contract facilities.
g. Removes the requirement for partial transcripts to be included in an aircraft accident package unless requested.
h. Updates ATO procedures related to the collection of documents and other items associated with an aircraft accident or incident.
i. Updates FAA Form 8020-3 to allow additional lines to be inserted as needed.
6. Authority to Change This Order. Authority for future revisions to this order is delegated to the Vice President for Safety and Technical Training, (AJI-0). Submit proposed changes or additions to the ATO Litigation Support Group (LSG), (AJI-17). Supplemental changes and requests for waivers
Chapter 1. General › 11. Distribution. Electronic Distribution.
to programs and policies transmitted by this order must receive prior approval through written requests to ATO Safety and Technical Training.
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 Quality Assurance Program
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. Selected, 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. › 6. Flight Inspection.
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, Compliance Services Group (CSG). The ATO participates in the investigation of aircraft accidents and aircraft incidents when FAA air traffic control or aeronautical communications facilities are involved. For all significant aircraft accidents and aircraft incidents, the ATO Safety (CSG) serves as the lead ATO representative and is responsible for ensuring aircraft accidents and aircraft incidents involving ATO facilities or functions are investigated and reported in a timely manner. The same requirements pertain to private, non-federal facilities. If a facility is operating within the NAS, it must comply with the same rules and regulations as the federal facility.
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, ATO Safety and Technical Training, 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 Inspection. Flight Inspection 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 Investigator-in-Charge (IIC) or TOAAR.
Chapter 3. Initial Notification and Reporting Responsibilities › 2. Federal Contract Facilities.
Chapter 3. Initial Notification and Reporting Responsibilities
1. General. In order to provide authorities in the FAA, National Transportation Safety Board (NTSB), or military services with information on aircraft accidents and aircraft incidents, follow notification procedures as outlined in this chapter.
a. Any FAA or FCF employee who becomes aware of an aircraft accident or aircraft incident must report the facts immediately to the nearest FAA air traffic facility (en route, terminal facility, or flight service station) or Regional Operations Center (ROC).
b. To report an aircraft accident or aircraft incident when you do not have access to an FAA air traffic facility or ROC, as in the case of international events, use established channels such as the Department of State, the FAA Aeronautical Fixed Telecommunications Network, or by any expeditious means appropriate to the aircraft accident or aircraft incident circumstances.
c. Report and make notifications for aircraft accidents and aircraft incidents involving Unmanned Aerial 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, Flight Service Directorate, or CSG, complete FAA Form 8020-11, Incident Report, for selected aircraft incidents.
2. Federal Contract Facilities. (FAA 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 "FAA" precedes the type of facility, the requirement applies to FAA facilities only. If the acronym "FAA" is not present, the requirement applies to all facilities (that is, FAA facilities and FCFs).
NOTE: A FCT is considered a FCF and not a 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).
Chapter 3. Initial Notification and Reporting Responsibilities › 4. Notification of Other Operations Centers.
3. Operations Center. When a notification of an aircraft accident or aircraft incident is received from any source, the Washington Operations Center (WOC) or Regional Operations Center (ROC) 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.
a. When the reported aircraft accident/incident is one that requires regional or Washington Operations Office 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 involved, Flight Program Operations must be included in the conference call.
c. Upon receiving a report 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, NTSB, manufacturers, CSG, TOAAR, Office of Airport Safety and Standards, Civil Aerospace Medical Institute, Aircraft Certification Directorates, and FAA William J. Hughes Technical Center, as necessary.
e. The 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 a ROC’s area of responsibility may be of concern to other regions or centers, the ROC officer must provide information to other ROCs and/or the WOC. These events include:
a. Aircraft accidents or aircraft incidents in which the aircraft operators’ operating certificate is held by another region or in which another region has the certification responsibility for that aircraft.
b. Aircraft accidents or suspected aircraft accidents (overdue and missing aircraft) of aircraft that are carrying prominent persons from another region.
c. Aircraft accidents involving injuries or death of FAA personnel from another region.
Chapter 3. Initial Notification and Reporting Responsibilities › 5. Aircraft Accident and Aircraft Incident Notification and Reporting.
d. Any other aircraft accident or aircraft incident, which, 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 an air traffic facility, prepare an aircraft accident package and file as outlined in this order.
(3) All aircraft incidents, selected criminal acts reported to or by law enforcement agencies, emergency evacuations of aircraft, in-flight major component failures, and any 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 or Vice President is 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 ATO QCG, WOC, ATO CSG, and the Flight Service Directorate.
(5) Overdue and missing aircraft when:
(a) Neither voice/data communication nor radar contact can be established, and 30 minutes have passed since the estimated time of arrival over a specified or compulsory reporting point or at a clearance limit in your area, or the clearance void time. If you have reason to believe that an aircraft is overdue before 30 minutes have passed, take the appropriate action immediately.
(b) Information is received that search and rescue procedures have commenced for an aircraft that is not on a flight plan.
b. How to Report. Facilities first receiving notification of a known or suspected aircraft accident/incident must:
(1) ROC. 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) FAA Air Traffic Facilities and FCFs.
(a) Notify the ROC.
(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.
(c) Complete and transmit FAA Form 8020-9 (see Chapter 7, paragraph 1).
(d) Make an entry on FAA Form 7230-4 via the Comprehensive Electronic Data Analysis and Reporting (CEDAR) program or other means. Include a reference to any associated MORs.
(e) Immediately notify ATO Safety CSG and the WOC through the ROC 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., EnRoute Automation Modernization (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 ROC by telephone in accordance with FAA Order JO 1030.3. The ROC 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 ROC 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 must be reported to the ROC as soon as possible.
Chapter 4. Terms and Definitions › 1. Terms Used in the This Order
Chapter 4. Terms and Definitions
1. Terms Used in the This Order
a. 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.
b. Alert Notice (ALNOT). A request originated by a flight service station (FSS) or an air route traffic control center (ARTCC) for an extensive communication search for overdue, unreported, or missing aircraft.
c. 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.
d. 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.
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 Standard Terminal Automated Replacement System (STARS)).
g. Holding Facility. The air traffic facility that is responsible for the final aircraft accident package.
h. Pertinent Services. Services that 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.
Chapter 4. Terms and Definitions › 2. Definitions Used in This Order
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 has 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.
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 vehicle 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 until the time that 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. Federal Contract Facility (FCF). FAA Contract Towers (FCTs), Non-Federal Contract Towers (NFCT) and Contracted Flight Service Station (FCFSS) facilities.
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. In accordance with FAA Order 8020.11, the FAA IIC must be an Aviation System or Office of Accident Investigation and Prevention (AVP) employee.
h. Fatal Injury. Any injury resulting in death within 30 days of the aircraft accident.
i. 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.
j. Mandatory Occurrence Report (MOR). An occurrence involving air traffic services, for which the collection of associated safety-related data and conditions is mandatory.
k. 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.
l. Occurrence. An abnormal event, other than an aircraft accident/incident.
(1) Any occurrence that meets the definition of a MOR; or
(2) An Electronic Occurrence Report (EOR): Any automatically detected safety event.
m. 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.
n. Pilot Deviation. An action of a pilot that results in the violation of a Federal Aviation Regulation or a North American Aerospace Defense Command (Air Defense Identification Zone) tolerance.
o. Serious Injury. Any injury associated with an aircraft accident that:
(1) Requires hospitalization for more than 48 hours, commencing within seven days from the date an injury was received.
(2) Results in a fracture of any bone (except simple fractures of fingers, toes, or nose).
(3) Causes severe hemorrhages or nerve, muscle, or tendon damage.
(4) Involves any internal organ.
(5) Involves second- or third-degree burns, or burns of any degree affecting more than five percent of the body surface.
p. Substantial Damage. Damage or failure which adversely affects the structural strength, performance, or flight characteristics of the aircraft, and which would normally require major repair or
replacement of the affected component. Engine failure or damage limited to an engine if only one engine fails or is damaged, bent fairings or cowling, dented skin, small punctured holes in the skin or fabric, ground damage to rotor or propeller blades, and damage to landing gear, wheels, tires, flaps, engine accessories, brakes, or wing tips are not considered "substantial damage."
q. Unmanned Aircraft System (UAS). A system that includes an unmanned aircraft, control station, and various mission elements used, or intended to be used, for flight. This includes all classes of airplanes, helicopters, airships, and translational lift aircraft that have no onboard pilot. The term UAS includes the airframe and all associated support elements, including the control station, communication links, equipment, and personnel necessary to conduct operations.
r. Unmanned Aircraft System 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.
Chapter 5. Aircraft Accident File/Package Process › 2. Determination of Air Traffic Facility Responsible for Final Data…
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 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
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 having communication 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 having communication with the aircraft.
NOTE: Communication may include two-way radio or telephonic communication with the pilot or inter/intra-facility coordination regarding the flight.
(5) Other Aircraft - the FAA air traffic facility having radar services responsibility for the area in which the aircraft accident occurred.
(6) Aircraft that have not communicated with an FAA facility; but have communicated exclusively with an FCF - The last FCF having communication with the aircraft for the flight. If more than one vendor is involved, the last FCF having communication with the aircraft for each vendor.
(7) Aircraft that have communicated with both an FAA facility and an FCF and/or different vendor FCFs.
(a) The last FAA facility having communication with the aircraft for the flight will conduct the final collection of all aircraft accident information involving FAA facilities. No information from a 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 and FCFs or different vendor FCFs.
NOTE: When both FAA 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.
Chapter 5. Aircraft Accident File/Package Process › FIGURE 5-2-1
FIGURE 5-2-1
Determination of Air Traffic Facility Responsible for Final Data Collection
Type Aircraft Accident Responsible Facility Reference
Aircraft on IFR flight plan under the FAA facility with jurisdiction Para 5-2a(1) control of FAA facility over the flight
Aircraft on IFR flight plan under the ARTCC in whose area the aircraft Para 5-2a(2) control of a military staffed facility accident occurred
Aircraft not on an IFR flight plan but FAA facility having communication Para 5-2a(3) in communication with an FAA facility with the aircraft when the aircraft accident occurred
Aircraft not in communication with Last FAA facility having Para 5-2a(4) an FAA facility; at the time of the communication with the aircraft aircraft accident
Other Aircraft FAA air traffic facility with radar Para 5-2a(5) responsibility for the area in which the aircraft accident occurred
Aircraft that have not communicated The last FCF having communication Para 5-2a(6) with an FAA facility, but have with the aircraft. If more than one communicated exclusively with an FCF vendor is involved, the last FCF having communication with the aircraft for each vendor.
Aircraft that have communicated Multiple facilities will be responsible Para 5-2a(7) with both an FAA facility and an FCF for the final data collection. See para 5-2a(7) (a) for FAA facility requirements. See para 5-2a(7)( b) for FCF facility requirements
Chapter 5. Aircraft Accident File/Package Process › 4. Data Flow between Involved Facilities.
3. Holding and Supporting Facilities. The holding facility is responsible for final data collection. Supporting facilities are air traffic facilities that provided services for, or had communication/contact regarding 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 still be 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 a 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 (e.g., FAA facilities, same vendor FCFs) facilities 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 pertinent services, routine services, or may not have provided services to the accident aircraft but have data (e.g., radar) regarding the aircraft (see Chapter 4, paragraph 1). The QCG, Flight Service Directorate/AFSIAG or the LSG may change a facility’s designation to 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.
Chapter 5. Aircraft Accident File/Package Process › 5. Review of Services and the Review of Services Memorandum.
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, Report of Aircraft Accident (Continuation Sheet), 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, Report of Aircraft Accident (Continuation Sheet), 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. Retain all data pertaining to the handling of the accident aircraft. Conduct the review within two administrative days of notification of an aircraft accident. Notify the holding facility of your services 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 originals/digital copies of the original are on file in this office.”
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.
Chapter 5. Aircraft Accident File/Package Process › 6. Additional Data Collection and Certification Information.
f. Facility layout charts.
g. Flight progress information and strips if printed.
h. Radar data.
i. Pilot reports (PIREP) and weather data (if available, Center Weather Advisories, Weather System Wide Access Capability, Terminal Area Forecasts (TAFs), etc.).
j. Significant Meteorological Information (SIGMET).
k. Airmen's Meteorological Information (AIRMET).
l. Notice to Airmen (NOTAM) and non-published NOTAMs.
m. FAA Form 7233-1, Flight Plan.
n. Video maps.
o. Copies of procedures (Standard Instrument Departures (SIDs)/STARSs) that the aircraft was flying or assigned at the time of the aircraft accident.
p. Copies of operations letters, letters of agreement, and facility memoranda.
6. Additional Data Collection and Certification Information.
a. AFSIAG. The FSS in whose flight plan area the aircraft accident occurs must query the FCFSS.
b. Contract Flight Service Station (FCFSS). Information regarding possible services provided by a FCFSS will be coordinated through the Flight Service Directorate as follows:
(1) The reporting facility can obtain information about FCFSS services through notification of the ROC.
(2) The ROC will notify the Central Region ROC of the aircraft accident.
(3) The Central Region ROC will contact the Flight Service Directorate.
c. 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.
d. 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 Air Traffic Control (ATC) Services. When requested by the FAA IIC, AVP-100, LSG, CSG, QCG, 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. Air Traffic Control System Command Center (ATCSCC). When the FAA IIC, LSG, CSG, QCG, or Flight Service Directorate determines that the ATCSCC may have information pertinent to an aircraft accident, the ATCSCC will be requested to retain data, documentation, and/or copies of recordings in accordance with this order and local directives.
(1) The ATCSCC must provide data, documentation, and/or copies of recordings as outlined in this order.
(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. 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 has not been collected and/or is no longer available in accordance with this order, a memorandum must be prepared and signed to explain what was discovered and why it happened. Insert this memorandum in the aircraft accident file.
Chapter 6. Aircraft Accident File/Package › 2. Content and Assembly of the Aircraft Accident File.
Chapter 6. Aircraft Accident File/Package
1. Numbering of Aircraft Accident File/Package.
a. The Aircraft Accident Package Generator (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 (threedigits), and then the identifier for the facility (e.g., ZDV). 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 2020 20-003-ZDV
First aircraft accident file/package for Front Range FCT in 2019 19-001-FTG-FCT
Fourth aircraft accident file/package for Atlanta TRACON in 2021 21-004-A80
Second aircraft accident file/package for Prescott FCFSS in 2022 22-002-PRC-FCFSS
First aircraft accident fil/package for Mohave NFCT in 2020 20-001-MHV-NFCT
b. Supporting FAA facilities retaining information in a 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 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 and data 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 additional 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).
(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.
(k) Additional information, may include:
i) Charts (e.g., minimum vector altitude (MVA) maps, approach plates).
ii) MORs.
iii) Covered Event Review.
Chapter 6. Aircraft Accident File/Package › 3. Content, General Instructions, and Assembly of the Aircraft Accident…
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).
(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 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 the 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) From the holding facilities aircraft accident file, all records described in paragraph 3-c below.
(2) From supporting facilities with pertinent services, all records described in paragraph 3-c below.
(3) From supporting facilities with 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).
(4) From military facilities with routine or pertinent services, the aircraft accident package will contain applicable equivalent documents when supplied by the military.
(5) 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.
(6) 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 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 include:
(1) Include a table of contents page that lists each section’s number and content.
(2) Insert a sheet of plain paper between each section with the section number and title of the section centered on the page.
(3) 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.
(4) All information in each section must be in the chronological order beginning with the first facility having contact with the aircraft and then in order of involvement.
(5) 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 (Box 12) must match those in Section 5, Personnel Logs.
(b) Positions of operation in Section 6, FAA Form 7230-10 must match positions transcribed in Section 10, Transcription of Voice Recordings, if transcripts are requested.
(c) Weather data entered on FAA Form 8020-6 must match weather listed in Section 12, Weather Products.
(6) 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 registration(s) or flight number(s) must be in the lower left-hand footer.
(7) 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) Cover Page. The cover page must be clearly marked with the following:
(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
18-002-ARV N56341, BE36 February 5, 2018, 0233 UTC
Destroy: February 5, 2023
(2) Section 1. Table of Contents (list each section’s number and content).
(3) Section 2. FAA Form 8020-6, Report of Aircraft Accident, and FAA Form 8020-6-1, Report of Aircraft Accident (Continuation Sheet) (see Chapter 7, paragraph 2). Only the holding facility completes FAA Form 8020-6. Each facility having provided air traffic services or having communication with or contact regarding the subject aircraft must submit FAA Form 8020-6-1. Place FAA Forms 8020-6-1 in chronological order.
(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.
(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 utilizing Cru-ART are required to include a memorandum listing those employees on regular days off (RDO) (see Appendix B). Redact any type of leave taken only on copies of the personnel logs.
(7) Section 6. FAA Form(s) 7230-10, Position Log(s), or automated equivalent.
(a) Towers or combined tower/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 or not. If the facility has more than one area of specialization, then include all positions of every area of specialization having contact with the aircraft.
(8) Section 7. Facility Layout Chart(s). Identify the facility being depicted on 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 FAAproduced diagrams. The APG has the ability to automatically load the appropriate airport diagram for aircraft accident s within one mile of the airport when available.
NOTE: FAA diagrams are available at (http://www.faa.gov/airports/runway_safety/diagrams/)
(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.
(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 weather entered on FAA Form 8020-6, including
remarks. PIREPs, SIGMETs, AIRMETs, TAFs, weather-related NOTAMs, and other weather information should also be included.
Chapter 6. Aircraft Accident File/Package › 5. Distribution.
(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, FCT, and NFCT facilities, with the exception of FAA FSS 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 (the FAA Accident Investigation Division (AVP-100) or FSDO, as appropriate).
Chapter 6. Aircraft Accident File/Package › 7. Changes to the Aircraft Accident Package After the Package Was…
(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 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 FAA FSS 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) After review for compliance with applicable FAA orders and directives, the Flight Service Directorate will forward one copy of a package to the LSG on a quarterly review basis. The Flight Service Directorate will forward three FCFSS DRAFTS to the LSG per quarter by the 20th of the last month of the quarter. Quarterly review periods are January through March, April through June, July through September and October through December.
(2) After the LSG has reviewed and released the package, or if the package is not part of the Quarterly Review process, the facility 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 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 change(s) with a complete explanation of the change(s).
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…
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 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 turbulence events, in-flight safety events, etc. that are not associated with a specific airport.
(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) The order of contacts must not be changed, but additional lines may be inserted as needed. 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 callsign 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.
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 2. FAA Form 8020-6, Report of Aircraft Accident.
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 latitude/longitude. The APG Software will 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 (VFR, IFR, SVFR, defense visual flight rules, and no flight plan).
(7) Block 6. Flight Crew. Enter the name of each flight crew member and flight attendants, his or her position, and 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’ name, addresses, and/or 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. PIREPs are not appropriate in Block 11 but should be included in the weather products section.
(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 that 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 parenthesis (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.
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 3. FAA Form 8020-9, Aircraft Accident/Incident Preliminary Notice.
(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 has 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 (i.e., 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 facility/office name of the facility 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) Box2. Enter the make and model.
(c) Box 3. Enter the name of the operator. Include "FAA" in Code B3, OPERATOR OF AIRCRAFT, if the aircraft is owned or operated by the FAA, flown by FAA personnel on official duty, or utilized by FAA inspectors performing flight tests.
(d) Box 4. Enter the type of activity (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 (i.e., 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 air traffic control 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. Signature of the name of the person receiving the information and their 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 separate form, or not required).
c. Aircraft Accident/Incident Preliminary Notice – Part 2
(1) CODE H. AIRCRAFT INFORMATION
(a) Box 1. Enter the aircraft registration number.
(b) Box2. Enter the make and model.
(c) Box 3. Enter UTC date and UTC time of the incident.
(2) CODE I. STATUS OF POTENTIALLY INVOLVED AIRWAYS FACILITIES.
(a) Box 1. Enter the facility type.
(b) Box 2. Enter the identifier of the facility/runway.
(c) Box 3. Indicate the status of the facility just prior to the occurrence.
(d) Box 4. Indicate the status of the facility at the time of the occurrence.
(e) Box 5. Indicate the status of flight inspections conducted.
(f) Box 6. In the remarks section, explain briefly any entry that is marked as abnormal or out of service.
(3) CODE J. STATUS REPORT RECEIVED FROM PILOTS OR OTHERS.
(a) Box 1. Enter the facility type.
(b) Box 2. Enter the identifier of the location/runway.
(c) Box 3. Enter the identification number of the aircraft and name of the person providing the report.
(d) Box 4. Enter the status of the facility.
(e) Box 5. Enter the UTC time of the observation.
(4) RECEIVED AT. Enter the name of the facility/office receiving the initial report.
(5) DELIVERED TO. Enter the name of the facility/office that the initial information was distributed to.
(6) TIME. Enter the UTC time.
(7) RECEIVED VIA. Check the appropriate box (in person, radio, or telephone).
(8) RECEIVED BY. Signature of the name of the person receiving the information and their title.
(9) NOTE: Part 1. Check the appropriate box to describe the status of FAA Form 8020-9, Part 1 (on the other side or on separate form).
d. Distributing Form and Data (Preliminary Message).
(1) The air traffic facility must distribute FAA Form 8020-9, Parts 1 and 2, as appropriate, to the ROC via fax or email within three hours of the detection of the known or suspected aircraft accident /incident. Suspected aircraft accidents/incidents include the abandonment of a search for an overdue/missing aircraft that cannot be located. The form will then be forwarded, as necessary, to:
(a) FAA, Washington Operations Center, Washington, D.C. The WOC will ensure timely notification to the 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 or AFSIAG, as appropriate.
(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 accident s 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.
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 4. FAA Form 8020-11, Incident Report.
(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, Incident Report, for selected aircraft incidents.
b. Form Instructions.
(1) TO. The name of the facility/office receiving the form.
(2) FROM. The name of the facility/office preparing the form.
(3) TYPE OF INCIDENT. Enter the type of incident (e.g., Emergency Evacuation, parachute jumping).
(4) DATE. Enter the date of the incident.
(5) DAY or NIGHT. Check the appropriate box.
(6) INCIDENT NO. If FAA Form 8020-11 is being completed to support a 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.
Chapter 7. FAA Forms 8020-3, 8020-6, 8020-9, 8020-11, and 8020-26 › 5. FAA Form 8020-26, Personnel Statements.
(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 competed 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 utilizing 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 the Freedom of Information Act (FOIA) or litigation activities including pretrial discovery, depositions, and actual court testimony.
(2) The text of the statement (Block 10) may be hand printed in blue or black ink or entered via keyboard. The accuracy of the statement is certified by the signature of the employee completing the form (Block 6). The personnel statement must not be edited. If additional space is needed, do not write on the back of the form. At the end of Block 10, write/type "page 1 of 2." Attach a second FAA Form 8020-26 and write "continued from page 1" at the top. Sign and date the second form.
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 ("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. Name of the employee completing the statement (i.e., first name, middle name or initial, last name) and, in parentheses, his or her operating initials used on personnel logs and/or position logs.
(7) Block 7. Title. Title of the employee completing the statement (ATCS, FLM, OM, etc.).
(8) Block 8. Position and Time (UTC). The identifier 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 › 1. Copies of Voice Recordings.
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;" and any subsequent copies are referred to as the "Working Copy."
a. General Instructions. The term "contact" (as used in this paragraph) is defined as communication and/or coordination with or about the subject aircraft. Therefore, retained voice data must include all communications and/or coordination pertaining to the subject aircraft even if a transmission is not completed or acknowledged. This definition may be extended to include transmissions and/or coordination involving search and rescue efforts, crash-fire rescue, "attention all aircraft" broadcasts, weather advisories, recorded phone lines, and all Automatic Terminal Information Service (ATIS)/Automatic Flight Information Service (AFIS) recordings made during the time that the subject aircraft was under air traffic control.
(1) Determine all recorded contact(s) regarding the subject aircraft. Protect the recording(s) from being altered, damaged, or lost.
(2) Produce and certify the original copy and working copies. Mark the first copy as "Original Copy" and the second copy as "Working Copy." Make additional copies from the "Working Copy."
(3) Certified copies of the recording must include all communications, including time track, pertinent to the aircraft accident from the period beginning 30 minutes before the initial contact and ending 30 minutes after last contact (FCFSS facilities do not need to include any time before initial contact or after last contact).
NOTE: For pilot deviations/occurrences facilities, record voice data from 15 minutes before the pilot deviation/occurrence until 15 minutes after the pilot deviation/occurrence.
(4) Compressed digital formats (MP3, AAC, WMA, etc.) for certified copies of original voice data are not permitted.
(5) Check all certified copies for adequate time and quality of voice.
(6) Certify each position of operation separate and independent of other positions.
(7) A voice announcement preceding the original or working copies of the recording must be made using the following format as necessary to certify the copy:
“This copy is being prepared by [facility]. The subject concerns [type of aircraft accident, aircraft incident, occurrence] involving [aircraft identification] on [date, UTC] at approximately [time, UTC]. The agencies/facilities involved in this [type of aircraft accident, aircraft incident, occurrence] are [agency/facilities name; do not use abbreviations]. The position of operation being copied is/are [position, for example, local control, ground control, R34R, etc.].”
“I certify that the following is a true copy of the original recorded transmissions pertaining to the [type of aircraft accident, aircraft incident or occurrence]. My name is [name]. I am employed as [title] at [facility].”
(8) The copy of each position of operation will be preceded by a certification statement naming the position and the UTC start and stop times of the copy as follows:
“This portion of the copy concerns communications at the [position] during the period of [time, UTC] to [time, UTC] on [date, UTC].”
(9) Conclude the copy of each position with the following statement:
“This is the end of the [position] copy concerning the [type of incident] involving [aircraft identification].”
(10) All the storage media on which the original or working copies are made (CD-R, DVD, etc.) must be marked properly with the aircraft accident, incident, or occurrence number; the aircraft identification; UTC date of the occurrence; facility name; and position with the UTC times encompassing each copy.
b. Digital Audio Legal Recorder (DALR).
(1) Air traffic facilities using DALR must export the Organizer Incident containing the proprietary- .incident and .NMF files. Additionally, air traffic facilities must produce and label an original copy and any working copies. Hold the original copy in a folder containing the .htm file, .xml file, and .jpg file, which accompany and authenticate the .wav file. The working copy need only contain the .wav file. To ensure that audio quality is sufficient to fulfill the requirements of this order, sampling rates must not be lower than 8 kHz and resolution must not be lower than 16 bits. Part-time facilities should not turn off the DALR system when the facilities close; however, air traffic managers should develop procedures to ensure that frequencies are not recorded when facilities are officially closed.
(2) The .wav file must include two channels (time in IRIG-B format on the right channel and voice on the left channel).
NOTE: The certification statements and other required verbal statements remain the same and must be a part of the .wav file.
c. Cassette Tape. When creating certified copies on cassette tapes, ensure that the copy includes a time track/channel. Make the recording with stereo equipment. Do not use the speaker-tomicrophone method. Record time on the right channel and data on the left track. When naming copies, ensure that the .wav files are in chronological sequence of flight if more than one .wav file is included on the storage media (see Appendix C).
Chapter 8. Voice Recordings and Transcripts › 2. Transcription of Voice Recordings.
d. Direction for Release of Voice Data in Specific Situations.
(1) When voice data is released for time periods other than those described in Chapter 8, paragraph 1, the facility must also retain a copy of the released copy and keep a record of to whom it was released and by what authority.
(2) Coordination for release of ATC voice communications to Public Affairs must be accomplished through the ATO LSG and Service Center QCGs or the Flight Service Directorate as appropriate.
(3) When copies of recordings are altered for training purposes, retain an unaltered copy and label the altered copy "Modified for Training Purposes Only."
2. Transcription of Voice Recordings.
a. Prepare partial/full transcriptions when requested by the FAA IIC, LSG, QCG, Office of Chief Counsel, or Flight Service Directorate. Transcripts should be completed using the APG.
b. Transcribe each operational position (e.g., ground control, local control, radar, radar associate) separately. Do not integrate different operational positions into the transcription unless requested by AVP-100, the LSG, the QCG, or the Flight Service Directorate. Transcriptions are made of the position, not of the individual controller or frequency.
c. Do not transcribe ATIS/AFIS recordings unless specifically requested.
d. When a transcript is requested before the transcript has been certified, ensure that the transcript is watermarked "DRAFT." Retain a record of these releases. Do not release transcripts until complete and vetted by the QCG in coordination with the LSG.
NOTE: For situations where an aircraft entered and exited a sector more than once or a direct flight had a stop at an intermediary airport, contact the LSG.
e. A full transcript must contain all recorded communications at the specific position regardless of source. Unless directed otherwise, full transcripts will span from five minutes before initial contact until five minutes after the last contact with the subject aircraft.
f. A partial transcript must contain all recorded communication about the subject aircraft. Unless advised otherwise, partial transcripts include 30 minutes before initial contact until 30 minutes after the last contact (see Chapter 8, paragraph 1).
g. The transcription will be prepared as follows:
(1) The first page must be an FAA memorandum and contain the following information (FCFs use company letterhead):
(a) For "Date," type the date that the transcription was certified and signed.
(b) For "To," type "Aircraft Accident File [aircraft accident file number]."
(c) For "From," type name of the facility preparing the transcription, not the facility manager or acting manager's name.
(d) For "Subject," type "INFORMATION: [Full/Partial] Transcript
[type of aircraft accident, aircraft incident, occurrence]; [aircraft identification]
[nearest city, state, of the aircraft accident location], [UTC date]."
(e) For the first line of the body of the memorandum, type, "This transcription covers the [facility] [operational position] position for the time period from [UTC date and UTC time] to [UTC date and UTC time]."
(f) Certification by the person making the transcription is as follows:
“I certify that the following is a true transcription of the recorded conversations pertaining to the subject [aircraft accident, near midair collision, etc.] involving [aircraft identification].”
Signature (do not use initials) Matthew Chance
Name Matthew Chance Title Air Traffic Manager Facility/Organization of person preparing the transcript Airville ATCT
NOTE: Digital signatures may be used.
(g) List facilities, position, and/or aircraft making transmissions, using the standard abbreviation for each. Spell out facilities indicated in the transcription using the facility name, followed by the appropriate abbreviation: (ARTCC, ATCT, CCF, FCT, NFCT, FCFSS, CERAP, FSS, IATSC, RAPCON, RATCF, or TRACON). Indicate air carriers by the appropriate company designator from the latest edition of FAA Order 7340.2, Contractions. Indicate air carrier flights by the company designator and the flight number. List in chronological order. Aircraft type (e.g., "BE35") is optional.
(2) The transcription text must be single-spaced. Separate each contact by triple spacing. If a cardinal minute is indicated between contacts, it must represent one of the triple spaces and one blank line must be added (either prior to or after the cardinal minute) to meet the triple spacing requirement. If two or more cardinal minutes are indicated, the triple spacing requirement is met and no blank lines are required. Preface each transmission by the transmitting agency abbreviation if transmissions of more than one agency/facility (center, tower, FSS, aircraft operations office, etc.) are recorded. If breaks occur during any contact, indicate with three dashes.
(a) Enter time entries at the beginning of each transmission if time-announce systems are present. When time-announce systems are not present, enter a remark in the certification regarding the timing method used.
(b) Enter time entries, including seconds to the left of each transmission, if electronically digital time systems are present.
(3) All cardinal minutes must be indicated unless:
Continue reading ↓ 120 of 271 passages shown