Runway incursion at gon, ct, causing a go around.

Attributes
ACN	491520
Time
Date	200011
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : gon.airport
State Reference	CT
Altitude	agl single value : 0
Environment
Weather Elements	other
Light	Night
Aircraft 1
Controlling Facilities	tower : gon.tower
Operator	general aviation : personal
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Aircraft 2
Controlling Facilities	tower : gon.tower
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing : go around
Route In Use	approach other
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 39 flight time total : 725 flight time type : 600
ASRS Report	491520
Person 2
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : airborne less severe incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : executed go around
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 2000 vertical : 500
Supplementary
Problem Areas	Airport Environmental Factor Flight Crew Human Performance
Primary Problem	Airport
Air Traffic Incident	Pilot Deviation
Situations
Airport	markings : gon.airport taxiway surface condition : gon.airport

Narrative:

After clearance from ground, I was taxiing to runway 23. It was very dark with a touch of ground mist. The lines were hard to see. As I approached the area where taxiway D and taxiway C split, it looked like the taxiway was to the right of the blue taxi lights, so I passed the correct taxiway and passed over the threshold marker that I could not see. As soon as I saw the runway lights, I knew I had made a mistake and immediately did a 180 degree turn. My nosewheel and wing may have actually been over the edge of the runway. The tower controller saw me doing the 180 degree turn and waved off a cessna on final. The tower requested that I call them. The tower controller told me by phone that the lines are scheduled to be repainted and that they will be rising reflective paint. That should solve this problem in the future. The txwys are confusing enough without compounding the problem with faded paint.

Original NASA ASRS Text

Title: RWY INCURSION AT GON, CT, CAUSING A GAR.

Narrative: AFTER CLRNC FROM GND, I WAS TAXIING TO RWY 23. IT WAS VERY DARK WITH A TOUCH OF GND MIST. THE LINES WERE HARD TO SEE. AS I APCHED THE AREA WHERE TXWY D AND TXWY C SPLIT, IT LOOKED LIKE THE TXWY WAS TO THE R OF THE BLUE TAXI LIGHTS, SO I PASSED THE CORRECT TXWY AND PASSED OVER THE THRESHOLD MARKER THAT I COULD NOT SEE. AS SOON AS I SAW THE RWY LIGHTS, I KNEW I HAD MADE A MISTAKE AND IMMEDIATELY DID A 180 DEG TURN. MY NOSEWHEEL AND WING MAY HAVE ACTUALLY BEEN OVER THE EDGE OF THE RWY. THE TWR CTLR SAW ME DOING THE 180 DEG TURN AND WAVED OFF A CESSNA ON FINAL. THE TWR REQUESTED THAT I CALL THEM. THE TWR CTLR TOLD ME BY PHONE THAT THE LINES ARE SCHEDULED TO BE REPAINTED AND THAT THEY WILL BE RISING REFLECTIVE PAINT. THAT SHOULD SOLVE THIS PROB IN THE FUTURE. THE TXWYS ARE CONFUSING ENOUGH WITHOUT COMPOUNDING THE PROB WITH FADED PAINT.

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.