22.02.2013 Views

MEMORANDUM FOR A1 - Air Force E-Publishing

MEMORANDUM FOR A1 - Air Force E-Publishing

MEMORANDUM FOR A1 - Air Force E-Publishing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AFI91-202 5 AUGUST 2011 65<br />

owning MAJCOMS and may be scheduled during reoccurring inspections or staff<br />

assistance visits.<br />

7.3.1.3.3. Consider potential wildlife strike hazards when developing or revising<br />

operational procedures, training routes, ranges, instrument approach and departure<br />

procedures, establishing Memorandums of Agreement (MOA) or low altitude tactical<br />

navigation areas.<br />

7.3.1.4. Wing, Base and Installation Safety Offices are responsible for the following:<br />

7.3.1.4.1. Base Level BASH Program. Host <strong>Air</strong> <strong>Force</strong>, AFRC or ANG installations<br />

with flying operations will establish a BASH program. The BASH program will<br />

include all tenant-flying units. The BASH program requires complete documentation<br />

of local wildlife hazards, effects on missions and possible solutions to include hazards<br />

surrounding ranges used by local flying units. Tenant units located on an airfield that<br />

is not hosted by the <strong>Air</strong> <strong>Force</strong>, AFRC or ANG will establish a BASH program with<br />

host authority (civilian airport, Naval <strong>Air</strong> Station, Federal airfield, etc.). The BASH<br />

program will document coordination with the host authority on reducing wildlife<br />

hazards.<br />

7.3.1.4.2. Review the BASH plan annually for accuracy and compliance with current<br />

directives, revising as necessary. Ensure all tenant units are included in the base<br />

BASH plan.<br />

7.3.1.4.3. BASH programs at overseas locations depend on host nation support and<br />

regulations. MAJCOMs will evaluate those plans to ensure the spirit of this<br />

instruction is complied with to the maximum extent possible.<br />

7.3.1.4.4. Each installation with flying operations must develop a contingency plan<br />

that lists responsibilities and procedures for wildlife control. Due to the complexities<br />

of hazard abatement and potential for loss of aircraft and crew, it is strongly<br />

recommended that a dedicated wildlife hazard management specialist be retained on<br />

staff.<br />

7.3.1.4.5. Establish a Bird Hazard Working Group (BHWG) consisting of<br />

organizations involved in airfield wildlife control, habitat management, operations<br />

and safety. The BHWG must meet at least semi-annually with minutes maintained.<br />

The vice installation commander or equivalent will chair the meeting. The BHWG<br />

will coordinate base improvement projects, e.g., base beautification, wastewater<br />

treatment, golf courses, etc., for BASH-related issues.<br />

7.3.1.4.6. Develop a Bird Hazard Warning System to inform aircrews of possible<br />

flight hazards due to wildlife activity in local areas. Bird Watch Condition (BWC)<br />

codes will be used to communicate local wildlife activity along with location, number<br />

and type of wildlife. Installation BASH plans will specify aircrew notification<br />

procedures for BWC changes. The most expeditious means of communicating the<br />

status change should be used (e.g. ATC or SOF radio transmissions combined with<br />

ATIS updates or other broadcast medium). BWC codes are defined as:<br />

7.3.1.4.6.1. SEVERE. Wildlife activity on or immediately above the active<br />

runway or other specific location representing high potential for strikes.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!