# NTSB NYC02FA055: Beech V35B, N32BR, Chester, CT, January 31, 2002 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: January 31, 2002, 18:50 local (23:50 UTC) - Place: Chester, CT - Coordinates: 41.391109, -72.508888 - Nearby events: https://openairdocs.org/map.md?lat=41.3911&lon=-72.5089&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed, report October 23, 2002 - Report: Approved by Office Director - Parties: FAA/FSDO, Teledyne Continental Motors, Raytheon Aircraft Company - NTSB case key (mKey): 54106 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC02FA055 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54106/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54106 - Page: https://openairdocs.org/ntsb/NYC02FA055 ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, circling (ifr) - airspeed - not maintained, pilot in command (cause) - weather condition - low ceiling (contributing factor) - light condition - night (contributing factor) - In flight collision with terrain/water, descent - uncontrolled ## Analysis 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. ## Factual narrative HISTORY OF FLIGHT On January 31, 2002, about 1850 eastern standard time, a (Raytheon) Beech V35B Bonanza, N32BR, was destroyed when it impacted terrain during a night circle-to-land instrument approach at Chester Airport (3B9), Chester, Connecticut. The certificated private pilot and his passenger were fatally injured. Instrument meteorological conditions prevailed at the time, and the flight was operating on an instrument flight rules flight plan between Roanoke Regional/Woodrum Field (ROA), Roanoke, Virginia, and Chester. The business flight was conducted under 14 CFR Part 91. According to a representative of the pilot's family, the pilot left home about 0700, and he and the passenger went to Chester in the passenger's car, where the airplane was hangared. The two then flew to Roanoke for a business meeting. Before beginning the trip home from Roanoke, the pilot called his wife. He noted that the weather in Virginia was beautiful, but that if it deteriorated to the point where he could not land at Chester, he would continue on to Hartford-Brainard Airport (HFD), Hartford, Connecticut, which was close to his home. About the time of the airplane's intended arrival, the pilot's wife went to Hartford-Brainard to wait for him. The pilot and his wife were scheduled to depart in the airplane the following morning, to visit relatives in Minnesota. A review of voice transmissions revealed that the pilot contacted the Islip/LOVES sector controller at New York Approach Control at 1825, while "descending forty eight hundred for three thousand." The controller cleared the pilot to proceed direct to the Madison VOR. In addition, he requested that the pilot "advise when receiving the weather at chester and what approach you'd like." At 1829, the pilot advised the controller, "...we'd like to try g-p-s three five into chester. not sure we'll get in right now, the automated weather says three hundred foot ceiling but we'd like to try g-p-s three five. The controller responded, "three two bravo romeo, proceed direct to flibb [intersection]. the closest weather i have is new haven, they were reporting as of 2321 [1821 local time], a special, winds zero six zero at seven, visibility three miles, light rain and mist, ceiling seven hundred overcast, temperature zero two [centigrade], dewpoint zero two, altimeter three zero two nine." The pilot acknowledged the weather report. At 1844, the pilot asked, "okay (unintelligible) for you for a direct turn into this?" and the controller responded, "i'll turn you in and give you a good intercept there." At 1845, the controller transmitted, "three two bravo romeo is ah three from the final approach fix. maintain ah two thousand until established on the ah final approach course. fly heading zero ah one zero to intercept, cleared the g-p-s runway three five approach." The pilot responded, "okay, cleared for the approach. zero ah one zero and down to two thousand, three two bravo romeo." At 1846, the controller announced, "(unintelligible) station change to advisory frequency is approved," and the pilot responded, "three two bravo romeo roger, we'll ah refer to you." The controller then stated, "three two bravo romeo report canceling i-f-r in the air on this frequency if you are able to reach me or on the ground with bridgeport flight service station, change to advisory frequency is approved," and the pilot again responded with, "three two bravo romeo roger, we'll ah refer to you." There were no further transmissions from the pilot recorded on the frequency. A review of radar data indicated that the airplane flew inbound on the GPS Rwy 35 approach course until it descended to an altitude of 1,500 feet, about 4.5 nautical miles from the airport. Radar contact was then lost due to radar antenna positioning and terrain. A witness was outside his home at the time of the accident. His home was located on the same road as the airport, at an estimated 1,000 feet northeast of the approach end of runway 17. The witness had lived in his home for the past 22 years, and was accustomed to watching airplanes in the traffic pattern. In addition, he had flown many times with his son, who was a certificated commercial pilot. The witness reported that the weather at the time of the accident was "not all that great." It was "drizzling a bit," and the night sky appeared to be more gray than black. The airplane caught the witness's attention because it flew almost directly over his house, and he was wondering what the pilot was going to do, given the weather conditions. The airplane was first seen flying northbound, parallel to the runway and about 1,000 feet east of it, at an altitude estimated to be about 400 feet. The witness observed it make a left turn from the downwind leg through to the final approach. He could see red navigation lights during the whole turn, along with the airplane's silhouette against the gray sky. The airplane's flight pattern was two to three times closer than what the witness was used to seeing. The witness was "pretty impressed" that the airplane was able to complete the turn in the space available, because the turn radius was much smaller than normal. The witness also noted that he had never seen an airplane fly the turn "so flat" before, and had expected the airplane to make the turn with a much larger angle of bank since the pattern the pilot was trying to fly was so tight. The witness further noted that the airplane was not traveling very fast during the approach - "it seemed slow" - and that engine rpm did not increase during the turn. As the airplane turned to 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". Another witness, a flight instructor whose house was aligned with runway 17, about 3/4 to 1 mile to the north, heard the noise of what sounded like a Bonanza. It sounded like it was circling to land on runway 17, and was turning onto final between the flight instructor's house and the runway. According to the flight instructor: "[The engine] rpm was steady and did not sound to be anything wrong at the time. The engine was at a moderate rpm, approximately 1,500 to 1,800 rpm I would guess. As I heard the aircraft flying close to the house I walked to the front...to see who it was. I knew when I left [the airport] earlier, [it] was fogged in [and had] more or less low ceilings and visibility. I did not see the lights of the aircraft, but immediately after hearing the engine I thought I heard a crash or loud thud. Looking towards the airport I could see REIL flash reflecting off the clouds. Slightly to the left of the lights I noticed a reddish/orange glow. The light wasn't steady, and it was bright at first and dimmed out slightly, but continued to glow." The accident occurred during the hours of darkness, in the vicinity of 41 degrees, 23.47 minutes north latitude, 72 degrees, 30.54 minutes west longitude. PERSONNEL INFORMATION The pilot held a private pilot certificate, with ratings for airplane single-engine land and instrument airplane. His latest Federal Aviation Administration (FAA) third class medical certificate was dated August 24, 2000. According to the pilot's logbook, as of January 14, 2002, he had logged 2,982 hours of flight experience, including 335 hours of night time and 340 hours of actual instrument time. The pilot completed a biennial flight review and an instrument proficiency check on October 20, 2001. AIRCRAFT INFORMATION The airplane's logbooks were onboard the airplane at the time of the accident, and were consumed in a post-impact fire. The last partially discernable logbook entry was made on October 12, 2001, ## Aircraft - Registration: [N32BR](https://openairdocs.org/deregistered/N32BR-2003-04-11), registration cancelled 2003-04-11, S/N D-10392, built 1982 (OpenAirDocs) - Reported make and model: Beech V35B - Registry model: [Beech V35B](https://openairdocs.org/model/beech-v35b) (registry code 1151548) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: D-10392 - Airframe hours: 1155 - Engines: Continental IO-520 285 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Business, Part 91 - Registered owner: John F. Howard - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 12, 2001, 95 hours before - Departed: ROA, Roanoke, VA - Destination: 3B9, Chester, CT - Flight plan: IFR - Airport: 3B9, Chester Airport, runway 17, 2,566 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; injuries: fatal; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; last flight review October 20, 2001; seat: left; toxicology performed; flight hours: 2,982 total ## Weather - Conditions: Instrument (IMC), Night - Wind: 80° at 6 knots - Visibility: 2.5 statute miles - Lowest ceiling: 300 ft overcast - Temperature: 32 °F, dew point 32 °F - Altimeter: 30.27 inHg - Observed at: 3B9 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20020131000729A](https://openairdocs.org/incident/20020131000729A), Jan 31, 2002: Beech V35B, Chester, CT, Destroyed, 2 fatal. (-23) PIC intended to land on runway 35, at airport 3B9, using GPS approach. Aircraft collided with the ground in wooded area 1475 feet beyond the departure… ## Docket (9 files) The files NTSB released with the investigation on October 4, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54106. 2.4 MB in all. - Witness Statements (item 1, .PDF, 396 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40382844&FileExtension=.PDF&FileName=Witness%20Statements-Redacted.PDF - Approach Procedures (item 2, .PDF, 222 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40167965&FileExtension=.PDF&FileName=Approach%20Procedures-Master.PDF - Radar Plot/Data (item 3, .PDF, 251 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40382845&FileExtension=.PDF&FileName=Radar%20Plot%2FData-Redacted.PDF - Work Orders/Info (item 4, .PDF, 281 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40382846&FileExtension=.PDF&FileName=Work%20Orders%2FInfo-Redacted.PDF - Toxicological Reports (item 5, .PDF, 124 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40382847&FileExtension=.PDF&FileName=Toxicological%20Reports-Redacted.PDF - Statement of Party Representatives to NTSB Investigation (item 6, .PDF, 85 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40382848&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 7, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40382850&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Wreckage Photo #1 (item 8, .PDF, 530 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40167972&FileExtension=.PDF&FileName=Wreckage%20Photo%20%231-Master.PDF - Wreckage Photo #2 (item 9, .PDF, 470 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40167975&FileExtension=.PDF&FileName=Wreckage%20Photo%20%232-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.