# Accident 20010215003349A: Cessna 172N, San Diego, CA, February 15, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 15, 2001, 15:16 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.8156° N, 117.1394° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.8156&lon=-117.1394&mi=10
- Aircraft: N4922D, registered now (https://openairdocs.org/aircraft/N4922D) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYC O320*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 3,000 total, 900 in this make and model, 65 in the last 90 days
- NTSB investigation: [NTSB LAX01LA102](https://openairdocs.org/ntsb/LAX01LA102) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010215003349A

## Narrative

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

(-23) ON FEBRUARY 2, 2001, A CESSNA 172 CRASHED AT THE MONTGOMERY AIRPORT (MYF) IN SAN DIEGO, CA. IT WAS RULED AN ACCIDENT AND NOT AN INCIDENT. THERE WERE NO INJURIES. NO OTHER A/C INVOLVED. (-19) ON FEBRUARY 15, 2001, ABOUT 1516 HOURS PST, A CESSNA 172N, N4922D, VEERED OFF THE RUNWAY AND COLLIDED WITH A TAXIWAY SIGN DURING LANDING ROLLOUT ON RUNWAY 28L AT THE MONTGOMERY FIELD, SAN DIEGO, CA. THE AIRPLANE WAS SUBSTANTIALLY DAMAGED. NEITHER THE AIRLINE TRANSPORT CERTIFICATED PILOT NOR PASSENGER WAS INJURED. PLUS ONE FLYERS, INC., IN SAN DIEGO, OPERATED THE AIRPLANE. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND AN INSTRUMENT FLIGHT RULES FLIGHT PLAN WAS FILED. THE PERSONAL FLIGHT WAS PERFORMED UNDER 14 CFR PART 91, AND IT ORIGINATED IN SCOTTSDALE, AZ. ABOUT 1135. AIRPORT PERSONNEL REPORTED THAT THE COLLISION OCCURRED ABOUT 1,000 FEET UPWIND OF THE RUNWAY'S THRESHOLD. THE AIRPLANE IMPACTED THE TAXIWAY "C" SIGN, AND VEERED OFF THE RUNWAY. THE AIRPLANE CAME TO A STOP ABOUT 200 FEET NORTH OF THE RUNWAY. THE PILOT STATED THAT DURING THE LANDING ROLLOUT, AS THE AIRPLANE WAS DECELERATING THROUGH ABOUT 50 KNOTS, THE LEFT WING SUDDENLY LIFTED UP. THEREAFTER                                  HE LOST CONTROL OF THE AIRPLANE. HE ADDITIONALLY REPORTED THAT HE WAS UNAWARE OF THE REASON FOR THIS OCCURENCE. NO MECHANICAL MALFUNCTIONS WERE REPORTED WITH THE AIRPLANE. (.4) ON FEBRUARY 15, 2001, ABOUT 1516 HOURS PACIFIC STANDARD TIME, A CESSNA 172N, N4922D, VEERED OFF THE RUNWAY AND COLLIDED WITH A TAXIWAY SIGN DURING LANDING ROLLOUT ON RUNWAY 28L AT THE MONTGOMERY FIELD, SAN DIEGO, CALIFORNIA. THE AIRPLANE WAS SUBSTANTIALLY DAMAGED. NEITHER THE AIRLINE TRANSPORT CERTIFICATED PILOT NOR PASSENGER WAS INJURED. PLUS ONE FLYERS, INC., SAN DIEGO, OPERATED THE AIRPLANE. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND AN INSTRUMENT FLIGHT RULES FLIGHT PLAN WAS FILED. THE PERSONAL FLIGHT WAS PERFORMED UNDER 14 CFR PART 91, AND ORIGINATED IN SCOTTSDALE, ARIZONA, ABOUT 1235 MOUNTAIN STANDARD TIME. AIRPORT PERSONNEL REPORTED THAT THE COLLISION OCCURRED ABOUT 1,000 FEET UPWIND OF THE RUNWAY'S THRESHOLD. THE AIRPLANE IMPACTED THE TAXIWAY "C" SIGN AND VEERED OFF THE RUNWAY. THE AIRPLANE CAME TO A STOP ABOUT 550 FEET FARTHER UPWIND OF THE SIGN AND ABOUT 200 FEET NORTH OF THE RUNWAY. THE PILOT STATED TO THE NATIONAL TRANSPORTATION SAFETY BOA                                                     RD INVESTIGATOR THAT DURING THE LANDING ROLLOUT, AS THE AIRPLANE WAS DECELERATING THROUGH ABOUT 50 KNOTS, THE LEFT WING SUDDENLY LIFTED UP. THEREAFTER, HE LOST CONTROL OF THE AIRPLANE. HE ADDITIONALLY REPORTED THAT HE WAS UNAWARE OF THE REASON FOR THIS OCCURRENCE. NO MECHANICAL MALFUNCTIONS WERE REPORTED WITH THE AIRPLANE. IN THE PILOT'S PARTIALLY COMPLETED ACCIDENT REPORT, HE INDICATED THAT WHEN THE AIRPLANE WAS "ALMOST HALF WAY DOWN THE RUNWAY" THE LEFT WING ROSE UP, AND THEREAFTER HE LOST CONTROL OF THE AIRPLANE AS IT "VIOLENTLY" VEERED OFF THE RUNWAY. THE PILOT ALSO REPORTED THAT WHEN HE WAS ON FINAL APPROACH THE TOWER CONTROLLER REPORTED THAT THE WIND WAS FROM 270 DEGREES AT 6 KNOTS.

## 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 LAX01LA102](https://openairdocs.org/ntsb/LAX01LA102), Feb 15, 2001: Cessna 172N (N4922D), San Diego, CA, substantial damage. Probable cause: The pilot's failure to maintain directional control of the airplane during landing rollout.

## Other reports on N4922D (1)

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

- [Incident 20210416005279I](https://openairdocs.org/incident/20210416005279I), Apr 16, 2021: Cessna 172N (N4922D), San Diego, CA, No damage. The student pilot was returning to myf after a first solo cross country flight. The pilot stated that after a normal approach and landing touched down on the…

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.
