As many of you may have seen recently, there may be a “pendulum swing” within the agency at the moment. With this often comes an attempted tightening of the grip on the workforce. One place where this has been seen is in the ATSAP/MOR process. The agency seems to want to come down on those that could/should have reported via ATSAP/MOR but didn’t. This is just a quick reminder of the reportable items. Remember as a CIC you are still covered under the ATSAP program, but you still have a responsibility to report MOR items to management. This plays out simply for us in the center environment, because we just pass it along to the OMIC and they handle the rest. The below items require a MOR report:

 

•   Airborne loss of separation

•   Airport surface loss of separation

•   Terrain or obstruction loss of separation

•   Airborne air traffic control anomaly involving airspace, altitude, route or speed that does not result in a loss of separation (missed point-outs or handoffs, TCAS or RA alerts, SUA spillout, or airspace violations with SUAs.)

•   Airport Environment (this would be rare for us, but, include any kind of surface incident reported to us).

•   Communication issues (NORDO, departure that never contacts ATC).

•   Emergency or in-flight hazard (Medical, bird strike, equipment, fuel, VFR trapped on top of clouds, laser event, hijack, bomb threat etc).

•   Inquiry (concern from an outside entity involving aircraft proximity or operation including NMAC notification from a flight crew).

 

Although it is voluntary, I would encourage you all to file an ATSAP to report any other event that you find out of the norm or inform the OMIC to see if an event warranted an MOR.

Derek Adams

Comment