|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1801 To 2400|
|Locale Reference||airport : ord.airport|
|Altitude||agl single value : 0|
|Operator||common carrier : air carrier|
|Make Model Name||B737-300|
|Flight Phase||ground : taxi|
|Controlling Facilities||tower : ord.tower|
|Make Model Name||Any Unknown or Unlisted Aircraft Manufacturer|
|Flight Phase||ground : taxi|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Experience||flight time last 90 days : 180|
flight time total : 15000
flight time type : 4000
|Anomaly||incursion : taxiway|
non adherence : clearance
other anomaly other
|Resolutory Action||controller : issued new clearance|
|Problem Areas||Environmental Factor|
Flight Crew Human Performance
ATC Human Performance
|Primary Problem||Environmental Factor|
|Air Traffic Incident||Pilot Deviation|
After pushing from gate, ground contacted us with taxi instructions to runway 9L, via taxiway B, taxiway A6, taxiway J to runway 9L. We entered taxiway B at taxiway A4. When we made the left turn onto taxiway B, we saw an aircraft approaching from the opposite direction. We stopped and asked ground for clarification. Apparently the controller had wanted us to use taxiway east to join taxiway B. We were issued new taxi instructions and proceeded to runway 9L without incident. Because ground frequency in ord is so busy it is often difficult to read back taxi instructions. In retrospect, we should have read back the clearance to insure compliance. This would have eliminated any misunderstanding. Perhaps use of coded taxi rtes could also eliminate confusion. The first officer is aware of this report I am filing. Again, I believe one of the major issues here is how to effectively communicate when ATC is so congested. Although it takes radio time, I will be reading back all taxi clearance in full.
Original NASA ASRS Text
Title: TXWY INCURSION WHEN B737 FLT CREW DOESN'T FOLLOW THE GND CTLR'S CLRNC PRECISELY AT ORD, IL.
Narrative: AFTER PUSHING FROM GATE, GND CONTACTED US WITH TAXI INSTRUCTIONS TO RWY 9L, VIA TXWY B, TXWY A6, TXWY J TO RWY 9L. WE ENTERED TXWY B AT TXWY A4. WHEN WE MADE THE L TURN ONTO TXWY B, WE SAW AN ACFT APCHING FROM THE OPPOSITE DIRECTION. WE STOPPED AND ASKED GND FOR CLARIFICATION. APPARENTLY THE CTLR HAD WANTED US TO USE TXWY E TO JOIN TXWY B. WE WERE ISSUED NEW TAXI INSTRUCTIONS AND PROCEEDED TO RWY 9L WITHOUT INCIDENT. BECAUSE GND FREQ IN ORD IS SO BUSY IT IS OFTEN DIFFICULT TO READ BACK TAXI INSTRUCTIONS. IN RETROSPECT, WE SHOULD HAVE READ BACK THE CLRNC TO INSURE COMPLIANCE. THIS WOULD HAVE ELIMINATED ANY MISUNDERSTANDING. PERHAPS USE OF CODED TAXI RTES COULD ALSO ELIMINATE CONFUSION. THE FO IS AWARE OF THIS RPT I AM FILING. AGAIN, I BELIEVE ONE OF THE MAJOR ISSUES HERE IS HOW TO EFFECTIVELY COMMUNICATE WHEN ATC IS SO CONGESTED. ALTHOUGH IT TAKES RADIO TIME, I WILL BE READING BACK ALL TAXI CLRNC IN FULL.
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.