Jump to content

1994 Fairchild Air Force Base B-52 crash

Coordinates: 47°36′38″N 117°39′02″W / 47.6105°N 117.6505°W / 47.6105; -117.6505
From Wikipedia, the free encyclopedia
(Redirected from Bud Holland)

1994 Fairchild Air Force Base
B-52 crash
61-0026, callsign Czar 52, a fraction of a second before crashing. The copilot McGeehan's escape hatch, jettisoned during his attempt to eject, can be seen near the tip of the vertical stabilizer.
Accident
Date24 June 1994
SummaryPilot error,[1] stall
SiteFairchild Air Force Base, Washington, U.S.
47°36′38″N 117°39′02″W / 47.6105°N 117.6505°W / 47.6105; -117.6505
Aircraft
Aircraft typeB-52H Stratofortress
Aircraft nameCzar 52
OperatorUnited States Air Force
Registration61-0026
Occupants4
Crew4
Fatalities4
Survivors0

On Friday, 24 June 1994, a United States Air Force (USAF) Boeing B-52 Stratofortress crashed at Fairchild Air Force Base, Washington, United States,[2] after its pilot, Lieutenant Colonel Arthur "Bud" Holland, maneuvered the bomber beyond its operational limits and lost control. The aircraft stalled, fell to the ground and exploded, killing Holland and the other three crew aboard. The crash was captured on video and was shown repeatedly on news broadcasts throughout the world.

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 compliance with safety regulations and correcting the behavior of anyone who violates safety procedures.

Crash

[edit]

At 07:30 local time (PDT) on 24 June 1994, a United States Air Force (USAF) B-52H bomber crew stationed at Fairchild Air Force Base prepared to practice an aircraft demonstration flight for an airshow. The crew consisted of pilots Lieutenant Colonel Arthur "Bud" Holland (age 46), 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. McGeehan was the copilot and Wolff was present 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. 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.[3][4]

A B-52H similar to the one involved in the accident

The mission plan for the flight called for a demanding 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 "finis flight" – a common tradition in which a retiring USAF aircrew member is met shortly after landing on his or her final flight at the airfield by relatives, friends and coworkers, and doused with water. Thus, 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 two youngest sons watched the flight from the backyard of McGeehan's living quarters, located nearby.[5]

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 had just landed and was on the runway. Maintaining an altitude of about 250 feet (75 m) above ground level (AGL), Holland radioed the control tower and asked for permission to execute a 360° left turn, which was immediately granted by the tower controller.

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 and exploded, killing the four crew members. McGeehan was seated 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 or not he cleared the aircraft. Huston was also seated in an ejection seat and the medical statement indicated that he had not initiated the ejection sequence. Wolff's seat was not ejection-capable. No one on the ground was injured.[8]

Investigation

[edit]

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 U.S. Department of Defense personnel, the AFR 110-14 report was released to the general public.[9][failed verification]

The AFR 110-14 investigation identified several factors which contributed to the crash, including the actual crash sequence, the personality and earlier behavior of Bud 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

[edit]
Turning flight stall illustrated: the tighter the turn, the greater the lift (and thus angle of attack, AoA) required to counter the sum of centrifugal force and weight. If the critical AoA is exceeded, the aircraft will stall, regardless of the airspeed remaining constant.

The investigation found that as the B-52 entered its final turn sequence around the tower, its indicated airspeed (IAS) was 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. Even though the airspeed indicator was available to all four aircrew members, the aircraft's airspeed was allowed to continue to decrease. Eight seconds before impact, the aircraft's IAS had deteriorated to 145 knots (269 km/h; 167 mph) and the aircraft's bank angle increased past 60°. At this time Holland or McGeehan applied full right spoiler, right rudder, and nose-up elevator, and the aircraft entered a turning flight stall (also called accelerated stall). This phenomenon is a stall that occurs at a higher airspeed than the design stall speed – which always refers to straight and level flight – because the aircraft is turning. Due to the bank of 60° or more, the stall speed for the aircraft at that moment was 147 knots (272 km/h; 169 mph). Thus, flying 2 knots slower, the aircraft stalled, without having sufficient altitude to recover before striking the ground.[8]

Holland's previous behavior and USAF leaders' reactions

[edit]

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 regained control of the aircraft. Holland also regularly and illegally parked his car in a "no parking" zone near the base headquarters building.[3][11]

During a 19 May 1991 air show at Fairchild, Holland was the command pilot of the B-52 aerial-demonstration flight. During the demonstration, Holland's aircraft violated several safety regulations, including exceeding bank and pitch limits, flying directly over the air-show spectators, and possibly violating altitude restrictions. The wing staff observed the demonstration, but apparently took no action.[12]

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. The wingover was not specifically prohibited but was not recommended, because it could damage the aircraft. After witnessing the flyover, the wing commander Colonel Arne Weinman and his deputy commander for operations (DO), Colonel Arnold Julich, verbally reprimanded Holland, but took no formal action.[13]

During the 17 May 1992 Fairchild air show, Holland was again the command pilot of the B-52 aerial demonstration flight. During the demonstration, Holland's aircraft again violated several 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 apparently took no action.[14] One week later Colonel Capotosti became the new DO. At some point after assuming the position, 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.[15]

Basic structure of USAF wings, groups, and squadrons

On 14 and 15 April 1993, Holland was the mission commander of a two-ship training mission to a bombing range near Guam in the Pacific Ocean. During the mission, Holland flew his aircraft 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, which was 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 not do anything about it and may have 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".[16]

At the 8 August 1993 Fairchild air show, Holland once again commanded the B-52 demonstration flight. The demonstration profile once again included bank angles 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 of 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.[3][17]

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".[3][7][18][19][20]

Lt Col Mark McGeehan, the copilot on the accident flight

After that mission, the crew decided that they would never again fly with Holland and reported the incident to the bomb squadron leadership. The 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 or 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, there was considerable animosity between Holland and McGeehan.[3][21][22]

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. The demonstration profile – as briefed by Holland – included numerous violations of regulations, including steep bank angles, low-altitude passes, and steep pitch attitudes. Brooks ordered Holland not to exceed 45° bank angles 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 crash.[13]

Other factors

[edit]

The demonstration profile as designed by Holland included a 360° turn around Fairchild's air-traffic-control tower. Holland had not attempted this maneuver in previous air-show demonstrations. During the final flight, Holland performed a series of 60° banked turns and a 68° pitch climb in violation of Brooks' orders. No evidence exists that McGeehan or Wolff attempted to intervene as Holland executed the maneuvers.[8]

Pellerin was originally scheduled to fly in this mission, as he had done on the 17 June flight. Pellerin was unavailable for the flight on 24 June 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. Thus, Wolff was not aware of the planned mission profile and did not have an opportunity to raise any objections before take-off.[8]

All of the aircrew involved in the crash had only limited flying time in the months before the crash. The B-52's aircrew were apparently unaware that the aircraft had stalled until shortly before impact, 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, the aircraft was likely too low to recover before hitting the ground.[8]

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

Conclusions

[edit]

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.[3][7][18][24]

The other environmental factors involved, including the addition of a new maneuver (the 360° turn around the tower), inadequate pre-flight involvement of Colonel Wolff, and the distractions from the 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.[3][7][18][24]

Aftermath

[edit]

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 the USAF's safety record stated that this crash was an example of a pattern of problems related to enforcement of safety procedures within the USAF.[3][25]

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.[26]

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.[27][28]

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.[29]

See also

[edit]

References

[edit]

Notes

[edit]
  1. ^ "336th Training Group history report". Air Force Historical Research Agency. 31 December 1994. pp. 12, 43.
  2. ^ Jewell, Mark (25 June 1995). "Another tragedy at Fairchild". Moscow-Pullman Daily News. (Idaho-Washington). Associated Press. p. 1. Archived from the original on 12 February 2023. Retrieved 12 February 2023.
  3. ^ a b c d e f g h Thompson, Mark (29 May 1995). "Way, Way Off in the Wild Blue Yonder". Time. Archived from the original on 20 July 2013. Retrieved 1 March 2007.
  4. ^ Kern, Darker Shades of Blue, pp. 30–31; USAF, AFR 110-14, pp. 2–3.
  5. ^ Piper, Chain of Events, p. 136; Kern, Darker Shades of Blue p. 31; USAF, AFR 110-14, pp. 2–3.
  6. ^ Kern, Darker Shades of Blue, p. 30.
  7. ^ a b c d Diehl, Silent Knights, p. 125.
  8. ^ a b c d e f g USAF, AFR 110-14, all.
  9. ^ "Brigadier General Orin L. Godsey". Air Force Link. 1996. Archived from the original on 15 February 2007. Retrieved 16 February 2007.
  10. ^ USAF, AFR 110-14, pp. 3–4; Kern, Darker Shades of Blue, pp. 34–35, 42–48.
  11. ^ Diehl, Silent Knights, p. 125; USAF, AFR 110-14, pp. 3–4.
  12. ^ Kern, Darker Shades of Blue, p. 36.
  13. ^ a b USAF, AFR 110-14, pp. 3–4; Kern, Darker Shades of Blue [page needed].
  14. ^ Kern, Darker Shades of Blue, pp. 37–38.
  15. ^ Kern, Darker Shades of Blue (web)
  16. ^ Diehl, Silent Knights, p. 125; Kern, Darker Shades of Blue, pp. 38–39. The article does not state whether this DO was Colonel Capotosti or a new DO, Colonel William E. Pellerin.
  17. ^ "Brigadier General James M. Richards". Air Force Link. 1996. Archived from the original on 15 February 2007. Retrieved 16 February 2007.
  18. ^ a b c USAF, AFR 110-14, pp. 2–3.
  19. ^ Kern, Darker Shades of Blue (web).
  20. ^ Walter, Jess (25 June 1994). "Shocking footage transfixes viewers again and again". Spokesman-Review. (Spokane, Washington). p. A6. Archived from the original on 12 February 2023. Retrieved 12 February 2023.
  21. ^ Kern, Darker Shades of Blue, pp. 44–45; USAF, AFR 110-14, pp. 3–4.
  22. ^ "Lt. Col. Mark C. McGeehan". Lou Holtz/Upper Ohio Valley Hall of Fame. 2000. Archived from the original on 12 March 2007. Retrieved 1 March 2007.
  23. ^ Camden, Jim (21 June 1994). "Under fire". Spokesman-Feview. (Spokane, Washington). p. A1. Archived from the original on 12 February 2023. Retrieved 12 February 2023.
  24. ^ a b Kern, Darker Shades of Blue [page needed].
  25. ^ Diehl, Silent Knights, p. 126.
  26. ^ Trimble, Stephen (17 December 2010). "C-17 crash report exposes cracks in USAF safety culture". Flightglobal. Reed Business Information. Archived from the original on 20 December 2010. Retrieved 5 March 2011.
  27. ^ Kern, Darker Shades of Blue, p. 29.
  28. ^ "The Crash of 'Czar 52'". Check-Six.com. Archived from the original on 13 May 2007. Retrieved 30 June 2013.[unreliable source?]
  29. ^ "Michael Bay apologizes, will cut B-52 crash from film". Air Force Times. Retrieved 12 November 2015.

Bibliography

[edit]
[edit]
Wikimedia Commons has media related to B-52 aircraft crash at Fairchild Air Force Base.
Retrieved from "https://en.wikipedia.org/w/index.php?title=1994_Fairchild_Air_Force_Base_B-52_crash&oldid=1247065722"