37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1582920 |
Time | |
Date | 201810 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZHU.ARTCC |
State Reference | TX |
Aircraft 1 | |
Make Model Name | PC-12 |
Operating Under FAR Part | Part 135 |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Helicopter |
Flight Phase | Climb |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
Person 2 | |
Function | Single Pilot Captain |
Qualification | Flight Crew Multiengine Flight Crew Commercial Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 56 Flight Crew Total 1760 Flight Crew Type 56 |
Events | |
Anomaly | Conflict NMAC |
Narrative:
Aircraft X was inbound to laredo airport direct IAF ovose on the rnv 18R at lrd. The aircraft was cleared to maintain 030 ft until established and cleared for the approach. About 5 miles from ovose; my trainee saw traffic with a beacon XXXX maneuvering in the area of ovose at 018 and called traffic to aircraft X. He said targets appear likely to merge. At that point the XXXX code turned [towards] aircraft X and climbed rapidly to 031. I then canceled the approach clearance of aircraft X and turned the aircraft 30 degrees right and issued a traffic alert. Aircraft X then called the unknown aircraft Y in sight; and said that it was a close one. At that point I asked aircraft X if they were time critical; and when learning they were not; I extended the aircraft vectors to make sure the unknown code XXXX would not be an issue again. Laredo tower was not in communication with aircraft Y; and when he finally did go to laredo to land; I had the tower give that aircraft our phone number to call. Aircraft X company called the supervisor and told him that aircraft Y was less than 200 ft from him same altitude; and that the pilot didn't see aircraft Y until he started the turn and banked away from it.I strongly insist that if there are border aircraft near or in the vicinity of lrd; that they monitor the frequency and let us know they are there. That way this situation won't happen.
Original NASA ASRS Text
Title: Houston Center Controller and an Air Taxi reported a NMAC with an aircraft not communicating with ATC.
Narrative: Aircraft X was inbound to Laredo airport direct IAF OVOSE on the RNV 18R at LRD. The aircraft was cleared to maintain 030 ft until established and cleared for the approach. About 5 miles from OVOSE; my trainee saw traffic with a beacon XXXX maneuvering in the area of OVOSE at 018 and called traffic to Aircraft X. He said targets appear likely to merge. At that point the XXXX code turned [towards] Aircraft X and climbed rapidly to 031. I then canceled the approach clearance of Aircraft X and turned the aircraft 30 degrees right and issued a traffic alert. Aircraft X then called the unknown Aircraft Y in sight; and said that it was a close one. At that point I asked Aircraft X if they were time critical; and when learning they were not; I extended the aircraft vectors to make sure the unknown code XXXX would not be an issue again. Laredo tower was not in communication with Aircraft Y; and when he finally did go to Laredo to land; I had the tower give that aircraft our phone number to call. Aircraft X company called the supervisor and told him that Aircraft Y was less than 200 ft from him same altitude; and that the pilot didn't see Aircraft Y until he started the turn and banked away from it.I strongly insist that if there are border aircraft near or in the vicinity of LRD; that they monitor the frequency and let us know they are there. That way this situation won't happen.
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.