FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18TA374 · Beech 35 K35

1 Sept 2018 · Harrisville, MI, United States

Beech 35 K35 · Accident: runway excursion during takeoff

From Harrisville Airport (5Y0) to Grosse Ile Municipal Airport (ONZ)

Report a problem

Event

NTSB case
CEN18TA374
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
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

Beech 35 K35

Aircraft type
Beechcraft 35
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
N5321E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Harrisville Airport (5Y0), Harrisville, MITo Grosse Ile Municipal Airport (ONZ), Detroit/Grosse Ile, MI
Aircraft age
About 59 years (built 1959)
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
Takeoff
Defining eventThe 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
Runway excursion
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
Tree(s)
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18TA374
Event ID
20180906X30904
Case number
CEN18TA374
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 20eb2c897158c5280719616651865eabfb383a9b7d2e2e2f985351002a979b5e; retrieved 2026-09-16T08:12:57.704Z.