At about 06:06 eastern time, a Piper PA-32RT-300 crashed during an ILS Runway 20 approach to Concord Regional Airport. The pilot was killed. The approach controller asked the pilot if he was familiar with the Notams at Concord, told the pilot that the glide slope was out of service and that the ILS DME was unmonitored. The pilot was further instructed by approach that the AWOS visibility report was unreliable at Concord The pilot was then cleared for approach. The pilot acknowledged the clearance. Thirty seconds later, the controller approved a frequency change and asked the pilot to report canceling IFR when he was on the ground. The pilot did not acknowledge the transmission.
March 30, Concord, N.C. / Piper Turbo Lance II
At about 06:06 eastern time, a Piper PA-32RT-300 crashed during an ILS Runway 20 approach to Concord Regional Airport. The pilot was killed. The approach controller asked the pilot if he was familiar with the Notams at Concord, told the pilot that the glide slope was out of service and that the ILS DME was unmonitored. The pilot was further instructed by approach that the AWOS visibility report was unreliable at Concord The pilot was then cleared for approach. The pilot acknowledged the clearance. Thirty seconds later, the controller approved a frequency change and asked the pilot to report canceling IFR when he was on the ground. The pilot did not acknowledge the transmission....
Key Takeaways:
- A Piper PA-32RT-300 crashed during an ILS approach to Concord Regional Airport, killing the pilot.
- Prior to the crash, the approach controller informed the pilot of critical ILS issues, including an inoperative glide slope, unmonitored DME, and unreliable AWOS visibility.
- Despite these warnings, the pilot was cleared for and acknowledged the approach, but failed to respond to a subsequent frequency change request.
Key takeaways sponsored by Aviator Pro | Start Your Training ->
See a mistake? Contact us.
