 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mgm controller expressed concern regarding lack of military NOTAM information.
| Attributes | |
| ACN | 737569 |
| Time | |
| Date | 200705 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : mgm.tracon |
| State Reference | AL |
| Aircraft 1 | |
| Controlling Facilities | tower : zzz.tower |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : flight data controller : handoff position |
| Qualification | controller : radar |
| Experience | controller radar : 19 controller supervisory : 2 controller time certified in position1 : 2.5 |
| ASRS Report | 737569 |
| Events | |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | ATC Human Performance FAA |
| Primary Problem | Ambiguous |
Narrative:
An F15 requested holding at lomax intersection and was cleared to do so. He then reported not receiving the mxf TACAN (a component of the intersection). A check with mxf tower revealed that the TACAN was NOTAM'ed OTS and expected to be out for 3 more days. Further research showed that the TACAN had already been out for 24 hours and a NOTAM had been issued. When an AFSS issues a NOTAM that a NAVAID is OTS; they call the affected ATC facilities and tell them about the NOTAM. Apparently when mxf basops issues a military NOTAM into the dins NOTAM system; they do not have an effective similar procedure to ensure that all of the affected ATC facilities are notified. We have no online/real-time method to know about active NOTAMS. If the appropriate AFSS/ARTCC/basops does not call us and tell us about them; we will not know. This is a safety issue when we have to divert attention from controling airplanes to search for information we should already have. It could be a bigger safety issue if we issue an approach clearance based on a NAVAID that is OTS. About 30 mins later; another aircraft (military) requested the TACAN approach and was surprised to learn that the TACAN was OTS. This also goes to show that even when a NOTAM is issued; somehow the pilots also don't get the word; making it even more important that we know about it.
Original NASA ASRS Text
Title: MGM CTLR EXPRESSED CONCERN REGARDING LACK OF MIL NOTAM INFO.
Narrative: AN F15 REQUESTED HOLDING AT LOMAX INTXN AND WAS CLRED TO DO SO. HE THEN RPTED NOT RECEIVING THE MXF TACAN (A COMPONENT OF THE INTXN). A CHK WITH MXF TWR REVEALED THAT THE TACAN WAS NOTAM'ED OTS AND EXPECTED TO BE OUT FOR 3 MORE DAYS. FURTHER RESEARCH SHOWED THAT THE TACAN HAD ALREADY BEEN OUT FOR 24 HRS AND A NOTAM HAD BEEN ISSUED. WHEN AN AFSS ISSUES A NOTAM THAT A NAVAID IS OTS; THEY CALL THE AFFECTED ATC FACILITIES AND TELL THEM ABOUT THE NOTAM. APPARENTLY WHEN MXF BASOPS ISSUES A MIL NOTAM INTO THE DINS NOTAM SYS; THEY DO NOT HAVE AN EFFECTIVE SIMILAR PROC TO ENSURE THAT ALL OF THE AFFECTED ATC FACILITIES ARE NOTIFIED. WE HAVE NO ONLINE/REAL-TIME METHOD TO KNOW ABOUT ACTIVE NOTAMS. IF THE APPROPRIATE AFSS/ARTCC/BASOPS DOES NOT CALL US AND TELL US ABOUT THEM; WE WILL NOT KNOW. THIS IS A SAFETY ISSUE WHEN WE HAVE TO DIVERT ATTN FROM CTLING AIRPLANES TO SEARCH FOR INFO WE SHOULD ALREADY HAVE. IT COULD BE A BIGGER SAFETY ISSUE IF WE ISSUE AN APCH CLRNC BASED ON A NAVAID THAT IS OTS. ABOUT 30 MINS LATER; ANOTHER ACFT (MIL) REQUESTED THE TACAN APCH AND WAS SURPRISED TO LEARN THAT THE TACAN WAS OTS. THIS ALSO GOES TO SHOW THAT EVEN WHEN A NOTAM IS ISSUED; SOMEHOW THE PLTS ALSO DON'T GET THE WORD; MAKING IT EVEN MORE IMPORTANT THAT WE KNOW ABOUT IT.
Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.