# Accident 20080116010449A: Gulstm 500B, Tulsa, OK, January 16, 2008

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 16, 2008, 22:43 local time
- Place: Tulsa, OK
- Damage: Destroyed
- Phase of flight: Climb
- Operating rules: Air taxi and commuter (Part 135)
- Operator: ZJWA
- Location: 36.2258° N, 95.8894° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.2258&lon=-95.8894&mi=10
- Aircraft: N712AT, a cancelled registration (https://openairdocs.org/deregistered/N712AT-2009-10-01) (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
- Reported engine: LYC TIO540*
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 3,678 total, 0 in this make and model, 0 in the last 90 days
- NTSB investigation: [NTSB DFW08FA056](https://openairdocs.org/ntsb/DFW08FA056) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20080116010449A

## Narrative

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

(-23) AIRCRAFT DEPARTED TULSA INTERNATIONAL (TUL) AIRPORT AT 2240HRS CST ENROUTE TO WILEY POST (PWA). AFTER DEPARTURE TUL TOWER CALLED PILOT AND HE REPORTED A GYRO PROBLEM. TOWER GAVE THE PILOT A LEFT TURN HEADING 250 DEGREES, WITH AN ASSIGNED ALTITUDE OF 6,000FT DIRECT TO PWA. TOWER TRIED TO RECONTACT PILOT AFTER RADAR SHOWED N712AT TURNING RIGHT INTO A 360 DEGREE TURN. PILOT CONTINUED RIGHT TURN, LAST CALL AT 2243HRS "HE HAD ANOTHER PROBLEM NOW." NO FURTHER CONTACT; LEFT, RIGHT WING AND AFT CONTROL SURFACES SEPARATED FROM AIRCRAFT INFLIGHT PRIOR TO MAIN FUSELAGE IMPACTING TERRAIN. FURTHER INFORMATION MAY BE AVAILABLE AFTER ACCIDENT RECONSTRUCTION.

## 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 DFW08FA056](https://openairdocs.org/ntsb/DFW08FA056), Jan 17, 2008: Aero Commander 500B (N712AT), Tulsa, OK, substantial damage, 1 fatal. Probable cause: The pilot's loss of control due to spatial disorientation and the pilot exceeding the design/stress limits of the aircraft. Factors contributing to the accident were the pilot's reported gyro…

## Other reports on N712AT (1)

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

- [Incident 20010802026719I](https://openairdocs.org/incident/20010802026719I), Aug 2, 2001: Gulstm 500B (N712AT), Peoria, IL, Minor damage. (-23) During night taxi operations, the pilot of N712AT, collided with a chain link fence in the ramp area, and sustained damage to the right wing tip lense…

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.