# Incident 20061012022879I: Gulstm 500B, Wichita, KS, October 12, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 12, 2006, 21:10 local time
- Place: Wichita, KS
- Airport: Colonel James Jabara Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: Air taxi and commuter (Part 135)
- Operator: ZJWA
- Location: 37.7476° N, 97.2211° W: Placed by OpenAirDocs at COLONEL JAMES JABARA (AAO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.7476&lon=-97.2211&mi=10
- Aircraft: N516DT, registered now (https://openairdocs.org/aircraft/N516DT) (OpenAirDocs)
- Registry model: Aero Commander 500-B (registry code 0141106, https://openairdocs.org/model/aero-commander-500-b) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: GULSTM 500B
- People aboard: 1
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20061012022879I

## Narrative

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

(-23) ON OCTOBER 12, 2006, AT 2110 LOCAL TIME, AIRCRAFT N516DT NOSE LANDING GEAR TIRE BLEW ON LANDING CAUSING MINOR DAMAGE TO THE WHEEL ASSEMBLY.

## Other reports on N516DT (2)

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

- [Accident 20200327009259A](https://openairdocs.org/incident/20200327009259A), Mar 27, 2020: Aero Commander 500-B (N516DT), Opalocka, FL, Substantial damage. Pilot failed to extend the gear prior to landing. Aircraft lower surface contacted the runway. Pilot was able to get aircraft back into the air. Pilot then…
- [Incident 20060417004499I](https://openairdocs.org/incident/20060417004499I), Apr 17, 2006: Gulstm 500B (N516DT), Kansas City, MO, Minor damage. (-23) During an approach to land, the nose wheel position light indicated a malfunction. After trouble shooting the system, the pilot made two "fly-bys" the…

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.