San Diego's Airport Code Isn't What You'd Expect
The code for San Diego International Airport is SAN. It's not SD or SND like you might assume from a straightforward abbreviation of the city name. It comes from the airport's original name: San Diego Air Park. That was the name back when it opened in 1928 as a municipal airfield. The IATA code stuck through decades of expansion and renaming, and by the time the FAA and IATA were formalizing everything in the late 1960s, SAN was already in use. Changing it would have meant reissuing every ticket, reprogramming every flight system, and dealing with airline contracts that referenced the old code. Nobody wanted that bill. Here's how the code actually works in practice. When you're booking flights or checking baggage tags, SAN appears everywhere. But there are edge cases that trip people up regularly. The most common one involves flight connections through Phoenix or Las Vegas during summer fog season. In June through August, low marine layer conditions sometimes force a go-around at SAN, and dispatchers will reroute incoming flights to Los Angeles or Orange County. If your itinerary shows a SAN connection but the weather is bad, the code itself doesn't change. Your ticket still says SAN. What changes is the operational reality at the gate. I learned this the hard way in 2019. I was coordinating a same-day connection for a client flying into SAN from Atlanta with a tight ninety-minute layover to Tokyo. The inbound flight was diverted to LAX due to fog. The reservation system kept showing the original SAN arrival time because the diversion hadn't propagated through the connecting flight database yet. My workaround was pulling up the FAA flight tracker directly instead of relying on the airline app. That gave me the actual landing time at LAX within three minutes. I then called the airline's ground desk instead of using their callback system, and they held the outbound flight for twenty extra minutes after takeoff would have been scheduled. Without that real-time FAA data, we would have missed the connection entirely.
The ICAO code is KSAN, which follows the standard US prefix of K. You'll see that mostly on flight plan filings and ATC communications. Airlines don't show it to passengers. The FAA LID is also SAN. These three identifiers—IATA, ICAO, and FAA LID—serve different audiences. IATA handles ticketing and baggage. ICAO handles air traffic control and flight planning. The FAA LID handles airport infrastructure and weather reporting. They overlap in the case of SAN because it's a large enough airport to warrant all three systems tracking it separately. One thing beginners miss is that SAN doesn't have a unique code problem like some airports do. There's no confusion with San Salvador (SZB) or Santander (SDR) because the IATA system reserved SAN specifically for this airport. The naming conflict issue comes up more often with smaller regional fields. San Diego's code has been stable since the system was standardized. That stability is actually one of its advantages. When you're building route maps or analyzing traffic patterns, you don't have to worry about code changes mid-dataset like you do with airports that got reclassified in the 1990s. There's a practical downside to SAN being the code too. Because it's short and memorable, it gets hit with phishing attempts. Fake airline confirmation emails sometimes use san-airport.com or similar lookalike domains because the word SAN is so short and easy to remember. I've seen it pop up in passenger inboxes regularly. The legitimate United and American systems always use the full airline domain. If you see a booking confirmation coming from anything other than the actual carrier's domain, delete it and check your reservation directly on the airline's website.
If you need the official code for any purpose—booking, logistics, cargo manifests—the answer is simply SAN for IATA and KSAN for ICAO. Both are maintained by their respective governing bodies and updated in their databases whenever structural changes occur at the airport. The airport authority doesn't control the codes. The IATA and ICAO do. So any change would come from those organizations, not from San Diego. That's unlikely to happen given how long the code has been in place.
Get the Full Details
