Narrative:

Aircraft is a regularly scheduled part 135 operation. The crew called for taxi from the terminal ramp and was cleared to 'taxi to runway 28' which they read back. They then taxied straight out from the terminal ramp crossed the parallel taxiway 'a' and continued onto taxiway 'A3' which is approximately 3100 ft from the end of the runway. The aircraft was not slowing to hold short of the runway. Since I was working both local and ground control and had no traffic using the runway; I advised the pilot he was entering the active runway and cleared him to do so with instructions on how to get back onto the parallel and to the runway. This has apparently happened before as the facility air traffic manager has asked to be notified when it happens.callback conversation with reporter revealed the following information: reporter stated that the flight crew was given clearance to taxi to runway 28 via taxiway 'a.' the readback was correct and the flight crew began to taxi. The reporter stated that he noticed the aircraft on taxiway 'A3' as it entered the active runway and alerted the flight crew of the incursion and directed the flight crew to turn left on runway 10/28; left on runway 3/21 and taxi to taxiway 'a.' there were no conflicts as reporter stated he was working both the local and ground position and it was early in the morning and there was no other traffic. Reporter indicated that a discussion with the facility manager regarding the incident revealed that this happened several times in the past at the same intersection and it was felt that it could be designated a 'hot spot' on the chart. The aircraft had taxied from the west side of the passenger terminal and this may have blocked the flight crew's view of the proper taxi route.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRJ200 FLT CREW HAS A RWY INCURSION AT MGM.

Narrative: ACFT IS A REGULARLY SCHEDULED PART 135 OPERATION. THE CREW CALLED FOR TAXI FROM THE TERMINAL RAMP AND WAS CLEARED TO 'TAXI TO RWY 28' WHICH THEY READ BACK. THEY THEN TAXIED STRAIGHT OUT FROM THE TERMINAL RAMP CROSSED THE PARALLEL TXWY 'A' AND CONTINUED ONTO TXWY 'A3' WHICH IS APPROXIMATELY 3100 FT FROM THE END OF THE RWY. THE ACFT WAS NOT SLOWING TO HOLD SHORT OF THE RWY. SINCE I WAS WORKING BOTH LOCAL AND GROUND CONTROL AND HAD NO TFC USING THE RWY; I ADVISED THE PLT HE WAS ENTERING THE ACTIVE RWY AND CLRED HIM TO DO SO WITH INSTRUCTIONS ON HOW TO GET BACK ONTO THE PARALLEL AND TO THE RWY. THIS HAS APPARENTLY HAPPENED BEFORE AS THE FACILITY AIR TFC MANAGER HAS ASKED TO BE NOTIFIED WHEN IT HAPPENS.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THE FLT CREW WAS GIVEN CLRNC TO TAXI TO RWY 28 VIA TXWY 'A.' THE READBACK WAS CORRECT AND THE FLT CREW BEGAN TO TAXI. THE RPTR STATED THAT HE NOTICED THE ACFT ON TXWY 'A3' AS IT ENTERED THE ACTIVE RWY AND ALERTED THE FLT CREW OF THE INCURSION AND DIRECTED THE FLT CREW TO TURN L ON RWY 10/28; L ON RWY 3/21 AND TAXI TO TXWY 'A.' THERE WERE NO CONFLICTS AS RPTR STATED HE WAS WORKING BOTH THE LCL AND GND POSITION AND IT WAS EARLY IN THE MORNING AND THERE WAS NO OTHER TFC. RPTR INDICATED THAT A DISCUSSION WITH THE FACILITY MGR REGARDING THE INCIDENT REVEALED THAT THIS HAPPENED SEVERAL TIMES IN THE PAST AT THE SAME INTERSECTION AND IT WAS FELT THAT IT COULD BE DESIGNATED A 'HOT SPOT' ON THE CHART. THE ACFT HAD TAXIED FROM THE W SIDE OF THE PAX TERMINAL AND THIS MAY HAVE BLOCKED THE FLT CREW'S VIEW OF THE PROPER TAXI RTE.

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