# Accident 20031025026842A: Cessna 172R, San Diego, CA, October 25, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 25, 2003, 12:25 local time
- Place: San Diego, CA
- Airport: Montgomery Field Airport
- Damage: Minor damage
- Collision: Midair collision, second aircraft
- Phase of flight: Engine Run-Up
- Operating rules: General operating rules (Part 91)
- Location: 32.8156° N, 117.1394° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.8156&lon=-117.1394&mi=10
- Aircraft: N72AF, a cancelled registration (https://openairdocs.org/deregistered/N72AF-2019-10-05) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0360 SER A&C (registry code 41511, https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 30 total, 30 in this make and model, 28 in the last 90 days
- NTSB investigation: [NTSB LAX04LA027](https://openairdocs.org/ntsb/LAX04LA027) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031025026842A

## Narrative

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

(-23) ON OCTOBER 25, 2003, AT 1225 HOURS PACIFIC TIME, A PIPER PA-28, N39494, SUSTAINED MINOR DAMAGE WHEN IT STRUCK A CE-172, N72AF, IN THE AIRCRAFT RUN-UP AREA SHORT OF RUNWAY 28R AT MONTGOMERY FIELD (MYF), SAN DIEGO, CA. THE STUDENT PILOT IN N39494 ADMITTED TO FAA INSPECTORS THAT HE DID PANIC AND FAILED TO FULLY DEPRESS THE BRAKE PEDALS RESULTING IN A COLLISION BETWEEN THE TWO AIRCRAFT. THERE WERE NO INJURIES SUSTAINED BY EITHER STUDENT PILOT. THE REPORTING INSPECTOR VERIFIED THAT THE BRAKES WERE OPERATING ON N39494.

## Other aircraft in the event

- N39494, Piper PA28161: [Accident 20031025026841A](https://openairdocs.org/incident/20031025026841A)

## 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 LAX04LA027](https://openairdocs.org/ntsb/LAX04LA027), Oct 25, 2003: Cessna 172R (N72AF), San Diego, CA, substantial damage. Probable cause: the pilot of the other airplane's inadvertent application of the rudder pedals rather than the brakes, which resulted in the collision with the Cessna 172R.

## Other reports on N72AF (2)

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

- [Accident 20160105003129A](https://openairdocs.org/incident/20160105003129A), Jan 5, 2016: Cessna 172R (N72AF), Sulphur Springs, TX, Substantial damage. A training flight originated at addison municipal airport (ADS) and landed at Sulphur Springs municipal airport (kslr) runway 19. After touchdown, the pilot…
- [Incident 20151207019439I](https://openairdocs.org/incident/20151207019439I), Dec 7, 2015: Cessna 172R (N72AF), Addison, TX, Minor damage. On 12/07/15, at 0753 CST, a Cessna 172, N72AF, s/n 17280070 owned by ameriflyers of California inc, 16151 Addison rd, Addison TX 75001 had an incident while…

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.