Prc controller described runway incursion event when pilot crossed the hold lines with another aircr...

Narrative:

Aircraft X called me (ground control) after landing runway 21R and exiting at taxiway A1. I instructed the pilot to 'turn right on taxiway C then hold short of runway 21L at C4'. The pilot read back the instructions verbatim. After the aircraft turned onto taxiway 4; the local controller stated 'stop that aircraft.' I instructed aircraft X to 'stop'. The aircraft came to rest midway between the hold line and the edge of runway 21L. At the time aircraft X came to a stop; an small aircraft (small aircraft) was rotating approximately 1000 feet up field. Recommendation; we as controllers are always having to deal with pilots that either don't care about operating within the fars; or don't have enough proficiency to operate safely. We report these types of incidents to our FSDO via pilot deviation reports expecting FSDO to do some thing. Unfortunately; the usual result of these reports are absolutely nothing. The FSDO usually either looks for some reason to blame the controller; or just shrugs the incident off as the pilot error and tells the pilot to not do it again; end of story. The pilots come to the conclusion that we (controllers) are the snitches out to unnecessarily persecute them and depend on the FSDO to jump up to to protect them from us. If you ever wonder why controllers are unwilling to report events; you just heard the answer. It's been this way throughout my career.

Original NASA ASRS Text

Title: PRC Controller described runway incursion event when Pilot crossed the hold lines with another aircraft on takeoff roll; reported alleged pilot errors are not handled appropriately by FSDO.

Narrative: Aircraft X called me (Ground Control) after landing Runway 21R and exiting at Taxiway A1. I instructed the pilot to 'turn right on Taxiway C then hold short of Runway 21L at C4'. The pilot read back the instructions verbatim. After the aircraft turned onto Taxiway 4; the local controller stated 'stop that aircraft.' I instructed Aircraft X to 'stop'. The aircraft came to rest midway between the hold line and the edge of Runway 21L. At the time Aircraft X came to a stop; an SMA (Small Aircraft) was rotating approximately 1000 feet up field. Recommendation; we as controllers are always having to deal with pilots that either don't care about operating within the FARs; or don't have enough proficiency to operate safely. We report these types of incidents to our FSDO via Pilot Deviation reports expecting FSDO to do some thing. Unfortunately; the usual result of these reports are absolutely nothing. The FSDO usually either looks for some reason to blame the Controller; or just shrugs the incident off as the pilot error and tells the Pilot to not do it again; end of story. The Pilots come to the conclusion that we (Controllers) are the snitches out to unnecessarily persecute them and depend on the FSDO to jump up to to protect them from us. If you ever wonder why Controllers are unwilling to report events; you just heard the answer. It's been this way throughout my career.

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	861403
Time
Date	200911
Local Time Of Day	0001-0600
Place
Locale Reference	PRC.Airport
State Reference	AZ
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Flight Phase	Taxi
Person 1
Function	Ground
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway

Prc controller described runway incursion event when pilot crossed the hold lines with another aircraft on takeoff roll; reported alleged pilot errors are not handled appropriately by FSDO.