FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16FA188 · Beech D35

19 May 2016 · Sevierville, TN, United States

Beech D35 · Accident: landing gear not configured

From Gatlinburg-Pigeon Forge Airport (GKT) to Gatlinburg-Pigeon Forge Airport (GKT)

Report a problem

Event

NTSB case
ERA16FA188
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
1 · 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 D35

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
N2967B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gatlinburg-Pigeon Forge Airport (GKT), Sevierville, TNTo Gatlinburg-Pigeon Forge Airport (GKT), Sevierville, TN
Aircraft age
About 63 years (built 1953)
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
Landing
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
Landing gear not configured
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 systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

After takeoff on a personal flight, the private pilot of the complex, high performance airplane flew around the local area for about 30 minutes before returning to the airport to land. According to security camera video, witnesses, and physical evidence, the airplane touched down with the wing flaps down and the landing gear in the up (retracted) position. The propeller struck the ground multiple times as the airplane skidded along the ground on its belly. The pilot increased engine power, and the airplane lifted off. The airplane climbed slowly to a point about 450 feet beyond the departure end of the runway and then pitched up, rolled to the left, and impacted terrain. The pitch up and left roll were consistent with a loss of control due to the pilot exceeding the airplane's critical angle of attack and encountering an aerodynamic stall.

Postaccident examination of the landing gear system revealed that the landing gear doors were closed; all three landing gear were in their retracted positions in the gear wells; the emergency gear extension handle was stowed; and the push-pull rods from the gearbox to the "A" frame assemblies at the wheels were retracted. These findings indicated that the pilot had retracted the landing gear after takeoff and failed to extend the landing gear before landing. Examination of the propeller also revealed that it sustained significant impact damage from contacting the runway, which likely affected its aerodynamic performance and resulted in a loss of thrust during the pilot's aborted landing and attempted climb.

Although the Federal Aviation Administration (FAA) requires that each pilot acting as pilot-in-command of an airplane must complete a flight review every 24 months to assess that pilot's flying skills, review of the pilot's logbooks revealed that his last flight review had occurred more than 10 years before the accident. Review of the pilot's logbook also indicated that the pilot had received 3.1 hours of flight instruction in the accident airplane about 1 year before the accident, but there was no record of the complex and high-performance endorsements required by the FAA to act as pilot-in-command of the airplane.

During the examination of the wreckage, the remains of a Pilot's Operating Handbook and Airplane Flight Manual (POH/AFM) was found behind the pilot's and copilot's seats in the cabin, an area that was out of reach from the pilot's position. The POH/AFM contained a Before Landing Checklist that directed the pilot to extend the landing gear and check that it was down before landing. No checklists were found near the pilot's seat.

Probable cause

The pilot's failure to properly configure the landing gear and the pilot's inappropriate decision to abort the landing after the propeller had contacted the runway, which resulted in a loss of thrust and a subsequent loss of control of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16FA188
Event ID
20160519X25723
Case number
ERA16FA188
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: 6e652b8cfd79fa67ffe4e9d36ea55e19ec0669c1059fed04f2dc8dbceadab850; retrieved 2026-09-14T21:47:01.812Z.