This is an excerpt from a report made to the Aviation Safety Reporting System. The narrative is written by the pilot, rather than FAA or NTSB officials. To maintain anonymity, many details, such as aircraft model or airport, are often scrubbed from the reports.
I received my IFR clearance and just obtained my taxi instructions from Ground at Syracuse Hancock International Airport (KSYR) in New York to taxi to Runway 15 via A – B – M from the FBO.
I had already done a run-up in the very large asphalt space just to the southwest of the aircraft parking, but still on the ramp. Upon read back of the taxi clearance, I proceeded straight ahead to what I though was to lead to Taxiway A.
Once on the roadway, I realized things were not right. At that point, I received a call from Ground telling me I was on a service road. The service road was not on the FAA airport diagram, and I saw no signs indicating it was a service road where I entered it.
I requested directions from Ground to get to Taxiway A and the ground controller was very helpful in getting me onto Taxiway A headed to Taxiway B.
Being on the eastern side of the large, paved area extension of the FBO, I did not see the exit to Taxiway A on the far right of my position and saw no signs indicating the way was a service road.
Looking at the airport chart, I should have realized that Taxiway A started at the southwest edge of the large, paved area departing the FBO. I was thinking that the roadway I took would lead to Taxiway A.
My mistake.
Primary Problem: Environment-Non Weather Related
ACN: 2091904
I bet that has happened many times at that airport.
If pilot was instrument rated, how did pilot not recognize the absence of taxiway or runway edge color or center lines? As a former FAA Check Airman – there’s got to be more to the story.
To his credit, he fessed up and I hope filed a NASA ASSRS. Even airliners have made errors.
Runway, taxiway, service road… All flat… All good.
ATC: “November, zero, zero, zero, zero, Alpha, cleared for take off service road, expedite take off…traffic…garbage truck ready to roll…good night.”
I did the same thing after landing at KVCV. I cleared the rwy at what I thought was a taxiway.
The service road which intersected the rwy at the same place as the taxiway was not shown on the airport diagram.
Fortunately no vehicles traveling toward him on the service road on an urgent call. Basically a non-event under the circumstances. I’m sure he made a note to himself to look for a solid yellow line (middle of the taxiway) rather than a dashed white line (middle of the service road) in the future.
Maybe, if traffic had been using the service road at the time, pilot would have identified the exit as that if a service road?
Not all airports have standard markings.
It seems to me that the pilot did not have an airport diagram, since taxiway ‘A’ runs along the length of that ramp area.
My no cost GPS AvareX software shows an airport diagram.
Also, a google image of the ramp clearly shows a huge red painted bar, indicating it is a non movement area.!!
This guy did not have all the information for a safe flight, or taxiing.!!
The ground controller was very kind to this guy.!!
Did you know that airport information is updated and previously may not have shown certain features.
The basis of your argument is the information you have now was current then. Bad assumption, friend.
Even if there was no ‘red’ bar across the access road, the yellow taxi lines on the ramp clearly lead to taxiway ‘A’
[ friend].
Great example of a “no panic…no problem” solution to an easy-to-make error…even though that service road should’ve looked too skinny to be a taxiway.
Another scenario where “Busy Taxi” technology, along with the old school airfield diagram, would’ve likely made a difference.
I’ll bet Syracuse Ground had a chuckle after they helped straighten things out.
Better to have a plane mistake a service road for a taxiway, than have a vehicle mistake a taxiway for a service road.