IAD97LA099 · Beech BE-35
Beech BE-35 · Accident: overrun during landing
From Weltzien Skypark Airport (15G) to an unrecorded destination
Event
- NTSB case
- IAD97LA099
- 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 BE-35
- Aircraft type
- Beechcraft BE-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
- N2738V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Weltzien Skypark Airport (15G)To not recorded
- 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
- Landing · landing roll
- 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
- Overrun
- 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
- Throttle/power lever › Inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The day prior, the engine would only accelerate to 2,000 rpm. After some adjustments, the engine attained the manufacturer's maximum rpm of 2,300. The pilot stated that there were no indications of any malfunctions during the engine run up and the acceleration during take off felt normal. Once airborne, the pilot was unable to reduce the propeller rpm by turning the propeller control knob. He stated that the propeller control knob was pulled out for the remainder of the flight and landing. Maintaining 95-100 mph on short final, the pilot stated that he touched down about one-third of the way down the runway. The pilot applied brakes immediately, but the airplane did not slow down and continued off the end of the runway into a ditch. The pilot stated that the propeller control problem distracted him and that he did not pull the throttle to the idle position. No other mechanical problems were found with the airplane.
Probable cause
The pilot's failure to retard the engine throttle to idle during the landing roll. A related factor was the diverted attention.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD97LA099
- Event ID
- 20001208X08405
- Case number
- IAD97LA099
- 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: 877333b3a6432ce9f5868ad41a86679364157486827117b1c2dd5f7fa5d3e373; retrieved 2026-09-22T19:10:47.504Z.