ZMA controllers described a loss of separation event occurring shortly after sector positions were s...

Narrative:

I was working the D3 position. Aside from being very short staffed; I was approaching 2 hours on position without a break. The sector was getting busy; I asked for them to split the sector; and the supervisor told me he had paged someone back to open up sector 4. When sector 4 was opened; the r-side at sector 3 was way too busy to give a position relief briefing; so I did it as the d-side; which is a common practice. Upon giving the traffic; the R4 controller accepted a point out on aircraft X who was level at 6;000 ft but landed kfpr; and would be descending into our altitude stratum shortly. Aircraft X was previously NORDO. The R3 controller shipped aircraft Y (5;000 ft) to sector 4 and dropped the data block while I was off line coordinating and updating my suspense bay. Conflict alert drew my attention back to the scope; where I saw aircraft X descending to 4;000 ft and was then turned to a 090 [degree] heading by the R3 controller. Recommendation: split sectors [in a] timely [manner] to prevent one sector from blowing up as quick as it did.

Original NASA ASRS Text

Title: ZMA Controllers described a loss of separation event occurring shortly after sector positions were split; the reports listing briefing procedures and late de-combining as causal factors.

Narrative: I was working the D3 position. Aside from being very short staffed; I was approaching 2 hours on position without a break. The sector was getting busy; I asked for them to split the sector; and the supervisor told me he had paged someone back to open up Sector 4. When Sector 4 was opened; the R-Side at Sector 3 was way too busy to give a position relief briefing; so I did it as the D-Side; which is a common practice. Upon giving the traffic; the R4 Controller accepted a point out on Aircraft X who was level at 6;000 FT but landed KFPR; and would be descending into our altitude stratum shortly. Aircraft X was previously NORDO. The R3 Controller shipped Aircraft Y (5;000 FT) to Sector 4 and dropped the data block while I was off line coordinating and updating my suspense bay. Conflict Alert drew my attention back to the scope; where I saw Aircraft X descending to 4;000 FT and was then turned to a 090 [degree] heading by the R3 Controller. Recommendation: split sectors [in a] timely [manner] to prevent one sector from blowing up as quick as it did.

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	925038
Time
Date	201012
Local Time Of Day	1201-1800
Place
Locale Reference	ZMA.ARTCC
State Reference	FL
Aircraft 1
Make Model Name	Baron 55/Cochise
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Socata (Aerospatiale) Undifferentiated or Other Model
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Person 2
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

ZMA controllers described a loss of separation event occurring shortly after sector positions were split; the reports listing briefing procedures and late de-combining as causal factors.