Rhv controller described a ground conflict event when traffic exiting the runway turned opposite dir...

Attributes
ACN	950698
Time
Date	201105
Local Time Of Day	1201-1800
Place
Locale Reference	RHV.Tower
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Bonanza 33
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Route In Use	None
Flight Plan	VFR
Aircraft 2
Make Model Name	Cessna 152
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Route In Use	None
Flight Plan	VFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Ground Incursion Taxiway

Narrative:

Aircraft Y landed [on runway] 31R; exited at delta; and was taxiing back to 31R via yankee [to] remain in the pattern. Aircraft X landed 31R; exited at charlie; and turned left onto taxiway yankee. [This] resulted in a nose-to-nose situation with aircraft Y. I observed the aircraft turning and ground controller asking local controller about it. Local tried to give ground approval to taxi on yankee (as local owns taxiway yankee) but ground pointed out the opposite direction traffic. The taxiway at that intersection is wide enough that aircraft X was able to turn around and taxi via zulu. This happened due to poor confusing signage and airport markings. Recommend installing new taxiway signs that accurately show airport layout. Signs pointing to parking aren't even visible from the runway exit at charlie. Repaint taxiway leader lines so that aircraft don't mistake charlie for a 'high-speed' runway exit.

Original NASA ASRS Text

Title: RHV Controller described a ground conflict event when traffic exiting the runway turned opposite direction to an aircraft taxiing out for departure; the reporter claiming poor signage/painting contributed to the error.

Narrative: Aircraft Y landed [on Runway] 31R; exited at Delta; and was taxiing back to 31R via Yankee [to] remain in the pattern. Aircraft X landed 31R; exited at Charlie; and turned left onto Taxiway Yankee. [This] resulted in a nose-to-nose situation with aircraft Y. I observed the aircraft turning and Ground Controller asking Local Controller about it. Local tried to give Ground approval to taxi on Yankee (as Local owns Taxiway Yankee) but Ground pointed out the opposite direction traffic. The taxiway at that intersection is wide enough that aircraft X was able to turn around and taxi via Zulu. This happened due to poor confusing signage and airport markings. Recommend installing new taxiway signs that accurately show airport layout. Signs pointing to parking aren't even visible from the runway exit at Charlie. Repaint taxiway leader lines so that aircraft don't mistake Charlie for a 'high-speed' runway exit.

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.

Rhv controller described a ground conflict event when traffic exiting the runway turned opposite direction to an aircraft taxiing out for departure; the reporter claiming poor signage/painting contributed to the error.