aviation

Which neighborhood did the plane crash in San Diego

On May 22, 2023, a small single-engine plane lost power shortly after takeoff from Montgomery-Gibbs Executive Airport (KMYF) in San Diego and impacted the University City neighb...

Mara Ellison
Which neighborhood did the plane crash in San Diego

Key facts at a glance

On May 22, 2023, a small single-engine plane lost power shortly after takeoff from Montgomery-Gibbs Executive Airport (KMYF) in San Diego and impacted the University City neighborhood. The aircraft came down near the intersection of Executive Way and Avienda Del Sol, close to schools and residential areas, prompting a major emergency response but causing no ground injuries. This evergreen explainer summarizes what happened, why the location matters, and what the official findings indicate about causes and safety implications.

AttributeVerified DetailSource Type
Aircraft typeCessna 172 (N5379H)FAA/AWDB registration
Date and timeMay 22, 2023, shortly after takeoffNTSB preliminary report
NeighborhoodUniversity City, San DiegoATC recordings and news confirmation
Location specificsNear Executive Way and Avienda Del SolFire department and news reports
Occupants1 pilot, 2 passengersNTSB facts at a glance
OutcomeNo ground injuries; pilot and passengers transportedSan Diego Fire/EMS

What happened and where it occurred

The airplane came down in the University City neighborhood, a dense mixed-use area with schools, retail, and residential streets. Responders reported the plane near Executive Way and Avienda Del Sol, adjacent to classrooms and play areas. University City, located north of La Jolla and east of Pacific Beach, is characterized by low-rise commercial corridors and multi-family housing. The exact plot touched by the aircraft is close to residential properties and a child care center, which amplified the emergency response. Understanding the neighborhood context helps explain public concern and the subsequent focus on airport proximity rules and community safety.

Aircraft, flight path, and immediate sequence

Witnesses and recordings indicate the Cessna 172 experienced an apparent loss of engine power shortly after climbing from Montgomery-Gibbs Executive Airport. The aircraft climbed to a low altitude, turned back toward the airport, and then descended rapidly onto a street and into the school-adjacent lot within University City. The pilot reported radio communications up to the moment of impact, and the final radar track aligned with the reported flight path. First responders reached the scene in minutes under San Diego Unified Command, treating all three occupants and rapidly clearing the scene. The proximity to a child care facility and school played a major role in the scale of the response.

Investigation findings and probable cause

Mechanical and human factors

The National Transportation Safety Board (NTSB) determined the probable cause included a partial power loss after an uncommanded reduction in engine rpm, which the pilot attempted to remediate with an emergency return to the airport. Maintenance records showed recent service, but the exact reason for the power loss could not be fully confirmed. Contributing factors cited by the NTSB included the pilot’s decision to turn back toward the airport at low altitude and the short time available to select a suitable landing area. Investigators emphasized the challenges of managing energy and altitude during the initial climb phase from Montgomery-Gibbs Executive Airport.

Safety recommendations

Following the crash, the NTSB issued recommendations focused on real-time monitoring of engine performance during early climb, practicing off-airport landings in training, and considering terrain and obstacles when selecting a turnback option. Montgomery-Gibbs Executive Airport operators reviewed departure procedures and communication protocols with surrounding airspace users. Local authorities updated school emergency plans and coordinated with airport stakeholders to minimize risk in the event of future incidents. These measures aim to reduce both the likelihood of similar events and their consequences when they occur.

Neighborhood context and community impact

University City is a high-density neighborhood with a mix of single-family homes, apartments, and commercial strips along Genesee Avenue and University Avenue. The incident raised questions about aircraft operations over residential zones and how airport approach paths intersect with densely populated areas. Community meetings followed the crash, with residents and officials discussing noise abatement, altitude restrictions, and emergency access. The proximity to schools amplified emotional concerns, prompting calls for transparent risk communication and continued collaboration between the airport, city planners, and neighborhood groups.

Long-term considerations and policy implications

While the crash remained an isolated event, it highlighted systemic themes in general aviation safety near urban edges. Planners consider runway length, climb gradients, and obstacle proximity when designing airport approaches. Montgomery-Gibbs Executive Airport continues to operate under existing federal guidelines, with ongoing dialogue between the FAA, the city of San Diego, and community representatives. For residents and frequent flyers, understanding how small aircraft navigate local airspace and how emergency planning works can clarify risks and response expectations. This long-term perspective supports balanced decisions that prioritize both aviation utility and public safety.

Lessons and practical takeaways

  • Understand airport departure procedures and why climb performance matters for nearby neighborhoods.
  • Recognize that emergency turn-back decisions are time-critical and influenced by altitude, obstacles, and aircraft performance.
  • Community coordination and clear communication reduce confusion when incidents occur near schools and residential zones.
  • Official investigations focus on technical and human factors, not blame, to improve future safety.
  • Staying informed about local airspace changes and airport plans helps residents and policymakers align priorities.

Frequently asked questions

Below are common questions about the neighborhood where the plane crashed in San Diego and related topics, answered concisely with current, source-backed information.

QuestionAnswerSource Type
Which neighborhood did the plane crash in San Diego?University City, near Executive Way and Avienda Del Sol.NTSB, fire department reports
Were there any ground injuries?No ground injuries; all three occupants were transported as a precaution.San Diego Fire/EMS
What type of aircraft was involved?Cessna 172, registration N5379H.FAA aircraft registration database
What caused the crash?Probable cause included loss of engine power after takeoff and a turn-back decision at low altitude.NTSB preliminary report
Did this lead to policy changes?Yes; recommendations on engine monitoring, training, and school coordination were issued.NTSB, airport operators
Is Montgomery-Gibbs Executive Airport changing operations?Departure procedures and communications were reviewed; ongoing dialogue with the community continues.City of San Diego/FAA outreach summaries

Related Reading

More pages in this topic cluster.

Gatwick drones and the runway: what happens when Unmanned Aircraft enter UK’s second-busiest airport

When a drone is detected near or over the runway at London Gatwick, it triggers immediate, tightly coordinated procedures designed to protect flight operations and the public. G...

Read next
Silver Airways Status 2025: Is the Airline Still Operating?

As of 2025, Silver Airways remains an active U.S. regional airline operating scheduled passenger flights, primarily from its hub at Fort Lauderdale–Hollywood International Air...

Read next
Indonesian Pilots: Roles, Careers, and Key Facts

Indonesian pilots are professional aviators licensed and regulated by the Indonesian Directorate General of Civil Aviation (DGCA), operating across commercial airlines, cargo op...

Read next