Piper J3C accident near San Diego, California, July 15, 2019
On July 15, 2019 at about 1:30 am local time, a 1946 Piper J3C, registered N92628, was substantially damaged in an accident during landing (flare/touchdown) 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
The pilot's failure to maintain directional control during landing, which resulted a ground loop.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 15, 2019 · about 1:30 am 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
- Piper J3C 65, built 1946 · all J3Cs on the register
- Registration
- N92628 · registry record · serial 16999
- 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, during his second touch-and-go landing, the airplane encountered a crosswind. He overcorrected with rudder input, and the airplane then ground looped and exited the runway to the left. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preimpact 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
- Other weather encounter during landing (flare/touchdown)
- Loss of control on ground during landing (flare/touchdown) defining event
- Runway excursion during landing (flare/touchdown)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: commercial pilot, remote
- Ratings: single-engine land; instrument: airplane
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Last inspection: annual inspection
- Seats: 2
- Landing gear: fixed
- Engine: (piston); 0 hours total
- Operator: Advanced Coherent Technologies Llc
The flight
- Departed from: MYF San Diego CA at 1:15 am
- Destination: MYF San Diego CA
- Flight plan: none
- Runway 28R, 4,598 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 250° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 61°F (16°C)
- Altimeter: 29.94 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on May 19, 2020. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot Record of Memorandum | PDF, 1 page | View Download |
| 2 | Accident Photo | PDF, 1 page | View Download |
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.