Beechcraft 35 N5321E
1 September 2018 · Harrisville, Michigan, United States · Minor injuries
Summary
On 1 September 2018 at about 18:00 local time, a Beechcraft 35 registered N5321E was involved in an accident near Harrisville, Michigan, United States. 4 people were on board and one had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 18:00
- Classification
- Accident
- Location
- Harrisville, Michigan, United States
- Nearest airport
- Harrisville (5Y0)
- Coordinates
- 44.6656, -83.3072
- Aircraft
- Beechcraft 35
- Registration
- N5321E
- Category
- Airplane
- Year built
- 1959
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Harrisville → Detroit/Grosse Ile
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- CEN18TA374
People
1 person had minor injuries.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 4 | 0 | 0 | 1 | 3 |
Probable cause
The pilot’s delayed decision to abort the takeoff, which resulted in the loss of lateral control of the airplane and collision with trees at the end of the runway. Contributing to the accident was the pilot’s decision to depart with a center of gravity exceeding the aft limit and his inadequate preflight planning of the airplane’s weight and balance calculations and runway length data.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The private pilot reported that he completed a preflight inspection and an engine run-up with no anomalies noted. With about 20 gallons of fuel in the left tank, he taxied the airplane to the runway and extended the flaps to 10°. He started the takeoff roll and noted that the first 200 ft of the runway was soft and consisted of long grass, while the rest of the runway consisted of sand and weed patches. The pilot stated that during the takeoff roll, the nosewheel lifted off the runway around 300 ft and the main landing gear lifted off near midfield; he kept the airplane in ground effect. When the airplane was about 3/4 of the way down the runway, while still in ground effect, it would not gain altitude, and the left wing contacted trees. The pilot aborted the takeoff and attempted to stop the airplane in the grass but collided with trees at the end of the runway. The pilot reported that there were no mechanical malfunctions or anomalies with the engine or airplane that would have precluded normal operation. The pilot stated that he could not get the airplane up to speed because of the tall grass on the runway. A 32-second video of the takeoff attempt revealed the beginning of the takeoff roll on the grass runway. At 14 seconds, the airplane veered toward the left side of the runway until 22 seconds, when a loud noise was heard, likely the airplane colliding with trees. The airplane made a sharp right turn, then slid on the runway where it came to rest in trees at the end of the runway. It is not clear from the video if the airplane became airborne as the pilot stated. The calculated takeoff weight was 12 lbs under the maximum takeoff weight of 2,950 lbs. The calculated center of gravity was 0.07 inch beyond the aft limit of 84.7 inches aft of datum. In addition, the pilot stated after the accident that the data he had for the airport showed an additional 600 ft of available runway. Based on the available video evidence, the pilot's delayed decision to abort the takeoff did not leave enough runway length for the airplane to stop before colliding with trees at the end of the runway. It is likely that the airplane being loaded near the maximum gross weight and the airplane's center of gravity aft of the allowable limit contributed to its difficulty gaining adequate speed for takeoff. These factors, along with the pilot's incorrect runway length data, likely contributed to his delayed decision to abort the takeoff, as he expected the airplane to gain adequate speed for takeoff without difficulties.
Quoted verbatim from the NTSB record.
Other Beechcraft 35 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 17 Aug 2018 | Beechcraft 35 | Mayport, Florida, United States | - | No injuries | - |
| 30 Jan 2018 | Beechcraft 35 A33 | Helenwood, Tennessee, United States | - | Fatal | 1 |
| 26 Aug 2018 | Beechcraft 35 | Bowman, North Dakota, United States | - | Serious injuries | - |
| 8 Feb 2018 | Beechcraft 35 | Batesville, Arkansas, United States | - | No injuries | - |
| 24 Oct 2018 | Beechcraft 35 | State College, Pennsylvania, United States | - | Minor injuries | - |
| 4 Aug 2018 | Beechcraft 35 | Knox, Indiana, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 29 May 2018 | Hughes Aero PREDATOR "C" | Copemish, Michigan, United States | - | Serious injuries | - |
| 8 Jul 2018 | Best Off SKYRANGER | Houghton Lake, Michigan, United States | - | Serious injuries | - |
| 29 Dec 2018 | Cessna R172K | Chesaning, Michigan, United States | - | Fatal | 1 |
| 31 Dec 2018 | Piper PA 23 | Beaver Island, Michigan, United States | - | Fatal | 1 |
| 23 Jul 2018 | Aeros VENTURE 2000 | Bad Axe, Michigan, United States | - | Fatal | 1 |
| 27 Apr 2018 | Wolfe KITFOX V | Kalkaska, Michigan, United States | - | Fatal | 2 |