PA28 issued 3 360 degrees to accommodate BE90 entering cll traffic pattern.

Attributes
ACN	538434
Time
Date	200202
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : cll.airport
State Reference	TX
Altitude	msl bound lower : 1200 msl bound upper : 1300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : cll.tower
Operator	general aviation : personal
Make Model Name	PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	None
Aircraft 2
Controlling Facilities	tower : cll.tower
Make Model Name	King Air C90 E90
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 25 flight time total : 1350 flight time type : 450
ASRS Report	538434
Person 2
Function	flight crew : single pilot
Events
Anomaly	non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Situations
ATC Facility	procedure or policy : cll.tower

Narrative:

I called tower at easterwood (cll), 20 mi out (north), with ATIS, 3500 ft MSL descending for landing cll. I was instructed 'straight-in runway 16, report 4 mi final.' a king air called 8 mi southwest cll and was instructed to join right downwind runway 16. I next called '4 mi final, runway 16,' and tower asked if I had field in sight, which I acknowledged. He then cleared the king air to land, #1 on runway 16. I was now at about 2 mi and instructed by tower to make left 360 degrees, turn to allow the king air in. I requested if an emergency situation had occurred since I was on short final. (No emergency by other aircraft.) tower had difficulty seeing the king air and now I called left base for runway 16 and no traffic in sight. King air was now turning right base runway 16 and tower told me 'do another 360 degrees,' which I did. King air reported some traffic, not me, but was cleared to land. I had to make a third 360 degrees to avoid traffic (Z) all at low altitude and on close in to runway 16, then landed. I believe tower favored larger aircraft and caused safety issues.

Original NASA ASRS Text

Title: PA28 ISSUED 3 360 DEGS TO ACCOMMODATE BE90 ENTERING CLL TFC PATTERN.

Narrative: I CALLED TWR AT EASTERWOOD (CLL), 20 MI OUT (N), WITH ATIS, 3500 FT MSL DSNDING FOR LNDG CLL. I WAS INSTRUCTED 'STRAIGHT-IN RWY 16, RPT 4 MI FINAL.' A KING AIR CALLED 8 MI SW CLL AND WAS INSTRUCTED TO JOIN R DOWNWIND RWY 16. I NEXT CALLED '4 MI FINAL, RWY 16,' AND TWR ASKED IF I HAD FIELD IN SIGHT, WHICH I ACKNOWLEDGED. HE THEN CLRED THE KING AIR TO LAND, #1 ON RWY 16. I WAS NOW AT ABOUT 2 MI AND INSTRUCTED BY TWR TO MAKE L 360 DEGS, TURN TO ALLOW THE KING AIR IN. I REQUESTED IF AN EMER SIT HAD OCCURRED SINCE I WAS ON SHORT FINAL. (NO EMER BY OTHER ACFT.) TWR HAD DIFFICULTY SEEING THE KING AIR AND NOW I CALLED L BASE FOR RWY 16 AND NO TFC IN SIGHT. KING AIR WAS NOW TURNING R BASE RWY 16 AND TWR TOLD ME 'DO ANOTHER 360 DEGS,' WHICH I DID. KING AIR RPTED SOME TFC, NOT ME, BUT WAS CLRED TO LAND. I HAD TO MAKE A THIRD 360 DEGS TO AVOID TFC (Z) ALL AT LOW ALT AND ON CLOSE IN TO RWY 16, THEN LANDED. I BELIEVE TWR FAVORED LARGER ACFT AND CAUSED SAFETY ISSUES.

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.