Loss of control Accident Piper PA-60-601P Aerostar 700 Superstar N6071R,
ASN logo
ASN Wikibase Occurrence # 232591
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 28 January 2020
Time:15:03
Type:Silhouette image of generic AEST model; specific model in this crash may look slightly different    
Piper PA-60-601P Aerostar 700 Superstar
Owner/operator:LKJ Properties LLC
Registration: N6071R
MSN: 61P-0686-7963324
Year of manufacture:1979
Total airframe hrs:3542 hours
Engine model:Lycoming IO-540-AA1A5
Fatalities:Fatalities: 3 / Occupants: 3
Aircraft damage: Destroyed
Category:Accident
Location:near Abraham Lincoln Capital Airport (KSPI), Springfield, IL -   United States of America
Phase: Approach
Nature:Private
Departure airport:Huntsville International Airport, AL (HSV/KHSV)
Destination airport:Springfield-Abraham Lincoln Capital Airport, IL (SPI/KSPI)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
On January 28, 2020, about 1503 central standard time, a Piper PA-60-601P airplane, N6071R, collided with terrain while on an instrument approach to Abraham Lincoln Capital Airport (SPI), Springfield, Illinois. The airline transport pilot, 2 passengers, and a dog were fatally injured. The airplane was destroyed during a postimpact fire. The airplane was owned by LKJ Properties, LLC, and operated under Title 14 Code of Federal Regulations Part 91 on an instrument flight rules (IFR) flight plan. Day instrument meteorological conditions (IMC) prevailed at the accident site. The personal cross-country flight departed Huntsville International Airport (HSV), Huntsville, Alabama, at 1301.

The pilot was conducting an instrument landing system (ILS) approach in instrument meteorological conditions at the conclusion of a cross-country flight. The airplane had been cleared to land, but the tower controller canceled the landing clearance because the airplane appeared not to be established on the localizer as it approached the locator outer marker. The approach controller asked the pilot if he was having an issue with the airplane’s navigation indicator, and the pilot replied, “yup.” Rather than accept the controller’s suggestion to use approach surveillance radar (ASR) approach instead of the ILS approach, the pilot chose to fly the ILS approach again. The pilot was vectored again for the ILS approach, and the controller issued an approach clearance after he confirmed that the pilot was receiving localizer indications on the airplane’s navigation equipment.

The airplane joined the localizer and proceeded toward the runway while descending. The pilot was instructed to contact the tower controller; shortly afterward, the airplane entered a left descending turn away from the localizer centerline. At that time, the airplane was about 3 nautical miles from the locator outer marker. The pilot then told the tower controller, “we’ve got a prob.” The tower controller told the pilot to climb and maintain 3,000 ft msl and to turn left to a heading of 180°. The pilot did not respond.

During the final 5 seconds of recorded track data, the airplane’s descent rate increased rapidly from 1,500 to about 5,450 ft per minute. The airplane impacted terrain about 1 nm left of the localizer centerline in a left-wing-down and slightly nose down attitude at a groundspeed of about 90 knots. A postimpact fire ensued.

Although the pilot was instrument rated, his recent instrument flight experience could not be determined with the available evidence for this investigation. Most of the fuselage, cockpit, and instrument panel was destroyed during the postimpact fire, but examination of the remaining wreckage revealed no anomalies. Acoustic analysis of audio sampled from doorbell security videos was consistent with the airplane's propellers rotating at a speed of 2,500 rpm before a sudden reduction in propeller speed to about 1,200 rpm about 2 seconds before impact.

The airplane’s flightpath was consistent with the airplane’s avionics receiving a valid localizer signal during both instrument approaches. However, about 5 months before the accident, the pilot told the airplane’s current maintainer that the horizontal situation indicator (HSI) displayed erroneous heading indications. The maintainer reported that a replacement HSI was purchased and shipped directly to the pilot to be installed in the airplane; however, the available evidence for the investigation did not show whether the malfunctioning HSI was replaced before the flight. The HSI installed in the airplane at the time of the accident sustained significant thermal and fire damage, which prevented testing.

During both ILS approaches, the pilot was cleared to maintain 3,000 ft mean sea level (msl) until the airplane was established on the localizer. During the second ILS approach, the airplane descended immediately, even though the airplane was below the lower limit of the glideslope. Although a descent to the glideslope intercept altitude (2,100 ft msl) would have been acceptable after joining the localizer, such a descent was not consistent with how the pilot flew the previous ILS approach, during which he maintained the assigned altitude of 3,000 ft msl until the airplane intercepted the glideslope.

If the HSI provided erroneous heading information during the flight, it could have increased the pilot’s workload during the instrument approach and contributed to a breakdown in his instrument scan and his ability to recognize the airplane’s deviation left of course and descent below the glideslope; however, it is unknown if the pilot had replaced the HSI.

Probable Cause: The pilot’s failure to follow the instrument landing system (ILS) course guidance during the instrument approach.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN20FA070
Status: Investigation completed
Duration: 3 years
Download report: Final report

Sources:

https://www.wandtv.com/news/plane-crashes-in-sangamon-county/article_676b2910-4216-11ea-9434-0b6536c13aeb.html
https://newschannel20.com/news/local/plane-crashes-in-sangamon-county
https://abc7chicago.com/twin-engine-plane-crashes-behind-home-near-springfield-airport-officials-say/5886205/

NTSB
https://flightaware.com/live/flight/N6071R/history/20200128/1835Z/KHSV/KSPI
https://www.flightradar24.com/data/aircraft/n6071r#23ae2640
https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=N6071R

https://www.aircraftdealer.com/dealers/j/jonathanadelberg/70059/big_z.PNG.jpg (Photo)

Location

Images:






Photos: NTSB

Revision history:

Date/timeContributorUpdates
28-Jan-2020 22:25 Geno Added
28-Jan-2020 22:49 Geno Updated [Aircraft type, Source]
28-Jan-2020 22:58 Geno Updated [Aircraft type, Registration, Cn, Operator, Departure airport, Source]
29-Jan-2020 02:29 Captain Adam Updated [Total fatalities, Total occupants, Location, Source, Damage, Narrative]
29-Jan-2020 02:37 Iceman 29 Updated [Time, Source, Embed code]
29-Jan-2020 02:38 Captain Adam Updated [Embed code, Narrative]
29-Jan-2020 02:41 RobertMB Updated [Time, Aircraft type, Cn, Location, Nature, Source, Embed code, Narrative]
29-Jan-2020 02:43 Iceman 29 Updated [Embed code]
29-Jan-2020 02:44 Iceman 29 Updated [Time, Source, Embed code]
29-Jan-2020 02:47 Iceman 29 Updated [Embed code]
29-Jan-2020 02:54 Iceman 29 Updated [Photo]
29-Jan-2020 02:55 Iceman 29 Updated [Source, Photo]
29-Jan-2020 03:03 Iceman 29 Updated [Narrative]
29-Jan-2020 03:47 RobertMB Updated [Registration, Source, Narrative]
29-Jan-2020 05:53 Captain Adam Updated [Location, Narrative]
29-Jan-2020 14:46 harro Updated [Destination airport]
29-Jan-2020 16:46 LarsonC210 Updated [Narrative]
29-Jan-2020 19:41 Iceman 29 Updated [Embed code]
29-Jan-2020 19:48 Iceman 29 Updated [Source, Embed code]
13-Feb-2020 14:25 AnAmericanIn Updated [Source, Narrative]
13-Jun-2021 17:56 aaronwk Updated [Time, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org