# Incident 20030223003129I: Beech 1900D, Dodge City, KS, February 23, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 23, 2003, 18:50 local time
- Place: Dodge City, KS
- Airport: Dodge City Regional Airport
- Damage: Minor damage
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: Air carrier (Part 121)
- Operator: GLBA
- Location: 37.7631° N, 99.9654° W: Placed by OpenAirDocs at DODGE CITY RGNL (DDC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.7631&lon=-99.9654&mi=10
- Aircraft: N249GL, a cancelled registration (https://openairdocs.org/deregistered/N249GL-2007-11-01) (OpenAirDocs)
- Registry model: Beech 1900D (registry code 1154162, https://openairdocs.org/model/beech-1900d) (OpenAirDocs)
- Registry engine: Pratt & Whitney PT6A series (registry code 52032, https://openairdocs.org/engine/pratt-whitney-pt6a-series) (OpenAirDocs)
- Reported make and model: BEECH 1900D
- Reported engine: PWA PT6A67D
- Pilot flight hours: 1,800 total, 900 in this make and model, 150 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030223003129I

## Narrative

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

(-23) FLIGHT LANDED AT DDC, AFTER EXITING RUNWAY AND TAXIING TO RAMP, THE AIRCRAFT ATTEMPTED TO TURN ON THE RAMP AND EXITED THE TAXIWAY. LEFT PROPELLER STRUCK TAXI LIGHT. AT THE TIME OF THE INCIDENT BRAKING ACTION ON THE RUNWAY WAS REPORTED AS POOR. WITNESS REPORTED TAXI SPEED OF THE AIRCRAFT WAS EXTREMELY SLOW AND THE AIRCRAFT CAME TO A COMPLETE STOP BEFORE MAKING THE TURN.

## Other reports on N249GL (1)

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

- [Incident 20021102034669I](https://openairdocs.org/incident/20021102034669I), Nov 2, 2002: Beech 1900D (N249GL), Mccook, NE, Substantial damage. (-23) During a night, IFR runway 12 approach at mck, gl 5035'S left wing tip contacted the runway. A go-around was executed, unable to see the runway on 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.