Narrative:

Were being vectored for visual approach to runway 36L at dfw, arrival from northwest. Extreme frequency congestion with only one controller on approach handling all those finals. Controller turned us to heading 030 degrees, maintain 3000 ft, and then forgot about us. Due to the frequency congestion, we could not get in a word. So because we had been told to expect a visual to runway 36L, we turned onto the final approach course and eventually began descent. Below 3000 ft to 2600 ft, but then elected to go around when we were unable to get a clearance to land or for the approach. Had we maintained the heading and altitude we definitely would have caused a traffic conflict. A call to the facility confirmed that the controller got swamped.

Google
 

Original NASA ASRS Text

Title: THE FLC OF AN ACR TURNED TO FINAL ON THEIR OWN AND SUBSEQUENTLY MADE A GAR DUE TO TFC CONGESTION AND NOT BEING ABLE TO OBTAIN LNDG CLRNC. RPTR WAS FORGOTTEN BY ATC ON BASE LEG!

Narrative: WERE BEING VECTORED FOR VISUAL APCH TO RWY 36L AT DFW, ARR FROM NW. EXTREME FREQ CONGESTION WITH ONLY ONE CTLR ON APCH HANDLING ALL THOSE FINALS. CTLR TURNED US TO HDG 030 DEGS, MAINTAIN 3000 FT, AND THEN FORGOT ABOUT US. DUE TO THE FREQ CONGESTION, WE COULD NOT GET IN A WORD. SO BECAUSE WE HAD BEEN TOLD TO EXPECT A VISUAL TO RWY 36L, WE TURNED ONTO THE FINAL APCH COURSE AND EVENTUALLY BEGAN DSCNT. BELOW 3000 FT TO 2600 FT, BUT THEN ELECTED TO GAR WHEN WE WERE UNABLE TO GET A CLRNC TO LAND OR FOR THE APCH. HAD WE MAINTAINED THE HDG AND ALT WE DEFINITELY WOULD HAVE CAUSED A TFC CONFLICT. A CALL TO THE FACILITY CONFIRMED THAT THE CTLR GOT SWAMPED.

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