2019 Boeing B-17 Flying Fortress crash
Collings Foundation Boeing B17 G · Crashed on final approach due to double engine failure and pilot error
From Bradley International Airport (BDL) to Bradley International Airport (BDL)
Event
- NTSB case
- ERA20MA001
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- 7 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 13
- Survivors
- 6
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 6 · 1 on the ground
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing B17 G
- Aircraft type
- Boeing B17
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N93012
- Operator
- Collings Foundation
- Onboard fatalities
- Unknown
- Route
- From Bradley International Airport (BDL), Windsor Locks, CTTo Bradley International Airport (BDL), Windsor Locks, CT
- Aircraft age
- About 75 years (built 1944)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area undershoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
From the Wikipedia article
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.
Background
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 argued that the FAA had been too strict in interpreting the rules of the program, and he had requested changes to allow passengers to manipulate an aircraft's flight controls.
Accident
On October 2, 2019, three crew and ten passengers boarded the B-17 for the "living history" flight. Takeoff was delayed by 40 minutes because of difficulty starting one of the engines. The pilot shut down the other engines, used a spray can to "blow out the moisture", and finally got the engine started. The aircraft took off from Bradley International Airport in Windsor Locks, Connecticut, at 09:48 local time (13:48 UTC). A witness reported that an engine was sputtering and smoking. At 09:50, the pilot radioed that there was a problem with the airplane's No. 4 engine, 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. The control tower diverted other traffic and cleared the bomber for an emergency landing on Runway 6. at At 09:54, the aircraft came in low, touched down 1000 feet short of the runway, 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. The aircraft burst into flames.
Seven occupants were killed, including the pilot and co-pilot, aged 75 and 71 respectively. The remaining six were injured severely enough to be taken to the hospital, including one who was airlifted. One of the passengers, 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. One person on the ground was injured.
The airport was closed for three and a half hours following the crash.
The crash and fire destroyed most of the aircraft. Only the left wing and part of the tail remained.
Investigation and cause
Investigation
The National Transportation Safety Board (NTSB) opened an investigation into the accident. A "go team" was dispatched to Bradley International Airport, headed by Jennifer Homendy.
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.
According to the final report released by the NTSB on May 17, 2021, the probable cause of the crash was:
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."
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.
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 with the landing gear extended. The pilot lowered the gear about 2.7 nmi from the runway threshold, in the downwind leg of the traffic pattern. The NTSB concluded that an airspeed of 120 mph 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". 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.
Text from the Wikipedia article “2019 Boeing B-17 Flying Fortress crash” (revision 1356589322, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
The National Transportation Safety Board (NTSB) identified the following safety issues during this accident investigation:
the need for an appropriate regulatory framework for living flight history experience (LHFE) flights, including maintenance and management policies and procedures; the need for increased Federal Aviation Administration (FAA) oversight of LHFE operations; and the need for FAA oversight of LHFE operators’ safety management systems (SMS).
These safety issues are discussed in the NTSB’s aviation investigation report addressing broader systemic safety issues associated with revenue passenger-carrying operations currently conducted under Title 14 Code of Federal Regulations Part 91, including LHFE flights. That aviation investigation report, titled Enhance Safety of Revenue PassengerCarrying Operations Conducted Under Title 14 Code of Federal Regulations Part 91 (NTSB/AAR-21/03), can be accessed from the Aviation Accident Reports page of the NTSB’s website. This report includes references to safety recommendations from the Part 91 aviation investigation report.
The vintage, former US military bomber airplane was on a tour that allowed members of the public to purchase an excursion aboard the airplane for an LHFE flight. The accident flight was the airplane’s first flight of the day. During the initial climb, one of the pilots retracted the landing gear, and the crew chief/flight engineer (referred to as the loadmaster) left the cockpit to inform the passengers that they could leave their seats and walk around the airplane.
One of the pilots reported to air traffic control that the airplane needed to return to the airport because of a rough magneto. At that time, the airplane was at an altitude of about 600 ft above ground level (agl) on the right crosswind leg of the airport traffic pattern for runway 6. The approach controller asked the pilot if he needed any assistance, to which the pilot replied, “negative.”
When the loadmaster returned to the cockpit, he realized that the airplane was no longer climbing, and the pilot, realizing the same, instructed the copilot to extend the landing gear, which he did. The loadmaster left the cockpit to instruct the passengers to return to their seats and fasten their seat belts. When the loadmaster returned again to the cockpit, the pilot stated that the No. 4 engine was losing power; the pilot then shut down that engine and feathered the propeller without any further coordination or discussion.
When the airplane was at an altitude of about 400 ft agl, it was on a midfield right downwind leg for runway 6. Witness video showed that the landing gear had already been extended by that time, even though the airplane still had about 2.7 nautical miles to fly in the traffic pattern before reaching the runway 6 threshold.
During final approach, the airplane struck the runway 6 approach lights in a right-wing-down attitude about 1,000 ft before the runway and then contacted the ground about 500 ft before the runway. After landing short of the runway, the airplane traveled onto the right edge of the runway threshold and continued to veer to the right. The airplane collided with vehicles and a deicing fluid tank before coming to rest upright about 940 ft to the right of the runway. A postcrash fire ensued.
Postaccident examination of the airframe revealed no preimpact mechanical anomalies that would have precluded normal operation. Teardown examination of the Nos. 3 and 4 propellers revealed that their blades were in the low-pitch and feathered positions, respectively.
Teardown examination of the No. 4 engine revealed that the left magneto’s P-lead was partially pulled out of the magneto housing and that a single strand of safety wire was around the retaining nut. Although the No. 4 engine’s left magneto produced a strong spark on the ignition leads for all nine cylinders, the grounding tab contacted the housing and caused the magneto to short and not function during a postaccident test. The No. 4 engine’s right magneto produced no spark on one of the nine ignition leads and a weak and intermittent spark on the other eight ignition leads because of wear to the compensator cam. The shortedout left magneto would have caused rough engine operation and a partial loss of engine power that would have been exacerbated by the weak right magneto, which is likely what prompted the pilot to shut down the No. 4 engine and return to the airport.
With the No. 4 engine shut down, the pilot would have had to use a higher power setting for the No. 3 engine to compensate for the loss of power from the No. 4 engine. Teardown examination of the No. 3 engine revealed evidence of detonation on four of the nine cylinders. In addition, the teardown examination revealed that the spark plugs were worn and had gaps between the electrodes that were beyond the manufacturer’s specifications. The condition of the spark plugs likely resulted in detonation and a partial loss of engine power that further reduced the total thrust available and exacerbated the thrust asymmetry. The pilot likely did not recognize, or recognized too late, the extent of the loss of engine power on the airplane’s right side.
The pilot had performed a preflight run-up check of the magnetos at an engine speed of 1,700 rpm, which was higher than the 1,600-rpm speed in the Collings Foundation’s run-up checklist; after the check, the magnetos appeared to perform normally. However, a B-17 engine ground test checklist included instructions to check the magnetos at an engine speed between 1,900 and 2,000 rpm. If the pilots had been required to perform the magneto check at the higher rpm, they might have detected the detonation on the No. 3 engine and/or the magneto anomalies on the No. 4 engine (if either resulted in an rpm drop that exceeded 100 rpm, which would have been inconsistent with the B17’s acceptable limits) and taken action before the flight to resolve the issues.
During the return to the airport, the pilot flew the traffic pattern at an airspeed of 100 mph and below, and he allowed the airspeed to decay far below that required to minimize the loss of altitude over a given distance flown (about 120 mph). It is likely that the airplane was unable to maintain altitude at the lower airspeeds because the pilot could apply only a limited amount of power to the left-wing engines while simultaneously trimming the asymmetric thrust with the available rudder authority. Extending the landing gear created additional drag that exacerbated this situation; the landing gear should not have been extended until it became evident that the airplane could reach the runway. If the pilot had lowered the airplane’s nose to maintain the airspeed that was initially achieved during the climb and kept the landing gear retracted until landing on the runway was assured, the NTSB’s airplane performance study showed that the airplane could likely have overflown the approach lights and touched down beyond the runway threshold. Thus, the pilot did not appropriately manage the airplane’s configuration and airspeed after he shut down the No. 4 engine.
The accident pilot was also the Collings Foundation’s director of maintenance and was responsible for performing the airplane’s maintenance while it was on tour. However, the teardown examinations of the Nos. 3 and 4 engines revealed maintenance issues that were not addressed during the airplane’s current tour. For example, the No. 3 engine’s 25-hour inspection occurred less than 1 month before the accident. As part of that inspection, the spark plugs should either have been cleaned, inspected, and tested or replaced with new plugs, and the gap between the electrodes should have been checked. The teardown examination found worn spark plugs with gaps between the electrodes that were beyond the manufacturer’s specifications, which should have been identified and corrected during the inspection of the No. 3 engine. As previously stated, the worn spark plugs would have contributed to the partial loss of power on the No. 3 engine and the asymmetric thrust.
The 25-hour inspection also includes a check of the point gap for each magneto. The No. 4 engine had its 25-hour inspection 9 days before the accident, but the teardown examination found that the gap between the points on the right magneto was less than the minimum gap that the manufacturer required, indicating that this check was either not performed or was improperly performed. As a result of the point gap, most of the ignition leads produced sparks that were weak or intermittent, adding to the loss of engine power caused by the short in the left magneto. To address the aircraft maintenance deficiencies found in this and other accident investigations discussed in the Part 91 aviation investigation report, the NTSB issued Safety Recommendation A-21-9 in April 2021. This safety recommendation asked the FAA to “develop national safety standards, or equivalent regulations, for revenue passenger-carrying operations that are currently conducted under Title 14 Code of Federal Regulations Part 91, including, but not limited to…living history flight experience and other vintage aircraft flights.” The recommendation stated that these standards, or equivalent regulations, should include (among other things) operationally specific maintenance requirements.
At the time of the accident, the Collings Foundation was operating with an LHFE exemption that provided the operator with relief from specific FAA regulations. The FAA’s most recent letter granting the Collings Foundation’s exemption stated that the foundation “must maintain and apply on a continuous basis its safety and risk management program that meets or exceeds the criteria specified in the FAA [LHFE] Policy.” The FAA’s policy stated that LHFE operators, including the Collings Foundation, were required to have a plan to mitigate risks that followed safety risk management principles.
The Collings Foundation implemented an SMS about 2 1/2 years before the accident, which could have met the requirements of the FAA’s LHFE policy and the FAA’s letter that granted the foundation’s LHFE exemption. However, the SMS was not an effective safety risk management program. The SMS safety officer, who was responsible for managing the SMS, was a part-time, volunteer pilot and, as such, interacted with the foundation’s management and personnel on a sporadic basis only. Further, the SMS did not detect and appropriately manage the risks associated with safety issues related to the pilot’s inadequate maintenance of the airplane while it was on tour.
The SMS also did not detect that the Collings Foundation’s engine run-up checklist was inconsistent with the B-17 engine ground test checklist or that the pilot and copilot did not wear their shoulder harnesses during flights (as reported by the loadmaster). In addition, the SMS did not detect that the loadmaster’s passenger briefings might have been insufficient (as indicated by statements from multiple surviving passengers that the briefing did not include information about seat belts, exits, or emergency equipment) or that he would stand unrestrained between the pilot and copilot during takeoff and landing, even though the foundation indicated that the seat to the left of the ball turret was available for him. The pilots’ failure to use their shoulder harnesses and the loadmaster’s failure to be restrained during takeoff and landing were inconsistent with federal regulations addressing the use of safety belts and shoulder harnesses.
Even though the Collings Foundation was not specifically required to have an SMS, the FAA’s most recent letter granting the Collings Foundation’s exemption stated that the foundation was required to have an SMS manual (used as a basis for an equivalent level of safety) and provide it to the Orlando, Florida, Flight Standards District Office (FSDO). However, the manual was not a regulatory or an approved document, and the FSDO did not review the manual or the safety reports submitted as part of the SMS to ensure that the SMS met or exceeded the safety risk management criteria in the FAA’s policy for operators with LHFE exemptions. As a result, the FAA’s oversight of the Collings Foundation’s SMS was not effective in identifying and mitigating safety risks. In April 2021, the NTSB issued Safety Recommendations A-21-13, which asked the FAA to require SMS for the revenue passenger-carrying operations discussed in the Part 91 aviation investigation report; these operations included LHFE flights. The NTSB also issued Safety Recommendation A21-14, which asked the FAA to provide ongoing oversight of each operator’s SMS once established.
Probable cause
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 pilot/maintenance director’s inadequate maintenance while the airplane was on tour, which resulted in the partial loss of power to the Nos. 3 and 4 engines; the Collings Foundation’s ineffective safety management system (SMS), which failed to identify and mitigate safety risks; and the Federal Aviation Administration’s inadequate oversight of the Collings Foundation’s SMS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: 2019 Boeing B-17 Flying Fortress crash
- Revision
- 1356589322 · 2026-05-28 · retrieved 2026-09-18
- Wikidata
- Q69551492
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record ERA20MA001
- Event ID
- 20191002X11326
- Case number
- ERA20MA001
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "2019 Boeing B-17 Flying Fortress crash" (page 61947103, revision 1356589322); merged with NTSB case ERA20MA001 (events / aircraft)
- Date
- NTSB record ERA20MA001: NTSB narrative opening date, consistent with the API date and time (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record ERA20MA001
- Map position
- NTSB record ERA20MA001: events decimal coordinates
- Aircraft, operator and route
- NTSB record ERA20MA001: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record ERA20MA001: operated under Part 91: General Aviation
- Fatalities
- NTSB record ERA20MA001: NTSB API totalFatal
- Ground fatalities
- NTSB record ERA20MA001: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "2019 Boeing B-17 Flying Fortress crash" and NTSB case ERA20MA001, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.