{"id":368,"date":"2009-07-14T00:01:31","date_gmt":"2009-07-14T04:01:31","guid":{"rendered":"http:\/\/christianfighterpilot.com\/blog\/?p=368"},"modified":"2009-11-21T21:16:37","modified_gmt":"2009-11-22T05:16:37","slug":"f-22-crash-cause-revealed","status":"publish","type":"post","link":"https:\/\/christianfighterpilot.com\/blog\/2009\/07\/14\/f-22-crash-cause-revealed\/","title":{"rendered":"Cause of Edwards F-22A Crash Revealed"},"content":{"rendered":"

As previously discussed<\/a>, an F-22A Raptor crashed during a test sortie at Edwards AFB, CA, in March of this year.\u00a0 The test pilot, Lockheed civilian contractor David “Cools” Cooley, perished in the incident.<\/p>\n

While an official investigation has not been publicized to date, the Washington Post appears to have been given an answer.\u00a0 In a marginally-related article on the future of the F-22 program<\/a>, writer R. Jeffrey Smith notes that Secretary of Defense Robert Gates had been willing to purchase four more F-22s, but only four, to make the total 187.\u00a0 One was to replace the lost F-22:\u00a0 <\/p>\n

\n

One of the last four planes Gates supported buying is meant to replace an F-22 that crashed during a test flight north of Los Angeles on March 25, during his review of the program.<\/p>\n

The Air Force has declined to discuss the cause, but a classified internal accident report completed the following month states that the plane flew into the ground after poorly executing a high-speed run with its weapons-bay doors open, according to three government officials familiar with its contents. The Lockheed test pilot died.<\/p>\n<\/blockquote>\n

Thus, “three government officials” have said the cause of the F-22A crash at Edwards was a “poorly executed” test maneuver.\u00a0 Again, the Air Force has not officially announced its conclusions on the incident.<\/p>\n

In fact, the “government officials” may wish to remain anonymous because their “revelation,” if true, may actually be punishable.\u00a0 The following explains:<\/p>\n

While one cannot use\u00a0the word “never,” it is\u00a0extremely rare for\u00a0the Air Force to “classify” an accident investigation.\u00a0 It may be that it is the writer’s terminology for what the Air Force calls “privileged.”<\/p>\n

There\u00a0are two separate investigations\u00a0after a mishap: the first is “privileged,” while the second is not.<\/p>\n

In the first\u00a0investigation (normally called a “mishap investigation”), a board of officers convenes in what is called a Safety Investigation Board (SIB).\u00a0 Their objective is to determine the cause of the incident in order to prevent further occurrences–their job is not<\/u><\/em> to assign blame.\u00a0 As a result, personnel involved in the mishap are granted “privilege,” which roughly means that they can speak freely, without a lawyer, and their words will not be used against them in any form, legal or otherwise.<\/p>\n

The Air Force guards the security of privilege jealously.\u00a0 Chapter 3 of Air Force Instruction (AFI) 91-204 (which is publicly available<\/a>) describes privileged information.\u00a0 It specifically notes<\/p>\n

\n

Air Force civilian employees, military members, and government contractors will not wrongfully use, permit the use of, gain access to, or allow access to the privileged information in any safety report, or portions thereof, for other than officially authorized mishap prevention purposes.\u00a0<\/p>\n<\/blockquote>\n

\n

Violations of [these] prohibitions…are punishable under Article 92, UCMJ and may be grounds for disciplinary actions according to civilian personnel regulations, or may lead to contract actions.\u00a0<\/p>\n<\/blockquote>\n

The Air Force protects privilege because\u00a0it enables honest and forthcoming input from those involved in the mishap, which is the most likely way to prevent future incidents.<\/p>\n

In most cases, and by regulation, the investigation is to conclude within 30 days, at which point the final report is briefed to the appropriate authority.\u00a0 These reports remain privileged forever because of their utility to the mishap prevention process.\u00a0 They are not “classified”\u00a0in the true sense of the word, though to a non-military person they may appear to be treated that way.<\/p>\n

In many cases, after the SIB completes its investigation, an Accident Investigation Board (AIB) convenes.\u00a0 (An AIB always occurs when a life is lost.)\u00a0 The objective of the AIB is<\/u><\/em> to assign blame.\u00a0 Those interviewed by this board may be read their rights and advised to speak with an attorney.\u00a0 The AIB does not have access to the privileged information collected by the SIB.\u00a0 The Washington Post appears to acknowledge an ongoing AIB for the F-22 mishap when it says<\/p>\n

\n

The Air Force is still probing who should be held accountable for the accident.<\/p>\n<\/blockquote>\n

The AIB report, barring unusual circumstances, is normally releasable to the public.\u00a0 In fact, an official Air Force website<\/a> provides the ability to download the executive summaries of all Class A reports over the past few years.\u00a0 (A Class A<\/em> mishap is one in which a life is lost or a specific dollar value is surpassed.)\u00a0 It currently lists the F-22 mishap at Edwards as “pending.”<\/p>\n

Thus, while “three government officials” gave a one-line answer claiming to reveal the cause of the F-22A crash, an official, publicly-releasable report has not yet been provided by the Air Force.<\/p>\n

The unnamed officials, or those who gave them access to the “report’s contents,” may have violated Air Force policies when they did so.<\/p>\n","protected":false},"excerpt":{"rendered":"

As previously discussed, an F-22A Raptor crashed during a test sortie at Edwards AFB, CA, in March of this year.\u00a0 The test pilot, Lockheed civilian contractor David “Cools” Cooley, perished in the incident. While an official investigation has not been publicized to date, the Washington Post appears to have been given an answer.\u00a0 In a marginally-related article on the future […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[2],"class_list":["post-368","post","type-post","status-publish","format-standard","hentry","category-fighter-pilot","tag-military"],"_links":{"self":[{"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/posts\/368","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/comments?post=368"}],"version-history":[{"count":0,"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/posts\/368\/revisions"}],"wp:attachment":[{"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/media?parent=368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/categories?post=368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/christianfighterpilot.com\/blog\/wp-json\/wp\/v2\/tags?post=368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}