1994 Fairchild Air Force Base B-52 crash

1994 Fairchild Air Force Base
B-52 crash
	The B-52, a fraction of a second before it crashed. Co-pilot McGeehan's escape hatch, jettisoned during his attempt to eject, is visible near the tip of the vertical stabilizer.
Accident
Date	24 June 1994
Summary	Pilot error led to stall
Site	Fairchild Air Force Base, Washington, U.S. ; 47°36′38″N 117°39′02″W / 47.6105°N 117.6505°W
Aircraft
Aircraft type	B-52H Stratofortress
Aircraft name	Czar 52
Operator	United States Air Force
Registration	61-0026
Passengers	0
Crew	4
Fatalities	4
Survivors	0
Ground casualties
Ground injuries	1

Fairchild
AFB

class=notpageimage|

Location of Fairchild in the United States

Fairchild AFB

class=notpageimage|

Location in Washington

Basic structure of USAF wings, groups, and squadrons in relation to the chain of command

On Friday, 24 June 1994, a United States Air Force (USAF) Boeing B-52 Stratofortress crashed at Fairchild Air Force Base, Washington, United States,^[1] after its pilot, Lieutenant Colonel Arthur "Bud" Holland, maneuvered the bomber beyond its operational limits and lost control. The B-52 stalled, fell to the ground and exploded, killing Holland and the three other field-grade officers on board the aircraft. In addition, one person on the ground suffered injuries during the accident, but survived. The crash was captured on video and was shown repeatedly on news broadcasts throughout the world.^[2]^[3]

The subsequent investigation concluded that the crash was attributable primarily to three factors: Holland's personality and behavior; USAF leaders' delayed or inadequate reactions to earlier incidents involving Holland; and the sequence of events during the aircraft's final flight. The crash is now used in military and civilian aviation environments as a case study in teaching crew resource management. It is also often used by the U.S. Armed Forces during aviation safety training as an example of the importance of complying with safety regulations and correcting the behavior of anyone who violates safety procedures.

Accident

Background

At 07:30 local time (PDT) on 24 June 1994, a USAF B-52H bomber crew stationed at Fairchild Air Force Base prepared to practice an aircraft demonstration flight for an air show which was due to take place the following day. The crew consisted of pilots Lt. Col. Arthur "Bud" Holland (aged 46) and Lt. Col. Mark McGeehan (38), Colonel Robert Wolff (46), and weapon systems officer/radar navigator Lt. Col. Ken Huston (41). Holland was the designated aircraft commander for the flight, with McGeehan as the co-pilot and Wolff as a safety observer. Holland was the chief of the 92nd Bomb Wing's Standardization and Evaluation branch, McGeehan was the commander of the 325th Bomb Squadron, Wolff was the vice commander of the 92nd Bomb Wing, and Huston was the 325th Bomb Squadron's operations officer.^[4]

The mission plan for the flight called for a series of low-altitude passes, 60° banked turns, a steep climb, and a touch-and-go landing on Fairchild's Runway 23. The flight was also Wolff's "fini flight" – a common tradition in which a retiring USAF aircrew member is met at the airfield by relatives, friends, and coworkers, shortly after landing on his or her final flight, and doused with water. Accordingly, Wolff's wife and many of his close friends were at the airfield to watch the flight and participate in the post-flight ceremony. McGeehan's wife and his two youngest sons were watching the flight from the backyard of McGeehan's living quarters, which were located nearby.^[5]

Takeoff

The B-52 aircraft, callsign Czar 52,^[6] took off at 13:58 and completed most of the mission's elements without incident. Upon preparing to execute the touch-and-go on Runway 23 at the end of the practice profile, the aircraft was instructed to go around because a KC-135 aircraft was on the runway, having just landed. Maintaining an altitude of about 250 feet (75 m) above ground level (AGL), Holland radioed the control tower and requested permission to execute a 360° left turn, which was immediately granted by the tower controller.

Crash

The B-52 then began the 360° left turn around the tower starting from about the midfield point of the runway. Located just behind the tower was an area of restricted airspace, reportedly because of a nuclear weapons storage facility.^[7] Apparently to avoid flying through the restricted airspace, Holland flew the aircraft in an extremely tight, steeply banked turn while maintaining the low, 250-foot (75 m) AGL altitude. Approximately three-quarters of the way around the turn, at 14:16, the aircraft banked past 90°, descended rapidly, clipped power lines and hit the ground, exploding and killing the four crew members. McGeehan was sitting in an ejection seat, but according to the medical statement, he had only "partially ejected at the time of impact"; it does not state whether he had managed to clear the aircraft. Huston was also sitting in an ejection seat; the medical statement indicated that he had not initiated the ejection sequence. Wolff's seat was not ejection-capable. One airman was injured on the ground observing.^[8]

Investigation

The USAF immediately convened a safety investigation board under the direction of the USAF's Chief of Safety, Brigadier General Orin L. Godsey. The board released the report of its investigation into the crash on 10 August 1994. A final evaluation of the safety investigation was released on 31 January 1995. An accident investigation board, called an "AFR 110-14 Investigation," released a separate report in 1995. Unlike the USAF safety investigation, which was released only to personnel of the U.S. Department of Defense, the AFR 110-14 report was released to the general public.^[9]

The AFR 110-14 investigation identified several factors which contributed to the crash, including the actual crash sequence, the personality and earlier behavior of Holland, previous supervision and lack of corrective action exercised by USAF officers over Holland, mission planning and execution, and other environmental and human factors.^[8]

Crash sequence

The investigation found that as the B-52 entered its final turn sequence around the tower, its airspeed indicator (ASI) was showing 182 knots (337 km/h; 209 mph). Although Holland increased the engine power after starting the turn, his input came too late to maintain the aircraft's airspeed, as the B-52 turbofan engines take up to eight seconds to respond to throttle commands. The ASI was available to all four aircrew members, but they allowed the aircraft's airspeed to continue decreasing. Eight seconds before impact, the airspeed had dropped to 145 knots (269 km/h; 167 mph) and the aircraft's bank angle had increased beyond 60°. This was the point at which Holland or McGeehan applied full right spoiler, right rudder, and nose-up elevator; however, due to the reduction in airspeed the aircraft entered a turning flight stall (also called an "accelerated stall"), which is a stall that occurs at a higher airspeed than the design stall speed—which itself always refers to straight and level flight—because of the fact that the aircraft is turning. Due to the bank angle of at least 60°, the stall speed for the aircraft at that moment was 147 knots (272 km/h; 169 mph). Hence, as it was flying 2 knots below the stall speed, the aircraft stalled, with insufficient altitude to recover before striking the ground.^[8]

Holland's previous behavior and USAF leaders' reactions

The accident board stated that Holland's macho, daredevil personality significantly influenced the crash sequence. USAF personnel testified that Holland had developed a reputation as an aggressive pilot who often broke flight-safety and other rules. The rule-breaking included flying below minimum-clearance altitudes and exceeding bank-angle limitations and climb rates.^[10]

An earlier incident occurred in 1991 when a B-52 piloted by Holland performed a circle above a softball game in which Holland's daughter was participating. Beginning at 2,500 feet (760 m) AGL, Holland's aircraft executed the circle at 65° of bank. In a maneuver described by one witness as a "death spiral", the nose of the aircraft continued to drop and the bank angle increased to 80°. After losing 1,000 feet (300 m) of altitude, Holland was able to regain control of the aircraft.^[11]

On 19 May 1991, Holland was the command pilot of the B-52 demonstration flight at the Fairchild air show. During the demonstration, Holland's aircraft violated several safety regulations; he exceeded bank and pitch limits, flew directly over the air show spectators, and possibly violated altitude restrictions. The base and wing commander, Colonel Arne Weinman, along with his staff, observed the demonstration but apparently took no action.^[6]

On 12 July 1991, Holland commanded a B-52 for a "flyover" during a change-of-command ceremony for the 325th Bomb Squadron at Fairchild. During both the practice and the actual flyover, Holland's aircraft flew at altitudes below 100 feet (30 m)—well below the established minimum altitude—flew steeply banked turns in excess of 45°, exceeded pitch-angle limits, and executed a wingover. Although not specifically prohibited, the wingover was not recommended because it could damage the aircraft. After witnessing the flyover, Colonel Weinman and his deputy commander for operations (DO), Colonel Julich, orally reprimanded Holland, but took no formal action.^[10]

At the Fairchild air show on 17 May 1992, Holland was again the command pilot of the B-52 aerial-demonstration flight. During the demonstration, Holland's aircraft again violated various safety regulations, including several low-altitude steep turns in excess of 45° of bank and a high-pitch-angle climb, estimated at over 60° nose high which Holland finished with a wingover maneuver. The new wing commander, Colonel Michael G. Ruotsala, apparently took no action. One week later, the new DO, Colonel Capotosti, on his own initiative warned Holland that if he violated any more safety regulations, Capotosti would ground him (remove him from flying status). Capotosti did not document his warning to Holland or take any other kind of formal action.^[6]

A B-52H takes off with a standard pitch attitude.

On 14 and 15 April 1993, Holland was the mission commander of a two-aircraft training mission to a bombing range near Guam in the Pacific Ocean. During the mission, Holland flew his B-52 closer to the other B-52 than regulations allowed. Holland also asked his navigator to videotape the bombs falling from the aircraft from inside the bomb bay, also against regulations. Holland's navigator later brought the video to the attention of three Fairchild USAF officers. The first, Lieutenant Colonel Bullock, the current 325th Bomb Squadron commander, did nothing about it and may have even tried to use the videotape as leverage to coerce the navigator into accepting a position as mission scheduler for the wing. The second, the deputy operations group commander, Lieutenant Colonel Harper, told the crew member to conceal the evidence. The third, the DO, allegedly responded to reports of the video by stating, "Okay, I don't want to know anything about that video—I don't care."^[12]

At the Fairchild air show on 8 August 1993, Holland once again commanded the B-52 demonstration flight. As before, the demonstration profile included bank angles of greater than 45°, low-altitude passes, and another high pitch climbing maneuver, this time in excess of 80° nose high. The climb was so steep that fuel flowed out through the vent holes from the aircraft's wing tanks. The new wing commander, Brigadier General James M. Richards, and the new DO, Colonel William E. Pellerin, both witnessed the demonstration, but neither took any action.^[13]

On 10 March 1994, Holland commanded a single-aircraft training mission to the Yakima Bombing Range, to provide an authorized photographer an opportunity to document the aircraft as it dropped training munitions. The minimum aircraft altitude permitted for that area was 500 feet (150 m) AGL; during the mission, Holland's aircraft was filmed crossing one ridgeline about 30 feet (10 m) above the ground. Fearing for their safety, the photography crew ceased filming and took cover as Holland's aircraft again passed low over the ground, this time estimated as clearing the ridgeline by only three feet (1 m). The co-pilot on Holland's aircraft testified that he grabbed the controls to prevent Holland from flying the aircraft into the ridge while the aircraft's other two aircrew members repeatedly screamed at Holland: "Climb! Climb!" Holland responded by laughing and calling one of the crew members "a pussy".^[2]

After that mission, the crew decided that they would never again fly with Holland and reported the incident to the bomb squadron leadership. The USAF squadron commander, Lieutenant Colonel Mark McGeehan, reported the incident to Pellerin and recommended that Holland be removed from flying duty. Pellerin consulted with Holland and gave him an oral reprimand and warning not to repeat the behavior, but refused to take him off flying duty. Pellerin also did not document the incident or the reprimand, nor did he notify his superiors, who remained unaware of the incident. McGeehan then decided that in order to protect his aircrews, he (McGeehan) would be the co-pilot on any future missions in which Holland was the command pilot. Evidence suggests that after this incident, "considerable animosity" existed between Holland and McGeehan.^[14]^[15]

Lt. Col. McGeehan refused to allow any of his squadron members to fly with Holland unless he (McGeehan) was also on board the aircraft

In preparation for the 1994 Fairchild air show, Holland was again selected as the command pilot for the B-52 demonstration flight. On 15 June 1994, Holland briefed the new wing commander, Colonel William Brooks, on the proposed flight plan. Holland's demonstration profile violated numerous regulations, including steep bank angles, low-altitude passes, and steep pitch attitudes. Brooks ordered Holland not to exceed 45° bank angle or 25° pitch attitude during the demonstration. During the first practice session, on 17 June, Holland repeatedly violated these orders. Brooks witnessed this, but took no action. Pellerin flew with Holland on that flight and reported to Brooks that, "the profile looks good to him; looks very safe, well within parameters." The next practice flight on 24 June ended with the fatal crash.^[10]

Other factors

The demonstration profile designed by Holland included a 360° turn around Fairchild's control tower, a maneuver which he had not attempted in previous air show demonstrations. During the final flight, Holland performed a series of 60° bank turns and a 68° pitch climb in violation of Brooks' orders. There is no evidence to suggest that either McGeehan or Wolff attempted to intervene as Holland carried out these dangerous maneuvers.^[8]

Pellerin was originally scheduled to fly in this mission, as he had done on the 17 June flight, but he was unavailable for the 24 June flight and Wolff was selected as the replacement aircrew member. Due to the short notice of his assignment to the mission, Wolff did not participate in the pre-flight briefing and boarded the aircraft after the engines were started. He was therefore unaware of the planned mission profile and had no opportunity to raise any objections before take-off.^[8]

All of the four aircrew involved in the crash had only limited flying time in the months before the crash. It would appear that none of them had noticed that the aircraft had stalled until shortly before impact, as indicated by a failure to apply standard recovery techniques to the aircraft once it entered the stall. The investigation reported that even if the proper stall recovery techniques had been applied, it was unlikely that the accident could have been prevented as the aircraft was already flying too low to be recovered.^[8]

Four days before the accident, on 20 June, Dean Mellberg, an emotionally disturbed ex-USAF serviceman, had entered Fairchild's hospital, fatally shooting four people and wounding many more before being killed by a security policeman.^[16] The crime was a major distraction for personnel stationed at Fairchild for some time afterwards.^[8]

Conclusions

The accident investigation concluded that the crash was primarily attributable to Holland's personality and behavior, USAF leaders' inadequate reactions to the previous incidents involving Holland, and the sequence of events and aircrew response during the final flight of the aircraft. Holland's disregard for procedures governing the safe operation of the B-52 aircraft that he commanded and the absence of firm and consistent corrective action by his superior officers allowed Holland to believe that he could conduct his flight in an unsafe manner, culminating with the slow, steeply banked, 360° turn around the control tower.^[2]

The other environmental factors involved, including the addition of a new maneuver (the 360° turn around the tower), inadequate pre-flight involvement of Wolff, and the distractions from the base shooting four days prior, combined with Holland's unsafe and risk-taking piloting behavior to produce conditions favorable for the crash to occur. The final factor, according to the USAF investigation report, was the 10-knot (19 km/h) wind and its effect on the maneuvers required to achieve the intended flightpath in relation to the ground.^[2]

Aftermath

On 19 May 1995, Pellerin pleaded guilty at a USAF court-martial proceeding to two counts of dereliction of duty for his actions, or lack thereof, that contributed to the crash. He was sentenced to forfeit $1,500 of salary a month for five months and received a written reprimand. The USAF did not reveal whether any other officer involved in the chain of events leading to the crash received any type of administrative or disciplinary action. Critics of USAF's safety record stated that this crash was an example of a pattern of problems related to enforcement of safety procedures within USAF.^[17]

Although the accident investigation found that procedures and policies were supposedly already in place to prevent such a crash from occurring again, the fact that this crash occurred showed that in at least one instance, the existing safety policies and their enforcement had been grievously inadequate. To re-emphasize the importance of adherence to existing safety policies and correcting the actions of anyone violating them at any time, the USAF quickly distributed the findings of the accident investigation throughout the service. These measures failed to prevent—sixteen years later—the occurrence in almost identical circumstances of another accident, when a C-17 transport aircraft crashed shortly after taking off from Elmendorf Air Force Base, Alaska, on an aerial-display practice flight.^[18]

Today, the Fairchild crash is used in both military- and civilian-aviation environments, as a training aid in teaching crew resource management and to show the importance of enforcing safety regulations.^[6]^[19]

Several years after his death, Lt. Col. McGeehan was recognized with an award by the Lou Holtz/Upper Ohio Valley Hall of Fame in East Liverpool, Ohio, for his lifetime of service. The citation included the following:

Ironically, just weeks before his death as Lt. Col. McGeehan was preparing to hand over the unit flag of the 325th Bomb Squadron for deactivation on 1 July, he wrote in an article that was printed 10 June 1994, in the military publication Strikehawk:
"When we think of those who went before us, we should do so with humility, respecting their great personal sacrifice. When we honor our heritage and those with whom we share a common bond and purpose, we are all enriched, and our lives are made a little more worth living."^[20]

Footage of the Fairchild crash was used in the making of the 2015 film Project Almanac, depicting an airline accident, which sparked public anger among relatives of Wolff and McGeehan. After an initial claim by Paramount Pictures that the video in question was of a 2009 Tokyo crash, producer Michael Bay issued an apology to the families and the footage was removed from the film's theatrical release and associated trailers at Bay's request.^[21]

References

^ Jewell, Mark (25 June 1995). "Another tragedy at Fairchild". Moscow-Pullman Daily News. (Idaho-Washington). Associated Press. p. 1.
^ ^a ^b ^c ^d Diehl, Silent Knights, p. 125, Thompson, Way, Way Off in the Wild Blue Yonder, USAF, AFR 110-14, pp. 2–3, and Kern, Darker Shades of Blue.
^ Walter, Jess (25 June 1994). "Shocking footage transfixes viewers again and again". Spokesman-Review. (Spokane, Washington). p. A6.
^ Thompson, Way, Way Off in the Wild Blue Yonder, Kern, Darker Shades of Blue, and USAF, AFR 110-14, pp. 2–3. Holland, as chief of standardization and evaluation, was responsible for the knowledge and enforcement of academic and in-flight standards for the bomb wing's flying operations.
^ Piper, Chain of Events, p. 136, Kern, Darker Shades of Blue, and USAF, AFR 110-14, pp. 2–3.
^ ^a ^b ^c ^d Kern, Darker Shades of Blue.
^ Diehl, Silent Knights, p. 125.
^ ^a ^b ^c ^d ^e ^f ^g USAF, AFR 110-14, all.
^ Air Force Link, Brigadier General Orin L. Godsey, and USAF, AFR 110-14, pp. 2–3.
^ ^a ^b ^c USAF, AFR 110-14, pp. 3–4, and Kern, Darker Shades of Blue.
^ Diehl, Silent Knights, p. 125, Thompson, Way, Way Off in the Wild Blue Yonder, and USAF, AFR 110-14, pp. 3–4. Holland also regularly and illegally parked his car in a "no parking" zone near the base headquarters building.
^ Diehl, Silent Knights, p. 125, Kern, Darker Shades of Blue. The article does not state whether this DO was Colonel Capotosti or a new DO, Colonel William E. Pellerin.
^ Air Force Link, Brigadier General James M. Richards USAF biography, Thompson, Way, Way Off in the Wild Blue Yonder, and Kern, Darker Shades of Blue.
^ Thompson, Way, Way Off in the Wild Blue Yonder, Kern, Darker Shades of Blue, and USAF, AFR 110-14, pp. 3–4.
^ Lou Holtz/Upper Ohio Valley Hall of Fame, Lt. Col. Mark C. McGeehan.
^ Camden, Jim (21 June 1994). "Under fire". Spokesman-Feview. (Spokane, Washington). p. A1.
^ Diehl, Silent Knights, p. 126, Thompson, Way, Way Off in the Wild Blue Yonder, Kern, Darker Shades of Blue.
^ Stephen Trimble (17 December 2010). "C-17 crash report exposes cracks in USAF safety culture". Flightglobal. Reed Business Information. Retrieved 5 March 2011.
^ Check-Six.com, The Crash of Czar 52.
^ "Hall of Fame Inductees". 12 March 2007. Archived from the original on 12 March 2007.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
^ "Michael Bay apologizes, will cut B-52 crash from film". Air Force Times. Retrieved 12 November 2015.