F-16 Runway Overrun, F/A-18 Emergency, and Fatal C130 Crash during cargo dropping

F-16 Runway Overrun, F/A-18 Emergency, and Fatal C-130 Crash During Cargo Dropping

Three military aircraft. Three very different emergencies.

One F-16 arrived at Oshkosh for an airshow and ended up sliding beyond the runway after the pilot's cockpit became almost completely obscured by fogging.

Years earlier, an F/A-18 Hornet suffered a serious engine emergency off the California coast. The pilot was trying to get back to base, but a decision to continue toward his home station instead of taking the nearer divert field left the aircraft with dangerously few options.

And at Fort Bragg, a C-130 Hercules was performing an extremely demanding low-altitude cargo-extraction demonstration when the aircraft descended into the ground and crashed in front of thousands of spectators.

These incidents were not connected. They occurred at different times and involved different services, aircraft and missions. But they share an important aviation-safety theme: military aircraft often operate with narrow margins, and once those margins disappear, there may be almost no time left to recover.

It is also important to clarify the investigative sources. These were U.S. military mishaps, so the primary investigations were conducted by the U.S. Air Force or U.S. Marine Corps, rather than the NTSB. The NTSB does not issue probable-cause reports for these military mishaps in the same manner it does for civil accidents. Accordingly, this reconstruction uses the applicable military investigation material and contemporary reporting rather than inventing NTSB findings.

The F-16 Runway Overrun at Oshkosh

On July 28, 2011, an Alabama Air National Guard F-16C arrived at Wittman Regional Airport in Oshkosh, Wisconsin, during the enormous EAA AirVenture gathering.

The aircraft, tail number 87-0296, belonged to the 100th Fighter Squadron of the 187th Fighter Wing and was flying as the second aircraft in a two-ship formation.

The landing initially looked routine.

Then the pilot's view began disappearing.

According to the subsequent Air Combat Command investigation, the F-16's environmental control system produced extreme fogging inside the cockpit during the landing sequence. The pilot attempted the prescribed defog procedure, but the problem did not clear. His normal visual references were severely degraded. (AVweb)

The aircraft continued down Runway 36.

But the pilot could not see the runway environment normally.

The F-16 eventually departed the paved runway and continued approximately 300 feet beyond its end. The nose gear collapsed and the aircraft came to rest in the grass. The pilot was not injured. (AVweb)

The aircraft, however, suffered approximately $5.4 million in damage.

A High-Performance Aircraft With a Visibility Problem

The investigation is particularly interesting because the accident was not simply a case of the pilot landing too fast.

The pilot was operating a high-performance fighter at an unfamiliar civilian airport environment during a major aviation event.

The cockpit fogging was the central problem.

When a pilot loses his visual references during the landing roll, seemingly simple tasks become much harder. Judging remaining runway, recognizing directional drift and determining how much stopping distance remains all depend on reliable visual information.

The F-16 investigation found that the pilot correctly attempted the defog procedure, but the fogging persisted. The loss of visual cues contributed directly to the difficulty in executing the normal landing procedure. (AVweb)

There were additional factors.

The aircraft touched down with more speed than desired, and the pilot's aerodynamic braking was insufficient to compensate for the increased landing distance. The combination of high touchdown energy and degraded visibility left little room to recover. (AVweb)

The runway itself was approximately 8,002 feet long, meaning this was not simply an aircraft being forced onto an obviously inadequate strip. The safety margin was consumed by the combination of aircraft energy and the cockpit visibility problem. (Hugging Face)

Contemporary FAA safety material also noted that Oshkosh had received substantial rain in the preceding days and that wet-runway conditions can further reduce braking effectiveness. (FAA Safety)

The accident illustrates an important point:

A runway overrun can begin before touchdown.

If the aircraft crosses the threshold too fast, if the pilot loses his visual references, or if braking effectiveness is degraded, the available stopping margin can disappear remarkably quickly.

The F/A-18 Emergency Over San Diego

The second incident was considerably more serious.

On December 8, 2008, Marine First Lieutenant Dan Neubauer was flying an F/A-18D Hornet during carrier-qualification operations aboard the USS Abraham Lincoln, approximately 60 miles southwest of San Diego.

The aircraft was BuNo 164017, assigned to VMFAT-101 at Marine Corps Air Station Miramar.

Shortly after departure, the pilot received an oil caution indication for the right engine.

He attempted to deal with the problem, but the indication could not be resolved.

The right engine was shut down.

The pilot declared an emergency. (Wikipedia)

Now the emergency became a question of where the aircraft should land.

North Island or Miramar?

The nearest suitable military airport was Naval Air Station North Island, located on the Coronado peninsula.

Controllers directed the pilot toward North Island.

That was the conservative choice.

According to the Marine Corps investigation, that decision became one of the central factors in the accident.

The aircraft was experiencing an engine emergency, and the remaining engine also had a history of fuel-system problems.

Those problems had existed for months.

Maintenance had been deferred under rules that were then in effect, and the aircraft had continued flying numerous sorties despite the known issue. The investigation found that when the right engine was shut down, the left engine could not obtain enough fuel to produce sufficient thrust to keep the aircraft safely airborne. (Wikipedia)

The situation had therefore become far more serious than a single-engine failure.

The Hornet was now effectively losing its remaining power source.

The Emergency Gets Worse

The Marine Corps investigation later concluded that the flight toward Miramar unnecessarily consumed additional time and distance.

The pilot also did not fully follow the emergency procedures investigators expected, including use of the applicable emergency checklist.

The approach toward Miramar was extended by a large turn rather than taking the shortest available path. (Wikipedia)

That matters enormously in an emergency.

An aircraft with one functioning engine can have substantial capability.

An aircraft with a failing remaining engine is a completely different situation.

Every additional mile means less altitude margin.

Every additional turn means more energy and time consumed.

And every minute spent flying toward a farther runway is a minute that cannot be recovered later.

The Marine Corps investigation eventually characterized the decision-making as a series of errors involving the pilot and supervisory personnel.

The Final Approach

As the F/A-18 approached Miramar, the remaining engine lost the ability to provide the required thrust.

The Hornet was now too low to recover.

The pilot attempted to keep the aircraft away from populated areas.

At approximately 11:59 a.m., the fighter crashed into the University City neighborhood, about two miles from MCAS Miramar.

The pilot ejected successfully and survived.

Four civilians on the ground were killed.

The victims were members of one family: Young Mi Yoon, her two young daughters, and her mother, Suk Im Kim. The crash destroyed the family's home and also affected a neighboring residence. (Wikipedia)

The accident was severe not only because of the mechanical failure but because the aircraft was carrying its emergency into a densely populated area.

The Investigation

The Marine Corps released the results of its investigation in March 2009.

The conclusion was unusually direct: the accident was considered preventable.

Four officers—including the squadron commander and senior maintenance and operations personnel—were relieved of duty. Nine additional Marines received disciplinary action. (OB Rag)

Investigators found that the aircraft had a history of fuel-system trouble involving the left engine.

The emergency therefore exposed an organizational weakness as well as an aircraft-system problem.

The investigation also concluded that the decision to continue toward Miramar rather than land at North Island was a critical error.

North Island provided a shorter route and an approach largely over water.

This is one of the clearest lessons from the accident:

During an emergency, familiarity is not necessarily safety.

A pilot may understandably prefer a familiar base with longer runways, known procedures and maintenance support.

But if another suitable runway is closer, the nearer field may provide the greatest survival margin.

The Marine Corps investigation specifically concluded that landing at North Island was the prudent choice. (OB Rag)

The Fatal C-130 Cargo-Drop Crash at Fort Bragg

The third accident occurred on July 1, 1987, at Fort Bragg, North Carolina.

A U.S. Air Force C-130E Hercules, tail number 68-10945, was participating in a capabilities exercise at the Sicily Drop Zone.

Thousands of people were watching.

The C-130 was demonstrating a specialized technique known as LAPES — Low Altitude Parachute Extraction System.

Unlike a conventional high-altitude airdrop, LAPES involves flying extremely close to the ground while a parachute extracts a heavy load through the rear of the aircraft.

The technique allowed tactical airlift crews to deliver large loads in environments where conventional landing or high-altitude parachute delivery might not be practical.

But the price was an extremely small altitude margin.

Flying Almost on the Ground

During LAPES, the C-130 must maintain precise control while operating only a few feet above the surface.

The aircraft approaches the drop zone at low altitude.

A parachute is deployed.

The parachute catches the airflow and pulls the cargo from the rear of the aircraft.

As the load leaves, the aircraft's weight and center of gravity change.

The pilot must maintain control and then climb away.

There is almost no time to correct a major deviation.

The C-130 crew had already successfully completed one demonstration.

The second approach did not go as planned.

Contemporary reporting and the military accident investigation described an excessive descent rate and an inadequate or delayed flare. The aircraft struck the ground, continued forward and eventually broke apart and burned. (U.S. Department of War)

The Crash in Front of Thousands

Witnesses reported that the aircraft came in extremely low and appeared to be struggling to recover.

It struck the ground and continued toward the edge of the demonstration area.

The aircraft then broke apart and erupted into flames. (UPI)

Six crew members were aboard.

Four of them died.

Two survived with serious injuries.

A soldier on the ground was also killed.

The aircraft narrowly missed the large spectator area.

Contemporary UPI reporting described spectators initially struggling to understand what they had witnessed before realizing that the aircraft had crashed. (UPI)

The accident therefore had an unusually large potential for casualties.

Had the aircraft deviated only slightly farther toward the crowd, the consequences could have been much worse.

The Cargo Was Part of the Problem—and the Mission

That was not a normal cargo drop.

The technique was designed specifically to deliver very heavy equipment at extremely low altitude.

The aircraft had to maintain precise flight parameters while the cargo was extracted.

The accident demonstrated why low-altitude cargo extraction has historically been regarded as one of the most demanding airlift techniques.

There was almost no room for pilot error.

The C-130 had already successfully completed one demonstration.

But a previous successful maneuver does not guarantee that the next one will remain within the same margins.

That is an important training lesson.

Repetition can create confidence, but confidence must never replace precise energy and altitude control.

What These Three Accidents Have in Common

The F-16, F/A-18 and C-130 were performing completely different missions.

Yet each accident demonstrates the same underlying principle:

The final few seconds are usually the end of the accident chain—not the beginning.

For the F-16, the runway overrun was not caused by one simple action. Cockpit fogging compromised visibility, touchdown energy was high and aerodynamic braking was insufficient. (AVweb)

For the F/A-18, the eventual crash was preceded by a known aircraft-system problem, an emergency engine shutdown, a questionable divert decision, procedural shortcomings and organizational decision-making. (Wikipedia)

For the C-130, the final impact followed an extremely demanding low-altitude maneuver in which the aircraft descended too rapidly and did not recover before striking the ground. (U.S. Department of War)

None of these accidents can be fully understood by watching only the final seconds.

Accident Facts

The Broader Aviation Safety Lesson

These three military accidents demonstrate why preserving options is one of the most important principles in emergency aviation.

The F-16 needed sufficient stopping margin after losing normal cockpit visibility.

The F/A-18 needed the shortest and safest route to a suitable runway after suffering a serious engine emergency.

The C-130 needed enough energy and altitude margin to recover from a deviation during a maneuver conducted only feet above the ground.

Once those margins disappeared, the pilots had very little left to work with.

The F-16 pilot survived because he kept the aircraft on the runway long enough to avoid a catastrophic crash, even though the fighter ultimately left the paved surface.

The F/A-18 pilot survived his aircraft's destruction because he ejected before impact, but four civilians who had no role in the emergency lost their lives.

At Fort Bragg, the C-130 crew was performing a mission designed to train for real-world tactical resupply, but the extremely low altitude left almost no room to recover from an unstable maneuver.

The larger lesson is not simply that military flying is dangerous.

It is that danger increases rapidly when pilots, controllers and organizations allow an emergency to consume the available margin.

A familiar runway is not necessarily the safest runway.

A long runway is useless if the pilot cannot see it properly.

And a mechanical problem that has been deferred does not become less important simply because the aircraft has completed another sortie without an accident.

These cases also show why accident investigations look beyond the aircraft itself.

Investigators examine maintenance records, crew decisions, procedures, training, supervision, airport conditions and the choices made before the final emergency.

That is where the most valuable lessons are found.

The F-16 overrun shows the importance of maintaining stopping margin when visual information suddenly deteriorates.

The F/A-18 tragedy shows why emergency diversions must be judged by survivability rather than familiarity.

The C-130 crash demonstrates how specialized low-altitude operations demand absolute discipline because there may be no altitude available to recover from a mistake.

Three aircraft.

Three different emergencies.

Three different chains of events.

But one common principle remains:

The safest flight is the one that preserves enough margin for the unexpected.

Once that margin is gone, even highly trained military crews can find themselves with only seconds to save an aircraft—and sometimes, seconds are not enough.

Sources

• Video source (ATC/audio reconstruction)

• U.S. Air Force / Air Combat Command investigation of F-16C 87-0296, Wittman Regional Airport, July 28, 2011. Contemporary reporting on the official investigation identified severe environmental-control-system fogging as the primary cause, with excessive touchdown speed and inadequate aerobraking as contributing factors. (AVweb)

• FAA safety analysis concerning the 2011 Oshkosh F-16 overrun and wet-runway considerations. (FAA Safety)

• U.S. Marine Corps investigation into the December 8, 2008 F/A-18D BuNo 164017 crash in San Diego, summarized in contemporary Marine Corps findings and reporting. (Wikipedia)

• Contemporary reporting and ATC-related coverage of the San Diego F/A-18 emergency and crash. (The Washington Post)

• U.S. Air Force accident investigation material concerning C-130E 68-10945, Sicily Drop Zone, Fort Bragg, July 1, 1987. Contemporary reporting based on the investigation documented the aircraft's flight hours, damage and circumstances. (U.S. Department of War)

• Contemporary UPI reporting from the July 1, 1987 Fort Bragg C-130 crash, including the LAPES demonstration, casualties and spectator response. (UPI)

• Bureau of Aircraft Accidents Archives cross-reference for the Fort Bragg C-130E accident. (Bureau of Aircraft Accidents Archives)