Narrative:

Aircraft X; checked in with me northwest of tix at 6;000. I pointed the aircraft out to stv. They accepted the point out; so I instructed them to descend to 3;000; and proceed direct tix. I took care of other tasks. When I made my next transmission to aircraft X; I informed them that the airport was 12 o'clock; and 12 miles; report the airport in sight. If you look at the falcon replay; the airport is exactly 12 miles away at their 12 o'clock. Aircraft X reported the airport in sight. I cleared them for the visual approach to runway 18 and immediately switched them to the tower. I received a correct read back; and continued onto other duties. As I was scanning; I saw aircraft X make a turn to the east to line up for runway 18 at tix; and a conflict alert went off for them and an untagged target that was southeast of them and over a 1;000 feet below them. Then I moved onto ensuring that an aircraft departing mlb flashed at the appropriate ZMA sector. Tix tower called me on the line and advised me it appeared that aircraft X had landed at arthur dunn airpark (X21). At that time I advised the supervisor on the floor what had occurred. I went on break; upon returning from break; management advised me that indeed aircraft X did in fact land at arthur dunn airpark. We need our stars brought up to par. This is a known issue in this facility. There was never a low altitude alert for this aircraft. The airport they landed at was 6 miles short of tix. That is unacceptable. The handoffs do not flash correctly; that's why I was ensuring that the mlb departure flashed to the correct ZMA sector. It is also a known problem with our stars; that the conflict alert isn't working correctly. We routinely get conflict alerts after targets have passed each other. Stars at F11 definitely contributed to this event. Please have a stars subject matter experts come to orlando and fix our stars.

Google
 

Original NASA ASRS Text

Title: A TRACON Controller reported a TBM7 on a visual approach to TIX; landed at X21 in error; additionally; the system failed to trigger a low altitude alert; which is a reoccurring problem.

Narrative: Aircraft X; checked in with me northwest of TIX at 6;000. I pointed the aircraft out to STV. They accepted the point out; so I instructed them to descend to 3;000; and proceed direct TIX. I took care of other tasks. When I made my next transmission to Aircraft X; I informed them that the airport was 12 o'clock; and 12 miles; report the airport in sight. If you look at the falcon replay; the airport is exactly 12 miles away at their 12 o'clock. Aircraft X reported the airport in sight. I cleared them for the visual approach to Runway 18 and immediately switched them to the tower. I received a correct read back; and continued onto other duties. As I was scanning; I saw Aircraft X make a turn to the east to line up for Runway 18 at TIX; and a Conflict Alert went off for them and an untagged target that was southeast of them and over a 1;000 feet below them. Then I moved onto ensuring that an aircraft departing MLB flashed at the appropriate ZMA sector. TIX tower called me on the line and advised me it appeared that Aircraft X had landed at Arthur Dunn Airpark (X21). At that time I advised the supervisor on the floor what had occurred. I went on break; upon returning from break; management advised me that indeed Aircraft X did in fact land at Arthur Dunn Airpark. We need our STARS brought up to par. This is a known issue in this facility. There was never a low altitude alert for this aircraft. The airport they landed at was 6 miles short of TIX. That is unacceptable. The handoffs do not flash correctly; that's why I was ensuring that the MLB departure flashed to the correct ZMA sector. It is also a known problem with our STARS; that the conflict alert isn't working correctly. We routinely get conflict alerts after targets have passed each other. STARS at F11 definitely contributed to this event. Please have a STARS Subject Matter Experts come to Orlando and fix our STARS.

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.