 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Den controller voiced concern regarding the asde-X equipment noting that beacon changes are not updated to reflect the correct aircraft/flight; adding that changes in the NAS equipment should be reflected in the asde-X logic.
| Attributes | |
| ACN | 1014015 |
| Time | |
| Date | 201206 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | DEN.Airport |
| State Reference | CO |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
A320 taxied out with an associated data block on the asde-X. When I asked clearance delivery for a flight progress strip; I was told that the old flight plan had been removed from the system and a new flight plan had been filed. I checked the asde-X and the A320 was on the old beacon code and not the new code. Had clearance delivery not been aware of the situation I could have taxied the A320 out and the flight would have departed on the old code and clearance in this case; the filed route was the same. I have seen this before; when a proposed flight plan is removed from the NAS; the data is not removed from the asde-X. I believe this is a serious flaw. Last summer I was working local control when a flight departed on an old clearance (different route) and did not discover the problem until the flight was airborne and had to ask the departure controller to fix the problem. When a proposed fp is removed from the NAS; the data should be removed from the asde-X. I can see no reason that this is not the case.
Original NASA ASRS Text
Title: DEN Controller voiced concern regarding the ASDE-X equipment noting that beacon changes are not updated to reflect the correct aircraft/flight; adding that changes in the NAS equipment should be reflected in the ASDE-X logic.
Narrative: A320 taxied out with an associated Data Block on the ASDE-X. When I asked CD for a flight progress strip; I was told that the old flight plan had been removed from the system and a new flight plan had been filed. I checked the ASDE-X and the A320 was on the old beacon code and not the new code. Had CD not been aware of the situation I could have taxied the A320 out and the flight would have departed on the old code and clearance in this case; the filed route was the same. I have seen this before; when a proposed flight plan is removed from the NAS; the data is not removed from the ASDE-X. I believe this is a serious flaw. Last summer I was working LC when a flight departed on an old clearance (different route) and did not discover the problem until the flight was airborne and had to ask the Departure Controller to fix the problem. When a proposed FP is removed from the NAS; the data should be removed from the ASDE-X. I can see no reason that this is not the case.
Data retrieved from NASA's ASRS site as of July 2013 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.