Narrative:

I was notified of an incident that while I was training at R5/6/26. During the training session; neither my instructor nor I were aware of the event; however; after watching the event on falcon; we were made aware of the event and recalled details that may have led to the occurrence of the event. Aircraft X departed mia (landing central america). W174C and W465 a/B were active. Aircraft X was cleared 'direct vrgas direct tadpo rest of route unchanged' to miss W465A and issued a climb instruction to climb to FL370. As the aircraft progressed towards tadpo there was no opposite direction traffic for the aircraft; however; volume and complexity increased due to the combination of sectors and priorities happening in other areas of the sector. When aircraft X was in the vicinity of mth or just south of mth; the controller at havana center called and spoke to my d-side. As the aircraft; got closer to tadpo; I believe I asked my d-side if the radar handoff on aircraft X had been made; but I can't be sure. I do not remember if the flight progress strip had been updated with a circled 'right;' or if an 'right' had been entered into the 4th line of the flight data block. I transferred communications of aircraft X to havana center while the aircraft was still in a climb to FL370. At the same time; havana center had aircraft Y northbound toward tadpo at FL380. In accordance with the havana center/miami center LOA; the havana center controller descended aircraft Y to FL360 prior to tadpo as aircraft X crossed the center boundary. While; the two aircraft were not in immediate proximity according to miami center (7110.65) standards; havana center (in an e-mail sent to quality assurance); said that drastic action was taken to turn aircraft X; though a proximity event didn't occur. The message from havana center indicated that they had no flight plan information on the aircraft and that a handoff had not been made. My flm informed me after watching falcon that a handoff had not been made (according to the d-side and r-side recordings). During the time that aircraft X was progressing toward tadpo; several other things were happening that impeded my ability to verify the radar handoff. Several mia departures came onto the frequency after aircraft X; a military aircraft that had been operational; wanted an IFR clearance; and VFR traffic was picking up in the marathon low sector. In addition; I was in the process of trying to split the marathon low (R5) sector off amidst the calls from traffic. I recommend that since this occurred on a day of the eram test run; that someone look into why havana center received no flight plan information on aircraft X. They received information on at least two subsequent mia departures that were on my scope at the same time; but failed to identify aircraft X; which was closer to their boundary. Flight plan processing to and from havana center will need to be seamless in order to not have this occur again once eram is fully operational 24/7.

Related reports:

Google
 

Original NASA ASRS Text

Title: Two reporters are made aware of an aircraft that was not handed off after returning to work at a later date. Operational error occurred due to this issue.

Narrative: I was notified of an incident that while I was training at R5/6/26. During the training session; neither my instructor nor I were aware of the event; however; after watching the event on FALCON; we were made aware of the event and recalled details that may have led to the occurrence of the event. Aircraft X departed MIA (landing Central America). W174C and W465 A/B were active. Aircraft X was cleared 'direct VRGAS direct TADPO rest of route unchanged' to miss W465A and issued a climb instruction to climb to FL370. As the aircraft progressed towards TADPO there was no opposite direction traffic for the aircraft; however; volume and complexity increased due to the combination of sectors and priorities happening in other areas of the sector. When Aircraft X was in the vicinity of MTH or just south of MTH; the Controller at Havana Center called and spoke to my D-side. As the aircraft; got closer to TADPO; I believe I asked my D-side if the radar handoff on Aircraft X had been made; but I can't be sure. I do not remember if the flight progress strip had been updated with a circled 'R;' or if an 'R' had been entered into the 4th line of the flight data block. I transferred communications of Aircraft X to Havana Center while the aircraft was still in a climb to FL370. At the same time; Havana Center had Aircraft Y northbound toward TADPO at FL380. In accordance with the Havana Center/Miami Center LOA; the Havana Center Controller descended Aircraft Y to FL360 prior to TADPO as Aircraft X crossed the center boundary. While; the two aircraft were not in immediate proximity according to Miami Center (7110.65) standards; Havana Center (in an e-mail sent to Quality Assurance); said that drastic action was taken to turn Aircraft X; though a proximity event didn't occur. The message from Havana Center indicated that they had no flight plan information on the aircraft and that a handoff had not been made. My FLM informed me after watching FALCON that a handoff had not been made (according to the D-side and R-side recordings). During the time that Aircraft X was progressing toward TADPO; several other things were happening that impeded my ability to verify the radar handoff. Several MIA departures came onto the frequency after Aircraft X; a military aircraft that had been operational; wanted an IFR clearance; and VFR traffic was picking up in the Marathon Low sector. In addition; I was in the process of trying to split the Marathon Low (R5) sector off amidst the calls from traffic. I recommend that since this occurred on a day of the ERAM test run; that someone look into why Havana Center received no flight plan information on Aircraft X. They received information on at least two subsequent MIA departures that were on my scope at the same time; but failed to identify Aircraft X; which was closer to their boundary. Flight plan processing to and from Havana Center will need to be seamless in order to not have this occur again once ERAM is fully operational 24/7.

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