P51 controller described conflict when ndz gca controller failed to utilized appropriate measures in...

Attributes
ACN	741049
Time
Date	200706
Place
Locale Reference	airport : ndz.airport
State Reference	FL
Altitude	msl single value : 1700
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : p31.tracon tower : ndz.tower
Operator	other
Make Model Name	Military
Flight Phase	landing : missed approach landing : go around
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : p31.tracon tower : ndz.tower
Operator	other
Make Model Name	Military
Flight Phase	landing : go around landing : missed approach
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 19 controller time certified in position1 : 7 flight time total : 350
ASRS Report	741049
Person 2
Affiliation	government : military
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

I was working the ndz arrival/departure sector at P31. Aircraft X was just handed off to me from ndz gca climbing to 1700 ft MSL heading 220 degrees. Ndz gca tried to hand another aircraft to me heading 220 degrees climbing to 1700 ft MSL. I initiated the call and refused the handoff. I told the ndz gca to put air carrier Y on a 270 degree heading for separation. The 2 aircraft were less than 3 NM apart within 1000 ft vertical and closing. The controller at ndz gca did not understand basic IFR separation. The controller at ndz gca stated 'that is our procedure.' if I would have taken the handoff; I would have been charged with loss of separation; this is a setup! If ndz gca procedures dictate to have loss of separation and pass it on to the next controller then ndz/gca procedures are extremely flawed. Fix: ndz gca procedures need to be reevaluated/changed to provide standard separation as soon as possible. Note: P31 has had numerous conflicts with IFR departures off of ndz and approachs that are arriving/missed approach off of ndz.

Original NASA ASRS Text

Title: P51 CTLR DESCRIBED CONFLICT WHEN NDZ GCA CTLR FAILED TO UTILIZED APPROPRIATE MEASURES IN ENSURE SEPARATION.

Narrative: I WAS WORKING THE NDZ ARR/DEP SECTOR AT P31. ACFT X WAS JUST HANDED OFF TO ME FROM NDZ GCA CLBING TO 1700 FT MSL HDG 220 DEGS. NDZ GCA TRIED TO HAND ANOTHER ACFT TO ME HDG 220 DEGS CLBING TO 1700 FT MSL. I INITIATED THE CALL AND REFUSED THE HDOF. I TOLD THE NDZ GCA TO PUT ACR Y ON A 270 DEG HDG FOR SEPARATION. THE 2 ACFT WERE LESS THAN 3 NM APART WITHIN 1000 FT VERT AND CLOSING. THE CTLR AT NDZ GCA DID NOT UNDERSTAND BASIC IFR SEPARATION. THE CTLR AT NDZ GCA STATED 'THAT IS OUR PROC.' IF I WOULD HAVE TAKEN THE HDOF; I WOULD HAVE BEEN CHARGED WITH LOSS OF SEPARATION; THIS IS A SETUP! IF NDZ GCA PROCS DICTATE TO HAVE LOSS OF SEPARATION AND PASS IT ON TO THE NEXT CTLR THEN NDZ/GCA PROCS ARE EXTREMELY FLAWED. FIX: NDZ GCA PROCS NEED TO BE REEVALUATED/CHANGED TO PROVIDE STANDARD SEPARATION ASAP. NOTE: P31 HAS HAD NUMEROUS CONFLICTS WITH IFR DEPS OFF OF NDZ AND APCHS THAT ARE ARRIVING/MISSED APCH OFF OF NDZ.

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

P51 controller described conflict when ndz gca controller failed to utilized appropriate measures in ensure separation.