# Accident 20110422009229A: Beech 58, Topeka, KS, April 22, 2011

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 22, 2011, 12:10 local time
- Place: Topeka, KS
- Damage: Destroyed
- Phase of flight: Other, Specify
- Operating rules: General operating rules (Part 91)
- Location: 39.1231° N, 95.5881° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.1231&lon=-95.5881&mi=10
- Aircraft: N580EA, a cancelled registration (https://openairdocs.org/deregistered/N580EA-2018-01-26) (OpenAirDocs)
- Registry model: Beech 58 (registry code 1152740, https://openairdocs.org/model/beech-58) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH 58
- Reported engine: CONT MOTOR IO 520 SERIES
- People aboard: 4
- Fatal injuries: 4
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 420 total, 20 in this make and model
- NTSB investigation: [NTSB CEN11FA302](https://openairdocs.org/ntsb/CEN11FA302) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20110422009229A

## Narrative

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

ON APRIL 22, 2011, AT APPROXIMATELY 1210 P.M. LOCAL TIME (1710 UTC), A PRIVATE PILOT WAS INVOLVED IN AN AIRCRAFT ACCIDENT RESULTING FROM AN APPARENT LOSS OF AIRCRAFT CONTROL UPON EXECUTING A PUBLISHED MISSED APPROACH PROCEDURE FROM THE LOCALIZER/BACKCOURSE RUNWAY 31 APPROACH AT THE TOPEKA PHILIP BILLARD AIRPORT (TOP), TOPEKA, KANSAS.  THE AIRCRAFT INVOLVED IN THIS ACCIDENT IS A PRIVATELY OWNED AND OPERATED BEECHCRAFT BE-58 BARON.  INSTRUMENT METEOROLOGICAL CONDITIONS (IMC) PREVAILED AT THE TIME OF THE AIRCRAFT ACCIDENT; APPROXIMATE 500 FT CEILINGS AND 2 ½ MILES VISIBILITY IN MIST WERE REPORTED VIA THE AUTOMATED WEATHER OBSERVATION SYSTEM.  AN INSTRUMENT FLIGHT PLAN WAS FILED FROM THE SCOTT CITY MUNICIPAL AIRPORT (KTQK), SCOTT CITY, KANSAS, TO THE TOPEKA PHILIP BILLARD AIRPORT (KTOP), TOPEKA, KANSAS.  CERTIFIED AUDIO RECORDINGS FROM THE KANSAS CITY AIR ROUTE TRAFFIC CONTROL CENTER (ZKC ARTCC) AND THE TOPEKA PHILIP BILLARD AIR TRAFFIC CONTROL TOWER, THE AIRMAN WAS CLEARED TO DESCEND AND INTERCEPT A GROUND-BASED NAVIGATIONAL COURSE THAT WOULD ESTABLISH THE AIRCRAFT ON THE FINAL APPROACH COURSE FOR THE LOCALIZER/BACKCOURSE RUNWAY 31 APPROACH.  THE AIRCRAFT FAILED TO INTERCEPT THE DESIGNATED RADIAL AND SUBSEQUENTLY FLEW THROUGH THE FINAL APPROACH COURSE; ADDITIONAL RADAR VECTORS WERE PROVIDED TO ENABLE THE AIRCRAFT TO RE-ESTABLISH ITSELF ON THE FINAL APPROACH COURSE.  SHORTLY THEREAFTER, THE AIRMAN WAS INSTRUCTED TO CONTACT THE TOPEKA PHILIP BILLARD AIR TRAFFIC CONTROL TOWER.  UPON ESTABLISHING INITIAL CONTACT WITH THE AIR TRAFFIC CONTROL TOWER, THE AIRMAN WAS REQUESTED TO REPORT FLYING OVER THE FINAL APPROACH FIX, WHICH THE AIRMAN DID NOT ACCOMPLISH.  PER THE AUDIO RECORDINGS, SUBSEQUENT COMMUNICATION BETWEEN THE AIRMAN AND THE TOPEKA PHILIP BILLARD AIR TRAFFIC CONTROL TOWER INDICATED THAT THE AIRMAN WAS NOT ABLE TO COMPLETE THE LOCALIZER/BACKCOURSE INSTRUMENT APPROACH DUE TO THE AIRCRAFT BEING WEST OF THE FINAL APPROACH COURSE; THE AIRMAN REQUESTED A CIRCLING APPROACH.  PRIMARILY DUE TO THE LOW CLOUDS AND VISIBILITY, A CIRCLING APPROACH MANEUVER WAS NOT AVAILABLE AND AIR TRAFFIC CONTROL PROVIDED THE AIRMAN WITH THE NECESSARY MISSED APPROACH INSTRUCTIONS.  SUBSEQUENT COMMUNICATION BETWEEN THE AIRCRAFT AND TOPEKA PHILIP BILLARD AIR TRAFFIC CONTROL TOWER REVOLVED AROUND THE AIRMAN'S REQUEST FOR THE GPS 36 APPROACH; MISSED APPROACH PROCEDURES WERE CONFIRMED AND THE AIRCRAFT WAS INSTRUCTED TO CONTACT ZKC ARTCC.  CERTIFIED AUDIO RECORDINGS OVER THE NEXT SEVERAL MINUTES DOCUMENT BOTH ZKC ARTCC AND TOPEKA PHILIP BILLARD AIR TRAFFIC CONTROL TOWER ATTEMPTING TO ESTABLISH COMMUNICATION WITH THE AIRCRAFT AS NO ADDITIONAL TRANSMISSIONS OR DISTRESS CALLS WERE RECEIVED.  SEVERAL MINUTES LATER THE AIRCRAFT ACCIDENT SITE WAS LOCATED APPROXIMATELY 3 MILES NORTHEAST OF THE TOPEKA PHILIP BILLARD AIRPORT IN A DOWN-SLOPING HARVESTED CORN FIELD.  INITIAL ACCIDENT SITE INVESTIGATION OF THE DEBRIS PATTERN, GROUND SCARRING AND IMPACT CRATER WERE ALL INDICATIVE OF THE AIRCRAFT IMPACTING THE GROUND AT A RELATIVELY HIGH ANGLE OF BANK AND VELOCITY.  FURTHER INVESTIGATION DID NOT REVEAL ANY ABNORMAL AIRCRAFT FLIGHT CONTROL OR ENGINE ANOMALIES; POST-IMPACT FIRE AND SUBSEQUENT ENGINE EXCAVATION REVEALED THE PRESENCE OF SUBSTANTIAL FUEL.  THE AIRMAN AND THREE PASSENGERS SUSTAINED FATAL INJURIES.  THE LOCALIZER/BACKCOURSE APPROACH HAD BEEN RECENTLY FLIGHT-CHECKED WITH NO ANOMALIES NOTED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN11FA302](https://openairdocs.org/ntsb/CEN11FA302), Apr 22, 2011: Beech 58 (N580EA), Topeka, KS, destroyed, 4 fatal. Probable cause: The pilot failed to maintain control of the airplane while maneuvering in instrument meteorological conditions. Contributing to the accident was the pilot’s minimal experience flying in actual…

## Other reports on N580EA (2)

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

- [Incident 20040823021339I](https://openairdocs.org/incident/20040823021339I), Aug 23, 2004: Beech 58 (N580EA), Omaha, NE. (-23) On August 23, 2004, at 0832 CDT, the pilot of a Beechcraft 58, N580EA, operating as flight ELT 311 under air carrier certificate JEMA166F to watertown,…
- [Incident 19970916033109I](https://openairdocs.org/incident/19970916033109I), Sep 16, 1997: Beech 58 (N580EA), Neligh, NE, Minor damage. Narrative: capt. james departed oma for 4V9 at 0715 CDT. At that time, the winds for 4V9 were southeast at about 8-10 KTS. And forecasted to remain the same.…

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.
