37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1427725 |
Time | |
Date | 201702 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | STS.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | VFR |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 40 Flight Crew Total 7000 Flight Crew Type 2700 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown Ground Incursion Runway |
Narrative:
In preparing for takeoff; we had been instructed to taxi to the run up area for runways 14/20. In reviewing the airport chart again; that is also the A3 intersection. I had been told to expect runway 14 for takeoff. The beginning of runway 14 is north of the run up area. The beginning of runway 20 is adjacent to the run up area. Both runways can be accessed from the A3 intersection; but not the full length of runway 14. Taxiing to the beginning of runway 14 takes one across the approach path for runway 20. The signage is confusing. When told to continue my taxi to the hold short line; I missed the A3 intersection and proceeded north to the beginning of the runway. When I realized my error a moment later; I stopped and notified ground control. They told me to continue my taxi to the runway end but advised of a possible pilot deviation and requested I call the tower later.when I spoke to the tower later on the phone; I was told there was no safety issue since there was no traffic for runway 20 and that; 'it was no big deal.' the controller told me that situation happens 2-3 times a day and they're documenting all instances in order to get the FAA to improve the signage. My takeaway is to be extra vigilant in studying the airport chart prior to taxi and have a clear picture of the route given in the instructions.
Original NASA ASRS Text
Title: GA pilot reported incurring STS Runway 20 approach hold area after leaving the run up area. The reporter did not see the hold-short line protecting the Runway 20 approach path because of its distance from the Runway 14 entry taxiway.
Narrative: In preparing for takeoff; we had been instructed to taxi to the run up area for Runways 14/20. In reviewing the airport chart again; that is also the A3 intersection. I had been told to expect Runway 14 for takeoff. The beginning of Runway 14 is north of the run up area. The beginning of Runway 20 is adjacent to the run up area. Both runways can be accessed from the A3 intersection; but not the full length of Runway 14. Taxiing to the beginning of runway 14 takes one across the approach path for runway 20. The signage is confusing. When told to continue my taxi to the hold short line; I missed the A3 intersection and proceeded north to the beginning of the runway. When I realized my error a moment later; I stopped and notified ground control. They told me to continue my taxi to the runway end but advised of a possible pilot deviation and requested I call the tower later.When I spoke to the tower later on the phone; I was told there was no safety issue since there was no traffic for Runway 20 and that; 'it was no big deal.' The controller told me that situation happens 2-3 times a day and they're documenting all instances in order to get the FAA to improve the signage. My takeaway is to be extra vigilant in studying the airport chart prior to taxi and have a clear picture of the route given in the instructions.
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.