National EAS Test — November 17, 2:20pm ET · it runs through the equipment FCC 47 CFR § 11.35(d) covers
Station Compliance

Station Compliance›Field Notes

Compliance Calendar

ETRS Form Two on November 17. What to write down during the test, and how to file it that afternoon.

Form Two is the shortest filing in ETRS and the easiest one to miss, because it is due 48 hours after a test most people stop thinking about once it is over. Here is what to have ready, what to write down while it happens, and why the same afternoon is the right time to file.

By Mark Shannon ·

The nationwide EAS test is Tuesday, November 17, at 2:20 pm Eastern (11:20 am Pacific). ETRS Form Two is due 48 hours later, by 2:20 pm Eastern on Thursday, November 19. It is short. The work is in knowing what happened on your air, and that is easiest to answer while it is still happening.

I have sat in a control room through a national test. It is over in a couple of minutes, the board goes back to normal, and the afternoon carries on. That is exactly why Form Two gets missed: by Thursday, nobody remembers who was meant to file it.

The dates

Date What
November 17, 2:20 pm ET Nationwide EAS test. Forms Two and Three open in ETRS when it starts.
November 19, 2:20 pm ET Form Two due
January 4, 2027 Form Three due

If the test is postponed to the backup date, December 3, Form Two is due December 5 at 2:20 pm ET, which is a Saturday, and Form Three by January 18, 2027 (DA 26-989).

The rule normally allows 24 hours for Form Two (§ 11.61(a)(3)(iv)(B)). The 48 hours is for this test only.

What Form Two is

Form Two is the "day of test" report. In plain terms it asks two things for your station: did the test reach you, and did you put it on the air. If the answer to either is no, it asks you to say what happened. Form Three comes later and asks for more detail.

You cannot start Form Two before the test. It opens in ETRS when the test begins.

Before the 17th

The equipment checks for before the test, firmware, clock, password and both monitoring sources, are in the pre-test checklist.

During the test: what to write down

Have a notepad, or a phone, at the EAS unit or on the board at 2:20 Eastern. Write down:

  1. The time the test arrived, from the EAS unit's display or log, and the time by a clock you trust. If they differ by more than a few seconds, note that too.
  2. Where it came from. The unit's log normally shows whether it arrived over IPAWS (the internet) or from one of your monitored stations, and which one.
  3. Whether it went to air, and at what time. If the unit forwards automatically, note the time it did. If someone pressed a button, note who and when.
  4. What it sounded like. Clean audio, both English and Spanish, or clipped, silent, garbled, cut off.
  5. Anything odd. It arrived twice, arrived late, did not arrive at all, the unit showed an error.

Take a photo of the EAS unit's log screen or print the log if your unit can. It is your record of the day, and Form Three will ask for more of the same detail in January.

If the test does not arrive at all, write that down with the time you were watching, and check the log again ten minutes later. A relay through a monitored station can arrive a little after IPAWS.

After the test: file the same afternoon

With those notes in front of you, Form Two takes a few minutes. Filing it the same afternoon means:

If the test did not reach air, say so. A station that reports a failure has told the FCC something it needs to know. A station that does not file has a second problem.

Filing questions go to ETRS@fcc.gov.

The short version

The EAS unit the test runs through is the same equipment the program-chain security rule covers. If you want all of it checked in one sitting, the kit walks through it.

Who wrote this

Mark Shannon has spent 43 years in broadcasting. He is the owner and program director of Power88.FM, and builds Cartwright — the traffic, CRM and billing software small-market stations run day to day. Like most people at a station this size, he does his own rack work: STL, codecs, automation, transmitter remote control. That is where these rules stop being paperwork and start being a Saturday afternoon. More about who writes this.

The kit is the version you can work from

Everything on this site is free to read. 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.

See the kit — $149

Get told when the FCC moves

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.

Free. No pitch. Your address is not sold or shared. One click to leave.