Narrative:

Chain of events:I called olympia ground control and requested a departure and progressive taxi instructions to the departure runway. The controller told me to taxi straight out on foxtrot and turn right on echo; then taxi down to the runup area and contact him on the tower frequency when ready for departure on runway 17. They had other traffic. I acknowledged the instructions and taxied from the FBO to the first taxi intersection; which had signage for runways 35-17. It did not; however; have signage for taxiway echo. The next intersection ahead was another taxiway; which was also unlabeled. The small diagram in the AFD did not label the taxiways. I called the controller and asked if my current intersection was taxiway echo. He simply repeated his previous instructions; without identifying which taxiway I was stopped at. I taxied ahead to the next intersection and turned right. The controller promptly informed me I was on taxiway charlie; not echo. He then told me to taxi straight ahead to the hold short line for runway 17; which I did. I was somewhat flustered from being on the wrong taxiway and he told me again to hold short for traffic on 17. I already was. He told me I had to read back the hold short instructions; which I should have done when I first stopped at the hold short line. I read back the hold short instructions. I did my runup while the controller worked the incoming traffic on 17. I then requested departure. He asked [to] where; then corrected himself as having already cleared me for my destination. I was cleared for departure and takeoff was uneventful.human factors:after arriving home; I reviewed the confusion and found a larger diagram in the back of the AFD for olympia; which had the taxiways clearly labeled. I should have looked more carefully for a larger diagram prior to calling the controller. The controller was busy with a departing helicopter and one or two incoming airplanes. Rather than simply ignoring my request for progressive taxi instructions; I think he should have simply told me he was busy with other traffic and requested that I wait for arriving traffic; so he could give me progressive instructions. Adding a taxiway identifier to the runway 35-17 sign would have cleared up my confusion; especially when another parallel taxiway was so close and easily mistaken. At least one of the parallel taxiways should have been identified; especially for visitor traffic from the FBO. What I expected to have happen when I stopped at the first taxi intersection was for the controller to verify that I was at taxiway echo and advise me to turn right; per his initial instructions. I do not understand why progressive taxi instructions were not delivered.

Google
 

Original NASA ASRS Text

Title: A pilot exited an FBO on Taxiway F with instructions to taxi via Taxiway E; but missed E because there was no taxiway signage prior to crossing E on F.

Narrative: Chain of Events:I called Olympia Ground Control and requested a departure and progressive taxi instructions to the departure runway. The Controller told me to taxi straight out on Foxtrot and turn right on Echo; then taxi down to the runup area and contact him on the Tower frequency when ready for departure on Runway 17. They had other traffic. I acknowledged the instructions and taxied from the FBO to the first taxi intersection; which had signage for Runways 35-17. It did not; however; have signage for Taxiway Echo. The next intersection ahead was another taxiway; which was also unlabeled. The small diagram in the AFD did not label the taxiways. I called the Controller and asked if my current intersection was Taxiway Echo. He simply repeated his previous instructions; without identifying which taxiway I was stopped at. I taxied ahead to the next intersection and turned right. The Controller promptly informed me I was on Taxiway Charlie; not Echo. He then told me to taxi straight ahead to the hold short line for Runway 17; which I did. I was somewhat flustered from being on the wrong taxiway and he told me again to hold short for traffic on 17. I already was. He told me I had to read back the hold short instructions; which I should have done when I first stopped at the hold short line. I read back the hold short instructions. I did my runup while the Controller worked the incoming traffic on 17. I then requested departure. He asked [to] where; then corrected himself as having already cleared me for my destination. I was cleared for departure and takeoff was uneventful.Human Factors:After arriving home; I reviewed the confusion and found a larger diagram in the back of the AFD for Olympia; which had the Taxiways clearly labeled. I should have looked more carefully for a larger diagram prior to calling the Controller. The Controller was busy with a departing helicopter and one or two incoming airplanes. Rather than simply ignoring my request for progressive taxi instructions; I think he should have simply told me he was busy with other traffic and requested that I wait for arriving traffic; so he could give me progressive instructions. Adding a taxiway identifier to the Runway 35-17 sign would have cleared up my confusion; especially when another parallel taxiway was so close and easily mistaken. At least one of the parallel taxiways should have been identified; especially for visitor traffic from the FBO. What I expected to have happen when I stopped at the first taxi intersection was for the Controller to verify that I was at Taxiway Echo and advise me to turn right; per his initial instructions. I do not understand why progressive taxi instructions were not delivered.

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