NYC06FA145 · Raytheon Aircraft Company B36TC
Raytheon Aircraft Company B36TC · Accident: loss of control in flight on approach
From Nashua Airport / Boire Field (ASH) to VA18 · North Garden, VA
Event
- NTSB case
- NYC06FA145
- 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
- Not recorded
Raytheon Aircraft Company B36TC
- 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
- N202EN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nashua Airport / Boire Field (ASH), Nashua, NHTo VA18 · North Garden, VA
- 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 pattern base
- 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
- 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
While operating on an instrument flight rules flight plan and approaching a non-towered airport in instrument meteorological conditions, about 3,100 feet above the ground, the pilot advised the controller that he was directly over the airport and wanted to spiral down. The controller cleared the pilot for a visual approach. Due to terrain conditions, landing was normally uphill, on runway 33, with a left traffic pattern. A witness, who was inside an office just to the north of the runway, heard the airplane go overhead, but did not see it. The wreckage was located southeast of the airport, about 20 degrees to the right of the final approach course and 4/10 of a mile from the runway threshold. Ground scars and wreckage evidence were consistent with airplane being in a spin at the time of impact. There were no mechanical anomalies noted with the airplane, and no noted medical issues with the pilot. The ceiling was unknown; however, the witness noted low clouds in the vicinity of the airport. The visibility was also unknown; however, when the witness left his office, he could see smoke from the crash site.
Probable cause
The pilot's failure to maintain airspeed while turning onto the final approach, which resulted in an inadvertent stall/spin and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06FA145
- Event ID
- 20060623X00807
- Case number
- NYC06FA145
- 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: 2f93baa22ae9032be7b0bb00b0956a8796a91b993f75935155fb42275f972f1c; retrieved 2026-09-20T17:17:47.725Z.