37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1015809 |
Time | |
Date | 201206 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
I stopped my one aircraft at 040 by cancelling his approach clearance. This was because the controller next to me had an aircraft that was going through his and my final and was conflicting with him. Due to a big tailwind; the trailing aircraft was given a late speed reduction and eventually was broken out to be re-sequenced. I then gave aircraft one an approach clearance once the conflict was resolved. I had the turboprop on a 330 degree heading (on base) to follow aircraft one. I then made a couple transmissions to other aircraft on frequency. I glanced down at the turboprop and the atpa was displaying a red bat pointed at the aircraft I was re-sequencing passing off the turboprop's left. This confused me and I thought I had already turned the turboprop onto final. I realized that he was still on a 330 heading when the ca alerted me. I then took corrective action and the turboprop told me he was responding to his TCAS. A B737 was the aircraft he was responding to. The B737 was on the other final and had the turboprop in sight maintaining visual separation. I think in this situation; atpa was a distraction more than a helpful tool. In the past I have used the 'cones' or 'bats' to show an aircraft's heading. At a glance when the atpa showed the turboprop's proximity to the aircraft passing off his left the 'bat' pointed in a direction towards his 'turn on' heading to final.
Original NASA ASRS Text
Title: Conflict developed between two air carriers conducting parallel approach procedures. The Automated Terminal Proximity Alerts (ATPA) tool introduced a measure of confusion contributing to the event.
Narrative: I stopped my one aircraft at 040 by cancelling his approach clearance. This was because the controller next to me had an aircraft that was going through his and my final and was conflicting with him. Due to a big tailwind; the trailing aircraft was given a late speed reduction and eventually was broken out to be re-sequenced. I then gave aircraft one an approach clearance once the conflict was resolved. I had the turboprop on a 330 degree heading (on base) to follow aircraft one. I then made a couple transmissions to other aircraft on frequency. I glanced down at the turboprop and the ATPA was displaying a red bat pointed at the aircraft I was re-sequencing passing off the turboprop's left. This confused me and I thought I had already turned the turboprop onto final. I realized that he was still on a 330 heading when the CA alerted me. I then took corrective action and the turboprop told me he was responding to his TCAS. A B737 was the aircraft he was responding to. The B737 was on the other final and had the turboprop in sight maintaining visual separation. I think in this situation; ATPA was a distraction more than a helpful tool. In the past I have used the 'cones' or 'bats' to show an aircraft's heading. At a glance when the ATPA showed the turboprop's proximity to the aircraft passing off his left the 'bat' pointed in a direction towards his 'turn on' heading to final.
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.