 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOB controller reported problems associated with reading and understanding notams that may or may not be pertinent to the operation.
| Attributes | |
| ACN | 1723178 |
| Time | |
| Date | 202002 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Aircraft 1 | |
| Make Model Name | Citation V/Ultra/Encore (C560) |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Caravan Undifferentiated |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 10 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
There was no separation error or loss of separation. This is [to] report the inefficiency of the new NOTAM procedure where we have to read all notams that are applicable to the approach. As controllers we are not 100% trained to know what the notams mean to the pilots; I had to decipher through 13 notams for 2 different pilots both in a short amount of time; which resulted in me being behind on other items that I feel were a higher priority (i.e. Separating aircraft in the NAS).the work ended up getting done; but the information needs to come to us more streamlined; it is an unreasonable expectation to expect controllers to be able to read all notams to each pilot doing an approach. Especially when we have to read through them and decipher which ones apply and which ones don't.when clicking on an approach in erids (en-route information display system); the notams that are displayed should be the ones pertinent to the approach. For example; when you click the ILS runway 18; it should list all pertinent notams for only that approach; instead of having us find the 3 out of 13 that are pertinent.I feel that the current procedure is a major distraction from the work that the radar controller should be doing; and if they are busy; an important NOTAM may be missed. The information needs to be streamlined and given to us in a foolproof manner.
Original NASA ASRS Text
Title: ZOB Controller reported problems associated with reading and understanding NOTAMs that may or may not be pertinent to the operation.
Narrative: There was no separation error or loss of separation. This is [to] report the inefficiency of the new NOTAM procedure where we have to read all NOTAMs that are applicable to the approach. As Controllers we are not 100% trained to know what the NOTAMs mean to the pilots; I had to decipher through 13 NOTAMs for 2 different pilots both in a short amount of time; which resulted in me being behind on other items that I feel were a higher priority (i.e. separating aircraft in the NAS).The work ended up getting done; but the information needs to come to us more streamlined; it is an unreasonable expectation to expect Controllers to be able to read all NOTAMs to each pilot doing an approach. Especially when we have to read through them and decipher which ones apply and which ones don't.When clicking on an approach in ERIDS (En-Route Information Display System); the NOTAMs that are displayed should be the ones pertinent to the approach. For example; when you click the ILS Runway 18; it should list all pertinent NOTAMs for only that approach; instead of having us find the 3 out of 13 that are pertinent.I feel that the current procedure is a major distraction from the work that the radar controller should be doing; and if they are busy; an important NOTAM may be missed. The information needs to be streamlined and given to us in a foolproof manner.
Data retrieved from NASA's ASRS site 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.