FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA166 · Beech A36TC

26 Jul 2017 · Ogden, UT, United States

Beech A36TC · Accident: loss of control in flight during an emergency descent

From Ogden Hinckley Airport (OGD) to Yellowstone Airport (WYS)

Report a problem

Event

NTSB case
WPR17FA166
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
4 · 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

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
N60WB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ogden Hinckley Airport (OGD), Ogden, UTTo Yellowstone Airport (WYS), W. YELLOWSTONE, MT
Aircraft age
About 36 years (built 1981)
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
Emergency descent
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
Loss of control in flight
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The private pilot and three passengers departed on a cross-country flight in the turbocharged single-engine airplane. Witnesses saw the airplane during the takeoff and reported that about 3,700 ft down the 5,195-ft-long runway, the airplane was about 100 ft above the runway surface. The witnesses also noticed that the engine sounded "underpowered" and that the tail of the airplane was moving up and down as if the pilot was struggling to keep the airplane airborne. The airplane continued its climbout, and soon after, the pilot communicated to the tower controller that the airplane was "going down." The airplane impacted the right side of a north-bound freeway. Detailed examination of the airplane, engine, and propeller did not reveal any pre-impact mechanical deficiencies that would have precluded normal operation.

Given the weights of the pilot, passengers, and fuel onboard, the airplane was near its maximum gross weight about the time of the accident. Additionally, the density altitude was about 6,500 ft. Both of these factors would have resulted in an increased takeoff distance and reduced climb performance, though review of performance data indicated that the runway available was adequately long to accommodate the airplane's predicted takeoff roll (2,109 ft) and distance to clear a 50-ft obstacle (3,401 ft). Although the actual loading of the airplane at the time of the accident could not be accurately determined, including the weight and location of any baggage and the positions of the rear passengers, it is likely that the airplane's center of gravity (CG) was outside of its forward end of the envelope as depicted on a weight and balance worksheet. A forward CG can result in nose heaviness and increased stall speed.

The pilot chose to operate the airplane under conditions which would have adversely affected its performance, namely, high gross weight, high density altitude, and with a CG that may have been forward of prescribed limits. Whether the pilot calculated the airplane's weight and balance before the flight and was prepared for the resulting negative effects on its takeoff performance could not be determined. Given the lack of anomalies observed during postaccident examination, it is unlikely that the pilot experienced a loss of engine power or mechanical failure during the takeoff; therefore, the reason for the pilot's loss of control shortly after takeoff could not be determined.

Probable cause

A loss of control during takeoff for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA166
Event ID
20170726X61759
Case number
WPR17FA166
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: 75ff7e408af6d894444382773a7cb1eb8e66a32aabdee65b26ee82323797a56a; retrieved 2026-09-15T06:09:47.132Z.