ZAU radar and tmu controller described an alleged overload scenario viewed from different perspectiv...

Narrative:

I was at the fwa sector and noticed there were about five or more dtw; (route; vhp fwa MIZAR3) arrivals approaching the logan and looth sectors with no miles in trail due to tma/tbm. I notified the supervisor of the situation. The supervisor went and talked to tmu and possibly ZOB. The logan controller did what needed to be done to comply with tma/tbm. As the first group of arrivals neared fwa the supervisor advised that stacks were not acceptable to ZOB they wanted at least five miles in trail; and to go in the hold; holding commenced. During this process there was a slow moving aircraft at FL250 going direct fwa CRUXX4 yip. There were also two to three departures from north of fwa climbing into fwa sectors airspace. In the face of this wave of arrivals we were supposed to stack for tma/tbm. We were lucky to escape without an error. It is unsafe to use a system that puts us in a position that requires us to stack multiple aircraft over fwa; a very busy VOR. The tmu person involved indicated tma/tbm worked like it should. This amount of stacking is unacceptable. Recommendation: meter to fixes on the arrivals in lieu of thresholds.

Original NASA ASRS Text

Title: ZAU RADAR and TMU Controller described an alleged overload scenario viewed from different perspectives; both suggesting new/revised procedures be explored.

Narrative: I was at the FWA Sector and noticed there were about five or more DTW; (route; VHP FWA MIZAR3) arrivals approaching the LOGAN and LOOTH Sectors with no miles in trail due to TMA/TBM. I notified the Supervisor of the situation. The Supervisor went and talked to TMU and possibly ZOB. The LOGAN Controller did what needed to be done to comply with TMA/TBM. As the first group of arrivals neared FWA the Supervisor advised that stacks were not acceptable to ZOB they wanted at least five miles in trail; and to go in the hold; holding commenced. During this process there was a slow moving aircraft at FL250 going direct FWA CRUXX4 YIP. There were also two to three departures from north of FWA climbing into FWA Sectors airspace. In the face of this wave of arrivals we were supposed to stack for TMA/TBM. We were lucky to escape without an error. It is unsafe to use a system that puts us in a position that requires us to stack multiple aircraft over FWA; a very busy VOR. The TMU person involved indicated TMA/TBM worked like it should. This amount of stacking is unacceptable. Recommendation: meter to fixes on the arrivals in lieu of thresholds.

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

Attributes
ACN	920895
Time
Date	201011
Local Time Of Day	1201-1800
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Aircraft 1
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Traffic Management
Events
Anomaly	ATC Issue All Types

ZAU radar and tmu controller described an alleged overload scenario viewed from different perspectives; both suggesting new/revised procedures be explored.