Narrative:

Approaching sav airport from the nne, we were being handled by ZJX. We were descending out of 5000 ft for 2000 ft and were heading to a point about 4 NM west of mavis, the LOM for runway 9. We could see the sav rotating beacon, the ramp area, and the lights for runway 18. The tower had closed for the night, so when ZJX cleared us for a visual approach to runway 9, I broadcast our position on left base and then turning final on 119.1, the CTAF. As we intercepted the runway 9 localizer outside mavis, I was surprised we couldn't see the runway lights since my broadcast and repeated keying of the microphone should have reactivated the runway lights. We configured the aircraft for landing, completed the checklists and intercepted the GS. At 1000 ft, even though we could see the airport environment and were established on the ILS, we still did not see the runway 9 runway lights. I voiced my concern about not having the runway lights and recommended a go around so we could get the light situation straightened out. The captain elected to continue. I continued to key the microphone and reset the CTAF. The runway lights finally came on with us on short final. Landing and rollout were uneventful. I'm not sure what the problem was although I suspect that even though the radio was set to 119.1, it may have been between frequencys and that my recycling it on short final might have taken care of the problem. While I've never had a problem of this nature before operating into an uncontrolled airport, I do believe that any distraction of this nature coupled with working 2 radios (CTAF and jax) simultaneously, configuring the aircraft for landing and accomplishing the checklists removes one of the layers of safety we like to have. While I don't consider this incident unsafe, I feel it would certainly be more safe if a manned, operating control tower were kept operating during part 121 operations.

Google
 

Original NASA ASRS Text

Title: A B737-300 FLC ON A NIGHT VISUAL APCH HAS DIFFICULTY IN ACTIVATING THE RWY LIGHTING SYS FOR RWY 9 AT SAV, GA.

Narrative: APCHING SAV ARPT FROM THE NNE, WE WERE BEING HANDLED BY ZJX. WE WERE DSNDING OUT OF 5000 FT FOR 2000 FT AND WERE HDG TO A POINT ABOUT 4 NM W OF MAVIS, THE LOM FOR RWY 9. WE COULD SEE THE SAV ROTATING BEACON, THE RAMP AREA, AND THE LIGHTS FOR RWY 18. THE TWR HAD CLOSED FOR THE NIGHT, SO WHEN ZJX CLRED US FOR A VISUAL APCH TO RWY 9, I BROADCAST OUR POS ON L BASE AND THEN TURNING FINAL ON 119.1, THE CTAF. AS WE INTERCEPTED THE RWY 9 LOC OUTSIDE MAVIS, I WAS SURPRISED WE COULDN'T SEE THE RWY LIGHTS SINCE MY BROADCAST AND REPEATED KEYING OF THE MIKE SHOULD HAVE REACTIVATED THE RWY LIGHTS. WE CONFIGURED THE ACFT FOR LNDG, COMPLETED THE CHKLISTS AND INTERCEPTED THE GS. AT 1000 FT, EVEN THOUGH WE COULD SEE THE ARPT ENVIRONMENT AND WERE ESTABLISHED ON THE ILS, WE STILL DID NOT SEE THE RWY 9 RWY LIGHTS. I VOICED MY CONCERN ABOUT NOT HAVING THE RWY LIGHTS AND RECOMMENDED A GAR SO WE COULD GET THE LIGHT SIT STRAIGHTENED OUT. THE CAPT ELECTED TO CONTINUE. I CONTINUED TO KEY THE MIKE AND RESET THE CTAF. THE RWY LIGHTS FINALLY CAME ON WITH US ON SHORT FINAL. LNDG AND ROLLOUT WERE UNEVENTFUL. I'M NOT SURE WHAT THE PROB WAS ALTHOUGH I SUSPECT THAT EVEN THOUGH THE RADIO WAS SET TO 119.1, IT MAY HAVE BEEN BTWN FREQS AND THAT MY RECYCLING IT ON SHORT FINAL MIGHT HAVE TAKEN CARE OF THE PROB. WHILE I'VE NEVER HAD A PROB OF THIS NATURE BEFORE OPERATING INTO AN UNCTLED ARPT, I DO BELIEVE THAT ANY DISTR OF THIS NATURE COUPLED WITH WORKING 2 RADIOS (CTAF AND JAX) SIMULTANEOUSLY, CONFIGURING THE ACFT FOR LNDG AND ACCOMPLISHING THE CHKLISTS REMOVES ONE OF THE LAYERS OF SAFETY WE LIKE TO HAVE. WHILE I DON'T CONSIDER THIS INCIDENT UNSAFE, I FEEL IT WOULD CERTAINLY BE MORE SAFE IF A MANNED, OPERATING CTL TWR WERE KEPT OPERATING DURING PART 121 OPS.

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.