Narrative:

Issue with NOTAM's; takeoff landing data; and airport diagram. ACARS conditions were set to request takeoff data for [runway] 04 and [runway] 04/[intersection] a in order to give us the flexibility to depart either full length or from an intersection. Takeoff data message was received; reviewed; and speeds/configuration were set. Fay issued taxi instructions to taxi to [runway] 4 via K hold short of a. We were then issued further instructions to follow another aircraft to [runway] 4. I was expecting to depart from [runway] 04/[intersection] a and not back taxi full length. I then became aware that the fay airport diagram page was incorrect and did not show that taxiway a went to full length and the indicated a intersection was renamed K. I followed the other aircraft to [runway] 4; full length via a; reset data for full length and departed with no issue. The problem is three fold: 1) the fay airport diagram does not correctly reflect the new and renamed taxiways. 2) there are no notams reflecting these changes either on ATIS or in the weather package. 3) the ACARS runways on the takeoff and landing data report are incorrect. Full length does not require a back taxi; 04/a is actually full length; and 04/K (the old a) does not exist. While it was not a performance issue for us; it could be. Additionally why has fay tower not issued notams reflecting these changes; jeppesen has not changed the airport diagram; and there are no chart change notices? If these changes had been made; aerodata would have the correct information and FCC could make the necessary changes.

Google
 

Original NASA ASRS Text

Title: An air carrier pilot noted the FAY Airport runway and taxiway configuration have changed so that Taxiway A extends the full length of the lengthened Runway 4 but his chart and NOTAMs do not reflect the change.

Narrative: Issue with NOTAM's; Takeoff Landing Data; and Airport Diagram. ACARS conditions were set to request takeoff data for [Runway] 04 and [Runway] 04/[Intersection] A in order to give us the flexibility to depart either full length or from an intersection. Takeoff data message was received; reviewed; and speeds/configuration were set. FAY issued taxi instructions to taxi to [Runway] 4 via K hold short of A. We were then issued further instructions to follow another aircraft to [Runway] 4. I was expecting to depart from [Runway] 04/[Intersection] A and not back taxi full length. I then became aware that the FAY Airport Diagram page was incorrect and did not show that Taxiway A went to full length and the indicated A Intersection was renamed K. I followed the other aircraft to [Runway] 4; full length via A; reset data for full length and departed with no issue. The problem is three fold: 1) The FAY Airport Diagram does not correctly reflect the new and renamed taxiways. 2) There are no NOTAMs reflecting these changes either on ATIS or in the weather package. 3) The ACARS runways on the takeoff and landing data report are incorrect. Full length does not require a back taxi; 04/A is actually full length; and 04/K (the old A) does not exist. While it was not a performance issue for us; it could be. Additionally why has FAY Tower not issued NOTAMs reflecting these changes; Jeppesen has not changed the Airport Diagram; and there are no Chart Change notices? If these changes had been made; Aerodata would have the correct information and FCC could make the necessary changes.

Data retrieved from NASA's ASRS site as of July 2013 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.