37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1064013 |
Time | |
Date | 201301 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | P50.TRACON |
State Reference | AZ |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors STAR MAIER |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors STAR EAGUL |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
Air carrier X was a maier arrival; had descended him to 4;000 feet; planning a base turn for a 6-8 NM final. He was number 1 for runway 26 and I had coordinated with verde air carrier Y to fit into my sequence. I subsequently turned air carrier Y eagul arrival toward a 5 NM final for spacing and descended to 6;000 feet. I turned air carrier X to the base leg; however; never got a read back. The air carrier Y eagul reported the airport in sight so I issued the visual approach clearance; expecting to clear air carrier X on the next transmission. However; I noticed air carrier X had not turned; tried to turn him further right with no response. I immediately cancelled the air carrier Y clearance with a maintain 6;000 feet; and a turn to the south. I tried air carrier X again and this time got a response. Wound up turning the air carrier Y back towards the northwest; then to the final. This is the first day we were running 'fused radar' in stars. I believe the unfamiliarity of the movements of the data blocks and history trails contributed to this event. Until I become more accustomed to the quirks of the fusion display; I will go into the finals (base legs; turns and clearances) with a more conservative technique. I have noticed that the ptl lines and the 'baseball bat' cones seem to lag behind more than traditional radar. This may just be an optical illusion.
Original NASA ASRS Text
Title: P50 Controller experienced a developing conflict event listing the unfamiliarity with 'fused RADAR' as a causal factor.
Narrative: Air Carrier X was a MAIER arrival; had descended him to 4;000 feet; planning a base turn for a 6-8 NM final. He was number 1 for Runway 26 and I had coordinated with Verde Air Carrier Y to fit into my sequence. I subsequently turned Air Carrier Y EAGUL arrival toward a 5 NM final for spacing and descended to 6;000 feet. I turned Air Carrier X to the base leg; however; never got a read back. The Air Carrier Y EAGUL reported the airport in sight so I issued the visual approach clearance; expecting to clear Air Carrier X on the next transmission. However; I noticed Air Carrier X had not turned; tried to turn him further right with no response. I immediately cancelled the Air Carrier Y clearance with a maintain 6;000 feet; and a turn to the South. I tried Air Carrier X again and this time got a response. Wound up turning the Air Carrier Y back towards the Northwest; then to the final. This is the first day we were running 'fused RADAR' in STARS. I believe the unfamiliarity of the movements of the data blocks and history trails contributed to this event. Until I become more accustomed to the quirks of the fusion display; I will go into the finals (base legs; turns and clearances) with a more conservative technique. I have noticed that the PTL lines and the 'baseball bat' cones seem to lag behind more than traditional RADAR. This may just be an optical illusion.
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.