NYC99FA126 · Beech D50C
Beech D50C · Accident: loss of control in flight while maneuvering
From Wurtsboro-Sullivan County Airport (N82) to Orange County Airport (MGJ)
Event
- NTSB case
- NYC99FA126
- 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
- 2 · 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 D50C
- Aircraft type
- Beechcraft 50
- 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
- N401JD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wurtsboro-Sullivan County Airport (N82), Wurtsboro, NYTo Orange County Airport (MGJ), Montgomery, NY
- 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
- Maneuvering
- 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/spin
- 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 › Airspeed, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Radar data depicted an airplane flying a track similar to a right traffic pattern for the runway. While on a track consistent with a right base leg, the airplane entered a left turn. About the same time as the accident, witnesses reported seeing an airplane fly a right base leg for the runway. The airplane entered a steep left bank, followed by an abrupt descent angle, and collision with terrain. A review of recorded radio transmissions revealed the pilot of the accident airplane flew a right hand pattern for the runway. The pilot queried a pilot of another airplane of his intentions. At that time, the other airplane was ahead of the accident airplane, on a final approach leg. The accident airplane then entered the left turn. A radar study indicated that while in the left turn, the approximate airspeed of the accident airplane was approaching or below the stall speed for the make and model airplane.
Probable cause
The pilot-in-command's failure to maintain adequate airspeed while maneuvering in the traffic pattern, which resulted in an inadvertent stall/spin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99FA126
- Event ID
- 20001212X18853
- Case number
- NYC99FA126
- 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: 1511cd1ed9958d82097aa07a4cabbf3c28dbe3c86c69690a91fd4eb676b345df; retrieved 2026-09-20T22:04:43.069Z.