Narrative:

Ground issued a taxi clearance to taxi to runway 10; via runway 16 and alpha. We were parked at the main terminal ramp. Trying to figure out where to exit the ramp; we stopped at the hold short line; of what turned out to be runway 16/34. Runway 4/22 is depicted on the airport diagram as a closed runway; and does not have the runway numbers depicted. We realized this; and before we could ask to use 16/34 to taxi to (closed) runway 4; ATC told us to utilize runway 16 to runway 4 to alpha to hold short runway 10. Based upon various parking conditions and congestion; it would be very easy to depart the ramp area; and mistake runway 16/34 as a parallel taxiway due to its close relative position to the ramp area; and narrow width. The lack of a runway 4/22 on the airport diagram; congested; small ramp; added to the confusion and increase workload. Additionally; this airport does not utilize the enhanced runway hold short markings; and the hold short markings at taxiway a and runway 10 are a bit faded. Additionally; ground control mentioned to us that the AWOS frequency needs to be activated; and sometimes works by keying the microphone 3 times. This isn't listed as a NOTAM; or on the jeppesen chart. Please update company ops notes to include these items. Please recommend that ATC be cognizant of these issues when issuing taxi clearance to our aircraft; and provide an initial progressive taxi; whether requested or not; to ensure that the aircraft make the proper exit at the north end of the terminal ramp to avoid a potential for runway incursion by entering runway 16/34 unintentionally. Issues with the AWOS should be resolved as an issuance of a NOTAM; especially considering that hto is a part-time tower; without radar surveillance.

Google
 

Original NASA ASRS Text

Title: First Officer reports confusion after being cleared by HTO Ground to taxi via Runway 16 and Taxiway A to Runway 10. The crew winds up holding short of Runway 16/34 at Taxiway F.

Narrative: Ground issued a taxi clearance to taxi to Runway 10; via Runway 16 and Alpha. We were parked at the main terminal ramp. Trying to figure out where to exit the ramp; we stopped at the hold short line; of what turned out to be Runway 16/34. Runway 4/22 is depicted on the airport Diagram as a closed runway; and does not have the runway numbers depicted. We realized this; and before we could ask to use 16/34 to taxi to (closed) Runway 4; ATC told us to utilize Runway 16 to Runway 4 to Alpha to hold short Runway 10. Based upon various parking conditions and congestion; it would be very easy to depart the ramp area; and mistake Runway 16/34 as a parallel taxiway due to its close relative position to the ramp area; and narrow width. The lack of a Runway 4/22 on the Airport Diagram; congested; small ramp; added to the confusion and increase workload. Additionally; this airport does not utilize the enhanced runway hold short markings; and the hold short markings at Taxiway A and Runway 10 are a bit faded. Additionally; Ground Control mentioned to us that the AWOS frequency needs to be activated; and sometimes works by keying the microphone 3 times. This isn't listed as a NOTAM; or on the Jeppesen chart. Please update Company Ops Notes to include these items. Please recommend that ATC be cognizant of these issues when issuing taxi clearance to our aircraft; and provide an initial progressive taxi; whether requested or not; to ensure that the aircraft make the proper exit at the North end of the terminal ramp to avoid a potential for runway incursion by entering Runway 16/34 unintentionally. Issues with the AWOS should be resolved as an issuance of a NOTAM; especially considering that HTO is a part-time Tower; without Radar surveillance.

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