Piper PA 25-235 accident near Arlington, Wisconsin, July 3, 2016
On July 3, 2016 at about 9:50 pm local time, a 1963 Piper PA 25-235, registered N6803Z, was substantially damaged in an accident during takeoff near Arlington, Wisconsin (Kazs Flying Service airport). It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to establish proper airspeed and angle-of-attack during takeoff with the airplane at its maximum gross weight in elevated density altitude and gusting tailwind conditions, which resulted in an aerodynamic stall.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 3, 2016 · about 9:50 pm local time
- Place
- Arlington, Wisconsin · Kazs Flying Service · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA 25-235, built 1963 · all PA 25-235s on the register
- Registration
- N6803Z · registry record · serial 25-2452
- Damage
- Substantial damage
- Flight
- Aerial application (crop spraying) flight · agricultural flying rules (Part 137)
The NTSB's narrative final · quoted from the NTSB record
The commercial pilot reported that he was conducting an agricultural application flight with the airplane at its maximum gross takeoff weight. He added that, after taking off toward the west, the airplane settled into a cornfield. He stated that there were no failures or malfunctions with the airplane preceding the accident, that the engine was running "fine," and that there were no flight control anomalies at the time of the accident. The pilot stated that the prevailing wind was from the east gusting to 18 knots, which resulted in a gusting tailwind during the takeoff. The density altitude was calculated to be about 3,000 ft. It is likely that the combined effects of the airplane operating at its maximum gross weight, the elevated density altitude, and the gusting tailwind resulted in the airplane becoming airborne at an airspeed that could not be maintained outside of ground effect. The pilot subsequently failed to maintain the proper angle-of-attack as he attempted to climb the airplane out of ground effect, which resulted in an aerodynamic stall.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during takeoff defining event
- Collision with terrain or object (not controlled flight into terrain) during takeoff
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
- Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High density altitude › Effect on operation
- Aircraft › Aircraft oper/perf/capability › Aircraft capability › Maximum weight › Not specified
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 9,850 hours in all; 9,700 in this make and model; 60 in the last 90 days; 60 in the last 30 days; 8,904 as pilot in command
- Last flight review: April 27, 2016
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: sngl
- Injury: minor injuries
The aircraft
- Airframe total time: 10,234.9 hours
- Last inspection: annual inspection, April 23, 2016; 70 hours since
- Maximum gross weight: 2,497 lb
- Seats: 1
- Landing gear: fixed
- Engine: Lycoming O-540-B4B5 (piston); 371 hours total
- Operator: Kazs Flying Service Ltd.
The flight
- Departed from: PVT Arlington WI at 9:50 pm
- Destination: PVT Arlington WI
- Flight plan: none
- Runway 27, 2,500 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 090° at 10 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 5,500 ft
- Temperature: 75°F (24°C), dew point 52°F (11°C)
- Altimeter: 30.01 inHg
- Observation at 9:53 pm from MSN, 13 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on August 25, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 7 pages | View Download |
| 2 | Conversation Record - FAA Inspector | PDF, 1 page | View Download |
| 3 | Density Altitude Calculations | PDF, 2 pages | View Download |
| 4 | Weather Data - Dane County Regional Airport | PDF, 2 pages | View Download |
| 5 | FAA Pilot's Handbook of Aeronautical Knowledge - Excerpts | PDF, 6 pages | View Download |
| 6 | FAA Airplane Flying Handbook - Excerpt | PDF, 2 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
