Air carrier X had airborne conflict with aircraft Y. See and avoid concept.

Attributes
ACN	138526
Time
Date	199003
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : shv
State Reference	LA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : shv
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 3400 flight time type : 1000
ASRS Report	138526
Person 2
Function	flight crew : single pilot
Events
Anomaly	conflict : airborne less severe
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Miss Distance	horizontal : 2500 vertical : 0
Supplementary
Air Traffic Incident	other

Narrative:

All approach segments and communications were normal with act. Air carrier X asked for a visibility runway 23 at shv (runway 14 was in use, but winds were 150/06, which is compatible). We checked in with second controller (119.9) and indicated heading (290 degrees) and altitude (3000'), which was assigned and again requested visibility 23. 'Roger,' was the reply. At approximately 20 mi from the field we saw the airport and called to the controller that it was in sight. The controller indicated to us to maintain 3000' for air carrier Y, which was at 1:30 and 3 mi, level at 3000'. We asked again about our altitude (we were still at 3000' since we were not cleared lower) since the traffic was also reported at 3000' by the time she replied, we saw our traffic, which was now at 11 O'clock and less than 1/2 mi at our altitude. Shv approach is always busy with military traffic that sometimes civ traffic is forgotten about. This is one of the more dangerous incidents I've been involved in. Many times I've been ignored due to military congestion. Recommend another controller to handle UHF traffic strictly and VHF controller to coordinate with UHF controller.

Original NASA ASRS Text

Title: ACR X HAD AIRBORNE CONFLICT WITH ACFT Y. SEE AND AVOID CONCEPT.

Narrative: ALL APCH SEGMENTS AND COMS WERE NORMAL WITH ACT. ACR X ASKED FOR A VIS RWY 23 AT SHV (RWY 14 WAS IN USE, BUT WINDS WERE 150/06, WHICH IS COMPATIBLE). WE CHKED IN WITH SECOND CTLR (119.9) AND INDICATED HDG (290 DEGS) AND ALT (3000'), WHICH WAS ASSIGNED AND AGAIN REQUESTED VIS 23. 'ROGER,' WAS THE REPLY. AT APPROX 20 MI FROM THE FIELD WE SAW THE ARPT AND CALLED TO THE CTLR THAT IT WAS IN SIGHT. THE CTLR INDICATED TO US TO MAINTAIN 3000' FOR ACR Y, WHICH WAS AT 1:30 AND 3 MI, LEVEL AT 3000'. WE ASKED AGAIN ABOUT OUR ALT (WE WERE STILL AT 3000' SINCE WE WERE NOT CLRED LOWER) SINCE THE TFC WAS ALSO RPTED AT 3000' BY THE TIME SHE REPLIED, WE SAW OUR TFC, WHICH WAS NOW AT 11 O'CLOCK AND LESS THAN 1/2 MI AT OUR ALT. SHV APCH IS ALWAYS BUSY WITH MIL TFC THAT SOMETIMES CIV TFC IS FORGOTTEN ABOUT. THIS IS ONE OF THE MORE DANGEROUS INCIDENTS I'VE BEEN INVOLVED IN. MANY TIMES I'VE BEEN IGNORED DUE TO MIL CONGESTION. RECOMMEND ANOTHER CTLR TO HANDLE UHF TFC STRICTLY AND VHF CTLR TO COORDINATE WITH UHF CTLR.

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