37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1427686 |
Time | |
Date | 201702 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | FRG.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 38 Flight Crew Total 8200 Flight Crew Type 1004 |
Events | |
Anomaly | Deviation - Procedural Clearance Ground Event / Encounter Other / Unknown Ground Incursion Runway |
Narrative:
While starting to taxi from an FBO at frg; we received instructions to taxi runway 32 via G; D and hold short of the assigned runway. As we taxi out of the FBO; we started looking for taxiway G but had a hard time finding it. We could not see any defined markings; signs or lighting that would indicate a taxiway. There was; however; a road 'we thought' that turned out to be the taxiway. It wasn't until we were parallel the taxiway while taxing via runway 19 and after receiving new instructions from the tower that we said; that's the taxiway; still not convinced; we both agree that this area needs help. I must say that the responsibility rest with the crew all the time; especially the PIC. As we taxi out; the flying pilot brief that he was familiar with the airport and I was happy to hear that he was familiar with the airfield because of the difficulties we both had trying to identify the taxiway G and the taxiway in general. It became evident that something was not right when we started to see runway 19 approaching and the hold lines; but; by the time I said we're approaching a runway and the captain realized he needed to stop we went probably 1 or 2 feet beyond the hold short of the runway lines.besides the need to make this area more visible; paint some markings or maybe add some signs; next time; I as the PIC of the flight; I'll make certain our actions will not lead us to an incursion!
Original NASA ASRS Text
Title: Corporate jet pilot reported a taxiway incursion at FRG. Reporter stated taxiway G signage and markings at the ramp were difficult to detect.
Narrative: While starting to taxi from an FBO at FRG; we received instructions to taxi Runway 32 via G; D and hold short of the assigned runway. As we taxi out of the FBO; we started looking for taxiway G but had a hard time finding it. We could not see any defined markings; Signs or lighting that would indicate a taxiway. There was; however; a road 'we thought' that turned out to be the taxiway. It wasn't until we were parallel the taxiway while taxing via Runway 19 and after receiving new instructions from the tower that we said; that's the taxiway; still not convinced; we both agree that this area needs help. I must say that the responsibility rest with the crew all the time; especially the PIC. As we taxi out; the flying pilot brief that he was familiar with the Airport and I was happy to hear that he was familiar with the airfield because of the difficulties we both had trying to identify the Taxiway G and the taxiway in general. It became evident that something was not right when we started to see Runway 19 approaching and the hold lines; but; by the time I said we're approaching a Runway and the Captain realized he needed to stop we went probably 1 or 2 feet beyond the hold short of the Runway lines.Besides the need to make this area more visible; paint some markings or maybe add some signs; next time; I as the PIC of the flight; I'll make certain our actions will not lead us to an incursion!
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.