<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Don’t Tarnish the Blues</title> <atom:link href="http://defensetech.org/2007/09/07/dont-tarnish-the-blues/feed/" rel="self" type="application/rss+xml" /><link>http://defensetech.org/2007/09/07/dont-tarnish-the-blues/</link> <description>The Future of the Military, Law Enforcement and National Security</description> <lastBuildDate>Mon, 22 Mar 2010 12:55:55 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Christian Lowe</title><link>http://defensetech.org/2007/09/07/dont-tarnish-the-blues/comment-page-1/#comment-166617</link> <dc:creator>Christian Lowe</dc:creator> <pubDate>Fri, 07 Sep 2007 18:29:02 +0000</pubDate> <guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3721#comment-166617</guid> <description>ohwilleke,
I&#039;ve actually done a fair amount of stories on JAGMAN reports in my day. Basically what they tend to redact is names, SSNs and medical information from the reports. But since it&#039;s up to the staff judge advocate of the command, there&#039;s a lot of leeway in the redaction as well. For example, I&#039;ve had some JAGMANs come to me with the &quot;recommendation&quot; section intact. Others, it was cut out. Sometimes I&#039;ve had ones with the names of the crew in the report, others without - but it&#039;s not so hard to figure out who is who in that situation. It&#039;s not so much an issue of endangering the named, insofar as the rules governing FOIA law protect privacy. SJAs are given some leeway to determine how far to go on that...but since the commander often has to sign off on the final report - and sometimes the redacted version - I&#039;m sure PR comes into play as well.
In this case, if the cause of the crash is pilot error, think what that would do - in some people&#039;s eyes - to the reputation of the Blue Angels. They&#039;re not supposed to make mistakes like this and I doubt the command wants that kind of PR problem on their hands. Of course, as a reporter, I believe there&#039;s a public good to knowing exactly what happened so we can try and avoid its happening again. </description> <content:encoded><![CDATA[<p>ohwilleke,<br
/> I’ve actually done a fair amount of stories on JAGMAN reports in my day. Basically what they tend to redact is names, SSNs and medical information from the reports. But since it’s up to the staff judge advocate of the command, there’s a lot of leeway in the redaction as well. For example, I’ve had some JAGMANs come to me with the “recommendation” section intact. Others, it was cut out. Sometimes I’ve had ones with the names of the crew in the report, others without — but it’s not so hard to figure out who is who in that situation. It’s not so much an issue of endangering the named, insofar as the rules governing FOIA law protect privacy. SJAs are given some leeway to determine how far to go on that…but since the commander often has to sign off on the final report — and sometimes the redacted version — I’m sure PR comes into play as well.<br
/> In this case, if the cause of the crash is pilot error, think what that would do — in some people’s eyes — to the reputation of the Blue Angels. They’re not supposed to make mistakes like this and I doubt the command wants that kind of PR problem on their hands. Of course, as a reporter, I believe there’s a public good to knowing exactly what happened so we can try and avoid its happening again.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc (user agent is rejected)
Database Caching 9/16 queries in 0.008 seconds using apc

Served from: unknown.dal.cologlobal.com @ 2010-03-22 13:04:03 -->