Small aircraft pilot unable to locate taxiway sign crosses hold line but stops prior to runway.

Attributes
ACN	255030
Time
Date	199310
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lns
State Reference	PA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	ground other : taxi
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 4 flight time total : 428 flight time type : 171
ASRS Report	255030
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Airport	other physical facility

Narrative:

After landing at lns in my small aircraft on runway 26, the ground controller said to turn left on taxiway G, right on D and hold. So, I turned left on G to its end, turned right, looking for taxiway D. At that time, I saw the runway about 150 ft ahead, so I braked to stop. At the same time the controller called and said to stop and that I had crossed the hold line. I saw the line on the runway, but still had not found taxiway D as instructed. The line was 10 or 15 ft behind me, and I was still more than 100 ft from the runway, when I stopped. After about 5 mins, the controller cleared me to the parking area and said to call the tower after tiedown. At that time, the controller said he was going to send this to the FSDO as a violation of the hold point. The problem arose because I was unable to follow the controller's instructions as given, there being no taxiway D marking at the 'G' to 'D' intersection. A contributing factor was the unusually long distance from the hold line to the runway (I didn't think I could have been at the hold point yet). Corrective action should be a marker on taxiway 'D' at 'G' to 'D' intersection. Also, there should be a spirit of cooperation for the very serious business of aviation safety between controllers and pilots. This is not the case at this airport. As pilot of the aircraft involved, I was very concerned about my and other's safety after this incident, and went to a training instructor and got a thorough chkout on ground operations at lns. I have also presently been training in the second phase of the wings program for aviation safety at this time. Callback conversation with reporter revealed the following information: reporter states there has been no FAA follow up at this time. He did mention lack of signage to tower with not much response. Mentioned hold line poorly visible as well. Speaking with local pilots and instructors he contacted, there seems to be a pattern of ATC personnel over-assertiveness regarding hold points at this airport. Reporter never even came close to entering the runway. Reporter feels there should be cooperation, not aggression between pilots and ATC. He is very safety oriented.

Original NASA ASRS Text

Title: SMA PLT UNABLE TO LOCATE TXWY SIGN CROSSES HOLD LINE BUT STOPS PRIOR TO RWY.

Narrative: AFTER LNDG AT LNS IN MY SMA ON RWY 26, THE GND CTLR SAID TO TURN L ON TXWY G, R ON D AND HOLD. SO, I TURNED L ON G TO ITS END, TURNED R, LOOKING FOR TXWY D. AT THAT TIME, I SAW THE RWY ABOUT 150 FT AHEAD, SO I BRAKED TO STOP. AT THE SAME TIME THE CTLR CALLED AND SAID TO STOP AND THAT I HAD CROSSED THE HOLD LINE. I SAW THE LINE ON THE RWY, BUT STILL HAD NOT FOUND TXWY D AS INSTRUCTED. THE LINE WAS 10 OR 15 FT BEHIND ME, AND I WAS STILL MORE THAN 100 FT FROM THE RWY, WHEN I STOPPED. AFTER ABOUT 5 MINS, THE CTLR CLRED ME TO THE PARKING AREA AND SAID TO CALL THE TWR AFTER TIEDOWN. AT THAT TIME, THE CTLR SAID HE WAS GOING TO SEND THIS TO THE FSDO AS A VIOLATION OF THE HOLD POINT. THE PROB AROSE BECAUSE I WAS UNABLE TO FOLLOW THE CTLR'S INSTRUCTIONS AS GIVEN, THERE BEING NO TXWY D MARKING AT THE 'G' TO 'D' INTXN. A CONTRIBUTING FACTOR WAS THE UNUSUALLY LONG DISTANCE FROM THE HOLD LINE TO THE RWY (I DIDN'T THINK I COULD HAVE BEEN AT THE HOLD POINT YET). CORRECTIVE ACTION SHOULD BE A MARKER ON TXWY 'D' AT 'G' TO 'D' INTXN. ALSO, THERE SHOULD BE A SPIRIT OF COOPERATION FOR THE VERY SERIOUS BUSINESS OF AVIATION SAFETY BTWN CTLRS AND PLTS. THIS IS NOT THE CASE AT THIS ARPT. AS PLT OF THE ACFT INVOLVED, I WAS VERY CONCERNED ABOUT MY AND OTHER'S SAFETY AFTER THIS INCIDENT, AND WENT TO A TRAINING INSTRUCTOR AND GOT A THOROUGH CHKOUT ON GND OPS AT LNS. I HAVE ALSO PRESENTLY BEEN TRAINING IN THE SECOND PHASE OF THE WINGS PROGRAM FOR AVIATION SAFETY AT THIS TIME. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THERE HAS BEEN NO FAA FOLLOW UP AT THIS TIME. HE DID MENTION LACK OF SIGNAGE TO TWR WITH NOT MUCH RESPONSE. MENTIONED HOLD LINE POORLY VISIBLE AS WELL. SPEAKING WITH LCL PLTS AND INSTRUCTORS HE CONTACTED, THERE SEEMS TO BE A PATTERN OF ATC PERSONNEL OVER-ASSERTIVENESS REGARDING HOLD POINTS AT THIS ARPT. RPTR NEVER EVEN CAME CLOSE TO ENTERING THE RWY. RPTR FEELS THERE SHOULD BE COOPERATION, NOT AGGRESSION BTWN PLTS AND ATC. HE IS VERY SAFETY ORIENTED.

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