# Accident 20050208005129A: Piper PA32300, Concord, NC, February 8, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 8, 2005, 18:12 local time
- Place: Concord, NC
- Airport: Concord Regional Airport
- Damage: Substantial damage
- Phase of flight: Forced Landing
- Operating rules: Air taxi and commuter (Part 135)
- Operator: X6PA
- Location: 35.3956° N, 80.7056° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.3956&lon=-80.7056&mi=10
- Aircraft: N364BW, a cancelled registration (https://openairdocs.org/deregistered/N364BW-2007-01-30) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- Reported engine: LYC IO540K1A5
- Fatal injuries: 0
- NTSB investigation: [NTSB ATL05LA049](https://openairdocs.org/ntsb/ATL05LA049) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050208005129A

## Narrative

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

(-23) THE AIRCRAFT LOST POWER ON FINAL. THIS OCCURRED 2 LEGS AFTER THE AIRCRAFT WAS RELEASED FROM MAINTENANCE FOR REPAIRS TO FIREWALL AND PROP RESULTING FROM A GEAR COLLAPSE SOFT FIELD EMERGENCY LANDING CLASSIFIED AS AN ACCIDENT DUE TO FIREWALL DAMAGE. THE REASON FOR THE EMERGENCY WAS DUE TO THE PILOT UNABLE TO START THE ENGINE AFTER THE ENGINE QUIT AT 6000FT. THE AIRCRAFT ON 02/08/2005 WAS TOPPED OFF AT ILM, THE AIRCRAFT DEPARTED WITH THE FUEL SELECTED TO THE RH MAIN, AFTER LEVEL OFF AT 6000 FT THE LH MAIN WAS SELECTED AND REMAINED IN THAT POSITION UNTIL THE ENGINE LOST POWER ON FINAL TO JQF. THE PILOT SWITCHED BACK TO THE RH MAIN THE ENGINE SEEMED TO WANT TO START AT FIRST BUT IT DID NOT. THE PILOT THEN SELECTED RH AUX SHORTLY AFTER THE AIRCRAFT IMPACTED TREES AND THE GROUND. IT CAME TO REST IN A GRAVEL PIT 1 MILE NORTH AND 1/4 MILE EAST OF RUNWAY 20 JQF. FUEL SYSTEM COMPONENTS AREA BEING TESTED AND THIS REPORT IS EXPECTED TO BE AMENDED.

## 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 ATL05LA049](https://openairdocs.org/ntsb/ATL05LA049), Feb 8, 2005: Piper PA-32-300 (N364BW), Concord, NC, substantial damage. Probable cause: The loss of engine power due to the failure of the fuel pump which resulted in fuel starvation.

## Other reports on N364BW (1)

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

- [Accident 20050106000139A](https://openairdocs.org/incident/20050106000139A), Jan 6, 2005: Piper PA32300 (N364BW), Polkton, NC, Substantial damage. (-23) Pilot reported to ATC the engine failed during flight at approximately 6,000 ft MSL during an IFR flight from myr to jqf. Pilot noted no fuel in rt main…

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.