# Incident 20130329005659I: Cessna 150L, Torrance Airpor, CA, March 29, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 29, 2013, 12:57 local time
- Place: Torrance Airpor, CA
- Airport: Zamperini Field
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.8034° N, 118.3396° W: Placed by OpenAirDocs at ZAMPERINI FLD (TOA), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.8034&lon=-118.3396&mi=10
- Aircraft: N6566G, registered now (https://openairdocs.org/aircraft/N6566G) (OpenAirDocs)
- Registry model: Cessna 150L (registry code 2071826, https://openairdocs.org/model/cessna-150l) (OpenAirDocs)
- Registry engine: Continental 0-200 series (registry code 17020, https://openairdocs.org/engine/continental-0-200-series) (OpenAirDocs)
- Reported make and model: CESSNA 150L
- Reported engine: CONT MOTOR 0-200 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130329005659I

## Narrative

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

ON THE FOURTH LANDING DURING PATTERN WORK AT TORRANCE AIRPORT, N6566G TOUCH DOWN AND IMMEDIATELY A VIBRATION AND WOBBLING OCCURRED.  A GRINDING NOISE WAS FELT AND HEARD FOLLOWED BY THE AIRCRAFT PULLING TO THE RIGHT.  THE PILOT MADE CONTROL INPUTS AND APPLIED BRAKES TO STOP THE VEERING.  THE AIRCRAFT STOPPED JUST PAST THE NUMBER ON THE RUNWAY OF 29R.  THE PILOT AND STUDENT EXITED THE AIRCRAFT TO FIND THE RH MAIN WHEEL ASSEMBLY HAD BROKEN OFF.

## Other reports on N6566G (1)

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

- [Accident 19930421020979A](https://openairdocs.org/incident/19930421020979A), Apr 21, 1993: Cessna 150M (N6566G), Lakeport, CA, Substantial damage. On first solo landing bounced, porpoised and then came down nose first.

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.