Landing pilot turns off on runway 10/28 at kcgi after landing on runway 20. He observes the runway s...

Attributes
ACN	530484
Time
Date	200111
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : cgi.airport
State Reference	MO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Golden Eagle 421
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 50 flight time total : 13000 flight time type : 2600
ASRS Report	530484
Person 2
Affiliation	other
Function	controller : local
Events
Anomaly	incursion : runway other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Situations
Airport	signage : cgi.airport

Narrative:

Upon landing on runway 20 at cgi, I rolled out and turned off on what I thought was a taxiway. The controller tells me that I turned off onto an active runway and that it was a violation. I was very puzzled because I had not seen the red marker that alerts you to a crossing runway. I took off on the same runway watching for the marker and discovered that there is another black box (probably a taxiway identifier for the taxiway behind me) that obscured the runway marker until I was right on top of it. This is a dangerous situation that should be remedied if the FAA is serious about stopping runway incursions. Callback conversation with reporter revealed the following information: the reporter said that the airport has standard signs, but they are so closely spaced that the taxiway sign blocks the runway sign. Both signs are on the left side of the runway and in line with each other. He suggests that one of them be place on the other side of the runway.

Original NASA ASRS Text

Title: LNDG PLT TURNS OFF ON RWY 10/28 AT KCGI AFTER LNDG ON RWY 20. HE OBSERVES THE RWY SIGN IS SO CLOSE AND IN LINE WITH THE TXWY SIGN THAT IT IS OBSCURED.

Narrative: UPON LNDG ON RWY 20 AT CGI, I ROLLED OUT AND TURNED OFF ON WHAT I THOUGHT WAS A TXWY. THE CTLR TELLS ME THAT I TURNED OFF ONTO AN ACTIVE RWY AND THAT IT WAS A VIOLATION. I WAS VERY PUZZLED BECAUSE I HAD NOT SEEN THE RED MARKER THAT ALERTS YOU TO A XING RWY. I TOOK OFF ON THE SAME RWY WATCHING FOR THE MARKER AND DISCOVERED THAT THERE IS ANOTHER BLACK BOX (PROBABLY A TXWY IDENTIFIER FOR THE TXWY BEHIND ME) THAT OBSCURED THE RWY MARKER UNTIL I WAS RIGHT ON TOP OF IT. THIS IS A DANGEROUS SIT THAT SHOULD BE REMEDIED IF THE FAA IS SERIOUS ABOUT STOPPING RWY INCURSIONS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR SAID THAT THE ARPT HAS STANDARD SIGNS, BUT THEY ARE SO CLOSELY SPACED THAT THE TXWY SIGN BLOCKS THE RWY SIGN. BOTH SIGNS ARE ON THE LEFT SIDE OF THE RWY AND IN LINE WITH EACH OTHER. HE SUGGESTS THAT ONE OF THEM BE PLACE ON THE OTHER SIDE OF THE RWY.

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.

Landing pilot turns off on runway 10/28 at kcgi after landing on runway 20. He observes the runway sign is so close and in line with the taxiway sign that it is obscured.