Narrative:

Aircraft X was on an IFR flight plan inbound to cid. Prior to taking the position; the aircraft seemed to be having difficulties tracking the localizer in after the controller cleared him for the ILS 27 approach. He was switched to tower and was issued a low altitude alert by the tower controller; all while turning left and right and not flying straight towards the airport on the approach. The approach controller told tower to put him on a 360 heading; climb him to 2;500 (the MVA); and to switch him back to approach for re-sequence.the approach controller then re-sequenced him and gave him an eastbound heading. I then relieved the controller and began working aircraft X. I gave him headings to intercept and cleared him for the ILS 27. He shot through the final; so I gave him a northbound heading to intercept. He then began flying westbound and paralleled the runway to the south; instead of flying the 290 heading. I asked him if he required to declare an emergency and he said no; but that he was having some problems with his dg equipment. I then began issuing him no-gyro vectors and was able to get him back on the localizer. At one point I issued him a low altitude alert. He advised that he was picking up icing on his wing. The aircraft arrived safely on the ground but did land long and spun his aircraft at the end of the runway.I wish the pilot would have let us know sooner that he was picking up icing and having equipment issues. We had no idea why he was not taking our turns and not responding to our calls. I'm sure he was shaken up and trying to keep control of his aircraft; but had we known what was happening we could have offered him more assistance and sooner.

Related reports:

Google
 

Original NASA ASRS Text

Title: CID TRACON Controller reported an aircraft not flying the ILS correctly and assisted in getting the aircraft safely on to the ground.

Narrative: Aircraft X was on an IFR flight plan inbound to CID. Prior to taking the position; the aircraft seemed to be having difficulties tracking the localizer in after the Controller cleared him for the ILS 27 approach. He was switched to tower and was issued a low altitude alert by the tower controller; all while turning left and right and not flying straight towards the airport on the approach. The approach controller told tower to put him on a 360 heading; climb him to 2;500 (the MVA); and to switch him back to approach for re-sequence.The approach controller then re-sequenced him and gave him an eastbound heading. I then relieved the controller and began working Aircraft X. I gave him headings to intercept and cleared him for the ILS 27. He shot through the final; so I gave him a northbound heading to intercept. He then began flying westbound and paralleled the runway to the south; instead of flying the 290 heading. I asked him if he required to declare an emergency and he said no; but that he was having some problems with his DG equipment. I then began issuing him no-gyro vectors and was able to get him back on the localizer. At one point I issued him a low altitude alert. He advised that he was picking up icing on his wing. The aircraft arrived safely on the ground but did land long and spun his aircraft at the end of the runway.I wish the pilot would have let us know sooner that he was picking up icing and having equipment issues. We had no idea why he was not taking our turns and not responding to our calls. I'm sure he was shaken up and trying to keep control of his aircraft; but had we known what was happening we could have offered him more assistance and sooner.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.