***New*** ASAP File Attachment Capability ***New***
BLUF: ASAP file attachment capabilities promote a strong culture of reporting, enable more effective report resolution, and result in more powerful messaging to a wider AF audience. AF Airmen can now amplify ASAP voluntary reporting by attaching valuable additional documentation. We noticed submitters often referenced or emailed additional documentation for their ASAP reports. Noticing this need, we’re delivering additional ASAP reporting capability by adding this new feature, so you can attach additional documentation or information! The file attachment feature is conveniently located between the “narrative of the event” and the “suggestions to prevent a recurrence of this hazard or error” blocks on the ASAP form.
An important note about attaching safety reports to an ASAP: If you decide to attach a safety report or form to enhance your ASAP submission, please ensure that your safety report is first submitted to the appropriate Safety office in accordance with AFI guidance and/or local guidance. Thanks for using ASAP to help prevent mishaps and complete the mission more safely.
Frequently Asked Questions
ASAP
The Military Aviation Safety Action Program (ASAP) is a program designed to enhance aviation safety through the prevention of accidents and incidents. It is an identity protected, self-reporting system modeled after systems currently in place at many airlines that encourage the voluntary reporting of operations and maintenance/logistics safety issues and events. It is designed to provide a non-punitive environment for the open reporting of safety concerns and information that might be critical to identifying precursors to accidents. These safety concerns may be either observed or experienced by the submitter. The goal is to prevent mishaps by addressing those unintentional errors, hazardous situations and events, or high-risk activities not identified and/or correctable by other methods or through traditional safety reporting sources. The reported information is used to reduce mishaps through operational, maintenance/logistics, training and procedural enhancements. Due to its capability of providing early identification of needed safety improvements, ASAP offers significant potential for avoiding mishaps. However, mishap prevention can only succeed with your input…..
ASAP STATUS SCOREBOARD
SUBMIT A REPORT
CONTACT YOUR FSO AS QUICKLY AS POSSIBLE FOR APPROPRIATE GUIDANCE."
If you are experiencing issues accessing ASAP using your CAC, please click here.
What Types of events to report?
Answer: Safety of flight related events not normally reported or captured by other methods.
- Personal errors that could have led to a mishap/incident.
- Unintentional errors by other individuals (including ATC), crewmembers or other members of your flight which could have led to a mishap or which resulted in a “close call.”
- Errors committed by other individuals or organizations that adversely affected or could have affected the safety of your flight including procedural errors, problems with SOPs, aircraft systems/design concerns, etc.
- Any unsafe action, event or condition encountered during any portion of a flight or mission from mission planning to ground operations to mission execution to crew rest.
- Observed hazards that may not have directly affected your operation, but may affect another's.
- Hazardous situations not reported by other methods such as safety reports, HATRs, etc.
- Any other events considered worthy of reporting in the name of flying safety.
If in doubt, FILL IT OUT. Remember, “zero accidents” is a shared responsibility.
Reporting Tips
This is an identity protected reporting system, which means we cannot contact you for more details or return feedback unless you provide optional contact information. However, we encourage submitters to add your name and contact information, especially if you are reporting an unsafe situation or event not under your direct control (i.e., you or your friends did nothing wrong). The ability to contact the submitter for further information is of great benefit when processing your report - plus it allows us to provide direct feedback as opposed to leaving notes for you in the Newsletter, and hoping you find them. Please provide sufficient detail about the event so it can properly be evaluated. For example, if the safety event involves a checklist issue or discrepancy that could possibly lead to a safety hazard or mishap, at a minimum please include publication name/number/date, checklist section/page number, step number, step narrative, problems with the information presented and how the discrepancy was discovered. If you have specific recommendations that may prevent a future reoccurrence of an event or mitigate an existing hazard, please provide your suggestions in the report.