F-16 Fighter Jet and Cessna Fatal Collision Over Charleston

Timeline

Event 1 —

The Cessna 150 climbed away from a nearby airport while the F-16 approached Charleston.

1.

Event 2 —

At about 10:52 a.m., the F-16 contacted Charleston Approach for a practice TACAN approach.

2.

Event 3 —

ATC issued headings and altitude instructions while the aircraft operated in the same area.

3.

Event 4 —

The controller issued a traffic advisory as the aircraft continued to close.

4.

Event 5 —

The F-16 began a turn that carried its flight path across the Cessna’s path.

5.

Event 6 —

About 40 seconds after the advisory, the F-16 and Cessna collided near Moncks Corner.

6.

Incident overview

At 11:00 a.m. on July 7, 2015, two aircraft were converging over South Carolina: a U.S. Air Force F-16 approaching Charleston and a small Cessna 150 climbing away from a nearby airport.

One pilot knew another aircraft was somewhere ahead.

The other pilot did not know the fighter was there.

Air traffic control had detected the conflict, but the warning came when the aircraft were already closing rapidly.

The controller issued a traffic advisory.

The F-16 pilot looked.

He could not find the Cessna.

Then ATC instructed him to turn left.

The fighter began turning—but the maneuver took it across the Cessna's flight path.

Approximately 40 seconds after the initial traffic advisory, the F-16 and Cessna collided in midair near Moncks Corner, South Carolina, roughly 30 miles north of Charleston.

The Cessna 150M was destroyed.

Its pilot and passenger were killed.

The F-16 was catastrophically damaged, but its pilot managed to keep the crippled fighter airborne for about another two and a half minutes before ejecting safely. The F-16 subsequently crashed into an uninhabited wooded area and was destroyed. The fighter pilot sustained minor injuries. (NTSB Data)

The accident became a major study in the limitations of see-and-avoid, the challenges of mixing military and civilian traffic, and the consequences of an ATC conflict-resolution decision made with very little time remaining.

Most importantly, the NTSB's final investigation did not conclude that the collision was simply a failure by one pilot to look outside.

It found that the controller's attempted resolution of the developing conflict was inadequate, while the inherent limitations of visual traffic detection contributed to both pilots being unable to avoid the collision in time. (NTSB Data)

Two Very Different Flights

The two aircraft had completely different missions.

The Cessna 150M, registration N3601V, was a privately operated, two-seat, single-engine airplane. The 30-year-old pilot held a private pilot certificate and had approximately 244 hours of total flight time, almost all of it in the Cessna 150. He was accompanied by a 68-year-old passenger. (NTSB Data)

They departed Berkeley County Airport near Moncks Corner at approximately 10:57 a.m.

The planned destination was Grand Strand Airport near North Myrtle Beach.

The Cessna was operating under visual flight rules and had not filed a flight plan. It was also not receiving flight-following services from ATC.

The airport was nontowered, and the pilot was not required to contact Charleston Approach simply because he was departing the area.

The F-16 was operating under an entirely different system.

It was a single-seat F-16CM, serial number 96-0085, assigned to the 55th Fighter Squadron at Shaw Air Force Base.

Its pilot was an experienced military aviator with approximately 2,383 hours of military flight experience, including 624 hours in the F-16. (NTSB Data)

He was flying an operational check flight after maintenance and was operating under an IFR flight plan.

His mission included practice instrument approaches at Myrtle Beach and Charleston before returning to Shaw Air Force Base.

The two aircraft therefore entered the same piece of sky from completely different directions and under different operating rules.

Neither pilot initially knew the other aircraft was there.

The F-16 Approaches Charleston

The F-16 had departed Shaw Air Force Base around 10:20 a.m.

After conducting practice approaches at Myrtle Beach International Airport, the pilot proceeded toward Charleston.

At approximately 10:52 a.m., he contacted Charleston Approach and requested a practice TACAN approach to Runway 15 at Charleston Air Force Base/International Airport.

The controller began providing radar vectors.

The F-16 was eventually instructed to fly a heading of approximately 260 degrees and descend to 1,600 feet mean sea level.

That altitude was significant.

The controller was using the minimum vectoring altitude available in that area.

There was no option to simply descend the F-16 beneath the traffic.

The aircraft was already operating relatively low while being positioned for the approach.

The controller was also managing other traffic arriving toward Charleston.

At this point, there was nothing unusual about the F-16's flight.

The danger developed when the Cessna departed Berkeley County Airport.

The Cessna Climbs Into the Same Airspace

At approximately 10:57 a.m., N3601V took off.

The airplane began climbing away from Berkeley County Airport.

The aircraft had an operating transponder, so its radar target appeared on the controller's display.

That fact would later become critical.

The controller could see the Cessna.

But she did not initially treat it as a developing conflict.

According to the NTSB investigation, the controller believed the Cessna would remain within the local traffic pattern around Berkeley County Airport.

That assumption turned out to be wrong.

The Cessna continued its departure climb toward the F-16's flight path. (NTSB Data)

The two aircraft were now moving toward one another.

The F-16 was traveling vastly faster than the Cessna.

The resulting closure rate would eventually reach approximately 300 knots.

The Radar Conflict Alert

At 11:00:13, the Charleston radar system generated a conflict alert.

The two aircraft were approximately 3.5 nautical miles apart laterally and only 400 feet apart vertically.

An audible alarm also alerted the controller.

Three seconds later, at 11:00:16, the controller issued a traffic advisory to the F-16 pilot.

The advisory described traffic at the F-16's 12 o'clock position, approximately two miles away, traveling in the opposite direction, at an indicated altitude of 1,200 feet.

The aircraft type was unknown.

The F-16 pilot acknowledged that he was looking for the traffic.

The controller then instructed him to turn left toward a heading of 180 degrees if he did not have the traffic in sight. (NTSB Data)

The exchange sounded straightforward.

But it contained a critical problem.

The F-16 pilot could not see the Cessna.

"Confirm Two Miles?"

At 11:00:30, the F-16 pilot asked the controller to confirm the traffic distance.

He asked whether the traffic was really two miles away.

That question became important during the investigation.

The F-16's own radar had detected a target much farther away—approximately 20 miles—and the pilot's understanding of the traffic location did not match what he was seeing on his displays.

The controller repeated the instruction.

The F-16 began turning.

But the turn was not the high-performance maneuver the controller apparently expected.

The pilot used the aircraft's autopilot to initiate an approximately standard-rate turn while continuing his visual search for the Cessna.

That distinction would prove critical.

The controller expected a fighter aircraft to make a much more aggressive turn.

The pilot interpreted the instruction differently.

Both believed they were acting appropriately.

The aircraft continued toward each other.

A Dangerous Turn

The F-16 was now turning left.

But because of the geometry of the two flight paths, the turn did not immediately take the fighter away from the Cessna.

Instead, the F-16's projected path crossed in front of the Cessna.

The NTSB later described this as the least conservative option available to the controller because it depended heavily on the F-16 pilot seeing the Cessna and responding correctly. (NTSB Data)

The controller had other possibilities.

She could have instructed the F-16 to climb.

She could have issued a different turn.

Or she could have used another form of separation.

But the F-16 was already at the minimum vectoring altitude, and the controller was uncertain about the Cessna's actual altitude because the Cessna pilot was not communicating with ATC.

The controller therefore chose the left turn.

The problem was that the turn required the F-16's flight path to cross the Cessna's path.

And there was almost no time remaining.

"Immediately"

The word "immediately" became one of the most important words in the investigation.

Under FAA terminology, "immediately" indicates that action is required to avoid an imminent situation.

But the controller and pilot did not share the same expectation about what "immediately" meant.

The controller later explained that she expected the F-16 to perform a high-performance fighter maneuver.

She believed the jet could turn extremely rapidly.

The F-16 pilot instead initiated approximately a standard-rate turn.

The NTSB found that the expectation of a high-performance maneuver was not clearly communicated. (NTSB Data)

The difference was only seconds.

But at a closure rate of hundreds of knots, seconds are enormous.

The Cessna Keeps Climbing

While the F-16 was turning, the Cessna continued on its departure path.

At approximately 11:00:49, the F-16 was about half a nautical mile northeast of the Cessna.

The two airplanes were now almost at the same altitude.

The controller issued another warning.

She advised the F-16 pilot that the traffic was passing below him at 1,400 feet.

The radar conflict alert continued.

The F-16's last recorded radar position came at 11:00:54.

The aircraft were about to collide.

Why Neither Pilot Saw the Other

This is where the accident becomes more complicated than a simple "failure to look."

The Cessna pilot was also operating under VFR, where the see-and-avoid principle applied.

Yet neither pilot saw the other in enough time.

The NTSB conducted an extensive aircraft-performance and cockpit-visibility study.

The results were revealing.

Because the aircraft were approaching on converging courses, each could appear to the other as a relatively small, stationary or slowly moving object.

That is one of the most dangerous visual situations for pilots.

A target that remains in nearly the same position on the windshield can be difficult to detect.

It may not appear to be moving at all.

The brain therefore has less motion information with which to identify the threat.

The NTSB found that the Cessna would have appeared small through the F-16's canopy.

As the F-16 turned left, the Cessna moved across the fighter pilot's field of view and could become obscured by part of the HUD structure. (NTSB Data)

The fighter pilot eventually saw the Cessna.

But by then, it was approximately 430 feet away.

The NTSB's analysis estimated that this was roughly one second before impact.

The Cessna Pilot Had Even Less Warning

The Cessna pilot faced an even more difficult visual problem.

Because of its speed, the fighter remained a relatively small target from the Cessna cockpit until only a few seconds before impact.

The NTSB estimated that the F-16 remained around the Cessna's 9-to-10 o'clock position until less than five seconds before the collision. (NTSB Data)

That is almost impossible to defend against using eyesight alone.

The F-16 was moving dramatically faster than the Cessna.

The fighter was also much smaller visually than its speed might suggest.

The aircraft had a transponder and radio, but no cockpit technology providing a traffic display or collision alert.

He was relying primarily on visual scanning.

The NTSB could not determine exactly how actively he was scanning for traffic immediately before the collision.

But investigators concluded that, given the geometry and speed of the approaching F-16, the Cessna pilot likely would not have had enough time to recognize and avoid the fighter once it became visually apparent. (NTSB Data)

The F-16's Radar Could Not Save the Situation

It might seem surprising that an F-16 could not simply detect a small Cessna with its radar.

But the fighter's radar was not designed primarily as a general-purpose collision-avoidance system.

Its tactical radar was optimized for detecting and tracking fast-moving targets.

A slow, small civilian aircraft presented a very different radar problem.

The NTSB found that the F-16 radar detected a target at approximately 20 miles, but that target was likely not the Cessna the controller was describing at two miles.

The F-16 did not have a dedicated traffic-collision system providing the pilots with a modern cockpit traffic picture or resolution advisory. (NTSB Data)

That meant the pilot's primary defenses were ATC information and his own eyes.

The ATC information was late and the visual acquisition came too late.

The safety layers were disappearing one by one.

The Collision

Witnesses described the Cessna traveling generally west-to-east and the F-16 traveling north-to-south.

Debris began falling across the area.

The F-16 was badly damaged but remained airborne.

One witness saw the fighter power up and turn south along the river after the collision.

The F-16's engine exhaust module had separated during the impact, leaving the aircraft without enough thrust to maintain altitude indefinitely. (Air & Space Forces Magazine)

The fighter pilot now had his own emergency.

But his aircraft was no longer capable of sustained flight.

The F-16 Pilot's Escape

The pilot attempted to keep the aircraft under control.

Radar tracked it until it reached approximately 300 feet.

At about 11:03, the pilot activated the F-16's ejection system.

The ejection seat separated him from the aircraft.

He descended safely under a parachute and landed with minor injuries. (NTSB Data)

A post-impact fire followed.

The government estimated the loss of the fighter at more than $29 million. (Air & Space Forces Magazine)

But the most important loss was not financial.

Two people aboard the Cessna had already died.

The Victims

The pilot was Joseph Elman Johnson, 30, who had earned his private pilot certificate in December 2014.

His passenger was his father, Michael Johnson, 68. (NTSB Data)

His flight instructor described him to investigators as careful and responsive.

The investigation also found that he had previously communicated with ATC on numerous occasions and understood the benefits of flight-following services. (NTSB Data)

The fact that he was not receiving flight-following on this particular flight should therefore not be interpreted as evidence that he routinely avoided ATC.

The accident happened in an area where a VFR aircraft could legally be operating without radar advisories.

That distinction became important to the safety analysis.

The Investigation Finds an ATC Failure

The NTSB's final investigation focused heavily on the controller's decision-making.

But the resolution came too late and directed the fighter into a path that crossed the Cessna's flight path.

The NTSB concluded that the controller became committed to an ineffective visual-separation plan instead of switching quickly to a different method of separation. (NTSB Data)

She recognized it.

She attempted to resolve it.

The problem was the specific resolution chosen and the timing.

The controller believed the F-16 pilot would see the Cessna or execute a high-performance turn.

The pilot did neither quickly enough.

The Role of Traffic Flow

Another subtle factor was airport traffic.

The F-16 was being sequenced toward Charleston's Runway 15.

The controller's left-turn instruction kept the F-16 closer to its intended final approach path.

From a traffic-flow perspective, that made sense.

From a collision-avoidance perspective, it was less conservative.

This is an important lesson in ATC decision-making.

A maneuver can be technically permissible while still being less robust than another available option.

When two aircraft are converging rapidly, the safest instruction is not necessarily the one that best preserves the original traffic sequence.

Collision avoidance has to take priority over efficiency.

"See and Avoid" Has Limits

The accident also became an important NTSB case study because both aircraft were operating in visual meteorological conditions.

It might therefore be easy to say:

They should have seen each other.

The investigation showed why that assumption is dangerous.

Visual detection is not perfect.

Humans have limited peripheral vision.

Cockpit structures obstruct parts of the view.

Small aircraft can blend into the background.

A converging target can appear stationary.

And pilots are often performing other tasks at the same time.

The NTSB emphasized that the see-and-avoid concept has inherent limitations, including human visual limitations, competing cockpit tasks, restricted fields of view and environmental factors. (NTSB Data)

In this accident, those limitations were amplified by the enormous difference in aircraft speed.

The Cessna could not see the F-16 in time.

ATC knew about the conflict.

That combination was fatal.

What If the Cessna Had Flight Following?

The NTSB examined this question carefully.

However, had he contacted ATC, the controller would have known more about his intended route and could have verified his altitude.

The controller might also have been able to provide the Cessna pilot with a traffic advisory concerning the F-16. (NTSB Data)

The NTSB did not say that flight-following would definitely have prevented the accident.

It is impossible to know.

But it could have added another layer of awareness.

Likewise, a cockpit traffic display could have helped.

The NTSB's simulation showed that an appropriate traffic-awareness system might have alerted the F-16 pilot to the Cessna earlier, giving him more time to respond.

The Cessna, too, could potentially have benefited from a traffic-alerting system.

The investigation therefore pointed toward technology as a valuable supplement to visual scanning—not a replacement for it. (NTSB Data)

The Final Seconds

The timeline is remarkably short.

11:00:13 — Conflict alert activates.

11:00:16 — Controller issues traffic advisory.

11:00:24 — F-16 pilot says he is looking for the traffic.

11:00:30 — Pilot asks to confirm the two-mile distance.

11:00:33 — Controller orders the left turn immediately.

11:00:49 — F-16 is approximately half a mile from the Cessna.

11:00:53 — Controller reports traffic passing below the F-16.

11:00:54 — Final Cessna radar return.

Approximately 11:00:55 — Midair collision.

11:03:17 — Radar contact with the damaged F-16 is lost near the eventual crash site. (NTSB Data)

From the first conflict alert to impact: roughly 42 seconds.

From the controller's initial traffic advisory to impact: roughly 39 seconds.

For two aircraft approaching at high relative speed, that is almost no time at all.

The NTSB Probable Cause

After its investigation, the National Transportation Safety Board determined:

“The approach controller's failure to provide an appropriate resolution to the conflict between the F-16 and the Cessna.”

The NTSB identified the inherent limitations of the see-and-avoid concept, which resulted in both pilots being unable to take evasive action in time, as a contributing factor. (NTSB Data)

This finding is significant because it does not assign the entire accident to the pilots.

The controller saw the conflict.

Yet the system still failed.

The safety margin had become too small.

Accident Facts

The NTSB final report identifies the accident as a midair collision involving N3601V and F-16CM 96-0085 near Moncks Corner. (NTSB Data)

What Changed After the Collision?

It became a training case.

In November 2016, the NTSB issued a safety recommendation report titled “Educating Controllers on Two Midair Collisions.” The report examined the Moncks Corner collision alongside another 2015 midair collision near San Diego. (NTSB)

The NTSB recommended that controllers and supervisors be briefed on the circumstances surrounding the accidents and that the cases be incorporated into controller training dealing with judgment, vigilance and safety awareness.

The Board also issued a safety alert emphasizing that pilots should not depend exclusively on visual acquisition for collision avoidance. (NTSB Data)

Berkeley County Airport subsequently increased local outreach concerning the area's military traffic and updated its chart information to highlight the presence of military and other traffic associated with Charleston. (NTSB Data)

The objective was not to blame VFR pilots for operating legally.

It was to make the surrounding system more predictable and more resistant to human error.

A Tragedy Created by a Narrow Safety Margin

The Moncks Corner collision is sometimes reduced to a simple headline:

F-16 hits Cessna. Two killed.

But the actual sequence was much more complicated.

A civilian aircraft departed legally under VFR.

A military fighter approached Charleston under IFR.

The Cessnappeared on radar.

The controller initially assumed it would remain near its departure airport.

The aircraft continued climbing.

A conflict alert activated.

The fighter began turning.

The controller expected a much more aggressive maneuver.

The Cessna continued climbing.

It was too late.

The Broader Aviation Safety Lesson

The July 7, 2015 Moncks Corner collision demonstrates why aviation safety cannot depend on a single defense.

See and avoid is important.

ATC traffic advisories are important.

Radar conflict alerts are important.

Flight-following is valuable.

Traffic-awareness technology can help.

Clear controller-pilot communication matters.

But each defense has limitations.

The controller can see a target but may misunderstand its intentions.

A pilot can receive a traffic advisory but fail to visually acquire the aircraft.

A fighter's radar can detect distant objects but may not provide useful collision-avoidance information for a small, slow civilian airplane.

A VFR pilot can legally operate without talking to ATC but may consequently miss information about nearby traffic.

And a maneuver that appears logical from an ATC traffic-flow perspective can become dangerous when aircraft are closing rapidly.

The most important lesson from Moncks Corner is therefore not simply “look harder.”

It is that the aviation system must recognize the limits of human vision and decision-making.

The NTSB's investigation showed that both pilots had difficulty seeing the other aircraft despite operating in good weather. The fighter pilot was actively searching and still did not acquire the Cessna until the final second. (NTSB Data)

The controller also recognized the developing conflict but did not resolve it conservatively enough.

That combination left almost no margin for recovery.

Two people aboard a small Cessna lost their lives.

A fighter pilot survived only because his aircraft's ejection system gave him a final escape option.

The accident ultimately reminds every pilot and controller of a fundamental principle:

When two aircraft are converging, the goal is not merely to provide instructions that can work. The goal is to create enough separation that the system still has room for a human being to make a mistake.

At Moncks Corner, there was not enough room.

Primary Source / Investigation Record

Investigation reference: ERA15MA259

Sources

• https://data.ntsb.gov/Docket?NTSBNumber=ERA15MA259