Tower controller described a runway separation infraction when IFR inbound traffic was issued a late...

Narrative:

Citationjet was an IFR arrival on visual approach to runway xxl. The local controller took the automated handoff from [the TRACON] and then waited for the aircraft to call on frequency. Then there was a low altitude alert and [the TRACON] called and told us to issue it. Local control [local control] told [the TRACON] we weren't talking to him. The aircraft continued to come in towards the airport. He was opposite direction to LC2's downwind traffic. LC2 had to start moving aircraft out of the citation's way. LC1 continued to try and contact the citation. I called [the TRACON] and told them we were still not talking to the aircraft and that he may go around because he didn't have a landing clearance; and they told me they had already switched him. This is not uncommon for [the TRACON] to give late frequency changes to IFR arrivals; so we were not completely concerned until the aircraft was on a 1 mile final and still could not be contacted. LC1 then realized this was a problem and had to concentrate on getting a previous arrival off the runway before the citation crossed the threshold. It was a tight squeeze. I was busy watching this close situation. LC2 was watching the situation and working their moderate traffic. The citation landed and then rolled out to taxiway a; exited and contacted me on ground control. I questioned him about whether he had radio issues and then issued a brasher statement. Later after management had listened to tapes; it was discovered that [the TRACON] had given the aircraft the wrong frequency per the LOA. [The TRACON] does this frequently. It was also discovered that the citation had called in on the wrong frequency which was LC2. LC2 must not have heard it because they were busy moving aircraft out of the citation's way. [The TRACON] caused the whole series of events by not following the LOA and we were complacent caused by [the TRACON's] routine late frequency changes; waiting too long with no time to do the things that were suggested. My recommendation is to come down hard on the TRACON and give them all remedial training on the LOA.

Original NASA ASRS Text

Title: Tower Controller described a runway separation infraction when IFR inbound traffic was issued a late frequency change by the TRACON and landed without clearance; the reporter listed LOA non-compliance as a factor.

Narrative: Citationjet was an IFR arrival on visual approach to Runway XXL. The Local Controller took the automated handoff from [the TRACON] and then waited for the aircraft to call on frequency. Then there was a low altitude alert and [the TRACON] called and told us to issue it. Local Control [LC] told [the TRACON] we weren't talking to him. The aircraft continued to come in towards the airport. He was opposite direction to LC2's downwind traffic. LC2 had to start moving aircraft out of the Citation's way. LC1 continued to try and contact the Citation. I called [the TRACON] and told them we were still not talking to the aircraft and that he may go around because he didn't have a landing clearance; and they told me they had already switched him. This is not uncommon for [the TRACON] to give late frequency changes to IFR arrivals; so we were not completely concerned until the aircraft was on a 1 mile final and still could not be contacted. LC1 then realized this was a problem and had to concentrate on getting a previous arrival off the runway before the Citation crossed the threshold. It was a tight squeeze. I was busy watching this close situation. LC2 was watching the situation and working their moderate traffic. The Citation landed and then rolled out to Taxiway A; exited and contacted me on Ground Control. I questioned him about whether he had radio issues and then issued a Brasher Statement. Later after management had listened to tapes; it was discovered that [the TRACON] had given the aircraft the wrong frequency per the LOA. [The TRACON] does this frequently. It was also discovered that the Citation had called in on the wrong frequency which was LC2. LC2 must not have heard it because they were busy moving aircraft out of the Citation's way. [The TRACON] caused the whole series of events by not following the LOA and we were complacent caused by [the TRACON's] routine late frequency changes; waiting too long with no time to do the things that were suggested. My recommendation is to come down hard on the TRACON and give them all remedial training on the LOA.

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

Attributes
ACN	1105543
Time
Date	201307
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Citationjet (C525/C526) - CJ I / II / III / IV
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Ground
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Local
Qualification	Air Traffic Control Developmental
Events
Anomaly	ATC Issue All Types Deviation - Procedural Landing Without Clearance Deviation - Procedural Published Material / Policy

Tower controller described a runway separation infraction when IFR inbound traffic was issued a late frequency change by the TRACON and landed without clearance; the reporter listed LOA non-compliance as a factor.