# Incident 19890826058269I: Boeing 737301, Dayton, OH, August 26, 1989

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 26, 1989, 12:05 local time
- Place: Dayton, OH
- Airport: James M Cox Dayton International
- Damage: Minor damage
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: Air carrier (Part 121)
- Operator: USAA
- Location: 39.9023° N, 84.2194° W: Placed by OpenAirDocs at JAMES M COX DAYTON INTL (DAY), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.9023&lon=-84.2194&mi=10
- Aircraft: N339US, a cancelled registration (https://openairdocs.org/deregistered/N339US-2003-11-19) (OpenAirDocs)
- Registry model: Boeing 737-301 (registry code 138447R, https://openairdocs.org/model/boeing-737-301) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: BOEING 737301
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 6,035 total, 1,920 in this make and model, 206 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19890826058269I

## Narrative

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

STABILIZER STRUCK JETWAY WHILE TAXIING OUT OF GATE AREA. MARSHAL GIVING INSTRUCTIONS. JETWAY OUT OF POSITION.

## Other reports on N339US (2)

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

- [Incident 19920223015669I](https://openairdocs.org/incident/19920223015669I), Feb 23, 1992: Boeing 737301 (N339US), Los Angeles, CA. Cleared and landed on runway 24R. Another aircraft made a go around as it also assigned 24R sidestep to 24L.
- [Incident 19890110008739I](https://openairdocs.org/incident/19890110008739I), Jan 10, 1989: Boeing 737301 (N339US), West Palm Beach, FL. Smoke from cabin and cockpit ducting. Nose wheel APU warning. Passengers evacuated. Suspect oil seal leak.

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.
