Narrative:

At approximately XA28Z after receiving the ATIS information at cae airport, we elected the visual runway 29. Night VMC, we were on a vector from the northeast. Columbia approach asked to report the airport in sight. Spotting the airport beacon, we then had the apparent runway in sight, informed approach and were cleared for the visual for runway 29. We then configured the aircraft for landing and turned for final. On final approach, we realized that the ILS runway 29 localizer was not on and determined that we were not lined up with runway 29. At this point we executed a go around and were given vectors for a landing on runway 11 at cae airport. My judgement is that we probably should not have called the runway until vectored on final. Suggestion: with the similar runway layouts and close proximity of the airports, ATC could give a heads up about this situation.

Google
 

Original NASA ASRS Text

Title: D-328 CREW LINED UP ON THE WRONG RWY DURING A NIGHT VISUAL APCH AT CAE.

Narrative: AT APPROX XA28Z AFTER RECEIVING THE ATIS INFO AT CAE ARPT, WE ELECTED THE VISUAL RWY 29. NIGHT VMC, WE WERE ON A VECTOR FROM THE NE. COLUMBIA APCH ASKED TO RPT THE ARPT IN SIGHT. SPOTTING THE ARPT BEACON, WE THEN HAD THE APPARENT RWY IN SIGHT, INFORMED APCH AND WERE CLRED FOR THE VISUAL FOR RWY 29. WE THEN CONFIGURED THE ACFT FOR LNDG AND TURNED FOR FINAL. ON FINAL APCH, WE REALIZED THAT THE ILS RWY 29 LOC WAS NOT ON AND DETERMINED THAT WE WERE NOT LINED UP WITH RWY 29. AT THIS POINT WE EXECUTED A GAR AND WERE GIVEN VECTORS FOR A LNDG ON RWY 11 AT CAE ARPT. MY JUDGEMENT IS THAT WE PROBABLY SHOULD NOT HAVE CALLED THE RWY UNTIL VECTORED ON FINAL. SUGGESTION: WITH THE SIMILAR RWY LAYOUTS AND CLOSE PROX OF THE ARPTS, ATC COULD GIVE A HEADS UP ABOUT THIS SIT.

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.