FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17FA119 · Beech B 60

4 Mar 2017 · Duette, FL, United States

Beech B 60 · Accident: aerodynamic stall/spin while maneuvering

From Sarasota Bradenton International Airport (SRQ) to Sarasota Bradenton International Airport (SRQ)

Report a problem

Event

NTSB case
ERA17FA119
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
2 · 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 B 60

Aircraft type
Beechcraft B-60
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
N39AG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sarasota Bradenton International Airport (SRQ), SARASOTA/BRADENTON, FLTo Sarasota Bradenton International Airport (SRQ), SARASOTA/BRADENTON, FL
Aircraft age
About 40 years (built 1977)
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
Maneuvering · low-altitude flying
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
Aerodynamic stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

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

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

NTSB narrative

The private pilot, who had recently purchased the airplane, and the flight instructor were conducting an instructional flight in the multi-engine airplane to meet insurance requirements. Radar data for the accident flight, which occurred on the second day of 2 days of training, showed the airplane maneuvering between 1,000 ft and 1,200 ft above ground level (agl) just before the accident. The witness descriptions of the accident were consistent with the airplane transitioning from slow flight into a stall that developed into a spin from which the pilots were unable to recover before the airplane impacted terrain. Examination of the wreckage did not reveal evidence of any preexisting mechanical malfunctions or anomalies that would have precluded normal operation of the airplane.

After the first day of training, the pilot told friends and fellow pilots that the instructor provided non-standard training that included stall practice that required emergency recoveries at low airspeed and low altitude. The instructor used techniques that were not in keeping with established flight training standards and were not what would be expected from an individual with his extensive background in general aviation flight instruction. Most critically, the instructor used two techniques that introduced unnecessary risk: increasing power before reducing the angle of attack during a stall recovery and introducing asymmetric power while recovering from a stall in a multi-engine airplane; both techniques are dangerous errors because they can lead to an airplane entering a spin. At one point during the first day of training, the airplane entered a full stall and spun before control was regained at very low altitude. The procedures performed contradicted standard practice and Federal Aviation Administration guidance; yet, despite the pilot's experience in multi-engine airplanes and in the accident airplane make and model, he chose to continue the second day of training with the instructor instead of seeking a replacement to complete the insurance check out.

The spin encountered on the accident flight likely resulted from the stall recovery errors advocated by the instructor and practiced on the prior day's flight. Unlike the previous flight, the accident flight did not have sufficient altitude for recovery because of the low altitude it was operating at, which was below the safe altitude required for stall training (one which allows recovery no lower than 3,000 ft agl).

Probable cause

The pilots' decision to perform flight training maneuvers at low airspeed at an altitude that was insufficient for stall recovery. Contributing to the accident was the flight instructor's inappropriate use of non-standard stall recovery techniques.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA119
Event ID
20170304X55438
Case number
ERA17FA119
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: 534d77906a8116fb80a736fb95669bf02ad64a0e6fbbe93cd638d00ee1f3bc70; retrieved 2026-09-15T05:59:24.829Z.