FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI00LA291 · Beech A36TC

9 Sept 2000 · MOOREHEAD, MN, United States

Beech A36TC · Accident: in flight collision with terrain/water during takeoff

From JKJ to Saint Paul, MN

Report a problem

Event

NTSB case
CHI00LA291
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
0
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
N3683D
Operator
Unknown
Onboard fatalities
Unknown
Route
From JKJTo Saint Paul, MN
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
Takeoff · roll/run
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
In flight collision with terrain/water
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

  • Pilot in command › Aborted takeoff, not performed
  • Proper climb rate › Not attained
  • Reason for occurrence undetermined

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

NTSB narrative

The airplane impacted a road after takeoff. Witnesses reported that the aircraft became airborne just before reaching the end of the 4,000 foot long runway and only achieved an altitude of a few feet. The airplane settled back to the ground and then impacted a road before coming to rest in a farm field. No anomalies were found with respect to the airframe. A teardown inspection of the engine and its accessories failed to reveal any anomalies that would have prevented normal engine operation. The pilot said that he recalled the start of the takeoff but had, "... no further memory of the event due to injury." The takeoff was made on runway 12 and the reported weather was: Wind 190 degrees magnetic at 15 knots gusting to 21 knots; Visibility 10 statute miles; Sky condition clear; Temperature 29 degrees Celsius; Dewpoint 16 degrees Celsius; Altimeter setting 29.32 inches of Mercury. According to the aircraft performance charts, the reported weather, and a maximum gross weight of 3,650 pounds, the takeoff ground roll should have been about 1,500 feet.

Probable cause

The pilots failure to abort the takeoff and the airplane not attaining a proper climb rate for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI00LA291
Event ID
20001212X21924
Case number
CHI00LA291
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: cb5972f0bef39d5298c777e728e01cae9d1964595e1d197a344fcc0e0298ee9f; retrieved 2026-09-21T10:26:37.001Z.