# Incident 20010215003229I: Beech B50, Raleigh-Durham, NC, February 15, 2001

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 15, 2001, 18:32 local time
- Place: Raleigh-Durham, NC
- Airport: Raleigh-Durham International
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 35.8776° N, 78.7875° W: Placed by OpenAirDocs at RALEIGH-DURHAM INTL (RDU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.8776&lon=-78.7875&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
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 540 total, 70 in this make and model, 20 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20010215003229I

## Narrative

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

(-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.

## 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 19861009062069I](https://openairdocs.org/incident/19861009062069I), Oct 9, 1986: Beech B50 (N550G), Tulsa, OK, Minor damage. Failed to lower gear or check indicator lights before landing. Landed gear up.

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.