37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 274271 |
Time | |
Date | 199406 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : gqo |
State Reference | TN |
Altitude | msl bound lower : 24000 msl bound upper : 24000 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl |
Operator | other |
Make Model Name | Fighting Falcon F16 |
Operating Under FAR Part | other : other |
Flight Phase | cruise other descent other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 5 |
ASRS Report | 274271 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | Navigational Facility |
Air Traffic Incident | other |
Situations | |
Navigational Aid | Unspecified |
Narrative:
North departure sector in ZTL has had numerous problems with the UHF frequency (370.9). This afternoon a flight of 4 F-16's (X) at FL240 wanted to descend and enter vr-1052. I never heard X check in. I called in the blind 3 times, with no response. I then called in the blind to issue X 11000 ft with no acknowledgment. I then observed the mode C and X begin a descent. I then attempted to switch X to another frequency. Again, there was no acknowledgment. I went and checked with the sector and X had checked in descending to 11000 ft. We have continued to file paperwork on this frequency and there is nothing being done. Callback conversation with reporter revealed the following information: reporter stated that the vr route is north of atl and the UHF frequency is associated with 127.05. UHF frequency is 370.9. Reporter says that numerous ucr's have been filed on this, and some work has been done to isolate the problem. Frequencys have been moved and some work done at the site, but the problem still exists. Reporter indicated that there have been no incidents caused by the frequency problem, however, controller workload and valuable time is needed handle this situation.
Original NASA ASRS Text
Title: ZTL UHF RECEIVER UNRELIABLE. ONGOING PROB.
Narrative: N DEP SECTOR IN ZTL HAS HAD NUMEROUS PROBS WITH THE UHF FREQ (370.9). THIS AFTERNOON A FLT OF 4 F-16'S (X) AT FL240 WANTED TO DSND AND ENTER VR-1052. I NEVER HEARD X CHK IN. I CALLED IN THE BLIND 3 TIMES, WITH NO RESPONSE. I THEN CALLED IN THE BLIND TO ISSUE X 11000 FT WITH NO ACKNOWLEDGMENT. I THEN OBSERVED THE MODE C AND X BEGIN A DSCNT. I THEN ATTEMPTED TO SWITCH X TO ANOTHER FREQ. AGAIN, THERE WAS NO ACKNOWLEDGMENT. I WENT AND CHKED WITH THE SECTOR AND X HAD CHKED IN DSNDING TO 11000 FT. WE HAVE CONTINUED TO FILE PAPERWORK ON THIS FREQ AND THERE IS NOTHING BEING DONE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THE VR RTE IS N OF ATL AND THE UHF FREQ IS ASSOCIATED WITH 127.05. UHF FREQ IS 370.9. RPTR SAYS THAT NUMEROUS UCR'S HAVE BEEN FILED ON THIS, AND SOME WORK HAS BEEN DONE TO ISOLATE THE PROB. FREQS HAVE BEEN MOVED AND SOME WORK DONE AT THE SITE, BUT THE PROB STILL EXISTS. RPTR INDICATED THAT THERE HAVE BEEN NO INCIDENTS CAUSED BY THE FREQ PROB, HOWEVER, CTLR WORKLOAD AND VALUABLE TIME IS NEEDED HANDLE THIS SIT.
Data retrieved from NASA's ASRS site as of July 2007 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.