# Accident 20200128001879A: Piper AEROSTAR 601P, Springfield, IL, January 28, 2020

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 28, 2020, 15:03 local time
- Place: Springfield, IL
- Airport: Abraham Lincoln Capital
- Damage: Destroyed
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 39.7624° N, 89.5722° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.7624&lon=-89.5722&mi=10
- Aircraft: N6071R, a cancelled registration (https://openairdocs.org/deregistered/N6071R-2023-03-04) (OpenAirDocs)
- Registry model: Piper AEROSTAR 601P (registry code 7106012, https://openairdocs.org/model/piper-aerostar-601p) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER AEROSTAR 601P
- Reported engine: LYCOMING IO-540 SER
- People aboard: 3
- Fatal injuries: 3
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- NTSB investigation: [NTSB CEN20FA070](https://openairdocs.org/ntsb/CEN20FA070) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200128001879A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON JANUARY 28, 2020, ABOUT 1503 CENTRAL STANDARD TIME (CST), N6071R, A PIPER PA-60-601P AIRPLANE, IMPACTED THE TERRAIN WHILE ON AN INSTRUMENT APPROACH TO ABRAHAM LINCOLN CAPITAL AIRPORT (SPI) IN SPRINGFIELD, ILLINOIS.  THE PILOT, 2 PASSENGERS, AND A DOG WERE FATALLY INJURED. THE AIRCRAFT WAS DESTROYED FROM THE IMPACT AND POST IMPACT FIRE.  THE AIRPLANE WAS OWNED BY LKJ PROPERTIES, LLC AND WAS OPERATED AS A PERSONAL PART 91 FLIGHT FROM HUNTSVILLE INTERNATIONAL AIRPORT (HSV) TO SPI ON AN INSTRUMENT FLIGHT RULES (IFR) FLIGHT PLAN.  WEATHER CONDITIONS AT THE ACCIDENT SCENE WERE INSTRUMENT METEOROLOGICAL CONDITIONS (IMC).

ON THE INITIAL APPROACH INTO SPI, THE PIC ATTEMPTED THE INSTRUMENT LANDING SYSTEM (ILS) FOR RUNWAY 31.  PRIOR TO THE APPROACH THE PIC NOTIFIED SPI APPROACH CONTROL THAT HE WAS NOT PICKING UP THE NAVIGATION SIGNAL FOR THE ILS 31.  ATC NOTIFIED THE PIC OF THE CORRECT FREQUENCY.  THE PIC HAD INITIALLY TUNED IN AN INCORRECT FREQUENCY.  THE AIRCRAFT PASSED BACK AND FORTH ACROSS THE FINAL APPROACH PATH AND HAD DIFFICULTY REMAINING ESTABLISHED ON THE APPROACH.  SPI APPROACH CONTROL ASKED THE PIC IF THE AIRCRAFT WAS ESTABLISHED ON THE LOCALIZER AND RECEIVING THE GLIDE SLOPE INDICATIONS.  THE PILOT RESPONDED THAT THEY WERE.  SPI APPROACH CONTROL THEN INSTRUCTED N6071R TO CONTACT SPI TOWER CONTROL.  SPI TOWER CONTROL THEN CLEARED N6071R FOR LANDING.  SPI TOWER CONTROL ADVISED THE PIC THAT HE APPEARED TO BE LEFT OF COURSE AND THE PIC REPLIED "CORRECTING".  SPI TOWER CONTROL THEN ADVISED THE PIC THAT THE AIRPLANE APPEARED TO BE ON COURSE.  THE PIC RESPONDED "IT LOOKS LIKE WE WENT THROUGH THE COURSE."  THE AIRCRAFT WAS WELL RIGHT OF COURSE WHEN THE SPI TOWER CONTROLLER INSTRUCTED N6071R TO CANCEL ANY CLEARANCE, CLIMB AND MAINTAIN 3,000 MSL, AND TURN RIGHT TO HEADING 360.  SPI TOWER CONTROL ADVISED N6071R THAT SPI DEPARTURE CONTROL WOULD VECTOR THEM AROUND FOR ANOTHER APPROACH AND THAT THE PRIOR APPROACH "DIDN'T LOOK SAFE FROM HERE".  SPI TOWER CONTROL THEN ADVISED N6071R TO CONTACT DEPARTURE CONTROL.  SPI APPROACH CONTROL ASKED THE PIC IF HE WOULD LIKE VECTORS BACK TO THE ILS 31 APPROACH OR CHANGE TO THE ILS 22 APPROACH.  THE PIC REPLIED HE WOULD LIKE TO GO BACK TO THE ILS 31.  SPI APPROACH CONTROL ASKED THE PIC IF HE WAS HAVING ISSUES WITH HIS "NAV HEAD" AND THE PIC REPLIED "YUP".  SPI APPROACH CONTROL THEN ASKED IF THE PIC WOULD LIKE AN APPROACH SURVEILLANCE RADAR (ASR) APPROACH.  DUE TO SEVERAL SUBSEQUENT INTERMITTENT RADIO TRANSMISSIONS SPI APPROACH CONTROL ASKED THE PIC IF HE WAS HAVING ELECTRICAL ISSUES TO WHICH HE REPLIED "THAT'S NEGATIVE."  AT THIS TIME THE PIC NOTIFIED SPI APPROACH CONTROL THAT THEY WOULD FLY THE ILS 31 APPROACH AGAIN AND THAT THEY WERE "PICKING UP A LITTLE ICE".  SPI APPROACH CONTROL AGAIN OFFERED THE PIC AN ASR APPROACH AND THE PIC RESPONDED "OKAY, NO WE WILL TRY IT AGAIN, IT JUST, AH, TOOK OFF WHEN WE, AH WHEN WE WERE AH ABOUT 2300."  SPI APPROACH CONTROL BEGAN GIVING N6071R VECTORS BACK FOR THE ILS 31 APPROACH AND ASKED IF THEY WERE STILL IN ICING CONDITIONS.  THE PIC RESPONDED THAT THEY WERE ABOVE THE ICING CONDITIONS AT 3,000 FEET MSL.  SPI APPROACH CONTROL THEN ASKED THE PIC IF THE LANDING GEAR WAS STILL EXTENDED.  THE PIC ACKNOWLEDGED THAT THE LANDING GEAR WAS STILL EXTENDED.  ON THE SECOND APPROACH THE AIRCRAFT PASSED THROUGH APPROACH COURSE AND PARALLELED IT INBOUND.  THE AIRCRAFT REMAINED LEFT OF THE APPROACH COURSE NEVER BECOMING ESTABLISHED ON THE INBOUND COURSE.  ABOUT 5 SECONDS AFTER SPI APPROACH CONTROL INSTRUCTED THE N6071R TO CONTACT SPI TOWER CONTROL, THE AIRCRAFT ENTERED A DESCENDING LEFT HAND TURN AWAY FROM THE APPROACH COURSE.  ABOUT 1 MINUTE LATER THE AIRCRAFT IMPACTED TERRAIN ABOUT 7 MILES SOUTHEAST OF SPI.

## The NTSB's investigation of this event (1)

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.

- [NTSB CEN20FA070](https://openairdocs.org/ntsb/CEN20FA070), Jan 28, 2020: Piper PA60 (N6071R), Springfield, IL, destroyed, 3 fatal. Probable cause: The pilot’s failure to follow the instrument landing system (ILS) course guidance during the instrument approach.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.
