Fcm tower controller reported while aircraft on takeoff roll; aircraft on back taxi utilizing crossi...

Narrative:

While aircraft number 2 was on takeoff roll from runway 36 and nearing the intersection of runway 10L; aircraft number 1 was back taxiing on runway 10L. [Runway] 36 was the primary runway in use and ground had control of runways 10L/right. No coordination to cross runway 36 had taken place. The speed of the taxiing aircraft indicated it did not intend to hold short of runway 36. Ground instructed the taxiing aircraft to stop. The speed of the departing aircraft would not have allowed it to abort. Aircraft number 2 became airborne just prior to the intersection of 10L and; about the same time; aircraft number 1 stopped but I am unsure whether the aircraft crossed the hold short point.the placement of the control tower makes it difficult to tell where hold short markings are and to recognize when potential runway incursions may be imminent. Using runway 36 as a primary runway is a less common configuration and increases the potential for controller and pilot error. Training to increase pilot awareness during unusual air traffic operations may be beneficial.

Original NASA ASRS Text

Title: FCM Tower Controller reported while aircraft on takeoff roll; aircraft on back taxi utilizing crossing runway; may not have held short of active runway. Tower cannot see the hold short markings.

Narrative: While Aircraft Number 2 was on takeoff roll from Runway 36 and nearing the intersection of Runway 10L; Aircraft Number 1 was back taxiing on Runway 10L. [Runway] 36 was the primary runway in use and Ground had control of Runways 10L/R. No coordination to cross Runway 36 had taken place. The speed of the taxiing aircraft indicated it did not intend to hold short of Runway 36. Ground instructed the taxiing aircraft to stop. The speed of the departing aircraft would not have allowed it to abort. Aircraft Number 2 became airborne just prior to the intersection of 10L and; about the same time; Aircraft Number 1 stopped but I am unsure whether the aircraft crossed the hold short point.The placement of the Control Tower makes it difficult to tell where hold short markings are and to recognize when potential runway incursions may be imminent. Using Runway 36 as a primary runway is a less common configuration and increases the potential for controller and pilot error. Training to increase pilot awareness during unusual air traffic operations may be beneficial.

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.

Attributes
ACN	1539836
Time
Date	201805
Local Time Of Day	1801-2400
Place
Locale Reference	FCM.Tower
State Reference	MN
Environment
Light	Night
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Flight Phase	Taxi
Flight Plan	VFR
Aircraft 2
Make Model Name	Skyhawk 172/Cutlass 172
Flight Phase	Takeoff
Flight Plan	VFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Ground Incursion Runway

Fcm tower controller reported while aircraft on takeoff roll; aircraft on back taxi utilizing crossing runway; may not have held short of active runway. Tower cannot see the hold short markings.