Narrative:

When aircraft are taxied from the FBO to runway 33, we use taxiway a (7000 ft remaining). This avoids closed txwys and departing over the bak-12. The airport authority/authorized claims that the hold short and taxiway markings are correct, but we have numerous aircraft attempt to continue past the hold short line (ATC either local or ground catches it prior to a runway incursion). Something must not be marked correctly or very well if all types of pilots, GA, air carrier, air transport, and military have tried to continue past the hold short line. My concern is that if the tower is IMC due to low cig's or fog, an aircraft may end up on the runway while in use and ATC won't know. If in fact, the signage is correct, then perhaps some non-standard explicit marking should be added. Callback conversation with reporter revealed the following information: reporter states the bak-12 is the arresting cable crossing the runway. This is an air force base as well as a civilian airport. Most of the markings are the responsibility of the air force but on the civilian side the county management is responsible. They say the marking is correct. Reporter believes that something must be done even if markings are correct because pilots do not seem to stop prior to the runway, they just keep going. Since there is a good deal of fog in the area reporter feels there may come a time when tower does not spot the error and the traffic will enter an active runway. There is also a problem at taxiway 1 where it crosses runway 15, there is no hold line at all. Many times the traffic will cross the runway and end up on the air force side of the runway. There is one other possible problem. The txwys have been given letter designations since there was a great deal of confusion with numbers. Controllers are not given runway/taxiway inspection rides, so reporter does not actually know the markings/signage or how accurate they are. Reporter feels something different must be done to make the hold area clear to all pilots.

Google
 

Original NASA ASRS Text

Title: CTLR RPT REGARDING PROB OF HOLD LINES WHICH GIVE CONFUSING INFO TO PLTS.

Narrative: WHEN ACFT ARE TAXIED FROM THE FBO TO RWY 33, WE USE TXWY A (7000 FT REMAINING). THIS AVOIDS CLOSED TXWYS AND DEPARTING OVER THE BAK-12. THE ARPT AUTH CLAIMS THAT THE HOLD SHORT AND TXWY MARKINGS ARE CORRECT, BUT WE HAVE NUMEROUS ACFT ATTEMPT TO CONTINUE PAST THE HOLD SHORT LINE (ATC EITHER LCL OR GND CATCHES IT PRIOR TO A RWY INCURSION). SOMETHING MUST NOT BE MARKED CORRECTLY OR VERY WELL IF ALL TYPES OF PLTS, GA, ACR, AIR TRANSPORT, AND MIL HAVE TRIED TO CONTINUE PAST THE HOLD SHORT LINE. MY CONCERN IS THAT IF THE TWR IS IMC DUE TO LOW CIG'S OR FOG, AN ACFT MAY END UP ON THE RWY WHILE IN USE AND ATC WON'T KNOW. IF IN FACT, THE SIGNAGE IS CORRECT, THEN PERHAPS SOME NON-STANDARD EXPLICIT MARKING SHOULD BE ADDED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THE BAK-12 IS THE ARRESTING CABLE XING THE RWY. THIS IS AN AIR FORCE BASE AS WELL AS A CIVILIAN ARPT. MOST OF THE MARKINGS ARE THE RESPONSIBILITY OF THE AIR FORCE BUT ON THE CIVILIAN SIDE THE COUNTY MGMNT IS RESPONSIBLE. THEY SAY THE MARKING IS CORRECT. RPTR BELIEVES THAT SOMETHING MUST BE DONE EVEN IF MARKINGS ARE CORRECT BECAUSE PLTS DO NOT SEEM TO STOP PRIOR TO THE RWY, THEY JUST KEEP GOING. SINCE THERE IS A GOOD DEAL OF FOG IN THE AREA RPTR FEELS THERE MAY COME A TIME WHEN TWR DOES NOT SPOT THE ERROR AND THE TFC WILL ENTER AN ACTIVE RWY. THERE IS ALSO A PROB AT TXWY 1 WHERE IT CROSSES RWY 15, THERE IS NO HOLD LINE AT ALL. MANY TIMES THE TFC WILL CROSS THE RWY AND END UP ON THE AIR FORCE SIDE OF THE RWY. THERE IS ONE OTHER POSSIBLE PROB. THE TXWYS HAVE BEEN GIVEN LETTER DESIGNATIONS SINCE THERE WAS A GREAT DEAL OF CONFUSION WITH NUMBERS. CTLRS ARE NOT GIVEN RWY/TXWY INSPECTION RIDES, SO RPTR DOES NOT ACTUALLY KNOW THE MARKINGS/SIGNAGE OR HOW ACCURATE THEY ARE. RPTR FEELS SOMETHING DIFFERENT MUST BE DONE TO MAKE THE HOLD AREA CLR TO ALL PLTS.

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.