FCC Watch · Week of September 28, 2026
The § 11.35(d) compliance date passed with no extension or waiver, reply comments on software EAS closed, and the next date is ETRS Form One on October 30.
By Mark Shannon ·
The program chain security rule is in force. September 29 passed with no extension, no blanket waiver, and no FCC action on the one petition asking for more time. Compliance with § 11.35(d) is now simply required.
If your station is not there yet, there was nothing to file, so there is no list of who missed it. What changed is that an inspection, a complaint or an incident can now reach the gap. What to do first.
Reply comments in the software-EAS proceeding closed on September 29, the same day. The filings visible so far include iHeartMedia, NCTA, APCO and the Colorado Council of 911 Authorities. There is no FCC timetable for a decision. What the proposal covers.
| Date | What |
|---|---|
| October 10 | Quarterly issues/programs list for July–September, in the public file |
| October 20 | EEO audit responses, for the 400 stations selected |
| October 30 | ETRS Form One, every EAS Participant |
| November 17 | National EAS Test, 2:20 pm Eastern |
The test is the next moment anyone outside your building sees your EAS chain working, or not. If the security work is still on the list, the week before November 17 is too late to start it.
More weeks
The rules on this site change without warning — a deadline gets waived, a filing window opens, a Public Notice lands on a Friday. Leave an address and you get an email when something changes that affects a small station. Nothing else, and one click to leave.
The Program Chain Compliance Kit is the implementation version — the device-by-device reference, the network patterns for a one-rack station, and the worksheets that leave a paper trail behind the work.