Great Lakes 2T-1A accident near San Diego, California, October 13, 2011
On October 13, 2011 at about 2:30 pm local time, a Great Lakes 2T-1A, registered N502GL, was substantially damaged in an accident during landing (landing roll) near San Diego, California (Montgomery Field Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's excessive brake application during landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 13, 2011 · about 2:30 pm local time
- Place
- San Diego, California · Montgomery Field Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Great Lakes 2T-1A · all 2T-1As on the register
- Registration
- N502GL · registry record · serial 0502
- 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 the landing roll, he applied wheel brakes in an effort to turn onto a taxiway. He stated that, when he applied the brakes, the right brake locked up and the airplane subsequently nosed over, coming to rest inverted. The airplane sustained substantial damage to the wing and vertical stabilizer. No preexisting mechanical failures or malfunctions with the airplane were reported.
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
- Loss of control on ground during landing (landing roll)
- Nose over/nose down during landing (landing roll) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Incorrect use/operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 2,094 hours in all; 239 in this make and model; 8 in the last 90 days; 4 in the last 30 days; 2,094 as pilot in command
- Last flight review: April 29, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: rear
- Injury: no injuries
The aircraft
- Airframe total time: 1,978 hours
- Last inspection: annual inspection, October 9, 2010; 50 hours since
- Maximum gross weight: 1,750 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: MYF San Diego CA at 2:15 pm
- Destination: MYF San Diego CA
- Flight plan: none
- Runway 28L, 3,401 ft by 60 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 66°F (19°C), dew point 46°F (8°C)
- Altimeter: 29.82 inHg
- Observation at 2:53 pm from MYF
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N502GL the same tail number, which may have belonged to a different aircraft at the time
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.