Minneapolis tower controller reported that an aircraft was cleared for takeoff when an aircraft was ...

Attributes
ACN	1441539
Time
Date	201704
Local Time Of Day	1801-2400
Place
Locale Reference	MSP.TRACON
State Reference	MN
Aircraft 1
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Other Instrument Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 6
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

Aircraft X was an arrival to runway 35 and approaching the arrival departure window (adw). Aircraft Z was holding in position on runway 30L while the previous arrival exited the runway. Aircraft Y was on final to runway 30L. I was training a certified professional controller - in training (cpc-it) on lcs/lcw [local south/local west] when the event occurred. When aircraft Z was cleared for take-off; aircraft X was outside of the runway 35 adw; however by the time they began departure roll aircraft X was inside of the adw. We were unable to wait for aircraft X to exit the adw because of traffic on final to runway 30L. The coordinated spacing for arrivals to the airport does not work; nor does it provide any way or time to predict when a pilot will delay their departure roll; often resulting in an adw violation. We have also been told not to take any action to re-acquire appropriate separation by sending an aircraft around since the error has already occurred. My recommendation would be to suspend converging runway operations (cro) operations at msp until the whole situation can be reevaluated and a better arrival spacing plan worked out.

Original NASA ASRS Text

Title: Minneapolis Tower Controller reported that an aircraft was cleared for takeoff when an aircraft was outside the Arrival Departure Window (ADW). Departing aircraft delayed and arrival entered the ADW and was not sent around.

Narrative: Aircraft X was an arrival to Runway 35 and approaching the Arrival Departure Window (ADW). Aircraft Z was holding in position on Runway 30L while the previous arrival exited the runway. Aircraft Y was on final to Runway 30L. I was training a Certified Professional Controller - In Training (CPC-IT) on LCS/LCW [Local South/Local West] when the event occurred. When Aircraft Z was cleared for take-off; Aircraft X was outside of the Runway 35 ADW; however by the time they began departure roll Aircraft X was inside of the ADW. We were unable to wait for Aircraft X to exit the ADW because of traffic on final to Runway 30L. The coordinated spacing for arrivals to the airport does not work; nor does it provide any way or time to predict when a pilot will delay their departure roll; often resulting in an ADW violation. We have also been told not to take any action to re-acquire appropriate separation by sending an aircraft around since the error has already occurred. My recommendation would be to suspend Converging Runway Operations (CRO) operations at MSP until the whole situation can be reevaluated and a better arrival spacing plan worked out.

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

Minneapolis tower controller reported that an aircraft was cleared for takeoff when an aircraft was outside the arrival departure window (adw). Departing aircraft delayed and arrival entered the adw and was not sent around.