Narrative:

Aircraft call sign was air carrier X, an light transport from mke to fnt. Captain (myself) called for taxi clearance from gate and received clearance from ground control to taxi to runway 19R at mke. Captain proceeded to taxi to the runway and the first officer proceeded with the before takeoff checklist. Captain flipped radio to tower frequency at the appropriate time and spoke the following 'milwaukee tower air carrier X ready 19R.' captain heard the following response. 'Air carrier X taxi into position and hold' captain proceeded to turn the corner and taxi onto the runway 19R and called for the 'final items checklist.' captain visually confirmed there was no traffic on approach end heard nothing on the tower frequency. Captain taxied onto position on the runway and approximately 15 seconds elapsed when tower controller said the following: air carrier X make 180 and taxi off runway, traffic on final. Captain proceeded to the end about 1/2 min later an air carrier large transport came into view on approach. Captain queried the controller and stated he had received clearance to taxi onto the active and acknowledged the clearance before taxiing onto the runway. Controller said that was not what he said and reissued taxi onto active runway clearance. Captain proceeded to do this and a normal departure ensued. No evasive action, priority, delay or conflict took place as a result of the incident. Captain was and still is sure he was given the clearance to taxi onto the runway and verbally acknowledged receipt of the clearance. The first officer said he was busy with the checklist and was not really listening to the communications taking place. Some problems brought forth by this incident are as follows: captain assumed the first officer was actively involved whereas in reality he was not following the events. The controller may not have been listening to the capts acknowledgement of the clearance in the first place and secondly, could have issued a clearance to hold short if he had noticed the aircraft doing something as closely as he should have been. This could have possibly changed the course of events.

Google
 

Original NASA ASRS Text

Title: ACR RPTR THINKS HE RECEIVED A CLRNC TO TAXI INTO POS AND HOLD. CTLR DENIES IT. NO CONFLICT.

Narrative: ACFT CALL SIGN WAS ACR X, AN LTT FROM MKE TO FNT. CAPT (MYSELF) CALLED FOR TAXI CLRNC FROM GATE AND RECEIVED CLRNC FROM GND CTL TO TAXI TO RWY 19R AT MKE. CAPT PROCEEDED TO TAXI TO THE RWY AND THE FO PROCEEDED WITH THE BEFORE TKOF CHKLIST. CAPT FLIPPED RADIO TO TWR FREQ AT THE APPROPRIATE TIME AND SPOKE THE FOLLOWING 'MILWAUKEE TWR ACR X READY 19R.' CAPT HEARD THE FOLLOWING RESPONSE. 'ACR X TAXI INTO POS AND HOLD' CAPT PROCEEDED TO TURN THE CORNER AND TAXI ONTO THE RWY 19R AND CALLED FOR THE 'FINAL ITEMS CHKLIST.' CAPT VISUALLY CONFIRMED THERE WAS NO TFC ON APCH END HEARD NOTHING ON THE TWR FREQ. CAPT TAXIED ONTO POS ON THE RWY AND APPROX 15 SECONDS ELAPSED WHEN TWR CTLR SAID THE FOLLOWING: ACR X MAKE 180 AND TAXI OFF RWY, TFC ON FINAL. CAPT PROCEEDED TO THE END ABOUT 1/2 MIN LATER AN ACR LGT CAME INTO VIEW ON APCH. CAPT QUERIED THE CTLR AND STATED HE HAD RECEIVED CLRNC TO TAXI ONTO THE ACTIVE AND ACKNOWLEDGED THE CLRNC BEFORE TAXIING ONTO THE RWY. CTLR SAID THAT WAS NOT WHAT HE SAID AND REISSUED TAXI ONTO ACTIVE RWY CLRNC. CAPT PROCEEDED TO DO THIS AND A NORMAL DEP ENSUED. NO EVASIVE ACTION, PRIORITY, DELAY OR CONFLICT TOOK PLACE AS A RESULT OF THE INCIDENT. CAPT WAS AND STILL IS SURE HE WAS GIVEN THE CLRNC TO TAXI ONTO THE RWY AND VERBALLY ACKNOWLEDGED RECEIPT OF THE CLRNC. THE FO SAID HE WAS BUSY WITH THE CHKLIST AND WAS NOT REALLY LISTENING TO THE COMS TAKING PLACE. SOME PROBLEMS BROUGHT FORTH BY THIS INCIDENT ARE AS FOLLOWS: CAPT ASSUMED THE FO WAS ACTIVELY INVOLVED WHEREAS IN REALITY HE WAS NOT FOLLOWING THE EVENTS. THE CTLR MAY NOT HAVE BEEN LISTENING TO THE CAPTS ACKNOWLEDGEMENT OF THE CLRNC IN THE FIRST PLACE AND SECONDLY, COULD HAVE ISSUED A CLRNC TO HOLD SHORT IF HE HAD NOTICED THE ACFT DOING SOMETHING AS CLOSELY AS HE SHOULD HAVE BEEN. THIS COULD HAVE POSSIBLY CHANGED THE COURSE OF EVENTS.

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.