The NTSB Issues Preliminary Report On The C-150/F-16 Mid-Air Collision | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.01.24

Airborne-Unlimited-04.16.24

Airborne-FlightTraining-04.17.24 Airborne-Unlimited-04.11.24

Airborne-Unlimited-04.12.24

Join Us At 0900ET, Friday, 4/10, for the LIVE Morning Brief.
Watch It LIVE at
www.airborne-live.net

Mon, Jul 20, 2015

The NTSB Issues Preliminary Report On The C-150/F-16 Mid-Air Collision

The Accident Took The Lives Of The Cessna Pilot And Passenger; The F-16 Pilot Ejected And Survived

The preliminary report indicates that the Cessna was destroyed at the time of the collision but that the F-16 continued for another 3 miles before the pilot ejected at low altitude. Visual meteorological conditions prevailed at the time of the accident. The accident occurred near Monks Corner, SC on July 7 of this year.

The report indicates that the F-16 was operating under instrument flight rules while the Cessna was operating under visual flight rules. According to the report, the Cessna was not in contact with air traffic control but the presence of the airplane was detected as the Cessna was using the appropriate VFR code.

The following is an excerpt from the preliminary report:

According to preliminary air traffic control (ATC) radar and voice communication data provided by the Federal Aviation Administration (FAA), the F-16 pilot contacted the approach controller at CHS (Charleston Air Force Base/International Airport) about 1052 and requested to perform a practice tactical air navigation system (TACAN) instrument approach to runway 15.

The controller subsequently instructed the F-16 pilot to fly a heading of 260 degrees to intercept the final approach course. At 1055, the controller instructed the F-16 pilot to descend from his present altitude of 6,000 feet to 1,600 feet. About that time, the F-16 was located about 34 nautical miles northeast of CHS.

At 1057:41, a radar target displaying a visual flight rules transponder code of 1200, and later correlated to be the accident Cessna, appeared in the vicinity of the departure end of runway 23 at MKS (Berkeley County Airport), at an indicated altitude of 200 feet. The Cessna continued its climb, and began tracking generally southeast over the next 3 minutes. For the duration of its flight, the pilot of the Cessna did not contact CHS approach control, nor was he required to do so. At 1100:18, the controller advised the pilot of the F-16, "traffic 12 o'clock, 2 miles, opposite direction, 1,200 [feet altitude] indicated, type unknown."

The F-16 pilot responded and advised the controller that he was "looking" for the traffic. At 1100:26, the controller advised the F-16 pilot, "turn left heading 180 if you don't have that traffic in sight." The pilot responded by asking, "confirm 2 miles?" Eight seconds later, the controller stated, "if you don't have that traffic in sight turn left heading 180 immediately." Over the next 18 seconds, the track of the F-16 began turning southerly.

At 1100:49, the radar target of the F-16 was located 1/2 nautical mile northeast of the Cessna, at an indicated altitude of 1,500 feet, and was on an approximate track of 215 degrees. At that time, the Cessna reported an indicated altitude of 1,400 feet, and was established on an approximate track of 110 degrees. At 1100:52 the controller advised the F-16 pilot, "traffic passing below you 1,400 feet." At 1100:54, the radar reported altitude of the F-16 remained at 1,500 feet and no valid altitude information was returned for the radar target associated with the Cessna.

At that point the targets were laterally separated by about 1,000 feet. No further radar targets were received from the Cessna, and the next radar target for the F-16 was not received until 1101:13. At 1101:19, the F-16 pilot transmitted a distress call, and no subsequent transmissions were received. Air traffic control radar continued to track the F-16 as it proceeded on a roughly southerly track, and after descending to an indicated altitude of 300 feet, radar contact was lost at 1103:17 in the vicinity of the F-16 crash site.

These are excerpts from the Preliminary Report; for the entire report use the link listed below.

FMI: NTSB report
 

Advertisement

More News

ANN's Daily Aero-Linx (04.16.24)

Aero Linx: International Business Aviation Council Ltd IBAC promotes the growth of business aviation, benefiting all sectors of the industry and all regions of the world. As a non->[...]

Aero-News: Quote of the Day (04.16.24)

"During the annual inspection of the B-24 “Diamond Lil” this off-season, we made the determination that 'Lil' needs some new feathers. Due to weathering, the cloth-cove>[...]

Airborne 04.10.24: SnF24!, A50 Heritage Reveal, HeliCycle!, Montaer MC-01

Also: Bushcat Woes, Hummingbird 300 SL 4-Seat Heli Kit, Carbon Cub UL The newest Junkers is a faithful recreation that mates a 7-cylinder Verner radial engine to the airframe offer>[...]

Airborne 04.12.24: SnF24!, G100UL Is Here, Holy Micro, Plane Tags

Also: Seaplane Pilots Association, Rotax 916’s First Year, Gene Conrad After a decade and a half of struggling with the FAA and other aero-politics, G100UL is in production a>[...]

Airborne-Flight Training 04.17.24: Feds Need Controllers, Spirit Delay, Redbird

Also: Martha King Scholarship, Montaer Grows, Textron Updates Pistons, FlySto The FAA is hiring thousands of air traffic controllers, but the window to apply will only be open for >[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC