# Accident 20030617011979A: Piper PA32300, Fort Mill, SC, June 17, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 17, 2003, 22:39 local time
- Place: Fort Mill, SC
- Damage: Substantial damage
- Phase of flight: Initial Approach-IFR
- Operating rules: Air taxi and commuter (Part 135)
- Operator: X6PA
- Location: 35.0073° N, 80.9484° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.0073&lon=-80.9484&mi=10
- Aircraft: N685BW, a cancelled registration (https://openairdocs.org/deregistered/N685BW-2012-09-25) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- Reported engine: LYC IO540K1A5
- Fatal injuries: 0
- Pilot flight hours: 1,250 total, 20 in this make and model, 60 in the last 90 days
- NTSB investigation: [NTSB ATL03LA108](https://openairdocs.org/ntsb/ATL03LA108) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030617011979A

## Narrative

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

(-23) PILOT REPORTED THAT WHEN TURNING TO INTERCEPT THE LOCALIZER FOR RUNWAY HE HEARD A LOUD BANG AND THE ENGINE QUIT. HE DECLARED AN EMERGENCY AND TRIED SEVERAL RESTARTS. IT IS UNDETERMINED AS TO WHY THE ENGINE HAD STOPPED AT THIS TIME.

## 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 ATL03LA108](https://openairdocs.org/ntsb/ATL03LA108), Jun 18, 2003: Piper PA-32-300 (N685BW), Fort Mill, SC, substantial damage. Probable cause: The pilot's mismanagement of the fuel supply, which resulted in fuel starvation and the subsequent loss of engine power.

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.