# Incident 20020424021719I: Bac AVRO146RJ85A, Dayton, OH, April 24, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 24, 2002, 18:15 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: MALA
- 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: N519XJ, a cancelled registration (https://openairdocs.org/deregistered/N519XJ-2007-06-19) (OpenAirDocs)
- Registry model: British Aerospace AVRO 146-RJ85A (registry code 1500097, https://openairdocs.org/model/british-aerospace-avro-146-rj85a) (OpenAirDocs)
- Registry engine: Alliedsign LF507-1F (registry code 02503, https://openairdocs.org/engine/alliedsign-lf507-1f) (OpenAirDocs)
- Reported make and model: BAC AVRO146RJ85A
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020424021719I

## Narrative

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

(-23) WHILE UNDER THE GUIDANCE OF A GROUND MARSHALER AND TWO WING WALKERS THE AIRCRAFT STRUCK A LIGHT POLE WITH THE RIGHT WINGTIP CAUSING MINOR DAMAGE TO THE AIRCRAFT.

## Other reports on N519XJ (2)

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

- [Incident 20060322003709I](https://openairdocs.org/incident/20060322003709I), Mar 22, 2006: Bac AVRO146RJ85A (N519XJ), Omaha, NE. (-23) N519XJ, avro-146-RJ85A, was being operated by mesaba airlines, as northwest flight 3635, between Omaha, NE. And minneapolis, MN. During take off from…
- [Incident 20050619013409I](https://openairdocs.org/incident/20050619013409I), Jun 19, 2005: Bac AVRO146RJ85A (N519XJ), Minneapolis, MN. (-23) Crew returned to msp following engine number #3 overspeed condition. Emergency was declared and engine was shut down. Aircraft landed without incident.

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.