The U.S. aircraft register, updated daily
Accidents · NTSB ERA16CA056 · Final report

Cirrus Design CORP SR22 accident near Danbury, Connecticut, November 24, 2015

On November 24, 2015 at about 11:18 pm local time, a 2010 Cirrus Design CORP SR22, registered N771BT, was substantially damaged in an accident during approach (VFR pattern final) near Danbury, Connecticut (Danbury Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain adequate clearance from obstructions while on approach to landing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 24, 2015 · about 11:18 pm local time
Place
Danbury, Connecticut · Danbury Municipal Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22 NO SERIES, built 2010
Registration
N771BT · registry record · serial 3622
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

Upon arrival at the pilot's destination airport, the wind was calm, there was no ceiling, and the visibility was unlimited. Sunset had already occurred. Air traffic control directed the pilot to enter a left downwind for the active runway. The pilot then entered the left downwind for the runway at approximately 1,500 feet and confirmed the pattern altitude with air traffic control as there were nearby radio towers. The pilot elected to fly an extended downwind beyond the radio towers, turned left base and then final. On the turn to final, the pilot slightly overshot the runway centerline and then adjusted to align with the runway. Upon turning final, the tower controller realized the runway edge lights (MIRL) were at low intensity, advised him, and increased their intensity making the runway more visible. The runway end identifier lights (REIL) were out of service and the displaced threshold for the runway was unlighted. On final approach, the pilot heard a "thunk" sound and felt a slight jolt as if something had struck the airplane. The pilot continued the approach and landed, touching down beyond the displaced threshold and then taxied to the ramp. Post flight inspection by the pilot revealed that the right wing had a yellowish goo spattered on top of it, a large dent in the TKS anti-ice panel on the leading edge of the outer part of the wing, a small dent in the TKS anti-ice panel on the leading edge more inward on the wing, a third dent on the corner of the leading edge of the composite cap at the end of the wing, and chipped paint on the top of the wing. Examination of the airplane by a Federal Aviation Administration inspector also revealed that a piece of wood with bark on one side of it was wedged between the right wing tiedown ring and the wing structure. Examination of the airplane by maintenance personnel revealed that the solid laminate and sandwich structure of the wing had been substantially damaged. Examination of the surrounding area revealed that trees were present along and below the flight path for the runway. Review of the Airport Facility Directory also revealed that it advised that 88 foot tall trees were present 450 feet from the runway which took a 3:1 slope to clear.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Controlled flight into terrain or object (CFIT) during approach (VFR pattern final) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
  • Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 284 hours in all; 182 in this make and model; 12 in the last 90 days; 4 in the last 30 days; 178 as pilot in command
  • Last flight review: March 19, 2014
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 812.8 hours
  • Last inspection: 100-hour inspection, September 2, 2015
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-550-N-61B (piston); 813 hours total

The flight

  • Departed from: HPN White Plains NY at 11:06 pm
  • Destination: DXR Danbury CT
  • Flight plan: none
  • Runway 26, 4,422 ft by 150 ft

Weather at the time

  • Light: dusk
  • Wind: from 230° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 32°F (0°C), dew point 21°F (-6°C)
  • Altimeter: 30.39 inHg
  • Observation at 10:53 pm from DXR

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on February 23, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.