# Accident 20000109003669A: Piper PA32300, Sweeney, TX, January 9, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 9, 2000, 18:45 local time
- Place: Sweeney, TX
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 29.0405° N, 95.6890° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=29.0405&lon=-95.6890&mi=10
- Aircraft: N8954N, registered now (https://openairdocs.org/aircraft/N8954N) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- Reported engine: LYC IO540K1A5
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 980 total, 48 in this make and model, 82 in the last 90 days
- NTSB investigation: [NTSB FTW00LA059](https://openairdocs.org/ntsb/FTW00LA059) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000109003669A

## Narrative

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

(.23) ON 01/09/00 AT 1830 CST, N8954N, PIPER PA-32-300 WAS SUBSTANTIALLY DAMAGED WHEN IT IMPACTED THE TERRAIN DURING A FORCED LANDING DUE TO LOSS OF POWER. THE FLIGHT INSTRUCTOR AND STUDENT PILOT WERE NOT INJURIED.  THE AIRCRAFT SUBSTAINED SUBSTANTIAL DAMAGE.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             THE AIRPLANE WAS IN LEVEL CRUISE FLIGHT DURING DARK NIGHT CONDITIONS WHEN THE 'ENGINE STOPPED.' THE INSTRUCTOR ELECTED TO MAKE A FORCED LANDING TO A FIELD.  ON FINAL APPROACH, THE INSTRUCTOR NOTICED WHAT APPEARED TO BE POWER LINES.  THE INSTRUCTOR BANKED THE AIRPLANE TO PARALLEL THE POWER LINES AND ROTATED THE AIRPLANE TO A NOSE HIGH PITCH ATTITUDE FOR TOUCHDOWN.  THE TOUCHDOWN WAS MADE ON BOTH MAIN WHEELS; HOWEVER, 'THE NOSE OF THE AIRCRAFT CAME DOWN HARD,' AND THE AIRPLANE SKIDDED TO A STOP.  AN FAA INSPECTOR SUPERVISED A 35-MINUTE TEST RUN OF THE ENGINE AND FOUND NO ANOMALIES.

## 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 FTW00LA059](https://openairdocs.org/ntsb/FTW00LA059), Jan 10, 2000: Piper PA-32-300 (N8954N), Sweeney, TX, substantial damage. Probable cause: The pilot's excessive flare resulting in a hard landing. Factors were the loss of engine power for undetermined reasons, the power lines on final approach and the dark night conditions.

## Other reports on N8954N (1)

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

- [Incident 19861029066819I](https://openairdocs.org/incident/19861029066819I), Oct 29, 1986: Piper PA32300 (N8954N), Danbury, TX, Minor damage. Aircraft slid off the end of a wet grass runway.

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.