Beechjet 400
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 4
Workload; Time Pressure; Confusion; Distraction; Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance
Human Factors; Procedure
Working local north; east flow runway 8 in use. Aircraft X called from the northwest for a landing clearance. He was told 'following a Boeing 737 on 2 mile final; runway 8; cleared to land.' Aircraft X read back cleared to land Runway 8. Aircraft Y was the aircraft that Aircraft X was supposed to follow as directed by the approach controller; and by me; the local controller. Aircraft X continued southeast through the final for Runway 8; then turned further south as they passed 500 feet underneath Aircraft Z on final for RWY 7R. I instructed Aircraft X to turn back to the north for Runway 8 and again told him the traffic he was supposed to be following. I also issued traffic to Aircraft X about Aircraft Z just above. Aircraft X said 'traffic in sight;' and I told them to maintain visual separation. I then tried again to get Aircraft X back to the Rwy 8 final with no success. During this time; Aircraft Z received a TCAS RA from Aircraft X and began an RA climb. Once the local south controller could verify Aircraft X was below Aircraft Z; he sent Aircraft Z around on Rwy heading. I could not get Aircraft X to line up for Rwy 8 final; so I coordinated with the finals controller at P50 (phoenix TRACON) for a right turn heading 270; and a climb to 4000 to meet the MVA. The coordination was approved and immediately issued to Aircraft X. Aircraft X executed the turn and climb; and was told to contact approach for re-sequencing.I believe the flight crew on Aircraft X confused Aircraft Z on final for rwy 7R for the traffic they were supposed to follow. I also believe a lack of awareness of position by the flight crew led to this event.Better awareness by flight crews to recognize there position by utilizing all means available on the flight deck.
We were given a 110 vector to final and cleared for a visual approach to runway 8 at PHX behind Aircraft Y. As we turned final behind Aircraft Y the pilot not flying pointed out Aircraft Z slightly higher and close on our right (This aircraft was on final for the parallel runway but we had not seen it and were unaware of its proximity). I leveled the wings and increased the rate of descent (thinking for a moment that this could possibly have been our called traffic and not wanting to get any closer). We then got a resolution alert to adjust vertical speed. The tower call directing us to turn north to re-intercept final; doing so took us back across the (but beneath) the path of the Aircraft Z on final to the parallel. The controller turned us off the approach to the south and back around to land on 7R.We saw Aircraft Z; we should have continued our turn into the runway and queried ATC rather than leveling the wings which seems to have resulted in the RA which took us further from final.
Aircraft pilot and Local Controller reported an aircraft came too close to another aircraft for an adjacent runway and had to be vectored off final.