# Incident 20110529009299I: Beech A36, Columbus, IN, May 29, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 29, 2011, 19:47 local time
- Place: Columbus, IN
- Airport: Columbus Municipal
- Damage: No damage
- Phase of flight: Climb
- Operating rules: General operating rules (Part 91)
- Location: 39.2619° N, 85.8963° W: Placed by OpenAirDocs at COLUMBUS MUNI (BAK), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.2619&lon=-85.8963&mi=10
- Aircraft: N67CD, registered now (https://openairdocs.org/aircraft/N67CD) (OpenAirDocs)
- Registry model: Beech A36 (registry code 1151604, https://openairdocs.org/model/beech-a36) (OpenAirDocs)
- Registry engine: Continental IO-550 series (registry code 17042, https://openairdocs.org/engine/continental-io-550-series) (OpenAirDocs)
- Reported make and model: BEECH A36
- Reported engine: CONT MOTOR IO-550 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/20110529009299I

## Narrative

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

THE OWNER/PILOT STATED THAT ON THIS FLIGHT FROM KIND TO KLEX, WHILE CLIMBING THROUGH 3500 FEET TO 5000 FEET, THE BUS VOLTAGE ANNUNCIATOR ILLUMINATED, INDICATING LOSS OF ALTERNATOR POWER. CONDITIONS WERE VFR. THE PILOT TOLD ATC HE INTENDED TO MAKE A PRECAUTIONARY LANDING. HE STATED THAT ATC INFORMED HIM HE HAD JUST CROSSED OVER AN AIRPORT. HE REPLIED THAT HE SAW IT, KNEW IT WAS COLUMBUS (KBAK), AND WOULD LAND THERE. ATC ASKED IF HE WANTED TO DECLARE AN EMERGENCY AND HE STATED HE DID NOT. HE MADE AN UNEVENTFUL LANDING AT KBAK. A LOCAL MECHANIC WAS CALLED TO CHECK OUT THE AIRCRAFT. THE MECHANIC STATED THAT THE PILOT SAID HE CYCLED THE ALTERNATOR SWITCH, AND THE SYSTEM OPERATED NORMALLY ON THE GROUND. THE MECHANIC INSPECTED THE AIRCRAFT, BUT OBSERVED NO REASON FOR THE FAILURE. HE SUSPECTED A FAULTY REGULATOR. THE AIRCRAFT WAS FLOWN TO ITS BASE AT LEXINGTON, WHERE THE OWNER ARRANGED FOR HIS MECHANIC TO CONDUCT AN INVESTIGATION OF THE SYSTEM, AND REPLACE THE REGULATOR.

## Other reports on N67CD (3)

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

- [Accident 20230923016089A](https://openairdocs.org/incident/20230923016089A), Sep 23, 2023: Beech A36 (N67CD), El Dorado, AR, Substantial damage. Aircraft departed from gulf shores, al (kjka) airport, enroute to sundance airport, ok (khsd). While enroute at approximately 10,000FT and 30 miles southeast…
- [Incident 20200803012639I](https://openairdocs.org/incident/20200803012639I), Aug 3, 2020: Beech A36 (N67CD), Sioux City, IA, Minor damage. Pilot stated that he had made a flight from spencer, Iowa (spw) to Sioux City, Iowa (sux) he mentally went through his pre landing checklist and thought that…
- [Accident 20180629008909A](https://openairdocs.org/incident/20180629008909A), Jun 29, 2018: Beech A36 (N67CD), Spencer, IA, Substantial damage. Landing approach to runway 18 in strong and gusting winds from 180. Communicating with departing and arriving traffic for same runway. Focusing on aircraft…

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.