# NTSB LAX01LA102: Cessna 172N, N4922D, San Diego, CA, February 15, 2001

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: February 15, 2001, 15:16 local (23:16 UTC)
- Place: San Diego, CA
- Coordinates: 32.815555, -117.139442
- Nearby events: https://openairdocs.org/map.md?lat=32.8156&lon=-117.1394&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report January 23, 2002
- Report: Approved by Office Director
- Parties: WP-FSDO
- NTSB case key (mKey): 51742
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX01LA102
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/51742/pdf
- Page: https://openairdocs.org/ntsb/LAX01LA102

## Probable cause

The pilot's failure to maintain directional control of the airplane during landing rollout.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - on ground/water, landing - roll
  - directional control - not maintained, pilot in command (cause)
- On ground/water collision with object, landing - roll
  - object - sign

## Analysis

During landing rollout, the airplane veered off the runway and collided with obstacles.  At the completion of a 3.7-hour-long flight, the tower controller advised the pilot that the local wind was from 270 degrees at 6 knots, and asked him to switch runways to the parallel.  After touchdown, the airplane was still traveling about 50 knots when, approaching runway 28L's midfield location, the pilot lost directional control.  The left wing rose upward.  The airplane veered off the runway and impacted a sign.  Airport personnel reported that the collision occurred about 1,000 feet upwind of the runway's threshold.  The airplane came to a stop about 550 feet farther upwind of the sign and about 200 feet north of the runway.   No mechanical malfunctions were reported with the airplane.

## Factual narrative

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 Board 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.

## Aircraft

- Registration: [N4922D](https://openairdocs.org/aircraft/N4922D), registered now, S/N 17272398, built 1979 (OpenAirDocs)
- Reported make and model: Cessna 172N
- Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17272398
- Engines: Lycoming O-320 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Plus One Flyers, Inc.
- Registered owner: Rent-2-Fly Aero II, Inc.
- Airworthiness certificate: Standard, Normal
- Departed: SDL, SCOTTSDALE, AZ
- Destination: MYF, San Diego, CA
- Flight plan: IFR
- Airport: MYF, Montgomery Field, runway 28L, 3,399 × 60 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 39; injuries: none; commercial, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; last flight review October 15, 2000; seat: left; flight hours: 3,000 total, 900 in this make and model, 2,200 as pilot in command, 65 in the last 90 days, 15 in the last 30 days, 5 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 290° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 57 °F, dew point 43 °F
- Altimeter: 30.12 inHg
- Observed at: MYF

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20010215003349A](https://openairdocs.org/incident/20010215003349A), Feb 15, 2001: Cessna 172N, San Diego, CA, Substantial damage. (-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…

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.

---
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.
