FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA064 · Beech A36TC UNDESIGNAT

23 Feb 2017 · Stevensville, MT, United States

Beech A36TC UNDESIGNAT · Accident before flight

From Stevensville Airport (32S) to Chandler Municipal Airport (CHD)

Report a problem

Event

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

Beech A36TC UNDESIGNAT

Aircraft type
Beechcraft 36
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
N3803J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stevensville Airport (32S), Stevensville, MTTo Chandler Municipal Airport (CHD), Chandler, AZ
Aircraft age
About 37 years (built 1980)
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
Prior to flight
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
Miscellaneous/other
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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 reported that before takeoff from his home airport for the personal flight, he noted the midfield windsock at the airport and believed that he would have a straight crosswind with gusts coming from both directions.

The pilot reported that the airplane lifted off about 80 knots. However, the airplane would not climb or accelerate, and the pilot felt that there was a rapid decrease in power. He ensured that the engine controls were in their appropriate positions for full takeoff power, but the airplane still would not climb. The airplane struck level terrain adjoining the right side of the runway and came to rest upright, about 300 ft from the runway centerline.

A witness reported that the airplane's engine sounded "strong and loud." The airplane lifted off about 2,400 ft from the runway threshold and attained an altitude of about 50 ft above ground level when the airplane began a steep right descending turn.

Although the pilot reported that he referenced the windsock and believed that he would be taking off with a direct crosswind, the airport's automated weather observation system indicated a tailwind component of about 8.5 to 11.2 knots for the takeoff runway at the time.

The accident runway was 3,800 ft long. Review of the airplane manufacturer's performance data indicated that a takeoff with maximum allowable gross weight and no flaps from a level runway with a 10-knot tailwind would have required a ground roll of about 2,109 ft and required about 3,385 ft to clear a 50-ft obstacle. The airplane manufacturer's published performance data did not account for tailwind components above 10 knots. The runway had a 1.94% uphill slope in the takeoff direction, but the performance data did not account for runway slope. Calculations indicated that the airplane was about 220 lbs above the maximum allowable takeoff weight. Each of these three factors would increase the takeoff distance and decrease the airplane climb performance, but there were no means for the pilot or investigators to quantify their individual or collective effects.

Examination of the airplane and engine did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation and performance. However, it is likely that the overweight condition of the airplane, the significant tailwind, and the uphill runway slope combined to affect the takeoff so that the airplane had insufficient energy to climb out of ground effect.

Probable cause

The pilot's decision to conduct a takeoff with a tailwind on an upsloping runway in an overweight airplane, which resulted in the airplane having insufficient energy to climb out of ground effect.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA064
Event ID
20170224X34451
Case number
WPR17LA064
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, 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: 3c493e6fe36e8f89fc03bdcf215d7fd19ebc20c27bbeb58c2b3db17e7c8be95e; retrieved 2026-09-16T05:02:25.374Z.