Air carrier X incorrect readback of ATC instructions. Held short of active runway as landing traffic...

Attributes
ACN	249716
Time
Date	199308
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : cle
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	ground : holding ground other : 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 : 10500 flight time type : 5000
ASRS Report	249716
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	other

Narrative:

We taxied out to runway 23R. By the terminal ramp, we were told to hold short of 28 at zulu. We finished our checklist and was sitting and waiting for mdt to takeoff on runway 23R. The local controller gave taxi instructions to taxi across runway 23L and hold short of 23R. I read back the complete taxi instructions. We checked runway 28 for aircraft and, as we started to move, we both noticed an air carrier Y on 1/4 mi final to runway 23L. Our aircraft may have moved 2 ft or so before we stopped again. I called the tower and asked him about the air carrier Y and he said we didn't go over the hold line and everything was ok. That controller gave us one set of instructions and then said we were clear on to runway 28, but to hold short of 23R. I find it more and more that ATC controllers do not listen to the readbacks of pilots. If we had not looked both ways before we moved, it would have been very close. He (the controller) may have said to taxi onto 28 and hold short of runway 23L, but we read back something very different. This isn't the first time I've had controllers not listen up.

Original NASA ASRS Text

Title: ACR X INCORRECT READBACK OF ATC INSTRUCTIONS. HELD SHORT OF ACTIVE RWY AS LNDG TFC OBSERVED.

Narrative: WE TAXIED OUT TO RWY 23R. BY THE TERMINAL RAMP, WE WERE TOLD TO HOLD SHORT OF 28 AT ZULU. WE FINISHED OUR CHKLIST AND WAS SITTING AND WAITING FOR MDT TO TKOF ON RWY 23R. THE LCL CTLR GAVE TAXI INSTRUCTIONS TO TAXI ACROSS RWY 23L AND HOLD SHORT OF 23R. I READ BACK THE COMPLETE TAXI INSTRUCTIONS. WE CHKED RWY 28 FOR ACFT AND, AS WE STARTED TO MOVE, WE BOTH NOTICED AN ACR Y ON 1/4 MI FINAL TO RWY 23L. OUR ACFT MAY HAVE MOVED 2 FT OR SO BEFORE WE STOPPED AGAIN. I CALLED THE TWR AND ASKED HIM ABOUT THE ACR Y AND HE SAID WE DIDN'T GO OVER THE HOLD LINE AND EVERYTHING WAS OK. THAT CTLR GAVE US ONE SET OF INSTRUCTIONS AND THEN SAID WE WERE CLR ON TO RWY 28, BUT TO HOLD SHORT OF 23R. I FIND IT MORE AND MORE THAT ATC CTLRS DO NOT LISTEN TO THE READBACKS OF PLTS. IF WE HAD NOT LOOKED BOTH WAYS BEFORE WE MOVED, IT WOULD HAVE BEEN VERY CLOSE. HE (THE CTLR) MAY HAVE SAID TO TAXI ONTO 28 AND HOLD SHORT OF RWY 23L, BUT WE READ BACK SOMETHING VERY DIFFERENT. THIS ISN'T THE FIRST TIME I'VE HAD CTLRS NOT LISTEN UP.

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.

Air carrier X incorrect readback of ATC instructions. Held short of active runway as landing traffic observed.