Date: 201302
Local time of day: 0001-0600
Location: SAV.Airport, GA
Flight conditions: VMC
Light: Night
Aircraft: Gulfstream V / G500 / G550
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class E ZJX
ATC / advisory: CTAF SAV; Center ZJX
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airport; Procedure
Primary problem: Ambiguous

Narrative: Our flight approached SAV from the north in night VMC conditions; the surface winds were calm. We requested and received the RNAV (GPS) Runway 19 approach from JAX Approach Control (SAV Approach/Tower was closed) and at approximately 12 miles from the airport; the pilot not flying activated the airport lighting on 119.1 per procedure when the Tower is closed. JAX Approach; and the ASOS did not provide any additional information regarding airport lighting and no NOTAM's were published indicating specific procedures for runway operations. We verified the airport beacon and lighting visually but had difficulty confirming runway lights for Runway 19. The pilot not flying completed the aircraft checklists and we continued the approach to inside the final approach fix. The pilot not flying again attempted to activate the Runway 19 lights but the lights remained off. We executed a missed approach and entered a downwind for Runway 10 (lights on) and executed an uneventful landing. I contacted SAV Tower upon my return to SAV and discussed the scenario. I was informed that the Tower Controller selects the runway to be illuminated before closing the Tower for the night to mitigate the risk potential of two aircraft landing on the perpendicular runways and colliding at the intersection. I was advised that JAX is informed of the runway selection prior to the Tower closing. I verified that no NOTAM is published and no notification is given via ATIS regarding the selected runway for night time operations. I believe the intentions of the SAV ATC facility are good by mitigating the potential for night time collisions. The runways are long and aircraft navigation and anti-collision lights could easily be lost in the ground clutter of airport lighting. I would like to submit the following suggestions to further enhance safety: 1: Revise airport directory/Commercial Chart data to reflect the specific procedures for night time operations at SAV. 2: Not all aircraft will be using/monitoring JAX Center for information regarding the active lighted runway so airport ATIS should be used to notify pilots of the active (lighted) runway. 3: A standing NOTAM should be issued to alert pilots that SAV selects a specific runway for night time operations (contact JAX Center for current information etc.) 4: JAX Center should have the capability to select the alternate runway due to wind shifts; aircraft performance etc. and revise ATIS as appropriate.5: Or; consider cancelling the operations procedure until specific procedures are posted through the appropriate aviation publications.




Synopsis: Gulfstream V Captain discovers SAV runway lighting after Tower closure is set to only illuminate one of the two runways; this information is not readily available to flight crews via ATIS or NOTAM. This resulted in a go around when Runway 19 lights could not be activated; followed by a visual approach to the lighted Runway 10.