MD11 flight crew challenged by rjoo tower after turning onto what was notamed as a closed taxiway.

Attributes
ACN	501187
Time
Date	200102
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : rjoo.airport
State Reference	FO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 9500 flight time type : 1600
ASRS Report	501187
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Events
Anomaly	incursion : taxiway non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Company Flight Crew Human Performance Airport
Primary Problem	Company
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : rjoo.tower
Airport	procedure or policy : rjoo.airport
Chart	airport : rjoo.airport

Narrative:

After landing at rjoo, osaka, japan, runway 6, VMC conditions exited runway at first available taxiway (highspd taxiway R3). Once on taxiway R3, rjoo tower said 'air carrier X, why are you on 'taxiway R3?' taxiway R3 is closed.' after approximately 5 mins of discussion in the tower, ground controller cleared us to continue to taxi on taxiway R3 and taxi to the gate. After shutdown, rjoo tower contacted the crew via cell phone to complain about using the 'closed taxiway R3.' I replied there were no NOTAMS, commercial chart restrs, ATIS, or tower instructions on landing to prevent use of high speed taxiway R3 which was completely lighted. Tower said 'all txwys except one at end closed for maintenance' and we should have seen this on NOTAMS. Turned out the NOTAM the tower referred to was a local document (airport diagram) marked with a pen showing taxiway maintenance and times and mailed/faxed to airport tenants. No way for arrival aircraft to have this information if not on ICAO NOTAMS or ATIS. Nonstandard information reporting. No further contact with rjoo tower at this time.

Original NASA ASRS Text

Title: MD11 FLC CHALLENGED BY RJOO TWR AFTER TURNING ONTO WHAT WAS NOTAMED AS A CLOSED TXWY.

Narrative: AFTER LNDG AT RJOO, OSAKA, JAPAN, RWY 6, VMC CONDITIONS EXITED RWY AT FIRST AVAILABLE TXWY (HIGHSPD TXWY R3). ONCE ON TXWY R3, RJOO TWR SAID 'ACR X, WHY ARE YOU ON 'TXWY R3?' TXWY R3 IS CLOSED.' AFTER APPROX 5 MINS OF DISCUSSION IN THE TWR, GND CTLR CLRED US TO CONTINUE TO TAXI ON TXWY R3 AND TAXI TO THE GATE. AFTER SHUTDOWN, RJOO TWR CONTACTED THE CREW VIA CELL PHONE TO COMPLAIN ABOUT USING THE 'CLOSED TXWY R3.' I REPLIED THERE WERE NO NOTAMS, COMMERCIAL CHART RESTRS, ATIS, OR TWR INSTRUCTIONS ON LNDG TO PREVENT USE OF HIGH SPD TXWY R3 WHICH WAS COMPLETELY LIGHTED. TWR SAID 'ALL TXWYS EXCEPT ONE AT END CLOSED FOR MAINT' AND WE SHOULD HAVE SEEN THIS ON NOTAMS. TURNED OUT THE NOTAM THE TWR REFERRED TO WAS A LCL DOCUMENT (ARPT DIAGRAM) MARKED WITH A PEN SHOWING TXWY MAINT AND TIMES AND MAILED/FAXED TO ARPT TENANTS. NO WAY FOR ARR ACFT TO HAVE THIS INFO IF NOT ON ICAO NOTAMS OR ATIS. NONSTANDARD INFO RPTING. NO FURTHER CONTACT WITH RJOO TWR AT THIS TIME.

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