Narrative:

During training flight, my student and I were practicing lndgs doing touch and goes on runway 18 at mobile regional airport. After doing several touch and goes, the 'incident' occurred when we made a touch and go and on the next downwind tower told us that we had been cleared to land, he'd call our departure. We never heard this transmission and postflt discussion with the controller revealed he attempted to call us 3-4 times. He said he knew we did not answer, we didn't answer because we did not hear the call. The hazard was that a falcon jet was departing on runway 14, necessitating our full stop. Since we did not full stop, our departure paths were conflicting and the falcon had to make a hard left turn out. I realize that it is important to 'keep ears open' at tower airports however, unreliable avionics (old original radios) and the activity of flight instructing (it's usually easiest to discuss the previous landing with a student on downwind) may have conflicted when tower was attempting to contact us. During the flight, we were vigilant in responding to all our calls that we had received. Since tower knew that we did not acknowledge their radio calls, perhaps runway 14 traffic should have been held on the ground longer to assure proper separation. In the future, I will be even more vigilant in listening for radio calls and wishing the aircraft was equipped with better quality avionics. Callback conversation with reporter revealed the following information: reporter states the aircraft was a C152. This is the first time such a thing has happened to him personally. There is a very active flight school at the airport and ATC will occasionally request full stop when traffic gets busy. The falcon is a military aircraft that was also doing training. No further follow up has occurred.

Google
 

Original NASA ASRS Text

Title: INSTRUCTOR WITH STUDENT PLT FAILS TO COME TO FULL STOP LNDG. FALCON JET MAKES HARD L TURN OUT. INSTRUCTOR NOT MONITORING RADIO WHILE IN TFC PATTERN.

Narrative: DURING TRAINING FLT, MY STUDENT AND I WERE PRACTICING LNDGS DOING TOUCH AND GOES ON RWY 18 AT MOBILE REGIONAL ARPT. AFTER DOING SEVERAL TOUCH AND GOES, THE 'INCIDENT' OCCURRED WHEN WE MADE A TOUCH AND GO AND ON THE NEXT DOWNWIND TWR TOLD US THAT WE HAD BEEN CLRED TO LAND, HE'D CALL OUR DEP. WE NEVER HEARD THIS XMISSION AND POSTFLT DISCUSSION WITH THE CTLR REVEALED HE ATTEMPTED TO CALL US 3-4 TIMES. HE SAID HE KNEW WE DID NOT ANSWER, WE DIDN'T ANSWER BECAUSE WE DID NOT HEAR THE CALL. THE HAZARD WAS THAT A FALCON JET WAS DEPARTING ON RWY 14, NECESSITATING OUR FULL STOP. SINCE WE DID NOT FULL STOP, OUR DEP PATHS WERE CONFLICTING AND THE FALCON HAD TO MAKE A HARD L TURN OUT. I REALIZE THAT IT IS IMPORTANT TO 'KEEP EARS OPEN' AT TWR ARPTS HOWEVER, UNRELIABLE AVIONICS (OLD ORIGINAL RADIOS) AND THE ACTIVITY OF FLT INSTRUCTING (IT'S USUALLY EASIEST TO DISCUSS THE PREVIOUS LNDG WITH A STUDENT ON DOWNWIND) MAY HAVE CONFLICTED WHEN TWR WAS ATTEMPTING TO CONTACT US. DURING THE FLT, WE WERE VIGILANT IN RESPONDING TO ALL OUR CALLS THAT WE HAD RECEIVED. SINCE TWR KNEW THAT WE DID NOT ACKNOWLEDGE THEIR RADIO CALLS, PERHAPS RWY 14 TFC SHOULD HAVE BEEN HELD ON THE GND LONGER TO ASSURE PROPER SEPARATION. IN THE FUTURE, I WILL BE EVEN MORE VIGILANT IN LISTENING FOR RADIO CALLS AND WISHING THE ACFT WAS EQUIPPED WITH BETTER QUALITY AVIONICS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THE ACFT WAS A C152. THIS IS THE FIRST TIME SUCH A THING HAS HAPPENED TO HIM PERSONALLY. THERE IS A VERY ACTIVE FLT SCHOOL AT THE ARPT AND ATC WILL OCCASIONALLY REQUEST FULL STOP WHEN TFC GETS BUSY. THE FALCON IS A MIL ACFT THAT WAS ALSO DOING TRAINING. NO FURTHER FOLLOW UP HAS OCCURRED.

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.