Date: 202108
Local time of day: 0601-1200
Location: FDK.Tower, MD
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
ATC / advisory: Tower FDK
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Confusion; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Recently FDK completed its Runway 5/23 extension from 5;219 ft to 5;819 feet. The next chart cycle date reflected the runway/taxiway markings.  As of cycle 2108; all of the FDK airport diagram and approach charts now show the runway 5/23 at 5;219 ft again. The reasoning from the airport manager was the FAA approach plate 'people' said that since they have not done an approach assessment (to be performed in March of 2022); that they would not allow the runway to be shown as extended; and the group unilaterally changed all airport/approach charts to show the runway shortened; but with a 600 feet relocated threshold and a taxiway leading up to the new unmarked runway threshold in cycle 2108.  Cycle 2107; the previous cycle; properly showed the runway's extension.  Also to note; the RNAV approach that services Runway 5 has been NOTAMed NA since the completion of the runway extension. Fun to note; that the RNAV approach was allowed when the runway was shortened by about 500 feet to 4;700 feet during runway extension construction without a NOTAM showing un-coincidental glideslope/PAPI relationship. This is no longer an issue; although it was brought up by local based charter pilots as being unsafe and improper.The following instances may occur.  An aircraft landing Runway 23 at night; may rightfully assume they have 600 feet past the Runway 5 threshold markings to exit at Taxiway A1; when in fact; there is no pavement past the Runway 5 threshold.  This can cause a runway excursion by confusion of the actual markings and the chart diagram. Aircraft may proceed onto Runway 5 from Taxiway A1 to pull up to the 600 foot relocated threshold; causing a runway incursion.  May cause pilot confusion or disorientation when a pilot lands or departs runway 5/23. Changing a diagram that does not depict the actual markings without a proper NOTAM or notification by the Tower is extremely reckless behavior and should not be tolerated as standard practice.Requested Fix: NOTAM the runway length to 5;819 feet; NOTAM to disregard the relocated threshold and revert the airport diagram and all approach charts to the Cycle 2107 depiction of the airport diagram/layout. Do not allow the FAA Approach Office to unilaterally change the airport diagram's of airports without concurrence of all related parties; and if the FAA Approach office does not have the concurrence; the office should perform a good faith effort to mitigate all safety issues.




Synopsis: FDK Tower Controller reported the runway extension which was previously charted was removed from the latest charts and will not be published until March of 2022.  The reporter states this will potentially cause runway excursions; incursions and confusion for pilots.