Mid-air collision Accident Boeing B-17G Flying Fortress N7227C,
ASN logo
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Saturday 12 November 2022
Time:13:22
Type:Silhouette image of generic B17 model; specific model in this crash may look slightly different    
Boeing B-17G Flying Fortress
Owner/operator:American Airpower Heritage Flying Museum
Registration: N7227C
MSN: 32513
Fatalities:Fatalities: 5 / Occupants: 5
Other fatalities:1
Aircraft damage: Destroyed
Category:Accident
Location:Dallas Executive Airport (RBD/KRBD), TX -   United States of America
Phase: Manoeuvring (airshow, firefighting, ag.ops.)
Nature:Demo/Airshow/Display
Departure airport:Dallas Executive Airport, TX (RBD/KRBD)
Destination airport:Dallas Executive Airport, TX (RBD/KRBD)
Investigating agency: NTSB
Confidence Rating: Information verified through data from accident investigation authorities
Narrative:
On November 12, 2022, about 1322 central standard time, a Boeing B-17G airplane, N7227C and a Bell P-63F airplane, N6763, collided in midair at the Dallas Executive Airport (RBD), Dallas, Texas. A post impact fire ensued. The pilot, co-pilot, and three crewmembers onboard the B-17G and the pilot of the P-63F were all fatally injured. There were no ground injuries reported. Both airplanes were operated under the provisions of Title 14 Code of Federal Regulations Part 91 in the Wings Over Dallas Airshow.

The P-63F was number 3 of a three-ship formation of historic fighter airplanes and the B-17G was lead of a five-ship formation of historic bomber airplanes.

According to the recorded audio for the airshow radio transmissions and Automatic Dependent Surveillance-Broadcast (ADS-B) data, the air boss directed both formations to maneuver southwest of the runway before returning to the flying display area, which was the designated performance area. He directed the fighter formation to transition to a trail formation, fly in front of the bomber formation, and proceed near the 500 ft show line. The bombers were directed to fly down the 1,000 ft show line. The 500 ft show line and 1,000 ft show line were 500 ft and 1,000 ft respectively from the airshow viewing line behind which the audience viewed the airshow.

There were no altitude deconflictions briefed before the flight or while the airplanes were in the air. When the fighter formation approached the flying display area, the P-63F was in a left bank and it collided with the left side of the B-17G, just aft of the wing section.

Both airplanes broke up in flight and impacted terrain in a grassy area on airport property south of the approach end of runway 31. A fire ignited in the wing center section of the B-17G as it descended to the ground. The B-17G exploded upon ground impact

The debris field was generally aligned on a magnetic heading of 320°. Documentation of the accident site found all major flight control components for both airplanes located in the debris field.

Both airplanes were equipped with ADS-B. An Avidyne IFD540 unit from the B-17G and a Garmin GPSMAP 496 unit from the P-63F were recovered and submitted to the National Transportation Safety Board Vehicle Recorders Laboratory. The IFD-540 contained position information relevant to the accident; however, the GPSMAP 496 did not record any information for the accident flight.

The wreckage of both airplanes was retained for further examination.

Sources:

https://nypost.com/2022/11/12/planes-collide-over-wings-over-dallas-air-show/
https://www.youtube.com/watch?v=DctMfHEcWAo&feature=youtu.be
https://twitter.com/DFWscanner/status/1591519373788938249?t=nseSfsXWEwPDLHm7Z1JboA&s=19

NTSB
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=7227C
https://globe.adsbexchange.com/?icao=a9ae4a&lat=32.671&lon=-96.868&zoom=14.0&showTrace=2022-11-12
https://flightaware.com/live/flight/N7227C

https://www.aerialvisuals.ca/AirframeDossier.php?Serial=31451 (history & vintage photos)

https://cdn.jetphotos.com/full/6/97221_1575188760.jpg (photo)

Location

Media:

Revision history:

Date/timeContributorUpdates
12-Nov-2022 19:57 Captain Adam Added
12-Nov-2022 20:56 nhofmann54 Updated [Aircraft type, Registration, Cn, Operator, Source, Embed code]
12-Nov-2022 21:04 nhofmann54 Updated [Embed code, Narrative]
12-Nov-2022 21:07 RobertMB Updated [Cn, Source, Narrative]
12-Nov-2022 22:14 Iceman 29 Updated [Time]
12-Nov-2022 22:18 Iceman 29 Updated [Embed code]
12-Nov-2022 22:20 Iceman 29 Updated [Embed code, Category]
12-Nov-2022 22:35 Iceman 29 Updated [Embed code]
12-Nov-2022 22:53 RobertMB Updated [Total fatalities, Total occupants, Other fatalities, Source, Embed code, Narrative]
13-Nov-2022 01:52 johnwg Updated [Time, Source, Narrative]
13-Nov-2022 09:26 harro Updated [Time, Departure airport, Destination airport, Source, Narrative]
14-Nov-2022 07:08 nhofmann54 Updated [Narrative]
14-Nov-2022 21:42 Iceman 29 Updated [Embed code]
14-Nov-2022 21:58 Iceman 29 Updated [Embed code]
15-Nov-2022 00:39 Iceman 29 Updated [Embed code]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org