Narrative:

We were on a downwind for runway 36L. We were given a heading and advised that our new runway would be runway 36R. We were cleared to maintain 4000 ft and to intercept the localizer for runway 36R. We flew through the GS; and it pegged on the bottom of screen. We asked for lower and were given 3000 ft. We were then cleared for the approach; asked to slow to 150 KTS or slower; and to contact tower. Before we switched over to tower; approach told us they needed us to slow as rapidly as possible. I said we were trying; but that we had been kept high and fast until pretty close in. Approach offered to sidestep us to the left side; but the captain declined. I told tower we could make it and we were told to contact tower. We were now high; fast; and on short final. We began configuring and trying to slow down. Somewhere in all the confusion; I heard tower ask a company Y flight if he could make a short approach and he said yes; but I was too busy configuring; running checklists; and talking to tower to notice what was developing. Tower then told us to begin s-turning because there was a dash-8 on a 1 mi final ahead of us. Tower advised that after 1 s-turn; we were cleared to land. The dash cleared just as our radio altimeter said '100.' we were stabilized by 500 ft afl and made an uneventful landing. However; I was configuring; running checklists; and asking the captain to 'verify' 2 items at a period of time when his eyes needed to be outside. We pulled it off; but I feel the margin of safety was severely compromised. Clt was trying to squeeze too many aircraft into too little airspace at the same time. I don't understand why we were told to plan for runway 36L; switched to runway 36R; and then offered a last-min sidestep back over to runway 36L. If runway 36L was available for a last-min sidestep; why didn't we just land there? Especially since landing on runway 36R apparently caused too much traffic in too short a timeframe. Clt ATC seems to have a particular problem with this. It appears to me that the controllers are trying to cram as much traffic as possible into the airspace quickly; but without having the experience to do so. I appreciate the effort to 'push tin;' but there's a fine line between pushing tin and bending it. I would rather accept more delays than compromise aircraft separation. I can't put my finger on the exact issue. Some of the more unique traffic management schemes that I see in lga; phl; or dca work out well. But in clt; it seems that these 'unique' efforts usually end up with a near disaster. Is it a controller experience issue? I don't know; but clt seems to me like an accident waiting to happen.

Google
 

Original NASA ASRS Text

Title: FO REPORTS NEAR GAR CAUSED BY ATC FILLING ARRIVAL GAPS WITH ACFT ON OPPOSITE DOWNWIND AND LEAVING INSUFFICIENT SPACING.

Narrative: WE WERE ON A DOWNWIND FOR RWY 36L. WE WERE GIVEN A HDG AND ADVISED THAT OUR NEW RWY WOULD BE RWY 36R. WE WERE CLRED TO MAINTAIN 4000 FT AND TO INTERCEPT THE LOC FOR RWY 36R. WE FLEW THROUGH THE GS; AND IT PEGGED ON THE BOTTOM OF SCREEN. WE ASKED FOR LOWER AND WERE GIVEN 3000 FT. WE WERE THEN CLRED FOR THE APCH; ASKED TO SLOW TO 150 KTS OR SLOWER; AND TO CONTACT TWR. BEFORE WE SWITCHED OVER TO TWR; APCH TOLD US THEY NEEDED US TO SLOW AS RAPIDLY AS POSSIBLE. I SAID WE WERE TRYING; BUT THAT WE HAD BEEN KEPT HIGH AND FAST UNTIL PRETTY CLOSE IN. APCH OFFERED TO SIDESTEP US TO THE L SIDE; BUT THE CAPT DECLINED. I TOLD TWR WE COULD MAKE IT AND WE WERE TOLD TO CONTACT TWR. WE WERE NOW HIGH; FAST; AND ON SHORT FINAL. WE BEGAN CONFIGURING AND TRYING TO SLOW DOWN. SOMEWHERE IN ALL THE CONFUSION; I HEARD TWR ASK A COMPANY Y FLT IF HE COULD MAKE A SHORT APCH AND HE SAID YES; BUT I WAS TOO BUSY CONFIGURING; RUNNING CHKLISTS; AND TALKING TO TWR TO NOTICE WHAT WAS DEVELOPING. TWR THEN TOLD US TO BEGIN S-TURNING BECAUSE THERE WAS A DASH-8 ON A 1 MI FINAL AHEAD OF US. TWR ADVISED THAT AFTER 1 S-TURN; WE WERE CLRED TO LAND. THE DASH CLRED JUST AS OUR RADIO ALTIMETER SAID '100.' WE WERE STABILIZED BY 500 FT AFL AND MADE AN UNEVENTFUL LNDG. HOWEVER; I WAS CONFIGURING; RUNNING CHKLISTS; AND ASKING THE CAPT TO 'VERIFY' 2 ITEMS AT A PERIOD OF TIME WHEN HIS EYES NEEDED TO BE OUTSIDE. WE PULLED IT OFF; BUT I FEEL THE MARGIN OF SAFETY WAS SEVERELY COMPROMISED. CLT WAS TRYING TO SQUEEZE TOO MANY ACFT INTO TOO LITTLE AIRSPACE AT THE SAME TIME. I DON'T UNDERSTAND WHY WE WERE TOLD TO PLAN FOR RWY 36L; SWITCHED TO RWY 36R; AND THEN OFFERED A LAST-MIN SIDESTEP BACK OVER TO RWY 36L. IF RWY 36L WAS AVAILABLE FOR A LAST-MIN SIDESTEP; WHY DIDN'T WE JUST LAND THERE? ESPECIALLY SINCE LNDG ON RWY 36R APPARENTLY CAUSED TOO MUCH TFC IN TOO SHORT A TIMEFRAME. CLT ATC SEEMS TO HAVE A PARTICULAR PROB WITH THIS. IT APPEARS TO ME THAT THE CTLRS ARE TRYING TO CRAM AS MUCH TFC AS POSSIBLE INTO THE AIRSPACE QUICKLY; BUT WITHOUT HAVING THE EXPERIENCE TO DO SO. I APPRECIATE THE EFFORT TO 'PUSH TIN;' BUT THERE'S A FINE LINE BTWN PUSHING TIN AND BENDING IT. I WOULD RATHER ACCEPT MORE DELAYS THAN COMPROMISE ACFT SEPARATION. I CAN'T PUT MY FINGER ON THE EXACT ISSUE. SOME OF THE MORE UNIQUE TFC MGMNT SCHEMES THAT I SEE IN LGA; PHL; OR DCA WORK OUT WELL. BUT IN CLT; IT SEEMS THAT THESE 'UNIQUE' EFFORTS USUALLY END UP WITH A NEAR DISASTER. IS IT A CTLR EXPERIENCE ISSUE? I DON'T KNOW; BUT CLT SEEMS TO ME LIKE AN ACCIDENT WAITING TO HAPPEN.

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