This site displays a prototype of a “Web 2.0” version of the daily
Federal Register. It is not an official legal edition of the Federal
Register, and does not replace the official print version or the official
electronic version on GPO’s govinfo.gov.
The documents posted on this site are XML renditions of published Federal
Register documents. Each document posted on the site includes a link to the
corresponding official PDF file on govinfo.gov. This prototype edition of the
daily Federal Register on FederalRegister.gov will remain an unofficial
informational resource until the Administrative Committee of the Federal
Register (ACFR) issues a regulation granting it official legal status.
For complete information about, and access to, our official publications
and services, go to
About the Federal Register
on NARA's archives.gov.
The OFR/GPO partnership is committed to presenting accurate and reliable
regulatory information on FederalRegister.gov with the objective of
establishing the XML-based Federal Register as an ACFR-sanctioned
publication in the future. While every effort has been made to ensure that
the material on FederalRegister.gov is accurately displayed, consistent with
the official SGML-based PDF version on govinfo.gov, those relying on it for
legal research should verify their results against an official edition of
the Federal Register. Until the ACFR grants it official status, the XML
rendition of the daily Federal Register on FederalRegister.gov does not
provide legal notice to the public or judicial notice to the courts.
Rule
Enter a search term or FR citation e.g.
88 FR 38230 FR 78782024-13208USDA09/05/24RULE0503-AA39SORN
Choosing an item from
full text search results
will bring you to those results. Pressing enter in the search box
will also bring you to search results.
Choosing an item from
suggestions
will bring you directly to the content.
This direct final rule will be effective February 16, 2016, without further notice, unless the NTSB receives adverse comment by January 14, 2016. If the NTSB receives adverse comment, we will publish a timely withdrawal of the direct final rule in the Federal Register informing the public that the rule will not take effect.
Table of Contents
Enhanced Content - Table of Contents
This table of contents is a navigational tool, processed from the
headings within the legal text of Federal Register documents.
This repetition of headings to form internal navigation links
has no substantive legal effect.
Notification and Reporting of Aircraft Accidents or Incidents and Overdue Aircraft, and Preservation of Aircraft Wreckage, Mail, Cargo, and Records
Public Comments
Enhanced Content - Public Comments
Comments are no longer being accepted.
See DATES for details.
Regulations.gov Data
Enhanced Content - Regulations.gov Data
FederalRegister.gov retrieves relevant information about this document
from Regulations.gov to provide users with additional context. This
information is not part of the official Federal Register document.
Notification and Reporting of Aircraft Accidents or Incidents and Overdue Aircraft, and Preservation of Aircraft Wreckage, Mail, Cargo, and Records
Document page views are updated periodically throughout the day and are
cumulative counts for this document. Counts are subject to sampling,
reprocessing and revision (up or down) throughout the day.
Page views
2,079
as of
10/08/2026 at 8:15 pm EDT
Other Formats
Enhanced Content - Other Formats
This document is also available in the following formats:
This PDF is FR Doc. 2015-30758 as it appeared on Public Inspection on
12/14/2015 at 8:45 am.
If you are using public inspection listings for legal research, you
should verify the contents of the documents against a final, official
edition of the Federal Register. Only official editions of the
Federal Register provide legal notice of publication to the public and judicial notice
to the courts under 44 U.S.C. 1503 & 1507.
Learn more here.
Published Document: 2015-30758 (80 FR 77586)
This document has been published in the Federal Register. Use the PDF linked in the document sidebar for the official electronic format.
AGENCY:
National Transportation Safety Board (NTSB).
ACTION:
Direct final rule.
SUMMARY:
The NTSB is publishing an amendment to its regulations concerning notification and reporting requirements with regard to aircraft accidents or incidents, titled, “Immediate notification.” The regulation currently requires reports of Airborne Collision and Avoidance System (ACAS) advisories issued under certain specific circumstances. The NTSB now narrows the ACAS reporting requirement, consistent with the agency's authority to issue non-controversial amendments to rules, pursuant to the direct final rulemaking procedure. The NTSB also updates its contact information for notifications.
DATES:
This direct final rule will be effective February 16, 2016, without further notice, unless the NTSB receives adverse comment by January 14, 2016. If the NTSB receives adverse comment, we will publish a timely withdrawal of the direct final rule in the
Federal Register
informing the public that the rule will not take effect.
ADDRESSES:
A copy of this direct final rule, published in the
Federal Register
, is available for inspection and copying in the NTSB's public reading room, located at 490 L'Enfant Plaza SW., Washington, DC 20594-2000. Alternatively, a copy of the rule is available on the NTSB Web site, at
http://www.ntsb.gov,
and at the government-wide Web site on regulations, at
http://www.regulations.gov.
FOR FURTHER INFORMATION CONTACT:
Scott Dunham, National Resource Specialist—ATC, Office of Aviation Safety, (202) 314-6387.
SUPPLEMENTARY INFORMATION:
Regulatory History
On October 7, 2008, the NTSB published a Notice of Proposed Rulemaking (NPRM) titled “Notification and Reporting of Aircraft Accidents or Incidents and Overdue Aircraft, and Preservation of Aircraft Wreckage, Mail, Cargo, and Records.” 73 FR 58520. The NPRM proposed several additions to 49 CFR 830.5, to require reports of various types of serious aviation incidents. Among the proposed requirements, the NTSB sought mandatory reports of Airborne Collision Avoidance System (ACAS) resolution advisories issued either (i) when an aircraft is being operated on an instrument flight rules (IFR) flight plan and compliance with the advisory is necessary to avert a substantial risk of collision between two or more aircraft, or (ii) to an aircraft operating in class A airspace. 73 FR 58523-24.
On January 7, 2010, the NTSB published its amendment to the final rule by requiring operators of civil aircraft to report certain ACAS incidents, along with other types of serious incidents. 75 FR 922. The NTSB explained its intent in imposing this reporting requirement is to identify, evaluate, and investigate (when appropriate) serious incidents where aircraft maneuvers were required to avert a substantial risk of collision between aircraft equipped with traffic collision avoidance systems (TCAS) and other aircraft and to evaluate situations where resolution advisories occur between aircraft under positive control in class A airspace. The NTSB clarified it did not intend to require the reporting of all resolution advisories or, outside class A airspace, to require the reporting of any resolution advisory resulting from an encounter between aircraft where no substantial risk of collision exists. 75 FR 925-26.
The NTSB stated it believed the reporting requirement would achieve the NTSB's objective of receiving notification of aircraft encounters that
( printed page 77587)
present a significant risk of collision. In the Final Rule, the NTSB adopted the proposed language, which now appears at 49 CFR 830.5(a)(10).[1]
Collection of Reports
By this direct final rule, the NTSB removes the requirement of notifications of ACAS reports from aircraft operators within Class A airspace. The NTSB has determined, through review of the types of events submitted, that it is possible to reduce the scope of the notification requirement while still achieving the safety objective of the rule, which is to increase our awareness of potentially hazardous occurrences in the air traffic control system.
When it issued the requirement of § 830.5(a)(10), the NTSB anticipated its collection of ACAS incident reports would educate the agency concerning whether the TCAS equipment functioned appropriately. In addition, the NTSB sought information concerning whether operators received improper resolution advisories, as well as a general understanding of the effectiveness of TCAS.
Collecting the data on the volume of TCAS alerts that fulfill the criteria listed in § 830.5(a)(10) has been educational and has assisted the NTSB Office of Aviation Safety with understanding the general effectiveness of TCAS as well as the types of encounters that are likely to cause TCAS resolution advisories.
Amending § 830.5(a)(10) to narrow the reporting requirement of TCAS resolution advisories also achieves the purpose of Executive Order 13579, “Regulation and Independent Regulatory Agencies” (76 FR 41587, July 14, 2011). The purpose of Executive Order 13579 is to ensure all agencies adhere to the key principles found in Executive Order 13563, “Improving Regulation and Regulatory Review” (76 FR 3821, January 21, 2011), which emphasizes agencies must promulgate regulations that are written plainly and clearly written, and do not present duplicative or unnecessary requirements. Removing the requirement of notifications from aircraft operators within Class A airspace that receive a TCAS resolution advisory achieves the purpose of Executive Order 13563, because the NTSB has concluded the notifications are not necessary.
Direct Final Rulemaking Procedure
The NTSB has determined it is appropriate to narrow the reporting requirement in § 830.5(a)(10) by publishing a Direct Final Rule. On September 23, 2015, the NTSB published a Final Rule codifying its authority to utilize the direct final rulemaking process to alter rules that are not controversial and to which the NTSB does not expect substantive comments. 80 FR 57307. As explained in its NPRM describing this process, agencies frequently use the direct final rulemaking process for minor changes to rules to which it does not expect adverse comments. 80 FR 34874 (June 18, 2015). The NTSB's rule on this procedure, codified at 49 CFR 800.44, states a direct final rule makes changes to a regulation which will take effect on a certain date unless the NTSB receives an adverse comment or a notice of intent to file an adverse comment. If the NTSB receives an adverse comment or notice of intent to file one, the agency will publish a document in the
Federal Register
withdrawing the rule change. The NTSB may then issue an NPRM proposing the change it sought to make by way of the direct final rulemaking process.
Id.
§ 800.44(d). Section 800.44 also defines “adverse comment” for purposes of the direct final rulemaking procedure.
This change limits required notifications to events that evidence a significant risk of collision, thereby reducing the regulatory burden on aircraft operators while continuing to achieve the safety objective of the rule. Informal discussions with organizations such as Air Line Pilots Association, International, Airlines for America, Regional Airline Association, and National Air Carrier Association have shown these organizations support the amendment. Overall, we do not expect to receive any negative industry comments.
Legal Analyses and Effective Date
The NTSB notes it analyzed the potential application of the Regulatory Flexibility Act (5 U.S.C. 601-612) to this rule. The NTSB certifies under 5 U.S.C. 605(b) that this rule would not have a significant economic impact on a substantial number of small entities.
In addition, this rule will not require collection of new information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). Operators continue to have the option of notifying the NTSB of an ACAS advisory that fulfills the requirements of this rule via telephone or email. The NTSB is continuing to work with the Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), to obtain an OMB control number under the Paperwork Reduction Act to collect reports of ACAS advisories, as well as other notifications, via a web-based form. See 80 FR 38751 (July 7, 2015).
Pursuant to 49 CFR 800.44(c), the NTSB will publish a confirmation rule in the
Federal Register
if it has not received an adverse comment or notice of intent to file an adverse comment within 30 days of the date of publication of this direct final rule.
The operator of any civil aircraft, or any public aircraft not operated by the Armed Forces or an intelligence agency of the United States, or any foreign aircraft shall immediately, and by the most expeditious means available, notify the nearest National Transportation Safety Board (NTSB) office,[1]
when:
(a) An aircraft accident or any of the following listed serious incidents occur:
* * * * *
(10) Airborne Collision and Avoidance System (ACAS) resolution advisories issued when an aircraft is being operated on an instrument flight rules flight plan and compliance with the advisory is necessary to avert a
( printed page 77588)
substantial risk of collision between two or more aircraft.
* * * * *
Christopher A. Hart,
Chairman.
Footnotes
1.
On December 8, 2011, the NTSB published an NPRM proposing to exempt certain “monitor vertical speed” advisories from § 830.5(a)(10)(ii). 76 FR 76686. The NTSB did not incorporate this exemption in an amendment to the rule.
1.
NTSB headquarters is located at 490 L'Enfant Plaza SW., Washington, DC 20594. Contact information for the NTSB's regional offices is available at
http://www.ntsb.gov.
To report an accident or incident, you may call the NTSB Response Operations Center, at 844-373-9922 or 202-314-6290.