FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW91FA084 · Piper PA-28-140

26 May 1991 · Folsom, LA, United States

Piper PA-28-140 · Accident: loss of control in flight while maneuvering

From 0R9 · Hammond, LA to an unrecorded destination

Report a problem

Event

NTSB case
FTW91FA084
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
1 · 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-28-140

Aircraft type
Piper PA-28
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
N6181W
Onboard fatalities
Unknown
Route
From 0R9 · Hammond, LATo not recorded
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
Maneuvering
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 control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Stall, inadvertent

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

NTSB narrative

THE STUDENT PILOT HAD NOTIFIED HIS BROTHER TO PHOTOGRAPH THE LOW ALTITUDE MANEUVERS OVER HIS RESIDENCE. MULTIPLE WITNESSES REPORTED THAT THE AIRPLANE WAS OBSERVED TO BE OPERATING AT A LOW ALTITUDE ESTIMATED TO BE 40 TO 100 FEET ABOVE GROUND LEVEL. ON A RIGHT TURN BACK TO THE BROTHER'S LOCATION CONTROL OF THE AIRPLANE WAS LOST. THE AIRPLANE, WHICH WAS BANKED IN EXCESS OF 45 DEGREES, STALLED, ROLLED RIGHT TO AN INVERTED POSITION, AND IMPACTED THE TERRAIN IN AN 80 DEGREE NOSE LOW ATTITUDE.

Probable cause

THE INADVERTENT STALL. FACTORS WERE THE PILOT'S POOR JUDGEMENT IN PERFORMING THE BUZZING MANEUVER AND HIS LACK OF EXPERIENCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW91FA084
Event ID
20001212X17004
Case number
FTW91FA084
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: fe808eb245ac6ce70ea6fb27ad7eaa59b037ad98b3be14cde95ec74feb07b94c; retrieved 2026-09-21T01:48:02.917Z.