Narrative:

While in cuban airspace; we had to deviate for weather. Havana asked us to fly direct to maxim which was not on our clearance. Our clearance was to fly to tadpo and then G448 to mth and the Curso2 arrival. We asked havana for the rest of the clearance and they said that mia center would provide that. 10 minutes prior to maxim; we began trying to reach mia center on 132.2. They would not answer. We could hear other aircraft as well as mia; but they would not answer us. As we approached maxim we had no clearance and were on a routing that was different from our filing. Twice we 'idented' attempting to get the controllers attention. We transmitted 'in the blind' several times. Still; nothing back from mia. At that point; as we were crossing into us airspace; without positive contact from mia; we elected to squawk 'no comm' on the transponder and proceed to waypoint curso. In our haste; we set 7500 rather than 7600. For the next several minutes we continued to try to reach mia and yet we still heard nothing from ATC. The observer pilot noticed that we were squawking 7500 rather than 7600. I looked; and he was right. We presumed that by now someone had surely noticed our squawk so we went back to our assigned squawk and continued to call mia. Finally mia responded but still did not give us a clearance. We kept trying to get one and then mia put us on a heading for sequencing. Additional radio calls from us to mia went unanswered with that controller. After we were handed off to the next controller; everything was normal.there were several contributing factors that caused this event. I believe that the primary factor was that the controller was over loaded and completely task saturated. There were several radio calls where he only partially acknowledged our transmissions and numerous calls that simply went unanswered. I'm not sure how ATC staffs or trains; but up until the point where we entered the wrong code; we believed that we were operating in compliance with SOP. It seems that there should be some monitoring of a controller when he is approaching a point of saturation so that radio calls; for more than 10 minutes; do not go unanswered; especially when entering us airspace. For us; the lesson is clear and well learned through this event - slow down; be more careful with your key strokes.

Google
 

Original NASA ASRS Text

Title: A US carrier in Cuban airspace deviated for weather and was placed a route not in the original flight plan. An apparently task saturated ZMA Controller did not respond to calls for a clearance after entering US airspace.

Narrative: While in Cuban airspace; we had to deviate for weather. Havana asked us to fly direct to MAXIM which was not on our clearance. Our clearance was to fly to TADPO and then G448 to MTH and the Curso2 Arrival. We asked Havana for the rest of the clearance and they said that MIA Center would provide that. 10 minutes prior to MAXIM; we began trying to reach MIA Center on 132.2. They would not answer. We could hear other aircraft as well as MIA; but they would not answer us. As we approached MAXIM we had no clearance and were on a routing that was different from our filing. Twice we 'idented' attempting to get the controllers attention. We transmitted 'in the blind' several times. Still; nothing back from MIA. At that point; as we were crossing into US airspace; without positive contact from MIA; we elected to squawk 'no comm' on the transponder and proceed to waypoint CURSO. In our haste; we set 7500 rather than 7600. For the next several minutes we continued to try to reach MIA and yet we still heard nothing from ATC. The observer pilot noticed that we were squawking 7500 rather than 7600. I looked; and he was right. We presumed that by now someone had surely noticed our squawk so we went back to our assigned squawk and continued to call MIA. Finally MIA responded but STILL did not give us a clearance. We kept trying to get one and then MIA put us on a heading for sequencing. Additional radio calls from us to MIA went unanswered with that controller. After we were handed off to the next controller; everything was normal.There were several contributing factors that caused this event. I believe that the primary factor was that the controller was over loaded and completely task saturated. There were several radio calls where he only partially acknowledged our transmissions and numerous calls that simply went unanswered. I'm not sure how ATC staffs or trains; but up until the point where we entered the wrong code; we believed that we were operating in compliance with SOP. It seems that there should be some monitoring of a controller when he is approaching a point of saturation so that radio calls; for more than 10 minutes; do not go unanswered; especially when entering US airspace. For us; the lesson is clear and well learned through this event - slow down; be more careful with your key strokes.

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.