# Incident 19811130086389I: Cessna 402C, Cleveland, OH, November 30, 1981

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 30, 1981, 20:30 local time
- Place: Cleveland, OH
- Airport: Hopkins
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: Air taxi and commuter (Part 135)
- Operator: BVRA
- Location: 41.4995° N, 81.6954° W: Placed by OpenAirDocs: center of Cleveland, OH, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.4995&lon=-81.6954&mi=10
- Aircraft: N3246M, a cancelled registration (https://openairdocs.org/deregistered/N3246M-2012-10-02) (OpenAirDocs)
- Registry model: Cessna 402C (registry code 207590R, https://openairdocs.org/model/cessna-402c) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 402C
- Reported engine: CONT IO520*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 12,000 total, 1,000 in this make and model, 90 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19811130086389I

## Narrative

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

LEAK IN TIRE TUBE CAUSED TUBE TO DEFLATE ON LANDING. WAS ABLE TO TAXI CLEAR OF RUNWAY. TIRE CHANGED ON TAXIWAY.

## Other reports on N3246M (2)

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

- [Incident 20000620033419I](https://openairdocs.org/incident/20000620033419I), Jun 20, 2000: Cessna 402C (N3246M), Albuquerque, NM. (-23)After departing elp, reported #1 engine running erratically. Declared emergency, returned to nearest available runway, biggs afb, runway 3. After…
- [Incident 19860504036099I](https://openairdocs.org/incident/19860504036099I), May 4, 1986: Cessna 402C (N3246M), Ft Lauderdale, FL. Both propellers stopped on final approach due to fuel exhaustion. Safe landing on runway. Passenger complaint.

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.