Narrative:

Incident #1: it was after work; I was tired; and it was one of those days when I should not have been flying alone; but since I had a CFI buddy along and needed the instrument practice; the safety bases were adequately covered. And I was new to cid; having just moved to the area. I observed the flags flapping in the breeze near the hangar and decided (first error -- assumption that was never confirmed nor challenged) that we'd be using runway 13. Ground cleared us to 'taxi runway 9 via taxiway C;' and that was the entire taxi clearance. I heard that; but was thinking runway 13; and was confused; because taxiway C goes from the runway 27 numbers to the runway 31 numbers; and runway 31 is the same pavement as runway 13; so I went to the runway 31 numbers. Fortunately; I stayed off the runway (lots of knowledge of runway incursions); and afterwards; I was thinking the next day; how could I have gotten so confused? Incident #2: fast forward several weeks; and I was in a friend's airplane giving a BFR. Same parking place; and we were cleared to 'taxi to runway 13 via charlie.' that was the entire clearance. My student; who had been flying from cid for yrs; also got confused and also went to the runway 31 numbers. The major common contributing factor; as I see it; was cid's unique practice of giving partial taxi clrncs. The clrncs as given were not complete taxi clrncs; as are given at all other airports; they are partial clrncs giving just the initial direction of taxi; and the pilot is 'assumed' to figure out the rest of the clearance. And since one end of taxiway C is runway 31/13; the clearance is easily misinterped. In these 2 events; the same mistake was made; and the only apparent common factor was an incomplete taxi clearance issued by ground control. And there are lots of other ASRS reports where 'local customs' have contributed to taxi errors and runway incursions. I hope you folks will give cid tower a call and see what's going on. After my error; I doubt they'd listen to me.

Google
 

Original NASA ASRS Text

Title: SMA EXPERIENCED TAXIING EVENT AT CID ALLEGING LCL ATC TAXI PHRASEOLOGY IS BOTH CONFUSING AND INCOMPLETE.

Narrative: INCIDENT #1: IT WAS AFTER WORK; I WAS TIRED; AND IT WAS ONE OF THOSE DAYS WHEN I SHOULD NOT HAVE BEEN FLYING ALONE; BUT SINCE I HAD A CFI BUDDY ALONG AND NEEDED THE INST PRACTICE; THE SAFETY BASES WERE ADEQUATELY COVERED. AND I WAS NEW TO CID; HAVING JUST MOVED TO THE AREA. I OBSERVED THE FLAGS FLAPPING IN THE BREEZE NEAR THE HANGAR AND DECIDED (FIRST ERROR -- ASSUMPTION THAT WAS NEVER CONFIRMED NOR CHALLENGED) THAT WE'D BE USING RWY 13. GND CLRED US TO 'TAXI RWY 9 VIA TXWY C;' AND THAT WAS THE ENTIRE TAXI CLRNC. I HEARD THAT; BUT WAS THINKING RWY 13; AND WAS CONFUSED; BECAUSE TXWY C GOES FROM THE RWY 27 NUMBERS TO THE RWY 31 NUMBERS; AND RWY 31 IS THE SAME PAVEMENT AS RWY 13; SO I WENT TO THE RWY 31 NUMBERS. FORTUNATELY; I STAYED OFF THE RWY (LOTS OF KNOWLEDGE OF RWY INCURSIONS); AND AFTERWARDS; I WAS THINKING THE NEXT DAY; HOW COULD I HAVE GOTTEN SO CONFUSED? INCIDENT #2: FAST FORWARD SEVERAL WKS; AND I WAS IN A FRIEND'S AIRPLANE GIVING A BFR. SAME PARKING PLACE; AND WE WERE CLRED TO 'TAXI TO RWY 13 VIA CHARLIE.' THAT WAS THE ENTIRE CLRNC. MY STUDENT; WHO HAD BEEN FLYING FROM CID FOR YRS; ALSO GOT CONFUSED AND ALSO WENT TO THE RWY 31 NUMBERS. THE MAJOR COMMON CONTRIBUTING FACTOR; AS I SEE IT; WAS CID'S UNIQUE PRACTICE OF GIVING PARTIAL TAXI CLRNCS. THE CLRNCS AS GIVEN WERE NOT COMPLETE TAXI CLRNCS; AS ARE GIVEN AT ALL OTHER ARPTS; THEY ARE PARTIAL CLRNCS GIVING JUST THE INITIAL DIRECTION OF TAXI; AND THE PLT IS 'ASSUMED' TO FIGURE OUT THE REST OF THE CLRNC. AND SINCE ONE END OF TXWY C IS RWY 31/13; THE CLRNC IS EASILY MISINTERPED. IN THESE 2 EVENTS; THE SAME MISTAKE WAS MADE; AND THE ONLY APPARENT COMMON FACTOR WAS AN INCOMPLETE TAXI CLRNC ISSUED BY GND CTL. AND THERE ARE LOTS OF OTHER ASRS RPTS WHERE 'LCL CUSTOMS' HAVE CONTRIBUTED TO TAXI ERRORS AND RWY INCURSIONS. I HOPE YOU FOLKS WILL GIVE CID TWR A CALL AND SEE WHAT'S GOING ON. AFTER MY ERROR; I DOUBT THEY'D LISTEN TO ME.

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