37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1373869 |
Time | |
Date | 201607 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | JCF.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
There is a tfr in place today for a fire at or below 8500 feet; 5 NM radius at ZZZ (VOR)110/014. We were not showing this as the tfr location in our status information. We had the previous tfr that had expired in our information. After having worked the sector for an hour; we kept getting reports from socal that the tfr is more in our sky than theirs; and our coordination on arriving aircraft was getting confusing because our maps were not showing the same information. I remembered our controller in charge had said earlier that they didn't want to read all the notams for the watch check list because there were too many. Eventually; I asked socal of the position of the tfr to make sure we have the correct display; and ours was incorrect. I asked our controller in charge to find out if our tfr was correct; and they told me to look it up (despite working traffic at the time). I looked up the NOTAM; and then corrected the drawing for our tfr and input the drawing on all the other scopes as needed; and updated our information area as for the new drawing.I'm not sure if anyone had gone through the tfr before I updated the drawings.I would have the controller in charge's get training on the desk and duties involved; and stress the need to make sure the notams are up to date or corrected. Another alternative is to not have a controller in charge; and have supervisors work the desk. Often times this happens when the controllers work the desk. I've seen other information get misrepresented or overlooked.
Original NASA ASRS Text
Title: Joint Control Facility (Edwards) TRACON Controller reported of a TFR that was not updated and the reporter did not know the exact position. Reporter eventually had to look up coordinates and then advise others.
Narrative: There is a TFR in place today for a fire at or below 8500 feet; 5 NM radius at ZZZ (VOR)110/014. We were not showing this as the TFR location in our Status Information. We had the previous TFR that had expired in our information. After having worked the sector for an hour; we kept getting reports from SoCal that the TFR is more in our sky than theirs; and our coordination on arriving aircraft was getting confusing because our maps were not showing the same information. I remembered our CIC had said earlier that they didn't want to read all the NOTAMs for the watch check list because there were too many. Eventually; I asked SoCal of the position of the TFR to make sure we have the correct display; and ours was incorrect. I asked our CIC to find out if our TFR was correct; and they told me to look it up (despite working traffic at the time). I looked up the NOTAM; and then corrected the drawing for our TFR and input the drawing on all the other scopes as needed; and updated our information area as for the new drawing.I'm not sure if anyone had gone through the TFR before I updated the drawings.I would have the CIC's get training on the desk and duties involved; and stress the need to make sure the NOTAMs are up to date or corrected. Another alternative is to not have a CIC; and have Supervisors work the desk. Often times this happens when the controllers work the desk. I've seen other information get misrepresented or overlooked.
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.