Plane crash map Locate crash sites, wreckage and more

N451TD accident description

Pennsylvania map... Pennsylvania list
Crash location 40.422778°N, 78.211667°W
Reported location is a long distance from the NTSB's reported nearest city. This often means that the location has a typo, or is incorrect.
Nearest city Williamsburg, PA
41.179508°N, 79.395322°W
81.0 miles away
Tail number N451TD
Accident date 19 Apr 2018
Aircraft type Cirrus Design Corp SR22
Additional details: None

NTSB Factual Report

HISTORY OF FLIGHT

On April 19, 2018, at 0843 eastern daylight time, a Cirrus SR22 airplane, N451TD, impacted terrain near Williamsburg, Pennsylvania. The private pilot and one passenger were fatally injured. The airplane was destroyed, and a postimpact fire consumed most of the wreckage. The airplane was registered to CPD-JJD, LLC, and operated by the pilot as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. Instrument meteorological conditions (IMC) prevailed along the flight route about the time of the accident, and an instrument flight rules (IFR) flight plan had been filed. The airplane departed Lancaster Airport (LNS), Lancaster, Pennsylvania, at 0734 and was initially en route to South Bend International Airport (SBN), South Bend, Indiana, but the pilot chose to divert toward Altoona-Blair County Airport (AOO), Altoona, Pennsylvania.

The pilot received a weather briefing the night before the accident and filed a flight plan. Refer to the Meteorological Information section for more information. A review of air traffic control (ATC) communications and radar data provided by the Federal Aviation Administration (FAA) revealed that, about 0828, while the airplane was en route to SBN on a 284° heading and about 5,425 ft mean sea level (msl), the pilot contacted an approach controller at John Murtha Johnstown-Cambria County Airport (JST), Johnstown, Pennsylvania, and requested to divert to JST (18 miles southwest of the airplane's position) due to ice accumulation on the airplane. The controller advised the pilot that the clouds at JST were overcast at 200 ft above ground level (agl) and that the clouds at AOO (30 miles southeast of the airplane's position) were overcast at 500 ft agl. About 0831, the pilot requested vectors to AOO for an instrument landing system (ILS) approach. After the controller provided the vectors, the pilot requested to descend to 4,000 ft msl, but the controller cleared him to 4,500 ft msl, which was the lowest altitude he could clear the airplane to descend to in that geographical area. Figure 1 shows a Google Earth overlay of the airplane's radar track in red, the AOO approach localizer path in white.

About 0842, the controller advised the pilot that the airplane had passed through the localizer for the ILS approach to runway 21 at AOO, and the pilot stated that he still wanted to land at AOO and requested vectors to intercept the localizer. The controller issued additional vectors for the pilot to make a box pattern to intercept the localizer; the airplane then turned left turn toward the north. At 0842:33, the airplane began a left standard rate turn and remained about 4,000 ft msl. At 0843:12, the airplane started to descend, and the airspeed increased. At 0843:38, the airplane descended through 2,525 ft msl and continued in a tight, left spiral turn. The final radar point was recorded at 0843:52 at 1,850 ft msl, at which point the airplane was still in a tight, left spiraling turn. Subsequently, radar contact was lost, and no additional communications were received from the pilot. See figure 2 for a radar track showing the initial left turn followed by the spiraling left turns.

Before the final left turn and descending spiral, the flight path and altitudes were normal with no erratic maneuvers or anomalies noted.

PERSONNEL INFORMATION

A review of the pilot's logbook revealed that he accumulated 70 hours of total flight experience from 1980 to 1985. He did not log any additional flight time until 2011. He first flew the accident airplane on January 31, 2014, and then exclusively logged flights in the accident airplane from April 9, 2014, until the accident date.

The pilot's flight instructor stated that he had flown with the pilot six times in the 6 months before the accident. Four of the flights were conducted for the purpose of maintaining instrument currency and proficiency. Their most recent flight was on November 30, 2017, during which the pilot completed ILS and GPS approaches in simulated IMC.

The pilot's logbooks showed that he had completed the recent instrument experience requirements in accordance with 14 CFR Section 61.57, "Recent flight experience: Pilot in command."

AIRCRAFT INFORMATION

General

The altitude indicating system and transponder, which were most recently tested in accordance with the requirements of 14 CFR Sections 91.411 and 91.413, "Altimeter system and altitude reporting equipment tests and inspections" and "ATC transponder tests and inspections," respectively, on September 26, 2017.

The airplane was not equipped with an anti-icing or deicing system, thus it was not equipped for flight in icing conditions.

The pilot had the ForeFlight application on a mobile device, which provided instrument approach plates; paper approach plates were found at the accident site.

The cockpit instrumentation included an airspeed indicator, attitude indicator, altimeter and a turn coordinator, vertical speed indicator, Garmin mechanical course deviation indicator, and Sandel SN3308 electronic horizontal situation indicator. The airplane was also equipped with an S-TEC 55X autopilot, a Garmin GTX345 transponder, dual Garmin GNS 430 units, and an ARNAV ICDS-2000 multifunction display (MFD) with an engine monitoring module (EMM-35) that displayed engine data. The ARNAV unit displayed, in part, navigational waypoints, course line, and ground speed and had a separate database, which displayed terrain elevations based on position. The Garmin GNS 430 was approved for IFR operations; however, the ARNAV MFD was for reference only and was not certified for flight in IMC.

Cirrus Airframe Parachute System (CAPS)

The airplane was equipped with a Ballistic Recovery Systems ballistic recovery parachute system. According to Cirrus, the CAPS will lower the airplane's entire airframe to the ground when all alternatives to land the airplane have been exhausted. The CAPS consisted of a parachute, a solid-propellant rocket to deploy the parachute, a rocket activation handle, and a Kevlar harness embedded within the fuselage structure. The pilot could activate the system by pulling on a T-handle mounted on the cockpit ceiling above the pilot's right shoulder, which in turn activated the firing pin mechanism that then ignited the solid-propellant rocket in the parachute enclosure.

In the airplane's Pilot's Operating Handbook "Normal Procedures, Preflight Walk-Around" checklist, item 1 states, "CAPS Handle…Pin Removed." In the "Before Starting Engine" checklist, item 4 states, "Verify CAPS handle safety pin is removed." In the "Before Takeoff" checklist, item 2 states, "CAPS Handle…Verify Pin Removed."

METEOROLOGICAL INFORMATION

The pilot received a weather briefing the night before the accident flight at 2127 and filed an IFR flight plan via the Foreflight mobile application with a planned flight route of LNS-EWC-NORNA-SBN at 6,000 ft msl. The pilot entered the same route into the application two times before he filed the flight plan, which is consistent with his comparing the winds aloft at two different flight altitudes.

The ForeFlight weather briefing contained the standard weather information valid for a departure time of 0645 on April 19, but some of the weather forecast products did not provide forecast information of the weather conditions at the time of departure because the weather briefing was requested 10 hours before the flight. The graphical forecast products from the weather briefing predicted cloud cover as low as 2,000 ft msl along the flight route, and the surface forecast predicted marginal visual flight rules conditions with likely snow shower activity. The AOO and JST TAFs called for IFR and low IFR conditions between 0200 and 1000 on April 19. The AIRMET received during the weather briefing was only valid until 0500 on April 19, which was before the intended departure time. At the time of the accident, there was an active AIRMET for moderate icing, IFR/mountain obscuration, and low-level turbulence. An updated AIRMET advisory from as late as 0452 on April 19 was recorded via the flight plan identification number, but it could not be determined if the pilot checked the updated AIRMET information before the flight. No records were found indicating whether the pilot retrieved any other weather information before or during the flight.

Icing Potential

Current icing potential (CIP) and forecast icing potential (FIP) products are intended to be supplemental to other icing advisories, such as AIRMETs and SIGMETs. The FIP products indicated a 50 to 70% probability of icing at trace-to-moderate levels above the accident site from 4,000 to 6,000 ft msl at 0900. The FIP indicated a 40 to 50% probability of supercooled large droplet (SLD) over the accident area around the accident time at 6,000 ft msl. The CIP product indicated a 60 to 85% probability of icing at light-to-moderate levels above the accident site from 4,000 to 6,000 ft msl at 0900. The CIP also indicated a 10 to 40% probability of SLD near the accident site at 0900 between 4,000 and 6,000 ft msl and a 0 to 40% probability of SLD near the accident site at 0800 between 4,000 and 6,000 ft msl. The CIP/FIP information would have been available to the pilot before the accident flight departed.

The National Weather Service Aviation Weather Center that issues the CIP and FIP advises, "NOTE: CIP/FIP is intended for flight planning purposes and should always be used in combination with icing information from all available sources including AIRMETs, SIGMETs, and PIREPs. CIP/FIP aid flight planning and situational awareness through graphical depiction of current and forecast icing conditions across an area or along a route of flight. NOTE: Pilots of aircraft that are not certified for flight into known or forecast icing conditions should be especially cautious of areas displaying any type of icing severity, regardless of the probability indicated on CIP graphics."

Satellite Data

Figure 3 shows the compiled Geostationary Operational Environmental Satellite 16 (GOES-16) infrared and visible data and the pilot's communication with ATC at the time he requested to divert with the direction of travel indicated with a red arrow. This imagery indicated that the airplane was in areas of abundant cloud cover with cloud top temperatures between -5° and -15°C throughout the flight. The airplane turned back toward the east before reaching an area of cloud top temperatures between -15° and -25°C. The cloud-top heights above the accident site at around the time of the accident were about 10,400 ft msl. The IMC and icing conditions would have ended above the cloud layer.

WRECKAGE AND IMPACT INFORMATION

The airplane impacted a field behind a residential property 9.5 miles northeast of AOO (see figure 4, which shows the initial impact point and the airplane wreckage). The wreckage debris path was about 200 ft long, on a magnetic heading of 150°, and at an elevation 1,025 ft msl.

Ground scars at the accident site and damage to the airplane were consistent with the airplane impacting terrain in a steep, nose-low, wings-level attitude. The left wing inspection panels and the pitot tube were found in the horizontal ground scar, which can be seen on the lower left side of figure 4. The ground scars surrounding the center impact crater were consistent with the shape of the wing leading edges and the tricycle landing gear. The engine, firewall, and all three propeller blades were found in the center impact crater, which was about 3 ft deep. A postimpact fire consumed most of the wreckage, but all major airplane structural components were located within the debris field.

The engine mounts and nose landing gear brace remained attached to the engine with the firewall. The throttle, mixture, and propeller control cables remained attached to their respective control levers. The front portion of the oil sump was flattened against the bottom side of the engine, and the aft portion of the oil sump was impact-damaged and displaced aft, exposing the bottom crankcase halves.

The three-bladed, constant-speed propeller remained attached to the crankshaft, but two of the blades were separated just outboard of the shank. The third blade remained attached to the hub and was bent aft around the engine's left side and twisted toward low pitch; the outboard tip was impact-separated from the blade. The leading edge of one of the separated blades exhibited deep gouges. The propeller spinner was crushed aft around the propeller hub.

Both the directional and turn coordinator gyros exhibited rotational scoring and signs of rotation at impact.

The ARNAV ICDS-2000 and EMM-35 were destroyed by fire, and data extraction was not possible.

The CAPS activation handle remained in its holder with the safety pin installed as shown in figure 5. The CAPS was found deployed, and the CAPS solid rocket propellant was expended. The parachute was found deployed, and it extended along the debris path. Portions of the CAPS that remained within the main wreckage were consumed by fire. All evidence revealed that the CAPS was not activated in flight but rather that it deployed due to impact forces and thermal exposure.

Although the postaccident examination was limited due to postimpact fire damage, examinations of the airframe and engine did not reveal evidence of any preaccident mechanical malfunctions or anomalies that would have precluded normal operation.

MEDICAL AND PATHOLOGICAL INFORMATION

Mount Nittany Medical Center, State College, Pennsylvania, conducted an autopsy of the pilot. The autopsy report concluded that the cause of death was "blunt force trauma." The examination was limited due to the extent of damage to the pilot's body as a result of the accident. However, the autopsy was able to determine that the pilot had mild-to-moderate atherosclerotic coronary artery disease with 50% stenosis of the left coronary artery and 30% stenosis of the left circumflex coronary artery. The examination of the remaining available cardiac tissue was unremarkable.

Toxicology testing performed by the laboratory at FAA Forensic Sciences identified the following: 10 mg/dL ethanol in liver tissue but no ethanol in the muscle tissue, diphenhydramine in liver and muscle tissue, amlodipine in kidney tissue, atenolol in kidney and heart tissue, 0.039 µg/mL 7-amino-clonazepam in kidney tissue, and 0.026 µg/mL 7-amino-clonazepam in lung tissue.

Ethanol is an intoxicant, which, after absorption, is uniformly distributed throughout all tissue and body fluids. It may also be produced in postmortem tissue by microbial action.

Diphenhydramine is a sedating antihistamine used to treat allergy symptoms and as a sleep aid. It is available over the counter under the names Benadryl and Unisom. In a driving simulator study, a single 50 mg dose of diphenhydramine impaired driving ability more than a blood alcohol concentration of 0.100%. Diphenhydramine carries the following U.S. Food and Drug Administration (FDA) warning: "may impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery)." Compared to other antihistamines, diphenhydramine causes marked sedation, which is the rationale for its use as a sleep aid. Altered mood and impaired cognitive and psychomotor performance may also be observed.

Amlodipine and atenolol are nonimpairing blood pressure medications, and the pilot had reported them to the FAA. According to records obtained from the pilot's primary care physician, at the time of the accident, the pilot had been prescribed both atenolol and amlodipine to control his hypertension.

Clonazepam, the parent drug that is metabolized into 7-amino-clonazepam (an inactive metabolite) is a sedating benzodiazepine used to treat panic and anxiety disorders and certain kinds of seizures. Clonazepam carries the following FDA warning: "Since clonazepam produces central nervous system (CNS) depression, patients receiving this drug should be cautioned against engaging in hazardous occupations requiring mental alertness, such as operating machinery or driving a motor vehicle. They should also be warned about the concomitant

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.