 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A321 flight crew experiences a TCAS RA at 4;500 feet over ffz during a visual approach to runway 26 at phx. The RA commands a climb that leads to a go-around. The intruding aircraft is never sighted by the crew.
| Attributes | |
| ACN | 1276652 |
| Time | |
| Date | 201507 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PHX.Airport |
| State Reference | AZ |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | A321 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach STAR EAGUL6 |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Commercial |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Commercial |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
We were on the EAGUL6 arrival into phx. After approach control asked if we had the airport in sight; we said we did. I was pilot flying. We were given a heading to intercept the localizer for runway 26 in phx; and cleared for the approach. We were in a descent and at approximately 4100 ft; we got a TCAS RA; climb; climb. I immediately followed the RA command and climbed. There was a solid red box showing aircraft below us was approximately 400 ft below us. The first officer advised phx tower we were responding to a TCAS RA command and will not be able to continue the approach. Tower vectored around for another approach; and an uneventful landing a second time around.after landing the first officer and I called phx TRACON; to find out why we did not get any traffic advisory from approach or tower about the aircraft that seemed to have been over ffz. The TRACON supervisor informed us that their radar initially picked up the aircraft in question's [transponder] on radar; but it then disappeared. He stated that the aircraft popped up again just before we got the RA command and disappeared again from their radar shortly afterwards. The aircraft was not in contact with any ATC facility. The first officer and I were startled by this and gave our contact information to the TRACON supervisor to give us any update they obtained about the aircraft as it seemed the aircraft was flying erratically and unsafely along the approach path of phx airport.as ffz is close to the approach path of the phx runway 26 approach; maintaining the recommended altitude as we transition from the arrival to runway 26 approach is very vital. However; even while above the recommended altitude; more vigilance is necessary as certain VFR traffic that are not in contact with ATC facility might still constitute a flight safety hazard as it did with our flight.the best suggestion is vigilance and awareness by flight crews; and improved traffic alerts by ATC of any traffic conflict that might occur. Having TCAS and following RA commands is also essential.
Original NASA ASRS Text
Title: A321 flight crew experiences a TCAS RA at 4;500 feet over FFZ during a visual approach to Runway 26 at PHX. The RA commands a climb that leads to a go-around. The intruding aircraft is never sighted by the crew.
Narrative: We were on the EAGUL6 Arrival into PHX. After approach control asked if we had the airport in sight; we said we did. I was pilot flying. We were given a heading to intercept the localizer for RWY 26 in PHX; and cleared for the approach. We were in a descent and at approximately 4100 FT; we got a TCAS RA; climb; climb. I immediately followed the RA command and climbed. There was a solid red box showing aircraft below us was approximately 400 FT below us. The First Officer advised PHX tower we were responding to a TCAS RA command and will not be able to continue the approach. Tower vectored around for another approach; and an uneventful landing a second time around.After landing the First Officer and I called PHX TRACON; to find out why we did not get any traffic advisory from approach or tower about the aircraft that seemed to have been over FFZ. The TRACON supervisor informed us that their radar initially picked up the aircraft in question's [transponder] on radar; but it then disappeared. He stated that the aircraft popped up again just before we got the RA command and disappeared again from their radar shortly afterwards. The aircraft was not in contact with any ATC facility. The First Officer and I were startled by this and gave our contact information to the TRACON supervisor to give us any update they obtained about the aircraft as it seemed the aircraft was flying erratically and unsafely along the approach path of PHX airport.As FFZ is close to the approach path of the PHX RWY 26 approach; maintaining the recommended altitude as we transition from the arrival to RWY 26 approach is very vital. However; even while above the recommended altitude; more vigilance is necessary as certain VFR traffic that are not in contact with ATC facility might still constitute a flight safety hazard as it did with our flight.The best suggestion is vigilance and awareness by flight crews; and improved traffic alerts by ATC of any traffic conflict that might occur. Having TCAS and following RA commands is also essential.
Data retrieved from NASA's ASRS site 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.