# Incident 20160619017669I: Beech 58, Dallas, TX, June 19, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 19, 2016, 13:06 local time
- Place: Dallas, TX
- Airport: Dallas Executive
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: Air taxi and commuter (Part 135)
- Operator: PE2A
- Location: 32.6813° N, 96.8688° W: Placed by OpenAirDocs at DALLAS EXEC (RBD), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.6813&lon=-96.8688&mi=10
- Aircraft: N711RX, a cancelled registration (https://openairdocs.org/deregistered/N711RX-2018-05-31) (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: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 8,000 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160619017669I

## Narrative

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

ON SUNDAY JUNE 19, 2016, A BEECHCRAFT MODEL 58 BARON EXPERIENCED A NOSE LANDING GEAR COLLAPSE WHILE LANDING ON RUNWAY 17 AT DALLAS EXECUTIVE AIRPORT (RBD), DALLAS TEXAS.  AN ONSITE INVESTIGATION WAS CONDUCTED AND THE NOSE GEAR RETRACTION MECHANISM WAS EXAMINED IN DETAIL.

THIS EXAMINATION SHOWED THE DRAG BRACE HAD FRACTURED IN THE TUBING; AT A POINT JUST FORWARD OF THE RIGHT ATTACH POINT. THE FRACTURE FACES DISPLAYED SURFACES THAT WERE INCLINED AT APPROXIMATELY 45-DEGREES TO THE AXIS OF THE SEPARATED PORTION OF THE TUBING, CONSISTENT WITH AN OVERLOAD EVENT.  ADDITIONALLY, SIGNS OF RUST WERE FOUND ALONG THE FRACTURE.  IT APPEARS THAT INTERNAL CORROSION LEAD TO AN UNDETECTED STRESS CRACK, CAUSING THE OVERLOAD CONDITION.

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.