Citrabra departure from lou experienced conflict with maule on go around.

Attributes
ACN	598526
Time
Date	200311
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lou.airport
State Reference	KY
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : lou.tower
Operator	general aviation : personal
Make Model Name	Champion Citabria 7ECA
Operating Under FAR Part	Part 91
Flight Phase	ground : holding ground : taxi
Flight Plan	None
Aircraft 2
Controlling Facilities	tower : lou.tower
Operator	general aviation : personal
Make Model Name	M-7
Operating Under FAR Part	Part 91
Flight Phase	landing : go around
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 8 flight time total : 12500 flight time type : 5
ASRS Report	598526
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took evasive action flight crew : executed go around
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Ambiguous

Narrative:

We taxied out with ATIS information 'to runway 24, did the run-up and then called tower, 'ready for takeoff runway 24.' tower told me, 'aircraft X, hold short.' I repeated 'holding short, aircraft X.' shortly after this, I heard, 'aircraft X, cleared for takeoff.' I proceeded onto the runway. Once lined up, I asked tower for a right turn departure. Tower replied, 'air carrier X, clear the runway,' followed by 'maule xx's, go around.' I then saw the maule fly overhead on the go around. I was still stopped, lined up on runway 24. Shortly after this, I received a takeoff clearance. 'Aircraft X, cleared for takeoff, right approved.' I departed the area and no further comments. I did notice on departure that the maule stayed in the pattern and did have a similar tail number. I do not know what that was. It also sounded as if there were 2 controllers working the tower frequency, or it may have been the controller's microphone was malfunctioned (loud and soft). Looking back, it would have been better if all involved (controller and pilots) to use the full call sign in a busy pattern. Also controllers should have their mikes the proper distance from their mouths. All should listen carefully in a busy pattern.

Original NASA ASRS Text

Title: CITRABRA DEP FROM LOU EXPERIENCED CONFLICT WITH MAULE ON GAR.

Narrative: WE TAXIED OUT WITH ATIS INFO 'TO RWY 24, DID THE RUN-UP AND THEN CALLED TWR, 'READY FOR TKOF RWY 24.' TWR TOLD ME, 'ACFT X, HOLD SHORT.' I REPEATED 'HOLDING SHORT, ACFT X.' SHORTLY AFTER THIS, I HEARD, 'ACFT X, CLRED FOR TKOF.' I PROCEEDED ONTO THE RWY. ONCE LINED UP, I ASKED TWR FOR A R TURN DEP. TWR REPLIED, 'ACR X, CLR THE RWY,' FOLLOWED BY 'MAULE XX'S, GO AROUND.' I THEN SAW THE MAULE FLY OVERHEAD ON THE GAR. I WAS STILL STOPPED, LINED UP ON RWY 24. SHORTLY AFTER THIS, I RECEIVED A TKOF CLRNC. 'ACFT X, CLRED FOR TKOF, R APPROVED.' I DEPARTED THE AREA AND NO FURTHER COMMENTS. I DID NOTICE ON DEP THAT THE MAULE STAYED IN THE PATTERN AND DID HAVE A SIMILAR TAIL NUMBER. I DO NOT KNOW WHAT THAT WAS. IT ALSO SOUNDED AS IF THERE WERE 2 CTLRS WORKING THE TWR FREQ, OR IT MAY HAVE BEEN THE CTLR'S MIKE WAS MALFUNCTIONED (LOUD AND SOFT). LOOKING BACK, IT WOULD HAVE BEEN BETTER IF ALL INVOLVED (CTLR AND PLTS) TO USE THE FULL CALL SIGN IN A BUSY PATTERN. ALSO CTLRS SHOULD HAVE THEIR MIKES THE PROPER DISTANCE FROM THEIR MOUTHS. ALL SHOULD LISTEN CAREFULLY IN A BUSY PATTERN.

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.