 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZFW controller voiced concern regarding a routing anomaly involving the mlc VOR and mlc airport that are separated by approximately 3 miles but sometimes used interchangeably within the NAS clearance system.
| Attributes | |
| ACN | 889951 |
| Time | |
| Date | 201005 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZFW.ARTCC |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Route In Use | SID TEXOMA ONE |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Track / Heading All Types |
Narrative:
Aircraft X was cleared ktki.TEX1.kmlc; the problem is that mlc is not collocated with the mlc VOR. The same issue was identified in previous reports (and corrected) with regard to cll and cll VOR. While the separation here is less than 3 miles; it is still an issue as the pilot verified he read back a clearance different than what NAS was showing. I cleared the flight direct the mlc airport. The pilot read back 'TEX1.mlc direct'; vice 'TEX1.mlc'. It is clear the earlier correction for cll only fixed that issue; and not all the similar issues with our automation. An additional earlier report identified the inability to specify an airport as an enroute fix rather than an identically identified NAVAID that is not co-located. Recommendation; this automation issue needs to be fixed. We are no longer as limited in data storage; so the old excuses are no longer valid.
Original NASA ASRS Text
Title: ZFW Controller voiced concern regarding a routing anomaly involving the MLC VOR and MLC airport that are separated by approximately 3 miles but sometimes used interchangeably within the NAS clearance system.
Narrative: Aircraft X was cleared KTKI.TEX1.KMLC; the problem is that MLC is NOT collocated with the MLC VOR. The same issue was identified in previous reports (and corrected) with regard to CLL and CLL VOR. While the separation here is less than 3 miles; it is still an issue as the pilot verified he read back a clearance different than what NAS was showing. I cleared the flight direct the MLC airport. The pilot read back 'TEX1.MLC direct'; vice 'TEX1.MLC'. It is clear the earlier correction for CLL only fixed that issue; and not all the similar issues with our automation. An additional earlier report identified the inability to specify an airport as an enroute fix rather than an identically identified NAVAID that is not co-located. Recommendation; this automation issue needs to be fixed. We are no longer as limited in data storage; so the old excuses are no longer valid.
Data retrieved from NASA's ASRS site as of April 2012 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.