Narrative:

This is an addition to a problem report turned in. Aircraft X departed muvr climbing to FL200; it was reported the estimate was passed to the D26 controller and entered into the system but was entered with an incorrect time. Aircraft Y departed miami and was being vectored around traffic and warning area W465A to gran cayman. Due to communications failure with havana and havana declaring non-radar operations no hand-offs were being made between the two facilities. Aircraft X was not tracked up nor did it auto acquire and a track could not be started as it was on the wrong code.aircraft passed somewhere north of the tadpo intersection both climbing possibly. Aircraft X noted the aircraft Y on TCAS and stopped their climb until the aircraft had passed and continued to their assigned altitude of FL200. Aircraft X was tracked up north of tadpo. ZMA and havana experienced a major failure of ade (data transfer) and meva the voice lines between ZMA and havana. The only form of communication was the commercial telephone at the area desk that then a call could be transferred to a phone at the D26 position. When I noted that the data system was failing I had an a-side join the sector team at R26 and once I realized that the voice lines were not working added a tracker to the position to help. Havana called for non-radar so I called tmu for a ground stop as havana was sending aircraft over to our frequency's without any information. I also called tarpon control to gain some airspace back for traffic not to all be over the same point tadpo. The military released FL240 and above to the area.the communications and data transfer failed for about 30 minutes and then came back on and off for about a half an hour. Havana had called the night before and an hour before the outage to verify our back-up phone numbers. No information I can find shows a scheduled outage of either meva or ade. An audio and video playback has not been made available to me to show my employees who were involved. I have attached an informational file to this report. My employees will file a report when they are made available to me.redraw sector R26 to reduce complex issues with arrivals and departures to havana muha and muvr as well as crossing traffic to canoa and maxim. Rework the warning areas to provide additional airways to and from havana. Set-up static restrictions for departures so all south florida airports do not run over each other out a single gate. Add an additional commercial phone with separate extension at R6. Add a separate shout line in meva for tadpo and canoa/maxim one each for R26 and R6. (Request has been made before) increase the reliability of meva and ade to avoid total failures.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMA Controller describes two fights that depart and are going towards Havana's airspace. Havana is ATC-Zero and cannot accept the aircraft. Both aircraft violate Havana's airspace and Havana tries to accept the aircraft via non-radar.

Narrative: This is an addition to a problem report turned in. Aircraft X departed MUVR climbing to FL200; it was reported the estimate was passed to the D26 controller and entered into the system but was entered with an incorrect time. Aircraft Y departed Miami and was being vectored around traffic and Warning Area W465A to Gran Cayman. Due to communications failure with Havana and Havana declaring NON-Radar operations no hand-offs were being made between the two facilities. Aircraft X was not tracked up nor did it auto acquire and a track could not be started as it was on the wrong code.Aircraft passed somewhere north of the TADPO intersection both climbing possibly. Aircraft X noted the Aircraft Y on TCAS and stopped their climb until the aircraft had passed and continued to their assigned altitude of FL200. Aircraft X was tracked up north of TADPO. ZMA and Havana experienced a major failure of ADE (data transfer) and MEVA the voice lines between ZMA and Havana. The only form of communication was the commercial telephone at the Area Desk that then a call could be transferred to a phone at the D26 position. When I noted that the DATA system was failing I had an A-side join the sector team at R26 and once I realized that the voice lines were not working added a Tracker to the position to help. Havana Called for non-radar so I called TMU for a ground stop as Havana was sending aircraft over to our frequency's without any information. I also called TARPON control to gain some airspace back for traffic not to all be over the same point TADPO. The Military released FL240 and above to the Area.The communications and data transfer failed for about 30 minutes and then came back on and off for about a half an hour. Havana had called the night before and an hour before the outage to verify our back-up phone numbers. No information I can find shows a scheduled outage of either MEVA or ADE. An audio and video playback has not been made available to me to show my employees who were involved. I have attached an informational file to this report. My employees will file a report when they are made available to me.Redraw Sector R26 to reduce complex issues with arrivals and departures to Havana MUHA and MUVR as well as crossing traffic to CANOA and MAXIM. Rework the Warning areas to provide additional airways to and from Havana. Set-up static restrictions for departures so all south Florida airports do not run over each other out a single gate. Add an additional commercial phone with separate extension at R6. Add a separate shout line in MEVA for TADPO and CANOA/MAXIM one each for R26 and R6. (Request has been made before) Increase the reliability of MEVA and ADE to avoid total failures.

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.