Narrative:

GA aircraft; descending to meet a restr with next sector; slow descent; was told to expedite down. Air carrier Y jet on vector to get lower and to sequence for spacing into cincinnati; oh. Radar controller issued an expedited descent to air carrier Y to FL280 from FL310 with unsafe distance between it and the GA aircraft. My belief is work habits of controller are weak and full of cumbersome data entries such as highlighting blocks of aircraft on frequency; using track ball when traffic is too busy to allow for data entry/highlighting; and unclr intentions of traffic order set. Also; frequency management could be better so blocked xmissions are reduced.

Google
 

Original NASA ASRS Text

Title: ZID ASSOC CTLR DESCRIBED CONFLICT AT FL290.

Narrative: GA ACFT; DSNDING TO MEET A RESTR WITH NEXT SECTOR; SLOW DSCNT; WAS TOLD TO EXPEDITE DOWN. ACR Y JET ON VECTOR TO GET LOWER AND TO SEQUENCE FOR SPACING INTO CINCINNATI; OH. RADAR CTLR ISSUED AN EXPEDITED DSCNT TO ACR Y TO FL280 FROM FL310 WITH UNSAFE DISTANCE BTWN IT AND THE GA ACFT. MY BELIEF IS WORK HABITS OF CTLR ARE WEAK AND FULL OF CUMBERSOME DATA ENTRIES SUCH AS HIGHLIGHTING BLOCKS OF ACFT ON FREQ; USING TRACK BALL WHEN TFC IS TOO BUSY TO ALLOW FOR DATA ENTRY/HIGHLIGHTING; AND UNCLR INTENTIONS OF TFC ORDER SET. ALSO; FREQ MGMNT COULD BE BETTER SO BLOCKED XMISSIONS ARE REDUCED.

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