Mlu controller experienced a loss of separation event during cenrap operations; noting the need for ...

Narrative:

I was informed that my manager is investigating 3 operational errors involving my session on radar. This is one of them; a citation was heading 320 off of runway 4; climbing to 12;000; the aircraft came onto my screen from the (more than 40 miles away) west descending to 13;000. When the citation was inside 2 1/2 miles from shreveport's airspace boundary; I descended it to 5;000. I told the citation; (heading 320); to report leaving 5000' so that I would have an idea of when I should see him in cenrap (center radar ARTS presentation). I then turned the citation left to a 270 heading. Right after; I saw what appeared to be his beacon code and altitude so I told him to 'identify' and radar identified him. The citation was cleared direct sabar; the OM 4 miles south of the mlu airport. The aircraft were more than 20 miles apart and I considered aircraft performance in my decision to turn the citation to the west. Recommendation; mlu does not go 'cenrap' often enough to keep everyone current on non-radar rules and separation. No one seems to have a clear idea of how to apply non-radar rules here other than 'one in; one out' of the airspace. This is not practical when the airspace is up to 12;000' and has a 30-40 mile radius. I made it known before I took position that I needed to review the non-radar rules and I was told; 'oh; the separation just increases from 3 to 5 miles and local has to call radar for IFR release'. I should know the non-radar rules. But I admit that; rarely working non-radar; I am not as proficient as I would like to be.

Original NASA ASRS Text

Title: MLU Controller experienced a loss of separation event during CENRAP operations; noting the need for training in the use of this rarely used procedure.

Narrative: I was informed that my manager is investigating 3 operational errors involving my session on RADAR. This is one of them; a Citation was heading 320 off of Runway 4; climbing to 12;000; the aircraft came onto my screen from the (more than 40 miles away) west descending to 13;000. When the Citation was inside 2 1/2 miles from Shreveport's airspace boundary; I descended it to 5;000. I told the Citation; (heading 320); to report leaving 5000' so that I would have an idea of when I should see him in CENRAP (Center Radar ARTS Presentation). I then turned the Citation left to a 270 heading. Right after; I saw what appeared to be his beacon code and altitude so I told him to 'IDENT' and RADAR identified him. The Citation was cleared direct SABAR; the OM 4 miles south of the MLU airport. The aircraft were more than 20 miles apart and I considered aircraft performance in my decision to turn the Citation to the west. Recommendation; MLU does not go 'CENRAP' often enough to keep everyone current on NON-RADAR rules and separation. No one seems to have a clear idea of how to apply NON-RADAR rules here other than 'one in; one out' of the airspace. This is not practical when the airspace is up to 12;000' and has a 30-40 mile radius. I made it known before I took position that I needed to review the NON-RADAR rules and I was told; 'oh; the separation just increases from 3 to 5 miles and Local has to call RADAR for IFR release'. I should know the NON-RADAR rules. But I admit that; rarely working NON-RADAR; I am not as proficient as I would like to be.

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.

Attributes
ACN	882918
Time
Date	201004
Local Time Of Day	1201-1800
Place
Locale Reference	MLU.Airport
State Reference	LA
Aircraft 1
Make Model Name	Cessna Citation Undifferentiated or Other Model
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Departure Flight Data / Clearance Delivery Approach Coordinator
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Departure Approach
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Mlu controller experienced a loss of separation event during cenrap operations; noting the need for training in the use of this rarely used procedure.