FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA001 · Beech M35

2 Oct 2001 · Denton, TX, United States

Beech M35 · Accident: loss of engine power during initial climb

From Denton Enterprise Airport (DTO) to Denton Enterprise Airport (DTO)

Report a problem

Event

NTSB case
FTW02LA001
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 M35

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
N9765R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Denton Enterprise Airport (DTO), Denton, TXTo Denton Enterprise Airport (DTO), Denton, TX
Aircraft age
Not recorded
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
Initial climb
First occurrenceThe 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 engine power
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

  • Reason for occurrence undetermined

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

NTSB narrative

The flight departed and flew 10 minutes to another airport. The pilot executed a full stop landing and decided to remain in the pattern and perform touch-and-go landings. He departed, flew one traffic pattern, landed and departed again. During the initial takeoff climb, the engine began to "surge and lose power." Subsequently, a forced landing was executed to a field. During the forced landing, the airplane contacted fence posts, both wings separated, and the airplane came to a stop upright. A review of the airplane's maintenance records did not reveal any open maintenance discrepancies. An examination of the engine and a successful full engine test run did not reveal the reason for the loss of engine power.

Probable cause

the loss of engine power for an undetermined reason, which resulted in a forced landing. A contributing factor was the lack of suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA001
Event ID
20011004X02040
Case number
FTW02LA001
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: f6a7f7dc93136568d562adca573ffb14bee2245900e772d88405390bff6430c3; retrieved 2026-09-22T11:32:11.021Z.