37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 691893 |
Time | |
Date | 200603 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | intersection : tadpo |
State Reference | FL |
Altitude | msl single value : 28000 |
Environment | |
Flight Conditions | VMC |
Weather Elements | Thunderstorm |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zma.artcc tower : hef.tower |
Operator | general aviation : corporate |
Make Model Name | Super King Air 200/Huron |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | enroute : other oceanic |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 100 flight time total : 3000 flight time type : 200 |
ASRS Report | 691893 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Events | |
Anomaly | inflight encounter : weather other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Airspace Structure ATC Human Performance FAA |
Primary Problem | Ambiguous |
Situations | |
ATC Facility | staffing : zma.artcc |
Airspace Structure | class a : zma.a |
Narrative:
We were approaching tadpo intersection. Havana center told us to contact miami on 132.7. We checked in with miami and informed them we were level FL280 and reported our estimated time to cross tadpo. We received no answer. It appeared that the controller was very busy. The frequency was very congested. We attempted to contact miami again upon crossing tadpo. Again; we received no response from miami. Several other aircraft; including airliners; also tried to check on at tadpo. The controller responded that all aircraft stand by. He said we were stepping on each other on the frequency and that he was covering 4 frequencys. We attempted to contact miami again upon crossing mth NDB; and again received no response. There was a very large line of thunderstorms on our route of flight. The worst of the storms appeared to be over or near dhp VOR which by coincidence was our next waypoint. We then continued monitoring ZMA on our assigned frequency; but we switched the transmitter over to #2 and tried contacting ZMA on guard frequency (121.5). We never received a response. We then switched the transmitter back to #1 and told ZMA that we needed a west deviation for WX. No response. We then transmitted to ZMA that if they did not acknowledge us we were going to declare an emergency. They then responded and asked if we were declaring an emergency. We responded that we were not; but that if we did not get a turn we would have no choice but to declare and deviation from our route of flight. We told ZMA that we did not even know if we were radar idented and that concerned us. ZMA then said we were radar contact; and that we needed to turn left to a heading of 270 degrees. We complied. Flew west for several mi and missed the WX by going around it. What concern me is that controller workload seems to be increasing. Covering more than 1 frequency seems to be the norm; not the exception. This is fine early morning in kansas; but on a saturated southern miami sector; when WX is pretty much everywhere; an overworked controller is a bad thing. This is a serious problem and continues to worsen.
Original NASA ASRS Text
Title: BE200 HAS DIFFICULTY ESTABLISHING COMS WITH ZMA IN THE CARIBBEAN AIRSPACE DUE TO CTLR WORKING 4 FREQS.
Narrative: WE WERE APCHING TADPO INTXN. HAVANA CTR TOLD US TO CONTACT MIAMI ON 132.7. WE CHKED IN WITH MIAMI AND INFORMED THEM WE WERE LEVEL FL280 AND RPTED OUR ESTIMATED TIME TO CROSS TADPO. WE RECEIVED NO ANSWER. IT APPEARED THAT THE CTLR WAS VERY BUSY. THE FREQ WAS VERY CONGESTED. WE ATTEMPTED TO CONTACT MIAMI AGAIN UPON XING TADPO. AGAIN; WE RECEIVED NO RESPONSE FROM MIAMI. SEVERAL OTHER ACFT; INCLUDING AIRLINERS; ALSO TRIED TO CHK ON AT TADPO. THE CTLR RESPONDED THAT ALL ACFT STAND BY. HE SAID WE WERE STEPPING ON EACH OTHER ON THE FREQ AND THAT HE WAS COVERING 4 FREQS. WE ATTEMPTED TO CONTACT MIAMI AGAIN UPON XING MTH NDB; AND AGAIN RECEIVED NO RESPONSE. THERE WAS A VERY LARGE LINE OF TSTMS ON OUR RTE OF FLT. THE WORST OF THE STORMS APPEARED TO BE OVER OR NEAR DHP VOR WHICH BY COINCIDENCE WAS OUR NEXT WAYPOINT. WE THEN CONTINUED MONITORING ZMA ON OUR ASSIGNED FREQ; BUT WE SWITCHED THE XMITTER OVER TO #2 AND TRIED CONTACTING ZMA ON GUARD FREQ (121.5). WE NEVER RECEIVED A RESPONSE. WE THEN SWITCHED THE XMITTER BACK TO #1 AND TOLD ZMA THAT WE NEEDED A W DEV FOR WX. NO RESPONSE. WE THEN XMITTED TO ZMA THAT IF THEY DID NOT ACKNOWLEDGE US WE WERE GOING TO DECLARE AN EMER. THEY THEN RESPONDED AND ASKED IF WE WERE DECLARING AN EMER. WE RESPONDED THAT WE WERE NOT; BUT THAT IF WE DID NOT GET A TURN WE WOULD HAVE NO CHOICE BUT TO DECLARE AND DEV FROM OUR RTE OF FLT. WE TOLD ZMA THAT WE DID NOT EVEN KNOW IF WE WERE RADAR IDENTED AND THAT CONCERNED US. ZMA THEN SAID WE WERE RADAR CONTACT; AND THAT WE NEEDED TO TURN L TO A HDG OF 270 DEGS. WE COMPLIED. FLEW W FOR SEVERAL MI AND MISSED THE WX BY GOING AROUND IT. WHAT CONCERN ME IS THAT CTLR WORKLOAD SEEMS TO BE INCREASING. COVERING MORE THAN 1 FREQ SEEMS TO BE THE NORM; NOT THE EXCEPTION. THIS IS FINE EARLY MORNING IN KANSAS; BUT ON A SATURATED SOUTHERN MIAMI SECTOR; WHEN WX IS PRETTY MUCH EVERYWHERE; AN OVERWORKED CTLR IS A BAD THING. THIS IS A SERIOUS PROB AND CONTINUES TO WORSEN.
Data retrieved from NASA's ASRS site as of January 2009 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.