Narrative:

Approaching sbd from the north; we were cleared for the visual approach to runway 24 at an altitude of greater than 10000 feet. Our position was on a high upwind for runway 24; but since we arrived on runway 6 that morning; I heard 'cleared for visual approach' and did not pay attention to the 'runway 24' part of the transmission.upon seeing the runway far below and to my left; I set up a left pattern with a steep approach to runway 6. When we were on final; approximately 2 miles out; the co-pilot questioned the runway; and I realized I had set up for the wrong runway. I executed a go-around; entered downwind for runway 24; and completed a normal landing.I believe among the causes for this error were: fatigue; complacency due to familiarity with the area and our earlier experience at the airport; and our relative position and altitude when cleared for the visual approach. Our prime concern on the descent was to make a smooth and rapid descent while ensuring the comfort of our passengers.the fatigue factor can be attributed to our [early] duty time start; the co-pilot's busier schedule (he had flown several times in the past few days; and though he had legal rest; was very tired from the start); and my poor sleep in the hours before the flight.this could have been avoided by a more thorough briefing as we approached the airport. This would have given my co-pilot a heads-up that I was about to set up on the wrong runway. We discussed the event after our passengers had been picked up; and plan to be even more vigilant when we know ourselves to be fatigued.

Related reports:

Google
 

Original NASA ASRS Text

Title: Corporate Jet Captain reported setting up for the wrong runway at SBD; executed a missed approach and completed a normal landing on the runway in use.

Narrative: Approaching SBD from the north; we were cleared for the visual approach to runway 24 at an altitude of greater than 10000 feet. Our position was on a high upwind for runway 24; but since we arrived on runway 6 that morning; I heard 'cleared for visual approach' and did not pay attention to the 'runway 24' part of the transmission.Upon seeing the runway far below and to my left; I set up a left pattern with a steep approach to runway 6. When we were on final; approximately 2 miles out; the co-pilot questioned the runway; and I realized I had set up for the wrong runway. I executed a go-around; entered downwind for runway 24; and completed a normal landing.I believe among the causes for this error were: Fatigue; complacency due to familiarity with the area and our earlier experience at the airport; and our relative position and altitude when cleared for the visual approach. Our prime concern on the descent was to make a smooth and rapid descent while ensuring the comfort of our passengers.The fatigue factor can be attributed to our [early] duty time start; the co-pilot's busier schedule (he had flown several times in the past few days; and though he had legal rest; was very tired from the start); and my poor sleep in the hours before the flight.This could have been avoided by a more thorough briefing as we approached the airport. This would have given my co-pilot a heads-up that I was about to set up on the wrong runway. We discussed the event after our passengers had been picked up; and plan to be even more vigilant when we know ourselves to be fatigued.

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.