2006-03 · NASA ASRS report 692075
CRJ CAPT RPTS ATC INSTRUCTIONS PLACED ACFT IN CONFLICT WITH ANOTHER ACFT AT 3000 FT; BOTH ACFT LNDG PHX.
WHILE BEING VECTORED ON A L DOWNWIND FOR RWY 25L AT PHX ARPT I NOTICED THAT WE WERE GETTING VECTORED CLOSER THAN NORMAL TO THE RWY AND MENTIONED THIS TO MY FO. APCH CTL THEN GAVE US A SLIGHT TURN TO THE R TO WIDEN US OUT. THE WINDS ALOFT WERE BTWN 20-30 KTS BLOWING OUT OF THE S (BLOWING US TOWARD THE RWY). WE CONTINUED ON THIS HDG UNTIL ATC GAVE US A BASE TURN APPROX 90 DEGS TO THE L. AS SOON AS WE ROLLED OUT ON OUR HDG I SAW THAT WE WERE BEING VECTORED ACROSS FINAL AND I ASKED MY FO TO QUERY ATC. I THEN NOTICED WHAT APPEARED TO BE A HVY ACFT AHEAD OF US COMING HEAD-ON. MY FO ATTEMPTED TO CONTACT ATC BUT HIS XMISSION APPEARED TO HAVE BEEN COVERED BY ANOTHER ACFT OR ATC. I DETERMINED THAT IF WE TURNED L TOWARDS THE ARPT WE WOULD COLLIDE WITH THE ONCOMING ACFT THAT APPEARED TO BE ON A R BASE FOR RWY 26 JUST SLIGHTLY CLOSER TO THE ARPT THAN WE WERE. AS I STARTED A R TURN TO AVOID THE CONFLICT I HEARD ATC WARN THE OTHER ACFT THAT THERE WAS AN RJ IN FRONT AND BELOW THEM AND TOLD THEM TO TURN R. I BELIEVE THAT MY FO WAS FINALLY ABLE TO GET A XMISSION THROUGH OVER THE BUSY FREQ AT THIS TIME. I AM NOT SURE WHAT HE SAID AS THINGS WERE HAPPENING FAST; I WAS TURNING AND AGGRESSIVELY LOOKING FOR TFC AS I WAS VECTORING MYSELF TOWARDS THE APCH CORRIDOR AND OUR TCAS BEGAN TO GIVE US AN RA. I BELIEVE AT THIS TIME ATC ASKED WHY WE DID NOT TURN IN TOWARDS THE ARPT AND MY FO STATED THAT WE WERE ON A HDG. I THEN TRIED TO EXPLAIN THAT WE WERE NOT CLRED FOR THE APCH AND WE HAD TO TURN R ON OUR OWN TO AVOID THE ONCOMING ACFT (I DID THIS BECAUSE WE WERE REQUIRED BY FAR'S TO NOTIFY ATC ASAP WHENEVER WE DEVIATE FROM A CLRNC). AT THIS POINT THE CTLR TOLD US TO BE QUIET; AS HE DIDN'T HAVE TIME TO LISTEN TO OUR EXCUSES. WE WERE GIVEN A CLB FROM 3000 FT TO 4000 FT AND A TURN TO THE R. WE WERE THEN TURNED TO A R BASE AND TOLD TO SLOW. THE CTLR THEN TOLD US WE WERE CLRED FOR THE VISUAL FOR RWY 26. AT THIS POINT WE WERE CLOSE TO XING THE FINAL FOR RWY 26 AND WOULD HAVE TO OVERSHOOT FINAL SLIGHTLY IN ORDER TO TURN IN. THE CTLR HAD NOT SAID 'SWITCH TO RWY 26' SO I ASKED THE CTLR TO VERIFY THAT WE WERE CLRED FOR RWY 26. HE SNAPPED BACK THAT WE WERE CLRED FOR THE VISUAL RWY 26. I COULD NOT BELIEVE THAT THE CTLR THAT HAD JUST VECTORED US HEAD-ON TO ANOTHER ACFT AND WAS CONTINUING TO TALK TO US IN WHAT I PERCEIVED TO BE AN UNPROFESSIONAL MANNER. I TOLD HIM THAT I HAD NEVER WITNESSED SUCH A BAD JOB OF CTLING. HE THEN TOLD US TO COPY DOWN A PHONE NUMBER AND I TOLD HIM THAT WE WERE TOO BUSY (I WAS TRYING TO CONFIGURE THE ACFT FOR LNDG AND SET UP FOR AN APCH TO A RWY WE HAD NOT PLANNED ON LNDG ON); BUT WE WOULD BE HAPPY TO CALL HIM ONCE ON THE GND. AFTER THE ACFT WAS SHUT DOWN AND OUR CHKLISTS WERE COMPLETED I CALLED PHX APCH ON THE TELEPHONE AND ASKED TO SPEAK TO THE SUPVR. MR X IDENTED HIMSELF AS THE SUPVR AND TOLD ME HE WAS ALSO THE CTLR THAT I HAD BEEN TALKING TO IN THE AIR. HE WAS VERY ANGRY AND TOLD ME HE WAS JUST ABOUT TO LISTEN TO THE TAPE OF THE INCIDENT. AS HE LISTENED TO THE TAPE HE TOLD ME WHAT HE HAD THOUGHT HAD HAPPENED AND WHY HE WAS UPSET WITH ME. AFTER HE HEARD THE TAPE AND REALIZED THAT HE HAD TURNED US TOWARDS THE ONCOMING TFC; HE WAS VERY; VERY APOLOGETIC. HE TOLD ME THAT IN HIS 20+ YRS AS AN ATC CTLR; HE HAD NEVER DONE ANYTHING LIKE THIS AND HE WAS IN FACT A PLT HIMSELF. I ALSO APOLOGIZED FOR THE COMMENT I HAD MADE ABOUT HIS CTLING. LOOKING BACK AT THIS INCIDENT; THE ONE THING THAT I WOULD HAVE DONE DIFFERENTLY WOULD HAVE BEEN TO KEEP MY COMMENT TO MYSELF UNTIL I WAS ON THE GND AND TALKING TO HIM PERSON-TO-PERSON. I THEN EXPLAINED TO HIM THAT IT WAS NOT THE MISTAKE HE MADE THAT HAD CAUSED ME TO MAKE THE COMMENT THAT OFFENDED HIM; BUT RATHER WHAT I HAD PERCEIVED TO BE RUDE AND UNPROFESSIONAL COMMENTS DIRECTED AT US DURING THE INCIDENT. HE AGAIN APOLOGIZED AND I DID THE SAME. LOOKING BACK AT THE INCIDENT; I THINK THE CONTRIBUTING FACTORS WERE BEING VECTORED CLOSER TO THE RWY THAN NORMAL ON DOWNWIND; THE WINDS ALOFT BLOWING US TOWARDS FINAL; THE CTLRTHINKING HE HAD CLRED US FOR THE VISUAL WHEN HE HAD NOT; AND THE CTLR'S ACCUSATORY COMMENTS THROUGHOUT THE INCIDENT. THE TONE AND PHRASEOLOGY THAT THE CTLR USED IMMEDIATELY PUT US ON THE DEFENSIVE AND MADE A DIFFICULT SITUATION EVEN MORE DIFFICULT. I HAVE NOT BEEN ABLE TO LISTEN TO THE RECORDING OF THE INCIDENT BUT I HAVE RECOUNTED THE EVENTS AS BEST AS I COULD RECALL.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.