# Incident 19881109062049I: Bbavia 8KCAB, Mt Pleasant, SC, November 9, 1988

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 9, 1988, 13:55 local time
- Place: Mt Pleasant, SC
- Airport: East Cooper Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 32.7941° N, 79.8626° W: Placed by OpenAirDocs: center of Mount Pleasant, SC, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.7941&lon=-79.8626&mi=10
- Aircraft: N7921S, a cancelled registration (https://openairdocs.org/deregistered/N7921S-2013-08-28) (OpenAirDocs)
- Registry model: Bellanca 8KCAB (registry code 1220801, https://openairdocs.org/model/bellanca-8kcab) (OpenAirDocs)
- Registry engine: Lycoming AEIO-360 series (registry code 41522, https://openairdocs.org/engine/lycoming-aeio-360-series) (OpenAirDocs)
- Reported make and model: BBAVIA 8KCAB
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,800 total, 50 in this make and model, 170 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19881109062049I

## Narrative

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

OVERCONTROLLED DURING BOUNCED LANDING CAUSING PROP TO STRIKE RUNWAY. RECOVERED AND TAXIED TO RAMP.

## Other reports on N7921S (2)

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

- [Accident 19980127012669A](https://openairdocs.org/incident/19980127012669A), Jan 27, 1998: Bbavia 8KCAB (N7921S), Van Nuys, CA, Substantial damage. Lost control on takeoff. Struck several parked aircraft. Looking at CFI abilities. (.4) while on the takeoff roll the aircraft pulled hard to the left and the…
- [Accident 19920607021139A](https://openairdocs.org/incident/19920607021139A), Jun 7, 1992: Bbavia 8KCAB (N7921S), Wallace, NC, Substantial damage. Lost directional control landing in crosswind. Weather vaned. Tried go around but engine failed to respond.

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.