Narrative:

Prior to the approach phase; the flight was a normal IFR flight. Conditions were IMC for most of the flight at 7;000 feet. Checked on with indianapolis center and was asked if I had weather and notams at sjs as well as my approach request. I confirmed weather and notams and requested the RNAV (GPS) runway 21 into sjs; direct zusri (IAF). I was immediately cleared to zusri by center. I then loaded the same approach into the garmin 530W. I was handed off to huntington approach. Approach stated that zusri was not on the approach plate; and I was then cleared direct ecane. I acknowledged the new fix and while loading ecane into the garmin 530W; discovered that it was not in the database. I notified huntington approach that ecane was neither in my GPS database nor on my approach plate. Approach then asked if I had the correct approach plate for the sjs RNAV (GPS) runway 21. I once again checked my approach plate provided by foreflight (ipad app) and noted the version. There were no updates pending during my preflight procedures. I had no evidence available to me that my approach plate was not correct or current. As it turns out; ecane was an IAF on the outdated approach procedure. Hunting approach then asked if I had the fix 'gence' (if/IAF) on my approach plate. I responded affirmative. I was then cleared direct gence. I reloaded the approach into the GPS (3rd change in GPS programming) with the gence IAF and proceeded direct. By this time I was concentrating on eliminating the distractions caused by the conflicting approach procedure publications. A couple minutes later; huntington approach asked if I would accept radar vectors to final. I answered affirmative and received an assigned heading. I reloaded the approach for radar vectors (4th change in GPS reprogramming) and intercepted final about 4 nm from gence at 4;100 feet. Passed gence and encountered VMC at 3;900 MSL. I canceled IFR shortly thereafter. Final approach and landing were normal.I contacted foreflight immediately after the flight and confirmed with them that I had the most recent published approach procedure. The airport manager called huntington tower; in my presence; to ask them if they were aware that both RNAV (GPS) approaches into sjs had recently changed. They stated they were not aware until after I landed and they contacted indianapolis center and confirmed the changes with them. The significant issues were prolonged pilot/controller confusion; as well as spikes in pilot/controller workload during a critical phase of flight. I am not at all familiar with the methods that ATC facilities use to maintain their publications. I do know this was the first time I experienced an incident like this; and found it very surprising that it could happen. I also do not understand how ATC could have outdated approach procedure. The flight was successful in that a safe landing occurred.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reports of flying IFR to an airport and receives clearance to a specific fix. The fix is not on his approach plate and he questions ATC. ATC Vectors the pilot to the IAF and then later pilot cancels IFR. ATC did not have current IFR approach plates and was using an old approach.

Narrative: Prior to the approach phase; the flight was a normal IFR flight. Conditions were IMC for most of the flight at 7;000 feet. Checked on with Indianapolis Center and was asked if I had weather and NOTAMs at SJS as well as my approach request. I confirmed weather and NOTAMs and requested the RNAV (GPS) RWY 21 into SJS; direct ZUSRI (IAF). I was immediately cleared to ZUSRI by Center. I then loaded the same approach into the Garmin 530W. I was handed off to Huntington Approach. Approach stated that ZUSRI was not on the approach plate; and I was then cleared direct ECANE. I acknowledged the new fix and while loading ECANE into the Garmin 530W; discovered that it was not in the database. I notified Huntington Approach that ECANE was neither in my GPS database nor on my approach plate. Approach then asked if I had the correct approach plate for the SJS RNAV (GPS) RWY 21. I once again checked my approach plate provided by ForeFlight (iPad App) and noted the version. There were no updates pending during my preflight procedures. I had no evidence available to me that my approach plate was not correct or current. As it turns out; ECANE was an IAF on the outdated approach procedure. Hunting Approach then asked if I had the fix 'GENCE' (IF/IAF) on my approach plate. I responded affirmative. I was then cleared direct GENCE. I reloaded the approach into the GPS (3rd change in GPS programming) with the GENCE IAF and proceeded direct. By this time I was concentrating on eliminating the distractions caused by the conflicting approach procedure publications. A couple minutes later; Huntington Approach asked if I would accept radar vectors to final. I answered affirmative and received an assigned heading. I reloaded the approach for radar vectors (4th change in GPS reprogramming) and intercepted final about 4 nm from GENCE at 4;100 feet. Passed GENCE and encountered VMC at 3;900 MSL. I canceled IFR shortly thereafter. Final approach and landing were normal.I contacted ForeFlight immediately after the flight and confirmed with them that I had the most recent published approach procedure. The airport manager called Huntington Tower; in my presence; to ask them if they were aware that both RNAV (GPS) approaches into SJS had recently changed. They stated they were not aware until after I landed and they contacted Indianapolis Center and confirmed the changes with them. The significant issues were prolonged pilot/controller confusion; as well as spikes in pilot/controller workload during a critical phase of flight. I am not at all familiar with the methods that ATC facilities use to maintain their publications. I do know this was the first time I experienced an incident like this; and found it very surprising that it could happen. I also do not understand how ATC could have outdated approach procedure. The flight was successful in that a safe landing occurred.

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.