Air carrier Dispatch reported confusion with the MDE airport NOTAMs that were issued for a pothole located near the threshold of Runway 1.

Date: 2025-06 · Aircraft: Commercial Fixed Wing

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-published-material-policy|ground-event-encounter-other-unknown

Synopsis

Air carrier Dispatch reported confusion with the MDE airport NOTAMs that were issued for a pothole located near the threshold of Runway 1.

Narrative

Several issues noted with how MDE Airport Authority handled the NOTAMs with a pothole located near the threshold of Runway 1. NOTAM was issued stating caution should be used due to pothole. A separate NOTAM was issued; shortening the length of Runway 19 for takeoff; and marking the use of Runway 1 for takeoff as NA. The NOTAM was later changed from NA to reflect NU which is non-standard nomenclature and not clearly defined in the list of contractions.It was confirmed that the pothole and runway length NOTAMs were associated. The Chief Dispatcher (Domestic) was informed that airlines were taking off all day on Runway 1 despite the NOTAM stating that Runway 1 was not authorized.The Airport Authority decided to extend the pothole NOTAM (at about XA:04) through XA:00 on Day 1; but did not extend the runway shortened NOTAM. This prompted an email to the Station Manager to obtain clarity on what has changed.According to the Station Manager; the airport did not feel it was necessary to extend the partial runway closure as they had hoped that the runway would have been repaired by the original expiration (NOTAM expiration was XB:20 on Day 0). Station Manager also relayed that the runway was not repaired and it is expected that we should comply with Runway 19 departure with shortened runway.Based on this information; I asked the Chief Dispatcher to obtain shortened runway data for Runway 19 (was still not present in the flight plan despite it being added previously; suspect that there is an expiration time for the shortened runway data on the application side?). I was still waiting on this data to dispatch the flight when it was time to turn over to the next shift. I briefed the next Dispatcher and forwarded the email chain to him for his reference. I followed up with the Chief Dispatcher; he said that he would include it in their turnover for midnight shift to follow up with the application to ensure data is loaded.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.