# Accident 20010419008189A: Cessna 172P, Torrance, CA, April 19, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 19, 2001, 12:57 local time
- Place: Torrance, CA
- Airport: Torrance Municipal Airport
- Damage: No damage
- Location: 33.8004° N, 118.3491° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=33.8004&lon=-118.3491&mi=10
- Aircraft: N97984, registered now (https://openairdocs.org/aircraft/N97984) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- NTSB investigation: [NTSB LAX01LA150](https://openairdocs.org/ntsb/LAX01LA150) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010419008189A

## Narrative

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

(-23)N97984, VEERED OFF RUNWAY 25 RIGHT AND NOSED OVER AFTER ENCOUNTERING SOFT SOIL DURING A TOUCH-AND-GO LANDING AT THE TORRANCE MUNICIPAL AIRPORT, TORRANCE, CALIFORNIA. THE PILOT STATED THAT THE RIGHT BRAKE HAD LOCKED ON TOUCHDOWN, CAUSING HIM TO VEER TO THE RIGHT AND EXIT THE RUNWAY.  FAA INSPECTOR EXAMINED THE AIRPLANE AND THE RUNWAY.  NO SKID MARKS WERE FOUND LEADING TO THE ACCIDENT SITE. THE TIRES WERE EXAMINED AND NO FLAT SPOTS WERE OBSERVED.  THE FAA INSPECTOR ROLLED THE AIRPLANE TO SEE IF THERE WAS ANY RESISTANCE FROM THE BRAKES.  NONE WERE NOTED.  THE BRAKES WERE INSPECTED AND OPERATED WITH NO DEFECTS OBSERVED.

## 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 LAX01LA150](https://openairdocs.org/ntsb/LAX01LA150), Apr 19, 2001: Cessna 172P (N97984), Torrance, CA, substantial damage. Probable cause: The failure of the pilot-in-command to execute a proper landing flare, which resulted in an improper touchdown attitude and a subsequent loss of directional control. A factor in the accident was the…

## Other reports on N97984 (3)

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

- [Accident 19911017046869A](https://openairdocs.org/incident/19911017046869A), Oct 17, 1991: Cessna 172P (N97984), Maple Lake, MN, Substantial damage. Engine quit climbing out. Landed soft field and nosed over. Engine ran normal. Post accident test. Fuel on board.
- [Accident 19900107000609A](https://openairdocs.org/incident/19900107000609A), Jan 7, 1990: Cessna 172P (N97984), St Cloud, MN, Substantial damage. Wing struck a light pole while taxiing to park.
- [Accident 19890723024829A](https://openairdocs.org/incident/19890723024829A), Jul 23, 1989: Cessna 172P (N97984), Duluth, MN, Substantial damage. Lost directional control landing in moderate variable wind. And nosed over.

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.