A runway incursion or near-collision event involving a business jet and a commercial Boeing 737 at San Diego International Airport (KSAN) has drawn the attention of federal aviation safety officials, adding to a growing national conversation about surface and airspace safety at high-density airports. San Diego's Lindbergh Field presents a uniquely demanding operational environment: it is one of the busiest single-runway airports in the United States, handling a mix of major air carrier operations, regional jets, and business aviation traffic in a compressed geographic footprint bordered by downtown San Diego, a harbor, and rapidly rising terrain to the east. The convergence of business jet movements — which often operate under Part 91 or Part 135 rules with varying levels of crew experience and procedural standardization — alongside high-frequency commercial airline operations on a single runway creates inherent complexity that demands precise coordination between flight crews and air traffic control.
For professional pilots operating into KSAN, the incident serves as a stark reinforcement of why situational awareness and strict adherence to ATC clearances are non-negotiable at airports with limited runway infrastructure. Business jet crews, who frequently operate into airports like KSAN on irregular schedules and may have less familiarity with the specific taxi geometry, hot spots, and sequencing norms than line pilots who fly the route daily, bear a heightened responsibility for vigilance. KSAN's Runway 27 approach is already well-known for its demands — a non-standard, curved visual approach over populated urban terrain — and any breakdown in communication or position awareness on the surface or in the terminal environment compounds the risk significantly. Part 91K and Part 135 operators should use incidents like this as a direct trigger for reviewing airport-specific briefing materials, FAA-published hot spot diagrams, and crew coordination protocols for complex, single-runway facilities.
The broader regulatory and safety context matters here as well. The FAA has been under sustained pressure following a series of high-profile runway incursions at major U.S. airports in recent years, including the 2023 near-collision at Austin-Bergstrom and other close calls at JFK and other capacity-constrained facilities. The agency has been advancing runway safety initiatives including enhanced surface detection technology, updated ATC phraseology standards, and increased scrutiny of mixed-use airport operations where general and business aviation intersect with Part 121 carriers. The National Transportation Safety Board has repeatedly flagged runway incursions as among the most preventable categories of aviation accidents, and incidents at airports like KSAN — where operational tempo is high and margin for error is low — are exactly the type of events that tend to accelerate regulatory action.
For corporate flight departments and charter operators, this type of incident also has operational risk management implications beyond the immediate crew level. Safety management systems (SMS) in Part 135 and larger Part 91 operations should be capturing voluntary safety reports from pilots who operate into complex airports and flagging systemic concerns about ATC workload, clearance ambiguity, or surface movement complexity. As the FAA and likely the NTSB investigate this close call, operators can expect scrutiny of whether proper CRM protocols were followed, whether crews received and correctly read back all relevant clearances, and whether any systemic ATC or airport design factors contributed to the event. The outcome of the investigation may produce safety recommendations with direct implications for how business aviation operates at Class B airports with high commercial traffic density.