# NTSB CEN16LA016: Cirrus Design SR22, N849CD, Lancaster, TX, October 17, 2015 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: October 16, 2015, 19:40 local (Oct 17, 2015, 00:40 UTC) - Place: Lancaster, TX - Coordinates: 32.558887, -96.699722 - Nearby events: https://openairdocs.org/map.md?lat=32.5589&lon=-96.6997&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Serious injuries - Injuries: 1 serious, 1 uninjured - Status: Completed, report February 17, 2016 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Flight Standards District Office - NTSB case key (mKey): 92200 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN16LA016 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92200/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92200 - Page: https://openairdocs.org/ntsb/CEN16LA016 ## Probable cause The pilot’s failure to maintain a proper glidepath during a night visual approach, which resulted in impact with a power line. Contributing to the accident was an inoperative precision approach path indicator. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cirrus Design SR22, 38 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2130001), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cirrus Design SR22, 14 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2130001), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Awareness of condition (probable cause); cases with it: [Cirrus Design SR22, 2 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=2130001), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cirrus Design SR22, 94 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2130001), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Attention/monitoring: monitoring environment](https://openairdocs.org/ntsb-findings/02021545): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Cirrus Design SR22, 3 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md?model=2130001), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md) - [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on operation (probable cause); cases with it: [Cirrus Design SR22, 13 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=2130001), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md) - [Approach aid coverage/avail: approach lighting](https://openairdocs.org/ntsb-findings/03012015): Environmental issues › Operating environment · Effect on operation (probable cause); cases with it: [Cirrus Design SR22, 1 case](https://openairdocs.org/ntsb-findings/03012015/cases.md?model=2130001), [All aircraft, 4 cases](https://openairdocs.org/ntsb-findings/03012015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Cirrus Design SR22, 12 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=2130001), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis The private pilot reported that he was flying a night visual pattern to a nontowered airport. Due to another airplane on final approach, the pilot extended the downwind leg to create spacing. While on the extended final in a rural area with low lighting, the pilot descended the airplane well below a proper glidepath to the runway and struck an unlit high-voltage power line located about 1 mile from the runway. After feeling a jolt, the passenger deployed the airframe's parachute system. The airplane subsequently became suspended in a second set of power lines, and the pilot and passenger safely egressed the airplane. At the time of the accident, the precision approach path indicators (PAPI) for both runways were inoperative due to maintenance. A notice to airmen (NOTAM) for the PAPI closure was active at the time of the accident, and the pilot was aware of the NOTAM. The dark conditions and extended final likely created a visual illusion in which the pilot thought he was higher than he was; without an operative PAPI, the pilot had limited external references to assist him in maintaining a proper glidepath during the approach. ## Factual narrative On October 16, 2015, about 1940 central daylight time, a Cirrus SR22 airplane, N849CD, was destroyed after striking a power line during approach to the Lancaster Regional Airport (LNC), Lancaster, Texas. The pilot was not injured and the passenger was seriously injured. The airplane was registered to and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Night visual meteorological conditions prevailed for the flight, which departed without a flight plan from the Mid-Way Regional Airport (JWY), Midlothian, Texas about 1850. The pilot stated he was practicing a 'no flap' visual approach to Runway 31 at LNC and extended his downwind leg to create spacing from an aircraft that was on final approach. As the pilot flew toward Runway 31 on final approach, the airplane struck the upper static line of a set of unlit high voltage power lines, located about one mile prior to the threshold of Runway 31. After feeling a jolt, the passenger deployed the Cirrus Airframe Parachute System (CAPS). The airplane continued northwest about 200 feet and impacted a second set of high voltage power lines. The airplane and CAPS became entangled in the second set of power lines and the airplane came to rest suspended by the parachute, with the nose about three feet above the ground. The pilot and passenger exited through the pilot's side door and jumped to the ground. The airplane was subsequently consumed by a post-crash fire. The pilot's final approach to Runway 31 was over a rural area with low cultural lighting. At the time of the accident, the precision approach path indicator (PAPI) for both runways was inoperative due to maintenance. The PAPI is a visual aid that provides glideslope information to help a pilot acquire and maintain the correct glide path to a runway. A Notice to Airman (NOTAM) concerning the inoperative PAPI was active, which the pilot stated he was aware of. The airport manager and Texas Department of Transportation personnel reviewed obstacle clearance information for LNC. The closest tower to the power line struck was 592 feet msl, which was 105 feet above the touchdown zone elevation for Runway 31. This tower and other power lines/obstacles in the vicinity of LNC were below the 34:1 obstacle clearance plane required for a non-precision runway. ## Aircraft - Registration: [N849CD](https://openairdocs.org/deregistered/N849CD-2018-03-07), registration cancelled 2018-03-07, S/N 0224, built 2002 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SR22 - Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 0224 - Year built: 2002 - Airframe hours: 832 - Engines: CONT MOTOR IO-550 SERIES 310 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Operator: Ataee Mahmood - Registered owner: Ataee Mahmood - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 18, 2015, 3 hours before - Departed: JWY, Waxahachie, TX - Destination: LNC, Lancaster, TX - Airport: LNC, Lancaster Rgnl, runway 31, 6,502 × 100 ft, asphalt - Equipment: Electronic primary flight display, Electronic multifunction display, Auto-pilot, Airframe parachute, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review July 22, 2015; seat: left; restraint: 4-point; flight hours: 935 total, 265 in this make and model, 870 as pilot in command, 36 in the last 90 days, 3 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Wind: 50° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 45 °F - Altimeter: 30.22 inHg - Observed at: KLNC, 2 nm away ## 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 20151016022029A](https://openairdocs.org/incident/20151016022029A), Oct 16, 2015: Cirrus Design Corp SR22, Lancaster, TX, Destroyed. Pilot and passenger on PT91 flights doing practice emergency procedures. While on downwind leg on landing approach to airport (lns) the pilot was in contact… ## Docket (2 files) The files NTSB released with the investigation on December 17, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92200. 3.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435042&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photos of Accident Airplane (item 2, .PDF, 2 photos, 280 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40435043&FileExtension=.PDF&FileName=Photos%20of%20Accident%20Airplane-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.