ZMA controller experienced operational error at FL340 when attempting to provide in trail separation to 2 aircraft received 'stacked' from another sector.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	680781
Time
Date	200512
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : orl.airport
State Reference	FL
Altitude	msl bound lower : 24000 msl single value : 34000
Aircraft 1
Controlling Facilities	artcc : zma.artcc tower : ord.tower
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zma.artcc
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	cruise : level descent : approach
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Experience	controller limited radar : 4.5 controller radar : 2.5 controller time certified in position1 : 2 controller time certified in position2 : 10
ASRS Report	680781
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 12000 flight time type : 1500
ASRS Report	680898
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued alert controller : issued new clearance flight crew : took evasive action
Consequence	faa : investigated
Miss Distance	horizontal : 18200 vertical : 0
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

I was working R2 by myself. In the north part of the sector where the new airways for the different arrs are very close together; we received 2 pbi arrs from jax stacked. I'm required to give a minimum of 5 mi to the next controller. To accomplish this; I turned air carrier X level at FL340 to a 240 degree heading. I had a northbound aircraft at FL330 whose data block overlapped air carrier Y's data block. I thought air carrier Y was level at FL350. With the added distraction of calling jax repeatedly for a NORDO aircraft; I missed that air carrier X and air carrier Y were traffic. When I realized this; I turned air carrier X to a 120 degree heading and air carrier Y to a 270 degree heading and descended air carrier X to FL240. This was too late to ensure separation. This situation may have been avoided if ZJX would have provided in trail separation to aircraft landing to the same airport.

Original NASA ASRS Text

Title: ZMA CTLR EXPERIENCED OPERROR AT FL340 WHEN ATTEMPTING TO PROVIDE IN TRAIL SEPARATION TO 2 ACFT RECEIVED 'STACKED' FROM ANOTHER SECTOR.

Narrative: I WAS WORKING R2 BY MYSELF. IN THE N PART OF THE SECTOR WHERE THE NEW AIRWAYS FOR THE DIFFERENT ARRS ARE VERY CLOSE TOGETHER; WE RECEIVED 2 PBI ARRS FROM JAX STACKED. I'M REQUIRED TO GIVE A MINIMUM OF 5 MI TO THE NEXT CTLR. TO ACCOMPLISH THIS; I TURNED ACR X LEVEL AT FL340 TO A 240 DEG HDG. I HAD A NBOUND ACFT AT FL330 WHOSE DATA BLOCK OVERLAPPED ACR Y'S DATA BLOCK. I THOUGHT ACR Y WAS LEVEL AT FL350. WITH THE ADDED DISTR OF CALLING JAX REPEATEDLY FOR A NORDO ACFT; I MISSED THAT ACR X AND ACR Y WERE TFC. WHEN I REALIZED THIS; I TURNED ACR X TO A 120 DEG HDG AND ACR Y TO A 270 DEG HDG AND DSNDED ACR X TO FL240. THIS WAS TOO LATE TO ENSURE SEPARATION. THIS SITUATION MAY HAVE BEEN AVOIDED IF ZJX WOULD HAVE PROVIDED IN TRAIL SEPARATION TO ACFT LNDG TO THE SAME ARPT.

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.