Jump to content

2015 Moncks Corner mid-air collision

Coordinates: 33°11′46″N 80°00′36″W / 33.196°N 80.010°W / 33.196; -80.010
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Aviationwikiflight (talk | contribs) at 13:04, 28 March 2024 (Small clean-up.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

2015 Moncks Corner mid-air collision
Depiction of both aircraft shortly before the collision
Accident
Date7 July 2015 (2015-07-07)
SummaryMid-air collision, Air Traffic Control error
SiteMoncks Corner, South Carolina, United States
33°11′46″N 80°00′36″W / 33.196°N 80.010°W / 33.196; -80.010
Total fatalities2
Total survivors1
First aircraft

96-0085, the F-16 involved in the collision, photographed in 2003
TypeGeneral Dynamics F-16C Fighting Falcon
Operator United States Air Force
Registration96-0085
Flight originShaw AFB, South Carolina, US
DestinationJoint Base Charleston, South Carolina, US
Occupants1
Crew1
Fatalities0
Survivors1
Second aircraft

A Cessna 150M similar to the aircraft involved
TypeCessna 150M
RegistrationN3601V
Flight originBerkeley County Airport, South Carolina, US
DestinationMyrtle Beach International Airport, South Carolina, US
Occupants2
Passengers1
Crew1
Fatalities2
Survivors0

On July 7, 2015, an F-16 fighter jet operated by the United States Air Force collided in-flight with a private Cessna 150 single-engine light aircraft over Moncks Corner, South Carolina, United States. Both occupants of the Cessna were killed; the pilot of the F-16 ejected safely.

The subsequent investigation found that the local Air Traffic Control unit had failed to ensure adequate separation between the two aircraft.

Collision

At about 11:00 AM on July 7, 2015, the F-16 and Cessna 150 collided over Moncks Corner, South Carolina, about 30 miles (48 km) north of Charleston.[1] Witnesses state that the Cessna was climbing when the F-16 hit it broadside.[2] The Cessna (N3601V) was climbing out of the MKS airport under visual flight rules, not in communication with FAA Air Traffic Control. Death 41 (the F-16) was on an ATC assigned heading of 260 degrees and issued a descent to maintain 1600' for an ILS approach to Runway15 at KCHS.

At 1100:16, the CHS ATC approach controller issued a traffic advisory advising the F-16 pilot of "traffic 12 o'clock, 2 miles, opposite direction, 1,200 [ft altitude] indicated, type unknown." At 1100:24, the F-16 pilot responded 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." At 1100:30, the pilot asked, "confirm 2 miles?" At 1100:33, the controller stated, "if you don't have that traffic in sight turn left heading 180 immediately." As the controller was stating the instruction and over the next 18 seconds, the radar-derived ground track of the F-16 began turning southerly toward the designated heading.

At 1100:49, the radar target of the F-16 was 1/2 nm northeast of the Cessna, at an altitude of 1,500 ft, and was on an approximate track of 215°. At that time, the Cessna reported an altitude of 1,400 ft and was established on an approximate ground track of 110°. The two aircraft collided at an approximate altitude of 1450 ft.[3]

The F-16 flew for a further three minutes before the pilot transmitted a mayday call. He then ejected safely.[4][5] Both aircraft crashed in Lewisfield Plantation.[1] Both occupants of the Cessna 150 were killed.[6][7][8] The pilot of the F-16 was on an instrument training mission. Its destination was Joint Base Charleston.[9] The Cessna was reported to be on a flight from Berkeley County Airport to Myrtle Beach.[2]

Aircraft

The first aircraft was a General Dynamics F-16C Fighting Falcon registered 96-0085.[10][11] It was based at Shaw Air Force Base, South Carolina, and was operated by the 20th Fighter Wing of the United States Air Force.[1][9]

The second aircraft involved was a privately-owned Cessna 150M registered N3601V.[12][13]

Investigation

The National Transportation Safety Board conducted the investigation into the accident.[4][14] The cause of the collision was found to be air traffic control errors in failing to provide an appropriate conflict resolution between the two aircraft.[15] The Federal Aviation Administration also opened an investigation.[2]

References

  1. ^ a b c "F-16, Cessna collide over Berkeley County plantation". ABC News. 7 July 2015. Retrieved July 7, 2015.
  2. ^ a b c Pager, Tyler. "2 killed after F-16, Cessna collide over S.C." USA Today. Retrieved July 7, 2015.
  3. ^ "NTSB Report".
  4. ^ a b "NTSB Identification: ERA15FA259A". National Transportation Safety Board. July 18, 2015. Retrieved July 19, 2015.
  5. ^ "Two Dead In F-16-Cessna Collision". AVweb. 7 July 2015. Retrieved July 8, 2015.
  6. ^ Santos, Suzelle; Phillips, Patrick. "NTSB: 2 killed aboard Cessna in midair collision with F-16". Tucson News Now. Archived from the original on July 9, 2015. Retrieved July 7, 2015.
  7. ^ "Cessna 150, F-16 collision: Body of passenger found as search for pilot continues". CBC News. July 8, 2015. Retrieved July 8, 2015.
  8. ^ "FAA Registry – Aircraft – N-Number Inquiry". Federal Aviation Administration. Archived from the original on July 9, 2015. Retrieved July 8, 2015.
  9. ^ a b Botelho, Greg; Nottingham, Shawn (7 July 2015). "F-16 jet, Cessna airplane collide over South Carolina". CNN. Retrieved July 7, 2015.
  10. ^ "F-16 collides with Cessna over South Carolina". f-16.net. Retrieved July 8, 2015.
  11. ^ "Airframe Details for F-16 #96-0085". f-16.net. Retrieved July 10, 2015.
  12. ^ "Aircraft Registration (N3601V)". Flight Aware. Retrieved July 8, 2015.
  13. ^ "FAA Accident and Incident Notification(s): Notice(s) Created 08-JUL-15". Federal Aviation Administration. Archived from the original on 2015-07-09. Retrieved July 8, 2015.
  14. ^ "Shaw Air Force Base F-16 pilot taken to Joint Base Charleston". The State. Retrieved July 7, 2015.
  15. ^ "Educating Controllers on Two Midair Collisions" (PDF). National Transportation Safety Board. 14 November 2016. Retrieved 19 November 2016.