 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An airspace infraction occurred when a data block was accidentally dropped. The reporter noted differing uret practices that likely contributed to the event.
| Attributes | |
| ACN | 966287 |
| Time | |
| Date | 201108 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZMA.ARTCC |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | B757-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Enroute |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I noticed a limited data block at FL380 northwest bound in my airspace and initially thought it was a ring around target from another aircraft northbound over ursus. When I realized it was not ring around I did a flight plan read out on the code and realized it was aircraft X. I then started a track and attempted to call on frequency for the aircraft and he did not acknowledge. I then called sector 60 and 62 to attempt to get the aircraft on our frequency. When aircraft X did call; a couple of minutes later; we had him identify for identification verification. Later asked what was the last frequency aircraft X was on he advised he was on 132 something and he noticed he was out of range and went to 126.27 because he heard the controller on the other frequency sending other aircraft to that frequency and they sent him to 126.32. I was sure we took the hand off and dropped track by mistake. In uret a lot of people use the drop track delete feature. If this was not used the aircraft would remain in uret with the call sign turning brown because the aircraft is not tracked. When drop track delete is selected the aircraft falls out of uret. Also must be aware of limited data blocks in your airspace or close to the boundary.
Original NASA ASRS Text
Title: An airspace infraction occurred when a data block was accidentally dropped. The reporter noted differing URET practices that likely contributed to the event.
Narrative: I noticed a limited data block at FL380 northwest bound in my airspace and initially thought it was a ring around target from another aircraft northbound over URSUS. When I realized it was not ring around I did a flight plan read out on the code and realized it was Aircraft X. I then started a track and attempted to call on frequency for the aircraft and he did not acknowledge. I then called Sector 60 and 62 to attempt to get the aircraft on our frequency. When Aircraft X did call; a couple of minutes later; we had him IDENT for identification verification. Later asked what was the last frequency Aircraft X was on he advised he was on 132 something and he noticed he was out of range and went to 126.27 because he heard the controller on the other frequency sending other aircraft to that frequency and they sent him to 126.32. I was sure we took the hand off and dropped track by mistake. In URET a lot of people use the drop track delete feature. If this was not used the aircraft would remain in URET with the call sign turning brown because the aircraft is not tracked. When drop track delete is selected the aircraft falls out of URET. Also must be aware of limited data blocks in your airspace or close to the boundary.
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.