Notification of close proximity encounters and analysis of data
Title I — Civil Aviation Matters
Read this section in the full bill →
No wording changed between Passed the House and Sent to the Senate.
How the text changed
(a) In general Not later than 180 days after the date of enactment of this Act, the Administrator, in accordance with the mandatory occurrence reporting requirements in FAA Order JO 7210.632A, titled Air Traffic Organization Occurrence Reporting (or any successor document), FAA Order 8020.11D, titled Aircraft Accident and Incident Notification, Investigation, and Reporting (or any successor document), and FAA Advisory Circular AC 90–120, titled Operational Use of Airborne Collision Avoidance Systems (or any successor document), shall establish a process to— (1) notify, with respect to each event, parties involved with— (A) a near midair collision event; (B) a traffic collision avoidance system resolution advisory event; (C) a close proximity encounter, as defined pursuant to section 122; and (D) any other events, as determined by the Administrator; and (2) provide deidentified event data to the Aviation Safety Information Analysis and Sharing program. (b) Requirements In establishing the process under subsection (a), the Administrator shall— (1) establish a database that tracks the details of events described in subsection (a)(1); (2) continuously monitor and review such database to identify areas of potential traffic conflict for safety assurance and safety risk management; (3) ensure timeliness of notifications to the parties described in subsection (a)(1) so that relevant data remains available before meaningful safety analysis, reporting, or corrective action is no longer practicable; (4) consider informing, with deidentified or aggregated data, other frequent operators of events described in subsection (a)(1); and (5) consider the practicality and usefulness of notification requirements for— (A) airport surface loss of separation; (B) loss of separation with terrain or obstacles; (C) airborne loss of separation; and (D) any other close proximity encounters as determined by the Administrator. (c) Consultation In establishing the process under subsection (a), the Administrator shall consult with— (1) air carriers operating under part 121 of title 14, Code of Federal Regulations; (2) air carriers operating under part 135 of title 14, Code of Federal Regulations; (3) air carriers operating under part 91 of title 14, Code of Federal Regulations; (4) organizations representing helicopter aviation operators and pilots; (5) organizations representing the general aviation community; (6) organizations representing business aviation operators; (7) organizations representing experimental aircraft operators; (8) organizations representing powered-lift operators; (9) organizations representing certified collective bargaining representatives of airline pilots; (10) the certified exclusive bargaining representatives of air traffic controllers of the Administration certified under section 7111 of title 5, United States Code; (11) FAA subject matter experts, including aviation safety inspectors; and (12) other aviation safety experts determined appropriate by the Administrator. (d) Briefing Not later than 30 days after establishing the process required under subsection (a), the Administrator shall brief the appropriate committees of Congress on the implementation of this section. (e) Report Not later than 1 year after establishing the process required under subsection (a), and annually thereafter, the Administrator shall submit to the appropriate committees of Congress a report containing— (1) data on number and location of— (A) near midair collision events; (B) traffic collision avoidance system resolution advisory events; and (C) close proximity encounters, as defined pursuant to section 122; (2) the average time of notification to parties involved in such events; (3) identified locations of concern or other trends; and (4) actions taken to mitigate identified risks and reduce such events. (f) Protection of data (1) In general Data collected in response to subsection (a) shall be used solely for safety assurance and safety risk management. (2) Consistency with existing safety programs The Administrator shall ensure consistency with existing voluntary safety programs, including the Aviation Safety Action Program, the Aviation Safety Reporting System, the Air Traffic Safety Action Plan, and flight operational quality assurance programs.
(a) In general Not later than 180 days after the date of enactment of this Act, the Administrator, in accordance with the mandatory occurrence reporting requirements in FAA Order JO 7210.632A, titled Air Traffic Organization Occurrence Reporting (or any successor document), FAA Order 8020.11D, titled Aircraft Accident and Incident Notification, Investigation, and Reporting (or any successor document), and FAA Advisory Circular AC 90–120, titled Operational Use of Airborne Collision Avoidance Systems (or any successor document), shall establish a process to— (1) notify, with respect to each event, parties involved with— (A) a near midair collision event; (B) a traffic collision avoidance system resolution advisory event; (C) a close proximity encounter, as defined pursuant to section 122; and (D) any other events, as determined by the Administrator; and (2) provide deidentified event data to the Aviation Safety Information Analysis and Sharing program. (b) Requirements In establishing the process under subsection (a), the Administrator shall— (1) establish a database that tracks the details of events described in subsection (a)(1); (2) continuously monitor and review such database to identify areas of potential traffic conflict for safety assurance and safety risk management; (3) ensure timeliness of notifications to the parties described in subsection (a)(1) so that relevant data remains available before meaningful safety analysis, reporting, or corrective action is no longer practicable; (4) consider informing, with deidentified or aggregated data, other frequent operators of events described in subsection (a)(1); and (5) consider the practicality and usefulness of notification requirements for— (A) airport surface loss of separation; (B) loss of separation with terrain or obstacles; (C) airborne loss of separation; and (D) any other close proximity encounters as determined by the Administrator. (c) Consultation In establishing the process under subsection (a), the Administrator shall consult with— (1) air carriers operating under part 121 of title 14, Code of Federal Regulations; (2) air carriers operating under part 135 of title 14, Code of Federal Regulations; (3) air carriers operating under part 91 of title 14, Code of Federal Regulations; (4) organizations representing helicopter aviation operators and pilots; (5) organizations representing the general aviation community; (6) organizations representing business aviation operators; (7) organizations representing experimental aircraft operators; (8) organizations representing powered-lift operators; (9) organizations representing certified collective bargaining representatives of airline pilots; (10) the certified exclusive bargaining representatives of air traffic controllers of the Administration certified under section 7111 of title 5, United States Code; (11) FAA subject matter experts, including aviation safety inspectors; and (12) other aviation safety experts determined appropriate by the Administrator. (d) Briefing Not later than 30 days after establishing the process required under subsection (a), the Administrator shall brief the appropriate committees of Congress on the implementation of this section. (e) Report Not later than 1 year after establishing the process required under subsection (a), and annually thereafter, the Administrator shall submit to the appropriate committees of Congress a report containing— (1) data on number and location of— (A) near midair collision events; (B) traffic collision avoidance system resolution advisory events; and (C) close proximity encounters, as defined pursuant to section 122; (2) the average time of notification to parties involved in such events; (3) identified locations of concern or other trends; and (4) actions taken to mitigate identified risks and reduce such events. (f) Protection of data (1) In general Data collected in response to subsection (a) shall be used solely for safety assurance and safety risk management. (2) Consistency with existing safety programs The Administrator shall ensure consistency with existing voluntary safety programs, including the Aviation Safety Action Program, the Aviation Safety Reporting System, the Air Traffic Safety Action Plan, and flight operational quality assurance programs.
added wordsremoved wordsComparison computed by Public Law Tracker from the official text