# Accident 20041113030739A: Grtlks 2T1A, San Diego, CA, November 13, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 13, 2004, 14:18 local time
- Place: San Diego, CA
- Airport: Montgomery Field Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 32.8000° N, 116.9667° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.8000&lon=-116.9667&mi=10
- Aircraft: N502GL, registered now (https://openairdocs.org/aircraft/N502GL) (OpenAirDocs)
- Registry model: Great Lakes 2T-1A (registry code 3910106, https://openairdocs.org/model/great-lakes-2t-1a) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: GRTLKS 2T1A
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 5,515 total, 400 in this make and model, 20 in the last 90 days
- NTSB investigation: [NTSB LAX05LA037](https://openairdocs.org/ntsb/LAX05LA037) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041113030739A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON NOVEMBER 13, 2004, AT 1418 PST, N502GL A MODEL 2T-1A GREAT LAKES AIRCRAFT GROUND LOOPED DURING LANDING ROLLOUT RUNWAY 28L, MONTGOMERY AIRFIELD, SAN DIEGO CA. THE FLIGHT WAS CONDUCTED UNDER THE PROVISION OF 14 CFR PART 91. THE PILOT STATED THAT DURING ROLLOUT HE APPLIED BRAKES BUT THE LEFT DID NOT ACTIVATE WHICH CAUSED THE AIRCRAFT TO DEPART THE RUNWAY TO THE RIGHT. THE SOFT GROUND CAUSED N502GL TO TIP ON THE LEFT LOWER WING AND NOSE OVER. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED, THE PILOT AND STUDENT PILOT WERE NOT INJURED. INVESTIGATION REVEALED THE LEFT BRAKE FELT SOFT WHEN ACTIVATED (FRONT AND REAR COCKPIT BRAKE LEVERS) HOWEVER NO MECHANICAL ABNORMALITIES WERE NOTED. POSSIBLE AIR OR BYPASS CONDITION. M OR D WILL BE SUBMITTED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX05LA037](https://openairdocs.org/ntsb/LAX05LA037), Nov 13, 2004: Great Lakes 2T-1A (N502GL), San Diego, CA, substantial damage. Probable cause: the flight instructor's failure to maintain directional control during the landing rollout.

## Other reports on N502GL (5)

Matched to the same aircraft by N-number and date.

- [Accident 20111013024159A](https://openairdocs.org/incident/20111013024159A), Oct 13, 2011: Great Lakes 2T-1A (N502GL), San Diego, CA, Substantial damage. After touching down during landing on runway 28L, tire marks on the runway showed the right maingear wheel braking hard and pulling the craft to the right of…
- [Accident 20020209002399A](https://openairdocs.org/incident/20020209002399A), Feb 9, 2002: Grtlks 2T1A (N502GL), Sandiego, CA, No damage. (-23) On February 9, 2002, N502GL a great lakes aircraft, model 2T-1A was conducting FAR part 91 flight operations. The pilot states that during roll out…
- [Incident 19910630029279I](https://openairdocs.org/incident/19910630029279I), Jun 30, 1991: Grtlks 2T1A (N502GL), San Diego, CA, Minor damage. Pilot stated he had to brake hard to avoid aircraft waiting ahead. Aircraft nosed over and propeller struck ground.
- [Incident 19790613015639I](https://openairdocs.org/incident/19790613015639I), Jun 13, 1979: Grtlks 2T1A1 (N502GL), San Diego, CA, Minor damage. Pilot taxiing into the sun applied brakes suddenly to avoid another aircraft. Nosed up.
- [Accident 19740810025929A](https://openairdocs.org/incident/19740810025929A), Aug 10, 1974: Grtlks 2T1A (N502GL), Holtville, CA, Substantial damage. Intentional spin to ldg with insufficient alt for complete recovery resulting in hard ldg off rwy

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.