Narrative:

This is actually two related incidents. There was an unsafe situation created by a chronic problem. According to the LOA between socal and multiple area towers; appendix 4; section 3 arrivals; (a) 2; TRACON shall transfer communications to tower no earlier than twelve (12) flying miles; but not less than seven (7) flying miles from the airport; unless otherwise coordinated. There has been a problem with approach control not switching aircraft outside of 7 miles. Most of the time; we do not receive communication from the aircraft until they are; at best; 5 miles from the airport. There have been multiple instances of aircraft not being switched to the tower until it was too late for them to avoid an airspace violation. There are many instances where an aircraft has been switched to the tower after already being in the airspace. This has been going on for a long time. There has been communication between the facilities; and after the managers have talked to each other; it gets better for a time; but always goes back to this issue. If the controllers at the TRACON would consistently transfer communication of aircraft in a timely manner; conflicts would be avoided. At this facility; we don't expect to hear from aircraft until 5 miles or less; despite what the LOA says. If we are unable to get a hold of aircraft inside of 5 miles from the airport; we call and ask the TRACON controller to attempt to switch the aircraft again. I recommend controllers at socal TRACON follow the LOA; and switch aircraft outside of 7 flying miles from the airport; not from the runway. Either that or we delete the word 'flying' from the paragraph. There's no reason to have aircraft we're supposed to control that close to our airspace and not have communication with them.

Google
 

Original NASA ASRS Text

Title: CRQ Controller voiced concern regarding the on-going failure of SCT Controller's to comply with LOA requirements with reference to the transfer of communications of VFR inbound aircraft to the Tower frequency.

Narrative: This is actually two related incidents. There was an unsafe situation created by a chronic problem. According to the LOA between SOCAL and multiple area Towers; appendix 4; section 3 Arrivals; (a) 2; TRACON Shall transfer communications to Tower no earlier than twelve (12) flying miles; but not less than seven (7) flying miles from the airport; unless otherwise coordinated. There has been a problem with Approach Control not switching aircraft outside of 7 miles. Most of the time; we do not receive communication from the aircraft until they are; at best; 5 miles from the airport. There have been multiple instances of aircraft not being switched to the Tower until it was too late for them to avoid an airspace violation. There are many instances where an aircraft has been switched to the Tower after already being in the airspace. This has been going on for a long time. There has been communication between the facilities; and after the managers have talked to each other; it gets better for a time; but always goes back to this issue. If the controllers at the TRACON would consistently transfer communication of aircraft in a timely manner; conflicts would be avoided. At this facility; we don't expect to hear from aircraft until 5 miles or less; despite what the LOA says. If we are unable to get a hold of aircraft inside of 5 miles from the airport; we call and ask the TRACON Controller to attempt to switch the aircraft again. I recommend Controllers at SOCAL TRACON follow the LOA; and switch aircraft OUTSIDE of 7 flying miles from the airport; not from the runway. Either that or we delete the word 'flying' from the paragraph. There's no reason to have aircraft we're supposed to control that close to our airspace and not have communication with them.

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.