Small aircraft pilot reports confusion and mishandling from tower local controller in traffic patter...

Attributes
ACN	179872
Time
Date	199106
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : spg
State Reference	FL
Altitude	msl bound lower : 150 msl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Aircraft
Flight Phase	descent : approach landing : go around other
Route In Use	approach : visual
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : cfi pilot : commercial
Experience	flight time last 90 days : 100 flight time total : 10000 flight time type : 100
ASRS Report	179872
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course flight crew : took evasive action
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation other
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

Reported about 10 mi northwest. Was not given another report point, even though 5 aircraft were inbound. I called a 3 mi northwest and was cleared to land on 18 from a right base. At about 150' I was given a go around, even though the aircraft in front had cleared the runway. I rejoined pattern, which was very wide, and the tower was not calling turns. 3 aircraft were on base. As we bunched up on final, I was stuck between a southeast high wing in front and a twin behind. I was given a 360 degree turn to the right. I told the controller that that turn would put me on a collision course with the twin behind me, and well right of centerline--silence! The twin was not warned nor told to take evasive action, so seeing a collision was possible, I turned left toward the runway. At this point I was cleared to land. I called the tower, but no one would talk to me. The controller's initials were a.B.; the tower chief's, C.D. Corrective actions: pattern control is very lax and unprofessional. A 360 degree turn on final between 2 aircraft should never be called by a controller. I would have accepted another go around as a safe and sane option.

Original NASA ASRS Text

Title: SMA PLT REPORTS CONFUSION AND MISHANDLING FROM TWR LCL CTLR IN TRAFFIC PATTERN.

Narrative: RPTED ABOUT 10 MI NW. WAS NOT GIVEN ANOTHER RPT POINT, EVEN THOUGH 5 ACFT WERE INBND. I CALLED A 3 MI NW AND WAS CLRED TO LAND ON 18 FROM A RIGHT BASE. AT ABOUT 150' I WAS GIVEN A GAR, EVEN THOUGH THE ACFT IN FRONT HAD CLRED THE RWY. I REJOINED PATTERN, WHICH WAS VERY WIDE, AND THE TWR WAS NOT CALLING TURNS. 3 ACFT WERE ON BASE. AS WE BUNCHED UP ON FINAL, I WAS STUCK BTWN A SE HIGH WING IN FRONT AND A TWIN BEHIND. I WAS GIVEN A 360 DEG TURN TO THE RIGHT. I TOLD THE CTLR THAT THAT TURN WOULD PUT ME ON A COLLISION COURSE WITH THE TWIN BEHIND ME, AND WELL RIGHT OF CENTERLINE--SILENCE! THE TWIN WAS NOT WARNED NOR TOLD TO TAKE EVASIVE ACTION, SO SEEING A COLLISION WAS POSSIBLE, I TURNED LEFT TOWARD THE RWY. AT THIS POINT I WAS CLRED TO LAND. I CALLED THE TWR, BUT NO ONE WOULD TALK TO ME. THE CTLR'S INITIALS WERE A.B.; THE TWR CHIEF'S, C.D. CORRECTIVE ACTIONS: PATTERN CTL IS VERY LAX AND UNPROFESSIONAL. A 360 DEG TURN ON FINAL BTWN 2 ACFT SHOULD NEVER BE CALLED BY A CTLR. I WOULD HAVE ACCEPTED ANOTHER GAR AS A SAFE AND SANE OPTION.

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.

Small aircraft pilot reports confusion and mishandling from tower local controller in traffic pattern.