B737-300 crew taxied on a weight restr taxiway at maf.

Attributes
ACN	500877
Time
Date	200102
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : maf.airport
State Reference	TX
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
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 : 180 flight time total : 24500 flight time type : 10000
ASRS Report	500877
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 125 flight time total : 4900 flight time type : 400
ASRS Report	501060
Events
Anomaly	incursion : taxiway non adherence : published procedure other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : became reoriented none taken : detected after the fact
Consequence	other
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance Airport
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Called for taxi expecting either the active (runway 16R) or the visual (runway 10). Tower offered the nearer runway (runway 34L) which was downwind. We accepted the quick taxi and set about doing the performance all over, then the checklist and briefing and finished with time to spare. We called for takeoff and were cleared. As we rounded the corner, I noticed that the route I had chosen was narrow. I said that I bet we just screwed up. Sure enough, a quick glance at the chart told me that taxiway left was not stressed for aircraft over 60000 pounds. I had studied the chart before landing, studied the airport plate page, looked at the taxi chart when I was cleared for taxi and again when cleared for takeoff. The arrow leading from the note and pointing at taxiway left was very long. I didn't see it. Nor did I see the warning sign which was probably there. This could have been prevented only by greater vigilance. But I have often longed for the commercial chart to color code or shade the areas that are not approved for taxi to help prevent these kinds of errors.

Original NASA ASRS Text

Title: B737-300 CREW TAXIED ON A WT RESTR TXWY AT MAF.

Narrative: CALLED FOR TAXI EXPECTING EITHER THE ACTIVE (RWY 16R) OR THE VISUAL (RWY 10). TWR OFFERED THE NEARER RWY (RWY 34L) WHICH WAS DOWNWIND. WE ACCEPTED THE QUICK TAXI AND SET ABOUT DOING THE PERFORMANCE ALL OVER, THEN THE CHKLIST AND BRIEFING AND FINISHED WITH TIME TO SPARE. WE CALLED FOR TKOF AND WERE CLRED. AS WE ROUNDED THE CORNER, I NOTICED THAT THE RTE I HAD CHOSEN WAS NARROW. I SAID THAT I BET WE JUST SCREWED UP. SURE ENOUGH, A QUICK GLANCE AT THE CHART TOLD ME THAT TXWY L WAS NOT STRESSED FOR ACFT OVER 60000 LBS. I HAD STUDIED THE CHART BEFORE LNDG, STUDIED THE ARPT PLATE PAGE, LOOKED AT THE TAXI CHART WHEN I WAS CLRED FOR TAXI AND AGAIN WHEN CLRED FOR TKOF. THE ARROW LEADING FROM THE NOTE AND POINTING AT TXWY L WAS VERY LONG. I DIDN'T SEE IT. NOR DID I SEE THE WARNING SIGN WHICH WAS PROBABLY THERE. THIS COULD HAVE BEEN PREVENTED ONLY BY GREATER VIGILANCE. BUT I HAVE OFTEN LONGED FOR THE COMMERCIAL CHART TO COLOR CODE OR SHADE THE AREAS THAT ARE NOT APPROVED FOR TAXI TO HELP PREVENT THESE KINDS OF ERRORS.

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.