Catastrophic Engine Overspeed Causes Air National Guard F-16 to Crash Near Joint Base Andrews

A Retest, Then Another, Then a Pass

Before it was ever bolted onto the engine that would fail on 5 April 2017, the main engine control unit on F-16C tail number 87-0306 had already failed twice. Routine testing on 31 January found it didn't meet performance standards; a fuel cam spline was found misaligned, corrected, and the unit retested. On 16 February it failed again — this time for problems with the fan discharge temperature spring and a variable stator vane that wasn't repeating consistently. The unit went back to the shop again. On 8 March, it finally passed. It was installed on the engine the day before the accident.

Four Jets, One Training Mission

The F-16, from the 113th Wing's 121st Fighter Squadron out of Joint Base Andrews, Maryland, took off the morning of 5 April as part of a four-ship formation heading out for basic surface attack training — a routine mission, loaded with training rounds carrying less gunpowder than combat ammunition. During takeoff, the engine began accelerating uncommanded, well beyond its normal operating range.

Two Fuel Tanks, Two Houses, Neither One Hit

What followed happened fast. As the engine spiraled into overspeed, over-temperature, and then fire, the pilot jettisoned the aircraft's external fuel tanks — a standard procedure to reduce weight and fire risk, but one that sends heavy, fuel-laden tanks falling toward whatever's below. One tank came down between two houses. The other landed in a patch of woods. Neither struck a structure or a person — a detail that, in an accident investigation otherwise focused on engine hardware, stands out as the difference between a destroyed airplane and a genuine tragedy on the ground.

Steering Toward the Trees

With the engine fire growing and the aircraft's glide range to the nearest suitable runway beyond reach, the pilot made a deliberate choice: rather than eject immediately and let an unguided aircraft come down wherever momentum carried it, he steered the jet toward a wooded, unpopulated area near the town of Clinton, Maryland, before ejecting safely. The F-16 crashed and was destroyed. The pilot was uninjured. Investigators later credited his decision-making explicitly — choosing where the aircraft would go down, even in the last seconds before ejecting, rather than abandoning that choice to chance.

The Missing Ring and Pin

When investigators stripped down the failed main engine control, they found what three rounds of testing hadn't caught: it was missing a required 600-degree retaining ring and an anti-rotation pin inside the differential pressure pilot valve — small components whose absence let the unit incorrectly meter far more fuel into the engine than it should have. That excess fuel flow is what produced the overspeed, the extreme over-temperature, and ultimately the fire that made the engine unusable and the aircraft unflyable.

"No Evidence" Against the People Who Built It

The Air Force's Accident Investigation Board was explicit on one point: there was no evidence that the 113th Wing's own maintenance personnel or supervision played any role in the mishap. The missing hardware traced back through the unit's overhaul and repeated testing process — testing that flagged real problems twice before, on different components entirely, without ever catching the specific missing ring and pin that would ultimately bring the aircraft down.

Why Small Parts Get Formal Accountability

A retaining ring and an anti-rotation pin are, individually, among the smallest and least glamorous components in a fighter jet's engine — the kind of hardware easy to overlook amid the far larger, more visible parts that make up a modern turbofan.

Three Test Failures That Missed the Real Problem

What makes the maintenance history of this specific main engine control genuinely striking is how much testing it went through before installation, and how none of it caught the eventual cause.

A Formation Mission Continuing Without Its Fourth Jet

The F-16 was one of four aircraft departing together that morning on a basic surface attack training mission — a formation that, after the accident aircraft's departure and emergency, continued on with three.

What $22 Million and a Clean Field Represent

The Accident Investigation Board's report placed the total cost of the mishap at roughly $22.2 million for the destroyed airframe, plus an additional $856,777 in environmental cleanup costs from the crash site and the two jettisoned fuel tanks.