Narrative:

We were air carrier X established on J152 at FL330, in and out of rainshower cloud tops with in-flight visibility of approximately 5-6 miles. Ny center was very busy and, quite suddenly ordered us to 'expedite to FL310' and an air carrier Y to turn left to a westerly heading 'immediately.' I was talking to company when this was broadcast, when I looked out my side, I saw the air carrier Y in a steep left bank. (We later found out it was 500' and 2 mi at the closest). ATC referred to it as an 'operational error'. The air carrier Y pilot asked if we were where we were supposed to be, center's answer was 'yes' and that he was real busy in another portion of the sector with 2 other conflicts. Suggest suitable watch supervisor to backup active controller during real busy operations.

Google
 

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION BETWEEN TWO ACR. OPERATIONAL ERROR.

Narrative: WE WERE ACR X ESTABLISHED ON J152 AT FL330, IN AND OUT OF RAINSHOWER CLOUD TOPS WITH INFLT VISIBILITY OF APPROX 5-6 MILES. NY CTR WAS VERY BUSY AND, QUITE SUDDENLY ORDERED US TO 'EXPEDITE TO FL310' AND AN ACR Y TO TURN L TO A WESTERLY HDG 'IMMEDIATELY.' I WAS TALKING TO COMPANY WHEN THIS WAS BROADCAST, WHEN I LOOKED OUT MY SIDE, I SAW THE ACR Y IN A STEEP L BANK. (WE LATER FOUND OUT IT WAS 500' AND 2 MI AT THE CLOSEST). ATC REFERRED TO IT AS AN 'OPERATIONAL ERROR'. THE ACR Y PLT ASKED IF WE WERE WHERE WE WERE SUPPOSED TO BE, CENTER'S ANSWER WAS 'YES' AND THAT HE WAS REAL BUSY IN ANOTHER PORTION OF THE SECTOR WITH 2 OTHER CONFLICTS. SUGGEST SUITABLE WATCH SUPVR TO BACKUP ACTIVE CTLR DURING REAL BUSY OPS.

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