# Incident 20060620015239I: Cessna 421A, Columbus, OH, June 20, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 20, 2006, 14:33 local time
- Place: Columbus, OH
- Airport: Port Columbus International
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 39.9612° N, 82.9988° W: Placed by OpenAirDocs: center of Columbus, OH, within about 8 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.9612&lon=-82.9988&mi=10
- Aircraft: N216WA, a cancelled registration (https://openairdocs.org/deregistered/N216WA-2018-02-12) (OpenAirDocs)
- Registry model: Cessna 421A (registry code 2076012, https://openairdocs.org/model/cessna-421a) (OpenAirDocs)
- Registry engine: Continental GTSIO-520 series (registry code 17046, https://openairdocs.org/engine/continental-gtsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 421A
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 25,000 total, 350 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060620015239I

## Narrative

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

(-23) AIRCRAFT N216WA WAS CLEARED TO LAND ON RUNWAY 28L AT CMH. ON LANDING ROLLOUT, PIC STATED THE LEFT WING STARTED TO SETTLE AND DIP. THE LEFT MAIN GEAR COLLAPSED AND THE LEFT WINGTIP AND PROPELLER CONTACTED THE RUNWAY. INSPECTORS ^PRIVACY DATA OMITTED^ INSPECTED THE AIRCRAFT FOUND THE BOLT ATTACHING THE BELLCRANK TO THE TRUNNION HAD SHEARED. THE FORWARD EAR ON THE TRUNNION WAS BROKEN AND THE BELLCRANK WAS DAMAGED.

## Other reports on N216WA (1)

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

- [Accident 20130501006279A](https://openairdocs.org/incident/20130501006279A), May 1, 2013: Cessna 421A (N216WA), Oakland, CA, Substantial damage. Cessna N216WA s/n 421A-0032. PIC - [privacy data omitted]. The airman reported the intended flight was to maintain IFR currency. Aircraft owner [privacy data…

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.