Narrative:

During landing roll at mke at a speed of approximately 80 KTS I noticed small transport Y roll across our runway on an intersecting runway also on his landing roll. I recall while we were on short final small transport Y had been instructed to hold short of runway 7R (our runway) and acknowledged this directive. Over a span of 60 seconds the tower operator was working a departing medium large transport air carrier, our air carrier X arrival and small transport Y arrival. In my opinion the controller simply became overloaded. I think too that the small transport pilot may have been of limited experience. I think the ratio of trnee controllers to full performance controllers is way too high. The practice of simultaneous operations on intersecting runways should be abandoned and TCA's should be IFR only. Also, more stringent proficiency checks for GA and business aviation pilots would help, as would requiring any PIC of a turbine pwred aircraft to possess a valid ATP. If all this slows the flow of traffic, so be it--safety first. Callback conversation with reporter revealed the following: discussed the fact that controller could not have legally given the small transport a 'hold short of runway 7R' clearance because the distance from threshold runway 1R to intersection would be much too short for that restriction. Reporter then said he must have heard some other conversation reference holding short, but is pretty sure that his flight was never advised to hold short of runway 1R. Supplemental information from acn 95680: air carrier X was landing runway 7R and small transport Y landing runway 1R. The air carrier was not given hold short instruction and traffic reference runway 1R traffic. Callback conversation with reporter revealed the following: reporter was local controller. Did not give either small transport or air carrier a hold short clearance. He confirms that small transport could not be given hold short of runway 7R because the distance from threshold to intersection is too short. Realized problem when air carrier was about to T/D, but decided it would be better to keep quiet at that point.

Google
 

Original NASA ASRS Text

Title: CRITICAL GND CONFLICT BETWEEN SMT AND ACR-MLG LNDG ON INTERSECTING RWYS. OPERATIONAL ERROR WITH LESS THAN STANDARD SEPARATION.

Narrative: DURING LNDG ROLL AT MKE AT A SPD OF APPROX 80 KTS I NOTICED SMT Y ROLL ACROSS OUR RWY ON AN INTERSECTING RWY ALSO ON HIS LNDG ROLL. I RECALL WHILE WE WERE ON SHORT FINAL SMT Y HAD BEEN INSTRUCTED TO HOLD SHORT OF RWY 7R (OUR RWY) AND ACKNOWLEDGED THIS DIRECTIVE. OVER A SPAN OF 60 SECS THE TWR OPERATOR WAS WORKING A DEPARTING MLG ACR, OUR ACR X ARR AND SMT Y ARR. IN MY OPINION THE CTLR SIMPLY BECAME OVERLOADED. I THINK TOO THAT THE SMT PLT MAY HAVE BEEN OF LIMITED EXPERIENCE. I THINK THE RATIO OF TRNEE CTLRS TO FULL PERFORMANCE CTLRS IS WAY TOO HIGH. THE PRACTICE OF SIMULTANEOUS OPS ON INTERSECTING RWYS SHOULD BE ABANDONED AND TCA'S SHOULD BE IFR ONLY. ALSO, MORE STRINGENT PROFICIENCY CHKS FOR GA AND BUSINESS AVIATION PLTS WOULD HELP, AS WOULD REQUIRING ANY PIC OF A TURBINE PWRED ACFT TO POSSESS A VALID ATP. IF ALL THIS SLOWS THE FLOW OF TFC, SO BE IT--SAFETY FIRST. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: DISCUSSED THE FACT THAT CTLR COULD NOT HAVE LEGALLY GIVEN THE SMT A 'HOLD SHORT OF RWY 7R' CLRNC BECAUSE THE DISTANCE FROM THRESHOLD RWY 1R TO INTXN WOULD BE MUCH TOO SHORT FOR THAT RESTRICTION. RPTR THEN SAID HE MUST HAVE HEARD SOME OTHER CONVERSATION REF HOLDING SHORT, BUT IS PRETTY SURE THAT HIS FLT WAS NEVER ADVISED TO HOLD SHORT OF RWY 1R. SUPPLEMENTAL INFO FROM ACN 95680: ACR X WAS LNDG RWY 7R AND SMT Y LNDG RWY 1R. THE ACR WAS NOT GIVEN HOLD SHORT INSTRUCTION AND TFC REF RWY 1R TFC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR WAS LCL CTLR. DID NOT GIVE EITHER SMT OR ACR A HOLD SHORT CLRNC. HE CONFIRMS THAT SMT COULD NOT BE GIVEN HOLD SHORT OF RWY 7R BECAUSE THE DISTANCE FROM THRESHOLD TO INTXN IS TOO SHORT. REALIZED PROBLEM WHEN ACR WAS ABOUT TO T/D, BUT DECIDED IT WOULD BE BETTER TO KEEP QUIET AT THAT POINT.

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.