Narrative:

I was the l-side at a busy sector. We were working an increased volume of traffic due to WX between pittsburgh and erie, PA. Aircraft were coming broadside into the sector at every altitude in conflict with all our normal traffic flows coming up from the south. In addition we were required to provide 20 mi in trail on the ewr flow, which had doubled with the rertes from the west. At the time of the error several aircraft had been cleared into holding at hpw. Aircraft X was flying ric J14 pxt at FL310, aircraft Y had been descended 3 mins prior from FL330 to FL290, to hold underneath the traffic. Due to other activity in the sector, we failed to see the substandard descent rate of aircraft Y. He descended only 2300 ft in 3 mins. When we saw the converging aircraft, there was 1000-1700 ft left in the aircraft Y descent and they were head-on. Conflict alert activated after we saw the situation, the MD80 got an RA and climbed 300 ft. The B727 took an additional full min to go the last 1000 ft in spite of an expedited request. In my opinion, traffic volume and complexity were partly to blame, as was the extremely slow descent rate of the B727 -- even after an immediate, expedited descent clearance was issued. Vectors were not an option at that point. How could it have been prevented? Better descent by the B727, more awareness on part of radar team, relaxation of 20 mi in trail ewr restr.

Google
 

Original NASA ASRS Text

Title: ARTCC RADAR CTL TEAM ARE MADE AWARE OF CONFLICT BTWN AN MD80 AND B727 BY CONFLICT ALERT FUNCTION. ACTIONS WERE NOT TIMELY OR SUFFICIENT TO STOP THE ERROR.

Narrative: I WAS THE L-SIDE AT A BUSY SECTOR. WE WERE WORKING AN INCREASED VOLUME OF TFC DUE TO WX BTWN PITTSBURGH AND ERIE, PA. ACFT WERE COMING BROADSIDE INTO THE SECTOR AT EVERY ALT IN CONFLICT WITH ALL OUR NORMAL TFC FLOWS COMING UP FROM THE S. IN ADDITION WE WERE REQUIRED TO PROVIDE 20 MI IN TRAIL ON THE EWR FLOW, WHICH HAD DOUBLED WITH THE RERTES FROM THE W. AT THE TIME OF THE ERROR SEVERAL ACFT HAD BEEN CLRED INTO HOLDING AT HPW. ACFT X WAS FLYING RIC J14 PXT AT FL310, ACFT Y HAD BEEN DSNDED 3 MINS PRIOR FROM FL330 TO FL290, TO HOLD UNDERNEATH THE TFC. DUE TO OTHER ACTIVITY IN THE SECTOR, WE FAILED TO SEE THE SUBSTANDARD DSCNT RATE OF ACFT Y. HE DSNDED ONLY 2300 FT IN 3 MINS. WHEN WE SAW THE CONVERGING ACFT, THERE WAS 1000-1700 FT LEFT IN THE ACFT Y DSCNT AND THEY WERE HEAD-ON. CONFLICT ALERT ACTIVATED AFTER WE SAW THE SIT, THE MD80 GOT AN RA AND CLBED 300 FT. THE B727 TOOK AN ADDITIONAL FULL MIN TO GO THE LAST 1000 FT IN SPITE OF AN EXPEDITED REQUEST. IN MY OPINION, TFC VOLUME AND COMPLEXITY WERE PARTLY TO BLAME, AS WAS THE EXTREMELY SLOW DSCNT RATE OF THE B727 -- EVEN AFTER AN IMMEDIATE, EXPEDITED DSCNT CLRNC WAS ISSUED. VECTORS WERE NOT AN OPTION AT THAT POINT. HOW COULD IT HAVE BEEN PREVENTED? BETTER DSCNT BY THE B727, MORE AWARENESS ON PART OF RADAR TEAM, RELAXATION OF 20 MI IN TRAIL EWR RESTR.

Data retrieved from NASA's ASRS site as of July 2007 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.