FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN06LA061 · Piper PA-25-235

12 Apr 2006 · Smith Center, KS, United States

Piper PA-25-235 · Accident: loss of control in flight while maneuvering

From Smith Center Municipal Airport (K82) to an unrecorded destination

Report a problem

Event

NTSB case
DEN06LA061
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
Unknown
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-25-235

Aircraft type
Piper PA-25
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
N9886P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Smith Center Municipal Airport (K82), Smith Center, KSTo 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 137: Agricultural
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 · aerial application
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/mush
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

  • Pilot in command › Airspeed, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot said, "Everything seemed okay and I took off on runway 35 from the Smith Center Municipal Airport ... As I turned and headed east, I took out the notch of flaps, and the tail of the plane sank. The plane was flying poorly and felt like it was on the edge of a stall. The throttle and mixture were full forward, and the tachometer was indicating 2,700 rpm." The pilot said that when he put the notch of flaps back in, the airplane seemed to perform better. The pilot said, "With almost a full load [of chemical], I did not want to land back at the airport, so I proceeded to the field thinking that once I had sprayed a few passes and relieved some of the weight, the airplane would start flying better." The pilot said that as he came to the pasture, he was only able to climb the airplane to approximately 300 feet above ground level (agl). He circled the field a couple of times looking for power lines, trees, anything that might hinder spraying operations. The pilot made his first pass about 20 feet above the ground. After the pass, he made a wide right turn. The airplane would not hold altitude in the turn. Attributing the poor performance to the airplane's weight, the pilot maneuvered to make the next pass over the middle of the field so that he could "dump some of the weight." He made a second pass over the field followed by a wide left turn toward the southwest and the airport. On completion of the turn, the pilot noted he had descended to approximately 40 feet agl. In front of him were power lines that he was now lower than and had to clear in order to return to the airport. The pilot said he started a climb about three-quarters of a mile from the power lines. The airplane was approximately 40 feet agl it "went into a stall." The pilot said he leveled the wings and prepared for the crash. The airplane hit the ground flat and slid approximately 100 feet before striking a pasture fence. An examination of the airplane revealed no anomalies. The density altitude at the time of the accident was 2,489 feet. The airplane's gross weight at the time of the accident was determined as approximately 2,993 pounds. Specifications for the PA-25-235 show an empty weight of 1,288 pounds and a maximum takeoff weight of 2,900 pounds. Civil Aeronautics Manual (CAM) 8, paragraph 8.10-4 (b) "Maximum Weight" states that establishing a maximum weight for an agricultural aircraft is not required.

Probable cause

the pilot's failure to maintain adequate airspeed which resulted in an inadvertent stall/mush, and subsequent impact with the field and fence. A factor contributing to the accident was the pilot's inadequate flight planning and preparation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN06LA061
Event ID
20060412X00429
Case number
DEN06LA061
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, coordinates. 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: 5936522081c7de5bba3939b7fbe0ff3d3f5423762c9134868aeb191cac700812; retrieved 2026-09-22T05:00:27.952Z.