The U.S. aircraft register, updated daily
Accidents · NTSB GAA18CA063 · Final report

Cessna 172N accident near San Diego, California, November 20, 2017

On November 20, 2017 at about 7:30 pm local time, a 1979 Cessna 172N, registered N172SX, was substantially damaged in an accident during approach near San Diego, California (Montgomery-Gibbs Executive airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

An in-flight collision with a bird.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 20, 2017 · about 7:30 pm local time
Place
San Diego, California · Montgomery-Gibbs Executive · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172N N, built 1979 · all 172Ns on the register
Registration
N172SX · registry record · serial 17273641
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that, about 2 miles from his destination, he made a left turn to enter the downwind leg for landing when a bird came "out of the sun." The pilot made a hard right turn to avoid the bird and prevent it from coming through the windscreen. The bird subsequently collided with the leading edge of the left wing. The pilot continued to his intended destination without further incident. Postaccident examination revealed substantial damage to the left wing. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Birdstrike during approach defining event

The NTSB's findings

  • cause Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Light condition › Glare › Effect on personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 174.1 hours in all; 44.2 in this make and model; 20.3 in the last 90 days; 5 in the last 30 days; 131.3 as pilot in command
  • Last flight review: November 17, 2016
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 2,299 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total
  • Operator: Personal Aviation INC.

The flight

  • Departed from: AJO Corona CA at 6:45 pm
  • Destination: MYF San Diego CA
  • Flight plan: none
  • Runway 28R, 4,577 ft by 150 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 34°F (1°C)
  • Altimeter: 30.02 inHg
  • Observation at 7:53 pm from KMYF

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on March 29, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.