Narrative:

Fgt X, flight of 2 fgt's departed homestead AFB at approximately xx:xx local time, on a standard instrument departure. I cleared the aircraft to climb to a block altitude of FL210-230. Approximately 1 min after departure, the homestead sector controller at ZMA called and asked me to stop fgt X at a block of 17000'-FL190, and clear the flight direct ruby/topaz, a fix on the mission profile. I acknowledged the call, and cleared fgt X direct to ruby/topaz, but did not issue altitude restriction. I also failed to transfer communication of fgt X to ZMA. Fgt X leveled at FL230 and came within 3.8 mi latitude, and 200' vertical, of another fgt at FL230. ZMA called and instructed me to descend fgt X immediately to FL190, which I did. The pilot then reported the other aircraft in sight. I immediately notified my supervisor. Until I listened to the tape recording of the incident, I was convinced that the center controller had erred. I could not remember the center controller issuing an altitude restriction and I would have sworn he had not. However, upon listening to the tape I realized I was entirely at fault. Fortunately the center controller was on the ball and called for the immediate descent. Contributing factors: 1) I was very tired from a long drive I had taken on my 2-DAY break. 2) I was working 4 positions combined--2 radar positions and 2 handoff positions. 3) I was very busy--numerous aircraft departing homestead and miami. Practice approach at tamiami airport, and 2 aircraft with transponder problems. I estimate I had 8 aircraft on frequency, with numerous landline calls also taking place. I believe this error occurred primarily due to my fatigue and lack of concentration. The fact that it was busy and I had 4 positions combined was only a minor contribution. It bothers me tremendously that I cannot recall the center controller's altitude restriction.

Related reports:

Google
 

Original NASA ASRS Text

Title: ALT RESTRICTION NOT ISSUED CAUSING AN FGT TO CLIMB TO AN ALT THAT CONFLICTED WITH ANOTHER FGT.

Narrative: FGT X, FLT OF 2 FGT'S DEPARTED HOMESTEAD AFB AT APPROX XX:XX LCL TIME, ON A STANDARD INSTRUMENT DEP. I CLRED THE ACFT TO CLB TO A BLOCK ALT OF FL210-230. APPROX 1 MIN AFTER DEP, THE HOMESTEAD SECTOR CTLR AT ZMA CALLED AND ASKED ME TO STOP FGT X AT A BLOCK OF 17000'-FL190, AND CLR THE FLT DIRECT RUBY/TOPAZ, A FIX ON THE MISSION PROFILE. I ACKNOWLEDGED THE CALL, AND CLRED FGT X DIRECT TO RUBY/TOPAZ, BUT DID NOT ISSUE ALT RESTRICTION. I ALSO FAILED TO TRANSFER COM OF FGT X TO ZMA. FGT X LEVELED AT FL230 AND CAME WITHIN 3.8 MI LAT, AND 200' VERT, OF ANOTHER FGT AT FL230. ZMA CALLED AND INSTRUCTED ME TO DSND FGT X IMMEDIATELY TO FL190, WHICH I DID. THE PLT THEN RPTED THE OTHER ACFT IN SIGHT. I IMMEDIATELY NOTIFIED MY SUPVR. UNTIL I LISTENED TO THE TAPE RECORDING OF THE INCIDENT, I WAS CONVINCED THAT THE CENTER CTLR HAD ERRED. I COULD NOT REMEMBER THE CENTER CTLR ISSUING AN ALT RESTRICTION AND I WOULD HAVE SWORN HE HAD NOT. HOWEVER, UPON LISTENING TO THE TAPE I REALIZED I WAS ENTIRELY AT FAULT. FORTUNATELY THE CENTER CTLR WAS ON THE BALL AND CALLED FOR THE IMMEDIATE DSCNT. CONTRIBUTING FACTORS: 1) I WAS VERY TIRED FROM A LONG DRIVE I HAD TAKEN ON MY 2-DAY BREAK. 2) I WAS WORKING 4 POSITIONS COMBINED--2 RADAR POSITIONS AND 2 HDOF POSITIONS. 3) I WAS VERY BUSY--NUMEROUS ACFT DEPARTING HOMESTEAD AND MIAMI. PRACTICE APCH AT TAMIAMI ARPT, AND 2 ACFT WITH XPONDER PROBS. I ESTIMATE I HAD 8 ACFT ON FREQ, WITH NUMEROUS LANDLINE CALLS ALSO TAKING PLACE. I BELIEVE THIS ERROR OCCURRED PRIMARILY DUE TO MY FATIGUE AND LACK OF CONCENTRATION. THE FACT THAT IT WAS BUSY AND I HAD 4 POSITIONS COMBINED WAS ONLY A MINOR CONTRIBUTION. IT BOTHERS ME TREMENDOUSLY THAT I CANNOT RECALL THE CENTER CTLR'S ALT RESTRICTION.

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