Narrative:

Combination of me conducting IOE on low experience first officer; runway change; long day. I was conducting IOE on a new hire first officer. It was his second day of IOE. We were on our sixth leg of the day. As we approached cvg; the ATIS advertised runways 18L/C/right as the active runways. We had set up and briefed the ILS runway 18L; including receiving the ACARS landing performance for runway 18L. We were switched to cvg approach control; and they told us to expect the ILS/visual approach to runway 36R. We were still around 10000 ft and only 20 miles from the airport. I told the first officer we needed to expedite our descent in order to help us get in position for a stabilized approach. He flew the airplane while I set up for the ILS runway 36R and got the ACARS performance data. The first officer briefed the new approach. We had the runway in sight and were cleared for the visual approach to runway 36R and told to switch to the tower frequency. We were still well above the glideslope. By the time we were done with setting up and briefing the approach; we were at 1000 ft above field elevation with flaps 20 and the gear down. Our airspeed was about 190 KTS. We were now transitioning below the glideslope. I told the first officer to increase the pitch to get back on the glideslope and help slow us down. I still needed to switch to tower frequency. I looked up the tower frequency and dialed it in. When I looked up I saw that we were at about 600 ft above field elevation with the gear down and flaps 30; and still about 1 DOT below the glideslope. I knew there was no way to get stabilized by 500 ft; so I called a go around. The go around was uneventful. We were given vectors back around for another visual approach. We landed without incident. I realized we were not going to be stabilized by 500 ft and we were below the glideslope. Give yourself more time to set up for the approach and more time to get configured/stabilized.

Google
 

Original NASA ASRS Text

Title: CL65-200 FLT CREW RECEIVES RWY CHANGE ARRIVING CVG WHICH RESULTS IN UNSTABILIZED APCH FOR IOE FO AND A GAR.

Narrative: COMBINATION OF ME CONDUCTING IOE ON LOW EXPERIENCE FO; RWY CHANGE; LONG DAY. I WAS CONDUCTING IOE ON A NEW HIRE FO. IT WAS HIS SECOND DAY OF IOE. WE WERE ON OUR SIXTH LEG OF THE DAY. AS WE APCHED CVG; THE ATIS ADVERTISED RWYS 18L/C/R AS THE ACTIVE RWYS. WE HAD SET UP AND BRIEFED THE ILS RWY 18L; INCLUDING RECEIVING THE ACARS LNDG PERFORMANCE FOR RWY 18L. WE WERE SWITCHED TO CVG APCH CTL; AND THEY TOLD US TO EXPECT THE ILS/VISUAL APCH TO RWY 36R. WE WERE STILL AROUND 10000 FT AND ONLY 20 MILES FROM THE ARPT. I TOLD THE FO WE NEEDED TO EXPEDITE OUR DSCNT IN ORDER TO HELP US GET IN POSITION FOR A STABILIZED APCH. HE FLEW THE AIRPLANE WHILE I SET UP FOR THE ILS RWY 36R AND GOT THE ACARS PERFORMANCE DATA. THE FO BRIEFED THE NEW APCH. WE HAD THE RWY IN SIGHT AND WERE CLRED FOR THE VISUAL APCH TO RWY 36R AND TOLD TO SWITCH TO THE TOWER FREQUENCY. WE WERE STILL WELL ABOVE THE GLIDESLOPE. BY THE TIME WE WERE DONE WITH SETTING UP AND BRIEFING THE APCH; WE WERE AT 1000 FT ABOVE FIELD ELEVATION WITH FLAPS 20 AND THE GEAR DOWN. OUR AIRSPEED WAS ABOUT 190 KTS. WE WERE NOW TRANSITIONING BELOW THE GLIDESLOPE. I TOLD THE FO TO INCREASE THE PITCH TO GET BACK ON THE GLIDESLOPE AND HELP SLOW US DOWN. I STILL NEEDED TO SWITCH TO TOWER FREQUENCY. I LOOKED UP THE TOWER FREQUENCY AND DIALED IT IN. WHEN I LOOKED UP I SAW THAT WE WERE AT ABOUT 600 FT ABOVE FIELD ELEVATION WITH THE GEAR DOWN AND FLAPS 30; AND STILL ABOUT 1 DOT BELOW THE GLIDESLOPE. I KNEW THERE WAS NO WAY TO GET STABILIZED BY 500 FT; SO I CALLED A GAR. THE GAR WAS UNEVENTFUL. WE WERE GIVEN VECTORS BACK AROUND FOR ANOTHER VISUAL APCH. WE LANDED WITHOUT INCIDENT. I REALIZED WE WERE NOT GOING TO BE STABILIZED BY 500 FT AND WE WERE BELOW THE GLIDESLOPE. GIVE YOURSELF MORE TIME TO SET UP FOR THE APCH AND MORE TIME TO GET CONFIGURED/STABILIZED.

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.