Narrative:

MD80 (X) filed mci to ord during busy ord push -- did not fit in overhead stream and was vectored into traffic, B737 (Y), oms to stl. Established procedure calls for mci departures to climb to FL230 on 050 degree heading. ZKC tmu instructed MD80 to be turned north for sequencing, into traffic, and not as coordinated by SOP. To avoid delays, ZKC tmu, will release departures without regard to sector volume and overhead stream -- the increase in complexity is forcing controllers to take risks involving safety to avoid ground delays. This is not an isolated incident -- it involved the violation of established/coordinated procedures, an operational deviation.

Google
 

Original NASA ASRS Text

Title: ZKC CTLR CONCERNED WITH ZKC TMU FAILING TO COMPLY WITH ZKC SATELLITE RELEASE POLICY FOR ENRTE INTEGRATION INTO ORD TFC FLOW.

Narrative: MD80 (X) FILED MCI TO ORD DURING BUSY ORD PUSH -- DID NOT FIT IN OVERHEAD STREAM AND WAS VECTORED INTO TFC, B737 (Y), OMS TO STL. ESTABLISHED PROC CALLS FOR MCI DEPS TO CLB TO FL230 ON 050 DEG HDG. ZKC TMU INSTRUCTED MD80 TO BE TURNED N FOR SEQUENCING, INTO TFC, AND NOT AS COORDINATED BY SOP. TO AVOID DELAYS, ZKC TMU, WILL RELEASE DEPS WITHOUT REGARD TO SECTOR VOLUME AND OVERHEAD STREAM -- THE INCREASE IN COMPLEXITY IS FORCING CTLRS TO TAKE RISKS INVOLVING SAFETY TO AVOID GND DELAYS. THIS IS NOT AN ISOLATED INCIDENT -- IT INVOLVED THE VIOLATION OF ESTABLISHED/COORDINATED PROCS, AN OPDEV.

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.