There is one way to reach this desk, and it is email: contact@aonia-pass-mx.com. There is no contact form on this site, no comment thread and no newsletter, because none of the three would be answered better than a plain message.
What is worth writing about
- A factual error. A misquoted rule, a misread standard, a number that does not come out the way the note says it does. Include the page and, if you can, the passage.
- A source that has moved or been revised. Rulebooks and federal standards get reissued, and a link that pointed at the right document last season can point at an older revision this one.
- A question a note should have answered and did not. That is the most useful message the desk receives, because it usually shows a gap rather than a mistake.
- A subject inside the scope of the site. Private practice tracks, their surface, their shapes, their upkeep and the weekend around them.
What the desk cannot help with
Some requests arrive regularly and the honest answer to all of them is no. The desk does not assess a specific property, does not design or sign off on a track layout, does not recommend a machine or a brand, does not value equipment and does not give medical, legal or engineering advice. It also does not put anyone in touch with a track, because no track is named on this site.
The design criteria quoted in the maintenance notes come from published conservation standards. Quoting them is not engineering, and a note that mentions a storm frequency or a side slope ratio is not a substitute for someone who is qualified to look at your actual ground.
How a correction is handled
A correction is checked against the source before anything changes. If the note is wrong, the text is corrected in place and the date in its source paragraph is updated to the day the document was rechecked. If the note is right, you get a reply saying which passage of which document it rests on, so you can judge for yourself rather than take the desk's word for it.
Reply times, honestly
This is a small desk and messages are read in batches rather than continuously. A factual correction gets looked at first because a wrong page keeps being wrong while it waits. A question that needs a document opened and read takes longer, and a request that falls outside the scope above gets a short reply saying so rather than a long one pretending otherwise.
If your message is about how the site itself works, who writes it and how sources are handled, the answer is probably already on the about page. If it is about what the site records and stores, that is on the privacy and terms page.