Read the issued CoW — not a briefing summary, not the version from lastyear’s show at the same venue. The issued document. Every conditionand limitation in that document is binding.

What are the specific items to verify?

Dates, effective times, and geographic coordinates first — make sure theevent you’re running matches what the CoW authorizes. Then identifywhich FARs are waived and, equally important, which are not. The FARsthat are not waived are still in full effect.

That’s an easy thing to overlook — focusing on what’s waived and notchecking what isn’t.

Exactly. Then check authorized act categories and their requiredseparation distances, any performer-specific restrictions orendorsements, special provisions that differ from standard practice, andERP references and required attachments. The CoW is a completedocument — treat it that way.

What about errors in the issued document?

Contact the FSDO before the show, not after. An error discovered post-incident is a different problem than one you flagged proactively. TheFSDO can issue corrections. You cannot correct it yourself by proceedingon your own interpretation.

And the show schedule is also part of the regulatory record.

The schedule submitted with the CoW application is part of that record. Ifyou deviate from the approved schedule, the IIC must be notified. Beforeeach Show Day, obtain and review the current approved schedule — notthe draft, not the working copy. The current approved version.

Version control on the schedule matters as much as the schedule contentitself.

An outdated schedule in your hand during the show is an operational risk.Know which version is current and confirm everyone is working from it.