Potential conflict ensues after small aircraft pilot botches landing and performs a go around. Multi...

Attributes
ACN	281500
Time
Date	199408
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sat
State Reference	TX
Altitude	agl bound lower : 0 agl bound upper : 500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : sat tracon : abe
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	landing : go around landing other
Flight Plan	None
Aircraft 2
Operator	general aviation : personal
Make Model Name	Cessna Twin Piston Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial climbout : takeoff cruise other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Experience	flight time last 90 days : 80 flight time total : 782
ASRS Report	281500
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : airborne less severe non adherence : clearance other anomaly other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took evasive action other
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 1800 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Clearance was given by the tower to land on runway 12L. In retrospect, my approach to land was poor resulting in a poor landing. After bouncing several times, I decided to execute a go around. I put the airplane in the proper confign -- flaps up, full power, began a takeoff and informed the tower of my go around. Tower issued an immediate left turn, with which I complied, before the landing gear was up. My situational awareness was that I completed the turn and did not encroach on runway 3. After executing the turn, I realized what had happened. The tower had cleared a twin cessna for takeoff on runway 3. The twin cessna saw my go around and executed a right turn away from my extended travel path had I continued to fly straight ahead. The tower cleared me for a second left downwind for runway 12L, and asked if I had a problem, and why I did not communicate my go around sooner. I responded I had plenty to do to put the aircraft in the proper confign for go around and I called the tower as soon as I felt able. After an uneventful second landing, I was requested to contact the tower after shutdown, which I did. Apparently from the tower's perspective, I was in a stabilized, decelerating rollout confign when they released the twin cessna for takeoff. In reality I was not, so my go around action was unexpected by the tower, resulting in the immediate left turn and some stress. The pilot of the twin cessna was upset, and exhibited good judgement in turning to the right to avoid my extended path, had I kept flying runway heading. Just as it is any pilot's choice to execute a go around when things don't seem right, I exhibited good judgement in executing this go around from a bad landing. This is not my aircraft, and had I continued with the landing, it could have resulted in porpoising, or a propeller strike. Pilots should aviate, navigation, then communicate, which I did.

Original NASA ASRS Text

Title: POTENTIAL CONFLICT ENSUES AFTER SMA PLT BOTCHES LNDG AND PERFORMS A GAR. MULTIPLE RWY OP INTERSECTING RWYS. ARR DEP TFC.

Narrative: CLRNC WAS GIVEN BY THE TWR TO LAND ON RWY 12L. IN RETROSPECT, MY APCH TO LAND WAS POOR RESULTING IN A POOR LNDG. AFTER BOUNCING SEVERAL TIMES, I DECIDED TO EXECUTE A GAR. I PUT THE AIRPLANE IN THE PROPER CONFIGN -- FLAPS UP, FULL PWR, BEGAN A TKOF AND INFORMED THE TWR OF MY GAR. TWR ISSUED AN IMMEDIATE L TURN, WITH WHICH I COMPLIED, BEFORE THE LNDG GEAR WAS UP. MY SITUATIONAL AWARENESS WAS THAT I COMPLETED THE TURN AND DID NOT ENCROACH ON RWY 3. AFTER EXECUTING THE TURN, I REALIZED WHAT HAD HAPPENED. THE TWR HAD CLRED A TWIN CESSNA FOR TKOF ON RWY 3. THE TWIN CESSNA SAW MY GAR AND EXECUTED A R TURN AWAY FROM MY EXTENDED TRAVEL PATH HAD I CONTINUED TO FLY STRAIGHT AHEAD. THE TWR CLRED ME FOR A SECOND L DOWNWIND FOR RWY 12L, AND ASKED IF I HAD A PROB, AND WHY I DID NOT COMMUNICATE MY GAR SOONER. I RESPONDED I HAD PLENTY TO DO TO PUT THE ACFT IN THE PROPER CONFIGN FOR GAR AND I CALLED THE TWR AS SOON AS I FELT ABLE. AFTER AN UNEVENTFUL SECOND LNDG, I WAS REQUESTED TO CONTACT THE TWR AFTER SHUTDOWN, WHICH I DID. APPARENTLY FROM THE TWR'S PERSPECTIVE, I WAS IN A STABILIZED, DECELERATING ROLLOUT CONFIGN WHEN THEY RELEASED THE TWIN CESSNA FOR TKOF. IN REALITY I WAS NOT, SO MY GAR ACTION WAS UNEXPECTED BY THE TWR, RESULTING IN THE IMMEDIATE L TURN AND SOME STRESS. THE PLT OF THE TWIN CESSNA WAS UPSET, AND EXHIBITED GOOD JUDGEMENT IN TURNING TO THE R TO AVOID MY EXTENDED PATH, HAD I KEPT FLYING RWY HDG. JUST AS IT IS ANY PLT'S CHOICE TO EXECUTE A GAR WHEN THINGS DON'T SEEM RIGHT, I EXHIBITED GOOD JUDGEMENT IN EXECUTING THIS GAR FROM A BAD LNDG. THIS IS NOT MY ACFT, AND HAD I CONTINUED WITH THE LNDG, IT COULD HAVE RESULTED IN PORPOISING, OR A PROP STRIKE. PLTS SHOULD AVIATE, NAV, THEN COMMUNICATE, WHICH I DID.

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.

Potential conflict ensues after small aircraft pilot botches landing and performs a go around. Multiple runway operation intersecting runways. Arrival departure traffic.