ZAB CTLR ISSUES IMMEDIATE DSCNT WHEN REALIZING CONFLICT BTWN CLBING A320 AND OPPOSITE DIRECTION MD80.

1999-07 · NASA ASRS report 443041

Date: 1999-07 · Aircraft: A320 · Phase: cruise

Anomalies: conflict-airborne-conflict|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-weather-turbulence

Synopsis

ZAB CTLR ISSUES IMMEDIATE DSCNT WHEN REALIZING CONFLICT BTWN CLBING A320 AND OPPOSITE DIRECTION MD80.

Narrative

PHOENIX DEP CTL HAD TURNED US ONTO A 070 DEG HDG AND A CLB TO 15000 FT SHORTLY AFTER DEP. AT APPROX 12500 FT PHX DEP INSTRUCTED US TO CONTACT ZAB ON 132.9. ZAB INSTRUCTED US TO CLB TO FL330. I REPEATED BACK OUR CLRNC TO FL330 AND THAT WE WOULD NEED TO FLY ABOUT A 040 DEG FOR WX AHEAD. ZAB TOLD US THAT WE WERE CLRED AS REQUESTED AND THAT WE COULD GO DIRECT LVS WHEN ABLE. I REPEATED OUR CLRNC BACK 'CLRED TO LVS WHEN ABLE; CLBING TO FL330.' CLBING THROUGH 16000 FT ZAB INSTRUCTED US FOR OUR BEST RATE OF CLB THROUGH FL210. WE COMPLIED WITH ABQ REQUEST. AFTER PASSING FL210 WE RETURNED TO OUR NORMAL CLB PROFILE; YET AT OUR HVY WT AND HIGH TAT (TOTAL AIR TEMP) WE WERE CLBING VERY SLOWLY. AT APPROX FL295 ZAB WAS BLOCKED ON A XMISSION; ALL WE HEARD WAS 'DSND NOW.' SOMEONE KEYED IN AND SAID 'BLOCKED.' ZAB THEN SAID; 'XXX DSND NOW TO FL290; NOW.' CAPT DISCONNECTED THE AUTOPLT AND WE DSNDED TO FL290. A FEW SECONDS LATER ABQ ASKED US WHAT OUR ALT WAS; WE REPLIED FL290. HE RPTED MD80 TFC 12 O'CLOCK POS; FL310. WE THEN SAW AN MD80 PASS BY. ZAB THEN SAID HE WAS SORRY ABOUT THAT TO THE MD80 CREW. I KEYED IN AND SAID THAT WE HAD BEEN CLRED TO FL330. ABQ STATED THAT THEY WOULD PLAY THE TAPES BACK AND LET OUR COMPANY KNOW. WHAT I THINK HAPPENED IN THIS EVENT IS THAT ZAB ON 132.9 WAS DEALING WITH A LOT OF WX IN HIS SECTOR AND WHEN WE GOT OUR INITIAL CLRNC TO FL330 HE HAD THOUGHT WE WOULD GET TO OUR ALT QUICKER THAN WE DID. I THINK HE WAS OVERLOADED WITH THE WX AND FORGOT THAT HE HAD CLRED US TO FL330 AND NOT FL290. I DON'T KNOW IF 5 MI AND 2000 FT SEPARATION WAS LOST. SUPPLEMENTAL INFO FROM ACN 443111: THE FO HAD A DISCUSSION WITH CTLR OF HEADING TO FLY TO AVOID WX; NE OF PHX. WE AGREED ON A 040 DEG HDG. WE WERE QUITE HVY AND AT CLBING SLOWLY. APPROX FL295; ZAB INSTRUCTED US TO IMMEDIATELY RETURN TO FL290. I DISCONNECTED THE AUTOPLT AND RETURNED TO FL290. WE SAW THE MD80 FLY OVER US AT FL310.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.