# Accident 19991103030999A: Piper PA28235, Raleigh-Durham, NC, November 3, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 3, 1999, 23:18 local time
- Place: Raleigh-Durham, NC
- Airport: Raleigh-Durham International
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- 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: N8515W, registered now (https://openairdocs.org/aircraft/N8515W) (OpenAirDocs)
- Registry model: Piper PA-28-235 (registry code 7102810, https://openairdocs.org/model/piper-pa-28-235) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA28235
- People aboard: 2
- Fatal injuries: 0
- NTSB investigation: [NTSB MIA00LA020](https://openairdocs.org/ntsb/MIA00LA020) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19991103030999A

## Narrative

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

(.19) ON NOVEMBER 3, 1999, AT ABOUT 1815 EASTERN STANDARD TIME, A PIPER PA-28-235, N8515W, REGISTERED TO A PRIVATE OWNER EXPERIENCED AN ON-GROUND COLLISION WITH A FIXED OBJECT AT THE RALEIGH-DURHAM INTERNATIONAL AIRPORT, RALEIGH, NORTH CAROLINA. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED. THE AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE. THE PRIVATE-RATED PILOT AND PRIVATE-RATED PILOT/PASSENGER REPORTED NO INJURIES. THE FLIGHT ORIGINATED FROM CONCORD, NORTH CAROLINA, ABOUT 1 HOUR BEFORE THE ACCIDENT. THE PILOT STATED HE MADE A VISUAL APPROACH TO RUNWAY 23 RIGHT, AND BACKED THE APPROACH UP WITH THE ILS. ON TOUCHDOWN THE AIRPLANE VEERED TO THE LEFT. HE STATED HE HAD NOT APPLIED ANY BRAKES. THE AIRPLANE DEPARTED THE RUNWAY INTO THE GRASS. HE APPLIED BRAKES, REGAINED DIRECTIONAL CONTROL, AND MANEUVERED THE AIRPLANE BACK ON THE RUNWAY. HE CONTACTED THE TOWER AND INFORMED THEM THAT HE DID NOT KNOW WHAT HAD HAPPENED. HE STATED THE TOWER ASKED HIM IF HE HAD A BIRD STRIKE. HE STATED HE DID NOT KNOW. HE EXITED THE RUNWAY ONTO THE TAXIWAY AND CONTACTED GROUND. HE LOOKED OUT THE WINDOW TO HIS LEFT AND SAW A DENT IN THE WING. HE INFORMED GROUND CONTROL THAT HE KNEW HE HAD HIT SOMETHING. HE TAXIED TO THE RAMP WITHOUT FURTHER INCIDENT. (-23)AFTER LANDING ON RUNWAY 23R THE PILOT REPORTED A BIRD STRIKE ON THE LEFT WING.  HE STATED THAT THE STRIKE SPUN THE AIRCRAFT AROUND ON THE GROUND.  THE CFR PERSONNEL INSPECTED THE AREA FOR EVIDENCE OF A STRIKE.  THEY DISCOVERED THE "TAXIWAY B" SIGN HAD BEEN DESTROYED.  THE DAMAGE ON THE AIRCRAFT MATCHED WITH THE DAMAGE ON THE SIGN AND ALSO THE TIRE MARKS OF THE GROUND NEAR THE SIGN MATCHED THE AIRCRAFT WHEEL PATTERN.  THERE WAS NO EVIDENCE OF A BIRD/ANIMAL STRIKE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB MIA00LA020](https://openairdocs.org/ntsb/MIA00LA020), Nov 3, 1999: Piper PA-28-235 (N8515W), Raleigh, NC, substantial damage. Probable cause: The pilot's failure to maintain directional control on landing rollout for undetermined reasons. This resulted in the airplane veering off the runway and colliding with an airport sign.

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.