The foundation to our understanding of
wildlife hazards to aviation lies in the quantity and quality of
strike data within the National Wildlife Strike Database (NWSD).
The database extends from 1990 - 2020 and is a collaborative effort
begun in 1995 between the FAA and the USDA. Although the quantity
of strikes reported each year over three decades has grown
significantly, the quality assurance provided by the USDA is the
keystone allowing the NWSD to be invaluable throughout the aviation
industry. Pilots, airports, and others involved in wildlife strikes
report strike data voluntarily on an as needed basis. The data
collection is used by the FAA, USDA Wildlife Service, airports,
engine and airframe manufacturers, ICAO and foreign countries to
develop standards to address bird and other wildlife hazards to
aircraft and injury to personnel and to develop wildlife habitat
control methods on or adjacent to airports. Using wildlife strike
reports, the FAA can determine the hazard level of species struck,
track national trends, and provide a scientific foundation for
regulatory guidance concerning mitigation of risks from wildlife
strikes. Airports and wildlife biologists use the data to identify
and mitigate hazardous species, to identify strike dynamics and
attractants, and to evaluate the effectiveness of their wildlife
management programs. Engine and airframe manufacturers use the data
to evaluate the effectiveness of aircraft components. A wildlife
strike report must include the incident date and time but can also
include information about the airport, aircraft, aircraft operator,
environmental conditions, damage, costs, effect on flight, wildlife
involved, and incident reporter. Reporters can also attach
photographs of damage and wildlife involved. The data elements
collected help the FAA and partner organizations identify trends in
wildlife strikes and their impact on U.S. aviation. Incident
reporter contact information is collected for internal use only to
contact reporters if more details about an incident are needed and
to help identify potential duplicate reports. The information
collected is authenticated and stored electronically in the FAA
National Wildlife Strike Database (https://wildlife.faa.gov/home).
This database is accessible to international, national, state, and
local governments and both public and private organizations and
individuals for use in addressing the wildlife aircraft strike
issue. The FAA Wildlife Hazard Program, managed by the Office of
Airports and the Airport Technology Research & Development
Branch, will retain control over the information and safeguard it
from improper access, modification, and destruction, consistent
with FAA standards for confidentiality, privacy, and electronic
information. See response to Question 10 of this Supporting
Statement for more information on confidentiality and privacy. The
information collection is designed to yield data that meet all
applicable information quality guidelines.
US Code:
49
USC 44706 Name of Law: Airport Operating Certificates
In the previous submissions FAA
counted responses from federally employed air traffic controllers
among the general public responses. However this submission more
correctly counts the number of responses submitted by federal Air
Traffic Controllers and the associated burden, toward the Cost to
Federal Government. This is not a change to the collection but a
correction in the way we are reporting data submitted by this group
of federal employees. We have also included the labor cost to the
public of submitting wildlife remains for identification. The
agency has separated collection activity into appropriate
information collections; there have been no additional forms or
applications added.
On behalf of this Federal agency, I certify that
the collection of information encompassed by this request complies
with 5 CFR 1320.9 and the related provisions of 5 CFR
1320.8(b)(3).
The following is a summary of the topics, regarding
the proposed collection of information, that the certification
covers:
(i) Why the information is being collected;
(ii) Use of information;
(iii) Burden estimate;
(iv) Nature of response (voluntary, required for a
benefit, or mandatory);
(v) Nature and extent of confidentiality; and
(vi) Need to display currently valid OMB control
number;
If you are unable to certify compliance with any of
these provisions, identify the item by leaving the box unchecked
and explain the reason in the Supporting Statement.