If you've worked a shift or flown a route and run into a Remote Communications Outlet (RCO) that wasn't working — or wasn't there when you expected it to be — we want to hear about it.
We've put together a short form to start collecting these reports in one place. It takes a couple of minutes to fill out, and every submission goes straight into a shared log we're using to track incidents as these closures mentioned in the previous posts take effect.
What we're asking for:
- Operating Initials/Pilot in Command
- Aircraft ID (ACID)
- Date/UTC Time
- Narrative — tell us which RCO you used, which RCO was missing (if you know), how it affected your ability to communicate, how it affected the safety of the NAS, and anything else worth noting
Why this matters
When we start logging these incidents consistently, we can show that RCO closures are already causing potential problems under real operational conditions. That's the kind of documented, first-hand evidence that makes a difference when we're making the case for continued investment in the infrastructure of the National Airspace System.
This isn't about pointing fingers. It's about building a record — in your own words, from the people actually working the radios and flying the routes — of what's really happening out there.
Submit a Report (this will open another tab) →Report Form
If you have questions about the form or want to report something that doesn't fit neatly into these fields, reach out directly and we'll figure it out.
Thanks for taking the time to document this. It matters more than it might feel like in the moment.
No comments:
Post a Comment