NYC96FA113 · Beech A36
Beech A36 · Accident: loss of control in flight during initial climb
From Emperor Nicholas II Murmansk Airport (MMK) to Parlin Field (2B3)
Event
- NTSB case
- NYC96FA113
- 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 A36
- 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
- N59WW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Emperor Nicholas II Murmansk Airport (MMK)To Parlin Field (2B3), Newport, NH
- 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
- Stall/mush
- 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 › Lift-off, premature
- Pilot in command › Planning/decision, improper
- Pilot in command › Stall/mush, inadvertent
- Pilot in command › Throttle/power control, improper use of
Approximate · Estimated position: the centre of Meriden, CT, the place the record names. Not the accident site.
NTSB narrative
The pilot initiated a downwind takeoff on runway 18 with two passengers aboard. He said that after a 600 foot ground run, he rotated the airplane for takeoff, and it climbed about 40 feet above the runway, then it stopped climbing and stopped accellerating. According to witnesses, the airplane entered a steep nose high attitude during takeoff, then after climbing briefly, the wings rocked (or wobbled) to the left and right. The pilot lowered the nose briefly and said he increased engine power '2 ticks into the yellow (arc).' He aborted the climb and attempted to land. After ground contact, the airplane veered off the runway. After stopping, a fire erupted, which resulted in further damage. The airplane's reciprocating engine had been replaced with an Allison 250-B17C, turbine engine per Supplemental Type Certificate (STC) SA3523NM, by Tradewind Turbines, Amarillo, TX. The wind was estimated to be from 350 degrees at 15 knots. The Pilot's Operating Handbook showed that a ground roll of 1,800 feet would have been required for the takeoff conditions. The airplane was estimated to be 76 pounds over its maximum takeoff weight and about 2 inches beyond the forward center of gravity (CG) limit (as listed in the STC). Also, the pilot did not use maximum power for takeoff as described in the STC.
Probable cause
the pilot's improper planning/decision, his failure to use takeoff power, and his premature lift-off of the airplane, which resulted in an inadvertent stall/mush and subsequent collision with terrain. Factors relating to the accident were: the pilot allowing the airplane's maximum takeoff weight to be exceeded, and the tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96FA113
- Event ID
- 20001208X05843
- Case number
- NYC96FA113
- 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: 55e2465432a37dd902de8dddaf4f8ce29e3aeece4b7ad8a97a65a3f8b58138a9; retrieved 2026-09-22T22:27:29.555Z.