TRACE THE
FAILURE
AVIATION FAILURE

Nothing was broken.
It flew past the airport.

The King Air had two trained pilots and no mechanical problem. It crossed the Martinsville airport in cloud, kept going, and hit a mountain about 10 nautical miles on. All ten people aboard were killed.

Follow the evidence
The burned cabin section of a Beechcraft King Air beside a tree on a wooded mountainside, with two window openings still visible.
Wreckage of N501RH on Bull Mountain. NTSB docket photograph, Airworthiness Factual Report, Figure 5. Not AI-generated.
THE COMPANION FILMNASCAR's Deadliest Plane Crash: Why Did They Fly Past the Airport? Watch episode 16:56

Why the plane flew past the airport

On October 24, 2004, a Beech King Air 200 owned by Hendrick Motorsports crashed on Bull Mountain near Stuart, Virginia, on its way to the NASCAR race at Martinsville. All ten people aboard were killed. NTSB brief, p. 1 Nothing mechanical had failed. NTSB brief, p. 17

The NTSB’s best explanation is a GPS mix-up. The flight path fits a crew who believed their GPS was counting down to a radio marker five nautical miles before the runway, when it had already moved on and was counting down to the airport itself. That would put the whole descent about five nautical miles late. NTSB brief, pp. 17 to 18 The explanation is an inference from radar. The plane carried no cockpit voice recorder or flight data recorder, and none was required, so nobody knows what was said in the cockpit. NTSB brief, p. 9

By our count this is the deadliest plane crash in NASCAR history: ten dead, against seven, five and four in the other crashes in our record. No source ranks them, so that comparison is ours.

Watch the episode

The film follows the flight on a map built from the NTSB’s radar returns, then follows NASCAR’s other losses in the air, up to Greg Biffle’s crash in December 2025.

The upgrade that went to the other plane

In 2004 NASCAR traveled by private plane. More than 100 aircraft flew from Concord, North Carolina, on many race weekends, and drivers called it a necessity. AP, October 29, 2004 Hendrick ran a flight department of 18 pilots with aircraft up to Gulfstream IIs, under Part 91, the rules for private flying. NTSB brief, p. 14 It reported never having had an accident, and said management “wanted it done right.” NTSB brief, p. 15

The company had two King Air 200s. This one, N501RH, had no terrain warning system. It had been for sale, so the upgrade went on the other King Air. The buyer then chose that other airplane, and N501RH went back on the line, with its own upgrade scheduled for the end of the 2004 racing season. NTSB brief, p. 7 By our reading, a federal rule would have required one on this plane after March 29, 2005, about five months after the crash. 14 CFR 91.223 The NTSB doesn’t make that link.

The plane had a GPS, but its database was out of date, so it wasn’t certified for instrument flight, the rules for flying in cloud. NTSB brief, p. 7

How the approach worked

Martinsville’s approach depended on one point: BALES, a radio marker five nautical miles before the missed approach point at the runway. Pilots stayed at 2,600 feet until they passed BALES, then could descend to 1,340 feet. If they reached the runway and still couldn’t see it, they climbed and turned right. NTSB brief, pp. 1 to 2

A controller told the crew to hold near BALES at 4,000 feet and expect a 28-minute delay. The plane ahead then broke out of the clouds and landed, and the King Air was cleared for the approach while still turning. That took it across BALES inbound at 3,900 feet, against the 2,600 expected. NTSB brief, pp. 1 to 2 and 17

The GPS explanation

Hendrick’s pilots said they used the GPS only as a backup. Its normal setup held two points, BALES and the airport, and it moved from the first to the second by itself at the first crossing. On this approach, that means it would have switched when the plane crossed BALES going into the hold. NTSB brief, p. 18

The NTSB says the flight profile fits a crew who didn’t notice that switch. A distance that looked like the miles left to BALES would have been the miles left to the airport, and the approach they flew sits about five nautical miles from the published one. NTSB brief, pp. 17 to 18

Other instruments could have caught it, and the NTSB said the crew didn’t use all the navigation aids available. On this plane the GPS sat between the pilots, below the seat cushion, so reading it meant turning your head 90 degrees and looking down. NTSB brief, p. 13, note 6 The NTSB didn’t say that placement caused the crash.

The question two days earlier

Two days before the crash, First Officer Elizabeth Morrison flew to Martinsville with a different captain. He read 2.9 miles off the GPS, and she asked, “Where did you get that DME?” DME is the distance readout on the main panel, and she sent him back to it. He told investigators about it afterward. NTSB docket, Operations Group report, pp. 11 to 12

That connection to Sunday is ours, and the NTSB’s analysis doesn’t make it. It’s one pilot’s recollection, and that day she had loaded only BALES into the GPS, so we can’t prove it was the same mix-up. On Friday, somebody noticed. Nobody knows if anyone asked on Sunday.

Over the airport and on

The King Air reached the point where it should have turned away still at 2,600 feet. It kept descending past the airport and leveled at about 1,400 feet. NTSB brief, p. 2 Witnesses at the airport heard it pass overhead with its engines smooth, though one said they sounded at idle, and they couldn’t see it. NTSB brief, p. 5

At 12:30:07, about 2.5 nautical miles past the airport, a low-altitude alarm fired for 15 seconds on the controller’s display in Greensboro. He said he neither saw nor heard it. NTSB brief, p. 9 The NTSB ruled it wasn’t a factor: radar service had already ended, and the plane stayed below radar coverage afterward. NTSB brief, p. 17

The last minute

The plane flew level at 1,400 to 1,500 feet for 1 minute 13 seconds, with the ground rising beneath it. Two witnesses saw a plane “flat and level,” very low, in fog, with its gear up and no sign of distress. NTSB brief, pp. 2 and 5

About 8 nautical miles past the airport it began a straight-ahead climb. The crew called, “we’re going missed,” and the controller told them to climb to 4,400 feet. The radar target was lost at 12:33:24. NTSB brief, pp. 2 and 5 The plane hit Bull Mountain at about 2,400 feet, about 10 nautical miles past the airport by our measurement of the NTSB’s radar table. Aircraft Performance report

The published missed approach was a climbing right turn. The NTSB’s study found that a right turn when the climb began would have cleared the terrain. The NTSB got that by interpolating the data, without a flight test. NTSB brief, p. 11

At Martinsville, the race went on. NASCAR learned during the race that the plane was missing and kept it from the Hendrick drivers until the end. Jimmie Johnson won and was excused from Victory Lane. AP, October 25, 2004

What the NTSB found

The NTSB adopted its brief on February 7, 2006. It found no mechanical problem and gave this probable cause:

“the flight crew’s failure to properly execute the published instrument approach procedure, including the published missed approach procedure, which resulted in controlled flight into terrain. Contributing to the cause of the accident was the flight crew’s failure to use all available navigational aids to confirm and monitor the airplane’s position during the approach.” NTSB brief, p. 18

The NTSB never said a terrain warning or a different GPS position would have saved this flight.

What changed, and what didn’t

Hendrick put a terrain warning on every aircraft. It created aviation director, safety manager and full-time dispatcher jobs, formed a safety committee and moved to two training sessions a year. The NTSB noted that some of this was already planned. NTSB brief, p. 15

NASCAR had lost people in the air before. Alan Kulwicki and three others died in April 1993 on a flight to Bristol, and the NTSB cited the pilot’s failure to follow engine anti-ice procedures. Summary of the record Ice has brought down many other planes. Three months later, Davey Allison died trying to land his helicopter in a small lot at Talladega. NTSB finding, via Spokesman-Review The week of Martinsville, AP wrote that NASCAR’s aircraft had “a very good safety record.” AP

In July 2007, NASCAR’s own Cessna 310 crashed in Sanford, Florida, killing both pilots and three people on the ground, and the NTSB blamed NASCAR’s aviation division and the pilots for flying with a known, unresolved problem. In that report, the NTSB said safety programs could help company flight departments, noted that Hendrick had adopted one, and said the FAA “has done nothing to ensure” that others did. NTSB AAR-09-01

After Jack Roush’s crash in 2010, Greg Biffle told reporters the planes were much safer because they had ground warning systems. FOX Sports In 2019, Dale Earnhardt Jr. and his family survived a crash at Elizabethton after an unstabilized approach the crew didn’t abandon. NBC Sports

On December 18, 2025, Biffle, his family and three others died in a jet crash at Statesville, North Carolina. The NTSB’s preliminary report gives no cause. Preliminary report, via AVgeekery On November 6, 2026, the NTSB’s investigation page still said the probable cause will come in the final report.

The ten people on Bull Mountain were Ricky Hendrick, John Hendrick, Jennifer and Kimberly Hendrick, Jeff Turner, Randy Dorton, Joe Jackson, Scott Lathram, Richard Tracy and Elizabeth Morrison. AP

Primary sources

The distance past the airport is our measurement from the NTSB’s radar table. The hero image and preview artwork are NTSB docket photographs of the accident airplane, not AI images. The film’s maps and diagrams are illustrations built from public records, not an official reconstruction.