MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
120 AFI91-202 5 AUGUST 2011<br />
Attachment 3<br />
HAZARDOUS AIR TRAFFIC REPORT PROGRAM<br />
A3.1. General. Hazard air traffic report information is vital to <strong>Air</strong> <strong>Force</strong> flight safety. This<br />
attachment establishes procedures for reporting and investigating near midair collisions (NMAC)<br />
and other hazardous air traffic conditions. Report all HATR incidents using the AF Form 651,<br />
Hazardous <strong>Air</strong> Traffic Report (HATR). Use of information taken from these reports is for mishap<br />
prevention only and not for disciplinary actions. HATR information is not privileged information<br />
and is releasable outside <strong>Air</strong> <strong>Force</strong> channels except for the identity of the personnel involved.<br />
A3.2. Reportable Incidents.<br />
A3.2.1. NMAC. <strong>Air</strong>crew took abrupt evasive action to avoid a collision or would have taken<br />
evasive action if circumstances allowed. NOTE: In many cases, the term AIRMISS is the<br />
terminology used for European incidents.<br />
A3.2.2. <strong>Air</strong> Traffic Control (ATC). Any ATC service that did or could contribute to a<br />
hazardous air traffic condition. Example: Failure by ATC to maintain required separation<br />
between aircraft under their control.<br />
A3.2.3. <strong>Air</strong>crew Deviation. Any aircrew actions that did or could contribute to a hazardous<br />
air traffic condition.<br />
A3.2.4. Communication or Navigational Aid (NAVAID). An equipment indication/<br />
malfunction that did or could contribute to a hazardous air traffic condition.<br />
A3.2.5. Procedural Guidance. Procedures described in any publication or directive that did<br />
or could contribute to a hazardous air traffic condition.<br />
A3.2.6. Ground Incidents. Any occurrence on the movement area that endangered an<br />
airborne aircraft or an aircraft operating on the ground.<br />
A3.2.7. TCAS Resolution Advisories (RA). TCAS RAs (involving USAF aircraft/RPA) that<br />
require the aircraft/RPA to deviate from an assigned clearance. This includes USAF<br />
aircraft/RPA triggering TCAS RA aboard civil or other DoD aircraft.<br />
A3.3. Responsibilities of the Unit Commander. Unit commanders will ensure AF Form 651 is<br />
available to aircrews at base operations workplaces, flying squadron operations offices, in trip<br />
kits and in USAF ATC workplaces. Commanders must emphasize the importance of identifying<br />
hazardous situations through the HATR program and encourage the filing of appropriate HATRs<br />
as a method of preventing future mishaps.<br />
A3.4. Responsibility of the Individual Filing the HATR. Any person (e.g., air traffic<br />
controller, pilot, safety officer, etc.) aware that a reportable event occurred shall file a HATR.<br />
Report the details on AF Form 651 in the following manner.<br />
A3.4.1. If the individual is at the <strong>Air</strong> <strong>Force</strong> base where the incident occurred, file the report<br />
within 24 hours to the base safety office.<br />
A3.4.2. If the incident occurred at another location (other than home station); report the<br />
incident to <strong>Air</strong> <strong>Force</strong> safety personnel at the nearest <strong>Air</strong> <strong>Force</strong> safety office or the next<br />
landing location with an <strong>Air</strong> <strong>Force</strong> safety office.
Change language