Piper PA-36-375 accident near Cambridge, Nebraska, July 23, 2011
On July 23, 2011 at about 11:38 am local time, a Piper PA-36-375, registered N3963E, was substantially damaged in an accident during takeoff near Cambridge, Nebraska (Cambridge Municipal Airport). It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to reset the engine's mixture control lever to the full rich position prior to takeoff.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 23, 2011 · about 11:38 am local time · cases in 2011
- Place
- Cambridge, Nebraska · Cambridge Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-36-375 · all PA-36-375s on the register
- Registration
- N3963E · no longer on the register · serial 36-7902029
- 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 pilot was departing on the first agricultural application flight of the day. He said that as he taxiing, he noticed the engine temperature rising, so he leaned the mixture. He completed his engine run-up and departed. He said that as the airplane was accelerating down the runway, he noticed the airplane was not developing enough power, but he had used up most of the runway and could not abort the takeoff. During climb, the airplane experienced a degrade in performance and struck terrain about 600 feet from the airport. The impact collapsed the landing gear and caused substantial damage to the airframe and elevator. The pilot reported that he inadvertently departed with the engine's mixture control lever at the halfway leaned setting. The pilot reported that there were no mechanical anomalies with the airplane, and the accident could have been prevented if he had used a checklist.
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
- Miscellaneous/other during prior to flight
- Loss of engine power (partial) during takeoff defining event
- Off-field or emergency landing during initial climb
- Collision with terrain or object (not controlled flight into terrain) during initial climb
- Landing gear collapse during post (impact)
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Aircraft › Aircraft power plant › Engine controls › Mixture control › Not used/operated other cases naming the engine
- Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land
- Flight time: 480 hours in all; 198 in this make and model; 99 in the last 90 days; 63 in the last 30 days; 438 as pilot in command
- Last flight review: October 19, 2010
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: sngl
- Injury: no injuries
The aircraft
- Airframe total time: 5,670 hours
- Last inspection: annual inspection, December 15, 2010
- Maximum gross weight: 4,800 lb
- Seats: 1
- Landing gear: fixed
- Engine: Lycoming IO-720 (piston); 0 hours total
The flight
- Departed from: CSB Cambridge NE at 11:38 am
- Destination: CSB Cambridge NE
- Flight plan: none
- Runway 32, 4,098 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 230° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 63°F (17°C)
- Altimeter: 29.85 inHg
- Observation at 11:53 am from KMCK, 21 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on September 15, 2011. 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, 11 pages | View Download |
| 2 | Pilot's Operating Handbook, Page 4-5 - Normal Checklist | PDF, 1 page | View Download |
| 3 | Map - Showing Airport and Impact Location | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N3963E: not on the register today · the record of its deregistration
- Piper PA-36 Pawnee Brave 99 registered today · the model family and its accident history
- Piper 44,854 aircraft on the register
- Engine: Lycoming IO-720 120 aircraft carry this series today · as the NTSB recorded it
- Cambridge Municipal · nearest airport
- Accidents and incidents in Nebraska 763 since 1982 · 108 in the last ten years
- Nebraska 2,950 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN11CA526.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.