Sticky Thread For Mid-Atlantic MilAir 2022

Status
Not open for further replies.

AirScan

Member
Premium Subscriber
Joined
Feb 13, 2007
Messages
3,029
Here's an excerpt from the LiveATC 1600Z reel for Potomac Approach on 124.7.

Here is the LiveATC audio of the Potomac KRANT sector 125.650 controller working BRAVE 1 and 2. Only clue on the ID of the TOI was they were 10 miles west of DCA tracking north-northeast grounding 80 knots. You can hear the controller calling them in the blind at the begining of the tape.

Audio: Potomac working BRAVE 1 and 2

Nothing showed up on 121.500, usually you would expect to hear the fighters trying to contact the TOI. Maybe they never had visual contact with it before Huntress cancelled the intercept ?
 

Mark

Member
Premium Subscriber
Joined
Jan 14, 2001
Messages
14,565
Location
Northeast Maryland
Seems another vid (edited) of that awful Dallas Cobra P-63 and C-17 accident shows that the Cobra may have hit a drone
and why that P-63 sort of suddenly dove down into back of the C-17. Cobra pilot had 31k flying hours so was top notch.
Dallas Midair Tragedy: New Videos Show Startling Change in Flight Path of P-63 - Plane & Pilot Magazine (planeandpilotmag.com)
Course obvious question is who was operating that drone and why did they not come forward with info... hmm.

1843 local TERRA-59 C-32B #00-9001 from McGuire calling STEEL-73 on 274.450 (AR-220) says we are 5 min behind.
 
Last edited:

wbagley

Active Member
Premium Subscriber
Joined
Dec 3, 2004
Messages
1,632
Location
Near Louisville, Kentucky
Cobra pilot had 31k flying hours so was top notch.

He certainly made a name for himself when he took a job as a replacement pilot while the Continental ALPA pilots were on strike in 1983.

Here is the narrative from the NTSB's Preliminary Report. Incredibly, to me anyway, it seems that the fighters and bombers were separated by 500 feet laterally but had no altitude separation for the flyby.

_________________________________

Aviation Investigation Preliminary Report

Location: Dallas, TX Accident Number: CEN23MA034
Date & Time: November 12, 2022, 13:22 Local Registration: N7227C (A1); N6763 (A2)
Aircraft: Boeing B17 (A1); Bell P63 (A2) Injuries: 5 Fatal (A1); 1 Fatal (A2)
Flight Conducted Under: Part 91: General aviation - Air race/show (A1); Part 91: General aviation - Air race/show (A2)

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.

 

Mark

Member
Premium Subscriber
Joined
Jan 14, 2001
Messages
14,565
Location
Northeast Maryland
He certainly made a name for himself when he took a job as a replacement pilot while the Continental ALPA pilots were on strike in 1983.
Here is the narrative from the NTSB's Preliminary Report. Incredibly, to me anyway, it seems that the fighters and bombers were separated by 500 feet laterally but had no altitude separation for the flyby.
Well being a scab pilot way back in the early 80's is just throwing un-needed dirt at him.
Though notice in vids that the first two fighters stayed well west of the B-17 as planned but the P-63 seemed to almost target the B-17.
Drone or no drone closing fast on that B-17 was a bad idea..
Even the best of older aviators make fatal mistakes like my old favorite Dale Snodgrass.Saw him a few times around here in his F-86 Sabre jet.
NTSB Releases Final Report on Dale Snodgrass Crash - Plane & Pilot (planeandpilotmag.com)

US Navy needs better port navigation training as seems they almost did it again.. :(
VIDEO: Navy ships play 'chicken' in San Diego Bay; Navy investigating (americanmilitarynews.com)
 
Last edited:

RaleighGuy

Member
Premium Subscriber
Joined
Jul 15, 2014
Messages
15,115
Location
Raleigh, NC

wbagley

Active Member
Premium Subscriber
Joined
Dec 3, 2004
Messages
1,632
Location
Near Louisville, Kentucky
Actually, I believe it was a pilot and a passenger, not two pilots. The female passenger was extricated first. They were sent to local trauma centers with serious but apparently non-life threatening injuries according to Montgomery County Fire Chief Scott Goldstein.

The pilot was apparently the owner of the aircraft, a civil trial lawyer who has a practice in DC.

The 911 call that was released indicates to me that the pilot was rational and not impaired. He says that he was lower than he should have been on the approach and did not know why. There was no indication that he lost engine power due to something like fuel exhaustion or carburetor icing.

However, in this ATC recording it sounds like the pilot was somewhat disoriented, missing headings and seemingly not able to take a final vector to the initial fix BEGKA for the RNAV (GPS) Runway 14 approach at Montgomery County Airport. He ended up about 100 feet above ground level about a mile from the runway. Normally he would be more like 300 feet above the ground at that point.


GAI RNAV 14 05212R14_1.jpg
 

Mark

Member
Premium Subscriber
Joined
Jan 14, 2001
Messages
14,565
Location
Northeast Maryland
Last edited:

dmi

Active Member
Premium Subscriber
Joined
Oct 3, 2007
Messages
510
Location
Somewhere In, MD
The link works great, thanks for sharing it. (y)

Coast Guard helo BLACKJACK ONE was joined by DC ANG F-16s BRAVE ONE and TWO for the intercept.

Here's an excerpt from the LiveATC 1600Z reel for Potomac Approach on 124.7. You can hear the controller, a supervisor and the instant disruption that ensues with an intercept at lunch rush hour. At about 2:35 into the clip the controller apologizes 'for all that is going on, it's crazy'.

View attachment 131956
Did anyone figure out what the scramble was for?
 
Status
Not open for further replies.
Top