IAD99LA048 · Beech BE-35
Beech BE-35 · Accident: loss of control in flight during initial climb
From Boonville Inc Airport (1NK7) to Carlisle Airport (N94)
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- IAD99LA048
- 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
- N3191V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boonville Inc Airport (1NK7)To Carlisle Airport (N94), Carlisle, PA
- 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 control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Airspeed(vlof), not attained
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed with a tailwind and rotated at low airspeed. At liftoff, he lost directional control, the airplane drifted left, and struck two small trees along the left side of the runway. After colliding with the trees, the airplane rotated 180 degrees and came to rest upright facing opposite the direction of travel. The occupants escaped with minor injuries but a post crash fire consumed the airplane. The pilot reported there were no mechanical deficiencies with the airplane. He said, 'I took off the runway too slow and the torque just took over.'
Probable cause
The pilot's failure to attain takeoff speed and his failure to maintain directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD99LA048
- Event ID
- 20001212X19011
- Case number
- IAD99LA048
- 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: 6315142f53fc7bc83dc25fa487a409ff3d745439d30e3945d2768c2047c1d1a3; retrieved 2026-09-21T20:31:23.089Z.