NYC02FA055 · Beech V35B
Beech V35B · Accident: loss of control in flight on approach
From Roanoke–Blacksburg Regional Airport (ROA) to 3B9 · Chester, CT
Event
- NTSB case
- NYC02FA055
- 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
- Unknown
- 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
- Instrument Meteorological Cond
Beech V35B
- Aircraft type
- Beechcraft 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
- N32BR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Roanoke–Blacksburg Regional Airport (ROA), Roanoke, VATo 3B9 · Chester, CT
- 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
- Approach · circling (IFR)
- 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
- 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, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot flew a GPS Rwy 35, circle-to-land runway 17 approach during night instrument meteorological conditions. A witness reported that the airplane's downwind leg was two to three times closer to the runway than normal. The airplane's turn radius to final approach was also much smaller than normal, and the turn was relatively "flat". The airplane appeared to be traveling at a relatively slow airspeed during the approach, and engine rpm did not increase during the turn. As the airplane turned toward the final approach course, the witness saw it "instantaneously" change from being relatively wings-level, to being wings-vertical, with the left wing pointing straight down and the right wing pointing straight up. He then lost sight of it, and almost immediately heard a "crunch". Examination of the wreckage revealed that the airplane had impacted the ground almost vertically, and upon impact, was facing approximately the opposite direction of the landing runway. Weather at the time included winds from 080 degrees true at 6 knots, visibility 2 1/2 statute miles in mist, an overcast ceiling at 300 feet above ground level, and a temperature and dewpoint of 32 degrees Fahrenheit. No pre-impact mechanical malfunctions were found.
Probable cause
The pilot's failure to maintain adequate airspeed during the turn to final, which resulted in an inadvertent stall/spin. Factors included low ceilings and night lighting conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02FA055
- Event ID
- 20020214X00223
- Case number
- NYC02FA055
- 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, coordinates. 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: 3f2b236a5ba491bbd0638e809cb68c03fbc6cf1902c5a3ef54aecfc1bd03538d; retrieved 2026-09-20T20:13:30.087Z.