C172 pilot described incident when tki tower controller used unclr verbiage to issue a go around exp...

Attributes
ACN	720554
Time
Date	200612
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : tki.tower
State Reference	TX
Altitude	agl single value : 150
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : tki.tower
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Flight Plan	None
Aircraft 2
Controlling Facilities	tower : tki.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	landing : roll
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 3 flight time total : 159 flight time type : 20
ASRS Report	720554
Person 2
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne less severe other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

The incident occurred on during a pleasure flight on dec/xa/06. I was originally cleared for takeoff on runway 17 and I made 3 uneventful 'touch and go' lndgs. After completing the third 'touch and go' landing I was advised to exit the pattern on the southeasterly heading until further advised. I was shortly advised to enter a left base and cleared to land on runway 35. I made 2 uneventful 'touch and go' lndgs. Sometime during my second approach to runway 35 I overheard communication between the controller and a pilot of a jet. I continued in a normal right traffic pattern for runway 35. I was given clearance to land on runway 35. On my mid/short final approach the controller gave me the instruction; 'cessna go around turn right.' at the same moment the controller gave me the instruction I observed a jet midfield and rolling on a heading of runway 17. I did not know if the jet was departing the runway or arriving but he was clearly rolling. I turned my aircraft right (heading of 90 degrees) and I was immediately chastised by the controller. The controller said; 'I said go around turn right but go ahead and continue on the easterly heading.' although there was a second aircraft in the pattern (C172) there was no conflict. The other aircraft was just turning crosswind to downwind for runway 35. It turned out that the jet was not taking off but was in fact landing on the opposite heading runway 17. My assertion is that non standard radio communication resulted in a miscom that did not achieve the safest result. I believe a better instruction may have been; 'cessna full go around make r-hand traffic for runway 35.' I discussed the issue with my club safety officer and I also contacted my personal flight instructor to get advice on how to deal with non standard radio communication in the future. Both individuals shared with me that in the event of an imminent safety concern in controled airspace the pilot is ultimately responsible for the safety of his aircraft and occupants; keeping in mind that in all cases the pilot should communicate clearly and concisely his actions to the controller. In the event there is no immediate safety concern a pilot should ask for clarification. I will follow this advice unless otherwise advised.

Original NASA ASRS Text

Title: C172 PLT DESCRIBED INCIDENT WHEN TKI TWR CTLR USED UNCLR VERBIAGE TO ISSUE A GAR EXPECTING THE ACFT TO ENTER R TFC FROM THE GAR.

Narrative: THE INCIDENT OCCURRED ON DURING A PLEASURE FLT ON DEC/XA/06. I WAS ORIGINALLY CLRED FOR TKOF ON RWY 17 AND I MADE 3 UNEVENTFUL 'TOUCH AND GO' LNDGS. AFTER COMPLETING THE THIRD 'TOUCH AND GO' LNDG I WAS ADVISED TO EXIT THE PATTERN ON THE SOUTHEASTERLY HDG UNTIL FURTHER ADVISED. I WAS SHORTLY ADVISED TO ENTER A L BASE AND CLRED TO LAND ON RWY 35. I MADE 2 UNEVENTFUL 'TOUCH AND GO' LNDGS. SOMETIME DURING MY SECOND APCH TO RWY 35 I OVERHEARD COM BTWN THE CTLR AND A PLT OF A JET. I CONTINUED IN A NORMAL R TFC PATTERN FOR RWY 35. I WAS GIVEN CLRNC TO LAND ON RWY 35. ON MY MID/SHORT FINAL APCH THE CTLR GAVE ME THE INSTRUCTION; 'CESSNA GO AROUND TURN R.' AT THE SAME MOMENT THE CTLR GAVE ME THE INSTRUCTION I OBSERVED A JET MIDFIELD AND ROLLING ON A HDG OF RWY 17. I DID NOT KNOW IF THE JET WAS DEPARTING THE RWY OR ARRIVING BUT HE WAS CLRLY ROLLING. I TURNED MY ACFT R (HDG OF 90 DEGS) AND I WAS IMMEDIATELY CHASTISED BY THE CTLR. THE CTLR SAID; 'I SAID GO AROUND TURN R BUT GO AHEAD AND CONTINUE ON THE EASTERLY HDG.' ALTHOUGH THERE WAS A SECOND ACFT IN THE PATTERN (C172) THERE WAS NO CONFLICT. THE OTHER ACFT WAS JUST TURNING XWIND TO DOWNWIND FOR RWY 35. IT TURNED OUT THAT THE JET WAS NOT TAKING OFF BUT WAS IN FACT LNDG ON THE OPPOSITE HDG RWY 17. MY ASSERTION IS THAT NON STANDARD RADIO COM RESULTED IN A MISCOM THAT DID NOT ACHIEVE THE SAFEST RESULT. I BELIEVE A BETTER INSTRUCTION MAY HAVE BEEN; 'CESSNA FULL GAR MAKE R-HAND TFC FOR RWY 35.' I DISCUSSED THE ISSUE WITH MY CLUB SAFETY OFFICER AND I ALSO CONTACTED MY PERSONAL FLT INSTRUCTOR TO GET ADVICE ON HOW TO DEAL WITH NON STANDARD RADIO COM IN THE FUTURE. BOTH INDIVIDUALS SHARED WITH ME THAT IN THE EVENT OF AN IMMINENT SAFETY CONCERN IN CTLED AIRSPACE THE PLT IS ULTIMATELY RESPONSIBLE FOR THE SAFETY OF HIS ACFT AND OCCUPANTS; KEEPING IN MIND THAT IN ALL CASES THE PLT SHOULD COMMUNICATE CLRLY AND CONCISELY HIS ACTIONS TO THE CTLR. IN THE EVENT THERE IS NO IMMEDIATE SAFETY CONCERN A PLT SHOULD ASK FOR CLARIFICATION. I WILL FOLLOW THIS ADVICE UNLESS OTHERWISE ADVISED.

Data retrieved from NASA's ASRS site as of January 2009 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.

C172 pilot described incident when tki tower controller used unclr verbiage to issue a go around expecting the aircraft to enter right traffic from the go around.