DOASS Publication No. 06/2006 

 
  

THE HASHEMITE KINGDOM OF JORDAN

CIVIL AVIATION REGULATORY COMMISSION
DIRECTORATE OF AIRPORTS SAFETY AND STANDARDS

National Bird Strike

Information System (IBIS)

Second Edition

December, 2007 

FOREWORD

This publication contains a description of the National Bird Strike Information System (NBIS) designed to collect and disseminate information on strikes which occur as a result of a collision between an aircraft and a bird / other wildlife.  It also describes the reporting system and states Civil Aviation Regulatory Commission (CARC) obligation to report bird strikes to ICAO in compliance with CARC Publication AN 14-I, Chapter 9, 9.4, Bird Hazard Reduction.

The collection of data will provide the opportunity to carry out necessary analysis in order to establish corrective and mitigation measures to minimize the safety hazard of aircraft operations.

 

 
Capt. Suleiman Obeidat
Chief Commissioner
Civil Aviation Regulatory Commission

 

 
TABLE OF CONTENTS
 

Amendment Record Sheet

i

Foreword

ii

Table of Contents

iii

     

1.

General

1

2.

Reporting

1

3.

What constitutes a reportable bird / other wildlife strike

2

4.

Display of aircraft landing lights

3

5.

The National Bird Hazard Committee

3

6.

Publication in the AIP

4

     

Appendices

 
     

Appendix 1

CARC Form DOASS-6

App 1-1

 

Directions for Filling the Form

App 1-2

 

  1. General 

1.1  To facilitate efforts to reduce bird hazards at and around airports; pilots, airport ground staff, air traffic controllers and aircraft maintenance staff shall report bird/other wildlife strikes identified in paragraph (3) of this publication within the space of the Hashemite Kingdom of Jordan, to Air traffic Control at the airport to be forwarded to the National Bird Hazard Committee / Flight Safety and Standards Directorate; or, as of January 2008, on CARC website. 

1.2  All reports, other than those submitted online on the CARC website, shall be forwarded to the following address: 

 

National Bird Hazard Committee,
Flight Safety and Standards Directorate,
Civil Aviation Regulatory Commission, 
Marka, Amman
Postal Address: 
P. O. Box 7547, 
Area Code 11110 
Fax: 4891653

1.3  Appendix 1 of this publication contains the Bird / Other Wildlife Strike Report Form (CARC Form DOASS-6) developed for this purpose, as well as directions on how to fill the form. 

  1. Reporting
 
2.1 The prescribed reporting form shall be distributed to aircraft operators and to each aerodrome.  The form may be obtained upon request from the Duty Officer, Ground Operations at each airport. 
 
2.2 Copies of the prescribed form are also available from CARC at:  
 
  1. Flight Safety and Standards Directorate.
  2. Accidents Investigation Unit.
  3. The Air Traffic Control Unit.
  4. The AIP.
  5. CARC website.

 

2.3  Every effort shall be made to positively identify the species of the bird/other wildlife involved in the strike.  In connection with incidents on or near an airport, it is requested that pilots make sure that the birds, or as much of the remnants as possible, are collected and handed to the Duty Officer, Ground Operations at the airport, to be forwarded to the biologist concerned.  Any supplementary information on the circumstances under which the incident took place should also be added. 
 
2.4  The Bird/Other Wildlife Strike Reporting Form shall be completed by the pilot following an aircraft collision with a bird. 
 
2.5  The reports shall be sent to CARC / Flight Safety and Standards Directorate by the operator involved.
 
2.6  CARC shall report bird/other wildlife strikes to ICAO to be incorporated in the ICAO Bird Strike Information System (IBIS) as specified in CARC Publication AN 14-I, 9.4.2, in compliance with ICAO requirements.
  1. What constitutes a reportable Bird/other wildlife strike
A bird/other wildlife strike report is required when one or more of the following situations has occurred:
  1. A pilot strikes one or more birds or other wildlife;
  2. Aircraft maintenance personnel identify aircraft damage as having been caused by a wildlife strike;
  3. Personnel on the ground report seeing an aircraft strike one or more birds or other wildlife;
  4. Bird or other wildlife remains are found within 60 meters of the centerline of a runway, unless another reason for the animal's death is identified;
  5. The animal's presence on the airport had a significant negative effect on a flight (e.g., aborted takeoff or landing, high-speed emergency stop, aircraft left pavement area to avoid collision with animal).
  6. Display of aircraft landing lights
 
4.1  It has been shown that the display of landing lights has reduced the number of bird strikes on aircraft.
 
4.2  Where the design limitations of aircraft installations permit, landing lights shall be operated in flight within terminal areas and during take-off, approach-to-land and climb and descent procedures.
 
  • The National Bird Hazard Committee
 
5.1  A National Bird Hazard Committee is formulated for the purpose of bird strike data collection and dissemination in accordance with the requirements specified in Chapter 9 of CARC Publication AN 14-I. 
 
5.2  The committee shall be headed by the Director of Flight Safety and Standards.
 
5.3  The committee shall have the following CARC members:
 

5.4  The committee shall also have representatives from:

5.5  The primary use of this database will be used in policy formulation, analysis, legislation, education, management and drawing strategies to reduce bird strike hazard potential.

5.6  Steps of recording the reports into the database shall be as follows:

5.7   The National Bird Hazard Committee shall be responsible for analyzing the bird strike statistics. 

5.8  The National Bird Hazard Committee shall, after analyzing the bird strike statistics, make recommendations regarding mitigation and corrective measures to minimize wildlife hazard to aircraft operations to be undertaken by aerodrome operators and other concerned governmental agencies. 

  1. A representative from the Accidents Investigation Unit.
  2. A representative from the Directorate of Air Traffic Services.
  3. A representative from the Directorate of Airports Safety and Standards.
  4. Airport Operators.
  5. Ministry of Environment.
  6. Ministry of Agriculture
  7. The Royal Society for the Conservation of Nature
  8. The Flight Safety and Standards Directorate shall be the party responsible for the database.
  9. The Flight Safety and Standards Directorate shall keep all bird/other wildlife strike reports received under 1.1 of this publication.
  10. The Flight Safety and Standards Directorate shall have a database manager who edits each report and consolidates multiple reports for the same strike.  The manager may contact persons who made the form for clarification.
  11. Reports shall be filed chronologically for future reference.
  12. The Flight Safety and Standards Directorate shall forward the report to the Directorate of Airports Safety and Standards (DASS).
  13. DASS shall review the report and take appropriate measures to insure that airports integrate all information in the Airport Wildlife Management Plan.
  14. DASS shall be responsible for reporting the information to ICAO to be incorporated into its International Bird Strike Database.
  15. Publication in the AIP 
  16. Paragraphs (1) to (4) and Appendix 1 of this publication shall be published in the AIP.

Appendix 1

Bird / Other Wildlife Strike Report

 

BIRD/OTHER WILDLIFE STRIKE REPORT

1. Name of Operator

2. Aircraft Make/Model

3. Engine Make/Model

4. Aircraft Registration

5. Date of incident
_______ / _______ / _______
Month        Day          Year

6. Local Time of incident
? Dawn  ? Dusk  ___HR  ___ MN
? Day     ? Night   ? AM    ? PM

7. Airport Name

8. Runway Used

9. Location if En Route (Nearest
      town/reference and governorate)

10. Height (AGL)

11. Speed (IAS)

12. Phase of Flight

13. Part(s) of Aircraft Struck or Damaged

 

?  A. Parked
?  B. Taxi
?  C. Take-off Run
?  D. Climb
?  E. En Route
?  F. Descent
?  G. Approach
?  H. Landing Roll

 

Struck

Damaged

 

Struck

Damaged

A. Radome
B. Windshield
C. Nose
D. Engine No.1
E.  Engine No.2
F. Engine No.3
G. Engine No.4

?
?
?
?
?
?
?

?
?
?
?
?
?
?

H. Propeller
I.  Wing/Rotor
J.  Fuselage
K. Landing Gear
L. Tail
M. Lights
N. Other:

?
?
?
?
?
?
?

?
?
?
?
?
?
?

(Specify if "N " is checked)

14. Effect of Flight

15. Sky Condition

16.  Precipitation

 

? None
? Aborted Take-Off
? Precautionary Landing
? Engines Shut Down
? Other: (Specify)

 

? No Clouds
? Some Clouds
? Overcast

 

? Fog
? Rain
? Snow
? None

17. Bird/Other Wildlife Species

18. Number of Birds / Other Wildlife seen
      and/or struck

19.  Size of Bird(s) seen and/or struck

Number

Seen

Struck

 

? Small
? Medium
? Large

1
2-10
11-100
more than 100

?
?
?
?

?
?
?
?

20. Pilot warned of Birds

? yes

? No

21. Remarks (Describe damage, injuries and other pertinent information)

DAMAGE / COST INFORMATION

22. aircraft time out of service:
_______ hours

23. Estimated cost of repairs or replacement ( JD)
      JD

24. Estimated other costs (JD)
        (e.g. loss of revenue, fuel, hotels):
      JD

Reported by (Optional)

Title

Date

CARC Form DOASS-6

 

Directions for CARC Form DOASS-6
Bird / Other Wildlife Strike Report
  1. Name of Operator: This can be an airline (abbreviations are okay), business, government agency, or if a private pilot, his or her name.
  2. Aircraft make/model:  Abbreviations are okay, but try to include the model (e.g. B737-200).
  3. Engine Make/Model: Abbreviations are allowed (e.g., PW 4060, GECT7, LYC 580).
  4. Aircraft Registration: This means the registration number for Jordanian aircraft.
  5. Date of Incident: Give the local date, not the ZULU GMT date.
  6. Local Time of Incident: Check the appropriate light conditions and fill in the hour and minute local time and check AM or PM or use the 24 clock and skip AM/Pm.
  7. Airport Name: Use the airport name or 3 letter code and location (city/country).
  8. Runway used: Self explanatory.
  9. Location if En Route: Put the name of the nearest city region, and country.
  10. Height AGL: Put the feet (meters) above ground level at the time of the strike (if you don’t know, use MSL and indicate this.)  For take-off run and landing roll, it must be zero.
  11. Speed (IAS): Speed at which the aircraft was traveling when the strike occurred.
  12. Phase of Flight: Phase of flight during which the strike occurred.
  13. Part(s) of Aircraft Struck or Damaged: Check which parts were struck and damaged.  If a part was damaged but not struck, indicate this with a check on the damaged column only and indicate in comments (#21) why this happened (e.g., the landing gear might be damaged by animal strike, causing the aircraft to flip over and damage parts not struck by animal).
  14. Effect on Flight: You can check more than one and if you check  "Other  "  , please explain in Comments (#21).
  15. Sky Condition: You may check the one that applies.
  16. Precipitation: You may check more than one that applies.
  17. Bird/Other Wildlife Species: Try to be accurate.  If you don’t know, put unknown and some description.  Collect feathers or remains for identification for damaging strikes.
  18. Number of birds seen and /or struck: Check the box in the Seen column with the correct number if you saw the birds/other wildlife before the strike and check the box in the Struck column to show how many were hit.  The exact number can be written next to the box.
  19. Size of Bird(s) / Other wildlife: Check what you think is the correct size (e.g., sparrow = small,     gulls = medium, geese = large).
  20. Pilot Warned of Birds: Check the correct box (even if it was an ATS warning or NOTAM).
  21. Remarks: Be as specific as you can.  Include information about the extent of the damage, injuries, anything you think would be helpful to know (e.g., number of birds ingested).
  22. Aircraft time out of service: Record how many hours the aircraft was out of service.
  23. Estimated cost of repairs or replacement: This may not be known immediately, but the data can be sent at a later date or put down a contact name and number for this data.
  24. Estimated other cost: Include loss of revenue, fuel, hotels, etc. (see directions for #23).
  25. Reported by: Although this is optional, it is helpful if questions arise about the information on the form (a telephone number could also be included).
  26. Title: This can be Pilot, Tower, Airport Operation, Airline Operations, Flight Safety, etc.
  27. Date: Date the form was filled out.