Maf controller described conflict event when he/she approved a NDB approach to runway 3 with IFR tra...

Attributes
ACN	869668
Time
Date	201001
Local Time Of Day	1801-2400
Place
Locale Reference	MAF.TRACON
State Reference	TX
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Other Instrument Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	None
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

I was assigned on R5 (sjt). I had numerous military aircraft executing practice approaches. The field was VFR and runway 18 was the active. Even though I was busy I felt that I had the situation under control. This explains why I asked for no assistance. At this time; aircraft X was holding over woole; the OM for the ILS runway 3. Meanwhile; tower requested aircraft Y runway heading off runway 18 which I approved. Then aircraft X requested to execute the NDB approach runway 3 from woole which I approved; with the assumption the aircraft X would proceed outbound on the approach. Instead aircraft X descended and proceeded inbound. Then aircraft Y came off runway 18 and separation was lost. Aircraft X reacted to his TCAS-RA and proceeded inbound to the field. Recommendation; never assume and be sure the pilot and the controller are on the same page. When it appears traffic may get congested; ask for assistance.

Original NASA ASRS Text

Title: MAF Controller described conflict event when he/she approved a NDB approach to Runway 3 with IFR traffic released from Runway 18; assuming the NDB traffic would complete the procedure turn which did not occur.

Narrative: I was assigned on R5 (SJT). I had numerous military aircraft executing practice approaches. The field was VFR and Runway 18 was the active. Even though I was busy I felt that I had the situation under control. This explains why I asked for no assistance. At this time; Aircraft X was holding over WOOLE; the OM for the ILS Runway 3. Meanwhile; Tower requested Aircraft Y runway heading off Runway 18 which I approved. Then Aircraft X requested to execute the NDB approach Runway 3 from WOOLE which I approved; with the assumption the Aircraft X would proceed outbound on the approach. Instead Aircraft X descended and proceeded inbound. Then Aircraft Y came off Runway 18 and separation was lost. Aircraft X reacted to his TCAS-RA and proceeded inbound to the field. Recommendation; never assume and be sure the pilot and the controller are on the same page. When it appears traffic may get congested; ask for assistance.

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

Maf controller described conflict event when he/she approved a NDB approach to runway 3 with IFR traffic released from runway 18; assuming the NDB traffic would complete the procedure turn which did not occur.