37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 87082 |
Time | |
Date | 198805 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : pvd |
State Reference | RI |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 13000 flight time type : 1500 |
ASRS Report | 87082 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 210 flight time total : 8000 flight time type : 2600 |
ASRS Report | 87427 |
Events | |
Anomaly | incursion : runway non adherence : clearance |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Airport |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
On taxi out, the ground controller, instructed us to taxi out to runway 23L, via runway 5L, and north (november) taxiway. Since north taxiway is not well marked on either the commercial airport diagram nor the actual airport layout, we asked for more specific instructions. The ground controller told us to follow runway 5L, to the 'old 10/28 runway', and then make about a 90 degree right turn onto november taxiway. As we approached this intersection area, I turned onto runway 16/34, expecting to see a taxiway with runway markings. As I completed the turn, I looked at the compass and saw that I had turned too far right, on to runway 16/34 (this used to be the way which we were routinely cleared to runway 23L). Contributing factors were a lack of properly marked taxiways, coupled with my expecting to taxi down an 'old runway' 10/28, and a previously familiar taxi route (16/34) to runway 23L. The controller's instructions led me 'astray' somewhat, and I'll be more vigilant in the future. The runway 16/34 was not in use, and crossed the taxi route, and we were told to remain on runway 16/34, for back taxi on 23L, as was previously a customary thing to do, 'no problem', commented the controller. I suggest improving the taxiway airport diagram chart, and improving airport taxiway signs. Callback conversation with reporter revealed the following information: reporter was rather vague as to the exact taxiway marking on the airport in general but was specific that no marking exists at the intersection of 16/34 and old 10/28. Suggests the marking of the intersection as approaching runway 16/34 when taxiing on runway 5L plus an indication of the exact location of taxiway 'north'.
Original NASA ASRS Text
Title: TAXIED ONTO RWY IN ERROR ACCOUNT POOR ARPT MARKINGS.
Narrative: ON TAXI OUT, THE GND CTLR, INSTRUCTED US TO TAXI OUT TO RWY 23L, VIA RWY 5L, AND N (NOVEMBER) TAXIWAY. SINCE N TAXIWAY IS NOT WELL MARKED ON EITHER THE COMMERCIAL ARPT DIAGRAM NOR THE ACTUAL ARPT LAYOUT, WE ASKED FOR MORE SPECIFIC INSTRUCTIONS. THE GND CTLR TOLD US TO FOLLOW RWY 5L, TO THE 'OLD 10/28 RWY', AND THEN MAKE ABOUT A 90 DEG RIGHT TURN ONTO NOVEMBER TAXIWAY. AS WE APCHED THIS INTERSECTION AREA, I TURNED ONTO RWY 16/34, EXPECTING TO SEE A TAXIWAY WITH RWY MARKINGS. AS I COMPLETED THE TURN, I LOOKED AT THE COMPASS AND SAW THAT I HAD TURNED TOO FAR RIGHT, ON TO RWY 16/34 (THIS USED TO BE THE WAY WHICH WE WERE ROUTINELY CLRED TO RWY 23L). CONTRIBUTING FACTORS WERE A LACK OF PROPERLY MARKED TAXIWAYS, COUPLED WITH MY EXPECTING TO TAXI DOWN AN 'OLD RWY' 10/28, AND A PREVIOUSLY FAMILIAR TAXI ROUTE (16/34) TO RWY 23L. THE CTLR'S INSTRUCTIONS LED ME 'ASTRAY' SOMEWHAT, AND I'LL BE MORE VIGILANT IN THE FUTURE. THE RWY 16/34 WAS NOT IN USE, AND CROSSED THE TAXI ROUTE, AND WE WERE TOLD TO REMAIN ON RWY 16/34, FOR BACK TAXI ON 23L, AS WAS PREVIOUSLY A CUSTOMARY THING TO DO, 'NO PROBLEM', COMMENTED THE CTLR. I SUGGEST IMPROVING THE TAXIWAY ARPT DIAGRAM CHART, AND IMPROVING ARPT TAXIWAY SIGNS. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING INFORMATION: REPORTER WAS RATHER VAGUE AS TO THE EXACT TXWY MARKING ON THE ARPT IN GENERAL BUT WAS SPECIFIC THAT NO MARKING EXISTS AT THE INTERSECTION OF 16/34 AND OLD 10/28. SUGGESTS THE MARKING OF THE INTERSECTION AS APCHING RWY 16/34 WHEN TAXIING ON RWY 5L PLUS AN INDICATION OF THE EXACT LOCATION OF TXWY 'N'.
Data retrieved from NASA's ASRS site as of August 2007 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.