Greenacres Learjet Crash: Weather and Midair Breakup Investigation

At 12:47 on a Sunday afternoon, a 20-year-old co-pilot keyed her microphone over the Gulf Coast of Florida and told Miami Center that her jet was picking up ice.

Light, clear ice. "Manageable," she said.

Moderate turbulence, the kind that was throwing the airplane up and down by about 700 feet at a time.

Outside the windows, it was -47 degrees Celsius.

She asked for a smoother ride. The controller told her to expect one.

90 seconds later, she was shouting into the same radio that the airplane was descending at 20,000 feet per minute and that they were going to hit the ground.

Then the frequency went quiet. What hit a road in Greenacres, Florida, a few miles southwest of Mar-a-Lago, was a Learjet 60 with nine people inside it.

It came in nose first at more than 300 miles an hour, fast enough that the FAA described the descent as 350 feet every second.

The airplane did not crash so much as it detonated.

A dash cam on a passing car caught a white streak, a fireball, and then a crater in the asphalt where the road used to be.

One man in a vehicle beside the impact point walked away with a leg injury.

Nobody on board had a chance. Within hours, we knew the names.

Adam Robinson, a 44-year-old Austin Tech founder.

His wife, Helen Sharp. Their children, Emma, four, and Charlie, two.

The family nanny. Two close friends, Captain Jeff Gregory, 55, from a small town northwest of Philadelphia, and the co-pilot on the radio, Nathalia Pilgueras, 20 years old, who had earned her private license at 17 through a high school aviation program in the same county where she died.

Within a day, the National Transportation Safety Board had more than 20 investigators on the scene, and the man running the briefings, board member Tom Chapman, said something that changed the shape of the whole story.

"There was evidence," he said, "that the airplane had started coming apart before it hit the ground."

That single sentence is why this is not a simple crash.

Airplanes fly into thunderstorms and come out the other side every day.

Airplanes pick up ice at altitude and shed it every day.

An airplane that goes from level cruise to a vertical dive in under half a minute, that scatters its tail across four miles of suburbs on the way down, and whose cockpit recorder may or may not have even been on board, that is a different category of event.

So here's what the official account says happened, here's where it stops making sense, and here's what the people who have spent their lives investigating exactly this kind of accident are quietly pointing at.

Start with the thing everyone can see. FlightRadar24 took the jet's position data and laid it over the weather radar from that afternoon, and the picture is hard to look at.

South Florida was covered in scattered cells.

The Learjet threads its way around a large one and then flies straight into a small red cell that is building upward at the exact moment the track line meets it.

The National Weather Service observation 15 minutes before the crash recorded thunderstorms near the site with three miles of visibility.

Storm tops in the area were reported to reach 48,000 feet.

The crew is at 35,000. That number is the first thing that bothers the experts because the airplane had not been at 35,000 for most of the flight.

It had been cruising at 41,000. Retired airline captain John Cox, who has spent decades on accident work, said he does not understand why the airplane came down from 41 as it approached the weather.

"If you are looking at thunderstorms," he said, "you would rather be at 41 than 35.

Descending toward the tops of a growing storm is the opposite of what you want to do."

Then there is the radio. Less than 20 minutes before the crash, while the jet was still near the Gulf Coast, a controller warned the crew that the turn they had requested toward the Bahamas could take them into a thunderstorm.

They continued. Other pilots on the frequency that afternoon can be heard asking for and receiving deviations around the weather.

This crew did not. When they asked for a better route, the controller told them to expect better rides ahead.

Then they reported precipitation and asked to climb 2,000 feet.

The controller approved 37,000. Less than 30 seconds after that clearance, the airplane was falling.

Michael Henderson, who runs an aviation law practice and a flight school in California, put the question bluntly.

"The weather destroyed the plane," he said, "but the question is why they flew into it."

And then he added something aviation lawyers do not usually say out loud this early.

He said he is tired of hearing that it was all pilot error, that they flew into a cell, and that is the end of it.

There is more behind this than weather. To be fair to the two people who cannot defend themselves, the picture on the radar overlay is not the picture they were looking at.

Ground-based weather radar lags real weather by several minutes.

A cell that shows as a small red dot on the archived image may have been a growing tower on the airplane's own nose radar, or it may have been hidden entirely behind a wall of rain in front of it.

Attenuation, the way heavy precipitation masks whatever sits behind it, is a known killer.

The FAA's own guidance says to stay 20 miles from any storm giving an intense echo.

We do not know what the Learjet's radar showed.

We do not know whether it was working. We do not know whether the crew had satellite weather on an iPad or whether they looked at it.

What we do know is that the airplane spent the last 20 minutes of its life being nudged by a route request, by a descent, by a climb clearance, closer to the one cell on the screen it needed to avoid.

And an airplane pushing through the tops of a growing storm at 35,000 feet in icing and turbulence strong enough to move it 700 feet at a time is being backed into a corner.

In this particular airplane, the corner has a name.

We will get to it. On Tuesday, two days after the crash, the NTSB announced that it had recovered most of the Learjet's left elevator.

The elevator is the hinge surface on the back of the horizontal stabilizer.

The small wing on the tail, and it is what the pilots use to point the nose up or down.

It was found in three pieces. The closest piece was one point three miles from the crater.

The farthest was three point eight miles away.

Chapman called it a very important piece of evidence, and it is, because a part found four miles from the impact did not get there by bouncing.

It came off in the air. The debris field the NTSB mapped is half a mile long and four-tenths of a mile wide, spread across ball fields, businesses, and people's homes.

By Thursday, the agency was asking residents to check their roofs.

Pieces of this airplane were landing on houses.

Here is where the investigators split, and the split is the heart of the mystery.

Pitch control is the whole game in a dive.

If the elevator, or worse, the entire horizontal stabilizer, came off at altitude, then everything the crew said on the radio was a description of an airplane they had already lost.

They were passengers in the front seats.

Jeff Guzzetti, a former NTSB and FAA investigator, said that if that happens, you cannot control the airplane, and that it would explain the missile-like profile just before impact.

But there is a second reading, and it is an uncomfortable one.

The tracking data shows the airplane briefly arresting its dive somewhere around eight thousand feet.

John Goglia, a former NTSB board member, looked at that and reached a different conclusion.

The pilot, he said, apparently leveled off for a few moments at eight thousand feet, and in doing so, likely overstressed the tail and the horizontal stabilizer separated.

Greg Feith, another former senior NTSB investigator, said much the same thing on Fox.

A pilot pulling with everything he had to save his passengers may have been the one who tore the tail off.

Both readings fit the debris. Goglia's point is that if the tail had let go at thirty-five thousand feet, the pieces would be far more than four miles away.

Pieces that land between one and four miles out are consistent with separation much lower during a recovery attempt in an airplane already moving far faster than it was ever built to go.

Then there is the video. A former Navy fighter pilot who went frame by frame through the dash cam footage says the tail looks wrong in the final frames before impact.

The silhouette appears smooth, as if the horizontal stabilizer is simply not there.

The NTSB has said publicly that it is still trying to determine whether the stabilizer came off before impact, which is a careful way of saying it has looked at the same frames and cannot rule it out.