Narrative:

15 mi out contacted tower after listening to ATIS. Told to report on 2 mi right base to runway 34. I reported as instructed, and was told to land on runway 28, straight in instead. I was shocked to see that I had been diverted due to an MTR on short approach to 34. Until then I was unaware of military training activities going on, since they were on another frequency. Just as I was about to T/D on 28, tower said, 'go around.' now there was another MTR on short approach to 34. I responded, 'unable.' completed landing and stopped short of 34. The military trainer was told to go around, and they did. If I had executed a go around, the potential for a midair would have occurred at intersection. On runway 28, 200' from intersection of 34, I stopped and asked for a 180 degree turn to return. I was cleared for 180 degree turn. As I departed runway, backtaxiing, was told to 'hold at intersection, watch for small aircraft Y and contact ground on 121.7.' I did not acknowledge or read back clearance since I did not see an small aircraft Y and did not now which intersection. A few seconds later tower sternly instructed to contact ground on 121.7 and to contact tower by phone. My conclusion was that the tower was looking for a chance to come down on me after screwing up earlier. 1) easterwood tower should have put on ATIS: 'numerous military lndgs and approachs in operation--caution.' 2) correct the terrible hazard of military on one frequency and civilian on another--yet with the same controller and runway. Lastly, label the txwys at easterwood like san antonio international where I am based, so you know which intersection is which.

Google
 

Original NASA ASRS Text

Title: GA SMA REFUSES GO AROUND WHEN LNDG ON A RWY THAT INTESECTED A MIL TRAINING RWY. PLT THEN MISSED TWR INSTRUCTIONS ABOUT TAXIING TO RAMP AREA.

Narrative: 15 MI OUT CONTACTED TWR AFTER LISTENING TO ATIS. TOLD TO RPT ON 2 MI RIGHT BASE TO RWY 34. I RPTED AS INSTRUCTED, AND WAS TOLD TO LAND ON RWY 28, STRAIGHT IN INSTEAD. I WAS SHOCKED TO SEE THAT I HAD BEEN DIVERTED DUE TO AN MTR ON SHORT APCH TO 34. UNTIL THEN I WAS UNAWARE OF MIL TRNING ACTIVITIES GOING ON, SINCE THEY WERE ON ANOTHER FREQ. JUST AS I WAS ABOUT TO T/D ON 28, TWR SAID, 'GO AROUND.' NOW THERE WAS ANOTHER MTR ON SHORT APCH TO 34. I RESPONDED, 'UNABLE.' COMPLETED LNDG AND STOPPED SHORT OF 34. THE MIL TRAINER WAS TOLD TO GO AROUND, AND THEY DID. IF I HAD EXECUTED A GAR, THE POTENTIAL FOR A MIDAIR WOULD HAVE OCCURRED AT INTXN. ON RWY 28, 200' FROM INTXN OF 34, I STOPPED AND ASKED FOR A 180 DEG TURN TO RETURN. I WAS CLRED FOR 180 DEG TURN. AS I DEPARTED RWY, BACKTAXIING, WAS TOLD TO 'HOLD AT INTXN, WATCH FOR SMA Y AND CONTACT GND ON 121.7.' I DID NOT ACKNOWLEDGE OR READ BACK CLRNC SINCE I DID NOT SEE AN SMA Y AND DID NOT NOW WHICH INTXN. A FEW SECS LATER TWR STERNLY INSTRUCTED TO CONTACT GND ON 121.7 AND TO CONTACT TWR BY PHONE. MY CONCLUSION WAS THAT THE TWR WAS LOOKING FOR A CHANCE TO COME DOWN ON ME AFTER SCREWING UP EARLIER. 1) EASTERWOOD TWR SHOULD HAVE PUT ON ATIS: 'NUMEROUS MIL LNDGS AND APCHS IN OPERATION--CAUTION.' 2) CORRECT THE TERRIBLE HAZARD OF MIL ON ONE FREQ AND CIVILIAN ON ANOTHER--YET WITH THE SAME CTLR AND RWY. LASTLY, LABEL THE TXWYS AT EASTERWOOD LIKE SAN ANTONIO INTL WHERE I AM BASED, SO YOU KNOW WHICH INTXN IS WHICH.

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.