Narrative:

I was on ground control. Tpa has an east/west runway that ground control owns and has to relinquish control to the local controller if they want to use the runway either for a vehicle or arriving/departing aircraft. I was taxing aircraft on the taxiways intersecting the runway and all of a sudden I hear 'runway 28 back to you.' the local controller had used it for a vehicle and never requested to take the runway from me to begin with.I was irritated but I let it slide since this controller in known for cutting corners; slacking; having deals; becoming un-certified from sectors; and overall not caring. It wasn't worth the argument. However; 5 minutes later we have [an aircraft] back to tpa. The tower only owns 1;600 feet AGL and the [aircraft] was IFR cleared initially to 3;000 feet. The [aircraft] departs and wants one turn in the pattern. The local controller does not amend his altitude; lets him climb to 3000 feet and puts him in right traffic. I asked if the radar sector was watching [aircraft] as he egregiously busted that airspace. Of course; he had not done his job by pointing him out or amending his altitude.the most dangerous thing in this situation is; directly over tpa we have 'the bridge' which is a corridor where we put IFR and VFR traffic overflying tpa at 2500 feet 4000 feet AGL. This [aircraft] could have flown through a 2500 foot VFR aircraft or gotten to close to a 3000 foot IFR aircraft or worst case scenario actually have a mid-air. Something has to be done about this controller. How many deals; SOP/LOA violations is someone allowed to receive before actually causing a situation that can have disastrous effects. This [aircraft] still being IFR was not pointed out to the final controller who has sole responsibility of sequencing all arrival traffic and maintaining separation. Two airspace violations happened and two point outs were not completed in this situation.

Google
 

Original NASA ASRS Text

Title: A Tower Controller observed the Local Controller allow an aircraft to fly in the Tower traffic pattern at an altitude in the TRACON's airspace without coordinating with the TRACON.

Narrative: I was on ground control. TPA has an east/west runway that Ground control owns and has to relinquish control to the local controller if they want to use the runway either for a vehicle or arriving/departing aircraft. I was taxing aircraft on the taxiways intersecting the runway and all of a sudden I hear 'runway 28 back to you.' The local controller had used it for a vehicle and never requested to take the runway from me to begin with.I was irritated but I let it slide since this controller in known for cutting corners; slacking; having deals; becoming UN-certified from sectors; and overall not caring. It wasn't worth the argument. However; 5 minutes later we have [an aircraft] back to TPA. The tower only owns 1;600 feet AGL and the [aircraft] was IFR cleared initially to 3;000 feet. The [aircraft] departs and wants one turn in the pattern. The local controller does not amend his altitude; lets him climb to 3000 feet and puts him in right traffic. I asked if the radar sector was watching [aircraft] as he egregiously busted that airspace. Of course; he had not done his job by pointing him out or amending his altitude.The most dangerous thing in this situation is; directly over TPA we have 'the bridge' which is a corridor where we put IFR and VFR traffic overflying TPA at 2500 feet 4000 feet AGL. This [aircraft] could have flown through a 2500 foot VFR aircraft or gotten to close to a 3000 foot IFR aircraft or worst case scenario actually have a mid-air. Something has to be done about this controller. How many deals; SOP/LOA violations is someone allowed to receive before actually causing a situation that can have disastrous effects. This [aircraft] still being IFR was not pointed out to the final controller who has sole responsibility of sequencing all arrival traffic and maintaining separation. Two airspace violations happened and two Point Outs were not completed in this situation.

Data retrieved from NASA's ASRS site 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.