# Accident 19890216002019A: Gulstm 500U, Daytona Beach, FL, February 16, 1989

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 16, 1989, 16:44 local time
- Place: Daytona Beach, FL
- Airport: Daytona Beach Regional
- Damage: Substantial damage
- Phase of flight: To Aborted (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 29.1799° N, 81.0580° W: Placed by OpenAirDocs at DAYTONA BEACH INTL (DAB), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=29.1799&lon=-81.0580&mi=10
- Aircraft: N1010U, a cancelled registration (https://openairdocs.org/deregistered/N1010U-2014-09-08) (OpenAirDocs)
- Registry model: Aero Commander 500-U (registry code 0141108, https://openairdocs.org/model/aero-commander-500-u) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: GULSTM 500U
- Reported engine: LYC IO540E1A5
- People aboard: 4
- Fatal injuries: 0
- Pilot flight hours: 644 total, 81 in this make and model, 39 in the last 90 days
- NTSB investigation: [NTSB MIA89LA086](https://openairdocs.org/ntsb/MIA89LA086) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19890216002019A

## Narrative

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

PILOT REPORTED LOUD BANG IN REAR OF AIRCRAFT AND RESTRICTED ELEVATOR. ABORTED, GEAR UP. NO CONTROL SYSTEM DEFECTS.

## 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 MIA89LA086](https://openairdocs.org/ntsb/MIA89LA086), Feb 16, 1989: Aero Commander 500U (N1010U), Daytona Beach, FL, substantial damage. Probable cause: CONTROL MALFUNCTION OF UNDETERMINED CAUSE THAT MADE FURTHER FLIGHT INADVISABLE.

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.