Ok, so lets use an existing cache to see what can be done. How about
Little Falls Cache (GCWMFE) by
Sudonim (2/2)? I'd be more fearfull of being shot there than visiting the Fitz Cache. Should we all email Andy and tell him it should be archived? Post numerous notes to the cache page? Contact gc.com and alert them? Go steal the cache?
Many caches have their dangers. Some from natural surroundings, some from animals, some from people. Sometimes they are more dangerous to certian groups, like age, sex, and race. It is nice when the description alerts cachers to those dangers.
Assuming the cache is placed within gc.com guidelines, if a cache appears to have dangers not posted on the cache page, it seems a polite email to the owner would be the first step. I don't see where it does any good to send multiple emails. They got the message in the first email, if they think the issue needs to be addressed they will do so.
If that does not work and you still feel strongly that people should be warned, then it makes sense to email a gc.com volunteer. If they argree and take action, by a cache log, note to the owner, or other means, IMO that is about all that can and should be done as far as the cache is concerned.
Other than that, adressing the real issue seems to be the best route to go. What good is getting the cache archived do? It prevents a few cachers monthly from visiting the area. It doesn't stop the danger there, and it doesn't stop non-cachers from unknowiningly accessing the area, either.
I don't expect the DOT to jump on any of these issues. I imagine the get contacted daily about these and other issues. But they should be informed. And, the more they are informed the more likely they may do somethign about it. In the case of the Fitz cache, these people hang out there because no one else does. If you can turn that around, that would be the best action.