2019 Boeing B-17 Flying Fortress crash
From Wikipedia the free encyclopedia
Accident | |
---|---|
Date | October 2, 2019 |
Summary | Crashed on final approach due to double engine failure and pilot error[1] |
Site | Bradley International Airport, Windsor Locks, Connecticut, United States 41°55′54″N 72°41′32″W / 41.93167°N 72.69222°W |
Aircraft | |
Aircraft type | Boeing B-17G-85-DL Flying Fortress |
Aircraft name | Nine-O-Nine (marked as) |
Operator | Collings Foundation |
Registration | N93012 44-83575 (actual) 42-31909 (marked as) |
Flight origin | Bradley International Airport |
Destination | Bradley International Airport |
Occupants | 13 |
Passengers | 10 |
Crew | 3 |
Fatalities | 7 |
Injuries | 6 |
Survivors | 6 |
Ground casualties | |
Ground injuries | 1 |
On October 2, 2019, a Boeing B-17 Flying Fortress privately owned by the Collings Foundation crashed at Bradley International Airport, Windsor Locks, Connecticut, United States. Seven of the thirteen people on board were killed, and the other six, as well as one person on the ground, were injured. The aircraft was destroyed by fire, with only a portion of one wing and the tail remaining.[2]
Background
[edit]Prior to the accident, the Collings Foundation had been operating the aircraft as part of the Living History Flight Experience, a Federal Aviation Administration (FAA) program that allows owners of vintage military aircraft to offer rides in their aircraft for compensation. The Foundation's executive director, Rob Collings, had previously requested changes to allow visitors to manipulate the controls of the aircraft and argued that the FAA had been too strict in interpreting the rules of the program.[3]
Aircraft
[edit]The aircraft involved was a 74-year-old Boeing B-17 Flying Fortress, military serial number 44-83575 (variant B-17G-85-DL) with civilian registration N93012.[4] The aircraft was painted as a representation of a different B-17G,[5] Nine-O-Nine, with military serial number 42-31909 (variant B-17G-30-BO), which had been scrapped shortly after World War II.[6] During its original military career, the plane operated as an Air-Sea Rescue aircraft until 1952, when it was reassigned to the Air Force Special Weapons Command for use as a specimen in weapons-effects testing. In this role, it was subjected to three nuclear explosions as part of Operation Tumbler–Snapper. The aircraft was purchased as scrap in 1965 for a price of US$269 (equivalent to $2,601 in 2023); being in relatively good condition, it was restored to airworthy condition for use as a water bomber over the course of ten years, entering service in 1977. Following its operator's liquidation in 1985, the aircraft was acquired by the Collings Foundation in January 1986,[5] restored to its 1945 configuration, and N93012 was flying as Nine-O-Nine by August 1986.[7][8] While operated by the Collings Foundation, it was involved in two prior accidents. On August 23, 1987, it overran the runway on landing at Beaver County Airport in Pittsburgh, Pennsylvania,[5][9] and on July 9, 1995, it was damaged on landing at Karl Stefan Memorial Airport in Norfolk, Nebraska, as the result of an undercarriage (landing gear) malfunction.[10][11]
The October 2019 crash and resulting fire destroyed most of the aircraft. Only the left wing and part of the tail remained.[12]
Accident
[edit]The "living history" flight had been delayed 40 minutes because of difficulty starting one of the engines. The pilot had shut down the other engines and gone out with a spray can to "blow out the moisture" prior to commencing the flight.[13][14] The aircraft had taken off from Bradley International Airport in Windsor Locks, Connecticut, at 09:48 local time (13:48 UTC), on a local flight.[10][15] It carried three crew and ten passengers.[16] A witness reported that an engine was sputtering and smoking.[17] At 09:50, the pilot radioed that there was a problem with the airplane's No. 4 engine,[12] the outer engine on the right wing. The pilot told the crew chief (who was also the loadmaster) to instruct the passengers to return to their seats; after the crew chief did so and returned to the cockpit, the pilot shut down the No. 4 engine.[18] The control tower diverted other traffic for an emergency landing on Runway 6. The aircraft came in low, touched down 1,000 feet (300 m) short of the runway,[13] clipped the Instrument Landing System (ILS) antenna array, veered to the right off the runway across a grassy area and taxiway, and then crashed into a de-icing facility at 09:54.[19][12] The aircraft burst into flames.[17] Seven occupants were killed, and the remaining six were injured severely enough to be taken to the hospital, including one who was airlifted.[10][19] Among the dead were the pilot and co-pilot, aged 75 and 71 respectively.[20] One person on the ground was injured.[21] The airport was closed for three and a half hours following the crash.[17]
Rescue
[edit]One of the passengers on the plane, a Connecticut Air National Guardsman, managed to open an escape hatch after the crash, despite having a broken arm and collarbone. An airport employee, who had been working in the building into which the plane had crashed, ran to the wreckage to help pull injured passengers from the burning plane. The employee suffered severe burns on his hands and arms and was taken by ambulance to the hospital.[22]
Investigation
[edit]The National Transportation Safety Board (NTSB) opened an investigation into the accident.[17] A "go team" was dispatched to Bradley International Airport, headed by Jennifer Homendy.[23]
The FAA also launched an investigation into the crash, and in March 2020, it revoked the exemption that allowed the Collings Foundation to carry paying passengers, citing safety deficiencies found during its investigation. According to the FAA, the foundation had not maintained a "culture of safety", and key personnel overseeing the flight were ignorant of the safety management system (SMS) that the organization had been required to implement to earn the exemption; the FAA found that the B-17 crew chief was completely unaware that the SMS existed.[24]
According to the final report released by the NTSB on May 17, 2021, the probable cause of the crash was:[18]: 5
The pilot's failure to properly manage the airplane's configuration and airspeed after he shut down the No. 4 engine following its partial loss of power during the initial climb. Contributing to the accident was the inadequate maintenance of the airplane while it was on tour, which resulted in the partial loss of power to the Nos. 3 and 4 engines; the ineffective safety management system (SMS) of the Collings Foundation, which failed to identify and mitigate safety risks; and the FAA's inadequate oversight of the Collings Foundation's SMS.
Post-crash teardowns of the No. 4 engine and the No. 3 engine (the inner engine on the right wing) found evidence of poor maintenance of the magnetos and spark plugs, which are critical components of the engines' ignition systems. The spark plugs of the No. 3 engine were worn beyond the manufacturer's specifications although a 25-hour engine inspection was done less than one month before the crash. A 25-hour inspection of the No. 4 engine had been performed only nine days prior, but the left magneto had an intermittent short circuit, and the right magneto was producing a weak spark in 8 of the 9 cylinders due to wear of the compensator cam. The NTSB said the problems with the No. 4 engine magnetos likely caused a loss of engine power that prompted the pilot to shut the engine down, while "The pilot likely did not recognize, or recognized too late, the extent of the loss of engine power on the airplane’s right side."[18]: 2
The NTSB found that the foundation's preflight checklist called for the engine run-up to be performed at lower RPM than specified in the B-17 ground maintenance checklist, and the preflight run-up of the accident flight was in fact performed at a lower RPM setting, which made magneto problems more difficult to detect because the RPM drop caused by a bad magneto would be less pronounced than at higher RPM. The foundation's SMS did not uncover or address this discrepancy in its checklist.[18]: 3,4
According to the final report, a key factor leading to the crash was the pilot's decision to fly the airfield traffic pattern at an airspeed of about 100 mph (160 km/h) with the landing gear extended.[18]: 3 The pilot lowered the gear about 2.7 nmi (5.0 km; 3.1 mi) from the runway threshold, in the downwind leg of the traffic pattern.[18]: 2 The NTSB concluded that an airspeed of 120 mph (190 km/h) would have minimized altitude loss, while the lower 100 mph airspeed made the aircraft lose altitude relatively quickly per distance flown, and lowering the gear early increased drag and "exacerbated the situation".[18]: 3 The board's airplane performance study found that the B-17 could have reached the runway if the pilot had increased airspeed by lowering the nose and keeping the gear retracted until the final approach.[18]: 4
Lawsuits
[edit]Surviving passengers and families of the deceased passengers pressed claims against the Collings Foundation. Two passengers accepted settlements in 2021 and the remaining eight claimants filed lawsuits after the final NTSB report was released. The parties then reached confidential settlements via mediation.[25] The family of the deceased co-pilot also filed a lawsuit against the Collings Foundation.[26]
References
[edit]- ^ "B-17 crash at Bradley International Airport". NTSB. Retrieved May 8, 2024.
- ^ Ranter, Harro. "ASN Aircraft accident Boeing B-17G-30-BO Flying Fortress N93012 Windsor Locks-Bradley International Airport, CT (BDL)". aviation-safety.net. Retrieved October 4, 2019.
- ^ Backus, Lisa (October 12, 2019). "In wake of fatal crash, Collings Foundation pushes to keep flying". The Middletown Press. Retrieved September 1, 2023.
- ^ Leone, Dario (October 2, 2019). "Collings Foundation B-17 Flying Fortress Crashes". theaviationgeekclub.com. Retrieved October 2, 2019.
- ^ a b c "History of the B-17 Nine O Nine". Collings Foundation. Archived from the original on August 9, 2014.
- ^ Havelaar, Marion H. (1995) The Ragged Irregulars of Bassingbourn: The 91st Bombardment Group in World War II. Schiffer Military History. ISBN 0-88740-810-9 p.185
- ^ Henrichs, Mary (August 11, 1986). "Sight of vintage bomber startles ex-crew member". The Vidette-Messenger. Valparaiso, Indiana. p. 9. Retrieved October 4, 2019 – via newspapers.com.
- ^ Thompson, Scott A. (2000) Final Cut: The Post-War B-17 Flying Fortress: The Survivors. Pictorial Histories Publishing Company. ISBN 1-57510-077-0 pp.116-120
- ^ Danhauer, Clifford (January 11, 1989). "National Transportation Safety Board Aviation Accident Data Summary, Accident Number: NYC87LA238". National Transportation Safety Board. Retrieved October 3, 2019 – via ntsb.gov.
- ^ a b c Bonner, Michael; Simison, Cynthia G. (October 2, 2019). "The vintage B-17 bomber that crashed at Bradley International Airport had crash landed before". masslive.com. Retrieved October 2, 2019.
- ^ "Nine-O-Nine's Replica Survives Emergency" (PDF). The Ragged Irregular. Vol. 28, no. 4. October 1995. pp. 1–2 – via 91stbombgroup.com.
- ^ a b c Owens, David; et al. (October 2, 2019). "7 dead, 7 injured in crash of World War II bomber at Connecticut's Bradley International Airport". Hartford Courant. Retrieved October 3, 2019.
- ^ a b "NTSB investigating whether B-17 that crashed at Bradley International Airport Wednesday had engine trouble prior to takeoff". Hartford Courant. October 3, 2019. Retrieved October 4, 2019.
- ^ "State police release names of victims, survivors of B-17 plane crash at Bradley International Airport". Hartford Courant. October 4, 2019. Retrieved October 4, 2019.
- ^ "N93012 Flight Path". Flight Aware. Retrieved October 2, 2019.
- ^ Paybarah, Azi; Negroni, Christine (October 2, 2019). "B-17 plane crashes at Bradley Airport Outside Hartford, Killing at Least 5". The New York Times. Retrieved October 2, 2019.
- ^ a b c d "World War II-era bomber trying to land crashes in fireball; 5 deaths confirmed". WDBJ7. Archived from the original on October 4, 2019. Retrieved October 2, 2019.
- ^ a b c d e f g h Aviation Investigation Final Report (Report). National Transportation Safety Board. May 17, 2021. ERA20MA001. Retrieved September 6, 2024.
- ^ a b "'Several dead' in Connecticut vintage B-17 WWII bomber crash". BBC News. October 2, 2019. Retrieved October 2, 2019.
- ^ Tziperman Lotan, Gal; Sweeney, Emily; Ellement, John R. (October 3, 2019). "Two Mass. men among 7 people killed in B-17 crash in Conn". The Boston Globe. Retrieved October 3, 2019.
- ^ Geneous, Jacob (October 2, 2019). "At least five dead after World War II-era plane crashes into airport". Metro. Retrieved October 2, 2019.
- ^ "'A very courageous individual.' Airport employee pulled injured passengers off burning plane, police sources say". Hartford Courant. October 3, 2019. Retrieved October 3, 2019.
- ^ National Transportation Safety Board [@NTSB_Newsroom] (October 2, 2019). "NTSB Go Team launching to investigate Wednesday's crash of a B17 at Bradley International Airport, Connecticut. Team led by Board Member Jennifer Homendy" (Tweet) – via Twitter.
- ^ Owens, David (March 25, 2020). "FAA says owner of World War II bomber that crashed at Bradley, killing seven, did not take safety seriously and can no longer carry passengers". Hartford Courant. Hartford, Connecticut. Retrieved March 26, 2020.
The permission Collings operated under required it to comply with specific conditions, and the FAA found that it "was not fulfilling several requirements" or satisfying its policy of maintaining "a culture of safety."
- ^ "Collings Foundation Reaches Settlement With Nine-0-Nine Crash Victims". AVweb.com. October 1, 2023.
- ^ "Family of copilot killed in fiery crash of WWII-era B-17 bomber at Bradley International Airport sues Collings Foundation that owned aircraft". Hartford Courant. June 16, 2021.
Further reading
[edit]- Collins, Dave; Haigh, Susan (October 3, 2019). "7 victims killed in Connecticut B-17 plane crash identified". Boston.com. AP. Retrieved October 4, 2019.
- "Statement from the Collings Foundation". Collings Foundation. Archived from the original on October 4, 2019.