A B767-300 crew at sbgr taxied onto a closed taxiway requiring ground crew assistance to exit and pr...

Attributes
ACN	719620
Time
Date	200612
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : sbgr.airport
State Reference	FO
Altitude	agl single value : 0
Environment
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B757-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : relief pilot
ASRS Report	719620
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	719622
Events
Anomaly	non adherence : published procedure non adherence : clearance other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	other
Supplementary
Problem Areas	Airport Flight Crew Human Performance ATC Human Performance Company Chart Or Publication
Primary Problem	Flight Crew Human Performance

Narrative:

After landing at gru; we crossed a runway as cleared; then taxied towards a closed taxiway; without actually entering it. There was no room to turn around; so we needed a tug to push us back and tow to gate. Detail: we landed runway 9R and exited bb; held short of runway 9L very briefly without having to stop completely; then were 'cleared to cross runway 9L and take dd and contact ground.' this should have been stated as 'back taxi on runway 9L to dd and then contact ground.' so; we crossed expeditiously directly into a taxiway that was closed for construction. We realized this before actually entering the taxiway. But by then it was too late to turn. So we called operations; and a tug came out to correct the situation. Why did this happen? 1) the above cited poor instructions from tower. 2) our failure to note the closure on gru ATIS. This occurred because ATIS was very hard to copy when we first tuned in at top-of-descent. It was difficult just to hear runway in use and altimeter; let alone taxi closure details. And then we become very busy during descent; with WX; communication problems and a busy STAR. 3) no mention of taxiway closure in paperwork.

Original NASA ASRS Text

Title: A B767-300 CREW AT SBGR TAXIED ONTO A CLOSED TXWY REQUIRING GND CREW ASSISTANCE TO EXIT AND PROCEED TO THE GATE.

Narrative: AFTER LNDG AT GRU; WE CROSSED A RWY AS CLRED; THEN TAXIED TOWARDS A CLOSED TXWY; WITHOUT ACTUALLY ENTERING IT. THERE WAS NO ROOM TO TURN AROUND; SO WE NEEDED A TUG TO PUSH US BACK AND TOW TO GATE. DETAIL: WE LANDED RWY 9R AND EXITED BB; HELD SHORT OF RWY 9L VERY BRIEFLY WITHOUT HAVING TO STOP COMPLETELY; THEN WERE 'CLRED TO CROSS RWY 9L AND TAKE DD AND CONTACT GND.' THIS SHOULD HAVE BEEN STATED AS 'BACK TAXI ON RWY 9L TO DD AND THEN CONTACT GND.' SO; WE CROSSED EXPEDITIOUSLY DIRECTLY INTO A TXWY THAT WAS CLOSED FOR CONSTRUCTION. WE REALIZED THIS BEFORE ACTUALLY ENTERING THE TXWY. BUT BY THEN IT WAS TOO LATE TO TURN. SO WE CALLED OPS; AND A TUG CAME OUT TO CORRECT THE SIT. WHY DID THIS HAPPEN? 1) THE ABOVE CITED POOR INSTRUCTIONS FROM TWR. 2) OUR FAILURE TO NOTE THE CLOSURE ON GRU ATIS. THIS OCCURRED BECAUSE ATIS WAS VERY HARD TO COPY WHEN WE FIRST TUNED IN AT TOP-OF-DSCNT. IT WAS DIFFICULT JUST TO HEAR RWY IN USE AND ALTIMETER; LET ALONE TAXI CLOSURE DETAILS. AND THEN WE BECOME VERY BUSY DURING DSCNT; WITH WX; COM PROBS AND A BUSY STAR. 3) NO MENTION OF TXWY CLOSURE IN PAPERWORK.

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

A B767-300 crew at sbgr taxied onto a closed taxiway requiring ground crew assistance to exit and proceed to the gate.