FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW97LA284 · Piper PA-32-300

26 Jul 1997 · Pine Bluff, AR, United States

Piper PA-32-300 · Accident: loss of engine power en route

From Pine Bluff Regional Airport, Grider Field (PBF) to C. A. Moore Airport (19M)

Report a problem

Event

NTSB case
FTW97LA284
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-32-300

Aircraft type
Piper PA-32
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N38800
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pine Bluff Regional Airport, Grider Field (PBF)To C. A. Moore Airport (19M), Lexington, MS
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Reason for occurrence undetermined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After takeoff, at 4,000 feet MSL, the airplane's engine 'started running rough.' The pilot contacted Little Rock approach control and reported that he was unable to maintain power, and was returning to Pine Bluff. He was not able to reach Pine Bluff and attempted to land on a farm maintained road leading to a rice field. The pilot was unable to stop the airplane, and it contacted the levee surrounding the rice field, which resulted in separation of the main landing gear. An engine run was performed, and an FAA inspector that attended the run reported that the engine, 'started easily and quickly, it ran smoothly from idle to max rpm in a satisfactory manner. There did not appear to be anything to cause a rough running engine.'

Probable cause

loss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW97LA284
Event ID
20001208X08394
Case number
FTW97LA284
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 981b022ea9c3c21e22e9d77bfdbcf7e4074ad122993f8cddbc6b0ba4a4d4e6bd; retrieved 2026-09-21T21:18:27.948Z.