NYC02LA017 · Beech B95A
Beech B95A · Accident: loss of control in flight on approach
From Nashua Airport / Boire Field (ASH) to Sky Manor Airport (N40)
Event
- NTSB case
- NYC02LA017
- 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
- 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
- Visual Meteorological Cond
Beech B95A
- Aircraft type
- Beechcraft 95
- 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
- N919Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nashua Airport / Boire Field (ASH), Nashua, NHTo Sky Manor Airport (N40), Pittstown, NJ
- 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 · VFR go-around
- 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
- 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, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot attempted two landings on runway 25. During his first landing attempt, he initiated a go-around about 100 feet above the runway. During his second landing attempt, he initiated a go-around about 20 feet above the runway. Shortly after the pilot added power, as the airplane was climbing past the treetops, the airplane rolled inverted, then hit the ground and slid upside down for approximately 25 feet. The pilot subsequently reported that during both approaches, the winds had shifted, and that during the second go-around attempt, "a severe gust rolled the aircraft inverted." Winds recorded at an airport 20 miles to the west, 4 minutes before the accident, were from 260 degrees true, at 14, gusting to 22 knots. The pilot reported 430 hours of total flight time, with 86 hours in multi-engine airplanes and 30 hours in make and model.
Probable cause
The pilot’s failure to maintain adequate airspeed during a go-around in gusty wind conditions, which resulted in an inadvertent stall. A factor was the gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA017
- Event ID
- 20011105X02197
- Case number
- NYC02LA017
- 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: 9e5f9818d82675092a06d7f3f3ab3fa551b89731b495562fe41b1a6a9ae4c3bd; retrieved 2026-09-21T19:49:40.270Z.