# Incident 19861009062069I: Beech B50, Tulsa, OK, October 9, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 9, 1986, 19:10 local time
- Place: Tulsa, OK
- Airport: Tulsa International
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.1984° N, 95.8881° W: Placed by OpenAirDocs at TULSA INTL (TUL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.1984&lon=-95.8881&mi=10
- Aircraft: N550G, a cancelled registration (https://openairdocs.org/deregistered/N550G-2003-10-25) (OpenAirDocs)
- Registry model: Beech B50 (registry code 1152506, https://openairdocs.org/model/beech-b50) (OpenAirDocs)
- Registry engine: Lycoming GO-435C&D series (registry code 41521, https://openairdocs.org/engine/lycoming-go-435c-d-series) (OpenAirDocs)
- Reported make and model: BEECH B50
- Fatal injuries: 0
- Pilot flight hours: 1,800 total, 150 in this make and model, 60 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19861009062069I

## Narrative

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

FAILED TO LOWER GEAR OR CHECK INDICATOR LIGHTS BEFORE LANDING. LANDED GEAR UP.

## Other reports on N550G (2)

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

- [Accident 20020706017279A](https://openairdocs.org/incident/20020706017279A), Jul 6, 2002: Beech B50 (N550G), Canton, AL, No damage. (-23) The pilot stated that his approach to runway 26 at clanton county airport was normal, until the last few minutes of flight. He attempted a go around but…
- [Incident 20010215003229I](https://openairdocs.org/incident/20010215003229I), Feb 15, 2001: Beech B50 (N550G), Raleigh-Durham, NC. (-23) N550G landed long at night on runway 32 at rdu (3,569 ft) and ran off the end of the runway. No injury to aircraft or personnel.

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.