Narrative:

Arrived overhead sps inbound from southeast at 4000 ft. Activated pilot controlled lighting prior to being overhead to confirm location of runway. Ca began turn to displace for downwind for runway 15C. We both noted that runway 33 was lit for use which was opposite direction for winds. We had planned to land runway 15C due to wind. Upon turning final; realized 15C was not lit when comparing localizer course to actual lit runway. Runway 15R was lit. Ca called for go around; we executed the go around and returned to left downwind to brief runway 15R visual approach. No further issues. After researching why runway 15R was lit we discovered we missed the note in the release. We also realized the notes in the 10-9A page can be misleading. Note 1 is clear that 15R/33L are lit when the tower [is closed]. Note 3 is less clear with the use of 'and' and the caveat of 'depending on weather'. Additionally; the lighting to both 15R and 33L are described as MALSR and the diagrams on approach plates are the same. They are not. 33L has lead in lights with sfls; but 15R does not. At least they weren't lit last night. We saw we had briefed and expected one runway but lighting to a different runway was encountered. We trapped that error by not continuing to accept the approach and possibly simply transitioned to a sidestep. So we went around and prepared for the 'new' runway. The release note would be better served if it were in the arrival remarks of the 10-7X page. The strange caveats of the approach plate notes in the 10-9A page could be clarified. For our improvement our crew could have discussed the notes. But we both missed the notes. So we need to incorporate better awareness of where notes can be located.

Related reports:

Google
 

Original NASA ASRS Text

Title: A medium turbojet First Officer reported there was confusion in the cockpit during a night visual approach to SPS airport concerning runway lighting and airport notes.

Narrative: Arrived overhead SPS inbound from southeast at 4000 ft. Activated pilot controlled lighting prior to being overhead to confirm location of runway. CA began turn to displace for downwind for runway 15C. We both noted that runway 33 was lit for use which was opposite direction for winds. We had planned to land runway 15C due to wind. Upon turning final; realized 15C was not lit when comparing LOC course to actual lit runway. runway 15R was lit. CA called for go around; we executed the go around and returned to left downwind to brief runway 15R visual approach. No further issues. After researching why runway 15R was lit we discovered we missed the note in the release. We also realized the notes in the 10-9A page can be misleading. Note 1 is clear that 15R/33L are lit when the Tower [is closed]. Note 3 is less clear with the use of 'and' and the caveat of 'depending on weather'. Additionally; the lighting to both 15R and 33L are described as MALSR and the diagrams on approach plates are the same. They are not. 33L has lead in lights with SFLs; but 15R does not. At least they weren't lit last night. We saw we had briefed and expected one runway but lighting to a different runway was encountered. We trapped that error by not continuing to accept the approach and possibly simply transitioned to a sidestep. So we went around and prepared for the 'new' runway. The release note would be better served if it were in the Arrival Remarks of the 10-7X page. The strange caveats of the approach plate notes in the 10-9A page could be clarified. For our improvement our crew could have discussed the notes. But we both missed the notes. So we need to incorporate better awareness of where notes can be located.

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