# NTSB ERA17LA261: Cessna 172, N612DF, Danbury, CT, July 30, 2017 - Type: NTSB accident investigation - Classification: Accident · Fatal · Limited investigation · Final report - Date: July 30, 2017, 10:25 local (14:25 UTC) - Place: Danbury, CT - Coordinates: 41.368057, -73.493057 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.3681&lon=-73.4931&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) - Highest injury: Fatal - Injuries: 1 fatal, 2 serious - Status: Completed, report September 10, 2019 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 95695 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA17LA261 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/95695/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=95695 - Page: https://openairdocs.org/ntsb/ERA17LA261 ## Probable cause The pilot's exceedance of the airplane's critical angle of attack during initial climb, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's decision to operate the airplane above its maximum gross weight, which likely reduced its takeoff performance. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 13 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=2072439), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md) - [Aircraft capability: maximum weight](https://openairdocs.org/ntsb-findings/01061035): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172S, 6 cases](https://openairdocs.org/ntsb-findings/01061035/cases.md?model=2072439), [All aircraft, 152 cases](https://openairdocs.org/ntsb-findings/01061035/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 41 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072439), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Performance/control parameters: configuration](https://openairdocs.org/ntsb-findings/01062017): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation; cases with it: [Cessna 172S, 2 cases](https://openairdocs.org/ntsb-findings/01062017/cases.md?model=2072439), [All aircraft, 80 cases](https://openairdocs.org/ntsb-findings/01062017/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Aircraft loading event](https://openairdocs.org/ntsb-events/010); cases with it: [Cessna 172S, 2 cases](https://openairdocs.org/ntsb-events/010/sequence.md?model=2072439), [All aircraft, 84 cases](https://openairdocs.org/ntsb-events/010/sequence.md) - [Initial climb: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Cessna 172S, 21 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=2072439), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172S, 118 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The private pilot and two passengers were departing in the airplane from the 4,422-ft-long asphalt runway. A witness reported that, while still over the runway, the airplane began to lose altitude, then entered a nose-high attitude. The airplane subsequently entered a left-turning descent consistent with an aerodynamic stall. Examination of the wreckage did not reveal any preimpact mechanical anomalies; although the ignition key was found in the left magneto position, the preimpact position of the key could not be determined. Performance calculations revealed that the airplane should have used less than half the available runway distance to clear a 50-ft obstacle at maximum gross weight with flaps extended to 10°. Weight and balance calculations revealed that the airplane was operating about 59 lbs over its maximum allowable gross weight at the time of the accident, and the flaps were found in the retracted position. It is likely that the pilot noticed the airplane's degraded climb performance after takeoff and attempted to compensate by increasing the airplane's pitch attitude, which resulted in decaying airspeed, an exceedance of the critical angle of attack, and an aerodynamic stall. ## Factual narrative On July 30, 2017, about 1025 eastern daylight time, a Cessna 172S, N612DF, was substantially damaged when it impacted terrain shortly after takeoff from Danbury Municipal Airport (DXR), Danbury, Connecticut. The pilot died from his injuries 4 days after the accident, and the two passengers received serious injuries. The airplane was owned by a private company and was being operated by Arrow Aviation LLC as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed, and no flight plan was filed for the flight, which was originating at the time of the accident.The rear-seat passenger was a certificated pilot with about 1,500 hours of flight experience. He stated that, when the airplane was cleared for takeoff, the pilot taxied to the runway and applied what sounded like full engine power. The rear-seat passenger could not see the instruments or flight controls from where he was seated. After a short ground roll, the airplane took off, but from what he could see out the side window, it seemed that the airplane was not gaining altitude normally. Less than 1 minute later, the pilot stated, "we're going in." According to an air traffic controller at DXR, the airplane lost altitude after takeoff while still over runway 26, a 4,422-ft-long runway. He then observed it "appearing to correct" as it had assumed a more nose-up attitude. It then began a left roll, followed by a "full nose up attitude, rolling to the left," before it descended and impacted the ground. Another witness, who was in a dog park near the accident site, stated that he heard a small airplane "lumbering" and sounding under-powered. He saw the airplane appear to turn sharply 180°, then impact the ground. According to Federal Aviation Administration records, the pilot held a private pilot certificate with ratings for airplane single-engine land and rotorcraft-helicopter. His most recent FAA third-class medical certificate was issued June 14, 2016, at which time he reported 582 hours of total flight experience. The pilot's logbook was not recovered. Review of the airplane's maintenance records revealed that the most recent annual inspection was completed on July 21, 2017, about 17 flight hours before the accident. At that time, the airframe had accrued about 4,013 hours and the engine had accrued 656 hours since overhaul. According to fuel records and statements from the operator, the airplane was fueled to capacity on the afternoon of July 28. The accident flight was the first flight since that fueling. The airplane's maximum gross weight was 2,550 lbs. The airplane's estimated weight at the time of the accident, including full fuel and the three occupants (not accounting for any baggage), was about 2,609 lbs. Review of takeoff performance data revealed that, at 2,550 lbs, a pressure altitude of 500 ft mean sea level, and a temperature of 20°C, the airplane required about 1,770 ft to clear a 50-ft obstacle. The data assumed no wind andflaps extended 10°. At 1053, the reported weather at DXR included wind from 350° at 9 knots, the temperature was 23°C, and the dew point was 12°C. An initial examination of the airplane by a Federal Aviation Administrator (FAA) inspector revealed that the fuselage came to rest upright in a nose-down attitude in an area of heavy brush about 1,000 ft from the departure end of the runway. The left wing was partially separated from the fuselage and exhibited leading edge crush damage from the root to the tip. The outboard one-third of the right wing was bent upward and aft. The fuselage was buckled on both sides aft of the rear window, and the left rear pillar was crushed and separated from the roof. The nose section, including the engine, was crushed and displaced upward and aft. The empennage, vertical and horizontal stabilizers, rudder, and elevators were largely undamaged. The ignition key was found positioned to the left magneto; however, the preimpact position of the key could not be determined. Several branches were found severed at a 45° angle in the westerly path leading up to the airplane consistent with propeller contact. Both propeller blades exhibited leading edge gouges and chordwise scratches. Fuel samples from both tanks were blue in color and absent of water. Oil was present in the engine, but the quantity could not be determined due to the resting position of the engine. The wreckage was transported to a recovery facility and examined again. Flight control continuity was confirmed from all control surfaces to the cockpit area. Measurement of the elevator trim jackscrew corresponded to a 5° tab up (nose down) elevator trim. Measurement of the flap actuator revealed that the flaps were in the fully retracted position. The engine crankshaft was rotated by means of a tool inserted in the vacuum pump drive pad and continuity of the crankshaft to the rear gears and to the valve train was observed. The interiors of the cylinders were examined with a lighted borescope and no anomalies were noted. The fuel servo, engine-driven fuel pump, flow divider, and injector nozzles remained attached to the engine and were removed and partially disassembled. The fuel servo regulator section was partially disassembled and no damage was noted to the rubber diaphragms or other internal components. The fuel servo fuel inlet screen was absent of debris. The flow divider was partially disassembled. No debris was noted inside and no damage to the rubber diaphragm was noted. The two-piece fuel injector nozzles were unobstructed. The engine-driven fuel pump was partially disassembled and no damage was noted to the rubber diaphragms or the internal check valves. Liquid with an odor consistent with aviation gasoline was observed in the engine-driven fuel pump, the hose from the pump to the servo, in the servo and in the hose from the servo to the flow divider. Both magnetos were removed and produced spark from all electrode towers when rotated by hand. A GPSdata card, and three personal electronic devices were forwarded to the National Transportation Safety Board Vehicle Recorder Laboratory, Washington, DC. No performance data were recovered for the accident takeoff. According to the Pilot's Handbook of Aeronautical Knowledge (FAA-H-8083-25B) Chapter 10, Weight and Balance, excessive weight reduces flight performance in almost every respect. Some of the most important performance deficiencies of an overloaded aircraft include higher takeoff speed, longer takeoff run, reduced rate and angle of climb, and higher stalling speed. ## Aircraft - Registration: [N612DF](https://openairdocs.org/deregistered/N612DF-2017-12-15), registration cancelled 2017-12-15, S/N 172S10201, built 2006 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S10201 - Year built: 2006 - Airframe hours: 4013 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Arrow Aviation LLC - Registered owner: Cessna 616df LLC - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: Annual, July 21, 2017, 17 hours before - Departed: DXR, Danbury, CT - Destination: DXR, Danbury, CT - Airport: DXR, Danbury Muni, runway 26, 4,422 × 150 ft, asphalt - Equipment: Stall warning system, Electronic primary flight display, Electronic multifunction display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: fatal; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; restraint: 4-point; flight hours: 582 total ## Weather - Conditions: Visual (VMC), Day - Wind: 350° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 73 °F, dew point 54 °F - Altimeter: 30.03 inHg - Observed at: KDXR ## 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 20170730012719A](https://openairdocs.org/incident/20170730012719A), Jul 30, 2017: Cessna 172S, Danbury, CT, Substantial damage, 1 fatal. Jul 30, 2017 - received telecom from the FAA the centralized regional operations center (croc) regarding aircraft accident, daily report application (dra)… ## Docket (11 files) The files NTSB released with the investigation on June 17, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=95695. 4.6 MB in all. - Controller Statements (item 1, .PDF, 187 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473460&FileExtension=.PDF&FileName=Controller%20Statements-Master.PDF - Passenger Statements (item 2, .PDF, 275 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473461&FileExtension=.PDF&FileName=Passenger%20Statements-Master.PDF - Police Report (item 3, .PDF, 269 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473462&FileExtension=.PDF&FileName=Police%20Report-Master.PDF - Weight and Balance Information (item 4, .PDF, 849 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473463&FileExtension=.PDF&FileName=Weight%20and%20Balance%20Information-Master.PDF - Excerpt from Information Manual (item 5, .PDF, 274 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473464&FileExtension=.PDF&FileName=Excerpt%20from%20Information%20Manual-Master.PDF - Excerpts from Maintenance Records (item 6, .PDF, 384 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473465&FileExtension=.PDF&FileName=Excerpts%20from%20Maintenance%20Records-Master.PDF - Fueling Record (item 7, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473466&FileExtension=.PDF&FileName=Fueling%20Record-Master.PDF - Photo Array (item 8, .PDF, 6 photos, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473467&FileExtension=.PDF&FileName=Photo%20Array-Master.PDF - Toxicological Report (item 9, .PDF, 103 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473468&FileExtension=.PDF&FileName=Toxicological%20Report-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 10, .PDF, 297 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473469&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF - Wreckage Release and Evidence Control Forms (item 11, .PDF, 266 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473470&FileExtension=.PDF&FileName=Wreckage%20Release%20and%20Evidence%20Control%20Forms-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.